|
|
This chapter describes those MIBs supported by AXSM 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, AXSM implementation does not support all of the tables defined in a particular MIB.
This chapter includes the following sections:
The standard MIBs supported by AXSM are shown in . Note that not all of the objects in a MIB are supported by AXSM. Restrictions on the use of these MIBs are listed in Table 1-3 and Table 1-4.
| MIB | RFC Number | MIB File Name | Supported Objects |
|---|---|---|---|
RFC 2233 | |||
RFC 2558 | |||
RFC 2496 | |||
RFC 2578 | |||
RFC 2579 | |||
RFC 2580 |
| 1There are some limitations. |
The Cisco Enterprise MIBs supported by AXSM are shown in Table 1-2. These MIBs are used in a wide variety of Cisco products. Note that not all of the objects in a MIB are supported by AXSM.
| MIB | MIB File Name | Supported Objects |
|---|---|---|
CISCO-SMI.my | CISCO-Specific Structure of Management Information | |
CISCO-TC.my | CISCO-Specific Textual Conventions | |
CISCO-SONET-MIB.my | CISCO-Specific extensions to SONET-MIB | |
Resource Partition MIB for the ATM Virtual Interfaces | ||
CISCO-DS3-MIB.my | Cisco-Specific Extensions to DS3-MIB | |
CISCO-ATM-VIRTUAL-IF-MIB.my | All Objects | |
All Objects | ||
All Objects |
Two kinds of MIB support restrictions exist. For certain standard MIB objects, the access defined in the MIB and the access as implemented in AXSM are different, with a different default value in certain cases. These constitute MIB support limitations.
There are also unsupported objects in certain standard MIBs. Certain tables or objects are unsupported.
Those objects for which there are MIB support limitations are shown in Table 1-3. In all cases, the access defined by the MIB is for read-write, while as implemented in the AXSM, only read-only is supported. The MIB file can be identified by the first part of the object name; SONET refers to the file SONET-MIB.my, and dsx3 refers to the DS3-MIB.my file.
| Object Name | Access Defined in MIB | Access as Implemented in AXSM | Default Value/Equivalent Object |
|---|---|---|---|
read-write | read-only | csConfigType | |
read-write | read-only | N/A | |
read-write | read-only | N/A | |
read-write | read-only | N/A | |
read-write | read-only | N/A | |
read-write | read-only | Not Supported | |
read-write | read-only | other (1) | |
read-write | read-only | N/A | |
read-write | read-only | disabled (1) | |
read-write | read-only | disabled (1) |
Those tables or objects that are unsupported by AXSM in the standard MIB specified are shown in Table 1-4.
| Standard MIB File | Unsupported Table or Objects |
|---|---|
SONET-MIB.my | |
DS3-MIB.my | |
| 1Denotes a Trap. |
The ifTable defined in IF-MIB has entries for the various physical and logical interfaces. The terminologies used for the various interfaces are shown in Table 1-5. These interfaces are identified by the ifType mib object in ifTable.
| Interface | Identification | ifType Values |
|---|---|---|
physical interface | Identifies the interface for physical lines. | ds3(30), sonet (39), ds1 (18), ethernetCsmacd(6) |
ATM physical interface (ATM Phy Interface) | Identifies the interface for the ATM Cell layer on a physical interface. | atm(37) |
ATM virtual interface | Identifies the logical interface configured on a physical interface. | atmVirtual(14) |
![]()
![]()
![]()
![]()
![]()
![]()
![]()
Posted: Fri Apr 14 20:02:03 PDT 2000
Copyright 1989 - 2000©Cisco Systems Inc.