|
|
This appendix describes the Cisco 6400 private (local) Management Information Base (MIB). The Cisco MIB is included with all Cisco software releases and with CiscoWorks router management software. MIB files contain variables that can be set or read to provide information on network devices and interfaces.
The Cisco MIB is a set of variables that are private extensions to the Internet standard MIB II. MIB II is documented in RFC 1213, Management Information Base for Network Management of TCP/IP-based Internets: MIB-II.
Cisco user-accessible MIB files are organized into two subdirectories. The SNMPv1 MIB files are in the v1/ subdirectory, and the SNMPv2 MIB files are in the v2/ subdirectory. To determine which MIBs the switch supports and get a description of the files, retrieve the following files:
You can obtain copies of these files and the Cisco MIB files in three ways:
http//www.cisco.com
You determine which MIBs the Cisco 6400 supports by obtaining the file supportlist.txt using the following FTP procedure:
Step 1 Use FTP to access the server ftp.cisco.com.
Step 2 Log in with the username anonymous.
Step 3 Enter your e-mail name when prompted for the password.
Step 4 At the ftp> prompt, change directories to /pub/mibs/supportlists/c6400.
Step 5 Use the get supportlist.txt command to obtain the supportlist.txt file containing a list of MIBs the switch supports.
Step 6 Use the get command to retrieve the desired MIB files from the v1/ or v2/ directory.
CCO serves a wide variety of users through two interfaces that are updated and enhanced simultaneously---a character-based version and a multimedia version, which resides on the World Wide Web (WWW). The character-based CCO (called "CCO Classic") supports Zmodem, Kermit, Xmodem, FTP, Internet e-mail, and fax download options, and is excellent for quick access to information over lower bandwidths. The WWW version of CCO provides richly formatted documents with photographs, figures, graphics, and video, as well as hyperlinks to related information.
You can access CCO in the following ways:
Determine which MIBs the Cisco 6400 supports by reading the file supportlist.txt using the following procedure:
Step 1 From the URL: http://www.cisco.com, locate the Cisco Connection Online main menu, and select Service & Support.
Step 2 From the Software Center list, select Network Management Products.
Step 3 From that screen select MIB Files.
Step 4 From the Index of /public/mibs list that appears, select the supportlists/ directory containing descriptions of the MIBs supported by each Cisco product.
Step 5 From the Index of /public/mibs/supportlists list that appears, select the c6400nsp/ directory.
Step 6 Then select the file supportlist.txt to read the supported list of Cisco 6400 MIBs.
Determine which MIBs you will need to copy by reading the supportlist.txt and readme files using the following procedure:
Step 1 From the URL: http://www.cisco.com, the Cisco Connection Online main menu, select Service & Support.
Step 2 From the Software Center list, select Network Management Products.
Step 3 From that screen, select MIB Files.
Step 4 From the Index of /public/mibs list that appears, select the v1/ or v2/ directory depending on which version of SNMP you are using.
Step 5 From the Index of /public/mibs/v1 or Index of /public/mibs/v2 list that appears, select the readme to obtain a brief description of the various MIB files.
The Cisco 6400 supports all standard traps defined in the standard MIBs. Cisco proprietary traps used by the Cisco 6400 are documented in the various MIB files and in the trap definition files located in the public/mibs/traps directory.
Determine which MIBs the Cisco 6400 supports by reading the file supportlist.txt by using the following procedure:
Step 1 Telnet to cco.cisco.com.
Step 2 From the Cisco Connection Online main menu, select Service & Support.
Step 3 From the Service & Support list, select Software Center.
Step 4 From the Software Center list, select Network Management Products.
Step 5 From the Software Network Management Products list, select MIB Files.
Step 6 From the Index of /public/mibs list that appears, select the supportlists/ directory containing descriptions of the MIBs supported by each Cisco product.
Step 7 From the Index of /public/mibs/supportlists list that appears, select the c6400nsp/ directory.
Step 8 Then select the file supportlist.txt to read the supported list of Cisco 6400 MIBs.
You determine which MIBs you will need to copy by reading the supportlists.txt and readme files by using the following procedure:
Step 1 Telnet to cco.cisco.com.
Step 2 From the Cisco Connection Online main menu, select Service & Support.
Step 3 From the Service & Support list, select Software Center.
Step 4 From the Software Center list, select Network Management Products.
Step 5 From the Software Network Management Products list, select MIB Files.
Step 6 From the Index of /public/mibs list that appears, select the v1/ or v2/ directory depending on which version of SNMP you use.
Step 7 From the Index of /public/mibs/v1 or Index of /public/mibs/v2 list that appears, select readme to obtain a brief description of the various MIB files.
The Cisco 6400 supports all standard traps defined in the standard MIBs. Cisco proprietary traps used by the Cisco 6400 are documented in the trap definition files located in the public/mibs/traps directory.
This section describes each of the MIB objects that return unexpected values on the Cisco 6400.
The NRP port connected to the NSP does not have an entry in ciscoAtmIfPhysTable. The NRP port should be treated as an internal port since it does not have a framer and cannot support the attributes defined in the ciscoAtmIfPhysTable.
The Cisco 6400 does not support this MIB object. This object is used on DS1 or E1 line cards that are not currently supported on the Cisco 6400.
The Cisco 6400 returns the value "unknown" for this MIB even though the power supply is working correctly. The PEM LED cannot be read by the system, therefore, the status cannot be reported. The state of the PED LED is determined by the software assuming everything is working correctly. In this case, the PEM status is correctly reported.
The NSP returns the value "unknown" for this MIB even though the fan is working correctly because the Fan LED cannot be read by the system.
This object does not apply to Cisco 6400 so a value of "unknown" is returned.
The Cisco 6400 does not support port level redundancy in the current release.
The Cisco 6400 does not support the auto-sync running-config command in this release. The corresponding bit mask is Bit 2, which has no effect.
You can access the Cisco MIB variables through the Simple Network Management Protocol (SNMP), an application-layer protocol designed to facilitate the exchange of management information between network devices. The SNMP system consists of three parts: SNMP manager, SNMP agent, and MIB.
Instead of defining a large set of commands, SNMP places all operations in a get-request, get-next-request, get-bulk, or set-request format. For example, an SNMP manager can get a value from an SNMP agent or store a value into that SNMP agent. The SNMP manager can be part of a network management system (NMS), and the SNMP agent can reside on a networking device such as a switch. You can compile the Cisco MIB with your network management software. If SNMP is configured on a Cisco 6400, the SNMP agent responds to MIB-related queries being sent by the network management system (NMS).
CiscoWorks, network management software, uses the Cisco MIB variables to set device variables and to poll devices on the internetwork for specific information. The results of a poll can be displayed as a graph and analyzed to troubleshoot internetwork problems, to increase network performance, to verify the configuration of devices, to monitor traffic loads, and more.
The SNMP agent gathers data from the MIB, which is the repository for information about device parameters and network data. (See Figure B-1.) The agent can send traps, or notification of certain events, to the SNMP manager.
The SNMP manager uses information in the MIB to perform the operations described in Table B-1.
| Operation | Description |
|---|---|
get-request | Retrieve a value from a specific variable. |
Retrieve a value from a variable within a table1. | |
get-response | The reply to a get-request, get-next-request, and set-request sent by an NMS. |
get-bulk | (SNMP version 2 only) Retrieve large blocks of data, such as multiple rows in a table, which would otherwise require the transmission of many small blocks of data. |
set-request | Store a value in a specific variable. |
trap | An unsolicited message sent by an SNMP agent to an SNMP manager which indicates that some event has occurred. |
| 1With this operation, an SNMP manager does not need to know the exact variable name. A sequential search is performed to find the needed variable from within a table. |
The MIB structure is logically represented by a tree hierarchy. The root of the tree is unnamed and splits into three main branches: Consultative Committee for International Telegraph and Telephone (CCITT), International Organization for Standardization (ISO), and joint ISO/CCITT.
These branches and those that fall below each category have short text strings and integers to identify them. Text strings describe object names, while integers allow computer software to create compact, encoded representations of the names. For example, the Cisco MIB variable authAddr is an object name and is denoted by number 5, which is listed at the end of its object identifier number 1.3.6.1.4.1.9.2.1.5.
The object identifier in the Internet MIB hierarchy is the sequence of numeric labels on the nodes along a path from the root to the object. The Internet standard MIB is represented by the object identifier 1.3.6.1.2.1. It also can be expressed as iso.org.dod.internet.mgmt.mib. (See Figure B-2.)
The private Cisco MIB is represented by the object identifier 1.3.6.1.4.1.9 or iso.org.dod.internet.private.enterprise.cisco.
For example, in Figure B-3, the Local MIB group is identified by 2; its subgroups, called SYSTEM, is identified by 1 and its subgroup called ciscoPing, is identified by 7. Therefore, the variable in the subgroup ciscoPing has an object identifier (OID) of 1.3.6.1.4.1.9.2.1.7.0. The appended 0 indicates that 1.3.6.1.4.1.9.2.1.7.0 is the only instance of this variable.
Many MIBs use items that are defined in other MIBs. These items are listed in the IMPORTS clause (located at the beginning of the MIB file).
If MIB B imports a definition from MIB A, some MIB compilers require you to load MIB A before you load MIB B. If the MIBs are loaded in the wrong order, the MIB compiler may inform you that the imported items were undefined.
The following list of MIBs that many other MIBs import definitions from shows the order in which these MIBs should be loaded:
1. SNMPv2-SMI.my
2. SNMPv2-TC.my
3. SNMPv2-MIB.my
4. RFC1213-MIB.my
5. IF-MIB.my
6. CISCO-SMI.my
7. CISCO-PRODUCTS-MIB.my
8. CISCO-TC.my
When you attempt to load a MIB and your MIB compiler returns an error of undefined items, look at the IMPORTS clause of the MIB to determine which definitions have been imported. Make sure that you have loaded all the preceding MIBs first.
Posted: Mon Nov 15 12:42:52 PST 1999
Copyright 1989-1999©Cisco Systems Inc.