Help us improve your experience.

Let us know what you think.

Do you have time for a two-minute survey?

Enabling Packet Flow Monitoring on SONET/SDH Interfaces

 

You can enable packet flow monitoring on SONET/SDH interfaces.

This topic includes the following tasks:

Configuring Packet Flow Monitoring on a SONET/SDH Interface

To configure packet flow monitoring on SONET/SDH interfaces:

  1. In configuration mode, go to the [edit interfaces so-fpc/pic/port unit logical-unit-number] hierarchy level.
  2. Configure packet flow monitoring to monitor packet flows from another router.
    Note
    • If you include this statement in the configuration, the SONET/SDH interface does not send keepalives or alarms, and does not participate actively on the network.

    • For SONET/SDH interfaces, you can include this statement on the logical interface only.

Configuring Packet Flow Monitoring on a Monitoring Services Interface

To configure packet flow monitoring on a monitoring services interface:

  1. In configuration mode, go to the [edit interfaces mo-fpc/pic/port unit logical-unit-number] hierarchy level.
  2. Enable packet flow monitoring to monitor packet flows from another router on a monitoring services interface by specifying the family option as inet.
  3. Configure the receive-options-packets and the receive-ttl-exceeded statements for conformity with cflowd record structure.

For the monitoring services interface, you can configure multiservice physical interface properties. For more information, see Configuring Multiservice Physical Interface Properties and the Junos OS Services Interfaces Library for Routing Devices.

Removing MPLS Labels from Incoming Packets

The Junos OS can forward only IPv4 packets to a Monitoring Services PIC. IPv4 packets with MPLS labels cannot be forwarded to a Monitoring Services PIC. By default, if packets with MPLS labels are forwarded to the Monitoring Services PIC, they are discarded. To monitor packets with MPLS labels, you must remove the MPLS labels as the packets arrive on the interface. You can remove up to two MPLS labels from an incoming packet to a Monitoring Services PIC.

To remove MPLS labels from an incoming packet to a Monitoring Services PIC:

  1. In configuration mode, go to the [edit interfaces interface-name sonet-options mpls] hierarchy level.
  2. Configure the pop-all-labels statement to remove up to two MPLS labels from incoming IP packets. Note that on T Series routers, the pop-all-labels statement removes up to five MPLS labels from incoming IP packets.
  3. Configure the required-depth number statement to specify the number of MPLS labels an incoming packet must have for the pop-all-labels statement to take effect.

    The required depth can be 1, 2, or [ 1 2 ]. If you include the required-depth 1 statement, the pop-all-labels statement takes effect for incoming packets with one label only.

    If you include the required-depth 2 statement, the pop-all-labels statement takes effect for incoming packets with two labels only. If you include the required-depth [ 1 2 ] statement, the pop-all-labels statement takes effect for incoming packets with one or two labels.

    A required depth of [ 1 2 ] is equivalent to the default behavior of the pop-all-labels statement.

Note

When you remove MPLS labels from incoming packets, note the following:

  • By default, the pop-all-labels statement takes effect for incoming packets with one or two labels.

  • The pop-all-labels statement has no effect on IP packets with three or more MPLS labels.

  • When you enable MPLS label removal, you must configure all ports on a PIC with the same label popping mode and required depth.

  • You use the pop-all-labels statement to enable passive monitoring applications, not active monitoring.

  • You cannot apply MPLS filters or accounting to the MPLS labels because the labels are removed as soon as the packet arrives on the interface.