To perform passive flow monitoring, your system
must meet these minimum requirements:
JUNOS Release 8.5 or later for passive flow monitoring
support on the MX-series MultiServices routers.
JUNOS Release 8.4 or later for passive flow monitoring
support on the MultiServices 400 PIC (Type 2).
JUNOS Release 7.6 or later to clear error and flow statistics
with the clear passive-monitoring statistics command
JUNOS Release 7.5 or later for support of the dynamic
flow capture (DFC) Management Information Base (MIB)
JUNOS Release 7.4 or later for dynamic flow capture on
Monitoring Services III PICs installed in T-series and M320 routing
platforms, and port mirroring of IPv6 packets
JUNOS Release 7.3 or later for passive flow monitoring
on selected Ethernet-based interfaces and filter-based forwarding
on output interfaces
JUNOS Release 7.1 or later for passive flow monitoring
and flow collection services on Monitoring Services II PICs installed
in T-series and M320 routing platforms
JUNOS Release 6.4 or later for support of the next-hop
IP address field in flow monitoring version 5 records
JUNOS Release 6.2 or later for ATM2 intelligent queuing
(IQ) interface passive monitoring, flow collection services, and MPLS
label stripping
JUNOS Release 6.1 or later for MPLS passive monitoring
JUNOS Release 6.0 or later for the Monitoring Services
II PIC
JUNOS Release 5.7 or later for the automatic insertion
of autonomous system (AS) numbers and SNMP index values for interfaces
into flow records
JUNOS Release 5.4 or later for the Monitoring Services
PIC
M40e, M160, M320, MX-series, or T-series routing platform
with an Internet Processor II ASIC or later
Type 1 enhanced FPCs
Two optical splitters
A Tunnel Services PIC (required if you wish to send traffic
to more than one analyzer)
An input interface from the following list:
SONET/SDH PIC—OC3, OC12, or OC48
ATM2 IQ PIC—OC3 or OC12
4-port Fast Ethernet PIC
Gigabit Ethernet PIC—4-port with small form-factor
pluggable transceiver (SFP) or 10-port with SFP
1-port 10-Gigabit Ethernet PIC with XENPAK
Outgoing PICs to connect to the flow collector or packet
analyzer
Flow monitoring version 5 collector
ES PIC and packet analyzers (optional)
Active Flow Monitoring
To implement active flow monitoring, your system
must meet these minimum requirements:
JUNOS Release 9.0 or later for version 9 flow aggregation
to multiple flow servers.
JUNOS Release 8.5 or later for active flow monitoring
support on MultiServices 500 PICs.
JUNOS Release 8.3 or later for flow monitoring version
9 support, MPLS support, and active flow monitoring support on MultiServices
100 and 400 PICs.
JUNOS Release 8.2 or later for M120 router support and
for flow monitoring version 5 and 8 support on MultiServices 100 and
400 PICs.
JUNOS Release 8.1 or later for the flow-tap services application
on Adaptive Services II PICs installed in M7i, M10i, M20, M40e, M320,
and T-series routing platforms
JUNOS Release 7.4 or later for port mirroring of IPv6
packets
JUNOS Release 7.3 or later for active flow monitoring
on Adaptive Services II PICs installed in TX Matrix platforms
JUNOS Release 7.0 or later for active flow monitoring
on Adaptive Services II PICs installed in T-series and M320 routing
platforms
JUNOS Release 7.0 or later for active flow monitoring
on J-series Services Routers
JUNOS Release 6.0 or later for the Adaptive Services PIC
JUNOS Release 5.7 or later for the automatic insertion
of AS numbers and SNMP index values for input and output interfaces
into records, port mirroring to multiple ports, and discard accounting
JUNOS Release 5.6 or later for the Monitoring Services
PIC
M5, M7i, M10, M10i, M20, M40e, M120, M160, M320, or T-series
routing platform with an Internet Processor II ASIC or later; or a
J-series Services Router
Type 1 enhanced FPCs
Two M-series or T-series PICs or J-series Physical Interface
Modules (PIMs) of your choice: One to receive incoming traffic and
one to forward outgoing traffic (the second PIC or PIM is not necessary
for discard accounting)
Export PICs to connect to the collector or packet analyzer
Tunnel Services PIC (required for multiple port mirroring
or mo- interface load balancing)
Flow collector version 5, 8, or 9
ES PIC and packet analyzers (optional)
Active Flow Monitoring
For Monitoring Services PIC specifications, see Table 21 and Table 22.
For Adaptive Services PIC specifications, see Table 23. For MultiServices PIC specifications, see Table 24 and Table 25.
Table 21: Monitoring
Services PIC Specifications
Specification
Description
Physical dimensions
Single-wide PIC that occupies one PIC slot
Connectors
DB-9 diagnostic serial console port
Status LED
One tricolor:
Off—The PIC is offline; it is safe to remove it
from the chassis.
Green—The PIC is operating normally.
Amber—The PIC is initializing.
Red—The PIC has an error or failure; no further
harm can be done by removing it from the chassis.
Application LED
One tricolor:
Off—The service is not running.
Green—The service is running under acceptable load.
Amber—The service is overloaded.
Table 22: Monitoring
Services II PIC Specifications
Specification
Description
Physical dimensions
Single-wide PIC that occupies one PIC slot
Connectors
N/A
Status LED
One tricolor:
Off—The PIC is offline; it is safe to remove it
from the chassis.
Green—The PIC is operating normally.
Amber—The PIC is initializing.
Red—The PIC has an error or failure; no further
harm can be done by removing it from the chassis.
Application LED
One tricolor:
Off—The flow collector is not running.
Green—The flow collector is running under acceptable
load.
Amber—The flow collector is overloaded.
Table 23: Adaptive
Services PIC Specifications
Specification
Description
Physical dimensions
Single-wide PIC that occupies one PIC slot
Connectors
N/A
Status LED
One tricolor:
Off—The PIC is offline; it is safe to remove it
from the chassis.
Green—The PIC is operating normally.
Amber—The PIC is initializing.
Red—The PIC has an error or failure; no further
harm can be done by removing it from the chassis.
Application LED
One tricolor:
Off—The flow collector is not running.
Green—The flow collector is running under acceptable
load.
Amber—The flow collector is overloaded.
Table 24: MultiServices
100 PIC
Specification
Description
Physical dimensions
Single-wide PIC that occupies one PIC slot
Connectors
N/A
Status LED
One tricolor:
Off—The PIC is offline; it is safe to remove it
from the chassis.
Green—The PIC is operating normally.
Amber—The PIC is initializing.
Red—The PIC has an error or failure; no further
harm can be done by removing it from the chassis.
Application LED
One tricolor:
Off—The service is not running.
Green—The service is running under acceptable load.
Amber—The service is overloaded.
Table 25: MultiServices
400 PIC
Specification
Description
Physical dimensions
Single-wide PIC that occupies one PIC slot
Connectors
N/A
Status LED
One tricolor:
Off—The PIC is offline; it is safe to remove it
from the chassis.
Green—The PIC is operating normally.
Amber—The PIC is initializing.
Red—The PIC has an error or failure; no further
harm can be done by removing it from the chassis.
Application LED
One tricolor:
Off—The service is not running.
Green—The service is running under acceptable load.
Amber—The service is overloaded.
Table 26: MultiServices 500 PIC
Specification
Description
Physical dimensions
Single-wide PIC that occupies one PIC slot
Connectors
N/A
Status LED
One tricolor:
Off—The PIC is offline; it is safe to remove it
from the chassis.
Green—The PIC is operating normally.
Amber—The PIC is initializing.
Red—The PIC has an error or failure; no further
harm can be done by removing it from the chassis.
Application LED
One tricolor:
Off—The service is not running.
Green—The service is running under acceptable load.
