Introduction

This guide describes the Cisco Systems private, or local, Management Information Base (MIB) for Software Release 9.1. The Cisco MIB is provided with all Cisco software releases and with the NetCentral network management software. The MIB file contains variables that can be set or read to provide information on network devices and interfaces.

You can obtain the file describing the Cisco MIB with the
ftp ftp.cisco.com command. Log in with the username anonymous and the password guest. Use the get README command to get the file containing a list of available files. To obtain the Software Release 9.1 MIB file, use the get mib91.txt command. You can compile the Cisco MIB with your network management software.

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.

The Cisco MIB variables are accessible via the Simple Network Management Protocol (SNMP). SNMP is an application-layer protocol designed to facilitate the exchange of management information between network devices. The SNMP system consists of three parts: an SNMP manager, SNMP agent, and Management Information Base (MIB).

Instead of defining a large set of commands, SNMP places all operations in a get request and set request format. A manager can get a value from an agent or store a value into that agent. The SNMP manager can be part of a Network Management System (NMS).

An example of an NMS is NetCentral, Cisco's network management software. NetCentral 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. See Figure 1.

Figure 1:

SNMP Network

The agent gathers data from the MIB, the repository for information about device parameters and network data.The agent can also send traps, or notification of certain events, to the manager. The Cisco trap file, mib.trap83, which documents the format of the Cisco traps, is available at ftp.cisco.com.

The SNMP manager uses information in the MIB to perform the operations described in Table 1.

SNMP Manager Operations

Operation	Description
get-request	Retrieve a value from a specific variable.
get-next-request	Retrieve a value from a variable within a table.1
get-response	The reply to a get-request sent by an NMS.
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.

Internet MIB Hierarchy

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 help us understand object names, while integers allow computer software to form compact, encoded representations of the names.

The object identifier in the 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 of 1.3.6.1.2.1. It can also be expressed as iso.org.dod.internet.mgmt.mib. The mib subtree contains both the original MIB and MIB II, which supersedes the original MIB.
See Figure 2.

Figure 2: Internet MIB Hierarchy

Groups in the Cisco MIB

The private Cisco MIB is represented by the object identifier of 1.3.6.1.4.1.9, or iso.org.dod.internet.private.enterprise.cisco. As shown in Figure 3, the Cisco MIB is split into two main areas: local variables and temporary variables.

Figure 3: Cisco Private MIB Hierarchy

In Figure 3, the local variables group is identified by a 2, its subgroup, called system, is identified by a 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. It is appended a 0, indicating 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 Figure 3 and as described above in the compilable MIB file, this quick reference guide organizes variable groups and variables within groups alphabetically in order to speed up the process of looking up descriptions of MIB variables.

---

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 can also contain tables of related variables. A table allows a related set of variables to be applied across several devices or interfaces.

For example, the Cisco MIB interface table contains a list of network interfaces for a particular device. The interface table contains many related variables. (Refer to Table 4 on page 24.) For simplification, only the following three variables are included in Table 2: locIfHardType, locIflineProt, and locIfLastIn.

Sample MIB Table

Interface Number	locIfHard Type	locIfline Prot	locIfLastIn
1	Ethernet	1	100
2	Ethernet	2	0
3	serial	1	500

The first column is the index to the table. An index uniquely identifies a row within a table. In this case, the index is a unique interface number. InTable 2, there are three interfaces associated with the device. For the locIfHardType variable, locIfHardType.1, locIfHardType.2, and locIfHardType.3 represent the instance identifiers that correlate to a specific interface.

Typically, an instance identifier can be a unique interface number, as described in Table 2, or as a 0, as described earlier with the romId example. An instance identifier can also be a network 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.

---

Note 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. All variables before this tag are part of the table. Variables described after the tag do not belong in the previous table.

---

End of Table

Local Variables

The local variables section pertains to all Cisco devices and contains the following subgroups:

• Flash group

Pertains to the Flash memory used to store, boot, and write system software images. Includes information such as Flash memory size, and erases Flash memory and writes Flash memory to a Trivial File Transfer Protocol (TFTP) server.

• Interface group

Provides information on Cisco device interfaces, such as traffic statistics, line status, average speed of input and output packets, error checking, and more.

• Internet Protocol (IP) group

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.

• IP checkpoint accounting group

Records the number of bytes and packets switched through the system on an IP address basis.

• System group

Provides information on system-wide parameters for Cisco devices, such as software version, host name, domain name, buffer size, configuration files, and environmental statistics.

• Terminal server group

Provides information about the Cisco communication server (previously terminal server) products, such as number of physical lines, line status, line type, line speed, type of flow control, and type of modem.

• Transmission Control Protocol (TCP) group

Provides statistics on the number of input and output bytes and packets for TCP connections.

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.

The temporary variables section consists of the following subgroups:

• AppleTalk group

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.

• DECnet group

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.

• Novell group

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.

• VINES group

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 Protocol (ICP) requests and replies.

• Xerox Network Systems (XNS) group

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.

Terminology

This section illustrates the syntax and access type categories used to describe each variable. An explanation of how tables work within the Cisco MIB is also included here. For details on syntax, refer to RFC 1155.

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. The syntax can be any one of the following categories:

• Counter

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.

• Display string

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.

• Integer

An integer is a numeric value. It can be an actual number, for example, the number of lost IP packets on an interface. It can also
be an arbitrary number that represents a nonnumeric value. For example, the variable tsLineType returns the type of terminal
server line. A 2 indicates a console line, a 3 indicates a terminal line, and so on.

• Network address

A network address represents an address for an interface or device. Currently, only the Internet Protocol (IP) is supported. For example, the variable hostConfigaddr indicates the IP address of the host that provided the host configuration file for a device.

• TimeTicks

TimeTicks is a nonnegative integer that counts hundredths of a second since an event. For example, the variable loctcpConnElapsed provides the length of time that a TCP connection has been established.

Access

The access type describes whether this MIB variable can be used under one of the following three circumstances:

• Read-only

This variable can be used to monitor information only.

• Read-write

This variable can be used to monitor information and to set a new value for the variable as well.

• Write-only

This variable can only be used to set a new value for the variable.

Five Areas of Internetwork Management

The Cisco MIB variables can be applied to manage your internetwork in any of the following five areas:

• Configuration management

Configuration management involves monitoring and controlling the configuration of devices on the internetwork.

Example:

The locIPhow and locIPwho variables described in "Internet Protocol (IP) Group" starting on page 52 provide information on how a device received its IP address and the device that provided it with its address.

The variables described in "Host Configuration File" on page 87 and "Network Configuration File" on page 88 provide information such as configuration file names and addresses of hosts supplying network configuration files.

The variables described in "System Configuration" on page 89 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.

• Performance Management

Performance management involves the measurement of traffic flow across the internet, calculating 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 "CPU Utilization" on page 77 provide feedback on CPU performance. The variables described in "Interface Group" on page 24 provide statistics on time between packets sent, number of packets transmitted successfully, and so on.

• Fault management

Fault management involves running diagnostic tests on the internetwork, analyzing the results, and isolating and resolving problems.

Example:

Several of the variables described in "Basic" on page 61 provide resources for troubleshooting. For example, the variables whyreload, ping, and freemem provide information on why a router was reloaded, whether a device is functioning, and how much memory is currently available in a device.

The variables described in "Environmental Monitor Card" on
page 78 provide feedback on the physical status of the AGS+ router.

Statistics from variables in "Interface Group" on page 24 record the number of packets dropped on particular interfaces so that they can be identified as potential trouble spots, and so on.

• Accounting management

Accounting management involves collecting and processing data related to resource consumption on the internet.

Example:

The variables described in "IP Checkpoint Accounting Group" on page 58 provide numerous statistics such as packets and bytes sent successfully or dropped.

• Security management

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.

Cisco-Supported MIBs

Cisco supports several MIBs which are described in the following Requests for Comments (RFCs). Also listed here are RFCs describing the Internet standards that Cisco Systems follows with regard to its MIB format.

• RFC 1155, Structure and Identification of Management Information for TCP/IP-based Internets, May 1990

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)

• RFC 1156, Management Information Base for Network Management of TCP/IP-based Internets, May 1990

Describes the initial version of the standard Internet Management Information Base, MIB I. MIB I is superceded by MIB II, described in RFC 1213.

• RFC 1157, A Simple Network Management Protocol (SNMP), May 1990

Describes the SNMP architecture and supported operations.

• RFC 1212, Concise MIB Definitions, March 1991

Describes the format for producing concise, yet descriptive, MIB modules.

• RFC 1213, Management Information Base for Network Management of TCP/IP-based Internets: MIB-II, March 1991

Describes the Internet standard MIB II for use with network management protocols in TCP/IP-based internets.

• RFC 1215, A Convention for Defining Traps for use with the SNMP, March 1991

Describes the SNMP standardized traps and provides a means for defining enterpise-specific traps.

• RFC 1231, IEEE 802.5 Token Ring MIB, May 1991

Describes the managed objects used for managing subnetworks which 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. Support is provided for only the CSC-R16, STR (dual-port Token Ring) and CTR (Token Ring card for the cBus controller) cards.

• RFC 1285, FDDI Management Information Base,
  January 1992

Describes the managed objects for 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 Cisco's FDDI MIB Variables in 9.0 Product Update Bulletin.

• RFC 1286, Definitions of Managed Objects for Bridges, December 1991.

Cisco supports only the "dotldBase" and "dotldSr" groups in this MIB, or objects applicable to all type of bridges and to source-route bridging, respectively.

To obtain copies of RFCs, use the ftp nic.ddn.mil command. Log in as anonymous with the password guest. 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 rfcxxxx.txt, where xxxx is the RFC number.

Related Cisco Publications

Refer to the following Cisco publications for detailed information on configuration and troubleshooting commands:

• Router Products Configuration and Reference

• Protocol Translator Configuration and Reference

• Communication Server Configuration and Reference

Refer to the NetCentral User Guide for information on Cisco's network 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

The following are suggested reading materials:

• Leinwand, A. and Fang, K., Network Management: A Practical Perspective, 1993.

• Rose, M.T., The Simple Book: An Introduction Management of TCP/IP-based Internets, 1991

Local Variables

This section describes the local variables within the Cisco product line. Certain groups of variables may or may not be present depending upon the software options in the managed device.

The local variables section contains the following group of variables:

• Flash

• Interface

• Internet Protocol (IP)

• IP Checkpoint Accounting

• System

• Terminal server

• Transmission Control Protocol (TCP)

Flash Group

The Flash memory card is an add-in card of Flash EPROM (erasable programmable read-only memory) storage onto which system software images may be stored, booted, and rewritten.

Flash File Table

The local Flash file table, lflashFileDirTable, contains information on a per file basis and includes the following three variables: flashDirName, flashDirSize, and flashDirStatus. The index to this table is flashEntries, or the number of Flash files. If the device has n number of flash files, the table will contain n number of rows.

For example, in Table 3, the flash1 file has a directory size of 50 octets and its status is valid, represented by the integer 1.

Flash File

flashEntries	flashDirName	flashDirSize	flashDirStatus
1	flash1	50	1
2	flash2	100	1
3	flash3	200	2

flashDirName

Provides the name associated with the Flash entry.

Syntax: Display string

Access: Read-only

flashDirSize

Provides the size (in octets) of a Flash entry.

Syntax: Integer

Access: Read-only

flashDirStatus

Indicates the status of the Flash entry.

Syntax: Integer (1=valid, 2=deleted)

Access: Read-only

End of Table

flashcard

Provides the type of card connected to the Flash card installed in the router.

Syntax: Display string

Access: Write-only

flashcontroller

Provides the type of Flash controller installed in the router.

Syntax: Display string

Access: Write-only

flashEntries

Provides the number of entries, or files, that exist in the Flash memory directory.

Syntax: Integer

Access: Read-only

flashErase

This variable sets a request to erase Flash memory in order to free up all available memory space. The entire Flash memory is erased. Individual files cannot be erased from Flash memory.

Syntax: Integer

Access: Write-only

flashEraseStatus

Indicates the status (successful or not) of the last Flash erase procedure.

Syntax: Integer (1=successful, 2=not successful)

Access: Read-only

flashEraseTime

Indicates the last time the Flash memory was erased.

Syntax: TimeTicks

Access: Read-only

flashFree

Provides the number (in octets) of unused, or available, Flash memory.

Syntax: Integer

Access: Read-only

flashSize

Provides the total size (in octets) of Flash memory. The Flash memory card provides 4 MB of storage.

Syntax: Integer

Access: Read-only

flashStatus

Provides status on the availability of Flash memory in the router.

Syntax: Integer

Access: Read-only

flashToNet

Requests to write the Flash memory to a Trivial File Transfer Protocol (TFTP) server. The value (display string) is the name of the Flash file being sent, or written, to the server. The instance ID is the IP address of the TFTP host.

Syntax: Display string

Access: Write-only

flashToNetStatus

Indicates the status of the last transfer from Flash memory to a Trivial File Transfer Protocol (TFTP) server on the network.

Syntax: Integer (1=successful, 2=not successful)

Access: Read-only

flashToNetTime

Indicates the last time a Trivial File Transfer Protocol (TFTP) image was copied into the Flash memory on the router.

Syntax: TimeTicks

Access: Read-only

flashVPP

Provides the status of the VPP DIP.

Syntax: Integer (1=installed, 2=missing)

Access: Read-only

netToFlash

Copies a software image from trivial file transfer protocol (TFTP) server to the Flash memory on the router. The value should be the name of the Flash entry to write. The instance ID is the IP address of the TFTP host.

Syntax: Display string

Access: Write-only

netToFlashStatus

Provides the status of last transfer of software image from the Trivial File Transfer Protocol (TFTP) server to the Flash memory in the router.

Syntax: Integer

Access: Read-only

netToFlashTime

Indicates the last time a copy from a Trivial File Transfer Protocol (TFTP) server to the Flash memory on the router took place.

Syntax: TimeTicks

Access: Read-only

Interface Group

The following variables apply to interfaces attached to Cisco devices. These variables can be used to monitor the performance of the network in terms of number of packets dropped, time allocations for input and output packets, and so on. These variables can also be used for fault management. For example, variable values indicate which interfaces are dropping packets or have had to be restarted several times.

Interface Table

The interface table, lifTable, contains all of the variables described in this section. The index to the table is ifIndex. ifIndex indicates the number of the interface. If the device has n number of interfaces, the interface table will contain n rows.

Interface

Interface Number	locifHardType	locIfLineProt	etc.
1	Contains all of the variables described under "Interface Group" from page 25 to page 51.
2
etc.

Across All Interfaces

This section contains basic interface variables that apply to all interfaces and are not protocol-specific.

locIfCarTrans

Provides the number of times the interface received the carrier detect (CD) signal.

Syntax: Integer

Access: Read-only

locIfCollisions

Provides the number of output collisions detected on this interface.

Syntax: Integer

Access: Read-only

locIfDelay

Provides the amount of delay in microseconds of the interface. Used by Interior Gateway Routing Protocol (IGRP).

Syntax: Integer

Access: Read-only

locIfDescr

Provides a description of the interface.

Syntax: Display string

Access: Read-write

locIfFastInOctets

Provides the octet count for inbound traffic routed with fast switching.

Syntax: Counter

Access: Read-only

locIfFastInPkts

Provides the packet count for inbound traffic routed with fast switching.

Syntax: Counter

Access: Read-only

locIfFastOutOctets

Provides the octet count for outbound traffic routed with fast switching.

Syntax: Counter

Access: Read-only

locIfFastOutPkts

Provides the packet count for outbound traffic routed with fast switching.

Syntax: Counter

Access: Read-only

locIfHardType

Provides the type of interface, such as Ethernet, serial, FDDI, and so on.

Syntax: Display string

Access: Read-only

locIfInAbort

Provides the number of input packets that were aborted.

Syntax: Integer

Access: Read-only

locIfInBitsSec

Provides a five-minute average of input bits per second.

Syntax: Integer

Access: Read-only

locIfInCRC

Provides the number of input packets that had cyclic redundancy checksum (CRC) errors.

Syntax: Integer

Access: Read-only

locIfInFrame

Provides the number of input packet that were misaligned.

Syntax: Integer

Access: Read-only

locIfInGiants

Provides the number of input packets that were larger than the physical media permitted.

Syntax: Integer

Access: Read-only

locIfInIgnored

Provides the number of input packets that were ignored by this interface.

Syntax: Integer

Access: Read-only

locIfInOverrun

Provides the number of input packets that arrived too quickly for the hardware to receive.

Syntax: Integer

Access: Read-only

locIfInPktsSec

Provides a five-minute average of input packets per second.

Syntax: Integer

Access: Read-only

locIfInputQueueDrops

Provides the number of packets dropped because the input queue was full.

Syntax: Integer

Access: Read-only

locIfInRunts

Provides the number of input packets that were smaller than the physical media permitted.

Syntax: Integer

Access: Read-only

locIfKeep

Indicates whether keepalives are enabled on this interface.

Syntax: Integer (1=enabled, 2=disabled)

Access: Read-only

locIfLastIn

Provides the elapsed time in milliseconds since the last line protocol input packet was received.

Syntax: Integer

Access: Read-only

locIfLastOut

Provides the elapsed time in milliseconds since the last line protocol output packet was transmitted.

Syntax: Integer

Access: Read-only

locIfLastOutHang

Provides the elapsed time in milliseconds since the last line protocol output packet could not be successfully transmitted.

Syntax: Integer

Access: Read-only

locIfLineProt

Indicates whether the interface is up or down.

Syntax: Integer (1=up, 2=down)

Access: Read-only

locIfLoad

Provides the loading factor of the interface. Used by Interior Gateway Routing Protocol (IGRP).

Syntax: Integer

Access: Read-only

locIfOutBitsSec

Provides a five-minute average of output bits per second.

Syntax: Integer

Access: Read-only

locIfOutPktsSec

Provides a five-minute average of output packets per second.

Syntax: Integer

Access: Read-only

locIfOutputQueueDrops

Provides the number of packets dropped because the output queue
was full.

Syntax: Integer

Access: Read-only

locIfPakmon

Enables Pakmon on IGS routers only. Pakmon is a software package designed to monitor traffic flow on the network.

Syntax: Integer (1=enable, 2=disable)

Access: Read-write

locIfReason

Provides the reason for the interface's most recent status change.

Syntax: Display string

Access: Read-only

locIfReliab

Provides the level of reliability for the interface. Used by Interior Gateway Routing Protocol (IGRP).

Syntax: Integer

Access: Read-only

locIfResets

Provides the number of times the interface was reset internally.

Syntax: Integer

Access: Read-only

locIfRestarts

Provides the number of times the interface needed to be completely restarted.

Syntax: Integer

Access: Read-only

locIfSlowInOctets

Provides the octet count for inbound traffic routed with slow switching.

Syntax: Counter

Access: Read-only

locIfSlowInPkts

Provides the packet count for inbound traffic routed with slow switching.

Syntax: Counter

Access: Read-only

locIfSlowOutPkts

Provides the packet count for outbound traffic routed with slow switching.

Syntax: Counter

Access: Read-only

locIfSlowOutOctets

Provides the octet count for outbound traffic routed with slow switching.

Syntax: Counter

Access: Read-only

Address Resolution Protocol (ARP)

The following variables in the interface group apply to interfaces running the Address Resolution Protocol (ARP). ARP provides dynamic addressing between 32-bit IP addresses and Ethernet addresses.

locIfarpInOctets

Provides the Address Resolution Protocol (ARP) input octet count.

Syntax: Counter

Access: Read-only

locIfarpInPkts

Provides the Address Resolution Protocol (ARP) input packet count.

Syntax: Counter

Access: Read-only

locIfarpOutOctets

Provides the Address Resolution Protocol (ARP) output octet count.

Syntax: Counter

Access: Read-only

locIfarpOutPkts

Provides the Address Resolution Protocol (ARP) output packet count.

Syntax: Counter

Access: Read-only

AppleTalk

The following variables in the interface group apply to interfaces running AppleTalk.

locIfAppleTalkInOctets

Provides the AppleTalk protocol input octet count.

Syntax: Counter

Access: Read-only

locIfAppleTalkInPkts

Provides the AppleTalk protocol input packet count.

Syntax: Counter

Access: Read-only

locIfAppleTalkOutOctets

Provides the AppleTalk protocol output octet count.

Syntax: Counter

Access: Read-only

locIfAppleTalkOutPkts

Provides the AppleTalk protocol output packet count.

Syntax: Counter

Access: Read-only

Apollo

The following variables in the interface group apply to interfaces running Apollo.

locIfapolloInOctets

Provides the Apollo protocol input octet count.

Syntax: Counter

Access: Read-only

locIfapolloInPkts

Provides the Apollo protocol input packet count.

Syntax: Counter

Access: Read-only

locIfapolloOutOctets

Provides the Apollo protocol output octet count.

Syntax: Counter

Access: Read-only

locIfapolloOutPkts

Provides the Apollo protocol output packet count.

Syntax: Counter

Access: Read-only

Bridging

The following variables in the interface group apply to interfaces running bridging protocols.

locIfbridgedInOctets

Provides the bridged protocol input octet count.

Syntax: Counter

Access: Read-only

locIfbridgedInPkts

Provides the bridged protocol input packet count.

Syntax: Counter

Access: Read-only

locIfbridgedOutOctets

Provides the bridged protocol output octet count.

Syntax: Counter

Access: Read-only

locIfbridgedOutPkts

Provides the bridged protocol output packet count.

Syntax: Counter

Access: Read-only

locIfsrbInOctets

Provides the source-route bridging (SRB) protocol input octet count.

Syntax: Counter

Access: Read-only

locIfsrbInPkts

Provides the source-route bridging (SRB) protocol input packet count.

Syntax: Counter

Access: Read-only

locIfsrbOutOctets

Provides the source-route bridging (SRB) protocol output octet count.

Syntax: Counter

Access: Read-only

locIfsrbOutPkts

Provides the source-route bridging (SRB) protocol output packet count.

Syntax: Counter

Access: Read-only

CHAOSnet

The following variables in the interface group apply to interfaces running CHAOSnet, a local area network protocol developed at the Massachusetts Institute of Technology in the mid-1970s.

locIfchaosInOctets

Provides the CHAOSnet protocol input octet count.

Syntax: Counter

Access: Read-only

locIfchaosInPkts

Provides the CHAOSnet protocol input packet count.

Syntax: Counter

Access: Read-only

locIfchaosOutOctets

Provides the CHAOSnet protocol output octet count.

Syntax: Counter

Access: Read-only

locIfchaosOutPkts

Provides the CHAOSnet protocol output packet count.

Syntax: Counter

Access: Read-only

Connectionless Network Service (CLNS)

The following variables in the interface group apply to interfaces running CLNS.

locIfclnsInOctets

Provides the Connectionless Network Service (CLNS) protocol input byte count.

Syntax: Counter

Access: Read-only

locIfclnsInPkts

Provides the Connectionless Network Service (CLNS) protocol input packet count.

Syntax: Counter

Access: Read-only

locIfclnsOutOctets

Provides the Connectionless Network Service (CLNS) protocol output byte count.

Syntax: Counter

Access: Read-only

locIfclnsOutPkts

Provides the Connectionless Network Service (CLNS) protocol output packet count.

Syntax: Counter

Access: Read-only

DECnet

The following variables in the interface group apply to interfaces running DECnet.

locIfdecnetInOctets

Provides the DECnet protocol input octet count.

Syntax: Counter

Access: Read-only

locIfdecnetInPkts

Provides the DECnet protocol input packet count.

Syntax: Counter

Access: Read-only

locIfdecnetOutOctets

Provides the DECnet protocol output octet count.

Syntax: Counter

Access: Read-only

locIfdecnetOutPkts

Provides the DECnet protocol output packet count.

Syntax: Counter

Access: Read-only

HP Probe

The following variables in the interface group apply towards interfaces running HP Probe, an address resolution protocol developed by
Hewlett-Packard.

locIfprobeInOctets

Provides the HP Probe protocol input octet count.

Syntax: Counter

Access: Read-only

locIfprobeInPkts

Provides the HP Probe protocol input packet count.

Syntax: Counter

Access: Read-only

locIfprobeOutOctets

Provides the HP Probe protocol output octet count.

Syntax: Counter

Access: Read-only

locIfprobeOutPkts

Provides the HP Probe protocol output packet count.

Syntax: Counter

Access: Read-only

Internet Protocol (IP)

The following variables in the interface group apply to interfaces running the Internet Protocol (IP).

locIfipInOctets

Provides the Internet Protocol (IP) input octet count.

Syntax: Counter

Access: Read-only

locIfipInPkts

Provides the Internet Protocol (IP) input packet count.

Syntax: Counter

Access: Read-only

locIfipOutOctets

Provides the Internet Protocol (IP) output octet count.

Syntax: Counter

Access: Read-only

locIfipOutPkts

Provides the Internet Protocol (IP) output packet count.

Syntax: Counter

Access: Read-only

LAN Network Manager (LNM)

The following variables in the interface group apply towards interfaces running the LAN Network Manager protocol. This protocol manages source-route bridge (SRB) networks.

locIflanmanInOctets

Provides the LAN Network Manager protocol input octet count.

Syntax: Counter

Access: Read-only

locIflanmanInPkts

Provides the LAN Network Manager protocol input packet count.

Syntax: Counter

Access: Read-only

locIflanmanOutOctets

Provides the LAN Network Manager protocol output octet count.

Syntax: Counter

Access: Read-only

locIflanmanOutPkts

Provides the LAN Network Manager protocol output packet count.

Syntax: Counter

Access: Read-only

Maintenance Operation Protocol (MOP)

The following variables in the interface group apply to interfaces running the Maintenance Operation Protocol (MOP).

locIfmopInOctets

Provides the Maintenance Operation Protocol (MOP) input octet count.

Syntax: Counter

Access: Read-only

locIfmopInPkts

Provides the Maintenance Operation Protocol (MOP) input packet count.

Syntax: Counter

Access: Read-only

locIfmopOutOctets

Provides the Maintenance Operation Protocol (MOP) output octet count.

Syntax: Counter

Access: Read-only

locIfmopOutPkts

Provides the Maintenance Operation Protocol (MOP) output packet count.

Syntax: Counter

Access: Read-only

Novell

The following variables in the interface group apply to interfaces running Novell.

locIfnovellInOctets

This provides the Novell protocol input octet count.

Syntax: Counter

Access: Read-only

locIfnovellInPkts

Provides the Novell protocol input packet count.

Syntax: Counter

Access: Read-only

locIfnovellOutOctets

Provides the Novell protocol output octet count.

Syntax: Counter

Access: Read-only

locIfnovellOutPkts

Provides the Novell protocol output packet count.

Syntax: Counter

Access: Read-only

Other Protocols

The following variables record the number input and output packets and number of input and output octets for interfaces running protocols other than those listed in the interface group.

locIfotherInOctets

Provides the input octet count for protocols other than those listed in this section.

Syntax: Counter

Access: Read-only

locIfotherInPkts

Provides the input packet count for protocols other than those listed in this section.

Syntax: Counter

Access: Read-only

locIfotherOutOctets

Provides the output octet count for protocols other than those listed in this section.

Syntax: Counter

Access: Read-only

locIfotherOutPkts

Provides the output packet count for protocols other than those listed in this section.

Syntax: Counter

Access: Read-only

PARC Universal Protocol (PUP)

The following variables in the interface group apply to interfaces running the Xerox PARC Universal Protocol (PUP).

locIfpupInOctets

Provides the PARC Universal Protocol (PUP) input octet count.

Syntax: Counter

Access: Read-only

locIfpupInPkts

Provides the PARC Universal Protocol (PUP) input packet count.

Syntax: Counter

Access: Read-only

locIfpupOutOctets

Provides the PARC Universal Protocol (PUP) output octet count.

Syntax: Counter

Access: Read-only

locIfpupOutPkts

Provides the PARC Universal Protocol (PUP) output packet count.

Syntax: Counter

Access: Read-only

Serial Tunnel (STUN)

The following variables in the interface group apply to interfaces using the Serial Tunnel (STUN) protocol. STUN allows devices that use Synchronous Data Link Control (SDLC) or High-level Data Link Control (HDLC) to be connected through one or more Cisco routers across different network topologies.

locIfstunInOctets

Provides the Serial Tunneling (STUN) protocol input octet count.

Syntax: Counter

Access: Read-only

locIfstunInPkts

Provides the Serial Tunneling (STUN) protocol input packet count.

Syntax: Counter

Access: Read-only

locIfstunOutOctets

Provides the Serial Tunneling (STUN) protocol output octet count.

Syntax: Counter

Access: Read-only

locIfstunOutPkts

Provides the Serial Tunneling (STUN) protocol output packet count.

Syntax: Counter

Access: Read-only

Spanning Tree

The following variables in the interface group apply to interfaces running the spanning-tree protocol. Used in bridging, spanning trees provide root and designated bridges to notify all other bridges in the network when an address change has occurred, thereby eliminating loops.

locIfspanInOctets

Provides the spanning-tree input octet packet count.

Syntax: Counter

Access: Read-only

locIfspanInPkts

Provides the spanning-tree input protocol packet count.

Syntax: Counter

Access: Read-only

locIfspanOutOctets

Provides the spanning-tree output octet packet count.

Syntax: Counter

Access: Read-only

locIfspanOutPkts

Provides the spanning-tree output protocol packet count.

Syntax: Counter

Access: Read-only

VINES

The following variables in the interface group apply to interfaces running the Banyan Virtual Network System (VINES) protocol. This proprietary protocol is derived from the Xerox Network Systems (XNS) protocol. The VINES variables provide the number of input and output packets and number of input and output octets on a per interface basis.

locIfvinesInOctets

Provides the VINES protocol input octet count.

Syntax: Counter

Access: Read-only

locIfvinesInPkts

Provides the VINES protocol input packet count.

Syntax: Counter

Access: Read-only

locIfvinesOutOctets

Provides the VINES protocol output octet count.

Syntax: Counter

Access: Read-only

locIfvinesOutPkts

Provides the VINES protocol output packet count.

Syntax: Counter

Access: Read-only

Xerox Network Systems (XNS)

The following variables in the interface group apply to interfaces running XNS.

locIfxnsInOctets

Provides the Xerox Network Systems (XNS) protocol input octet count.

Syntax: Counter

Access: Read-only

locIfxnsInPkts

Provides the Xerox Network Systems (XNS) input packet count.

Syntax: Counter

Access: Read-only

locIfxnsOutOctets

Provides the Xerox Network Systems (XNS) protocol output octet count.

Syntax: Counter

Access: Read-only

locIfxnsOutPkts

Provides the Xerox Network Systems (XNS) protocol output packet count.

Syntax: Counter

Access: Read-only

End of Table

Internet Protocol (IP) Group

The IP group provides variables pertaining to the Internet Protocol (IP), such as the determination of how an interface obtained its IP address, who supplied the address, and Internet Control Message Protocol (ICMP) messages about IP packet processing.

IP Address Table

The Cisco IP address table, lipAddrTable, contains six entries, or rows. These entries are the following variables: locIPHow, locIPWho, locIPHelper, locIPSecurity, locIPRedirects, and locIPUnreach. The index to this table is the IP address of the device, or ipAdEntAddr. If a device has n number of IP addresses, there will be n rows in the table.

For simplification, Table 5 shows only the locIpHow and locIPWho variables. The locIPHow variable value shows that the device at 131.108.201.245 obtained its address through nonvolatile memory. The locIPWho variable value indicates the device was assigned its current address by the device at 131.101.200.248.

IP Address

IP Address	locIPHow	locIPWho	etc.
131.108.201.245	nonvolatile	131.101.200.248
142.111.202.244	nonvolatile	131.56.70.249
etc.

locIPHelper

Provides the IP address for broadcast forwarding support.

Syntax: Network address

Access: Read-only

locIPHow

Describes how this interface obtained its IP address. Typically, the address is determined by nonvolatile memory.

Syntax: Display string

Access: Read-only

locIPRedirects

Indicates whether Internet Control Message Protocol (ICMP) redirects will be sent or not.

Syntax: Integer (1=sent, 2=not sent)

Access: Read-only

locIPSecurity

Describes the IP security level assigned to the interface. Levels include Reserved4, TopSecret, Secret, Confidential, and so on. See RFC 1108, U.S. Department of Defense Security Options for the Internet Protocol, for details on IP security levels.

Syntax: Integer

Access: Read-only

locIPUnreach

Indicates whether Internet Control Message Protocol (ICMP) packets indicating an unreachable addresses will be sent or not.

Syntax: Integer (1=sent, 2=not sent)

Access: Read-only

locIPWho

Provides the IP address of the device from which this interface received its IP address.

Syntax: Network address

Access: Read-only

End of Table

IP Routing Table

The local IP routing table, lipRoutingTable, contains the following three variables: locRtMask, locRtCount, and locRtUses. 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 Table 6, for the route with the destination IP address of 131.104.111.1 the routing table network mask is 255.255.255.0. The number of parallel routes within the routing table is 3, and the route was used in a forwarding operation two times.

IP Routing

ipRouteDest	locRtMask	locRtCount	locRtUses
131.104.111.1	255.255.255.0	3	2
133.45.244.245	255.255.255.0	1	1

locRtCount

Provides the number of parallel routes within the routing table.

Syntax: Integer

Access: Read-only

locRtMask

Provides the routing table network mask. For example, 255.255.255.0.

Syntax: Network address

Access: Read-only

locRtUses

Provides the number of times the route was used in a forward operation.

Syntax: Integer

Access: Read-only

End of Table

actLostByts

Provides the total number of bytes of lost IP packets.

Syntax: Integer

Access: Read-only

actLostPkts

Provides the number of IP packets that were lost due to memory limitations.

Syntax: Integer

Access: Read-only

actThresh

Provides the threshold of IP accounting records in use before IP traffic will be discarded.

Syntax: Integer

Access: Read-only

IP Checkpoint Accounting Group

IP accounting records the number of bytes and packets switched through the system on a source and destination IP address basis. These variables provide much of the internetwork statistics that can be analyzed to improve network performance.

The Cisco router maintains two accounting databases: an active database and a checkpoint database. The router takes a snapshot of the running, or active, database, and copies it into the checkpoint database. In this manner, a Network Management System (NMS) can use checkpoint MIB variables to analyze data that is stable.

IP Checkpoint Accounting Table

The local IP checkpoint accounting table, lipCkAccountingTable, includes the following four related variables: ckactSrc, ckactDst, ckactPkts, and ckactByts. The index for this table is ckacSrc and ckactDst. For example, in Table 7, the source host address is 131.24.35.248. The destination host address is 138.32.28.245. Fifty IP packets and 400 bytes of data have been sent between the source and destination address.

IP Checkpoint Accounting

ckacSrc	ckactDst	ckactPkts	ckactByts
131.24.35.248	138.32.28.245	50	400
123.34.216.244	124.45.222.246	60	480

ckactByts

Provides the total number of bytes in IP packets from source to destination in the checkpoint matrix.

Syntax: Integer

Access: Read-only

ckactDst

Provides the IP destination address of the host receiving the IP packets. The address is listed in the checkpoint traffic matrix.

Syntax: Network address

Access: Read-only

ckactPkts

Provides the number of IP packets sent from the source to the destination address in the checkpoint matrix.

Syntax: Integer

Access: Read-only

ckactSrc

Provides the IP source address of the host sending the IP packets. The address is listed in the checkpoint traffic matrix.

Syntax: Network address

Access: Read-only

End of Table

actCheckPoint

Activates a checkpoint database. This variable must be read and then set to the same value that was read. The value read and then set will be incremented after a successful set request.

Syntax: Integer

Access: Read-write

ckactAge

Provides information on how long ago the data was first stored in the checkpoint matrix.

Syntax: TimeTicks

Access: Read-only

ipNoaccess

Provides the total number of packets dropped due to access control failure.

Syntax: Counter

Access: Read-only

System Group

The variables described in this section are system-wide and apply to all Cisco Systems products.

Basic

The following variables pertain to basic information such as system software description and version number, host name, domain name, and number of bytes of free memory in the managed device.

authAddr

Contains the IP address of the device causing the last Simple Network Management Protocol (SNMP) authorization failure. The device did not have the correct community string for the host it was attempting to reach.

Syntax: Network address

Access: Read-only

bootHost

Contains the IP address of the host that supplied the software currently running on the managed device.

Syntax: Network address

Access: Read-only

domainName

The domain portion of the domain name of the host.

Syntax: Display string

Access: Read-only

freeMem

Provides the number of bytes of free memory available in the managed device.

Syntax: Integer

Access: Read-only

hostName

Represents the name of the host in printable ASCII characters.

Syntax: Display string

Access: Read-only

ping

Setting the packet internet groper (ping) variable results in an echo request packet being sent to an address, and then awaiting a reply. Results from this echo protocol can help in evaluating the path-to-host reliability, delays over the path, and whether the host can be reached or is functioning. The ping variable can be used on interfaces running the IP or AppleTalk protocols.

The instance identifier for the ping object is
protocol. address.count.size.timeout, where the protocol can be either
1 for IP or 2 for AppleTalk. The address is an IP address. The count is the number of echo requests to send. The size is the bytes in each echo request packet. Timeout is the number of seconds to wait for a reply to each echo request.

Syntax: Integer

Access: Read-write

romId

Contains a printable octet string that contains the system bootstrap description and version identification.

Syntax: Display string

Access: Read-only

whyReload

Contains a printable octet string that contains the reason why the system was last restarted.

Syntax: Display string

Access: Read-only

Buffer

The following variables are used to monitor the amount and type of buffer space available within a managed device. Buffers are blocks of memory used to hold network packets. There are five types of buffers based on size: small, middle, big, large, and huge. There are several pools of different sized buffers. These pools grow and shrink based upon demand. Some buffers are temporary and are created and destroyed as warranted. Others are permanently allocated.

Basic

Two basic buffer variables are bufferFail and bufferNoMem.

bufferFail

Contains the total number of allocation requests that have failed due to lack of any free buffers.

Syntax: Integer

Access: Read-only

bufferNoMem

Counts the number of failures due to a lack of memory to create a new buffer.

Syntax: Integer

Access: Read-only

Buffer Elements

Buffer elements are blocks of memory used in internal operating system queues.

bufferElCreate

Contains the count of new buffer elements created for the managed device.

Syntax: Integer

Access: Read-only

bufferElFree

Contains the number of buffer elements that are not currently allocated and are available for use in the managed device.

Syntax: Integer

Access: Read-only

bufferElHit

Contains the count of successful attempts to allocate a buffer element when needed.

Syntax: Integer

Access: Read-only

bufferElMax

Contains the maximum number of buffer elements the managed device can have.

Syntax: Integer

Access: Read-only

bufferElMiss

Contains the count of allocation attempts that failed because there were no buffer elements available.

Syntax: Integer

Access: Read-only

Small Buffers

Small buffer sizes are configurable.

bufferSmCreate

Contains the number of small buffers created in the managed device.

Syntax: Integer

Access: Read-only

bufferSmFree

Contains the number of small buffers that are currently available to the managed device.

Syntax: Integer

Access: Read-only

bufferSmHit

Contains the count of successful attempts to allocate a small buffer when needed.

Syntax: Integer

Access: Read-only

bufferSmMax

Contains the maximum number of small buffers that can be allocated to the managed device.

Syntax: Integer

Access: Read-only

bufferSmMiss

Contains the count of allocation attempts that failed because there were no small buffers available.

Syntax: Integer

Access: Read-only

bufferSmSize

Provides the size (in bytes) of small buffers.

Syntax: Integer

Access: Read-only

bufferSmTotal

Provides the total number of small buffers allocated to the managed device.

Syntax: Integer

Access: Read-only

bufferSmTrim

Contains the small buffers that have been destroyed in the managed device.

Syntax: Integer

Access: Read-only

Middle Buffers

Middle buffer sizes are configurable.

bufferMdCreate

Contains the number of middle buffers created in the managed device.

Syntax: Integer

Access: Read-only

bufferMdFree

Contains the number of middle buffers that are currently available to the managed device.

Syntax: Integer

Access: Read-only

bufferMdHit

Contains the count of successful attempts to allocate a middle buffer when needed.

Syntax: Integer

Access: Read-only

bufferMdMax

Contains the maximum number of middle buffers that can be allocated to the managed device.

Syntax: Integer

Access: Read-only

bufferMdMiss

Contains the count of allocation attempts that failed because there were no middle buffers available.

Syntax: Integer

Access: Read-only

bufferMdSize

Provides the size (in bytes) of middle buffers.

Syntax: Integer

Access: Read-only

bufferMdTotal

Provides the total number of middle buffers allocated to the managed device.

Syntax: Integer

Access: Read-only

bufferMdTrim

Contains the middle buffers that have been destroyed in the managed device.

Syntax: Integer

Access: Read-only

Big Buffers

Big buffer sizes are configurable.

bufferBgCreate

Contains the number of big buffers created in the managed device.

Syntax: Integer

Access: Read-only

bufferBgFree

Contains the number of big buffers that are currently available to the managed device.

Syntax: Integer

Access: Read-only

bufferBgHit

Contains the count of successful attempts to allocate a big buffer when needed.

Syntax: Integer

Access: Read-only

bufferBgMax

Contains the maximum number of big buffers that can be allocated to the managed device.

Syntax: Integer

Access: Read-only

bufferBgMiss

Contains the count of allocation attempts that failed because there were no big buffers available.

Syntax: Integer

Access: Read-only

bufferBgSize

Provides the size (in bytes) of big buffers.

Syntax: Integer

Access: Read-only

bufferBgTotal

Provides the total number of big buffers allocated to the managed device.

Syntax: Integer

Access: Read-only

bufferBgTrim

Contains the big buffers that have been destroyed in the managed device.

Syntax: Integer

Access: Read-only

Large Buffers

Large buffer sizes are configurable.

bufferLgCreate

Contains the number of large buffers created in the managed device.

Syntax: Integer

Access: Read-only

bufferLgFree

Contains the number of large buffers that are currently available to the managed device.

Syntax: Integer

Access: Read-only

bufferLgHit

Contains the count of successful attempts to allocate a large buffer when needed.

Syntax: Integer

Access: Read-only

bufferLgMax

Contains the maximum number of large buffers that can be allocated to the managed device.

Syntax: Integer

Access: Read-only

bufferLgMiss

Contains the count of allocation attempts that failed because there were no large buffers available.

Syntax: Integer

Access: Read-only

bufferLgSize

Provides the size (in bytes) of large buffers.

Syntax: Integer

Access: Read-only

bufferLgTotal

Provides the total number of large buffers allocated to the managed device.

Syntax: Integer

Access: Read-only

bufferLgTrim

Contains the large buffers that have been destroyed in the managed device.

Syntax: Integer

Access: Read-only

Huge Buffers

Huge buffer sizes are configurable.

bufferHgCreate

Contains the number of huge buffers created in the managed device.

Syntax: Integer

Access: Read-only

bufferHgFree

Contains the number of huge buffers that are currently available to the managed device.

Syntax: Integer

Access: Read-only

bufferHgHit

Contains the count of successful attempts to allocate a huge buffer when needed.

Syntax: Integer

Access: Read-only

bufferHgMax

Contains the maximum number of huge buffers that can be allocated to the managed device.

Syntax: Integer

Access: Read-only

bufferHgMiss

Contains the count of allocation attempts that failed because there were no huge buffers available.

Syntax: Integer

Access: Read-only

bufferHgSize

Provides the size (in bytes) of huge buffers.

Syntax: Integer

Access: Read-only

bufferHgTotal

Provides the total number of huge buffers allocated to the managed device.

Syntax: Integer

Access: Read-only

bufferHgTrim

Contains the huge buffers that have been destroyed in the managed device.

Syntax: Integer

Access: Read-only

CPU Utilization

The following variables provide statistics on the CPU utilization of a device.

avgBusy1

Provides a cumulative average of the CPU usage percentage over a
one-minute period.

Syntax: Integer

Access: Read-only

avgBusy5

Provides a cumulative average of the CPU usage percentage over a
five-minute period.

Syntax: Integer

Access: Read-only

busyPer

Provides the percentage of CPU usage over the first five-second period in the scheduler. The scheduler determines which process or task takes priority over another and triggers them accordingly.

Syntax: Integer

Access: Read-only

ciscoContactInfo

Provides Cisco's name and address for reference purposes.

Syntax: Display string

Access: Read-only

Environmental Monitor Card

The environmental monitor card is provided only with the Cisco AGS+ router. The following variables are used to poll and display power supply voltage and air temperature (in Celsius) in an AGS+ to help prevent system problems.

envBurnDate

Provides the date of the calibration of the environmental monitor card.

Syntax: Display string

Access: Read-only

envFirmVersion

Provides the firmware level of the environmental monitor card.

Syntax: Display string

Access: Read-only

envPresent

Checks to see if there is an environmental monitor card in a router.

Syntax: Integer

Access: Read-only

envSerialNumber

Provides the serial number of the environmental monitor card.

Syntax: Display string

Access: Read-only

envTechnicianID

Provides the technician ID for the environmental monitor card.

Syntax: Display string

Access: Read-only

envTestPt1Descr

Test point 1 is the temperature of air entering the AGS+ router.

Syntax: Display string

Access: Read-only

envTestPt1last

Provides the temperature of air entering the AGS+ router when the last shutdown occurred.

Syntax: Integer

Access: Read-only

envTestPt1MarginVal

Provides warning and fatal threshold values for the AGS+ router's internal intake air.

Syntax: Integer

Access: Read-only

envTestPt1Measure

Provides the current temperature of air entering the AGS+ router.

Syntax: Display string

Access: Read-only

envTestPt1warn

Indicates whether or not the air temperature entering the AGS+ router is at warning level.

Syntax: Integer (1=warning, 2=no warning)

Access: Read-only

envTestPt2Descr

Test point 2 is the temperature of air leaving the router.

Syntax: Display string

Access: Read-only

envTestPt2last

Provides the temperature of air leaving the AGS+ router when the last shutdown occurred.

Syntax: Integer

Access: Read-only

envTestPt2MarginVal

Provides the fatal threshold value for the AGS+ router's exhaust air flow.

Syntax: Integer

Access: Read-only

envTestPt2Measure

Provides the temperature of the AGS+ router's exhaust air flow.

Syntax: Integer

Access: Read-only

envTestPt2warn

Indicates whether or not the temperature of air flow leaving the AGS+ router is at warning level.

Syntax: Integer (1=warning, 2=no warning)

Access: Read-only

envTestPt3Descr

Test point 3 is the +5 volt line on the router.

Syntax: Display string

Access: Read-only

envTestPt3last

Provides the value of the +5 volt line when the last shutdown occurred.

Syntax: Integer

Access: Read-only

envTestPt3MarginPercent

Provides the warning and fatal thresholds for the +5 volt line to the power supply on the AGS+ router. The warning threshold is +/- 5% above or below +5 volts. The fatal threshold at which the router shuts down is
+/- 10% above or below +5 volts.

Syntax: Integer

Access: Read-only

envTestPt3Measure

Provides the current value for the +5 volt line to the power supply on the AGS+ router. The value is expressed in millivolts.

Syntax: Integer

Access: Read-only

envTestPt3warn

Indicates whether or not the +5 volt line to the power supply is at warning level. The warning threshold is +/- 5% above or below +5 volts.

Syntax: Integer (1=warning, 2=no warning)

Access: Read-only

envTestPt4Descr

Test point 4 is the +12 volt line to the router's power supply.

Syntax: Display string

Access: Read-only

envTestPt4last

Provides the value of the +12 volt line when the last shutdown occurred.

Syntax: Integer

Access: Read-only

envTestPt4MarginPercent

Provides the warning and fatal thresholds for the +12 volt line to the power supply on the AGS+ router. The warning threshold is +/- 10% above or below +12 volts. The fatal threshold at which the router shuts down is +/- 15% above or below +12 volts.

Syntax: Integer

Access: Read-only

envTestPt4Measure

Provides the current value (in millivolts) of the +12 volt line to the router's power supply.

Syntax: Integer

Access: Read-only

envTestPt4warn

Indicates whether or not the +12 volt line to the power supply is at warning level. The warning threshold is +/- 10% above or below
+12 volts.

Syntax: Integer (1=warning, 2=no warning)

Access: Read-only

envTestPt5Descr

Test point 5 is the -12 volt line to the router's power supply.

Syntax: Display string

Access: Read-only

envTestPt5last

Provides the value of the -12 volt line when the last shutdown occurred.

Syntax: Integer

Access: Read-only

envTestPt5MarginPercent

Provides the warning and fatal thresholds for the -12 volt line to the power supply on the AGS+ router. The warning threshold is +/- 10% above or below -12 volts. The fatal threshold at which the router shuts down is
+/- 15% above or below -12 volts.

Syntax: Integer

Access: Read-only

envTestPt5Measure

Provides the current value (in millivolts) of the -12 volt line to the router's power supply.

Syntax: Integer

Access: Read-only

envTestPt5warn

Indicates whether or not the -12 volt line to the power supply on the AGS+ router is at warning level. The warning threshold is +/- 10% above or below -12 volts.

Syntax: Integer (1=warning, 2=no warning)

Access: Read-only

envTestPt6Descr

Test point 6 is the -5 volt line to the AGS+ router's power supply.

Syntax: Display string

Access: Read-only

envTestPt6last

Provides the value of the -5 volt line to the AGS+ router's power supply when the last shutdown occurred.

Syntax: Integer

Access: Read-only

envTestPt6MarginPercent

Provides the warning and fatal thresholds for the -12 volt line to the power supply on the AGS+ router. The warning threshold is +/- 5% above or below -5 volts. The fatal threshold at which the router shuts down is
+/- 10% above or below -5 volts.

Syntax: Integer

Access: Read-only

envTestPt6Measure

Provides the current value (in millivolts) of the -5 volt line to the AGS+ router's power supply.

Syntax: Integer

Access: Read-only

envTestPt6warn

Indicates whether or not the -5 volt line to the power supply on the AGS+ router is at warning level. The warning threshold is +/- 5% above or below -5 volts.

Syntax: Integer (1=warning, 2=no warning)

Access: Read-only

envType

Provides the type of environmental card.

Syntax: Display string

Access: Read-only

Host Configuration File

The following variables are used to monitor and set host configuration file information.

hostConfigAddr

Provides the address of the host that provided the host configuration file. The host configuration file contains commands that apply to one network server in particular.

Syntax: Network address

Access: Read-only

hostConfigName

Provides the name of the host configuration file.The default host configuration filename is host-config.

Syntax: Display string

Access: Read-only

hostConfigProto

Provides the protocol that supplied the host configuration file.

Syntax: Integer

Access: Read-only

hostConfigSet

Allows the Network Management System (NMS) to load a new host configuration file via Trivial File Transfer Protocol (TFTP) onto the managed device.

Syntax: Display string

Access: Write-only

Network Configuration File

The following variables begin are used to monitor and set network configuration file information.

netConfigAddr

Provides the address of the host that supplied the network configuration file for the managed device. The network configuration file contains commands that apply to all network servers and terminal servers
on a network.

Syntax: Network address

Access: Read-only

netConfigName

Provides the name of the network configuration file that resides on the managed device. The default name of this file is network-confg.

Syntax: Display string

Access: Read-only

netConfigProto

Provides the protocol that supplied the network configuration file.

Syntax: Integer

Access: Read-only

netConfigSet

Loads a new network configuration file via Trivial File Transfer Protocol (TFTP) onto the managed device.

Syntax: Display string

Access: Write-only

System Configuration

The following variables are used to monitor and set system-wide parameters.

sysClearARP

Performs a clearing of the entire Address Resolution Protocol (ARP) cache and Internet Protocol (IP) route cache. The ARP provides dynamic mapping between IP addresses and Ethernet addresses. The ARP cache table keeps a record of these mappings and can be cleared for maintenance purposes.

Syntax: Integer

Access: Write-only

sysClearInt

Clears an interface that is given IfIndex as a value. To clear an interface, take the ifIndex for the interface and set this variable to that value. For example, to clear the interface Ethernet0 which has an ifIndex of 4, set sysClearInt to 4.

Syntax: Integer

Access: Write-only

sysConfigAddr

Provides the address of the host that supplied the system boot image for the managed device. New versions of software can be downloaded over the network with boot image files. The new file takes effect the next time the managed device is reloaded.

Syntax: Network address

Access: Read-only

sysConfigName

Provides the name of the system boot image file. New versions of software can be downloaded over the network with boot image files. The new file takes effect the next time the managed device is reloaded.

Syntax: Display string

Access: Read-only

sysConfigProto

Provides the protocol type that supplied the system boot image.

Syntax: Integer

Access: Read-only

writeMem

Writes the current (running) configuration into nonvolatile memory where it can be stored and retained even if the router is reloaded. Erase configuration memory if 0.

Syntax: Integer

Access: Write-only

writeNet

Sends a copy of the current configuration via Trivial File Transfer Protocol (TFTP) to a remote host. Once it is stored on the host, the configuration file can be edited and retrieved by other network entities.

Syntax: Display string

Access: Write-only

Terminal Server Group

These variables can be applied to terminal servers. This group contains terminal-server specific information on a per line basis, such as line status, line type, line speed, type of flow control, and type of modem.

---

Note The Cisco MIB continues to refer to what is now called the communication server as the terminal server. Variables begin with the letters "ts." Therefore, although the current name is "communication server," this document must refer to it as the terminal server.

---

tsLines

Number of physical lines on the device.

Syntax: Integer

Access: Read-only

Terminal Server Line Table

The local terminal server line table, ltsLineTable, contains all of the variables described in this section. The index to this table is the number of the terminal server line. If there are n number of terminal lines associated with the device, there will be n rows in the table. See Table 8.

Terminal Server Line

Line Number	tsLineActive	tsLineType	etc.
1	Contains all of the variables described in "Terminal Server Line Table."
2
etc.

tsLineActive

Indicates whether or not this line is active.

Syntax: Integer (1=active, 2=not active)

Access: Read-only

tsLineAutobaud

Indicates whether or not the line is set to autobaud detection so that it can adapt to the rate at which data is being sent to it.

Syntax: Integer (1=autobaud, 2=not autobaud)

Access: Read-only

tsLineEsc

Indicates what is used to represent the escape (Esc) character. The escape character allows a user to break out of active sessions.

Syntax: Display string

Access: Read-only

tsLineFlow

Indicates the type of flow control the line is using. The flow can be controlled from software or hardware. Input indicates the flow control is coming from the device to the terminal server. Output indicates flow control is provided by the terminal server.

Syntax: Integer

Access: Read-only

The possible integer values are as follows:

1=unknown
2=none
3=software-input
4=software-output
5=software-both
6=hardware-input
7=hardware-output
8=hardware-both

tsLineLoc

Describes the line's physical location.

Syntax: Display string

Access: Read-only

tsLineModem

Describes the type of modem control the line is using.

Syntax: Integer

Access: Read-only

The possible integer values are as follows:

1=unknown
2=none
3=call-in
4=call-out
5=cts-required
6=rs-is-cd

Call-in indicates dial-in modems that use the status of data terminal ready (DTR) to determine whether or not answer an incoming call.

Call-out indicates modems that raise data terminal ready (DTR) to see
if clear to send (CTS) becomes high as an indication that the host has noticed its signal.

Cts-required indicates the form of modem control that requires CTS to be high throughout the use of the line.

Rs-is-cd is used for lines with high-speed modems. The modem answers the call if DTR is high, uses its carrier detect (CD) signal to reflect the carrier presence, and has its CD signal wired to the terminal server's
ring input.

tsLineNoise

Provides the count of garbage characters received while the line is inactive.

Syntax: Integer

Access: Read-only

tsLineNses

Indicates the number of current sessions on the line.

Syntax: Integer

Access: Read-only

tsLineRotary

This variable specifies the number of the rotary group to which the line belongs. If the first line in a rotary group is busy, a connection can be made to the next free line.

Syntax: Integer

Access: Read-only

tsLineScrlen

Provides the length (in lines) of the screen of the terminal attached to the line.

Syntax: Integer

Access: Read-only

tsLineScrwid

Provides the width (in characters) of the screen of the terminal attached to the line.

Syntax: Integer

Access: Read-only

tsLineSestmo

Specifies the interval (in seconds) for closing the connection when there is no input or output traffic during a session.

Syntax: Integer

Access: Read-only

tsLineSpeedin

Indicates the input speed at which the line is running.

Syntax: Integer

Access: Read-only

tsLineSpeedout

Indicates the output speed at which the line is running.

Syntax: Integer

Access: Read-only

tsLineTerm

Describes the line's terminal type.

Syntax: Display string

Access: Read-only

tsLineTmo

Specifies the interval (in seconds) for closing the connection when there is no input or output traffic on the line.

Syntax: Integer

Access: Read-only

tsLineType

Describes the terminal line type.

Syntax: Integer

Access: Read-only

The possible integer values are as follows:

1=unknown
2=console
3=terminal
4=line-printer
5=virtual-terminal
6=auxiliary

tsLineUser

Provides Terminal Access Controller Access System (TACACS) username and whether or not TACACS is enabled on this line. TACACS servers provide security for accessing terminals remotely.

Syntax: Display string

Access: Read-only

tsLineUses

Indicates the number of times a connection has been made to or from
this line.

Syntax: Integer

Access: Read-only

End of Table

Terminal Server Line Session Table

The terminal server line session table, ltsLineSessionTable, contains the following six variables: tslineSesType, tslineSesDir, tslineSesAddr, tslineSesName, tslineSesCur, and tslineSesIdle.

For simplification, Table 9 shows values for three of the variables contained in the terminal server line session table. The index to the table is the session number and line number. Line 1 in the first session illustrates a Telnet connection. The session was started by the terminal. The remote host for this session is located at the IP address of 131.38.141.244.

Terminal Server Line Session

Session # Line #	tslineType	tslineDir	tslineSesAddr
1,1	5	3	131.38.141.244
2,4	3	2	138.121.128.243

tslineSesAddr

Provides the address of the remote host for this session.

Syntax: Network address

Access: Read-only

tslineSesCur

Indicates whether or not this session is currently active.

Syntax: Integer (1=active, 2=not active)

Access: Read-only

tslineSesDir

Indicates whether this session was started by another device (incoming) or by the terminal (outgoing).

Syntax: Integer

Access: Read-only

The possible integer values are as follows:

1=unknown
2=incoming
3=outgoing

tslineSesIdle

Indicates the amount of time (in seconds) that this session has been idle.

Syntax: Integer

Access: Read-only

tslineSesName

Provides the name of the remote host for this session.

Syntax: Display string

Access: Read-only

tslineSesType

Describes the type of session that is currently active.

Syntax: Integer

Access: Read-only

The possible integer values are as follows:

1= Unknown
2= X.3 Packet Assembler/Disassembler (PAD)
3= Stream (enables a raw TCP stream with no Telnet control sequences)
4= Rlogin (for making remote connection to a host--part of TCP/IP)
5= Telnet (for making remote connection to a host)--UNIX protocol)
6= Transmission Control Protocol (TCP)
7= Local Area Transport (LAT)
8= Maintenance Operation Protocol (MOP)
9= Serial Line Internet Protocol (SLIP)
10= Xremote (provides support for X Windows over a serial line)

End of Table

Terminal Server Messages

The following variables pertain to terminal server message parameters.

tsMsgDuration

Sets the length of time (in milliseconds) allocated to reissue a message. The minimum nonzero setting is 10000.0. A setting of 0 will not repeat the message.

Syntax: Integer

Access: Read-write

tsMsgIntervaltim

Sets the interval (in milliseconds) that occurs between re-issues of the same message. The minimum (nonzero) setting for this interval is 10000. 0 milliseconds. If set to 10000.0, the intervals will become more frequent as the message duration gets close to expiring. For example, 2 hours,
1 hour, 30 minutes, 5 minutes, and 1 minute.

Syntax: Integer

Access: Read-write

tsMsgSend

Determines what action to take after the message has been sent.

Syntax: Integer

Access: Read-write

The possible integer values are as follows:

1=nothing
2=reload
3=message done
4=abort

tsMsgText

Sets the text of the message. Up to 256 characters can be included in the message.

Syntax: Display string

Access: Read-write

tsMsgTmpBanner

Determines whether or not to use the message text as a temporary banner.

Syntax: Integer (1=no, 2=yes, in addition to the regular banner)

Access: Read-write

tsMsgTtyLine

Selects the TTY line to which you want the message sent. Setting this variable to -1 will send the message to all TTY lines.

Syntax: Integer

Access: Read-write

Transmission Control Protocol (TCP) Group

These variables can be applied to Cisco products running the Transmission Control Protocol (TCP).These variables provide statistics on the number of input and output bytes and packets for TCP connections.

TCP Connection Table

The TCP connection table, ltcpConnTable, contains the following five variables: loctcpConnInBytes, loctcpConnOutBytes, loctcpConnInPkts, loctcpConnOutPkts, and loctcpConnElapsed.

The index to this table includes the local host address and port number and the remote host address and port number for each TCP connection that is active for the device. These values are represented by tcpConnLocalAddress, tcpConnLocalPort, tcpConnRemAddress, and tcpConRemPort.

For n number of TCP connections, there are n rows in the table. The value n can change at any time if another TCP connection opens, or if an existing TCP connection closes.

In Table 10, TCP A represents the first TCP connection in the table.
The TCP A connection shows 100 input bytes, 100 output bytes, 85 input packets, 85 output packets for the connection. The connection has been established for 60 seconds, or 6000 TimeTicks.

TCP Connection

	InBytes	OutBytes	InPkts	OutPkts	Elapsed
TCP A	100	100	85	85	6000
TCP B	200	130	90	100	4500
TCP C	300	250	100	95	9000

loctcpConnElapsed

The variable provides the length of time that the TCP connection has been established.

Syntax: TimeTicks

Access: Read-only

loctcpConnInBytes

Provides the number of input bytes for the TCP connection.

Syntax: Integer

Access: Read-only

loctcpConnInPkts

Provides the number of input packets for the TCP connection.

Syntax: Integer

Access: Read-only

loctcpConnOutBytes

Provides the number of output bytes for the TCP connection.

Syntax: Integer

Access: Read-only

loctcpConnOutPkts

Provides the number of output packets for the TCP connection.

Syntax: Integer

Access: Read-only

End of Table

Temporary Variables

This section is equivalent to the experimental space defined by the Structure of Management Information (SMI). It contains variables that are useful to have but are beyond Cisco's ability to control and maintain. Support for these variables can change with each Cisco Systems software release.

The temporary variables section includes the following group of variables:

• AppleTalk

• DECnet

• Novell

• Virtual Network System (VINES)

• Xerox Network System (XNS)

AppleTalk Group

Variables in this group can be used with all Cisco products running the AppleTalk protocol. These variables provide such information 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.

atArpprobe

Indicates the total number of input AppleTalk Address Resolution Protocol (ARP) probe packets.

Syntax: Integer

Access: Read-only

atArpreply

Indicates the total number of AppleTalk Address Resolution Protocol (ARP) reply packets output.

Syntax: Integer

Access: Read-only

atArpreq

Indicates the total number of input AppleTalk Address Resolution Protocol (ARP) request packets.

Syntax: Integer

Access: Read-only

atAtp

Indicates the total number of AppleTalk Transaction Protocol (ATP) packets received.

Syntax: Integer

Access: Read-only

atBcastin

Indicates the total number of AppleTalk input broadcast packets.

Syntax: Integer

Access: Read-only

atBcastout

Indicates the total number of AppleTalk output broadcast packets.

Syntax: Integer

Access: Read-only

atChksum

Indicates the total number of AppleTalk input packets with checksum errors.

Syntax: Integer

Access: Read-only

atDdpbad

Indicates the total number of illegal sized AppleTalk Datagram Delivery Protocol (DDP) packets received.

Syntax: Integer

Access: Read-only

atDdplong

Indicates the total number of long AppleTalk Datagram Delivery Protocol (DDP) packets received.

Syntax: Integer

Access: Read-only

atDdpshort

Indicates the total number of short AppleTalk Datagram Delivery Protocol (DDP) packets received.

Syntax: Integer

Access: Read-only

atEcho

Indicates the total number of AppleTalk echo packets received.

Syntax: Integer

Access: Read-only

atEchoill

Indicates the total number of illegal AppleTalk echo packets received.

Syntax: Integer

Access: Read-only

atForward

Indicates the total number of AppleTalk packets forwarded.

Syntax: Integer

Access: Read-only

atHopcnt

Indicates the total number of AppleTalk input packets that have exceeded the maximum hop count.

Syntax: Integer

Access: Read-only

atInmult

Indicates the total number of AppleTalk input packets with multicast addresses.

Syntax: Integer

Access: Read-only

atInput

Indicates the total number of input AppleTalk packets.

Syntax: Integer

Access: Read-only

atLocal

Indicates the total number of AppleTalk input packets for this host.

Syntax: Integer

Access: Read-only

atNbpin

Indicates the total number of AppleTalk Name Binding Protocol (NBP) packets received.

Syntax: Integer

Access: Read-only

atNbpout

Indicates the total number of AppleTalk Name Binding Protocol (NBP) packets sent.

Syntax: Integer

Access: Read-only

atNoaccess

Indicates the total number of AppleTalk packets dropped due to access control.

Syntax: Integer

Access: Read-only

atNobuffer

Indicates the total number of AppleTalk packets lost due to no memory.

Syntax: Integer

Access: Read-only

atNoencap

Indicates the total number of AppleTalk packets that were dropped because they could not be encapsulated.

Syntax: Integer

Access: Read-only

atNoroute

Indicates the total count of number of AppleTalk packets dropped because the router did not know where to forward them.

Syntax: Integer

Access: Read-only

atNotgate

Indicates the total number of AppleTalk input packets received while AppleTalk routing was not enabled.

Syntax: Integer

Access: Read-only

atOutput

Indicates the total number of AppleTalk output packets.

Syntax: Integer

Access: Read-only

atRtmpin

Indicates the total number of AppleTalk Routing Table Maintenance Protocol (RTMP) packets received.

Syntax: Integer

Access: Read-only

atRtmpout

Indicates the total number of AppleTalk Routing Table Maintenance Protocol (RTMP) packets sent.

Syntax: Integer

Access: Read-only

atUnknown

Indicates the total number of unknown AppleTalk input packets.

Syntax: Integer

Access: Read-only

atZipin

Indicates the total number of AppleTalk Zone Information Protocol (ZIP) packets received.

Syntax: Integer

Access: Read-only

atZipout

Indicates the total number of AppleTalk Zone Information Protocol (ZIP) packets sent.

Syntax: Integer

Access: Read-only

DECnet Group

This section describes the Cisco MIB variables pertaining to monitoring and managing a device running the DECnet protocol. These variables gather information, such as hop count, host name, total packets received and sent, and number of packets with header errors.

---

Note The terms "Level 1" and "Level 2" are used often with these variables. Level 1 routers can communicate with end nodes and with other Level 1 routers in an area. Level 2 routers communicate with Level 1 routers in the same area and with Level 2 routers in different areas.The term "hellos" is also used. Hosts learn each other's addresses by listening to host hello messages. Hosts learn about nearby routers by listening to router hello messages.

---

dnBadhello

Provides the total number of received bad hello messages.

Syntax: Integer

Access: Read-only

dnBadlevel1

Provides the total number of bad Level 1 routing packets that have been received.

Syntax: Integer

Access: Read-only

dnBigaddr

Provides the total number of addresses that are too large.

Syntax: Integer

Access: Read-only

dnDatas

Provides the total number of received data packets.

Syntax: Integer

Access: Read-only

dnFormaterr

Provides the total number of DECnet packets received with header errors.

Syntax: Integer

Access: Read-only

dnForward

Provides the total count of DECnet packets that have been forwarded.

Syntax: Integer

Access: Read-only

dnHellos

Provides the total number of hello messages received.

Syntax: Integer

Access: Read-only

dnHellosent

Indicates the total number of output hello messages.

Syntax: Integer

Access: Read-only

dnLevel1s

Provides the total number of Level 1 routing packets received.

Syntax: Integer

Access: Read-only

dnLevel1sent

Indicates the total number of Level 1 routing packets sent.

Syntax: Integer

Access: Read-only

dnLevel2s

Indicates the total number of Level 2 routing packets received.

Syntax: Integer

Access: Read-only

dnLevel2sent

Indicates the total number of Level 2 routing packets sent.

Syntax: Integer

Access: Read-only

dnNoaccess

Provides the total number of packets dropped due to access control failure.

Syntax: Integer

Access: Read-only

dnNoencap

Provides the total number of packets that were dropped because they could not be encapsulated.

Syntax: Integer

Access: Read-only

dnNomemory

Indicates the total number of transactions denied due to lack of memory.

Syntax: Integer

Access: Read-only

dnNoroute

Provides the total number of packets that were dropped because the router did not know where to forward them.

Syntax: Integer

Access: Read-only

dnNotgateway

Provides the total number of packets that were received while not routing DECnet.

Syntax: Integer

Access: Read-only

dnNotimp

Provides the total number of unknown control packets received.

Syntax: Integer

Access: Read-only

dnNotlong

Provides the total number of received packets not in the long DECnet format. This number should always be zero.

Syntax: Integer

Access: Read-only

dnNovector

Indicates the total number of missing routing vectors. Occurs when a packet is received for which there is no entry in the routing table.

Syntax: Integer

Access: Read-only

dnOtherhello

Provides the total number of hello messages received from another area by a Level 1 router.

Syntax: Integer

Access: Read-only

dnOtherlevel1

Provides the total number of Level 1 routing packets received from another area.

Syntax: Integer

Access: Read-only

dnOtherlevel2

Provides the total number of Level 2 routing packets that have been received from another area.

Syntax: Integer

Access: Read-only

dnReceived

Provides the count of total DECnet packets received.

Syntax: Integer

Access: Read-only

dnToomanyhops

Provides the total number of packets received that exceeded the maximum hop count set for this device and have been discarded.

Syntax: Integer

Access: Read-only

DECnet Area Routing Table

The DECnet area routing table, dnAreaTable, includes the following seven variables: dnArea, dnACost, dnAHop, dnAIfIndex, dnANextHop, dnAAge, and dnAPrio. The index for this table is the DECnet area, or dnArea.If there are n number of areas for the device, there will be n rows in the table.

For example, in Table 11, the DECnet area is 44, the cost is 3, and the maximum number of hops allowed is 2. The interface used to get to area 44 is number 1, the address for the next hop is 46.5, the routing table was updated 30 seconds ago, and the next hop area is prioritized as 1.

DECnet Area Routing

dn Area	dnA Cost	dnA Hop	dnA IfIndex	dnA Next Hop	dnA Age	dnA Prio
44	3	2	1	46.5	30	1
24	60	4	2	24.7	12	2
6	17	2	3	6.4	60	3

dnAAge

Indicates the age (in seconds) of an area route. When a route is used or has been verified as functional, its age is reset to zero. If a route is not used, its age will gradually grow Eventually, routes with large ages are cleared out.

Syntax: Integer

Access: Read-only

dnACost

Indicates the cost of the router's area. The cost value can be an integer from 1 to 63. The cost signifies routing preference. The lower the cost, the better the path.

Syntax: Integer

Access: Read-only

dnAHop

Indicates the maximum number of hops for a route to a distant area that the router will accept.

Syntax: Integer

Access: Read-only

dnAIfIndex

Provides the instance ID of the interface providing the next hop address to the area. A zero denotes self. The DECnet table is indexed by dnArea. For example, dnAIfIndex.5 is the ifIndex for the next hop to DECnet area 5, dnAifIndex.7 is the ifIndex for the next hop to DECnet area 7, and
so on.

If dnAIfIndex.5 is set to the value of 4, then to get to the next hop for DECnet area 5, the router sends the packet via the interface that has an ifIndex of 4.

Syntax: Integer

Access: Read-only

dnANextHop

Provides the DECnet address for the next hop.

Syntax: Octet string

Access: Read-only

dnAPrio

Provides the priority of the next hop router for an area route.

Syntax: Integer

Access: Read-only

dnArea

Indicates the DECnet area for the device.

Syntax: Integer

Access: Read-only

End of Table

DECnet Host Table

The DECnet host table, dnHostTable, contains the following seven variables: dnHost, dnHCost, dnHHop, dnHIfIndex, dnHNextHop, dnHAge, and dnHPrio.

In Table 12, the first DECnet host address in the table is 44.5. Its cost is 3, the number of hops to the host is 4, and the interface number 1 provides the next hop to address 55.6. The route was updated 30 seconds ago and the priority for the next hop is set to 4.

DECnet Host

dnHost	dnHCost	dnHHop	dnHifIndex	dnHNext Hop	dnHAge	dnHPrio
44.5	3	4	1	55.6	30	4
54.6	1	3	2	33.2	20	3
23.2	2	1	3	25.1	60	2

dnHAge

Indicates the age (in seconds) of the route to the host.When a route is used or has been verified as functional, its age is reset to zero. If a route is not used, its age will gradually grow. Eventually, routes with large ages are cleared out.

Syntax: Integer

Access: Read-only

dnHCost

Provides the cost of the path to this device.

Syntax: Integer

Access: Read-only

dnHHop

Provides the number of hops to this device.

Syntax: Integer

Access: Read-only

dnHIfIndex

This variable is provides the index of the interface to the next hop address to the node. 0 denotes self.

Syntax: Integer

Access: Read-only

dnHost

Provides the DECnet node address.

Syntax: Integer

dnHNextHop

Provides the DECnet address of the next hop destination.

Syntax: Octet string

Access: Read-only

dnHPrio

Describes the priority of the next hop router for the node.

Syntax: Integer

Access: Read-only

End of Table

DECnet Interface Table

The DECnet interface table, dnIfTable, contains the dnIfCost variable. The index to this table is ifIndex, or the interface number. If there are n number of interfaces associated with the device, there will be n rows in the table.

For example, in Table 13, interface 1 has a cost of 20, interface 2 has a cost of 31, and so on.

DECnet Interface

Interface Number	dnIfCost
1	20
2	31
3	12

dnIfCost

Indicates the cost of this interface.

Syntax: Integer

Access: Read-only

End of Table

Novell Group

The variables in this group can be used with all Cisco products running the Novell protocol. These variables provide such information as total number of input and output packets, number of packets with errors, number of packets with Service Access Point (SAP) requests and replies.

novellBcastin

Indicates the total number of Novell input broadcast packets.

Syntax: Integer

Access: Read-only

novellBcastout

Indicates the total number of Novell output broadcast packets.

Syntax: Integer

Access: Read-only

novellChksum

Indicates the total number of Novell input packets with checksum errors.

Syntax: Integer

Access: Read-only

novellFormerr

Indicates the total number of Novell input packets with header errors.

Syntax: Integer

Access: Read-only

novellForward

Indicates the total number of Novell packets forwarded.

Syntax: Integer

Access: Read-only

novellHopcnt

Indicates the total number of Novell input packets that have exceeded the maximum hop count.

Syntax: Integer

Access: Read-only

novellInmult

Indicates the total number of Novell input multicast packets.

Syntax: Integer

Access: Read-only

novellInput

Indicates the total number of Novell input packets.

Syntax: Integer

Access: Read-only

novellLocal

Indicates the total number of Novell input packets for this host.

Syntax: Integer

Access: Read-only

novellNoencap

Indicates the total number of Novell packets dropped due to output encapsulation failure.

Syntax: Integer

Access: Read-only

novellNoroute

Indicates the total number of Novell packets dropped because the router did not know where to forward them.

Syntax: Integer

Access: Read-only

novellOutput

Indicates the total number of Novell output packets.

Syntax: Integer

Access: Read-only

novellSapout

Indicates the total number of Novell Service Access Point (SAP) request packets sent.

Syntax: Integer

Access: Read-only

novellSapreply

Indicates the total number of Novell Service Access Point (SAP) reply packets sent.

Syntax: Integer

Access: Read-only

novellSapreqin

Indicates the total number of Novell Service Access Point (SAP) request packets received.

Syntax: Integer

Access: Read-only

novellSapresin

Indicates the total number of Novell Service Access Point (SAP) response packets received.

Syntax: Integer

Access: Read-only

novellUnknown

Indicates the total number of unknown Novell input packets.

Syntax: Integer

Access: Read-only

Virtual Network System (VINES) Group

The variables in this group can be used with all Cisco products running the Banyan Virtual Network System (VINES) protocol. This protocol is derived from the Xerox Network Systems (XNS) protocol. These variables provide information such as total number of input and output packets, number of packets with errors, and number of packets with Internet Control Protocol (ICP) requests and replies.

vinesBcastfwd

Indicates the total number of VINES broadcast packets forwarded.

Syntax: Integer

Access: Read-only

vinesBcastin

Indicates the total number of VINES input broadcast packets.

Syntax: Integer

Access: Read-only

vinesBcastout

Indicates the total number of VINES output broadcast packets.

Syntax: Integer

Access: Read-only

vinesCksumerr

Indicates the total number of VINES input packets with checksum errors.

Syntax: Integer

Access: Read-only

vinesEchoIn

Indicates the total number of VINES echo packets received.

Syntax: Integer

Access: Read-only

vinesEchoOut

Indicates the total number of VINES echo packets generated.

Syntax: Integer

Access: Read-only

vinesEncapsfailed

Indicates the total number of VINES packets dropped because they could not be encapsulated.

Syntax: Integer

Access: Read-only

vinesFormaterror

Indicates the total number of VINES input packets with header errors.

Syntax: Integer

Access: Read-only

vinesForwarded

Indicates the total number of VINES packets forwarded.

Syntax: Integer

Access: Read-only

vinesHopcount

Indicates the total number of VINES input packets that have exceeded the maximum hop count.

Syntax: Integer

Access: Read-only

vinesIcpIn

Indicates the total number of VINES Internet Control Protocol (ICP) packets received.

Syntax: Integer

Access: Read-only

vinesIcpOut

Indicates the total number of VINES Internet Control Protocol (ICP) packets generated.

Syntax: Integer

Access: Read-only

vinesInput

Indicates the total number of VINES input packets.

Syntax: Integer

Access: Read-only

vinesLocaldest

Indicates the total number of VINES input packets for this host.

Syntax: Integer

Access: Read-only

vinesMacEchoIn

Indicates the total number of VINES Media Access Control (MAC) level echo packets received.

Syntax: Integer

Access: Read-only

vinesMacEchoOut

Indicates the total number of VINES Media Access Control (MAC) level echo packets generated.

Syntax: Integer

Access: Read-only

vinesMetricOut

Indicates the total number of VINES Internet Control Protocol (ICP) metric notification packets generated.

Syntax: Integer

Access: Read-only

vinesOutput

Indicates the total number of VINES output packets.

Syntax: Integer

Access: Read-only

vinesNocharges

Total count of number of VINES broadcast packets not forwarded to all interfaces because the no charges only bit on the modem was set to on.

Syntax: Integer

Access: Read-only

vinesNoroute

Indicates the total number of VINES packets dropped because the router did not know where to forward them.

Syntax: Integer

Access: Read-only

vinesNotgt4800

Indicates the total number of VINES broadcast packets not forwarded to all interfaces because the over 4800 bps bit on the modem was set to on.

Syntax: Integer

Access: Read-only

vinesNotlan

Indicates the total number of VINES broadcast packets not forwarded to all interfaces because the lan only bit on the modem was set to on.

Syntax: Integer

Access: Read-only

vinesUnknown

Indicates the total number of unknown VINES input packets.

Syntax: Integer

Access: Read-only

Xerox Network Systems (XNS) Group

This group is present in all router based products running the Xerox Network Systems (XNS) protocol.These variables provide such information as the number of packets forwarded, total number of input packets, and total number of packets transmitted with errors.

xnsBcastin

Indicates the total number of Xerox Network Systems (XNS) input broadcast packets.

Syntax: Integer

Access: Read-only

xnsBcastout

Indicates the total number of Xerox Network Systems (XNS) output broadcast packets.

Syntax: Integer

Access: Read-only

xnsChksum

Indicates the total number of Xerox Network Systems (XNS) input packets with checksum errors.

Syntax: Integer

Access: Read-only

xnsEchorepin

Indicates the total number of Xerox Network Systems (XNS) echo reply packets received.

Syntax: Integer

Access: Read-only

xnsEchorepout

Indicates the total number of Xerox Network Systems (XNS) echo reply packets sent.

Syntax: Integer

Access: Read-only

xnsEchoreqin

Indicates the total count of number of Xerox Network Systems (XNS) echo request packets were received.

Syntax: Integer

Access: Read-only

xnsEchoreqout

Indicates the total number of Xerox Network Systems (XNS) echo request packets sent.

Syntax: Integer

Access: Read-only

xnsErrin

Indicates the total number of Xerox Network Systems (XNS) error input packets.

Syntax: Integer

Access: Read-only

xnsErrout

Indicates the total number of Xerox Network Systems (XNS) error output packets.

Syntax: Integer

Access: Read-only

xnsForward

Indicates the total number of Xerox Network Systems (XNS) packets that have been forwarded.

Syntax: Integer

Access: Read-only

xnsFormerr

Indicates the total number of Xerox Network Systems (XNS) input packets with header errors.

Syntax: Integer

Access: Read-only

xnsFwdbrd

Indicates the total number of Xerox Network Systems (XNS) broadcast packets forwarded.

Syntax: Integer

Access: Read-only

xnsHopcnt

Indicates the total number of Xerox Network Systems (XNS) input packets that have exceeded the maximum hop count.

Syntax: Integer

Access: Read-only

xnsInmult

Indicates the total number of Xerox Network Systems (XNS) input packets received with multicast addresses.

Syntax: Integer

Access: Read-only

xnsInput

Indicates the total number of input Xerox Network Systems (XNS) packets.

Syntax: Integer

Access: Read-only

xnsLocal

Indicates the total number of Xerox Network Systems (XNS) input packets for this host.

Syntax: Integer

Access: Read-only

xnsNoencap

Provides the total number of Xerox Network Systems (XNS) packets dropped because they could not be encapsulated.

Syntax: Integer

Access: Read-only

xnsNoroute

Indicates the total number of Xerox Network Systems (XNS) packets that were discarded because the router did not know where to forward them.

Syntax: Integer

Access: Read-only

xnsNotgate

Indicates the total number of Xerox Network Systems (XNS) input packets received while not XNS routing was not enabled.

Syntax: Integer

Access: Read-only

xnsOutput

Indicates the total number of Xerox Network Systems (XNS) output packets.

Syntax: Integer

Access: Read-only

xnsUnknown

Indicates the total number of unknown Xerox Network Systems (XNS) input packets.

Syntax: Integer

Access: Read-only