MIBs supported by Cisco TelePresence Exchange System

The lists below indicate which MIBs and SNMP traps are supported by Cisco TelePresence Exchange System.

SNMP version 1 MIB files are in the v1 directory and SNMP version 2 MIB files are in the v2 directory. Note that for every MIB.my in the v2 directory, there exists a SNMP version 1 MIB-V1SMI.my in the v1 directory as well.

CTX System Software through Release 1.3.x

Supported MIBs - All Platforms

MIB Name 1.0.x 1.1.x 1.2.x 1.3.x Revision ID Notes
CISCO-TELEPRESENCE-EXCHANGE-SYSTEM-MIB.my YES YES YES YES 201101130000Z Release 1.2 - Notes:
  • Large Meetings for Resources has been deprecated. ctxMediaCapacityLargeMeeting will always be FALSE
  • All key objects have been updated to match the SOAP API business keys
CISCO-TELEPRESENCE-EXCHANGE-SYSTEM-CAPABILITY.my - - YES YES 201304110000Z New in Release 1.2
Updated in Release 1.3.
CISCO-CDP-MIB.my YES YES YES YES 200111230000Z
CISCO-SYSLOG-MIB.my YES YES YES YES 200512030000Z
HOST-RESOURCES-MIB.my YES YES YES YES 200003060000Z RFC 2790
IF-MIB.my YES YES YES YES 200006140000Z
SNMP-FRAMEWORK-MIB.my YES YES YES YES 200210140000Z RFC 2571
SNMP-MPD-MIB.my YES YES YES YES 200210140000Z RFC 2572
SNMP-NOTIFICATION-MIB.my YES YES YES YES 200210140000Z RFC 2573
SNMP-TARGET-MIB.my YES YES YES YES 200210140000Z RFC 2573
SNMP-USM-MIB.my YES YES YES YES 9901200000Z RFC 2574
SNMP-VACM-MIB.my YES YES YES YES 9901200000Z RFC 2575
SNMPv2-MIB.my YES YES YES YES 200210160000Z
RFC1213-MIB.my YES YES YES YES n/a
TCP-MIB.my YES YES YES YES 200502180000Z
UDP-MIB.my YES YES YES YES 200505200000Z

Additional MIBs Supported – MCS7845-I3 Servers

MIB Name Notes
IBM-SYSTEM-ASSETID-MIB IBM director agent 5.20.02
IBM-SYSTEM-HEALTH-MIB IBM director agent 5.20.02
IBM-SYSTEM-MEMORY-MIB IBM director agent 5.20.02
IBM-SYSTEM-LMSENSOR-MIB IBM director agent 5.20.02
IBM-SYSTEM-NETWORK-MIB IBM director agent 5.20.02
IBM-SYSTEM-POWER-MIB IBM director agent 5.20.02
IBM-SYSTEM-PROCESSOR-MIB IBM director agent 5.20.02
IBM-SYSTEM-STORAGE-MIB IBM director agent 5.20.02 
                See http://www-01.ibm.com/support/docview.wss?uid=isg1IC73225
                for details on how to monitor
                the operational status.

                For ibmStorageDiskDriveOperationalStatus use:
                0  =  Unknown, State of drive is unknown
                2  =  OK, drive is online and functional
                3  =  Degraded, drive function is degraded
                5  =  Predictive Failure, drive is predicting a failure
                6  =  Error, drive is not functional or defunct
                8  =  Starting, drive is starting
                9  =  Stopping, drive is stopping
                10 =  Stopped, drive is in stopped state
                15 =  Dormant, drive is not in use or part of volume


                For ibmStorageStorageVolumeOperationalStatus use:
                0  =  Unknown, state of volume is unknown
                2  =  OK, volume is online and functional
                3  =  Degraded, a drive has failed, a rebuild is in process, or
                a spare drive is in use for  the volume
                6  =  Error, volume is not functional