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 device status
- Host Resources Device Status
- hrDeviceStatus 1.3.6.1.2.1.25.3.2.1.5 (defined in rfc1514)
The current operational state of the device described by this row of the table. A value unknown(1) indicates that the current state of the device is unknown. running(2) indicates that the device is up and running and that no unusual error conditions are known. The warning(3) state indicates that agent has been informed of an unusual error condition by the operational software (e.g., a disk device driver) but that the device is still 'operational'. An example would be high number of soft errors on a disk. A value of testing(4), indicates that the device is not available for use because it is in the testing state. The state of down(5) is used only when the agent has been informed that the device is not available for any use. - local Hw Device Operation Status
- localHwDeviceOperStatus 1.3.6.1.4.1.52.4.1.1.17.1.10.1.1.3 (defined in ct-hsimphys-mib)
This object describes the current state of the device. - local Hw Device Admin Status
- localHwDeviceAdminStatus 1.3.6.1.4.1.52.4.1.1.17.1.10.1.1.4 (defined in ct-hsimphys-mib)
This object is used by the Network Management System to request a change in the current state of the device. - Cisco Blocked Serial Tunneling Route BIP Device Status
- bstunRouteBIPDeviceStatus 1.3.6.1.4.1.9.9.35.1.4.1.1.18 (defined in CISCO-BSTUN-MIB)
If bstunRouteType is bip then this indicates the OR bit mask status of the mapped bisync device: if no bits are set, indicates that the bisync device is up and operational. Bit 0, if set, indicates that the bisync device is reporting an operation check error. Bit 2, if set, indicates that the bisync device is reporting a data check error. Bit 3, if set, indicates that the bisync device is reporting an equipment check error. Bit 4, if set, indicates that the bisync device is reporting that intervention is required. Bit 5, if set, indicates that the bisync device is reporting that a command has been rejected. Bit 6, if set, indicates that the bisync device is not responding to polls. Bit 7, if set, indicates that the bisync device is now responding to polls and is operational. Bit 9, if set, indicates that the bisync device is reporting that is no longer busy. Bit 10, if set, indicates that the bisync device is reporting a device unit specify. Bit 11, if set, indicates that the bisync device is reporting a busy condition. - Cisco Call Manager Media Device Status
- ccmMediaDeviceStatus 1.3.6.1.4.1.9.9.156.1.6.1.1.5 (defined in CISCO-CCM-MIB)
The status of the Media Device. The status changes from unknown to registered when it registers itself with the local CUCM. - Cisco Call Manager Media Device Status Reason
- ccmMediaDeviceStatusReason 1.3.6.1.4.1.9.9.156.1.6.1.1.9 (defined in CISCO-CCM-MIB)
The reason code associated with the media device status change. - Cisco Call Manager Media Device Time Last Status Update
- ccmMediaDeviceTimeLastStatusUpdt 1.3.6.1.4.1.9.9.156.1.6.1.1.10 (defined in CISCO-CCM-MIB)
The time the status of the media device changed. - Cisco Call Manager CTI Device Status
- ccmCTIDeviceStatus 1.3.6.1.4.1.9.9.156.1.8.1.1.5 (defined in CISCO-CCM-MIB)
The status of the CTI Device. The CTI Device status changes from unknown to registered when it registers itself with the local CUCM. - Cisco Call Manager CTI Device Status Reason
- ccmCTIDeviceStatusReason 1.3.6.1.4.1.9.9.156.1.8.1.1.10 (defined in CISCO-CCM-MIB)
The reason code associated with the CTI Device status change. - Cisco Call Manager CTI Device Time Last Status Update
- ccmCTIDeviceTimeLastStatusUpdt 1.3.6.1.4.1.9.9.156.1.8.1.1.11 (defined in CISCO-CCM-MIB)
The time the status of the CTI device changed.
