Network Management and Monitoring | Junos OS Evolved

sFlow: debugging & traceability support (PTX10001-36MR, PTX10004, PTX10008, and PTX10016)—Starting in Junos OS Evolved Release 22.4R1, we have implemented ingress and egress sFlow functionalities for transit nodes with PTX10008 and PTX10016 devices. This functionality is supported for IPV4-in-IPV4, IPV6-in-IPV4, and regular IPv4/IPV6 traffic.

In transit-only devices, the IP-in-IP encapsulated packet can transit through the device without any change or may get "decapsulated and forwarded" or "decapsulated and encapsulated" and forwarded based on the NextHop configuration.

Additionally, the packet may traverse through multiple VRFs while getting forwarded. For all those variations, we support ingress and egress sFlow. The functionality caters to sFlow capabilities for ECMP traffic as well.

[See sFlow Monitoring Technology.]

SNMP infra enhancements on Junos OS Evolved—Starting in Junos OS Evolved Release 22.4R1, the show snmp stats-response-statistics is made available. This command displays statistics of SNMP responses sent from the Packet Forwarding Engine during the MIB II process (mib2d). We've also introduced the MIB objects for managing tunnels of any type over IPv4 and IPv6 networks.

[See show snmp stats-response-statistics and Standard MIBs for Junos OS Evolved.]

Use the gRIBI service to program next hops with MAC addresses (PTX10004, PTX10008, and PTX10016)—Starting in Junos OS Evolved Release 22.4R1, we have enhanced the gRPC Routing Information Base Interface (gRIBI) service to allow you to program next hops with MAC addresses instead of IP addresses. This feature is useful in networks where devices cannot use dynamic Address Resolution Protocol (ARP) or Neighbor Discovery Protocol (NDP) to look up the next hop's MAC address.

To program the next hop using the MAC address, include the MAC address and the outgoing logical interface name in the NextHop AFT message. To confirm that the route was programmed successfully, use the show route programmed command in the CLI.

[See gRIBI.]

Support for additional family in port mirroring (PTX10003)—Starting in Junos OS Evolved Release 22.4R1, you can configure family any (as well as the earlier family options, inet and inet6) for local port mirroring and remote port mirroring:

Family any (for family any, ccc, ethernet-switching, or mpls)

Note:

You use the family any configuration option to process all four families.

As of Release 22.4R1, you no longer configure port mirroring by using the [edit forwarding-options port-mirroring analyzer] hierarchy on the PTX devices. You now use [edit forwarding-options port-mirroring] for local port mirroring or

[edit forwarding-options port-mirroring instance
            instance-name]

for remote port mirroring, with both of those configurations also requiring a firewall filter.

The following configuration statements are no longer part of the port mirroring configuration on PTX: next-hop for family any; family vpls; no-filter-check; hosted-service; and server-profile.

[See port-mirroring .]