Supported Platforms
Measuring Health
You can monitor health metrics reactively by using fault management software such as SMARTS InCharge, Micromuse Netcool Omnibus, or Concord Live Exceptions. We recommend that you monitor the health metrics shown in Table 1.
Table 1: Health Metrics
| Metric: | Errors in |
Description | Number of inbound packets that contained errors, preventing them from being delivered |
MIB name | IF-MIB (RFC 2233) |
Variable name | ifInErrors |
Variable OID | .1.3.6.1.31.2.2.1.14 |
Frequency (mins) | 60 |
Allowable range | To be baselined |
Managed objects | Logical interfaces |
| Metric: | Errors out |
Description | Number of outbound packets that contained errors, preventing them from being transmitted |
MIB name | IF-MIB (RFC 2233) |
Variable name | ifOutErrors |
Variable OID | .1.3.6.1.31.2.2.1.20 |
Frequency (mins) | 60 |
Allowable range | To be baselined |
Managed objects | Logical interfaces |
| Metric: | Discards in |
Description | Number of inbound packets discarded, even though no errors were detected |
MIB name | IF-MIB (RFC 2233) |
Variable name | ifInDiscards |
Variable OID | .1.3.6.1.31.2.2.1.13 |
Frequency (mins) | 60 |
Allowable range | To be baselined |
Managed objects | Logical interfaces |
| Metric: | Unknown protocols |
Description | Number of inbound packets discarded because they were of an unknown protocol |
MIB name | IF-MIB (RFC 2233) |
Variable name | ifInUnknownProtos |
Variable OID | .1.3.6.1.31.2.2.1.15 |
Frequency (mins) | 60 |
Allowable range | To be baselined |
Managed objects | Logical interfaces |
| Metric: | Interface operating status |
Description | Operational status of an interface |
MIB name | IF-MIB (RFC 2233) |
Variable name | ifOperStatus |
Variable OID | .1.3.6.1.31.2.2.1.8 |
Frequency (mins) | 15 |
Allowable range | 1 (up) |
Managed objects | Logical interfaces |
| Metric: | Label Switched Path (LSP) state |
Description | Operational state of an MPLS label-switched path |
MIB name | MPLS-MIB |
Variable name | mplsLspState |
Variable OID | mplsLspEntry.2 |
Frequency (mins) | 60 |
Allowable range | 2 (up) |
Managed objects | All label-switched paths in the network |
| Metric: | Component operating status |
Description | Operational status of a router hardware component |
MIB name | JUNIPER-MIB |
Variable name | jnxOperatingState |
Variable OID | .1.3.6.1.4.1.2636.1.13.1.6 |
Frequency (mins) | 60 |
Allowable range | 2 (running) or 3 (ready) |
Managed objects | All components in each Juniper Networks router |
| Metric: | Component operating temperature |
Description | Operational temperature of a hardware component, in Celsius |
MIB name | JUNIPER-MIB |
Variable name | jnxOperatingTemp |
Variable OID | .1.3.6.1.4.1.2636.1.13.1.7 |
Frequency (mins) | 60 |
Allowable range | To be baselined |
Managed objects | All components in a chassis |
| Metric: | System up time |
Description | Time, in milliseconds, that the system has been operational. |
MIB name | MIB-2 (RFC 1213) |
Variable name | sysUpTime |
Variable OID | .1.3.6.1.1.3 |
Frequency (mins) | 60 |
Allowable range | Increasing only (decrement indicates a restart) |
Managed objects | All routers |
| Metric: | No IP route errors |
Description | Number of packets that could not be delivered because there was no IP route to their destination. |
MIB name | MIB-2 (RFC 1213) |
Variable name | ipOutNoRoutes |
Variable OID | ip.12 |
Frequency (mins) | 60 |
Allowable range | To be baselined |
Managed objects | Each router |
| Metric: | Wrong SNMP community names |
Description | Number of incorrect SNMP community names received |
MIB name | MIB-2 (RFC 1213) |
Variable name | snmpInBadCommunityNames |
Variable OID | snmp.4 |
Frequency (hours) | 24 |
Allowable range | To be baselined |
Managed objects | Each router |
| Metric: | SNMP community violations |
Description | Number of valid SNMP communities used to attempt invalid operations (for example, attempting to perform SNMP Set requests) |
MIB name | MIB-2 (RFC 1213) |
Variable name | snmpInBadCommunityUses |
Variable OID | snmp.5 |
Frequency (hours) | 24 |
Allowable range | To be baselined |
Managed objects | Each router |
| Metric: | Redundancy switchover |
Description | Total number of redundancy switchovers reported by this entity |
MIB name | JUNIPER-MIB |
Variable name | jnxRedundancySwitchoverCount |
Variable OID | jnxRedundancyEntry.8 |
Frequency (mins) | 60 |
Allowable range | To be baselined |
Managed objects | All Juniper Networks routers with redundant Routing Engines |
| Metric: | FRU state |
Description | Operational status of each field-replaceable unit (FRU) |
MIB name | JUNIPER-MIB |
Variable name | jnxFruState |
Variable OID | jnxFruEntry.8 |
Frequency (mins) | 15 |
Allowable range | 2 through 6 for ready/online states. See jnxFruOfflineReason in the event of a FRU failure. |
Managed objects | All FRUs in all Juniper Networks routers. |
| Metric: | Rate of tail-dropped packets |
Description | Rate of tail-dropped packets per output queue, per forwarding class, per interface. |
MIB name | JUNIPER-COS-MIB |
Variable name | jnxCosIfqTailDropPktRate |
Variable OID | jnxCosIfqStatsEntry.12 |
Frequency (mins) | 60 |
Allowable range | To be baselined |
Managed objects | For each forwarding class per interface in the provider network, when CoS is enabled. |
| Metric: | Interface utilization: octets received |
Description | Total number of octets received on the interface, including framing characters. |
MIB name | IF-MIB |
Variable name | ifInOctets |
Variable OID | .1.3.6.1.2.1.2.2.1.10.x |
Frequency (mins) | 60 |
Allowable range | To be baselined |
Managed objects | All operational interfaces in the network |
| Metric: | Interface utilization: octets transmitted |
Description | Total number of octets transmitted out of the interface, including framing characters. |
MIB name | IF-MIB |
Variable name | ifOutOctets |
Variable OID | .1.3.6.1.2.1.2.2.1.16.x |
Frequency (mins) | 60 |
Allowable range | To be baselined |
Managed objects | All operational interfaces in the network |
 | Note: Byte counts vary depending on interface type, encapsulation used and PIC supported. For example, with vlan-ccc encapsulation on a 4xFE, GE, or GE 1Q PIC, the byte count includes framing and control word overhead. (See Table 2.) |
Table 2: Counter Values for vlan-ccc Encapsulation
PIC Type | Encapsulation | input (Unit Level) | Output (Unit Level) | SNMP |
|---|---|---|---|---|
4xFE | vlan-ccc | Frame (no frame check sequence [FCS]) | Frame (including FCS and control word) | ifInOctets, ifOutOctets |
GE | vlan-ccc | Frame (no FCS) | Frame (including FCS and control word) | ifInOctets, ifOutOctets |
GE IQ | vlan-ccc | Frame (no FCS) | Frame (including FCS and control word) | ifInOctets, ifOutOctets |
SNMP traps are also a good mechanism to use for health management. For more information, see “Standard SNMP Traps Supported on Devices Running Junos OS” and “Juniper Networks Enterprise-Specific SNMP Traps” in the SNMP MIBs and Traps Reference.
