Help us improve your experience.

Let us know what you think.

Do you have time for a two-minute survey?

 
ON THIS PAGE
 

Inline Flow Monitoring for Virtual Chassis Overview

Inline flow monitoring enables you to monitor the flow of traffic by means of a router or switch participating in a network.

Inline flow monitoring for an MX Series Virtual Chassis or an EX9200 Virtual Chassis supports the following features:

  • Active sampling and exporting of both IPv4 and IPv6 traffic flows. Active (inline) sampling occurs on an inline data path without the need for a services DPC.

  • Sampling traffic flows in both the ingress and egress directions.

  • Configuring flow collection on either IPv4 or IPv6 devices.

  • Using the IPFIX flow collection template for traffic sampling. The IPFIX template supports both IPv4 and IPv6 export records.

  • Sampling and exporting of VPLS flows

  • Exporting of data in Version-IPFIX and Version 9 formats

Consider the following guidelines when you configure Virtual Chassis for inline flow monitoring.

Syntax of the sampling-instance Statement

To associate a sampling instance with an FPC in the Virtual Chassis primary router (member ID 0), use the sampling-instance instance-name statement at the [edit chassis member member-number fpc slot slot-number] hierarchy level, where member-number is 0 (zero) and slot-number is a number in the range 0 through 11. For example, the following statement associates a sampling instance named sample1 to the FPC in slot 1 of a Virtual Chassis primary router:

To associate a sampling instance with an FPC in the Virtual Chassis backup router (member ID 1), use the sampling-instance instance-name statement at the [edit chassis member member-number fpc slot slot-number] hierarchy level, where member-number is 1 and slot-number is a number in the range 0 through 11. For example, the following statement associates a sampling instance named sample2 to the FPC in slot 2 of Virtual Chassis backup router:

FPC Slot Numbers for the Virtual Chassis

After you configure the member ID and, optionally, slot count for each router that you want to add to the Virtual Chassis, the Routing Engines in that chassis reboot and the slots for line cards (FPCs) are renumbered. The FPC slot numbering used for each member router is based on the slot count and offsets used in the Virtual Chassis instead of the physical slot numbers where the line card is actually installed.

For example, assume that in your Virtual Chassis configuration, member 0 is an MX960 router and member 1 is an MX2010 router, with the default slot count (12) in effect on both routers. In this topology, a 10-Gigabit Ethernet interface that appears as xe-14/2/2 (FPC slot 14, PIC slot 2, port 2) in the show services accounting status inline-jflow command output or the show interfaces command output is actually physical interface xe-2/2/2 (FPC slot 2, PIC slot 2, port 2) on member 1 after deducting the offset of 12 for member 1.

Note:

Platform support and associated slots depend on the Junos OS release in your installation.

For more information about how slot count and slot numbering work in an MX Series Virtual Chassis, see Virtual Chassis Components Overview.

Related Documentation