|
|
This chapter describes those MIBs supported by PXM45 Version 2.0. Existing MIBs include those public MIBs that are part of the Internet Official Protocol Standards and are published as Request for Comments (RFC) text files. Another category of existing MIBs are Cisco Enterprise MIBs, which are common for Cisco products. In both categories, PXM45 implementation does not support all of the tables defined in a particular MIB.
This chapter includes the following sections:
Note that not all of the objects in a MIB are supported by PXM45. Restrictions on the use of these MIBs are listed in Table 1-4. Table 1-1 shows the standard MIBs supported by PXM45.
| MIB | RFC Number | MIB File Name | Supported Objects |
|---|---|---|---|
RFC 2233 | IF-MIB.my | ||
RFC2737 | ENTITY-MIB.my | ||
RFC 1659 | RS-232-MIB.my | ||
RFC 2578 | |||
RFC 2579 | |||
RFC 2580 |
These MIBs are used in a wide variety of Cisco products. Note that not all of the objects in a MIB are supported by PXM45. Table 1-2 shows the Cisco Enterprise MIBs supported by PXM45.
| MIB | MIB File Name | Supported Objects |
|---|---|---|
CISCO-ENTITY-FRU-CONTROL-MIB.my | ||
CISCO-ENTITY-SENSOR-MIB.my | All the objects | |
CISCO-PRODUCTS-MIB.my | Only OIDs used for sysObjectID object for MSSBU Products | |
CISCO-SMI.my | CISCO-Specific Structure of Management Information | |
CISCO-TC.my | CISCO-Specific Textual Conventions | |
CISCO-SYSTEM-MIB.my | All the objects | |
CISCO-ENTITY-VENDORTYPE-MIB.my | Those OIDs used for entphysicalVendorType Object for MSSBU Products |
The legacy MIBs supported in PXM45 are part of the AXIPOP-MIB.my file. These are shown in Table 1-3.
| MIB | MIB File Name | Supported Objects |
|---|---|---|
RTM-MIB.my | All the objects | |
ERROR-STATUS-MIB.my | All the objects | |
BASIS-SHELF-MIB.my | ||
BASIS SHELF MIB: For Module Redundancy Table | BASIS-SHELF-MIB.my | |
BASIS-GENERIC1-MIB.my | ||
GENERICOBJECT-MIB.my |
For certain standard MIB objects, the access defined in the MIB and the access as implemented in PXM45 are different, with a different default value in certain cases. These constitute MIB support limitations.
Table 1-4 shows those objects for which there are MIB support limitations. In all cases, the access defined by the MIB is for read-write, while only read-only is supported in the PXM45.
| MIB | MIB File Name | Unsupported Table/Objects |
|---|---|---|
SNMPv2-MIB.my | ||
IF-MIB.my |
All the deprecated Objects | |
ENTITY-MIB.my | ||
CISCO-ENTITY-FRU-CONTROL-MIB.my | ||
BASIS-SHELF-MIB.my | ||
BASIS-GENERIC1-MIB.my | all the objects except moduleTrapAlarmSeverity | |
GENERICOBJECT-MIB.my |
This MIB contains OID assignments for CISCO components for use by ENTITY-MIB. This MIB module defines the object identifiers that are assigned to various components on Cisco products, which are used by the entPhysicalTable of the ENTITY-MIB to uniquely identify the type of each physical entry.
Table 1-5 shows the possible values for entPhysicalVendorType object in MGX8850 Release 2.0.
Table 1-5 shows the OID assignments for chassis, backplane, slots, and fans.
| Component Name | OID Name |
|---|---|
MGX 8850 Chassis | |
MGX 8850 Backplane | |
Processor Switch Module (PXM) Slot | |
Service Module (SM) Slot | |
MGX 8800 Fan Tray(9 Fans) | |
MGX 8800 AC Power Supply Tray | |
MGX 8800 Single Pulse Fan | |
MGX 8800 Dual Pulse Fan | |
MGX 8800 Power Entry Module (PEM) | |
MGX 8800 Temperature Sensor | |
MGX 8800 Power Supply Voltage Level Monitor (DC Level Monitor) | |
Fan Speed Sensor for MGX 8850, SES | |
Alternating Current (AC) Power Supply, | |
Alternating Current (AC) Power Supply, | |
SMFLR-1-622 | |
SMFIR-2-622 | |
SMFLR-2-622 | |
MMF-8-155 | |
SMFIR-8-155 | |
SMFLR-8-155 | |
SMFIR-1-2488 | |
Table 1-6 shows the OID assignments for Front Modules as defined in CISCO-ENTITY-VENDORTYPE-OID-MIB.
| Component Name | OID Name |
|---|---|
Table 1-6 shows the OID assignments for Line Modules.
| Component Name | OID Name |
|---|---|
![]()
![]()
![]()
![]()
![]()
![]()
![]()
Posted: Fri Apr 14 19:49:05 PDT 2000
Copyright 1989 - 2000©Cisco Systems Inc.