The Monitoring Services I and Monitoring Services II PICs are designed to enable IP services. If you have a Monitoring Services PIC and an ATM PIC installed in an M160, M40e, or T-series routing platform, you can monitor IP version 4 (IPv4) traffic from another routing platform.
On ATM interfaces, you enable packet flow monitoring by including the passive-monitor-mode statement at the [edit interfaces at-fpc/pic/port] hierarchy level:
- [edit interfaces at-fpc/pic/port]
If you include the passive-monitor-mode statement in the configuration, the ATM interface is always up, and the interface does not receive or transmit incoming control packets, such as OAM cell and ILMI.
On monitoring services interfaces, you enable packet flow monitoring by including the family statement at the [edit interfaces mo-fpc/pic/port unit logical-unit-number] hierarchy level, specifying the inet option:
- [edit interfaces mo-fpc/pic/port unit logical-unit-number]
- family inet;
For conformity with cflowd record structure, you must include the receive-options-packets and receive-ttl-exceeded statements at the [edit interfaces mo-fpc/pic/port unit logical-unit-number family inet] hierarchy level:
- [edit interfaces mo-fpc/pic/port unit logical-unit-number family inet]
For the monitoring services interface, you can configure multiservice physical interface properties. For more information, see Configuring Multiservice Physical Interface Properties and the JUNOS Services Interfaces Configuration Guide.