Table Of Contents
Accessing Other-Vendor MIB Variables Supported by Cisco
Interpreting the Object Identifier
Object Identifier Numbers for Variables
Fast Serial Interface Processor (FSIP) Group
Address Resolution Protocol (ARP)
Connectionless Network Service (CLNS)
Maintenance Operation Protocol (MOP)
Banyan Virtual Integrated Network Service (VINES)
IP Checkpoint Accounting Group
IP Checkpoint Accounting Table
Local IPX Checkpoint Accounting Table
Binary Synchronous Communication (BSC) Group
Blocked Serial Tunnel (BSTUN) Group
Notification for Blocked Serial Tunnel Group
Interface Output Counter Table
Cisco Integrated Services Digital Network (ISDN) MIB Group
Trap related to connection management
Qualified Logical Link Control (QLLC) MIB Group
QLLC Link Station Administrative Table (qllcLSAdminTable)
QLLC Link Station Operational Table (qllcLSOperTable)
QLLC Link Station Statistics Table (qllcLSStatsTable)
QLLC Link Station Admin Group (qllcLSAdminGroup)
QLLC Link Station Operational Group (qllcLSOperGroup)
QLLC Link Station Statistics Group (qllcLSStatsGroup)
QLLC Conversion Administrative Table (convQllcAdminTable)
QLLC Conversion Operational Table (convQllcOperTable)
Channel Interface Processor (CIP) Group
Notifications for Cisco CIP CSNA MIB
Notification for Cisco SNA LLC Group
Cisco Transmission Control Protocol (ciscoTCP) Group
Cisco DownStream Physical Unit (DSPU) Group
Flash Partition Level Information
Cisco Integrated CSU/DSU Group
CSU/DSU Static Configuration Table
T1 CSU/DSU Module Configuration Table
Sw56k CSU/DSU Module Configuration Table
Sw56k CSU/DSU Module Status Table
Notifications for Cisco Integrated CSU/DSU
Cisco Repeater (ciscoRptr) Group
Cisco Remote Source-Route Bridging (RSRB) Group
Environmental Monitor Card and Environmental Monitoring
ciscoEnvMonTemperatureStatusTable
SNMPv2 Notifications Used in Cisco Environmental Monitoring
Notification for Cisco SDLLC Conversion Group
Cisco Serial Tunnel (STUN) Group
Notification for Cisco Serial Tunnel Group
Synchronous Data Link Control (SDLC) Group
Terminal Services Line Session Table
Transmission Control Protocol (TCP) Group
Virtual Integrated Network Service (VINES) Group
Xerox Network Systems (XNS) Group
Public SNMP Traps Supported by Cisco
Variables Supported in RFC 1285
MIBs Supported by Cisco Software Releases
Cisco Internetwork Operating System (Cisco IOS) Release 10.0
Cisco Internetwork Operating System (Cisco IOS) Release 10.2
Cisco Internetwork Operating System (Cisco IOS) Release 10.3(2)
Cisco Internetwork Operating System (Cisco IOS) Release 10.3
Cisco Internetwork Operating System (Cisco IOS) Release 10.3(3)
Cisco Internetwork Operating System (Cisco IOS) Release 11.0
Cisco Internetwork Operating System (Cisco IOS) Release 11.0(5)
MIB User Quick Reference
Preface
From the perspective of a network manager, network management takes place between two major types of systems: those in control, called managing systems, and those observed and controlled, called managed systems. The most common managing system is called a Network Management System (NMS). Managed systems can include hosts, servers, or network components such as routers or intelligent repeaters.
To promote interoperability, cooperating systems must adhere to a common framework and a common language, called a protocol. In the Internet Network Management Framework, that protocol is the Simple Network Management Protocol, commonly called SNMP.
The exchange of information between managed network devices and a robust NMS is essential for reliable performance of a managed network. Because some of these devices may have a limited ability to run management software, the software must minimize its performance impact on the managed device. The bulk of the computer processing burden, therefore, is assumed by the NMS. The NMS in turn runs the network management applications, such as CiscoWorks or CiscoView, that present management information to network managers and other users.
In a managed device, the specialized low-impact software modules, called agents, access information about the managed devices and make it available to the NMS. Managed devices maintain values for a number of variables and report those, as required, to the NMS. For example, an agent might report such data as the number of bytes and packets in and out of the device, or the number of broadcast messages that were sent and received. In the Internet Network Management Framework, each of these variables is referred to as a managed object. A managed object is a classification of anything that can be managed, anything that an agent can access and report back to the NMS. All managed objects are contained in the Management Information Base (MIB), a database of the managed objects.
An NMS can control a managed device by sending a message to the agent (of that managed device) requiring the device to change the value of one or more of its variables. The managed devices can respond to commands such as Sets or Gets. Sets are used by the NMS to control the device. Gets are used by the NMS to monitor the device.
The Cisco MIB User Quick Reference lists the MIB variables that are proprietary to Cisco devices. However, many other internet-standard MIBS are supported by Cisco agents. These standard MIBs are defined in documents called Requests for Comments (RFCs). (For information on the RFC MIBs supported by Cisco, refer to the section "Cisco-Supported MIBs" later in this guide.) Therefore, in order to find specific MIB information, examine the Cisco proprietary MIB structure and the standard RFC MIBs supported by Cisco.
If your NMS is unable to get requested information from a managed device, such as a Cisco router, the MIB that allows that specific data collection might be missing. Typically, if an NMS cannot retrieve a particular MIB variable, either the NMS does not recognize the MIB variable or the agent does not support the MIB variable. If the NMS does not recognize a specified MIB variable, the MIB might need to be loaded into the NMS, usually by means of a MIB compiler. As an NMS administrator, you might need to load the Cisco MIB or the supported RFC MIB into the NMS in order to execute a specified data collection. If the agent does not support a specified MIB variable, you need to find out what version of Cisco IOS or system software you are running. Different MIBs are supported in different software releases.
Use this guide to determine whether your version of software actually supports the specified MIB variable. (See the section "MIBs Supported by Cisco Software Releases" at the end of this guide.) Or, you might want to use this guide to see what variables are available for a given software release. As you reference this guide, read the descriptions of the variables to learn what they are and what they do. Check the Access or Max-Access type to learn what operations, such as reading Gets or writing Sets, can be performed on a particular MIB variable. Check the Syntax type to determine the data type for the MIB variable. Some variables provide textual information (for example, syntax of DisplayString), while others provide numeric information (for example, syntax of Integers or Counters). Once you identify a needed MIB variable, you can easily load the file into the NMS. To learn how to access a Cisco MIB file, refer to "Accessing Cisco MIB Files" later in this main section. Cisco Systems also supports many MIB variables developed by other vendors.
Introduction to the MIB Guide
This guide describes the Cisco Systems private, or local, Management Information Base (MIB) for Cisco Internetwork Operating System (IOS) Release 11.0. 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 and many other internet standard MIBs. MIB II is documented in RFC 1213, Management Information Base for Network Management of TCP/IP-based Internets: MIB-II.
The Cisco MIB is described by a number of MIB files, which can be obtained by FTP from the Cisco server. The listing of Cisco MIB variables in those files is identical to the listing in this guide.
Accessing Cisco MIB Files
You can obtain the files that describe the Cisco MIB using anonymous ftp or the World Wide Web (WWW) to access Cisco Information Online (CIO).
Via ftp, use the ftp ftp.cisco.com command. Log in with the username anonymous and enter your e-mail name when prompted for the password. Use the cd pub/mibs command to go to the directory that contains the MIB files, and then issue the get README command to obtain the readme file containing a list of available product family directories. Cisco IOS MIB files are in the routers subdirectory, organized by release number. Refer to the README file in each directory, as necessary, to determine the location of the desired MIB file. You can then use the ftp command get filename to retrieve the MIB file.
To access CIO via the WWW, use the URL: http://www.cisco.com/public/mibs or ftp://www.cisco.com/pub/mibs.
Accessing Other-Vendor MIB Variables Supported by Cisco
You can obtain the files that describe other-vendor MIB variables supported by Cisco by using the ftp ftp.venera.isi.edu command. Log in with the username anonymous and enter your e-mail name when prompted for the password. Use the cd mib command to go to the directory that contains the MIB files, and then issue the get README command to display the readme file containing a list of available files. You can then use the get filename command to retrieve the desired MIB file (for example, use get novell-nlsp-mib.my to retrieve the Novell NLSP MIB).
Working with SNMP
The Cisco MIB variables are accessible via the Simple Network Management Protocol (SNMP), which is 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-request, 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 router. You can compile the Cisco MIB with your network management software. If SNMP is configured on a router, the SNMP agent can respond to MIB-related queries being sent by the 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 graphed 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 1, the SNMP agent gathers data from the MIB, which is the repository for information about device parameters and network data. The agent also can send traps, or notification of certain events, to the manager. The Cisco trap file, mib.traps, which documents the format of the Cisco traps, is available on the Cisco host ftp.cisco.com.
Figure 1 SNMP Network
The SNMP manager uses information in the MIB to perform the operations described in Table 1.
Table 1 SNMP Manager Operations
get-request
Retrieve a value from a specific variable.
get-next-request
Retrieve the value following the named variable. Often used to retrieve variables from within a table1 .
get-response
The reply to a get-request, get-next-request, get-bulk-request, and set-request sent by an NMS.
get-bulk-request
Similar to get-next-request, but fill the get-response with up to max-repetition number of get-next interactions.
set-request
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.
1 With 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 the MIB.
Internet MIB Hierarchy
The MIB structure is logically represented by a tree hierarchy. (See .) 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 2
Internet MIB Hierarchy
Cisco MIB
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. The Cisco MIB includes the following subtrees: local (2), temporary (3), and, ciscoMgmt (9).
The local subtree contains MIB objects defined prior to Cisco Internetwork Operating System (IOS) Release 10.2. MIB objects defined prior to Software Release 10.2 implemented the SNMPv1 Structure of Management Information (SMI). Beginning with Cisco IOS 10.2, however, Cisco MIBs are defined using the SNMPv2 SMI. MIBs defined using SNMPv2 are being placed in the ciscoMgmt tree. (See .) MIBs currently defined in the local subtree are being deprecated by Cisco as an ongoing process, and being replaced with new objects defined in the ciscoMgmt subtree. For example, the TCP group that was in the local group has been deprecated and replaced with a new TCP group in the ciscoMgmt tree.
Figure 3 Cisco Private MIB Hierarchy
In , the local variables group is identified by 2; its subgroup, called lsystem, is identified by 1; and the first variable is romId with a value of 1. Therefore, the variable romId has a value of 1.3.6.1.4.1.9.2.1.1.0. The appended 0 indicates that 1.3.6.1.4.1.9.2.1.1.0 is the one and only instance of romId.
Note
Although variables are arranged as shown in and as described in the compilable Cisco MIB file, this quick reference guide organizes variable groups and variables within groups alphabetically, so that you can quickly look up descriptions of MIB variables.
Interpreting the Object Identifier
In this guide, each group of Cisco MIB variables is accompanied by an illustration that indicates the specific object identifier for each variable.
For example, in the object identifier 1.3.6.1.4.1.9.2.1 at the top of the illustration indicates the labeled nodes. The last value is the number of the Cisco MIB variable. For example, the MIB variable hostConfigAddr is indicated by the number 51. The object identifier for hostConfigAddr is iso.org.dod.internet.private.enterprise.cisco.local variables.system group.hostConfigAddr or 1.3.6.1.4.1.9.2.1.51.
Figure 4
Object Identifier Example for a Cisco MIB Variable
Tables
When network management protocols use names of MIB variables in messages, each name has a suffix appended. For simple variables, the suffix 0 refers to the instance of the variable with that name. A MIB also can contain tables of related variables.
Following is an excerpt of the information on the IP Routing table (known as lipRoutingTable) from the associated mib file:
lipRoutingTable OBJECT-TYPESYNTAX SEQUENCE OF LIpRouteEntryACCESS not-accessibleSTATUS mandatoryDESCRIPTION"A list of IP routing entries."::= { lip 2 }lipRouteEntry OBJECT-TYPESYNTAX LIpRouteEntryACCESS not-accessibleSTATUS mandatoryDESCRIPTION"A collection of additional objects in thecisco IP routing implementation."INDEX { ipRouteDest }::= { lipRoutingTable 1 }LIpRouteEntry ::=SEQUENCE {locRtMaskIpAddress,locRtCountINTEGER,}The local IP Routing table, lipRoutingTable, is described in . The lipRoutingTable contains two variables: locRtMask and locRtCount. The index for this table is the destination address of the IP route, or ipRouteDest. If there are n number of routes available to a device, there will be n rows in the IP Routing table.
In , for the route with the destination IP address of 131.104.111.1, the IP Routing table network mask is 255.255.255.0. The number of parallel routes within the routing table is 3.
Table 2 IP Routing
Typically, an instance identifier might be a unique interface number or a 0, as described earlier with the romId example. An instance identifier can also be an (IP) address. For example, to find the network mask for the route with a destination address of 131.104.211.243, use the variable locRtMask with an instance identifier of 131.104.211.243. The format is locRtMask.131.104.211.243.
In this guide, when variables belong to a table, they are listed in the section describing the table. The following tag is used to indicate the end of a table:
End of Table
All variables before this tag are part of the table.
Local Variables
The local variables section pertains to all Cisco devices and contains the following groups.
Note
•
Pertains to the Flash memory used to store, boot, and write system software images. Includes information such as Flash memory size and the contents of flash. Operations can be invoked by SETing MIB variables such as erasing Flash memory and transferring a Flash memory file to a Trivial File Transfer Protocol (TFTP) server. The Flash group supports Cisco 7000, 7010, and AGS+. The Flash group in Local Variables has been deprecated by the Cisco Flash group found in CiscoMgmt.
•
Provides information on Cisco device interfaces, such as traffic statistics, line status, average speed of input and output packets, and error checking.
•
Provides information about devices running IP. Includes information such as how and from whom an interface obtained its address, Internet Control Message Protocol (ICMP) messages, and number of packets lost.
•
Provides information on system-wide parameters for Cisco devices, such as software version, host name, domain name, buffer size, configuration files, and environmental statistics.
•
Provides information about terminal services, such as number of physical lines, line status, line type, line speed, type of flow control, and type of modem.
•
Provides statistics on the number of input and output bytes and packets for TCP connections. The "local" TCP group has been deprecated, and replaced with a new TCP group in the ciscoMgmt group which provides more functionality.
Temporary Variables
This section is equivalent to the experimental space defined by the Structure of Management Information (SMI). These variables are subject to change for each Cisco Systems software release.
Temporary variables consists of the following groups, which are presented in alphabetical order. (See .)
•
Pertains to devices running the AppleTalk protocol. Includes information such as total number of input and output packets, number of packets with errors, and number of packets with Address Resolution Protocol (ARP) requests and replies.
•
Pertains to hardware information about Cisco devices. Includes information such as the types of cards used by the device, the hardware version of the cards, and the number of slots in the chassis. The cardTableIfIndex Table, introduced in Cisco IOS Release 10.3, provides logical mapping between the device interface and a card's presence in the chassis. The variables in this table support only the Cisco 4000, Cisco 4500, Cisco 7000, and Cisco7010. By implementing the new MIB table in supported configurations, you can discover statistics about the card. The new MIB table provides significant solutions for CiscoWorks and CiscoView users.
•
Pertains to devices running the DECnet protocol. Includes information such as hop count, host name, total packets received and sent, and number of packets with header errors.
•
•
•
Pertains to devices running the Novell protocol. Includes information such as total number of input and output packets, number of packets with errors, and number of packets with service access point (SAP) requests and replies.
•
Pertains to devices running the VINES protocol. Includes information such as total number of input and output packets, number of packets with errors, and number of packets with Internet Control Message Protocol (ICMP) requests and replies.
•
Pertains to devices running the XNS protocol. Includes information such as number of packets forwarded, total number of input packets, and total number of packets with errors.
ciscoMgmt Variables
The ciscoMgmt subtree consists of the following variables:
•
Provides configuration and operational information for Cisco's Binary Synchronous Communications (BSC) implementation. The following two entities are managed: BSC ports (serial interfaces), and BSC control units (stations on a port).
•
Provides configuration and operational information about Cisco's blocked serial tunnel (BSTUN) implementation. Four entities are managed: BSTUN global entry, BSTUN group table, BSTUN port table, and BSTUN route table.
•
Specifies the MIB module for objects used to manage the Cisco CIP card.
•
Provides information on the configuration of the Channel Interface Processor (CIP) Channel Systems Network Architecture (CSNA) feature. In eight tables, three pieces of information are provided: configuration of I/O device addresses of communication controllers, information regarding VTAM to internal adapter connections, and the number of sessions allowed between the VTAM and internal adapter.
•
Provides configuration information on the internal (virtual) LAN and internal (virtual) adapter components of the CIP CSNA feature.Within the LAN configuration are entries for the type of LAN and the bridging protocol. Within the adapter configuration are entries for the MAC address and the SNA name used for alerts.
•
Manages the TCP/IP protocol stack running on the Channel Interface Processor (CIP) card. In Release 11.0, only the TCP/IP offload feature makes use of this MIB. The read-only values allow statistics and status for every instance of IP, TCP, UDP, and ICMP protocol stacks to be viewed.
•
Provides the MIB module for management of the Cisco Discovery Protocol in Cisco devices.
•
Contains the information necessary for the definition and management of DSPU objects. Supported DSPU objects include dspuNode (Global DSPU node information), dspuPoolClass (LU pool class information), dspuPooledLu (Pooled LU information), dspuPu (Upstream/Downstream PU node information), dspuLu (Upstream/Downstream LU information), and dspuSap (Local SAP information)
•
Provides the status of the Environmental Monitor on those devices that support one. The Cisco Environmental Monitor MIB is new and contains enhanced functionality over its predecessor, including support for redundant power supplies.
•
Provides support for the Dual Flash Bank feature introduced in Cisco IOS Release 10.3(4). The Cisco Flash group is also supported in Release 10.2.
•
The integrated Channel Service Unit (CSU)/Data Service Unit (DSU) group is used with the Cisco 2524 and Cisco 2525 products, and is for T1 and switched 56 kbps interfaces. It enables network managers to retrieve line statistics and CSU/DSU configuration data.
•
Provides the status of the ISDN Interfaces on the routers. The ISDN MIB was introduced in Release 10.3(3).
•
Provides detailed access to custom and priority queuing information. This information was previously available only via the show queue EXEC command.
•
Provides user with the ability to initiate a ping (ICMP echo request) from the Cisco device to a specified destination address.
•
Provides information about the attributes of the local-remote RSRB peer relationship. The following three entities are managed: virtual rings, remote peers, and associated Token Rings.
•
Provides standard repeater (hub) features that are not in RFC 1516. The objects in this MIB support features such as link-test, auto-polarity, and source-address control, and the MDI/MDI-X switch status. The Cisco Repeater MIB was introduced in Release 10.3(3).
•
Provides read-only configuration and operational information on Cisco's implementation of SDLC-to-LLC2 media translation. The SDLLC MIB provides a table entry for each serial interface and SDLC address pair, and includes information such as FEP MAC addresses, SDLC station addresses, and Token Ring numbers on LLC2 stations.
•
Provides configuration and operational information on Cisco's serial tunnel implementation. The following four entities are managed: global STUN information, STUN groups, STUN ports, and STUN routes
•
Manages the LLC2 stack that runs on a Channel Interface Processor (CIP) card. The CIP card provides the SNA gateway to an IBM mainframe via a channel connection from the router.
•
Provides access to the cisco Snapshot support and is present in all router based products.
Snapshot routing provides easy solutions to two common problems:
1) The need to configure static routes for Dial on Demand Routing (DDR) interfaces, and 2) the overhead of periodic updates for routing protocols to remote branch offices over dedicated serial lines.
When snapshot routing is configured on an interface, normal routing updates can be sent across the interface for a short time (determined by the user). When this user-configured period of activity has elapsed, the routing updates are suspended, and the routes known to the snapshot interface are locked, putting the interface into a "frozen period." The duration of this period is also user configurable. During this time, changes in network topology are typically not transmitted across the snapshot interface, although some network protocols provide the capability to transmit changes.
•
Manages configuration of the TCP offload feature. It is made up of one table entry that shows configuration information such as path, device, host name, router name, API host application, and API router application.
•
Provides statistics on the number of input and output bytes and packets for TCP connections; ciscoTCP, however, provides more functionality over its counterpart in the Local Variables subtree.
•
Pertains to devices running the VINES protocol. Includes information such as total number of input and output packets, number of packets with errors, and number of packets with ARP and RTP requests and replies. Also includes tables of routes and neighbors. This MIB incorporates objects from the Cisco VINES command line interface, and was influenced by Banyan VINES MIB. The ciscoVINES provides VINES routing information with enhanced functionality over its predecessor located in the temporary variables subtree.
•
The QLLC is a data link protocol defined by IBM that allows SNA data to be transported across X.25 networks. The QLLC MIB includes a managed entity, called a link station. The link station includes objects to configure and monitor logical connections.
Terminology
This section presents the syntax and access type categories used to describe each variable. For details on syntax, refer to RFC 1155, and to RCF 1442 for SNMPv2.
Syntax
The syntax describes the format of the information, or value, that is returned upon monitoring or setting information in a device with a MIB variable.
Note
The syntax can be any one of the following categories:
•
Syntax: Octet string (SIZE (0-2)). The two-octet hex device address for the device the Systems Network Architecture (SNA) host will use to communicate with the Channel Systems Network Architecture (CSNA) feature on the Channel Interface Processor (CIP).
The first octet will always be zero for consistency with other CIP MIBs.
For example, for device address 1C (decimal 28) the 2-octet value is 00:1C.
•
A counter is a nonnegative integer that increases until it reaches some maximum value. After reaching the maximum value, it rolls back to zero. For example, the variable locIfipInPkts counts the number of IP protocol input packets on an interface.
•
The type of queuing algorithm used on the interface.
Syntax: Integer. 1 = fifo (first-in, first-out), 2 = priority (priority queuing), 3 = custom (custom queuing), 4 = weightedFair (weighted fair queuing)
•
A display string is a printable ASCII string. It is typically a name or description. For example, the variable netConfigName provides the name of the network configuration file for a device.
•
Syntax: Octet string (SIZE (0-2)). This channel path is a two-octet value made up of the following values:
For example, for path C7, channel logical address 9, control unit logical address 4, the 2-octet value is C7:94.
Note
•
An integer of 1 or 2, where 1 = disabled and 2 = enabled. Represents status information for a particular row in the table.
•
An integer is a numeric value. It can be an actual number, for example, the number of lost IP packets on an interface. It also can be a number that represents a nonnumeric value. For example, the variable tsLineType returns the type of terminal services line to the SNMP manager. A 2 indicates a console line; a 3 indicates a terminal line; and so on.
•
An integer from -232 to 232-1.
•
The variable hostConfigAddr indicates the IP address of the host that provided the host configuration file for a device.
•
TimeStamp is defined in RFC 1443 as the value of the MIB-II sysUpTime object at which a specific event occurred.
•
Timeticks is a nonnegative integer that counts the hundredths of a second since an event. For example, the variable loctcpConnElapsed provides the length of time that a TCP connection has been established.
•
An integer of 1 or 2, where 1 = true or 2 = false. TruthValue is defined in "Textual Conventions for version 2 of the Simple Network Management Protocol (SNMPv2)," RFC 1443.
Access
The access type, which applies to SNMPv1, describes whether a MIB variable can be used under one of the following circumstances:
•
This variable can be used to monitor information only. For example, the locIPUnreach variable, whose access is read-only, indicates whether Internet Control Message Protocol (ICMP) packets concerning an unreachable address will be sent.
•
This variable can be used to monitor information and to set a new value for the variable. For example, the tsMsgSend variable, whose access is read-write, determines what action to take after a message has been sent.
The possible integer values for this variable follow:
1 = nothing
2 = reload
3 = message done
4 = abort•
This variable can be used to set a new value for the variable only. For example, the writeMem variable, whose access is write-only, writes the current (running) router configuration into nonvolatile memory where it can be stored and retained even if the router is reloaded. If the value is set to 0, the writeMem variable erases the configuration memory.
Max-Access
This variable, which applies to SNMPv2, can represent one of the following four states: read-create, read-write, read-only, and not-accessible.
•
You cannot read or write to this variable. Entry statements are typically among those variables that are not accessible.
•
This specifies a tabular object that can be read, modified, or created as a new row in a table.
•
This variable can be used only to monitor information .
•
You can read or modify this variable.
Internetwork Management
The International Organization for Standards (ISO) Network Management Forum defined five areas of network management: fault, configuration, security, performance, and accounting. Cisco MIB variables can be mapped to each of these areas (as described in this section) and used to manage your internetwork.
Although a variable might have a primary use for one aspect of network management, variables often overlap multiple areas. For example, locIPhow and locIPwho, discussed next under "Configuration Management," can also be used for fault management if a system is not loading properly.
•
Fault management involves running diagnostic tests on the internetwork, analyzing the results, and isolating and resolving problems.
Example:
Several of the variables described in the section "Basic" provide resources for troubleshooting. For example, the variables freeMem, and whyReload provide information on why a router was reloaded, and indicate how much memory is currently available in a device.
The variables described in the section "Environmental Monitor Card and Environmental Monitoring" provide feedback on the physical status of the AGS+ router or Cisco 7000 router.
Statistics from variables in the section "Interface Table" record the number of packets dropped on particular interfaces so that they can be identified as potential trouble spots.
•
Configuration management involves monitoring and controlling the configuration of devices on the internetwork.
Example:
The locIPhow and locIPwho variables described in the section "Internet Protocol (IP) Group" provide information on how a device received its IP address and the device that provided it with its address.
The variables described in the sections "Host Configuration File" and "Network Configuration File" provide configuration file names and addresses of hosts supplying network configuration files.
The variables described in the section "System Configuration" provide information such as the name of the host that supplied the system boot image for a device and the name of the boot image.
•
Security management deals with controlling access to network resources through the use of authentication techniques and authorization policies.
Example:
The variable authAddr contains the address of the last SNMP manager that failed the authorization check. The locIPSecurity variable provides the IP security level assigned to an interface.
•
Performance management measures traffic flow across the internet, calculates the number of packets that are successfully transmitted against those that are dropped, and so on, in order to optimize efficiency.
Example:
The variables described in the section "CPU Utilization" provide feedback on CPU performance. The variables described in the section "Interface Group" provide statistics on time between packets sent, number of packets transmitted successfully, and so on.
•
Accounting management involves collecting and processing data related to resource consumption on the internet.
Example:
The variables described in the section "IP Checkpoint Accounting Table" later in this guide, provide numerous statistics such as packets and bytes sent successfully or dropped.
Cisco-Supported MIBs
Cisco supports several MIBs, which are described in the following Requests for Comments (RFCs). Also listed are RFCs describing the Internet standards that Cisco Systems follows with regard to its MIB format and the SNMP protocol.
•
Describes the common structures and identification scheme for the definition of management information for use with TCP/IP-based Internets. Formal descriptions of the structure are given using Abstract Syntax Notation One (ASN.1).
•
Describes the initial version of the standard Internet Management Information Base, MIB I. MIB I is superseded by MIB II, as described in RFC 1213.
•
Describes the SNMP architecture and supported operations.
•
Describes the format for producing concise, yet descriptive, MIB modules.
•
Describes the Internet standard MIB II for use with network management protocols in TCP/IP-based internets.
RFC 1213 obsoletes RFC 1158.
•
Describes the SNMP standardized traps and provides a means for defining enterprise-specific traps.
•
Describes the managed objects used for managing subnetworks that use the IEEE 802.5 Token Ring technology.
Cisco implements the mandatory tables (Interface table and Statistics table), but not the optional table (Timer table) of this MIB.
RFC 1239 contains information that updates RFC 1231.
•
Describes the managed objects for AppleTalk that use the SNMP protocol.
Cisco Systems provides support for the AppleTalk Resolution Protocol (ARP), AppleTalk Port Group, AppleTalk Datagram Delivery Protocol (DDP), AppleTalk Routing Table Maintenance Protocol (RTMP), AppleTalk Zone Information Protocol (ZIP), AppleTalk Name Binding Protocol (NBP), and AppleTalk Echo Group
•
The OSPF MIB defines an IP routing protocol that provides management information related OSPF and is supported by Cisco routers.
•
Describes the managed objects for Fiber Distributed Data Interface (FDDI) devices that are accessible via the Simple Network Management Protocol (SNMP).
Cisco Systems supports only some of the variables in the Station Management (SMT) and Media Access Control (MAC) groups of this MIB. Refer to the Cisco publication FDDI MIB Variables in 9.0 Product Update Bulletin No. 181. RFC 1285 corresponds to the ANSI FDDI SMT 6.2 draft standard
•
RFC 1512 updates, but does not obsolete, RFC 1285.The changes from RFC 1285, based on changes from ANSI SMT 6.2 to SMT 7.3, were so numerous that the objects in this MIB module are located on a different branch of the MIB tree. No assumptions should be made about compatibility with RFC 1285.
•
Specifies an IAB (Internet Activities Board) standards track protocol for the Internet community and defines objects for managing Ethernet-like objects.
•
This document outlines the subset of OSI's Abstract Syntax Notation One (ASN.1) used to define the Management Information Base (MIB) for version 2 of the Simple Network Management Protocol (SNMPv2).
•
This document defines the initial set of extensions (textual conventions) to the basic types defined in the SMI (RFC1442) which are available to all MIB modules.
•
Describes the managed objects which correspond to the properties associated with SNMPv2 parties, SNMPv2 contexts, and access control policies, as defined by the SNMPv2 Administrative Model.
Cisco supports the MIB variables as required by the Conformance clauses specified in these MIBs.
•
Describes the managed objects that cause the behavior of an SNMPv2 implementation.
Cisco supports the MIB variables as required by the Conformance clauses specified in these MIBs.
•
RFC 1493 obsoletes half of RFC 1286.
•
Defines a portion of the Management Information Base (MIB) for use with network management protocols in the Internet community. In particular, this RFC defines objects for managing IEEE 802.3 10- megabits per second (mbps) baseband repeaters, sometimes referred to as hubs.
•
RFC 1525 obsoletes half of RFC 1286.
Cisco supports all of the groups described in this MIB, including the following groups: dotldBase, dotldSr, dot1dStp, and dotIdTp.
•
RFC 1406 obsoletes RFC 1232.
•
Cisco supports the following tables in this MIB:
•
•
•
•
The Error Table is not supported in this MIB.
•
Cisco supports the following tables in this MIB:
•
•
•
The LAPB XID table is not supported in this MIB.
•
The X.25 packet layer MIB is available under the ifType node
rfc887-x25 (5) registered under the MIB-II transmission Object Identifier. This condition applies to all X.25 interfaces, including any DDN-X.25 encapsulation interfaces. Cisco supports the following tables in this MIB:•
•
•
•
•
•
The following tables are not supported in this MIB:
•
•
•
Provides some support for RFC 1269 and replacement draft IETF-BGP-MIBC4-OS.Txt. Cisco supports the following tables in this MIB:
•
•
•
•
•
The RS-232-like Hardware Device MIB applies to interface ports that might logically support the Interface MIB, a Transmission MIB, or the Character MIB. The most common example is an RS-232 port with modem signals.
The RS-232-like Hardware Device MIB is mandatory for all systems that have such a hardware port supporting services managed through some other MIB.
The MIB includes many similar types of hardware, and as a result contains objects not applicable to all of those hardware types. The compliance definitions have a general group for all implementations, and separate groups for the different types of ports, such as asynchronous and synchronous.
The RS-232-like Hardware Port MIB includes RS-232, RS-422, RS-423, V.35, and serial physical links (other asynchronous or synchronous) with a similar set of control signals.
The MIB contains objects that relate to physical layer connections. Such connections may provide hardware signals (other than for basic data transfer), such as RNG and DCD. Hardware ports also have such attributes as speed and bits per character.
•
Cisco supports most, but not all, objects in RFC 1593, an informational RFC containing managed objects that describe the Advanced Peer-to-Peer Networking (APPN) node, the connections of the node to other SNA nodes, and the APPN network topology.
To obtain copies of RFCs, use the ftp nic.ddn.mil command. Log in as anonymous and enter your e-mail name when prompted for the password. Enter the cd rfc command to change to the correct directory. Use the get rfc-index.txt command to retrieve a list of all available RFCs. To obtain a copy of any specific RFC, enter get rfcnnnn.txt, where nnnn is the RFC number.
Related Cisco Publications
For detailed information on configuration and troubleshooting commands, refer to the following Cisco publications:
•
•
•
•
Users of the CiscoWorks router management software can refer to the CiscoWorks User Guide for information on CiscoWorks router management software features and its use of MIB variables for the purposes of graphing and analyzing network performance, ensuring configuration consistency, troubleshooting, and more.
Suggested Reading
Following are suggested reading materials:
•
•
•
•
•
Object Identifier Numbers for Variables
The figures in this section provide a visual overview of the Cisco MIB variables along with the object identifier numbers for each MIB variable. The MIB variables are arranged alphabetically within each figure (in the same order in which they appear in the sections of this guide).
Figure 5
Local Variables: Flash File Table and Flash Group
Figure 6
Local Variables: FSIP Group Variables
Figure 7
Local Variables: Interface Group Table
Figure 8 Local Variables: Interface Group—ARP, AppleTalk, Apollo, Bridging, CLNS, DECnet, HP Probe, IP, LNM, and MOP
Figure 9 Local Variables: Interface Group—Novell, Other Protocols, STUN, Spanning Tree
Figure 10
Local Variables: Interface Group—VINES
Figure 11
Local Variables: Interface Group—XNS
Figure 12
Local Variables: Internet Protocol (IP) Group
Figure 13
Local Variables: IP Accounting Table
Figure 14
Local Variables: IP Checkpoint Accounting Table
Figure 15
Local Variables: System Group—Buffers
Figure 16 Local Variables: System Group—CPU Utilization and Environmental Monitor Card
Figure 17
Local Variables: Terminal Services Group
Figure 18 Local Variables: Transmission Control Protocol (TCP) Connection Table
Figure 19
Temporary Variables: AppleTalk and Chassis
Figure 20
Temporary Variables: DECnet
Figure 21
Temporary Variables: DECnet Tables
Figure 22 Temporary Variables: Novell and Xerox Network Systems (XNS)
Figure 23
Temporary Variables: IPX Accounting Table I
Figure 24
Temporary Variables: IPX Checkpoint Accounting Table
Figure 25 Temporary Variables: Virtual Integrated Network System (VINES) I
Figure 26 Temporary Variables: (VINES) II
Figure 27 ciscoMgmt Variables: Binary Synchronous Communication (BSC)
Figure 28 ciscoMgmt Variables: Blocked Serial Tunnel (BSTUN)
Figure 29 ciscoMgmt Variables: Channel Interface Processor (CIP) Card Table
Figure 30 ciscoMgmt Variables: Channel Interface Processor (CIP) Card Daughter Board and SubChannel Tables
Figure 31 ciscoMgmt Variables: Channel Interface Processor Group CardClaw
Figure 32 ciscoMgmt Variables: Cisco CIP CSNA
Figure 33 ciscoMgmt Variables: Cisco CIP CSNA (cont.)
Figure 34 ciscoMgmt Variables: Cisco CIP LAN
Figure 35 ciscoMgmt Variables: ciscoDiscovery Protocol
Figure 36 ciscoMgmt Variables: Cisco CIP TCP/IP
Figure 37 ciscoMgmt Variables: Cisco CIP TCP/IP (cont.)
Figure 38 ciscoMgmt Variables: Cisco Flash MIB
Figure 39 ciscoMgmt Variables: Cisco Integrated CSU/DSU Group
Figure 40 ciscoMgmt Variables: Cisco Interface Queue
Figure 41 ciscoMgmt Variables: Cisco ISDN MIB
Figure 42 ciscoMgmt Variables: Cisco Remote Source-Route Bridging (RSRB)
Figure 43
ciscoMgmt Variables: Cisco Repeater (ciscoRptr) MIB
Figure 44 ciscoMgmt: Qualified Logical Link Control (QLLC)
Figure 45 ciscoMgmt Variables: Cisco SDLLC Conversion
Figure 46 ciscoMgmt Variables: Cisco Serial Tunnel (STUN)
Figure 47 ciscoMgmt Variables: Cisco SNA LLC
Figure 48 ciscoMgmt Variables: Cisco SNA LLC (cont.)
Figure 49 ciscoMgmt Variables: ciscoSnapshot MIB
Figure 50 ciscoMgmt Variables: Cisco Transmission Control Protocol (TCP) Connection Table
Figure 51 ciscoMgmt Variables: Cisco TCP Offload
Figure 52 ciscoMgmt Variables: ciscoVINES MIB I
Figure 53 ciscoMgmt Variables: ciscoVINES MIB II
