|
|
This chapter describes those Management Information Base (MIBs) supported by PNNI Version 2.0. Existing MIBs include 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, Private Network-to-Network Interface (PNNI) implementation does not support all of the tables defined in a particular MIB.
Contents of this chapter include:
For all the rowStatus attributes in the PNNI MIB and CISCO-WAN-SVC-MIB, the agent supports only the following:
The Network Management System (NMS) can use createAndGo to create a row and destroy to delete a row.
The standard MIBs supported by PNNI are listed in Table 1-1.
 |
Note Not all of the objects in a MIB are supported by PNNI. |
| MIB | RFC | MIB File Name | Supported Objects |
|---|---|---|---|
ATM PNNI MIB | atm forum pnni mib | PNNI-MIB.my | pnniBase Group, pnniNodeTable1, |
ATM MIB | RFC 2515 | ATM-MIB.my | atmInterfaceConfTable2 |
| 1pnniNodeDomain Name is not supported. 2This object supports only atmInterfaceMyNeighborIpAddress and atmInterface MyNeighborIfName as read-only. |
The CISCO-WAN-SVC-MIB.my file is defined for Switched Virtual Circuit (SVC) and PNNI management.
Table 1-2 shows the standard MIB that is supported by PNNI.
| MIB | RFC | MIB File Name | Supported Objects |
|---|---|---|---|
CISCO SVC | none | CISCO-WAN-SVC-MIB.my | ciscoWANSvcInfo Group, |
Restrictions on the use of the MIB is listed in Table 1-3.
|
Note Not all of the objects in a MIB are supported by PNNI. |
| MIB | RFC Number | MIB File Name | Not Supported Objects |
|---|---|---|---|
CISCO SVC | Not Applicable | CISCO-WAN-SVC-MIB.my | cwspIlmiSecureLink, |
| 1This object is not supported. 2This object is implemented as read-only. |
Posted: Fri Sep 15 11:17:03 PDT 2000
Copyright 1989-2000©Cisco Systems Inc.