|
|
This appendix describes the Cisco Systems private, or local, Management Information Base (MIB) for the LightStream 1010 ATM switch. The Cisco MIB is provided with all Cisco software releases and with CiscoWorks router management software. The MIB file contains 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. The MIB II is documented in RFC 1213, Management Information Base for Network Management of TCP/IP-based Internets: MIB-II.
Cisco's public MIB files are organized into two subdirectories. SNMPv1 MIBs are in the v1/ subdirectory and SNMPv2 MIBs are in the v2/ subdirectory. Determine which MIBs the switch supports and get a description of the files by retrieving the following:
You can obtain a copy of these files and the Cisco MIB files in three ways:
http//www.cisco.com
You determine which MIBs the LightStream 1010 switch supports by obtaining the file supportlist.txt using the following FTP procedure:
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:
http://www.cisco.com.
cco.cisco.com (198.92.32.130).
You determine which MIBs the LightStream 1010 switch supports by reading the file supportlist.txt using the following procedure:
You determine which MIBs you will need to copy by reading the supportlist.txt and readme files using the following procedure:
The LightStream 1010 ATM switch supports all standard traps defined in the standard MIBs listed in the "Product Overview" chapter. Cisco proprietary traps used by the LightStream 1010 ATM switch are documented in the various MIB files and in the trap definition files in the public/mibs/traps directory.
You determine which MIBs the LightStream 1010 switch supports by reading the file supportlist.txt using the following procedure:
You determine which MIBs you will need to copy by reading the supportlists.txt and readme files using the following procedure:
The LightStream 1010 ATM switch supports all standard traps defined in the standard MIBs listed in the "Product Overview" chapter. Cisco proprietary traps used by the LightStream 1010 ATM switch are documented in the trap definition files in the public/mibs/traps directory.
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, and 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 LightStream 1010 switch, the SNMP agent responds to MIB-related queries being sent by the network management system (NMS).
An example of an NMS is the CiscoWorks network management software. CiscoWorks 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 in order to troubleshoot internetwork problems, increase network performance, verify the configuration of devices, monitor traffic loads, and more.
As shown in Figure B-1, the SNMP agent gathers data from the MIB, which is the repository for information about device parameters and network data. The agent can send traps, or notification of certain events, to the manager.
The SNMP manager uses information in the MIB to perform the operations described in Table B-1.
| Operation | Description |
|---|---|
Retrieve a value from a specific variable | |
Retrieve a value from a variable within a table1 | |
The reply to a get-request, get-next-request, and set-request sent by an NMS | |
get-bulk2 | Retrieve large blocks of data, such as multiple rows in a table, which would otherwise require the transmission of many small blocks of data |
Store a value in a specific variable | |
trap | An unsolicited message sent by an SNMP agent to an SNMP manager indicating that some event has occurred |
The MIB structure is logically represented by a tree hierarchy. (See Figure B-2.) 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, identified by 1 and its subgroup called ciscoPing, 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 definitions that are defined in other MIBs. These definitions are listed in the IMPORTS clause near the top of the MIB.
If MIB B imports a definition from MIB A, some MIB compilers require you to load MIB A prior to loading MIB B. If you get the MIB loading order wrong, the MIB compiler might complain about what was imported claiming it as undefined.
Following is a list of MIBs that many other MIBs import definitions from and 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
Loading the MIBs in this order can eliminate 95 percent of your load order definition problems.
When you attempt to load a MIB and your MIB compiler returns and error of undefined items, look at which MIB definitions the MIB you are loading imports definitions from in the IMPORTS clause of the MIB. Make sure that you have loaded all the preceding MIBs first.
|
|