Network Management and Monitoring | Junos OS Evolved

Support for multiple gRPC servers hosting different service sets (ACX7024, ACX7024X, ACX7100-32C, ACX7100-48L, ACX7332, ACX7348, ACX7509, PTX10001-36MR, PTX10002-36QDD, PTX10003, PTX10004, PTX10008, PTX10016, QFX5130-32CD, QFX5130-48C, QFX5130-48CM, QFX5130E-32CD, QFX5220, QFX5230-64CD, QFX5700, and QFX5700E)—You can configure multiple gRPC servers that host different sets of services on unique ports. Additionally, each server can support different certificates, listening addresses, and routing instances. You configure the gRPC servers at the [edit system services http servers] hierarchy level. Distributing gRPC services across different servers allows for better allocation of network resources, reducing the risk of port conflicts and optimizing server performance.

[See Configure gRPC Services and server.]

Support for controller card power management using gNMI and gNOI (PTX10001-36MR, PTX10008, and PTX10016)—You can manage the power state of Routing Engines using the gRPC Network Management Interface (gNMI) and gRPC Network Operations Interface (gNOI) services. Use gNMI for configurations that persist across reboots, ensuring the controller card remains powered off. Use gNOI to temporarily power down a Routing Engine until the next reboot. This capability is particularly beneficial for troubleshooting and isolating faulty cards. To use the gNMI service, configure the path /components/component/controller-card/config/power-admin-state and set the value to "POWER_DISABLED" or "POWER_ENABLED" for the target Routing Engine. For the gNOI service, use the System service Reboot() RPC with the POWERDOWN or POWERUP option and specify the target Routing Engine.

[See gNOI System Service and Sensor Power-State Management Support Using gNMI.]

gNOI OS service RPC updates (PTX10001-36MR, PTX10003, PTX10004, PTX10008, and PTX10016)—We've updated the gRPC Network Operations Interface (gNOI) OS service remote procedure calls (RPCs) to more efficiently manage software upgrades. These changes enable you to install software without immediate activation, validate the current configuration against any installed software version, and activate any installed software version.

The Install() RPC copies the software installation package to the device, validates the configuration against the specified software version, and installs the software. The Activate() RPC sets the specified software version as the next boot version. If the specified software version is already installed on the device, Install() instead validates the current configuration against the existing software image and stores the validated current configuration as the running configuration associated with that image. In previous releases, the Install() RPC only copies the software installation package to the device. The Activate() RPC performs the rest of the actions—validates the configuration, installs the software, and sets the software version as the next boot version.

[See gNOI Operating System (OS) Service.]

SNMP MIB walk and traps support for coherent ZR optics (ACX7024, ACX7024X, ACX7100-32C, ACX7100-48L, ACX7332, ACX7348, ACX7509, PTX10001-36MR, PTX10002-36QDD, PTX10003, PTX10004, PTX10008, and PTX10016)—Use SNMP MIB walk and traps to efficiently monitor and manage coherent ZR optics, including 100ZR, 400ZR, 400ZR-M, and 400ZR-M-HP. Use this feature to retrieve OID information sequentially and receive notifications when alarms are triggered or cleared. This enhancement extends SNMP MIB walks to include new digital optical monitoring (DOM) fields and implements SNMP traps for critical alarms.

[See Enterprise-Specific MIBs for Junos OS Evolved and show snmp mib.]

SNMP support for coherent ZR optics performance monitoring and threshold alerts (PTX10001-36MR, PTX10002-36QDD, and PTX10003)—You can monitor the performance of coherent ZR optics (100ZR, 400ZR, 400ZR-M, and 400ZR-M-HP) and receive threshold crossing alerts using SNMP. Retrieve real-time, historical, and statistical data for various performance parameters through SNMP Get requests. You also can receive trap notifications for threshold crossing alerts and clear events.

Use the updated enterprise MIB named Juniper-IFOPTICS-MIB to comprehensively monitor and manage coherent ZR series transceivers.

[See show snmp mib, Enterprise-Specific MIBs for Junos OS, and SNMP MIB Explorer.]

Export of extended gateway structure in sFlow records (PTX10001-36MR, PTX10003, PTX10004, PTX10008, and PTX10016)—You can export an extended gateway structure in sFlow records. The extended gateway structure includes BGP next-hop, autonomous system (AS) numbers, and community data. You must configure the extended-gateway option at the [edit protocols sFlow family structure-list] hierarchy level to export an extended gateway structure in sFlow records.

The sFlow functionality is managed by the sflowapp application instead of the sflowd process. This enhancement improves the sFlow scaling and integrates BGP-related data, such as AS numbers and communities, into the sFlow records, facilitating more comprehensive network monitoring and analysis.

[See sFlow Technology Overview and sFlow.]

sFlow configuration support for aggregated Ethernet bundles (PTX10001-36MR, PTX10002-36QDD, PTX10003, PTX10004, PTX10008, and PTX10016)—You can configure sFlow over an aggregated Ethernet bundle and manage sFlow sampling for all interfaces within the bundle through a single configuration command. This feature improves efficiency with sFlow configured at the aggregated Ethernet interface level in the CLI, and individual interfaces configured at the physical interface level. Use the command set protocols sFlow interfaces ae0 sample-rate ingress 1 to set the sampling rate for the aggregated Ethernet bundle.

[See sFlow Technology Overview and sFlow.]