This chapter describes the vendor-specific Management Information Base (MIB) text documents that Cisco Unified Communications Manager (Cisco Unified CM) supports and that are used with Simple Network Management Protocol (SNMP).
The MIBs described in this chapter exist on various Cisco Media Convergence Servers (MCS), depending on vendor and model number. To query these MIBS, you can use the standard MIB browsers provided by the vendor. Go to the following URLs:
1 Supported, but note that Cisco Unified Communications Manager 6.1 and higher requires memory of minimum 2GB for MCS 7815/16/25/35, and 4GB for MCS 7845, and hard drive capacity of 72/80 GB or higher.This will result in mandatory memory and hard drive upgrades, if older supported servers are desired for use with the new software versions.
2 Supported, but note that Cisco Unified Communications Manager 6.1 and higher requires memory of minimum 2GB for MCS 7815/16/25/35, and 4GB for MCS 7845, and hard drive capacity of 72/80 GB or higher.This will result in mandatory memory and hard drive upgrades, if older supported servers are desired for use with the new software versions.
3 Supported, but note that Cisco Unified Communications Manager 6.1 and higher requires memory of minimum 2GB for MCS 7815/16/25/35, and 4GB for MCS 7845, and hard drive capacity of 72/80 GB or higher.This will result in mandatory memory and hard drive upgrades, if older supported servers are desired for use with the new software versions.
4 Supported, but note that Cisco Unified Communications Manager 6.1 and higher requires memory of minimum 2GB for MCS 7815/16/25/35, and 4GB for MCS 7845, and hard drive capacity of 72/80 GB or higher.This will result in mandatory memory and hard drive upgrades, if older supported servers are desired for use with the new software versions.
5 Supported, but note that Cisco Unified Communications Manager 6.1 and higher requires memory of minimum 2GB for MCS 7815/16/25/35, and 4GB for MCS 7845, and hard drive capacity of 72/80 GB or higher.This will result in mandatory memory and hard drive upgrades, if older supported servers are desired for use with the new software versions.
6 Supported, but note that Cisco Unified Communications Manager 6.1 and higher requires memory of minimum 2GB for MCS 7815/16/25/35, and 4GB for MCS 7845, and hard drive capacity of 72/80 GB or higher.This will result in mandatory memory and hard drive upgrades, if older supported servers are desired for use with the new software versions.
7 Supported, but note that Cisco Unified Communications Manager 6.1 and higher requires memory of minimum 2GB for MCS 7815/16/25/35, and 4GB for MCS 7845, and hard drive capacity of 72/80 GB or higher.This will result in mandatory memory and hard drive upgrades, if older supported servers are desired for use with the new software versions.
8 Supported, but note that Cisco Unified Communications Manager 6.1 and higher requires memory of minimum 2GB for MCS 7815/16/25/35, and 4GB for MCS 7845, and hard drive capacity of 72/80 GB or higher.This will result in mandatory memory and hard drive upgrades, if older supported servers are desired for use with the new software versions.
9 Supported, but note that Cisco Unified Communications Manager 6.1 and higher requires memory of minimum 2GB for MCS 7815/16/25/35, and 4GB for MCS 7845, and hard drive capacity of 72/80 GB or higher.This will result in mandatory memory and hard drive upgrades, if older supported servers are desired for use with the new software versions.
10 Supported, but note that Cisco Unified Communications Manager 6.1 and higher requires memory of minimum 2GB for MCS 7815/16/25/35, and 4GB for MCS 7845, and hard drive capacity of 72/80 GB or higher.This will result in mandatory memory and hard drive upgrades, if older supported servers are desired for use with the new software versions.
11 Supported, but note that Cisco Unified Communications Manager 6.1 and higher requires memory of minimum 2GB for MCS 7815/16/25/35, and 4GB for MCS 7845, and hard drive capacity of 72/80 GB or higher.This will result in mandatory memory and hard drive upgrades, if older supported servers are desired for use with the new software versions.
12 Supported, but note that Cisco Unified Communications Manager 6.1 and higher requires memory of minimum 2GB for MCS 7815/16/25/35, and 4GB for MCS 7845, and hard drive capacity of 72/80 GB or higher.This will result in mandatory memory and hard drive upgrades, if older supported servers are desired for use with the new software versions.
13 Supported, but note that Cisco Unified Communications Manager 6.1 and higher requires memory of minimum 2GB for MCS 7815/16/25/35, and 4GB for MCS 7845, and hard drive capacity of 72/80 GB or higher.This will result in mandatory memory and hard drive upgrades, if older supported servers are desired for use with the new software versions.
14 Supported, but note that Cisco Unified Communications Manager 6.1 and higher requires memory of minimum 2GB for MCS 7815/16/25/35, and 4GB for MCS 7845, and hard drive capacity of 72/80 GB or higher.This will result in mandatory memory and hard drive upgrades, if older supported servers are desired for use with the new software versions.
15 Supported, but note that Cisco Unified Communications Manager 6.1 and higher requires memory of minimum 2GB for MCS 7815/16/25/35, and 4GB for MCS 7845, and hard drive capacity of 72/80 GB or higher.This will result in mandatory memory and hard drive upgrades, if older supported servers are desired for use with the new software versions.
16 Supported, but note that Cisco Unified Communications Manager 6.1 and higher requires memory of minimum 2GB for MCS 7815/16/25/35, and 4GB for MCS 7845, and hard drive capacity of 72/80 GB or higher.This will result in mandatory memory and hard drive upgrades, if older supported servers are desired for use with the new software versions.
17 Supported, but note that Cisco Unified Communications Manager 6.1 and higher requires memory of minimum 2GB for MCS 7815/16/25/35, and 4GB for MCS 7845, and hard drive capacity of 72/80 GB or higher.This will result in mandatory memory and hard drive upgrades, if older supported servers are desired for use with the new software versions.
18 Supported, but note that Cisco Unified Communications Manager 6.1 and higher requires memory of minimum 2GB for MCS 7815/16/25/35, and 4GB for MCS 7845, and hard drive capacity of 72/80 GB or higher.This will result in mandatory memory and hard drive upgrades, if older supported servers are desired for use with the new software versions.
19 Supported, but note that servers running Cisco Unified Communications Manager (CallManager) 4.0 and later require a minimum of 2 GB of memory for Cisco MCS 7815, MCS 7816, MCS 7825, and MCS 7835 and 4 GB of memory for Cisco MCS 7845.
20 Supported, but note that Cisco Unified Communications Manager 6.1 and higher requires memory of minimum 2GB for MCS 7815/16/25/35, and 4GB for MCS 7845, and hard drive capacity of 72/80 GB or higher.This will result in mandatory memory and hard drive upgrades, if older supported servers are desired for use with the new software versions.
21 Supported, but note that Cisco Unified Communications Manager 6.1 and higher requires memory of minimum 2GB for MCS 7815/16/25/35, and 4GB for MCS 7845, and hard drive capacity of 72/80 GB or higher.This will result in mandatory memory and hard drive upgrades, if older supported servers are desired for use with the new software versions.
22 Supported, but note that servers running Cisco Unified Communications Manager (CallManager) 4.0 and later require a minimum of 2 GB of memory for Cisco MCS 7815, MCS 7816, MCS 7825, and MCS 7835 and 4 GB of memory for Cisco MCS 7845.
Table 11 IBM hardware status messages, MIBs and objects names, and object responses
Cisco Unified CM Release 6.x
MCS-78xx Status
MIBS and Object Names
Object Responses
System Fan
IBM-SYSTEM-LMSENSOR-MIB::ibmSystem TachometerStatus (also see ibmSystemTachometerKeyIndex)
This is a string indicating the current status of the object. Various operational and non-operational statuses can be defined.
Operational statuses are OK, Degraded and Pred Fail. Pred Fail indicates that an element may be functioning properly but predicting a failure in the near future. An example is a SMART-enabled hard drive.
Non-operational statuses are Error, Starting, Stopping and Service. Service can apply during mirror-resilvering of a disk, reload of a user permissions list, or other administrative work.
Not all such work is on-line, yet the managed element is neither OK nor in one of the other states.
OK = Normal; Error = Critical
Voltage Sensor
IBM-SYSTEM-LMSENSOR-MIB::ibmSystem VoltageSensorStatus (also see ibmSystemVoltageSensorKeyIndex)
This is a string indicating the current status of the object. Various operational and non-operational statuses can be defined.
Operational statuses are OK, Degraded and Pred Fail. Pred Fail indicates that an element may be functioning properly but predicting a failure in the near future. An example is a SMART-enabled hard drive.
Non-operational statuses are Error, Starting, Stopping and Service. Service can apply during mirror-resilvering of a disk, reload of a user permissions list, or other administrative work. Not all such work is on-line, yet the managed element is neither OK nor in one of the other states.
OK = Normal; Error = Critical
Thermal
IBM-SYSTEM-LMSENSOR-MIB::ibmSystem TemperatureSensorStatus (also see ibmSystemTemperatureSensorKeyIndex)
The Status property is a string indicating the current status of the object. Various operational and non-operational statuses can be defined. Operational statuses are OK, Degraded and Pred Fail. Pred Fail indicates that an element may be functioning properly but predicting a failure in the near future. An example is a SMART-enabled hard drive. Non-operational statuses can also be specified. These are Error, Starting, Stopping and Service. The latter, Service, could apply during mirror-resilvering of a disk, reload of a user permissions list, or other administrative work. Not all such work is on-line, yet the managed element is neither OK nor in one of the other states. OK = Normal; Error = Critical
Network Interface Card
IBM-SYSTEM-NETWORK-MIB::ibmSystem LogicalNetworkAdapterStatus (also see ibmSystemLogicalNetworkAdapterKeyIndex)
The online status of the adapter.
Logical Drive
IBM-SYSTEM-TRAP-MIB::ibmSystem RaidLogicalDriveStatus (also see ibmSystemRaidLogicalDriveKeyIndex)
The status of the logical drive
Physical Drive
IBM-SYSTEM-TRAP-MIB::ibmSystem RaidDiskDriveStatus & ibmSystemRaidControllerStatus (also see ibmSystemRaidDiskDriveKeyIndex & ibmSystemRaidControllerKeyIndex)
The logical drive can be in one of the following states:
Ok (2) Indicates that the logical drive is in normal operation mode.
Failed (3) Indicates that more physical drives have failed than the fault tolerance mode of the logical drive can handle without data loss.
Unconfigured (4) Indicates that the logical drive is not configured.
Recovering (5) Indicates that the logical drive is using Interim Recovery Mode. In Interim Recovery Mode, at least one physical drive has failed, but the logical drive's fault tolerance mode lets the drive continue to operate with no data loss.
Ready Rebuild (6) Indicates that the logical drive is ready for Automatic Data Recovery. The physical drive that failed has been replaced, but the logical drive is still operating in Interim Recovery Mode.
Rebuilding (7) Indicates that the logical drive is currently doing Automatic Data Recovery. During Automatic Data Recovery, fault tolerance algorithms restore data to the replacement drive.
Wrong Drive (8) Indicates that the wrong physical drive was replaced after a physical drive failure.
Bad Connect (9) Indicates that a physical drive is not responding.
Physical Drive1
CPQIDA-MIB1.3.6.1.4.1.232.3.2.5.1.1.6
cpqDaPhyDrv Status
Clearing Value = 2
The following values are valid for the physical drive status:
other (1) Indicates that the instrument agent does not recognize the drive. You may need to upgrade your instrument agent and/or driver software.
ok (2) Indicates the drive is functioning properly.
failed (3) Indicates that the drive is no longer operating and should be replaced.
predictiveFailure(4) Indicates that the drive has a predictive failure error and should be replaced.
System Fan
CPQHLTH-MIB1.3.6.1.4.1.232.6.2.6.4
cpqHeThermalSystemFan Status
Clearing Value = 2
This value will be one of the following:
other(1) Fan status detection is not supported by this system or driver.
ok(2) The fan is operating properly.
degraded(2) A redundant fan is not operating properly.
failed(4) A non-redundant fan is not operating properly.
CPU Fan
CPQHLTH-MIB1.3.6.1.4.1.232.6.2.6.5
cpqHeThermalCpuFan Status
Clearing Value = 2
This value will be one of the following:
other(1) Fan status detection is not supported by this system or driver.
ok(2) The fan is operating properly.
degraded(2) A redundant fan is not operating properly.
failed(4) A non-redundant fan is not operating properly.
Network Interface Card (NIC)
CPQNIC-MIB1.3.6.1.4.1.232.18.2.3.1.1.13
cpqNicIfPhysAdapterState
Clearing Value = 2 and 3
The following values are valid—
unknown(1) The instrument agent was not able to determine the status of the adapter. The instrument agent may need to be upgraded.
ok(2) The physical adapter is operating properly.
generalFailure(3) The physical adapter has failed.
linkFailure(4) The physical adapter has lost link. Check the cable connections to this adapter.
Thermal
CPQHLTH-MIB1.3.6.1.4.1.232.6.2.6.1
cpqHeThermalCondition
Clearing Value = 2
This value will be one of the following:
other(1) Temperature could not be determined.
ok(2) The temperature sensor is within normal operating range.
degraded(3) The temperature sensor is outside of normal operating range.
failed(4) The temperature sensor detects a condition that could permanently damage the system.
Note
The system automatically shuts down if the failed (4) condition occurs, so it is unlikely that 4 will ever be returned by the agent. If the cpqHeThermalDegradedAction is set to shut down (3), the system will shut down if the condition occurs.
Power Supply1
CPQHLTH-MIB1.3.6.1.4.1.232.6.2.9.3.1.5
cpqHeFltTolPowerSupply Status
Clearing Value = 1
This value will be one of the following:
other(1) The status could not be determined or not present.
ok(2) The power supply is operating normally.
degraded(3) A temperature sensor, fan or other power supply component is outside of normal operating range.
failed(4) A power supply component detects a condition that could permanently damage the system.
NIC Errors
CPQNIC-MIB1.3.6.1.4.1.232.18.2.3.1.1.16
cpqNicIfPhysAdapterGood Transmits
Clearing Value = <0.5% for 1 hour
Interface is experiencing excessive errors
1.3.6.1.4.1.232.18.2.3.1.1.18
cpqNicIfPhysAdapterBad Transmits
1.3.6.1.4.1.232.18.2.3.1.1.17
cpqNicIfPhysAdapterGood Receives
1.3.6.1.4.1.232.18.2.3.1.1.19
cpqNicIfPhysAdapterBad Receives
NIC Utilization
CPQNIC-MIB1.3.6.1.4.1.232.18.2.3.1.1.16
cpqNicIfPhysAdapterGood Transmits
Clearing Value = <50% for 1 hour
Interface is experiencing High Utilization
1.3.6.1.4.1.232.18.2.3.1.1.18
cpqNicIfPhysAdapterBad Transmits
1.3.6.1.4.1.232.18.2.3.1.1.17
cpqNicIfPhysAdapterGood Receives
1.3.6.1.4.1.232.18.2.3.1.1.19
cpqNicIfPhysAdapterBad Receives
Memory Module Trap
1.3.6.1.4.1.232.6.3
cpqHe4CorrMemReplace MemModule
See CPQHOST-MIB for information on the following trap variables:
sysName
cpqHoTrapFlags
cpqHeResMemBoardIndex
cpqHeResMemModuleIndex
cpqHeResMemModuleSpare PartNo
cpqSiMemModuleSize
cpqSiServerSystemId
Trap number is 6056 which replaces 6029.
A correctable memory log entry indicates a memory module needs to be replaced. The errors have been corrected, but the memory module should be replaced. The error information is reported in the variable cpqHeCorrMemErrDesc