OIDs - Current Status monitor
The objects described here can be monitored with the IPHost Network Monitor.
You can start SNMP monitoring using free 30-day trial version of IPHost right now.
OID list for current status
- access Switch System Current Status
- accessSwitchSystemCurrentStatus 1.3.6.1.4.1.890.1.5.1.1.1 (defined in ZYXEL-accessSwitch-MIB)
The sysCurrentStatus is a bit map represented as a sum, therefore, it can represent multiple defects simultaneously. The sysNoDefect should be set if and only if no other flag is set. The various bit positions are: 1 sysNoDefect 2 sysOverHeat 3 sysFanRpmLow 4 sysVoltageLow 5 sysThermalSensorFailure - snmp Fddi MAC Current Frame Status
- snmpFddiMACCurrentFrameStatus 1.3.6.1.2.1.10.15.2.2.1.19 (defined in rfc1285)
A value that indicates the MAC's operational frame status setting functionality. The value is a sum. This value initially takes the value zero, then for each functionality present, 2 raised to a power is added to the sum. The powers are according to the following table: Functionality Power FSC-Type0 0 -- MAC repeats A/C indicators as received FSC-Type1 1 -- MAC sets C but not A on copying for -- forwarding FSC-Type2 2 -- MAC resets C and sets A on C set and A -- reset if frame is not copied REFERENCE ANSI { fddiMAC 63 } - sonet Section Current Status
- sonetSectionCurrentStatus 1.3.6.1.2.1.10.39.1.2.1.1.1 (defined in rfc1595)
This variable indicates the status of the interface. The sonetSectionCurrentStatus is a bit map represented as a sum, therefore, it can represent multiple defects simultaneously. The sonetSectionNoDefect should be set if and only if no other flag is set. The various bit positions are: 1 sonetSectionNoDefect 2 sonetSectionLOS 4 sonetSectionLOF - sonet Line Current Status
- sonetLineCurrentStatus 1.3.6.1.2.1.10.39.1.3.1.1.1 (defined in rfc1595)
This variable indicates the status of the interface. The sonetLineCurrentStatus is a bit map represented as a sum, therefore, it can represent multiple defects simultaneously. The sonetLineNoDefect should be set if and only if no other flag is set. The various bit positions are: 1 sonetLineNoDefect 2 sonetLineAIS 4 sonetLineRDI - sonet Path Current Status
- sonetPathCurrentStatus 1.3.6.1.2.1.10.39.2.1.1.1.2 (defined in rfc1595)
This variable indicates the status of the interface. The sonetPathCurrentStatus is a bit map represented as a sum, therefore, it can represent multiple defects simultaneously. The sonetPathNoDefect should be set if and only if no other flag is set. The various bit positions are: 1 sonetPathNoDefect 2 sonetPathSTSLOP 4 sonetPathSTSAIS 8 sonetPathSTSRDI 16 sonetPathUnequipped 32 sonetPathSignalLabelMismatch - sonet VT Current Status
- sonetVTCurrentStatus 1.3.6.1.2.1.10.39.3.1.1.1.2 (defined in rfc1595)
This variable indicates the status of the interface. The sonetVTCurrentStatus is a bit map represented as a sum, therefore, it can represent multiple defects and failures simultaneously. The sonetVTNoDefect should be set if and only if no other flag is set. The various bit positions are: 1 sonetVTNoDefect 2 sonetVTLOP 4 sonetVTPathAIS 8 sonetVTPathRDI 16 sonetVTPathRFI 32 sonetVTUnequipped 64 sonetVTSignalLabelMismatch - Cisco Aps Status Current
- cApsStatusCurrent 1.3.6.1.4.1.9.10.71.1.2.1.3 (defined in CISCO-APS-MIB)
The current status of the APS group. modeMismatch Modes other than 1+1 unidirectional monitor protection line K2 bit 5, which indicates the architecture and K2 bits 6-8, which indicate if the mode is unidirectional or bidirectional. A conflict between the current local mode and the received K2 mode information constitutes a mode mismatch. channelMismatch This bit indicates a mismatch between the transmitted K1 channel and the received K2 channel has been detected. psbf This bit indicates a Protection Switch Byte Failure (PSBF) is in effect. This condition occurs when either an inconsistent APS byte or an invalid code is detected. An inconsistent APS byte occurs when no three consecutive K1 bytes of the last 12 successive frames are identical, starting with the last frame containing a previously consistent byte. An invalid code occurs when the incoming K1 byte contains an unused code or a code irrelevant for the specific switching operation (e.g., Reverse Request while no switching request is outstanding) in three consecutive frames. An invalid code also occurs when the incoming K1 byte contains an invalid channel number in three consecutive frames. feplf Modes other than 1+1 unidirectional monitor the K1 byte for Far-End Protection-Line failures. A Far-End Protection-Line defect is declared based on receiving SF on the protection line. extraTraffic This bit indicates whether extra traffic is currently being accepted on the protection line. - Cisco Diameter Base Protocol Peer Statistics DW Current Status
- cdbpPeerStatsDWCurrentStatus 1.3.6.1.4.1.9.10.133.1.4.1.1.5 (defined in CISCO-DIAMETER-BASE-PROTOCOL-MIB)
This object indicates the connection status. okay(1) - Indicates the connection is presumed working. suspect(2) - Indicates the connection is possibly congested or down. down(3) - The peer is no longer reachable, causing the transport connection to be shutdown. reopen(4) - Three watchdog messages are exchanged with accepted round trip times, and the connection to the peer is considered stabilized.