show passive-monitoring error
Syntax
Release Information
Command introduced before Junos OS Release 7.4.
Description
(M40e, M160, and M320 routers and T Series routers only) Display passive monitoring error statistics.
Options
* | all | mo-fpc/pic/port | — | Display error statistics for monitoring interfaces. Use a wildcard character, specify all interfaces, or provide a specific interface name. |
Required Privilege Level
view
List of Sample Output
show passive-monitoring error allOutput Fields
Table 1 lists the output fields for the show passive-monitoring error command. Output fields are listed in the approximate order in which they appear.
Table 1: show passive-monitoring error Output Fields
Field Name | Field Description |
|---|---|
Passive monitoring interface | Name of the passive monitoring interface. |
Local interface index | Index counter of the local interface. |
Interface state | State of the passive monitoring interface:
|
| Error information | |
Packets dropped (no memory) | Number of packets dropped because of memory shortage. |
Packets dropped (not IP) | Number of non-IP packets dropped. |
Packets dropped (not IPv4) | Number of packets dropped because they failed the IPv4 version check. |
Packets dropped (header too small) | Number of packets dropped because the packet length or IP header length was too small. |
Memory allocation failures | Number of flow record memory allocation failures. A small number reflects failures to replenish the free list. A large number indicates the monitoring station is almost out of memory space. |
Memory free failures | Number of flow record memory free failures. |
Memory free list failures | Number of flow records received from free list that failed. Memory is nearly exhausted or too many new flows greater than 128 KB are being created per second. |
Memory warning | Whether the flows have exceeded 1 million packets per second (Mpps) on a Monitoring Services PIC or 2 Mpps on a Monitoring Services II PIC. The response can be Yes or No. |
Memory overload | Whether the memory has been overloaded. The response can be Yes or No. |
PPS overload | Whether the PIC is receiving more packets per second than the configured threshold. The response can be Yes or No. |
BPS overload | Whether the PIC is receiving more bits per second than the configured threshold. The response can be Yes or No. |
Sample Output
show passive-monitoring error all
user@host> show passive-monitoring error all
Passive monitoring interface: mo-4/0/0, Local interface index: 44
Interface state: Monitoring
Error information
Packets dropped (no memory): 0, Packets dropped (not IP): 0
Packets dropped (not IPv4): 0, Packets dropped (header too small): 0
Memory allocation failures: 0, Memory free failures: 0
Memory free list failures: 0
Memory warning: No, Memory overload: No, PPS overload: No, BPS overload: No
Passive monitoring interface: mo-4/1/0, Local interface index: 45
Interface state: Not monitoring
Error information
Packets dropped (no memory): 0, Packets dropped (not IP): 0
Packets dropped (not IPv4): 0, Packets dropped (header too small): 0
Memory allocation failures: 0, Memory free failures: 0
Memory free list failures: 0
Memory warning: No, Memory overload: No, PPS overload: No, BPS overload: No
