Table Of Contents
Accessing Other-Vendor MIB Variables Supported by Cisco
Interpreting the Object Identifier
Object Identifier Numbers for Variables
Fast Serial Interface Processor (FSIP) Group
Address Resolution Protocol (ARP)
Connectionless Network Service (CLNS)
Maintenance Operation Protocol (MOP)
Banyan Virtual Integrated Network Service (VINES)
IP Checkpoint Accounting Group
IP Checkpoint Accounting Table
Local IPX Checkpoint Accounting Table
Binary Synchronous Communication (BSC) Group
Blocked Serial Tunnel (BSTUN) Group
Notification for Blocked Serial Tunnel Group
Interface Output Counter Table
Cisco Integrated Services Digital Network (ISDN) MIB Group
Trap related to connection management
Qualified Logical Link Control (QLLC) MIB Group
QLLC Link Station Administrative Table (qllcLSAdminTable)
QLLC Link Station Operational Table (qllcLSOperTable)
QLLC Link Station Statistics Table (qllcLSStatsTable)
QLLC Link Station Admin Group (qllcLSAdminGroup)
QLLC Link Station Operational Group (qllcLSOperGroup)
QLLC Link Station Statistics Group (qllcLSStatsGroup)
QLLC Conversion Administrative Table (convQllcAdminTable)
QLLC Conversion Operational Table (convQllcOperTable)
Channel Interface Processor (CIP) Group
Notifications for Cisco CIP CSNA MIB
Notification for Cisco SNA LLC Group
Cisco Transmission Control Protocol (ciscoTCP) Group
Cisco DownStream Physical Unit (DSPU) Group
Flash Partition Level Information
Cisco Integrated CSU/DSU Group
CSU/DSU Static Configuration Table
T1 CSU/DSU Module Configuration Table
Sw56k CSU/DSU Module Configuration Table
Sw56k CSU/DSU Module Status Table
Notifications for Cisco Integrated CSU/DSU
Cisco Repeater (ciscoRptr) Group
Cisco Remote Source-Route Bridging (RSRB) Group
Environmental Monitor Card and Environmental Monitoring
ciscoEnvMonTemperatureStatusTable
SNMPv2 Notifications Used in Cisco Environmental Monitoring
Notification for Cisco SDLLC Conversion Group
Cisco Serial Tunnel (STUN) Group
Notification for Cisco Serial Tunnel Group
Synchronous Data Link Control (SDLC) Group
Terminal Services Line Session Table
Transmission Control Protocol (TCP) Group
Virtual Integrated Network Service (VINES) Group
Xerox Network Systems (XNS) Group
Public SNMP Traps Supported by Cisco
Variables Supported in RFC 1285
MIBs Supported by Cisco Software Releases
Cisco Internetwork Operating System (Cisco IOS) Release 10.0
Cisco Internetwork Operating System (Cisco IOS) Release 10.2
Cisco Internetwork Operating System (Cisco IOS) Release 10.3(2)
Cisco Internetwork Operating System (Cisco IOS) Release 10.3
Cisco Internetwork Operating System (Cisco IOS) Release 10.3(3)
Cisco Internetwork Operating System (Cisco IOS) Release 11.0
Cisco Internetwork Operating System (Cisco IOS) Release 11.0(5)
MIB User Quick Reference
Preface
From the perspective of a network manager, network management takes place between two major types of systems: those in control, called managing systems, and those observed and controlled, called managed systems. The most common managing system is called a Network Management System (NMS). Managed systems can include hosts, servers, or network components such as routers or intelligent repeaters.
To promote interoperability, cooperating systems must adhere to a common framework and a common language, called a protocol. In the Internet Network Management Framework, that protocol is the Simple Network Management Protocol, commonly called SNMP.
The exchange of information between managed network devices and a robust NMS is essential for reliable performance of a managed network. Because some of these devices may have a limited ability to run management software, the software must minimize its performance impact on the managed device. The bulk of the computer processing burden, therefore, is assumed by the NMS. The NMS in turn runs the network management applications, such as CiscoWorks or CiscoView, that present management information to network managers and other users.
In a managed device, the specialized low-impact software modules, called agents, access information about the managed devices and make it available to the NMS. Managed devices maintain values for a number of variables and report those, as required, to the NMS. For example, an agent might report such data as the number of bytes and packets in and out of the device, or the number of broadcast messages that were sent and received. In the Internet Network Management Framework, each of these variables is referred to as a managed object. A managed object is a classification of anything that can be managed, anything that an agent can access and report back to the NMS. All managed objects are contained in the Management Information Base (MIB), a database of the managed objects.
An NMS can control a managed device by sending a message to the agent (of that managed device) requiring the device to change the value of one or more of its variables. The managed devices can respond to commands such as Sets or Gets. Sets are used by the NMS to control the device. Gets are used by the NMS to monitor the device.
The Cisco MIB User Quick Reference lists the MIB variables that are proprietary to Cisco devices. However, many other internet-standard MIBS are supported by Cisco agents. These standard MIBs are defined in documents called Requests for Comments (RFCs). (For information on the RFC MIBs supported by Cisco, refer to the section "Cisco-Supported MIBs" later in this guide.) Therefore, in order to find specific MIB information, examine the Cisco proprietary MIB structure and the standard RFC MIBs supported by Cisco.
If your NMS is unable to get requested information from a managed device, such as a Cisco router, the MIB that allows that specific data collection might be missing. Typically, if an NMS cannot retrieve a particular MIB variable, either the NMS does not recognize the MIB variable or the agent does not support the MIB variable. If the NMS does not recognize a specified MIB variable, the MIB might need to be loaded into the NMS, usually by means of a MIB compiler. As an NMS administrator, you might need to load the Cisco MIB or the supported RFC MIB into the NMS in order to execute a specified data collection. If the agent does not support a specified MIB variable, you need to find out what version of Cisco IOS or system software you are running. Different MIBs are supported in different software releases.
Use this guide to determine whether your version of software actually supports the specified MIB variable. (See the section "MIBs Supported by Cisco Software Releases" at the end of this guide.) Or, you might want to use this guide to see what variables are available for a given software release. As you reference this guide, read the descriptions of the variables to learn what they are and what they do. Check the Access or Max-Access type to learn what operations, such as reading Gets or writing Sets, can be performed on a particular MIB variable. Check the Syntax type to determine the data type for the MIB variable. Some variables provide textual information (for example, syntax of DisplayString), while others provide numeric information (for example, syntax of Integers or Counters). Once you identify a needed MIB variable, you can easily load the file into the NMS. To learn how to access a Cisco MIB file, refer to "Accessing Cisco MIB Files" later in this main section. Cisco Systems also supports many MIB variables developed by other vendors.
Introduction to the MIB Guide
This guide describes the Cisco Systems private, or local, Management Information Base (MIB) for Cisco Internetwork Operating System (IOS) Release 11.0. The Cisco MIB is provided with all Cisco software releases and with CiscoWorks router management software. The MIB file contains variables that can be set or read to provide information on network devices and interfaces.
The Cisco MIB is a set of variables that are private extensions to the Internet standard MIB II and many other internet standard MIBs. MIB II is documented in RFC 1213, Management Information Base for Network Management of TCP/IP-based Internets: MIB-II.
The Cisco MIB is described by a number of MIB files, which can be obtained by FTP from the Cisco server. The listing of Cisco MIB variables in those files is identical to the listing in this guide.
Accessing Cisco MIB Files
You can obtain the files that describe the Cisco MIB using anonymous ftp or the World Wide Web (WWW) to access Cisco Information Online (CIO).
Via ftp, use the ftp ftp.cisco.com command. Log in with the username anonymous and enter your e-mail name when prompted for the password. Use the cd pub/mibs command to go to the directory that contains the MIB files, and then issue the get README command to obtain the readme file containing a list of available product family directories. Cisco IOS MIB files are in the routers subdirectory, organized by release number. Refer to the README file in each directory, as necessary, to determine the location of the desired MIB file. You can then use the ftp command get filename to retrieve the MIB file.
To access CIO via the WWW, use the URL: http://www.cisco.com/public/mibs or ftp://www.cisco.com/pub/mibs.
Accessing Other-Vendor MIB Variables Supported by Cisco
You can obtain the files that describe other-vendor MIB variables supported by Cisco by using the ftp ftp.venera.isi.edu command. Log in with the username anonymous and enter your e-mail name when prompted for the password. Use the cd mib command to go to the directory that contains the MIB files, and then issue the get README command to display the readme file containing a list of available files. You can then use the get filename command to retrieve the desired MIB file (for example, use get novell-nlsp-mib.my to retrieve the Novell NLSP MIB).
Working with SNMP
The Cisco MIB variables are accessible via the Simple Network Management Protocol (SNMP), which is an application-layer protocol designed to facilitate the exchange of management information between network devices. The SNMP system consists of three parts: SNMP manager, SNMP agent, and MIB.
Instead of defining a large set of commands, SNMP places all operations in a get-request, get-next-request, get-bulk-request, and set-request format. For example, an SNMP manager can get a value from an SNMP agent or store a value into that SNMP agent. The SNMP manager can be part of a network management system (NMS), and the SNMP agent can reside on a networking device such as a router. You can compile the Cisco MIB with your network management software. If SNMP is configured on a router, the SNMP agent can respond to MIB-related queries being sent by the NMS.
An example of an NMS is the CiscoWorks network management software. CiscoWorks uses the Cisco MIB variables to set device variables and to poll devices on the internetwork for specific information. The results of a poll can be graphed and analyzed in order to troubleshoot internetwork problems, increase network performance, verify the configuration of devices, monitor traffic loads, and more.
As shown in Figure 1, the SNMP agent gathers data from the MIB, which is the repository for information about device parameters and network data. The agent also can send traps, or notification of certain events, to the manager. The Cisco trap file, mib.traps, which documents the format of the Cisco traps, is available on the Cisco host ftp.cisco.com.
Figure 1 SNMP Network
The SNMP manager uses information in the MIB to perform the operations described in Table 1.
Table 1 SNMP Manager Operations
get-request
Retrieve a value from a specific variable.
get-next-request
Retrieve the value following the named variable. Often used to retrieve variables from within a table1 .
get-response
The reply to a get-request, get-next-request, get-bulk-request, and set-request sent by an NMS.
get-bulk-request
Similar to get-next-request, but fill the get-response with up to max-repetition number of get-next interactions.
set-request
Store a value in a specific variable.
trap
An unsolicited message sent by an SNMP agent to an SNMP manager indicating that some event has occurred.
1 With this operation, an SNMP manager does not need to know the exact variable name. A sequential search is performed to find the needed variable from within the MIB.
Internet MIB Hierarchy
The MIB structure is logically represented by a tree hierarchy. (See .) The root of the tree is unnamed and splits into three main branches: Consultative Committee for International Telegraph and Telephone (CCITT), International Organization for Standardization (ISO), and joint ISO/CCITT.
These branches and those that fall below each category have short text strings and integers to identify them. Text strings describe object names, while integers allow computer software to create compact, encoded representations of the names. For example, the Cisco MIB variable authAddr is an object name and is denoted by number 5, which is listed at the end of its object identifier number 1.3.6.1.4.1.9.2.1.5.
The object identifier in the Internet MIB hierarchy is the sequence of numeric labels on the nodes along a path from the root to the object. The Internet standard MIB is represented by the object identifier 1.3.6.1.2.1. It also can be expressed as iso.org.dod.internet.mgmt.mib. (See .)
Figure 2
Internet MIB Hierarchy
Cisco MIB
The private Cisco MIB is represented by the object identifier 1.3.6.1.4.1.9, or iso.org.dod.internet.private.enterprise.cisco. The Cisco MIB includes the following subtrees: local (2), temporary (3), and, ciscoMgmt (9).
The local subtree contains MIB objects defined prior to Cisco Internetwork Operating System (IOS) Release 10.2. MIB objects defined prior to Software Release 10.2 implemented the SNMPv1 Structure of Management Information (SMI). Beginning with Cisco IOS 10.2, however, Cisco MIBs are defined using the SNMPv2 SMI. MIBs defined using SNMPv2 are being placed in the ciscoMgmt tree. (See .) MIBs currently defined in the local subtree are being deprecated by Cisco as an ongoing process, and being replaced with new objects defined in the ciscoMgmt subtree. For example, the TCP group that was in the local group has been deprecated and replaced with a new TCP group in the ciscoMgmt tree.
Figure 3 Cisco Private MIB Hierarchy
In , the local variables group is identified by 2; its subgroup, called lsystem, is identified by 1; and the first variable is romId with a value of 1. Therefore, the variable romId has a value of 1.3.6.1.4.1.9.2.1.1.0. The appended 0 indicates that 1.3.6.1.4.1.9.2.1.1.0 is the one and only instance of romId.
Note
Although variables are arranged as shown in and as described in the compilable Cisco MIB file, this quick reference guide organizes variable groups and variables within groups alphabetically, so that you can quickly look up descriptions of MIB variables.
Interpreting the Object Identifier
In this guide, each group of Cisco MIB variables is accompanied by an illustration that indicates the specific object identifier for each variable.
For example, in the object identifier 1.3.6.1.4.1.9.2.1 at the top of the illustration indicates the labeled nodes. The last value is the number of the Cisco MIB variable. For example, the MIB variable hostConfigAddr is indicated by the number 51. The object identifier for hostConfigAddr is iso.org.dod.internet.private.enterprise.cisco.local variables.system group.hostConfigAddr or 1.3.6.1.4.1.9.2.1.51.
Figure 4
Object Identifier Example for a Cisco MIB Variable
Tables
When network management protocols use names of MIB variables in messages, each name has a suffix appended. For simple variables, the suffix 0 refers to the instance of the variable with that name. A MIB also can contain tables of related variables.
Following is an excerpt of the information on the IP Routing table (known as lipRoutingTable) from the associated mib file:
lipRoutingTable OBJECT-TYPESYNTAX SEQUENCE OF LIpRouteEntryACCESS not-accessibleSTATUS mandatoryDESCRIPTION"A list of IP routing entries."::= { lip 2 }lipRouteEntry OBJECT-TYPESYNTAX LIpRouteEntryACCESS not-accessibleSTATUS mandatoryDESCRIPTION"A collection of additional objects in thecisco IP routing implementation."INDEX { ipRouteDest }::= { lipRoutingTable 1 }LIpRouteEntry ::=SEQUENCE {locRtMaskIpAddress,locRtCountINTEGER,}The local IP Routing table, lipRoutingTable, is described in . The lipRoutingTable contains two variables: locRtMask and locRtCount. The index for this table is the destination address of the IP route, or ipRouteDest. If there are n number of routes available to a device, there will be n rows in the IP Routing table.
In , for the route with the destination IP address of 131.104.111.1, the IP Routing table network mask is 255.255.255.0. The number of parallel routes within the routing table is 3.
Table 2 IP Routing
Typically, an instance identifier might be a unique interface number or a 0, as described earlier with the romId example. An instance identifier can also be an (IP) address. For example, to find the network mask for the route with a destination address of 131.104.211.243, use the variable locRtMask with an instance identifier of 131.104.211.243. The format is locRtMask.131.104.211.243.
In this guide, when variables belong to a table, they are listed in the section describing the table. The following tag is used to indicate the end of a table:
End of Table
All variables before this tag are part of the table.
Local Variables
The local variables section pertains to all Cisco devices and contains the following groups.
Note
•
Pertains to the Flash memory used to store, boot, and write system software images. Includes information such as Flash memory size and the contents of flash. Operations can be invoked by SETing MIB variables such as erasing Flash memory and transferring a Flash memory file to a Trivial File Transfer Protocol (TFTP) server. The Flash group supports Cisco 7000, 7010, and AGS+. The Flash group in Local Variables has been deprecated by the Cisco Flash group found in CiscoMgmt.
•
Provides information on Cisco device interfaces, such as traffic statistics, line status, average speed of input and output packets, and error checking.
•
Provides information about devices running IP. Includes information such as how and from whom an interface obtained its address, Internet Control Message Protocol (ICMP) messages, and number of packets lost.
•
Provides information on system-wide parameters for Cisco devices, such as software version, host name, domain name, buffer size, configuration files, and environmental statistics.
•
Provides information about terminal services, such as number of physical lines, line status, line type, line speed, type of flow control, and type of modem.
•
Provides statistics on the number of input and output bytes and packets for TCP connections. The "local" TCP group has been deprecated, and replaced with a new TCP group in the ciscoMgmt group which provides more functionality.
Temporary Variables
This section is equivalent to the experimental space defined by the Structure of Management Information (SMI). These variables are subject to change for each Cisco Systems software release.
Temporary variables consists of the following groups, which are presented in alphabetical order. (See .)
•
Pertains to devices running the AppleTalk protocol. Includes information such as total number of input and output packets, number of packets with errors, and number of packets with Address Resolution Protocol (ARP) requests and replies.
•
Pertains to hardware information about Cisco devices. Includes information such as the types of cards used by the device, the hardware version of the cards, and the number of slots in the chassis. The cardTableIfIndex Table, introduced in Cisco IOS Release 10.3, provides logical mapping between the device interface and a card's presence in the chassis. The variables in this table support only the Cisco 4000, Cisco 4500, Cisco 7000, and Cisco7010. By implementing the new MIB table in supported configurations, you can discover statistics about the card. The new MIB table provides significant solutions for CiscoWorks and CiscoView users.
•
Pertains to devices running the DECnet protocol. Includes information such as hop count, host name, total packets received and sent, and number of packets with header errors.
•
•
•
Pertains to devices running the Novell protocol. Includes information such as total number of input and output packets, number of packets with errors, and number of packets with service access point (SAP) requests and replies.
•
Pertains to devices running the VINES protocol. Includes information such as total number of input and output packets, number of packets with errors, and number of packets with Internet Control Message Protocol (ICMP) requests and replies.
•
Pertains to devices running the XNS protocol. Includes information such as number of packets forwarded, total number of input packets, and total number of packets with errors.
ciscoMgmt Variables
The ciscoMgmt subtree consists of the following variables:
•
Provides configuration and operational information for Cisco's Binary Synchronous Communications (BSC) implementation. The following two entities are managed: BSC ports (serial interfaces), and BSC control units (stations on a port).
•
Provides configuration and operational information about Cisco's blocked serial tunnel (BSTUN) implementation. Four entities are managed: BSTUN global entry, BSTUN group table, BSTUN port table, and BSTUN route table.
•
Specifies the MIB module for objects used to manage the Cisco CIP card.
•
Provides information on the configuration of the Channel Interface Processor (CIP) Channel Systems Network Architecture (CSNA) feature. In eight tables, three pieces of information are provided: configuration of I/O device addresses of communication controllers, information regarding VTAM to internal adapter connections, and the number of sessions allowed between the VTAM and internal adapter.
•
Provides configuration information on the internal (virtual) LAN and internal (virtual) adapter components of the CIP CSNA feature.Within the LAN configuration are entries for the type of LAN and the bridging protocol. Within the adapter configuration are entries for the MAC address and the SNA name used for alerts.
•
Manages the TCP/IP protocol stack running on the Channel Interface Processor (CIP) card. In Release 11.0, only the TCP/IP offload feature makes use of this MIB. The read-only values allow statistics and status for every instance of IP, TCP, UDP, and ICMP protocol stacks to be viewed.
•
Provides the MIB module for management of the Cisco Discovery Protocol in Cisco devices.
•
Contains the information necessary for the definition and management of DSPU objects. Supported DSPU objects include dspuNode (Global DSPU node information), dspuPoolClass (LU pool class information), dspuPooledLu (Pooled LU information), dspuPu (Upstream/Downstream PU node information), dspuLu (Upstream/Downstream LU information), and dspuSap (Local SAP information)
•
Provides the status of the Environmental Monitor on those devices that support one. The Cisco Environmental Monitor MIB is new and contains enhanced functionality over its predecessor, including support for redundant power supplies.
•
Provides support for the Dual Flash Bank feature introduced in Cisco IOS Release 10.3(4). The Cisco Flash group is also supported in Release 10.2.
•
The integrated Channel Service Unit (CSU)/Data Service Unit (DSU) group is used with the Cisco 2524 and Cisco 2525 products, and is for T1 and switched 56 kbps interfaces. It enables network managers to retrieve line statistics and CSU/DSU configuration data.
•
Provides the status of the ISDN Interfaces on the routers. The ISDN MIB was introduced in Release 10.3(3).
•
Provides detailed access to custom and priority queuing information. This information was previously available only via the show queue EXEC command.
•
Provides user with the ability to initiate a ping (ICMP echo request) from the Cisco device to a specified destination address.
•
Provides information about the attributes of the local-remote RSRB peer relationship. The following three entities are managed: virtual rings, remote peers, and associated Token Rings.
•
Provides standard repeater (hub) features that are not in RFC 1516. The objects in this MIB support features such as link-test, auto-polarity, and source-address control, and the MDI/MDI-X switch status. The Cisco Repeater MIB was introduced in Release 10.3(3).
•
Provides read-only configuration and operational information on Cisco's implementation of SDLC-to-LLC2 media translation. The SDLLC MIB provides a table entry for each serial interface and SDLC address pair, and includes information such as FEP MAC addresses, SDLC station addresses, and Token Ring numbers on LLC2 stations.
•
Provides configuration and operational information on Cisco's serial tunnel implementation. The following four entities are managed: global STUN information, STUN groups, STUN ports, and STUN routes
•
Manages the LLC2 stack that runs on a Channel Interface Processor (CIP) card. The CIP card provides the SNA gateway to an IBM mainframe via a channel connection from the router.
•
Provides access to the cisco Snapshot support and is present in all router based products.
Snapshot routing provides easy solutions to two common problems:
1) The need to configure static routes for Dial on Demand Routing (DDR) interfaces, and 2) the overhead of periodic updates for routing protocols to remote branch offices over dedicated serial lines.
When snapshot routing is configured on an interface, normal routing updates can be sent across the interface for a short time (determined by the user). When this user-configured period of activity has elapsed, the routing updates are suspended, and the routes known to the snapshot interface are locked, putting the interface into a "frozen period." The duration of this period is also user configurable. During this time, changes in network topology are typically not transmitted across the snapshot interface, although some network protocols provide the capability to transmit changes.
•
Manages configuration of the TCP offload feature. It is made up of one table entry that shows configuration information such as path, device, host name, router name, API host application, and API router application.
•
Provides statistics on the number of input and output bytes and packets for TCP connections; ciscoTCP, however, provides more functionality over its counterpart in the Local Variables subtree.
•
Pertains to devices running the VINES protocol. Includes information such as total number of input and output packets, number of packets with errors, and number of packets with ARP and RTP requests and replies. Also includes tables of routes and neighbors. This MIB incorporates objects from the Cisco VINES command line interface, and was influenced by Banyan VINES MIB. The ciscoVINES provides VINES routing information with enhanced functionality over its predecessor located in the temporary variables subtree.
•
The QLLC is a data link protocol defined by IBM that allows SNA data to be transported across X.25 networks. The QLLC MIB includes a managed entity, called a link station. The link station includes objects to configure and monitor logical connections.
Terminology
This section presents the syntax and access type categories used to describe each variable. For details on syntax, refer to RFC 1155, and to RCF 1442 for SNMPv2.
Syntax
The syntax describes the format of the information, or value, that is returned upon monitoring or setting information in a device with a MIB variable.
Note
The syntax can be any one of the following categories:
•
Syntax: Octet string (SIZE (0-2)). The two-octet hex device address for the device the Systems Network Architecture (SNA) host will use to communicate with the Channel Systems Network Architecture (CSNA) feature on the Channel Interface Processor (CIP).
The first octet will always be zero for consistency with other CIP MIBs.
For example, for device address 1C (decimal 28) the 2-octet value is 00:1C.
•
A counter is a nonnegative integer that increases until it reaches some maximum value. After reaching the maximum value, it rolls back to zero. For example, the variable locIfipInPkts counts the number of IP protocol input packets on an interface.
•
The type of queuing algorithm used on the interface.
Syntax: Integer. 1 = fifo (first-in, first-out), 2 = priority (priority queuing), 3 = custom (custom queuing), 4 = weightedFair (weighted fair queuing)
•
A display string is a printable ASCII string. It is typically a name or description. For example, the variable netConfigName provides the name of the network configuration file for a device.
•
Syntax: Octet string (SIZE (0-2)). This channel path is a two-octet value made up of the following values:
For example, for path C7, channel logical address 9, control unit logical address 4, the 2-octet value is C7:94.
Note
•
An integer of 1 or 2, where 1 = disabled and 2 = enabled. Represents status information for a particular row in the table.
•
An integer is a numeric value. It can be an actual number, for example, the number of lost IP packets on an interface. It also can be a number that represents a nonnumeric value. For example, the variable tsLineType returns the type of terminal services line to the SNMP manager. A 2 indicates a console line; a 3 indicates a terminal line; and so on.
•
An integer from -232 to 232-1.
•
The variable hostConfigAddr indicates the IP address of the host that provided the host configuration file for a device.
•
TimeStamp is defined in RFC 1443 as the value of the MIB-II sysUpTime object at which a specific event occurred.
•
Timeticks is a nonnegative integer that counts the hundredths of a second since an event. For example, the variable loctcpConnElapsed provides the length of time that a TCP connection has been established.
•
An integer of 1 or 2, where 1 = true or 2 = false. TruthValue is defined in "Textual Conventions for version 2 of the Simple Network Management Protocol (SNMPv2)," RFC 1443.
Access
The access type, which applies to SNMPv1, describes whether a MIB variable can be used under one of the following circumstances:
•
This variable can be used to monitor information only. For example, the locIPUnreach variable, whose access is read-only, indicates whether Internet Control Message Protocol (ICMP) packets concerning an unreachable address will be sent.
•
This variable can be used to monitor information and to set a new value for the variable. For example, the tsMsgSend variable, whose access is read-write, determines what action to take after a message has been sent.
The possible integer values for this variable follow:
1 = nothing
2 = reload
3 = message done
4 = abort•
This variable can be used to set a new value for the variable only. For example, the writeMem variable, whose access is write-only, writes the current (running) router configuration into nonvolatile memory where it can be stored and retained even if the router is reloaded. If the value is set to 0, the writeMem variable erases the configuration memory.
Max-Access
This variable, which applies to SNMPv2, can represent one of the following four states: read-create, read-write, read-only, and not-accessible.
•
You cannot read or write to this variable. Entry statements are typically among those variables that are not accessible.
•
This specifies a tabular object that can be read, modified, or created as a new row in a table.
•
This variable can be used only to monitor information .
•
You can read or modify this variable.
Internetwork Management
The International Organization for Standards (ISO) Network Management Forum defined five areas of network management: fault, configuration, security, performance, and accounting. Cisco MIB variables can be mapped to each of these areas (as described in this section) and used to manage your internetwork.
Although a variable might have a primary use for one aspect of network management, variables often overlap multiple areas. For example, locIPhow and locIPwho, discussed next under "Configuration Management," can also be used for fault management if a system is not loading properly.
•
Fault management involves running diagnostic tests on the internetwork, analyzing the results, and isolating and resolving problems.
Example:
Several of the variables described in the section "Basic" provide resources for troubleshooting. For example, the variables freeMem, and whyReload provide information on why a router was reloaded, and indicate how much memory is currently available in a device.
The variables described in the section "Environmental Monitor Card and Environmental Monitoring" provide feedback on the physical status of the AGS+ router or Cisco 7000 router.
Statistics from variables in the section "Interface Table" record the number of packets dropped on particular interfaces so that they can be identified as potential trouble spots.
•
Configuration management involves monitoring and controlling the configuration of devices on the internetwork.
Example:
The locIPhow and locIPwho variables described in the section "Internet Protocol (IP) Group" provide information on how a device received its IP address and the device that provided it with its address.
The variables described in the sections "Host Configuration File" and "Network Configuration File" provide configuration file names and addresses of hosts supplying network configuration files.
The variables described in the section "System Configuration" provide information such as the name of the host that supplied the system boot image for a device and the name of the boot image.
•
Security management deals with controlling access to network resources through the use of authentication techniques and authorization policies.
Example:
The variable authAddr contains the address of the last SNMP manager that failed the authorization check. The locIPSecurity variable provides the IP security level assigned to an interface.
•
Performance management measures traffic flow across the internet, calculates the number of packets that are successfully transmitted against those that are dropped, and so on, in order to optimize efficiency.
Example:
The variables described in the section "CPU Utilization" provide feedback on CPU performance. The variables described in the section "Interface Group" provide statistics on time between packets sent, number of packets transmitted successfully, and so on.
•
Accounting management involves collecting and processing data related to resource consumption on the internet.
Example:
The variables described in the section "IP Checkpoint Accounting Table" later in this guide, provide numerous statistics such as packets and bytes sent successfully or dropped.
Cisco-Supported MIBs
Cisco supports several MIBs, which are described in the following Requests for Comments (RFCs). Also listed are RFCs describing the Internet standards that Cisco Systems follows with regard to its MIB format and the SNMP protocol.
•
Describes the common structures and identification scheme for the definition of management information for use with TCP/IP-based Internets. Formal descriptions of the structure are given using Abstract Syntax Notation One (ASN.1).
•
Describes the initial version of the standard Internet Management Information Base, MIB I. MIB I is superseded by MIB II, as described in RFC 1213.
•
Describes the SNMP architecture and supported operations.
•
Describes the format for producing concise, yet descriptive, MIB modules.
•
Describes the Internet standard MIB II for use with network management protocols in TCP/IP-based internets.
RFC 1213 obsoletes RFC 1158.
•
Describes the SNMP standardized traps and provides a means for defining enterprise-specific traps.
•
Describes the managed objects used for managing subnetworks that use the IEEE 802.5 Token Ring technology.
Cisco implements the mandatory tables (Interface table and Statistics table), but not the optional table (Timer table) of this MIB.
RFC 1239 contains information that updates RFC 1231.
•
Describes the managed objects for AppleTalk that use the SNMP protocol.
Cisco Systems provides support for the AppleTalk Resolution Protocol (ARP), AppleTalk Port Group, AppleTalk Datagram Delivery Protocol (DDP), AppleTalk Routing Table Maintenance Protocol (RTMP), AppleTalk Zone Information Protocol (ZIP), AppleTalk Name Binding Protocol (NBP), and AppleTalk Echo Group
•
The OSPF MIB defines an IP routing protocol that provides management information related OSPF and is supported by Cisco routers.
•
Describes the managed objects for Fiber Distributed Data Interface (FDDI) devices that are accessible via the Simple Network Management Protocol (SNMP).
Cisco Systems supports only some of the variables in the Station Management (SMT) and Media Access Control (MAC) groups of this MIB. Refer to the Cisco publication FDDI MIB Variables in 9.0 Product Update Bulletin No. 181. RFC 1285 corresponds to the ANSI FDDI SMT 6.2 draft standard
•
RFC 1512 updates, but does not obsolete, RFC 1285.The changes from RFC 1285, based on changes from ANSI SMT 6.2 to SMT 7.3, were so numerous that the objects in this MIB module are located on a different branch of the MIB tree. No assumptions should be made about compatibility with RFC 1285.
•
Specifies an IAB (Internet Activities Board) standards track protocol for the Internet community and defines objects for managing Ethernet-like objects.
•
This document outlines the subset of OSI's Abstract Syntax Notation One (ASN.1) used to define the Management Information Base (MIB) for version 2 of the Simple Network Management Protocol (SNMPv2).
•
This document defines the initial set of extensions (textual conventions) to the basic types defined in the SMI (RFC1442) which are available to all MIB modules.
•
Describes the managed objects which correspond to the properties associated with SNMPv2 parties, SNMPv2 contexts, and access control policies, as defined by the SNMPv2 Administrative Model.
Cisco supports the MIB variables as required by the Conformance clauses specified in these MIBs.
•
Describes the managed objects that cause the behavior of an SNMPv2 implementation.
Cisco supports the MIB variables as required by the Conformance clauses specified in these MIBs.
•
RFC 1493 obsoletes half of RFC 1286.
•
Defines a portion of the Management Information Base (MIB) for use with network management protocols in the Internet community. In particular, this RFC defines objects for managing IEEE 802.3 10- megabits per second (mbps) baseband repeaters, sometimes referred to as hubs.
•
RFC 1525 obsoletes half of RFC 1286.
Cisco supports all of the groups described in this MIB, including the following groups: dotldBase, dotldSr, dot1dStp, and dotIdTp.
•
RFC 1406 obsoletes RFC 1232.
•
Cisco supports the following tables in this MIB:
•
•
•
•
The Error Table is not supported in this MIB.
•
Cisco supports the following tables in this MIB:
•
•
•
The LAPB XID table is not supported in this MIB.
•
The X.25 packet layer MIB is available under the ifType node
rfc887-x25 (5) registered under the MIB-II transmission Object Identifier. This condition applies to all X.25 interfaces, including any DDN-X.25 encapsulation interfaces. Cisco supports the following tables in this MIB:•
•
•
•
•
•
The following tables are not supported in this MIB:
•
•
•
Provides some support for RFC 1269 and replacement draft IETF-BGP-MIBC4-OS.Txt. Cisco supports the following tables in this MIB:
•
•
•
•
•
The RS-232-like Hardware Device MIB applies to interface ports that might logically support the Interface MIB, a Transmission MIB, or the Character MIB. The most common example is an RS-232 port with modem signals.
The RS-232-like Hardware Device MIB is mandatory for all systems that have such a hardware port supporting services managed through some other MIB.
The MIB includes many similar types of hardware, and as a result contains objects not applicable to all of those hardware types. The compliance definitions have a general group for all implementations, and separate groups for the different types of ports, such as asynchronous and synchronous.
The RS-232-like Hardware Port MIB includes RS-232, RS-422, RS-423, V.35, and serial physical links (other asynchronous or synchronous) with a similar set of control signals.
The MIB contains objects that relate to physical layer connections. Such connections may provide hardware signals (other than for basic data transfer), such as RNG and DCD. Hardware ports also have such attributes as speed and bits per character.
•
Cisco supports most, but not all, objects in RFC 1593, an informational RFC containing managed objects that describe the Advanced Peer-to-Peer Networking (APPN) node, the connections of the node to other SNA nodes, and the APPN network topology.
To obtain copies of RFCs, use the ftp nic.ddn.mil command. Log in as anonymous and enter your e-mail name when prompted for the password. Enter the cd rfc command to change to the correct directory. Use the get rfc-index.txt command to retrieve a list of all available RFCs. To obtain a copy of any specific RFC, enter get rfcnnnn.txt, where nnnn is the RFC number.
Related Cisco Publications
For detailed information on configuration and troubleshooting commands, refer to the following Cisco publications:
•
•
•
•
Users of the CiscoWorks router management software can refer to the CiscoWorks User Guide for information on CiscoWorks router management software features and its use of MIB variables for the purposes of graphing and analyzing network performance, ensuring configuration consistency, troubleshooting, and more.
Suggested Reading
Following are suggested reading materials:
•
•
•
•
•
Object Identifier Numbers for Variables
The figures in this section provide a visual overview of the Cisco MIB variables along with the object identifier numbers for each MIB variable. The MIB variables are arranged alphabetically within each figure (in the same order in which they appear in the sections of this guide).
Figure 5
Local Variables: Flash File Table and Flash Group
Figure 6
Local Variables: FSIP Group Variables
Figure 7
Local Variables: Interface Group Table
Figure 8 Local Variables: Interface Group—ARP, AppleTalk, Apollo, Bridging, CLNS, DECnet, HP Probe, IP, LNM, and MOP
Figure 9 Local Variables: Interface Group—Novell, Other Protocols, STUN, Spanning Tree
Figure 10
Local Variables: Interface Group—VINES
Figure 11
Local Variables: Interface Group—XNS
Figure 12
Local Variables: Internet Protocol (IP) Group
Figure 13
Local Variables: IP Accounting Table
Figure 14
Local Variables: IP Checkpoint Accounting Table
Figure 15
Local Variables: System Group—Buffers
Figure 16 Local Variables: System Group—CPU Utilization and Environmental Monitor Card
Figure 17
Local Variables: Terminal Services Group
Figure 18 Local Variables: Transmission Control Protocol (TCP) Connection Table
Figure 19
Temporary Variables: AppleTalk and Chassis
Figure 20
Temporary Variables: DECnet
Figure 21
Temporary Variables: DECnet Tables
Figure 22 Temporary Variables: Novell and Xerox Network Systems (XNS)
Figure 23
Temporary Variables: IPX Accounting Table I
Figure 24
Temporary Variables: IPX Checkpoint Accounting Table
Figure 25 Temporary Variables: Virtual Integrated Network System (VINES) I
Figure 26 Temporary Variables: (VINES) II
Figure 27 ciscoMgmt Variables: Binary Synchronous Communication (BSC)
Figure 28 ciscoMgmt Variables: Blocked Serial Tunnel (BSTUN)
Figure 29 ciscoMgmt Variables: Channel Interface Processor (CIP) Card Table
Figure 30 ciscoMgmt Variables: Channel Interface Processor (CIP) Card Daughter Board and SubChannel Tables
Figure 31 ciscoMgmt Variables: Channel Interface Processor Group CardClaw
Figure 32 ciscoMgmt Variables: Cisco CIP CSNA
Figure 33 ciscoMgmt Variables: Cisco CIP CSNA (cont.)
Figure 34 ciscoMgmt Variables: Cisco CIP LAN
Figure 35 ciscoMgmt Variables: ciscoDiscovery Protocol
Figure 36 ciscoMgmt Variables: Cisco CIP TCP/IP
Figure 37 ciscoMgmt Variables: Cisco CIP TCP/IP (cont.)
Figure 38 ciscoMgmt Variables: Cisco Flash MIB
Figure 39 ciscoMgmt Variables: Cisco Integrated CSU/DSU Group
Figure 40 ciscoMgmt Variables: Cisco Interface Queue
Figure 41 ciscoMgmt Variables: Cisco ISDN MIB
Figure 42 ciscoMgmt Variables: Cisco Remote Source-Route Bridging (RSRB)
Figure 43
ciscoMgmt Variables: Cisco Repeater (ciscoRptr) MIB
Figure 44 ciscoMgmt: Qualified Logical Link Control (QLLC)
Figure 45 ciscoMgmt Variables: Cisco SDLLC Conversion
Figure 46 ciscoMgmt Variables: Cisco Serial Tunnel (STUN)
Figure 47 ciscoMgmt Variables: Cisco SNA LLC
Figure 48 ciscoMgmt Variables: Cisco SNA LLC (cont.)
Figure 49 ciscoMgmt Variables: ciscoSnapshot MIB
Figure 50 ciscoMgmt Variables: Cisco Transmission Control Protocol (TCP) Connection Table
Figure 51 ciscoMgmt Variables: Cisco TCP Offload
Figure 52 ciscoMgmt Variables: ciscoVINES MIB I
Figure 53 ciscoMgmt Variables: ciscoVINES MIB II
Figure 54 ciscoMgmt Variables: DownStream Physical Unit (DSPU)
Figure 55 ciscoMgmt Variables: DownStream Physical Unit (DSPU) (cont.)
Figure 56 ciscoMgmt Variables: Environmental Monitor
Figure 57 ciscoMgmt Variables: Ping Group
Figure 58 Synchronous Data Link Control (SDLC)
Figure 59 Synchronous Data Link Control (SDLC) (cont.)
Local Variables
This section describes the MIB variables within the Cisco product line. Certain groups of variables might or might not be present, depending upon the software options and configuration in the managed device.
Local Variables Available
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
This has been deprecated and replaced with a version in the ciscoMgmt group.
•
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 can 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 , the flash1 file has a directory size of 50 octets, and its status is valid, represented by the integer 1.
Table 3 Flash File Table
flashDirName
Provides the name associated with a Flash directory entry.
Syntax: Display string
Access: Read-only
flashDirSize
Provides the size (in octets) of a Flash directory entry.
Syntax: Integer
Access: Read-only
flashDirStatus
Indicates the status of the Flash directory 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. For example, the type of card connected to the Flash card could be either CSC-MS or CSC-MC+.
Syntax: Display string
Access: Read-only
flashController
Provides the type of Flash controller (either CCTL or CCTL2) installed in the router.
Syntax: Display string
Access: Read-only
flashEntries
Provides the number of directory entries, or files, that exist in the Flash memory directory.
Syntax: Integer
Access: Read-only
flashErase
Sets a request to erase Flash memory, freeing up all available memory space. All of the Flash memory is erased out. Individual files cannot be erased from Flash memory.
Syntax: Integer
Access: Write-only
flashEraseStatus
Indicates the status of current or last erasing of Flash memory.
Syntax: Integer
Access: Read-only
flashEraseTime
Indicates the value of sysUpTime the last time the Flash memory was erased.
Syntax: Timeticks
Access: Read-only
flashFree
Provides the amount of available Flash memory in octets.
Syntax: Integer
Access: Read-only
flashSize
Provides the amount of total Flash memory in octets.
Syntax: Integer
Access: Read-only
flashStatus
Indicates the status of the availability of Flash memory.
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.
This copy of the system image can serve as a backup copy and can also be used to verify that the copy in the Flash memory is the same as the original file.
The Flash memory card can be used as a TFTP file server for other routers on the network. This feature allows you to boot a remote router with an image that resides in the Flash server memory.
Syntax: Display string
Access: Write-only
flashToNetStatus
Indicates the status of the current or last flash to net transfer.
Syntax: Integer
Access: Read-only
flashToNetTime
Indicates the value of sysUpTime the last time a file was copied from the Flash memory in the router to the TFTP host.
Syntax: Timeticks
Access: Read-only
flashVPP
Provides the status of the VPP DIP jumper on the Flash memory card. Files can be written to the Flash memory card only if the VPP DIP jumper is turned on.
Syntax: Integer (1 = VPP enabled/Flash write enabled, 2 = VPP disabled/Flash write disabled)
Access: Read-only
netToFlash
Copies a software image from Trivial File Transfer Protocol (TFTP) server to the Flash memory on the router. The value (display string) is the name of the file being sent, or written, to the Flash memory. The instance ID is the IP address of the TFTP host.
The TFTP image copied to the Flash memory must be at least System Software Release 9.0 or later. If earlier system software is copied into the Flash memory, the host processor card will not recognize the CSC-MC+ card upon the next reboot.
If free Flash memory space is unavailable, or if the Flash memory has never been written to, the erase routine is required before new files can be copied.
Syntax: Display string
Access: Write-only
netToFlashStatus
Indicates the status of the current or next-to-last flash transfer.
Syntax: Integer
Access: Read-only
netToFlashTime
Indicates the value of sysUpTime the last time a file was copied from a Trivial File Transfer Protocol (TFTP) server to the Flash memory on the router.
Syntax: Timeticks
Access: Read-only
Fast Serial Interface Processor (FSIP) Group
The local FSIP Card table, lfsipTable, contains information about FSIP cards used by the Cisco 7000 and includes the following six variables that provide information about the processor: locIfFSIPtype, locIfFSIPrts, locIfFSIPcts, locIfFSIPdtr, locIfFSIPdcd, and locIfFSIPdsr. The index to this table is locIfSIPIndex, which indicates the interface index of the card corresponding to its IfIndex.
Table 4 FSIP Card Table
locIfFSIPcts
Indicates whether the CTS (clear to send) signal is up or down.
Syntax: Integer (1 = not available, 1 = up, 2 = down)
Access: Read-only
locIfFSIPdcd
Indicates whether the DCD (data carrier detect) signal is up or down.
Syntax: Integer (1 = not available, 2 = up, 3 = down)
Access: Read-only
locIfFSIPdsr
Indicates whether the DSR (data set ready) signal is up or down.
Syntax: Integer (1 = not available, 2 = up, 3 = down)
Access: Read-only
locIfFSIPdtr
Indicates whether the DTR (data terminal ready) signal is up or down.
Syntax: Integer (1 = not available, 2 = up, 3 = down)
Access: Read-only
locIfFSIPIndex
Indicates the index interface port of the corresponding ifIndex. (RFC 1213)
Syntax: Integer
Access: Read-only
locIfFSIPrts
Indicates whether the RTS (request to send) signal is up or down.
Syntax: Integer (1 = not available, 2 = up, 3 = down)
Access: Read-only
locIfFSIPtype
Indicates whether the FSIP line uses DCE (data communications equipment) or DTE (data terminal equipment).
Syntax: Integer (1 = not available, 2 = DTE, 3 = DCE)
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 the number of packets dropped, time allocations for input and output packets, and so on. These variables also can 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 in the Interface group. The index to the table is ifIndex, which indicates the number of the interface. If the device has n number of interfaces, the Interface table will contain n rows.
In the Interface table shown in , the first column indicates the number of interfaces on the device. Each of the variables in the interface table occupies one column; for example, locIfHardType is shown in a column, followed by locIfLineProt in the next column, and so on.
Table 5 Interface Table
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 serial interface received the Carrier Detect (CD) signal. If the carrier detect line is changing state often, it might indicate modem or line problems.
Syntax: Integer
Access: Read-only
locIfCollisions
Provides the number of output collisions detected on this interface.
Syntax: Integer
Access: Read-only
locIfDelay
Provides the media-dependent delay in transferring a packet to another interface on the media. The delay is indicated in microseconds. Used by Interior Gateway Routing Protocol (IGRP).
Syntax: Integer
Access: Read-only
locIfDescr
Provides a description of the interface (such as Ethernet, serial, and so on) that corresponds to the user-configurable interface description commands
Syntax: Display string
Access: Read-write
locIfFastInOctets
Provides the octet count for inbound traffic routed with fast and autonomous switching.
Syntax: Counter
Access: Read-only
locIfFastInPkts
Provides the packet count for inbound traffic routed with fast and autonomous switching.
Syntax: Counter
Access: Read-only
locIfFastOutOctets
Provides the octet count for outbound traffic routed with fast and autonomous switching.
Syntax: Counter
Access: Read-only
locIfFastOutPkts
Provides the packet count for outbound traffic routed with fast and autonomous 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. Aborted input packets usually indicate a clocking problem between the serial interface and the data-link equipment.
Syntax: Integer
Access: Read-only
locIfInBitsSec
Provides a weighted 5-minute exponentially decaying average of interface input bits per second.
Syntax: Integer
Access: Read-only
locIfInCRC
Provides the number of input packets that had cyclic redundancy checksum (CRC) errors. The CRC generated by the originating station or far-end device does not match the checksum calculated from the data received. On a serial link, CRCs usually indicate noise, gain hits, or other transmission problems on the data link.
Syntax: Integer
Access: Read-only
locIfInFrame
Provides the number of input packets that were received incorrectly with framing errors. On a serial line, this is usually the result of noise or other transmission problems.
Syntax: Integer
Access: Read-only
locIfInGiants
Provides the number of input packets that were discarded because they exceeded the maximum packet size allowed by the physical media.
Syntax: Integer
Access: Read-only
locIfInIgnored
Provides the number of input packets that were ignored by this interface because the interface hardware ran low on internal buffers. Broadcast storms and bursts of noise can cause the ignored count to be increased.
Syntax: Integer
Access: Read-only
locIfInKeep
Indicates whether keepalives are enabled on this interface.
Syntax: Integer (1 = enabled, 2 = disabled)
Access: Read-only
locIfInOverrun
Provides the number of times the serial receiver hardware was unable to send data to a hardware buffer because the input rate exceeded the ability of the receiver to handle the data.
Syntax: Integer
Access: Read-only
locIfInPktsSec
Provides a weighted 5-minute exponentially decaying average of input packets.
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 discarded because they were smaller than the minimum packet size allowed by the physical media.
Syntax: Integer
Access: Read-only
locIfLastIn
Provides the elapsed time in milliseconds since the last line protocol input packet was successfully received by an interface. Useful for knowing when a dead interface failed.
Syntax: Integer
Access: Read-only
locIfLastOut
Provides the elapsed time in milliseconds since the last line protocol output packet was successfully transmitted by an interface. Useful for knowing when a dead interface failed.
Syntax: Integer
Access: Read-only
locIfLastOutHang
Provides the elapsed time in milliseconds since the last line protocol output packet could not be successfully transmitted.
OR
Provides the elapsed time (in milliseconds) since the interface was last reset because of a transmission that took too long.
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. The load on the interface is calculated as an exponential average over 5 minutes and expressed as a fraction of 255 (255/255 is completely saturated). Used by Interior Gateway Routing Protocol (IGRP).
Syntax: Integer
Access: Read-only
locIfOutBitsSec
Provides a weighted 5-minute exponentially decaying average of interface output bits per second for the specific protocol.
Syntax: Integer
Access: Read-only
locIfOutPktsSec
Provides a weighted 5-minute exponentially decaying average of interface output packets per second for the specific protocol.
Syntax: Integer
Access: Read-only
locIfOutputQueueDrops
Provides the number of packets dropped because the output queue
was full.Syntax: Integer
Access: Read-only
locIfReason
Provides the reason for the most recent status change of the interface.
Syntax: Display string
Access: Read-only
locIfReliab
Provides the level of reliability for the interface. The reliability of the interface is calculated as an exponential average over 5 minutes and expressed as a fraction of 255 (255/255 is 100 percent). Used by Interior Gateway Routing Protocol (IGRP).
Syntax: Integer
Access: Read-only
locIfResets
Provides the number of times the interface was reset internally. An interface can be reset if packets queued for transmission were not sent within several seconds. On a serial line, this can be caused by a malfunctioning modem that is not supplying the transmit clock signal or by a cable problem. If the system notices that the carrier detect line of a serial interface is up, but the line protocol is down, it periodically resets the interface in an effort to restart it. Interface resets also can occur when an interface is looped back or shut down.
Syntax: Integer
Access: Read-only
locIfRestarts
Provides the number of times the interface needed to be completely restarted because of errors.
Syntax: Integer
Access: Read-only
locIfSlowInOctets
Provides the octet count for inbound traffic routed with process switching.
Syntax: Counter
Access: Read-only
locIfSlowInPkts
Provides the packet count for inbound traffic routed with process switching.
Syntax: Counter
Access: Read-only
locIfSlowOutPkts
Provides the packet count for outbound traffic routed with process switching.
Syntax: Counter
Access: Read-only
locIfSlowOutOctets
Provides the octet count for outbound traffic routed with process switching.
Syntax: Counter
Access: Read-only
End of Table
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. For detailed information on ARP, refer to the Router Products Configuration and Reference publication.
locIfarpInOctets
Provides the ARP input octet count.
Syntax: Counter
Access: Read-only
locIfarpInPkts
Provides the ARP input packet count. It indicates the number of ARP Reply packets received by this router on this interface from other hosts.
Syntax: Counter
Access: Read-only
locIfarpOutOctets
Provides the ARP output octet count.
Syntax: Counter
Access: Read-only
locIfarpOutPkts
Provides the ARP output packet count. It indicates the number of ARP Request packets sent by this router on this interface to other hosts on the network.
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 SRB protocol input packet count.
Syntax: Counter
Access: Read-only
locIfsrbOutOctets
Provides the SRB protocol output octet count.
Syntax: Counter
Access: Read-only
locIfsrbOutPkts
Provides the SRB protocol output packet count.
Syntax: Counter
Access: Read-only
Connectionless Network Service (CLNS)
The following variables in the Interface group apply to interfaces running Connectionless Network Service (CLNS):
locIfclnsInOctets
Provides the CLNS protocol input byte count.
Syntax: Counter
Access: Read-only
locIfclnsInPkts
Provides the CLNS protocol input packet count.
Syntax: Counter
Access: Read-only
locIfclnsOutOctets
Provides the CLNS protocol output byte count.
Syntax: Counter
Access: Read-only
locIfclnsOutPkts
Provides the 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 to 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 IP input octet count.
Syntax: Counter
Access: Read-only
locIfipInPkts
Provides the IP input packet count.
Syntax: Counter
Access: Read-only
locIfipOutOctets
Provides the IP output octet count.
Syntax: Counter
Access: Read-only
locIfipOutPkts
Provides the IP output packet count.
Syntax: Counter
Access: Read-only
LAN Network Manager (LNM)
The following variables in the Interface group apply to interfaces running the LAN Network Manager (LNM) protocol. This protocol manages source-route bridging (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 MOP input octet count.
Syntax: Counter
Access: Read-only
locIfmopInPkts
Provides the MOP input packet count.
Syntax: Counter
Access: Read-only
locIfmopOutOctets
Provides the MOP output octet count.
Syntax: Counter
Access: Read-only
locIfmopOutPkts
Provides the MOP output packet count.
Syntax: Counter
Access: Read-only
Novell
The following variables in the Interface group apply to interfaces running Novell:
locIfnovellInOctets
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 in the Interface group record the number of input and output packets and 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 the Interface group.
Syntax: Counter
Access: Read-only
locIfotherInPkts
Provides the input packet count for protocols other than those listed in the Interface group.
Syntax: Counter
Access: Read-only
locIfotherOutOctets
Provides the output octet count for protocols other than those listed in the Interface group.
Syntax: Counter
Access: Read-only
locIfotherOutPkts
Provides the output packet count for protocols other than those listed in the Interface group.
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 STUN protocol input octet count.
Syntax: Counter
Access: Read-only
locIfstunInPkts
Provides the STUN protocol input packet count.
Syntax: Counter
Access: Read-only
locIfstunOutOctets
Provides the STUN protocol output octet count.
Syntax: Counter
Access: Read-only
locIfstunOutPkts
Provides the 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
Banyan Virtual Integrated Network Service (VINES)
The following variables in the Interface group apply to interfaces running the Banyan Virtual Integrated Network Service (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 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 Xerox Network Systems (XNS).
locIfxnsInOctets
Provides the XNS protocol input octet count.
Syntax: Counter
Access: Read-only
locIfxnsInPkts
Provides the XNS input packet count.
Syntax: Counter
Access: Read-only
locIfxnsOutOctets
Provides the XNS protocol output octet count.
Syntax: Counter
Access: Read-only
locIfxnsOutPkts
Provides the XNS protocol output packet count.
Syntax: Counter
Access: Read-only
Internet Protocol (IP) Group
The Internet Protocol (IP) group provides variables pertaining to the 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 the following six variable entries, or rows: locIPHelper, locIPHow, locIPRedirects, locIPSecurity, locIPUnreach, and locIPWho. 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, 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.
Table 6 IP Address
131.108.201.245
nonvolatile
131.101.200.248
142.111.202.244
nonvolatile
131.56.70.249
and so on
locIPHelper
Provides the IP address for broadcast forwarding support. Provides the destination broadcast or IP address that the router should use when forwarding User Datagram Protocol (UDP) broadcast datagrams, including BootP, received on the interface.
Syntax: IpAddress
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. A router sends an ICMP Redirect message to the originator of any datagram that it is forced to resend through the same interface on which it was received. It does so because the originating host presumably could have sent that datagram to the ultimate destination without involving the router at all. ICMP Redirect messages are sent only if the router is configured with the ip redirects command.
Syntax: Integer (1 = sent, 2 = not sent)
Access: Read-only
locIPSecurity
Indicates whether IP security is enabled on the interface. For details on IP security levels, see RFC 1108, U.S. Department of Defense Security Options for the Internet Protocol.
Syntax: Integer (0 = false, 1 = true)
Access: Read-only
locIPUnreach
Indicates whether Internet Control Message Protocol (ICMP) packets indicating unreachable addresses will be sent for a specific route.
If this variable is set, and the router receives a datagram that it cannot deliver to its ultimate datagram (because it knows of no route to the destination address), it replies to the originator of that datagram with an ICMP Host Unreachable message.
Syntax: Integer (0 = false, 1 = true)
Access: Read-only
locIPWho
Provides the IP address of the device from which this interface received its IP address. If the interface does not use an IP address from another device, a value of 0.0.0.0 displays.
Syntax: IpAddress
Access: Read-only
End of Table
IP Routing Table
The local IP routing table, lipRoutingTable, contains two variables: locRtCount and locRtMask. The index for this table is the destination address of the IP route, or ipRouteDest. If there are n number of routes available to a device, there will be n rows in the IP routing table.
In , for the route with the destination IP address of 131.104.111.1, the 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.
Table 7 IP Routing Table
locRtCount
Provides the number of parallel routes within the IP Routing table.
Syntax: Integer
Access: Read-only
locRtMask
Provides the IP Routing table network mask. For example, 255.255.255.0.
Syntax: IpAddress
Access: Read-only
End of Table
actLostByts
Provides the total number of bytes of lost IP packets as a result of accounting failure.
Syntax: Integer
Access: Read-only
actLostPkts
Provides the number of IP packets that were lost due to memory limitations and accounting failure.
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 Accounting Group
Cisco routers maintain 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. For detailed information on active and checkpoint databases, refer to the Router Products Configuration and Reference and Router Products Command Reference publications.
This group provides access to the active database that is created and maintained if IP accounting is enabled on a router. The active database contains information about the number of bytes and packets switched through a system on a source and destination IP address basis. Only transit IP traffic is measured and only on an outbound basis; traffic generated by the router or terminating in the router is not included in the accounting statistics. Internetwork statistics obtained through these variables can be analyzed to improve network performance.
IP Accounting Table
The local IP accounting table, lipAccountingTable, includes four related variables: actByts, actDst, actPkts, and actSrc. The index for this table is actSrc and actDst. For example, in the first row in , the source host address is 131.24.35.248, and 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.
Table 8 Local IP Accounting Table
400
138.32.28.245
50
131.24.35.248
1259
128.52.33.101
110
128.52.33.96
actByts
Provides the total number of bytes in IP packets from the source to destination host.
Syntax: Integer
Access: Read-only
actDst
Provides the IP destination address for the host traffic matrix.
Syntax: Ip Address
Access: Read-only
actPkts
Provides the number of IP packets sent from the source to destination host.
Syntax: Integer
Access: Read-only
actSrc
Provides the IP address for the host traffic matrix.
Syntax: IpAddress
Access: Read-only
actViolation
Specifies the access list number violated by packets from this source to this destination. A zero value indicates that no access list was violated.
Syntax: Integer
Access: Read-only
End of Table
actAge
Provides the age of the accounting data in the current data matrix of the active database.
Syntax: Timeticks
Access: Read-only
IP Checkpoint Accounting Group
The Cisco router maintains two accounting databases: an active database and a checkpoint database. For detailed information on active and checkpoint databases, refer to the Router Products Configuration and Reference publication.
The running, or active database, is copied into the checkpoint database. If the checkpoint database already has data obtained previously from the active database, the router appends the latest copy of the active database to the existing data in the checkpoint database. The checkpoint database stores data retrieved from the active database until actCheckPoint is set or you delete the contents of this database by using the clear ip accounting [checkpoint] command.
A network management system (NMS) can use checkpoint MIB variables to analyze stable data in the checkpoint database.
IP Checkpoint Accounting Table
The local IP Checkpoint Accounting table, lipCkAccountingTable, includes four related variables: ckactByts, ckactDst, ckactPkts, and ckactSrc. The index for this table is ckacSrc and ckactDst. For example, in , 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.
Table 9 IP Checkpoint Accounting
400
138.32.28.245
50
131.24.35.248
480
124.45.222.246
60
123.34.216.244
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: IpAddress
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: IP address
Access: Read-only
ckactViolation
Provides the access list number violated by packets from source to destination in the checkpoint matrix.
Syntax: Integer
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.
For detailed information on active and checkpoint databases, refer to the Router Products Command Reference and Router Products Configuration and Reference publications.
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
IPX Accounting
The IPX Accounting table allows a related set of IPX accounting variables to be applied across several devices or interfaces.
ipxActLostByts
Provides the total bytes of lost IPX packets.
Syntax: Counter
Access: Read-only
ipxActLostPkts
Provides the lost IPX packets due to memory limitations.
Syntax: Counter
Access: Read-only
ipxActThresh
Provides the threshold of IPX accounting records in use before IPX traffic will be unaccounted.
Syntax: Integer
Access: Read-only
Local IPX Accounting Table
The local IPX accounting table (see ), lipxAccountingTable, provides access to the Cisco IPX accounting support. The Local IPX Accounting Table (see ) includes the following variables: ipxActSrc, ipxActDst, ipxActPkts, and ipxActByts.
Table 10 Local IPX Accounting Table
ipxActByts
Provides the total number of bytes in IPX packets from source to destination.
Syntax: Counter
Access: Read-only
ipxActDst
Provides the IPX Destination address for host traffic matrix.
Syntax: Octet String
Access: Read-only
ipxActPkts
Provides the number of IPX packets sent from source to destination.
Syntax: Counter
Access: Read-only
ipxActSrc
Provides the IPX source address for host traffic matrix.
Syntax: Octet String
Access: Read-only
End of Table
ipxActAge
Provides the age of the data in the current IPX data matrix.
Syntax: TimeTicks
Access: Read-only
Local IPX Checkpoint Accounting Table
The Local IPX Checkpoint Accounting table, ipxCkAccountingTable, includes four related variables: ipxckActByts, ipxckActDst, ipxckActPkts, and ipxckActSrc. The index for this table is ckActSrc and ckActDst.
Table 11 IPX Checkpoint Accounting
ipxCkactByts
Provides the number of bytes in IPX packets from source to destination in the checkpoint matrix.
Syntax: Counter
Access: Read-only
ipxCkactDst
Provides the IPX destination address for host in checkpoint traffic matrix.
Syntax: Octet String
Access: Read-only
ipxCkactPkts
Provides the number of IPX packets sent from source to destination in checkpoint matrix.
Syntax: Counter
Access: Read-only
ipxCkactSrc
Provides the IPX source address for host in checkpoint traffic matrix.
Syntax: Octet String
Access: Read-only
End of Table
ipxCkactAge
Provides the age of data in the IPX checkpoint matrix.
Syntax: TimeTicks
Access: Read-only
ipxActCheckPoint
Provides a checkpoint to the IPX accounting database. This MIB variable must be read and then set with the same value for the checkpoint to succeed. The value read and then set will be incremented after a successful set request
Syntax: Integer
Access: Read-write
CiscoMgmt Group
This section describes the group of MIB variables managed by Cisco Systems.
Binary Synchronous Communication (BSC) Group
The variables in this section provide configuration and operational information for Cisco's Binary Synchronous Communications (BSC) implementation. Entities managed by this MIB are: BSC ports (serial interfaces) and BSC control units (stations on a port).
BSC ports are identified by the interface index. Additional information about this interface can be obtained from the Cisco Serial Interface MIB.
BSC control units are identified by the control unit address; this is the address used by blocked serial tunneling (BSTUN) to route the BSC traffic—it is therefore equivalent to the bstunRouteStationAddress in the bstunRouteTable MIB.
bscPortTable
This table contains a list of port (serial interfaces) that have been configured to support a BSC BSTUN group.
Syntax: SEQUENCE OF BscPortEntry
Max-Access: Not-accessible
bscPortRole
The router's data link control (DLC) role with respect to the attached node. (If the bscPortRole is primary, this implies that the port is connected to a remote secondary device.)
Syntax: Integer 1 = primary, 2 = secondary, 3 = contention
Max-Access: Read-only
bscPortCodeSet
The code set used for the line controls.
Syntax: Integer 1 = ebcdic, 2 = ascii
Max-Access: Read-only
bscPortPause
For primary, this is the minimum time to be taken for a cycle around the active poll table; if this time has not elapsed when the bottom of the poll table is reached, then polling will pause until this timer expires. A value of zero means there will be no pause between cycles round the poll table.
For secondary, time out is the delay taken before sending a response to a poll when it has no data frame to send. The units are tenths of a second. The default is 10 (1 second).
Syntax: Integer (1-255)
Max-Access: Read-only
bscPortServlim
This parameter is valid for primary only. It is the number of times the active poll table will be cycled before a non-responding control unit will be polled. The default is 3.
Syntax: Integer (1-50)
Max-Access: Read-only
bscPortPollTimeout
This parameter is valid for primary only. It is the time that the primary will wait for a response to a poll or select. The units are tenths of a second. The default is 10 (1 second).
Syntax: Integer (1-100)
Max-Access: Read-only
bscPortRecoveryRetries
The number of times that a recovery sequence will be retried before the connection is considered to have failed. The default is 5.
Syntax: Integer (1-100)
Max-Access: Read-only
bscPortUnknownControlUnitsReceived
The number of frames received from the serial interface with an unsupported control unit address. If this value is non-zero, it indicates a problem in the configuration.
Syntax: Counter32
Max-Access: Read-only
bscPortSoftErrors
The number of soft errors; these are errors that are recovered. This includes cyclic redundancy check (CRC) errors received, frames that were retransmitted for any reason (NAK received or the wrong ACK received), etc. The count measures the quality of the port/line, but should be considered in relation to the amount of traffic on the port (frames or bytes sent and received).
This count includes all control unit soft errors on this port, plus errors that were not for a specific control unit.
Syntax: Counter32
Max-Access: Read-only
bscPortHardErrors
The number of hard errors; these are errors that are not recovered after bscPortRecoveryRetries number of retries, and therefore the connection has been terminated. These errors could be caused by a hardware error in the line or in the remote device, or possibly the bscPortRecoveryRetries value is set too low for the quality of the line.
This count includes all control unit hard errors on this port, plus errors that were not for a specific control unit.
Syntax: Counter32
Max-Access: Read-only
bscPortProtocolViolations
The number of protocol violations. This counter is incremented when an unexpected BSC data link control character is received from the remote device; that is, the control character is invalid in the current state of the local BSC FSM.
This indicates that there is an incompatibility between the two implementations of the BSC protocol. This count includes all control unit protocol violations on this port, plus errors which were not for a specific control unit.
Syntax: Counter32
Max-Access: Read-only
End of Table
bscControlUnitTable
This table contains information about specific control units.
Syntax: SEQUENCE OF BscCUEntry
Max-Access: Not-accessible
bscCUAddress
The poll address of the BSC control unit. This address must be unique within a BSTUN group.
Syntax: Integer (1-255)
Max-Access: Not-accessible
bscCUState
The state of the BSC control unit. If "active," this indicates that the remote control unit is polling or responding to polls.
Syntax: Integer 1 = inactive, 2 = active
Max-Access: Read-only
bscCUBytesSent
The number of sent bytes (octets), including all control characters.
Syntax: Counter32
Max-Access: Read-only
bscCUBytesReceived
The number of received bytes (octets), including all control characters.
Syntax: Counter32
Max-Access: Read-only
bscCUTotalFramesSent
The number of sent frames (blocks), including all control frames.
Syntax: Counter32
Max-Access: Read-only
bscCUTotalFramesReceived
The number of received frames (blocks), including all control frames.
Syntax: Counter32
Max-Access: Read-only
bscCUDataFramesSent
The number of sent data frames (blocks).
Syntax: Counter32
Max-Access: Read-only
bscCUDataFramesReceived
The number of received data frames (blocks).
Syntax: Counter32
Max-Access: Read-only
bscCUSoftErrors
The number of soft errors; these are errors that are recovered. This includes cyclic redundancy check (CRC) errors received, frames that were retransmitted for any reason (NAK received or the wrong ACK received), etc. The count measures the quality of the connection, but should be considered in relation to the amount of traffic on the connection (frames or bytes sent and received).
Syntax: Counter32
Max-Access: Read-only
bscCUHardErrors
The number of hard errors; these are errors that have not been recovered after bscPortRecoveryRetries number of retries, and therefore the connection has been terminated.
These errors could be caused by a hardware error in the link or in the remote device; or possibly the bscPortRecoveryRetries value is set too low for the quality of the connection.
Syntax: Counter32
Max-Access: Read-only
bscCUProtocolViolations
The number of protocol violations. This counter is incremented when an unexpected BSC data link control character is received from the remote device; that is, the control character is invalid in the current state of the local BSC FSM.
This number indicates that there is an incompatibility between the two implementations of the BSC protocol.
Syntax: Counter32
Max-Access: Read-only
End of Table
Blocked Serial Tunnel (BSTUN) Group
The variables in this section provide configuration and operational information for Cisco's blocked serial tunneling (BSTUN) implementation.
bstunIPAddr
The configured IP address used by the BSTUN component in this router.
Syntax: IpAddress
Max-Access: Read-only
bstunGroupTable
This table contains objects that represent BSTUN groups configured on the router. Each BSTUN-enabled interface is assigned to a BSTUN group, and packets can only travel between BSTUN-enabled interfaces in the same group.
Syntax: SEQUENCE OF BstunGroupEntry
Max-Access: Not-accessible
bstunGroupIndex
The configured BSTUN group number. This number must match the BSTUN group number configured in the router at the other end of the BSTUN tunnel.
Syntax: Integer (1-225)
Max-Access: Not-accessible
bstunProtocolType
The protocol type for this BSTUN group.
Syntax: Integer 1 = BSC (Binary Synchronous Communications)
Max-Access: Read-only
bstunLocalAck
Indicates whether the BSTUN connection is locally acknowledged. A value of TRUE means that the BSTUN connection is locally acknowledged; FALSE means the BSTUN connection is not locally acknowledged.
Syntax: TruthValue
Max-Access: Read-only
bstunGroupUnroutableTransmit
The number of unroutable frames received by this group from the remote partner. They were unroutable because the address was not recognized; that is, there is no bstun route command configured for this address. This indicates that the configuration in this router is incompatible with the peer router.
Syntax: Counter 32
Max-Access: Read-only
bstunGroupUnroutableReceive
The number of frames received from a serial interface with an unsupported poll address. There may be several ports configured within this BSTUN group; a non-zero value in this field indicates that at least one of these ports is receiving frames for which there are no bstun route commands configured. This indicates that the configuration in this router is incompatible with the configuration in at least one of the attached devices.
Syntax: Counter32
Max-Access: Read-only
End of Table
bstunPortTable
This table contains a list of BSTUN-enabled interfaces (ports).
Syntax: SEQUENCE OF BstunPortEntry
Max-Access: Not-accessible
bstunPortGroupNumber
The group number to which the BSTUN port belongs. Frames will only be routed to other ports (on this or another router) in the same BSTUN group. This group should match the bstunGroupIndex in the bstunGroupTable.
Syntax: Integer (1-255)
Max-Access: Read-only
bstunPortDefaultPeerType
The type of identification of the remote default partner. (This is as configured with the route all command.) If the identification is IP then the value is in bstunPortDefaultPeerIP; if it is serial or serialDirect then the value is in bstunPortDefaultPeerSerial.
Syntax: Integer 1 = none, 2 = IP, 3 = serial, 4 = serialDirect
Max-Access: Read-only
bstunPortDefaultPeerIP
The IP address of the remote default BSTUN partner, for unrecognized addresses. This is 0.0.0.0 if the partner address type is not IP.
Syntax: IpAddress
Max-Access: Read-only
bstunPortDefaultPeerSerial
If the bstunRouteType is serial, this is the serial interface index of the point-to-point link to the remote partner. If the bstunRouteType is serialDirect, the remote partner is in the local BSTUN. If the bstunRouteType is IP, then this field is 0.
Syntax: InterfaceIndex
Max-Access: Read-only
bstunPortUnroutableReceive
The number of frames received from the serial interface with an unsupported poll address.
Syntax: Counter32
Max-Access: Read-only
End of Table
bstunRouteTable
This table contains information about specific poll addresses. There is one table entry for each address configured by the bstun route command.
Syntax: SEQUENCE OF BstunRouteEntry
Max-Access: Not-accessible
bstunRouteGroupIndex
The index of the BSTUN Group owning this station.
Syntax: Integer (1-255)
Max-Access: Not-accessible
bstunRouteStationAddress
The poll address of the station. 256 indicates the all parameter on the stun route command, which is the route for all unrecognized addresses.
Syntax: Integer (1-256)
Max-Access: Not-accessible
bstunRouteType
The type of identification of the remote partner. If the identification is IP, the value is in bstunRouteIP; if it is serial or serialDirect, then the value is in bstunRouteSerial.
Syntax: Integer 1 = none, 2 = ip, 3 = serial, 4 = serialDirect
Max-Access: Read-only
bstunRouteIP
The IP address of the remote BSTUN partner. This is 0.0.0.0 if the partner address type is not IP.
Syntax: IpAddress
Max-Access: Read-only
bstunRouteSerial
If bstunRouteType is serial, this is the serial interface index of the point-to-point link to the remote partner. If bstunRouteType is serialDirect, the remote partner is in the local BSTUN. If the bstunRouteType is IP, then this field is 0.
Syntax: InterfaceIndex
Max-Access: Read-only
bstunRoutePriority
The priority with which this station's traffic will be routed across the network.
Syntax: Integer 1 = low, 2 = normal, 3 = medium, 4 = high
Max-Access: Read-only
bstunRoutePeerState
The state of the peer connection through the BSTUN tunnel.
Syntax: Integer 1 = dead, 2 = closed, 3 = opening, 4 = openWait, 5 = connected, 6 = direct
Max-Access: Read-only
bstunRouteRxPackets
The number of frames received from the serial interface with this station's address.
Syntax: Counter32
Max-Access: Read-only
bstunRouteTxPackets
The number of frames transmitted at the serial interface with this station's address.
Syntax: Counter32
Max-Access: Read-only
bstunRouteRxBytes
The number of bytes received from the serial interface with this station's address.
Syntax: Counter32
Max-Access: Read-only
bstunRouteTxBytes
The number of bytes transmitted at the serial interface with this station's address.
Syntax: Counter32
Max-Access: Read-only
End of Table
Notification for Blocked Serial Tunnel Group
The following notification is supported with the BSTUN MIB:
bstunPeerStateChangeNotification
This notification indicates that the state of a BSTUN route has transitioned to active (connected) or inactive (dead or closed).
ciscoVINES Group
The MIB module in this section describes the management of VINES routing information in Cisco devices.
cvBasicNetwork
Specifies the VINES network number of this router.
Syntax: VinesNetworkNumber
Max-Access: Read-only
cvBasicHost
Specifies the VINES host (subnetwork) number of this router.
Syntax: VinesHostNumber
Max-Access: Read-only
cvBasicNextClient
Specifies the next VINES client host (subnetwork) number to be assigned by this router.
Syntax: VinesHostNumber
Max-Access: Read-only
Neighbor Table
The Cisco VINES Neighbor Table contains the objects listed in this section.
cvForwNeighborNeighborCount
Specifies the number of neighbors in the neighbor table, cvForwNeighborTable.
Syntax: Gauge32
Max-Access: Read-only
cvForwNeighborPathCount
Specifies the number of paths in the neighbor table, cvForwNeighborTable.
Syntax: Gauge32
Max-Access: Read-only
cvForwNeighborVersion
Specifies the version number of the neighbor table, cvForwNeighborTable, which is incremented each time a route or path is added or deleted.
Syntax: Integer32
Max-Access: Read-only
cvForwNeighborTable
Specifies a table of information about neighbors of this router.
Syntax: SEQUENCE OF CvForwNeighborEntry
Max-Access: Not-accessible
cvForwNeighborNetwork
Specifies the network part of the neighbor's VINES internet address.
Syntax: VinesNetworkNumber
Max-Access: Not-accessible
cvForwNeighborHost
Specifies the host part of the neighbor's VINES internet address.
Syntax: VinesHostNumber
Max-Access: Not-accessible
cvForwNeighborPhysAddress
Specifies the neighbor's physical address on the network interface as indicated by this entry's ifIndex and interpreted according to ifType at ifIndex in ifTable.
Syntax: PhysAddress
Max-Access: Not-accessible
cvForwNeighborSource
Specifies the source of this entry.
Syntax: Integer 1 = unrecognized, 2 = self, 3= rtpRedirect, 4 = rtpUpdate, 5 = manualRoute, 6 = igrp, 7 = test, 8 = manualNeighbor
Max-Access: Read-only
cvForwNeighborRtpVersion
Specifies the version of RTP through which the entry was learned.
Syntax: Integer32 (0-255)
Max-Access: Read-only
cvForwNeighborUsageType
Specifies the way in which this path will be used to forward a message.
Syntax: Integer 1 = next, 2 = roundRobin, 3 = backup
Max-Access: Read-only
cvForwNeighborAge
Specifies the age of the entry, in seconds. The value -1 indicates not applicable for RTP Version 0 neighbors on WAN interfaces when the interface is configured for delta-only updates.
Syntax: Integer32 (-1-65535)
Max-Access: Read-only
cvForwNeighborMetric
Specifies the expected one-way delay to send a message to this neighbor
Syntax: VinesMetric
Max-Access: Read-only
cvForwNeighborUses
Specifies the number of times the path has been used to forward a message for all cvForwNeighborSource values except "manualRoute." For a "manualRoute," the cvForwNeighborUses variable specifies the number of static routes that use this neighbor as its first hop.
Syntax: Counter32
Max-Access: Read-only
End of Table
VINES Route Table
The VINES Route table contains the objects specified in this section.
cvForwRouteRouterCount
Specifies the number of routers (servers) in the route table, cvForwRouteTable.
Syntax: Gauge32
Max-Access: Read-only
cvForwRouteRouteCount
Specifies the number of routes in the route table, cvForwRouteTable.
Syntax: Gauge32
Max-Access: Read-only
cvForwRouteVersion
Specifies the version number of the route table, cvForwRouteTable, incremented each time a route or server (router) is added or deleted.
Syntax: Integer32
Max-Access: Read-only
cvForwRouteUpdateCountdown
Specifies the number of seconds until the next routing update.
Syntax: Gauge32
Max-Access: Read-only
cvForwRouteTable
Specifies a table of information about routes from this router to other VINES networks.
Syntax: SEQUENCE OF CvForwRouteEntry
Max-Access: Not-accessible
cvForwRouteNetworkNumber
Specifies the remote network's VINES network number.
Syntax: VinesNetworkNumber
Max-Access: Not-accessible
cvForwRouteNeighborNetwork
Specifies the network part of the VINES internetwork address of the neighbor that is the next hop to the remote network. Because the neighbor is a router by definition, its host number is 1.
Syntax: VinesNetworkNumber
Max-Access: Not-accessible
cvForwRouteSource
Specifies the source of this entry.
Syntax: Integer 1 = unrecognized, 2 = self, 3 = rtpRedirect, 4 = rtpUpdate, 5 = manualRoute, 6 = igrp, 7 = test
Max-Access: Read-only
cvForwRouteRtpVersion
Specifies the version of RTP through which the entry was learned.
Syntax: Integer32 (0-255)
Max-Access: Read-only
cvForwRouteUseNext
Specifies whether this route is the one to use next to get to the remote network.
Syntax: TruthValue
Max-Access: Read-only
cvForwRouteForwardBroadcast
Specifies whether this route will be used to forward a broadcast from a serverless network.
Syntax: TruthValue
Max-Access: Read-only
cvForwRouteSuppress
Specifies whether this route is temporarily being suppressed as normal operation before eventually advertising it.
Syntax: TruthValue
Max-Access: Read-only
cvForwRouteLoadShareEligible
Specifies whether this route is eligible for load sharing because its metric is equal to the best metric for the same neighbor.
Syntax: TruthValue
Max-Access: Read-only
cvForwRouteAge
Specifies the age of the entry, in seconds. The value -1 indicates not applicable for RTP Version 0 neighbors on WAN interfaces when the interface is configured for delta-only updates.
Syntax: Integer32 (-1-65535)
Max-Access: Read-only
cvForwRouteMetric
Specifies the expected one-way delay, in milliseconds to send a message on this route.
Syntax: VinesMetric
Max-Access: Read-only
cvForwRouteUses
Specifies the number of times the route has been used to forward a message.
Syntax: Counter32
Max-Access: Read-only
Global Total Counters
The global total counters used by the Cisco VINES MIB contains objects listed in this section.
cvTotalInputPackets
Specifies the total count of number of VINES input packets.
Syntax: Counter32
Max-Access: Read-only
cvTotalOutputPackets
Specifies the total count of number of VINES output packets.
Syntax: Counter32
Max-Access: Read-only
cvTotalLocalDestPackets
Specifies the total count of VINES input packets for this host.
Syntax: Counter32
Max-Access: Read-only
cvTotalForwardedPackets
Specifies the total count of number of VINES packets forwarded.
Syntax: Counter32
Max-Access: Read-only
cvTotalBroadcastInPackets
Specifies the total count of number of VINES input broadcast packets.
Syntax: Counter32
Max-Access: Read-only
cvTotalBroadcastOutPackets
Specifies the total count of number of VINES output broadcast packets.
Syntax: Counter32
Max-Access: Read-only
cvTotalBroadcastForwardPackets
Specifies the total count of number of VINES broadcast packets forwarded.
Syntax: Counter32
Max-Access: Read-only
cvTotalLanOnlyPackets
Specifies the total count of number of VINES broadcast packets not forwarded to all interfaces because the LAN ONLY bit was set.
Syntax: Counter32
Max-Access: Read-only
cvTotalNotOver4800Packets
Specifies the total count of number of VINES broadcast packets not forwarded to all interfaces because the OVER 4800 BPS bit was set.
Syntax: Counter32
Max-Access: Read-only
cvTotalNoChargesPackets
Specifies the total count of number of VINES broadcast packets not forwarded to all interfaces because the NO CHARGES only bit was set.
Syntax: Counter32
Max-Access: Read-only
cvTotalFormatErrors
Specifies the total count of VINES input packets with header errors.
Syntax: Counter32
Max-Access: Read-only
cvTotalChecksumErrors
Specifies the total count of VINES input packets with checksum errors.
Syntax: Counter32
Max-Access: Read-only
cvTotalHopCountsExceeded
Specifies the total count of VINES input packets that have exceeded the maximum hop count.
Syntax: Counter32
Max-Access: Read-only
cvTotalNoRouteDrops
Specifies the total count of VINES packets dropped due to no route.
Syntax: Counter32
Max-Access: Read-only
cvTotalEncapsFailedDrops
Specifies the total count of VINES packets dropped due to output encapsulation failed.
Syntax: Counter32
Max-Access: Read-only
cvTotalUnknownPackets
Specifies the total count of unknown VINES input packets.
Syntax: Counter32
Max-Access: Read-only
cvTotalIcpInPackets
Specifies the total count of VINES ICP packets received.
Syntax: Counter32
Max-Access: Read-only
cvTotalIcpOutPackets
Specifies the total count of VINES ICP packets generated.
Syntax: Counter32
Max-Access: Read-only
cvTotalMetricOutPackets
Specifies the total count of VINES ICP Metric Notification packets generated.
Syntax: Counter32
Max-Access: Read-only
cvTotalMacEchoInPackets
Specifies the total count of VINES MAC level Echo packets received.
Syntax: Counter32
Max-Access: Read-only
cvTotalMacEchoOutPackets
Specifies the total count of VINES MAC level Echo packets generated.
Syntax: Counter32
Max-Access: Read-only
cvTotalEchoInPackets
Specifies the total count of VINES Echo packets received.
Syntax: Counter32
Max-Access: Read-only
cvTotalEchoOutPackets
Specifies the total count of VINES Echo packets generated.
Syntax: Counter32
Max-Access: Read-only
cvTotalProxyOutPackets
Specifies the total count of proxy packets sent.
Syntax: Counter32
Max-Access: Read-only
cvTotalProxyReplyOutPackets
Specifies the total count of responses to proxy packets.
Syntax: Counter32
Max-Access: Read-only
Interface Configuration Table
The Interface Configuration Table (cvInterface) contains the objects listed in this section.
cvIfConfigMetric
Specifies the VINES protocol metric value.
Syntax: VinesMetric
Max-Access: Read-only
cvIfConfigEncapsulation
Specifies the VINES protocol default encapsulation.
Syntax: Integer 1 = ARPA, 2 = TokenRing, 3 = SNAP
Max-Access: Read-only
cvIfConfigAccesslist
Specifies the VINES protocol outgoing access list number.
Syntax: Integer32
Max-Access: Read-only
cvIfConfigPropagate
Specifies the VINES protocol propagation control.
Syntax: Integer 1 = never, 2 = always, 3 = dynamic
Max-Access: Read-only
cvIfConfigArpEnabled
Specifies the VINES protocol arp replies enabled.
Syntax: Integer 1 = never, 2 = always, 3 = dynamic
Max-Access: Read-only
cvIfConfigServerless
Specifies that VINES protocol serverless support is enabled.
Syntax: Integer 1 = never, 2 = dynamic, 3 = always, 4 = alwaysBroadcast
Max-Access: Read-only
cvIfConfigRedirectInterval
Specifies the VINES protocol redirect interval in milliseconds.
Syntax: Integer32
Max-Access: Read-only
cvIfConfigSplitDisabled
Specifies that the VINES protocol split horizon is disabled.
Syntax: TruthValue
Max-Access: Read-only
cvIfConfigLineup
Specifies whether the VINES protocol line is up or down.
Syntax: TruthValue
Max-Access: Read-only
cvIfConfigFastokay
Specifies whether the VINES protocol fast switching is supported.
Syntax: TruthValue
Max-Access: Read-only
cvIfConfigRouteCache
Specifies whether the VINES protocol fast switching was requested.
Syntax: TruthValue
Max-Access: Read-only
cvIfConfigInputRouterFilter
Specifies the VINES protocol filter on received routing information source address.
Syntax: Integer32
Max-Access: Read-only
cvIfConfigInputNetworkFilter
Specifies the VINES protocol filter on received routing information content.
Syntax: Integer32
Max-Access: Read-only
cvIfConfigOutputNetworkFilter
Specifies the VINES protocol filter on transmitted routing information content.
Syntax: Integer32
Max-Access: Read-only
End of Table
Interface Input Counter Table
The Interface Input Counter Table (cvIfCountInTable) contains the objects listed in this section.
cvIfCountInNotEnabledDrops
Specifies the VINES protocol count of input packets that were discarded because the interface was not configured.
Syntax: Counter32
Max-Access: Read-only
cvIfCountInFormatErrors
Specifies the VINES protocol count of input packets with format errors.
Syntax: Counter32
Max-Access: Read-only
cvIfCountInLocalDestPackets
Specifies the VINES protocol count of input packets destined for this router.
Syntax: Counter32
Max-Access: Read-only
cvIfCountInBroadcastPackets
Specifies the VINES protocol input broadcast count.
Syntax: Counter32
Max-Access: Read-only
cvIfCountInForwardedPackets
Specifies the VINES protocol count of input packets forwarded to another interface.
Syntax: Counter32
Max-Access: Read-only
cvIfCountInNoRouteDrops
Specifies the VINES protocol count of input packets that were dropped because there was no route to the destination.
Syntax: Counter32
Max-Access: Read-only
cvIfCountInZeroHopCountDrops
Specifies the VINES protocol count of input packets that were dropped due to a zero hop count.
Syntax: Counter32
Max-Access: Read-only
cvIfCountInChecksumErrors
Specifies the VINES protocol count of input packets with checksum errors.
Syntax: Counter32
Max-Access: Read-only
cvIfCountInArpQueryRequests
Specifies the VINES protocol count of input ARP Query Request messages.
Syntax: Counter32
Max-Access: Read-only
cvIfCountInArpQueryResponses
Specifies the VINES protocol count of input ARP Query Response messages.
Syntax: Counter32
Max-Access: Read-only
cvIfCountInArpAssignmentRequests
Specifies the VINES protocol count of input ARP Assignment Request messages.
Syntax: Counter32
Max-Access: Read-only
cvIfCountInArpAssignmentResponses
Specifies the VINES protocol count of input ARP Assignment Response messages.
Syntax: Counter32
Max-Access: Read-only
cvIfCountInArpIllegalMessages
Specifies the VINES protocol count of input illegal ARP messages.
Syntax: Counter32
Max-Access: Read-only
cvIfCountInIcpErrorMessages
Specifies the VINES protocol count of input ICP error messages.
Syntax: Counter32
Max-Access: Read-only
cvIfCountInIcpMetricMessages
Specifies the VINES protocol count of input ICP metric messages.
Syntax: Counter32
Max-Access: Read-only
cvIfCountInIcpIllegalMessages
Specifies the VINES protocol count of input illegal ICP messages.
Syntax: Counter32
Max-Access: Read-only
cvIfCountInIpcMessages
Specifies the VINES protocol count of input IPC messages.
Syntax: Counter32
Max-Access: Read-only
cvIfCountInRtp0Messages
Specifies the VINES protocol count of input RTP type 0 messages.
Syntax: Counter32
Max-Access: Read-only
cvIfCountInRtp1Messages
Specifies the VINES protocol count of input RTP Request messages.
Syntax: Counter32
Max-Access: Read-only
cvIfCountInRtp2Messages
Specifies the VINES protocol count of input RTP type 2 messages.
Syntax: Counter32
Max-Access: Read-only
cvIfCountInRtp3Messages
Specifies the VINES protocol count of input RTP type 3 messages.
Syntax: Counter32
Max-Access: Read-only
cvIfCountInRtpUpdateMessages
Specifies the VINES protocol count of input RTP Update messages.
Syntax: Counter32
Max-Access: Read-only
cvIfCountInRtpResponseMessages
Specifies the VINES protocol count of input RTP Response messages.
Syntax: Counter32
Max-Access: Read-only
cvIfCountInRtpRedirectMessages
Specifies the VINES protocol count of input RTP Redirect messages.
Syntax: Counter32
Max-Access: Read-only
cvIfCountInRtpIllegalMessages
Specifies the VINES protocol count of input illegal RTP messages.
Syntax: Counter32
Max-Access: Read-only
cvIfCountInSppMessages
Specifies the VINES protocol count of input SPP messages.
Syntax: Counter32
Max-Access: Read-only
cvIfCountInIpUnknownProtocols
Specifies the VINES protocol count of input packets of unknown VINES protocols.
Syntax: Counter32
Max-Access: Read-only
cvIfCountInIpcUnknownPorts
Specifies the VINES protocol count of input packets of unknown VINES IPC ports.
Syntax: Counter32
Max-Access: Read-only
cvIfCountInBroadcastsHelpered
Specifies the VINES protocol count of input packets helpered to another server.
Syntax: Counter32
Max-Access: Read-only
cvIfCountInBroadcastsForwarded
Specifies the VINES protocol input broadcast forwarded to other interface(s).
Syntax: Counter32
Max-Access: Read-only
cvIfCountInBroadcastDuplicates
Specifies the VINES protocol input duplicate broadcast count.
Syntax: Counter32
Max-Access: Read-only
cvIfCountInEchoPackets
Specifies the VINES protocol count of input IPC echo messages.
Syntax: Counter32
Max-Access: Read-only
cvIfCountInMacEchoPackets
Specifies the VINES protocol count of input MAC layer echo frames.
Syntax: Counter32
Max-Access: Read-only
cvIfCountInProxyReplyPackets
Specifies the VINES protocol count of responses to proxy packets.
Syntax: Counter32
Max-Access: Read-only
End of Table
Interface Output Counter Table
The VINES interface output counter table (cvIfCountOutTable) contains the objects in this section.
cvIfCountOutUnicastPackets
Specifies the VINES protocol unicast packets generated.
Syntax: Counter32
Max-Access: Read-only
cvIfCountOutBroadcastPackets
Specifies the VINES protocol broadcast packets generated.
Syntax: Counter32
Max-Access: Read-only
cvIfCountOutForwardedPackets
Specifies the VINES protocol count of forwarded packets.
Syntax: Counter32
Max-Access: Read-only
cvIfCountOutEncapsulationFailures
Specifies the VINES protocol output encapsulation failures.
Syntax: Counter32
Max-Access: Read-only
cvIfCountOutAccessFailures
Specifies the VINES protocol output access list failures.
Syntax: Counter32
Max-Access: Read-only
cvIfCountOutDownFailures
Specifies the VINES protocol output interface down count.
Syntax: Counter32
Max-Access: Read-only
cvIfCountOutPacketsNotBroadcastToSource
Specifies the VINES protocol output broadcast not sent because interface leads back to the source.
Syntax: Counter32
Max-Access: Read-only
cvIfCountOutPacketsNotBroadcastLanOnly
Specifies the VINES protocol output broadcast not sent due to Lan Only class.
Syntax: Counter32
Max-Access: Read-only
cvIfCountOutPacketsNotBroadcastNotOver4800
Specifies the VINES protocol output broadcast not sent due to High Speed class.
Syntax: Counter32
Max-Access: Read-only
cvIfCountOutPacketsNotBroadcastNoCharge
Specifies the VINES protocol output broadcast not sent due to No Charges class.
Syntax: Counter32
Max-Access: Read-only
cvIfCountOutBroadcastsForwarded
Specifies the VINES protocol output broadcast forwarded from another interface.
Syntax: Counter32
Max-Access: Read-only
cvIfCountOutBroadcastsHelpered
Specifies the VINES protocol output broadcast helpered to a VINES server.
Syntax: Counter32
Max-Access: Read-only
cvIfCountOutArpQueryRequests
Specifies the VINES protocol count of output ARP Query Request messages.
Syntax: Counter32
Max-Access: Read-only
cvIfCountOutArpQueryResponses
Specifies the VINES protocol count of output ARP Query Response messages.
Syntax: Counter32
Max-Access: Read-only
cvIfCountOutArpAssignmentRequests
Specifies the VINES protocol count of output ARP Assignment Request messages.
Syntax: Counter32
Max-Access: Read-only
cvIfCountOutArpAssignmentResponses
Specifies the VINES protocol count of input ARP Assignment Response messages.
Syntax: Counter32
Max-Access: Read-only
cvIfCountOutIcpErrorMessages
Specifies the VINES protocol count of output IPC Error messages.
Syntax: Counter32
Max-Access: Read-only
cvIfCountOutIcpMetricMessages
Specifies the VINES protocol count of output IPC metric messages.
Syntax: Counter32
Max-Access: Read-only
cvIfCountOutIpcMessages
Specifies the VINES protocol count of output ICP messages.
Syntax: Counter32
Max-Access: Read-only
cvIfCountOutRtp0Messages
Specifies the VINES protocol count of output RTP type 0 messages.
Syntax: Counter32
Max-Access: Read-only
cvIfCountOutRtpRequestMessages
Specifies the VINES protocol count of output RTP Request messages.
Syntax: Counter32
Max-Access: Read-only
cvIfCountOutRtp2Messages
Specifies the VINES protocol count of output RTP type 2 messages.
Syntax: Counter32
Max-Access: Read-only
cvIfCountOutRtp3Messages
Specifies the VINES protocol count of output RTP type 3 messages.
Syntax: Counter32
Max-Access: Read-only
cvIfCountOutRtpUpdateMessages
Specifies the VINES protocol count of output RTP Update messages.
Syntax: Counter32
Max-Access: Read-only
cvIfCountOutRtpResponseMessages
Specifies the VINES protocol count of output RTP Response messages.
Syntax: Counter32
Max-Access: Read-only
cvIfCountOutRtpRedirectMessages
Specifies the VINES protocol count of output RTP Redirect messages.
Syntax: Counter32
Max-Access: Read-only
cvIfCountOutSppMessages
Specifies the VINES protocol count of output SPP messages.
Syntax: Counter32
Max-Access: Read-only
cvIfCountOutEchoPackets
Specifies the VINES protocol count of output IPC echo messages.
Syntax: Counter32
Max-Access: Read-only
cvIfCountOutMacEchoPackets
Specifies the VINES protocol count of output IPCMAC layer echo frames.
Syntax: Counter32
Max-Access: Read-only
cvIfCountOutProxyPackets
Specifies the VINES protocol count of proxy packets sent.
Syntax: Counter32
Max-Access: Read-only
ciscoDiscovery Protocol Group
The MIB module in this section describes the management of the Cisco Discovery Protocol (CDP) in Cisco devices.
cdpInterfaceTable
The (conceptual) table containing the status of CDP on the device's interfaces.
Syntax: SEQUENCE OF CdpInterfaceEntry
Max-Access: Not-accessible
cdpInterfaceEntry
Specifies an entry (conceptual row) in the cdpInterfaceTable containing the status of CDP on an interface.
Syntax: CdpInterfaceEntry
Max-Access: Not-accessible
cdpInterfaceIfIndex
Specifies the ifIndex value of the local interface. For 802.3 Repeaters on which the repeater ports do not have ifIndex values assigned, this value is a unique value for the port, and greater than any ifIndex value supported by the repeater; in this case, the specific port is indicated by corresponding values of cdpInterfaceGroup and cdpInterfacePort, where these values correspond to the group number and port number values of RFC 1516.
Syntax: Integer32
Max-Access: Not-accessible
cdpInterfaceEnable
Provides an indication of whether the Cisco Discovery Protocol is currently running on this interface.
Syntax: TruthValue
Max-Access: Read-write
cdpInterfaceMessageInterval
Specifies the interval at which CDP messages are to be generated on this interface. The default value is 60 seconds.
Syntax: Integer (10-300). Units are in seconds.
Max-Access: Read-write
cdpInterfaceGroup
This object is only relevant to interfaces that are repeater ports on 802.3 repeaters. In this situation, it indicates the RFC1516 group number of the repeater port which corresponds to this interface.
Syntax: Integer32
Max-Access: Read-only
cdpInterfacePort
This object is only relevant to interfaces that are repeater ports on 802.3 repeaters. In this situation, it indicates the RFC1516 port number of the repeater port that corresponds to this interface.
Syntax: Integer32
Max-Access: Read-only
End of Table
cdpCacheTable
Specifies the (conceptual) table containing the cached information obtained by means of receiving CDP messages.
Syntax: SEQUENCE OF CdpCacheEntry
Max-Access: Not-accessible
cdpCacheEntry
Specifies an entry (conceptual row) in the cdpCacheTable containing the information received by means of CDP on one interface from one device.
Syntax: CdpCacheEntry
Max-Access: Not-accessible
cdpCacheIfIndex
Normally specifies the ifIndex value of the local interface. For 802.3 Repeaters for which the repeater ports do not have ifIndex values assigned, this value is a unique value for the port, and greater than any ifIndex value supported by the repeater; the specific port number, in this case, is given by the corresponding value of cdpInterfacePort.
Syntax: Integer32
Max-Access: Not-accessible
cdpCacheDeviceIndex
Specifies a unique value for each device from which CDP messages are being received.
Syntax: Integer32
Max-Access: Not-accessible
cdpCacheAddressType
Provides an indication of the type of address contained in the corresponding instance of cdpCacheAddress.
Syntax: CiscoNetworkProtocol
Max-Access: Read-only
cdpCacheAddress
Specifies the (first) network-layer address of the device's SNMP-agent as reported in the most recent CDP message. For example, if the the corresponding instance of cacheAddressType had the value ip(1), then this object would be an IP-address.
Syntax: CiscoNetworkAddress
Max-Access: Read-only
cdpCacheVersion
Specifies the Version string as reported in the most recent CDP message. The zero-length string indicates no Version field (TLV) was reported in the most recent CDP message.
Syntax: DisplayString
Max-Access: Read-only
cdpCacheDeviceId
Specifies the Device-ID string as reported in the most recent CDP message. The zero-length string indicates no Device-ID field (TLV) was reported in the most recent CDP message.
Syntax: DisplayString
Max-Access: Read-only
cdpCacheDevicePort
Specifies the Port-ID string as reported in the most recent CDP message. This will typically be the value of the ifName object (for example, Ethernet0). The zero-length string indicates no Port-ID field (TLV) was reported in the most recent CDP message.
Syntax: DisplayString
Max-Access: Read-only
cdpCachePlatform
Specifies the device's hardware platform as reported in the most recent CDP message. The zero-length string indicates that no Platform field (TLV) was reported in the most recent CDP message.
Syntax: DisplayString
Max-Access: Read-only
cdpCacheCapabilities
Specifies the device's functional capabilities as reported in the most recent CDP message. For latest set of specific values, see the latest version of the CDP specification. The zero-length string indicates no Capabilities field (TLV) was reported in the most recent CDP message.
Syntax: Octet string (SIZE (0-4))
Max-Access: Read-only
Cisco Integrated Services Digital Network (ISDN) MIB Group
This group describes the status of the ISDN Interfaces on Cisco devices.The ISDN hardware interface Basic Rate Interface (BRI) or Primary Rate Interface (PRI) is represented by the D channel. The interface has an ifType value of basicISDN(20) or primaryISDN(21). For related information, refer to RFC 1213.
Each B channel is also represented in an entry in the ifTable. The B channels has an ifType value of other(1). This model is used in defining objects and tables for management.
The ISDN MIB allows sub-layers. For example, the data transfer over a B channel can take place with PPP encapsulation. While the ISDN MIB describes the B channel, a media-specific MIB for PPP can be used on a layered basis, according to RFC 1573. The ISDN call information will be stored in the neighbor table.
demandNbrTable
Specifies the list of neighbors from which the router accepts calls or to which it places them.
Syntax: SEQUENCE OF DemandNbrEntry
Max-Access: Not-accessible
demandNbrEntry
Specifies a single Neighbor. This entry is effectively permanent, and contains information describing the neighbor, its permissions, its last call attempt, and its cumulative effects.
Syntax: DemandNbrEntry
Max-Access: Not-accessible
demandNbrPhysIf
Specifies the ifIndex value of the physical interface the neighbor is called on. On an ISDN interface, this is the ifIndex value of the D channel.
Syntax: Integer32 (1-2147483647)
Max-Access: Not-accessible
demandNbrId
Specifies an arbitrary sequence number associated with the neighbor.
Syntax: Integer32
Max-Access: Not-accessible
demandNbrLogIf
Specifies the ifIndex value of virtual interface associated with the neighbor.This interface maintains a queue of messages holding for the neighbor awaiting call completion, and all statistics.
Syntax: Integer32 (1-2147483647)
Max-Access: Read-create
demandNbrName
Specifies the ASCII name of the neighbor.
Syntax: DisplayString
Max-Access: Read-create
demandNbrAddress
Specifies the call address at which the neighbor should be called.Consider this address as the set of characters following "ATDT" or the "phone number" included in a D channel call request.
Syntax: DisplayString
Max-Access: Read-create
demandNbrPermission
Specifies the applicable permissions.
Syntax: Integer 1 = iCanCallHim, 2 = heCanCallMe, 3 = weCanCallEachOther
Max-Access: Read-create
demandNbrMaxDuration
Maximum call duration in seconds. Zero means "unlimited".
Syntax: Integer32 (1-2147483647)
Max-Access: Read-create
demandNbrLastDuration
Specifies the duration of last call in seconds.
Syntax: Integer32 (1-2147483647)
Max-Access: Read-only
demandNbrClearReason
Specifies the ASCII reason that the last call terminated.
Syntax: DisplayString
Max-Access: Read-only
demandNbrClearCode
Specifies the encoded reason for the last call tear down.
Syntax: Octet string
Max-Access: Read-only
demandNbrSuccessCalls
Specifies the number of completed calls to neighbor since system reset.
Syntax: Counter32
Max-Access: Read-only
demandNbrFailCalls
Specifies the number of call attempts that have failed.
Syntax: Counter32
Max-Access: Read-only
demandNbrAcceptCalls
Specifies the number of calls accepted from the neighbor.
Syntax: Counter32
Max-Access: Read-only
demandNbrRefuseCalls
Specifies the number of calls from the neighbor that have been refused.
Syntax: Counter32
Max-Access: Read-only
demandNbrLastAttemptTime
Specifies the sysUpTime of last call attempt.
Syntax: TimeStamp
Max-Access: Read-only
demandNbrStatus
Enables a new vendor to manage the device using SNMP.
Syntax: RowStatus
Max-Access: Read-create
End of Table
Trap related to connection management
This section describes the trap associated with the ciscoISDN MIB group.
demandNbrCallInformation
This trap/inform is sent to the manager whenever a successful call clears, or a failed call attempt is determined to have ultimately failed. In the event that call retry is active, then the trap is sent after all retry attempts have failed. However, only one such trap is sent in between successful call attempts; subsequent call attempts result in no trap.
Qualified Logical Link Control (QLLC) MIB Group
The QLLC MIB includes a managed entity or LS (link station). The managed entity includes objects needed to configure and monitor the logical connections.
QLLC Link Station Administrative Table (qllcLSAdminTable)
This table contains objects that can be changed for each QLLC entry. Changing one of these parameters will take effect in the operating LS immediately. Each QLLC connection will have an entry in this table.
Syntax: SEQUENCE OF QllcLSAdminEntry
Access: Not-accessible
qllcLSAdminIfIndex
Specifies the interface index value for the QLLC connection.
Syntax: IfIndexType
Max-Access: Read-write
qllcLSAdminLciVcIndex
Specifies the virtual circuit number for the logical channel identifier or PVC number depending on the type of circuit on this interface.
Syntax: IfIndexType
Max-Access: Read-write
qllcLSAdminCircuitType
Specifies the circuit type on this interface.
Syntax: Integer 1 = switchedVC, 2 = permanentVC
Max-Access: Read-write
qllcLSAdminRole
Specifies the role that the QLLC link station shall assume.
Syntax: Integer 1 = primary, 2 = secondary, 3 = peerToPeer
Max-Access: Read-write
qllcLSAdminX25Add
Specifies the X.25 address associated with the QLLC connection.
Syntax: X121Address
Max-Access: Read-write
qllcLSAdminModulo
Specifies the modulus for QLLC link station. It determines the size of the rotating ACK window and can take values of 8 and 128.
Syntax: Integer 1 = modulo8, 2 = modulo128
Max-Access: Read-write
qllcLSAdminLgX25
Specifies the largest QLLC packet allowed to go out on the QLLC/X.25 side.
Syntax: Integer32
Max-Access: Read-write
End of Table
QLLC Link Station Operational Table (qllcLSOperTable)
Specifies an entry for each QLLC connection.
qllcLSOperIfIndex
Specifies the interface index value for the QLLC connection.
Syntax: IfIndexType
Max-Access: Read-only
qllcLSOperLciVcIndex
Specifies the virtual circuit number for the logical channel identifier on this interface.
Syntax: IfIndexType
Max-Access: Read-only
qllcLSOperCircuitType
Specifies the circuit type on this interface.
Syntax: Integer 1 = switchedVC, 2 = permanentVC
Max-Access: Read-only
qllcLSOperRole
Specifies the role of the QLLC link station.
Syntax: Integer 1 = primary, 2 = secondary, 3 = peerToPeer
Max-Access: Read-only
qllcLSOperX25Add
Specifies the remote X.25 address associated with the QLLC connection.
Syntax: X121Address
Max-Access: Read-only
qllcLSOperModulo
The modulus for QLLC link station. It determines the size of the rotating ACK window and can take values of 8 and 128.
Syntax: Integer 1 = modulo8, 2 = modulo128
Max-Access: Read-only
qllcLSOperState
Specifies the state of a particular QLLC connection. Inop, closed, opening, closing, recovery, and opened are states defined in the IBM document SC30-3409-1, The X.25 1984/1988 DTE/DCE and DTE/DTE Interface Architecture Reference.
Syntax: Integer 1 = lsStateInop, 2 = lsStateClosed, 3 = lsStateOpening, 4 = lsStateClosing, 5 = lsStateRecovery, 6 = lsStateOpened
Max-Access: Read-only
qllcLSOperLgX25
Specifies the largest QLLC packet allowed to go out on the QLLC/X.25 side.
Syntax: Integer32
Max-Access: Read-only
End of Table
QLLC Link Station Statistics Table (qllcLSStatsTable)
The qllcLSStatsTable defines link station statistics kept for each QLLC connection.
qllcLSStatsEntry
Specifies the link station statistics.
Syntax: QllcLSStatsEntry
Max-Access: Not-accessible
qllcLSStatsIfIndex
Specifies the interface index value for the QLLC connection.
Syntax: IfIndexType
Max-Access: Read-only
qllcLSStatsLciVcIndex
Specifies the virtual circuit number for the logical channel identifier on this interface.
Syntax: IfIndexType
Max-Access: Read-only
qllcLSStatsXidIn
Specifies the number of XIDs received from the LS on this VC.
Syntax: Counter32
Max-Access: Read-only
qllcLSStatsXidOut
Specifies the number of XIDs sent to the LS on this VC.
Syntax: Counter32
Max-Access: Read-only
qllcLSStatsTestIn
Specifies the number of TEST packets received from the LS on this VC.
Syntax: Counter32
Max-Access: Read-only
qllcLSStatsTestOut
Specifies the number of TEST packets sent to the LS from this VC.
Syntax: Counter32
Max-Access: Read-only
qllcLSStatsQuenchOff
Specifies the number of times the connection quenched off for this connection.
Syntax: Counter32
Max-Access: Read-only
qllcLSStatsQuenchOn
Specifies the number of times the connection quenched on for this connection.
Syntax: Counter32
Max-Access: Read-only
qllcLSStatsInPaks
Specifies the total number of information packets received on this interface.
Syntax: Counter32
Max-Access: Read-only
qllcLSStatsOutPaks
Specifies the total number of information packets sent on this interface.
Syntax: Counter32
Max-Access: Read-only
qllcLSStatsInBytes
Specifies the total number of bytes in the information packets received on this connection.
Syntax: Counter32
Max-Access: Read-only
qllcLSStatsOutBytes
Specifies the total number of bytes in the information packets sent on this connection.
Syntax: Counter32
Max-Access: Read-only
qllcLSStatsNumRcvQsms
Specifies the number of QSMs received on this connection.
Syntax: Counter32
Max-Access: Read-only
qllcLSStatsNumSndQsms
Specifies the number of QSMs sent on this connection.
Syntax: Counter32
Max-Access: Read-only
qllcLSStatsNumRcvDiscs
Specifies the number of DISCs received on this connection.
Syntax: Counter32
Max-Access: Read-only
qllcLSStatsNumSndDiscs
Specifies the number of DISCs sent on this connection.
Syntax: Counter32
Max-Access: Read-only
qllcLSStatsNumRcvDms
Specifies the number of DMs received on this connection.
Syntax: Counter32
Max-Access: Read-only
qllcLSStatsNumSndDms
Specifies the number of DMs sent on this connection.
Syntax: Counter32
Max-Access: Read-only
qllcLSStatsNumRcvFrmrs
Specifies the number of FRMRs received on this connection.
Syntax: Counter32
Max-Access: Read-only
qllcLSStatsNumSndFrmrs
Specifies the number of FRMRs sent on this connection.
Syntax: Counter32
Max-Access: Read-only
qllcLSStatsNumDrops
Specifies the number of packets dropped due to buffer allocation or other internal problems.
Syntax: Counter32
Max-Access: Read-only
qllcLSStatsNumErrs
Specifies the number of HDLC protocol errors detected.
Syntax: Counter32
Max-Access: Read-only
End of Table
QLLC Link Station Admin Group (qllcLSAdminGroup)
This group specifies a collection of objects providing configuration capability.
qllcLSAdminIfIndex
Specifies the interface index value for the QLLC connection.
Syntax: IfIndexType
Max-Access: Read-write
qllcLSAdminLciVcIndex
Specifies the virtual circuit number for the logical channel identifier or PVC number depending on the type of circuit on this interface.
Syntax: IfIndexType
Max-Access: Read-write
qllcLSAdminRole
Specifies the role that the QLLC link station shall assume.
Syntax: Integer 1 = primary, 2 = secondary, 3 = peerToPeer
Max-Access: Read-write
qllcLSAdminCircuitType
Specifies the circuit type on this interface.
Syntax: Integer 1 = switchedVC, 2 = permanentVC
Max-Access: Read-write
qllcLSAdminX25Add
Specifies the X.25 address associated with the QLLC connection.
Syntax: X121Address
Max-Access: Read-write
qllcLSAdminModulo
Specifies the modulus for QLLC link station. It determines the size of the rotating ACK window and can take values of 8 and 128.
Syntax: Integer 1 = modulo8, 2 = modulo128
Max-Access: Read-write
qllcLSAdminLgX25
Specifies the largest QLLC packet allowed to go out on the QLLC/X.25 side.
Syntax: Integer32
Max-Access: Read-write
QLLC Link Station Operational Group (qllcLSOperGroup)
This group specifies a collection of objects providing operational control capability.
qllcLSOperIfIndex
Specifies the interface index value for the QLLC connection.
Syntax: IfIndexType
Max-Access: Read-only
qllcLSOperLciVcIndex
Specifies the virtual circuit number for the logical channel identifier on this interface.
Syntax: IfIndexType
Max-Access: Read-only
qllcLSOperCircuitType
Specifies the circuit type on this interface.
Syntax: Integer 1 = switchedVC, 2 = permanentVC
Max-Access: Read-only
qllcLSOperRole
Specifies the role of the QLLC link station.
Syntax: Integer 1 = primary, 2 = secondary, 3 = peerToPeer
Max-Access: Read-only
qllcLSOperX25Add
Specifies the remote X.25 address associated with the QLLC connection.
Syntax: X121Address
Max-Access: Read-only
qllcLSOperModulo
The modulus for QLLC link station. It determines the size of the rotating ACK window and can take values of 8 and 128.
Syntax: Integer 1 = modulo8, 2 = modulo128
Max-Access: Read-only
qllcLSOperState
Specifies the state of a particular QLLC connection. Inop, closed, opening, closing, recovery, and opened are states defined in the IBM document SC30-3409-1, The X.25 1984/1988 DTE/DCE and DTE/DTE Interface Architecture Reference.
Syntax: Integer 1 = lsStateInop, 2 = lsStateClosed, 3 = lsStateOpening, 4 = lsStateClosing, 5 = lsStateRecovery, 6 = lsStateOpened
Max-Access: Read-only
qllcLSOperLgX25
Specifies the largest QLLC packet allowed to go out on the QLLC/X.25 side.
Syntax: Integer32
Max-Access: Read-only
QLLC Link Station Statistics Group (qllcLSStatsGroup)
This group specifies a collection of objects providing statistics.
qllcLSStatsEntry
Specifies the link station statistics.
Syntax: QllcLSStatsEntry
Max-Access: Not-accessible
qllcLSStatsIfIndex
Specifies the interface index value for the QLLC connection.
Syntax: IfIndexType
Max-Access: Read-only
qllcLSStatsLciVcIndex
Specifies the virtual circuit number for the logical channel identifier on this interface.
Syntax: IfIndexType
Max-Access: Read-only
qllcLSStatsXidIn
Specifies the number of XIDs received from the LS on this VC.
Syntax: Counter32
Max-Access: Read-only
qllcLSStatsXidOut
Specifies the number of XIDs sent to the LS on this VC.
Syntax: Counter32
Max-Access: Read-only
qllcLSStatsTestIn
Specifies the number of TEST packets received from the LS on this VC.
Syntax: Counter32
Max-Access: Read-only
qllcLSStatsTestOut
Specifies the number of TEST packets sent to the LS from this VC.
Syntax: Counter32
Max-Access: Read-only
qllcLSStatsQuenchOff
Specifies the number of times the connection quenched off for this connection.
Syntax: Counter32
Max-Access: Read-only
qllcLSStatsQuenchOn
Specifies the number of times the connection quenched on for this connection.
Syntax: Counter32
Max-Access: Read-only
qllcLSStatsInPaks
Specifies the total number of information packets received on this interface.
Syntax: Counter32
Max-Access: Read-only
qllcLSStatsOutPaks
Specifies the total number of information packets sent on this interface.
Syntax: Counter32
Max-Access: Read-only
qllcLSStatsInBytes
Specifies the total number of bytes in the information packets received on this connection.
Syntax: Counter32
Max-Access: Read-only
qllcLSStatsOutBytes
Specifies the total number of bytes in the information packets sent on this connection.
Syntax: Counter32
Max-Access: Read-only
qllcLSStatsNumRcvQsms
Specifies the number of QSMs received on this connection.
Syntax: Counter32
Max-Access: Read-only
qllcLSStatsNumSndQsms
Specifies the number of QSMs sent on this connection.
Syntax: Counter32
Max-Access: Read-only
qllcLSStatsNumRcvDiscs
Specifies the number of DISCs received on this connection.
Syntax: Counter32
Max-Access: Read-only
qllcLSStatsNumSndDiscs
Specifies the number of DISCs sent on this connection.
Syntax: Counter32
Max-Access: Read-only
qllcLSStatsNumRcvDms
Specifies the number of DMs received on this connection.
Syntax: Counter32
Max-Access: Read-only
qllcLSStatsNumSndDms
Specifies the number of DMs sent on this connection.
Syntax: Counter32
Max-Access: Read-only
qllcLSStatsNumRcvFrmrs
Specifies the number of FRMRs received on this connection.
Syntax: Counter32
Max-Access: Read-only
qllcLSStatsNumSndFrmrs
Specifies the number of FRMRs sent on this connection.
Syntax: Counter32
Max-Access: Read-only
qllcLSStatsNumDrops
Specifies the number of packets dropped due to buffer allocation or other internal problems.
Syntax: Counter32
Max-Access: Read-only
qllcLSStatsNumErrs
Specifies the number of HDLC protocol errors detected.
Syntax: Counter32
Max-Access: Read-only
CONV(ersion) MIB
The Qualified Logical Link Control (QLLC) conversion provides data link layer support for SNA communication. The CONV(ersion) MIB includes a managed entity (link station). The managed entity includes objects to configure and monitor the logical connections. Managed objects fall in one of the following categories:
•
•
This section is closely coupled with the qllcmib document and provides general conversion information that can be extended to support RSRB/SDLLC as well, but currently addresses only the QLLC aspects of the conversion module.
The permissions allowed on these objects are as follows:
•
•
CISCO-SNADLC-CONV-MIB
This is the MIB module for objects used to manage QLLC-to-SDLC and QLLC-to-LLC2 conversion.
QLLC Conversion Administrative Table (convQllcAdminTable)
This table contains objects that can be changed for each QLLC entry. Changing one of these parameters will take effect in the operating LS immediately. Each QLLC connection will have an entry in this table.
Syntax: SEQUENCE OF ConvQllcAdminEntry
Max-Access: Not-accessible
convQllcAdminEntry
Specifies configured parameter values for a specific QLLC connection.
Syntax: ConvQllcAdminEntry
Max-Access: Not-accessible
convQllcAdminVirtualMac
Specifies the virtual address assigned to the QLLC connection. It is in the form of 802.3, 802.5 MAC address.
Syntax: MacAddress
Max-Access: Read-write
convQllcAdminConversionType
Specifies the conversion that is being used. The conversion is from QLLC to one of unknown-conversion is not one of sdlc (QLLC to SDLC), llc (QLLC to LLC), or localAck (QLLC to local acknowledgment.)
Syntax: Integer 1 = unknown, 2 = sdlc, 3 = llc, 4 = localAck
Max-Access: Read-write
convQllcAdminSdlcAdd
Specifies the SDLC address associated with the QLLC connection.
Syntax: Integer (0-255)
Max-Access: Read-write
convQllcAdminPartner
Specifies the X.25 connection partner of the other DLC (SDLC or LLC2). It is in the form of 802.3, 802.5 MAC address.
Syntax: MacAddress
Max-Access: Read-write
convQllcAdminThisRing
Specifies that the Virtual ring number QLLC end-stations are on. It is used for LLC<->QLLC only.
Syntax: Integer32
Max-Access: Read-write
convQllcAdminBridgeNum
Specifies the Bridge number QLLC end-stations are on. It is used for LLC<->QLLC only.
Syntax: Integer32
Max-Access: Read-write
convQllcAdminTargetRing
Specifies the ring number LLC end-stations are on. It is used for LLC
<->QLLC only.Syntax: Integer32
Max-Access: Read-write
convQllcAdminLargestSDLC
Specifies the largest QLLC packet allowed to go out on the SDLC side.
Syntax: Integer32
Max-Access: Read-write
convQllcAdminLargestLLC2
Specifies the largest QLLC packet allowed to go out on the LLC2 side.
Syntax: Integer32
Max-Access: Read-write
convQllcAdminLSDsap
Specifies the LS destination sap address.
Syntax: Integer32
Max-Access: Read-write
convQllcAdminLSSsap
Specifies the LS source sap address.
Syntax: Integer32
Max-Access: Read-write
convQllcAdminLSXid
Specifies the QLLC XID that is being used for the particular connection.
Syntax: Octet string (SIZE (0 | 4))
Max-Access: Read-write
QLLC Conversion Operational Table (convQllcOperTable)
This table contains objects for each QLLC connection.
Syntax: SEQUENCE OF ConvQllcOperEntry
Max-Access: Not-accessible
convQllcOperEntry
Specifies the operational values for a specific QLLC connection.
Syntax: ConvQllcOperEntry
Max-Access: Not-accessible
convQllcOperVirtualMac
Specifies the virtual address assigned to the QLLC connection. It is in the form of 802.3, 802.5 MAC address.
Syntax: MacAddress
Max-Access: Read-only
convQllcOperConversionType
Specifies the conversion that is being used. The conversion is from QLLC to one of unknown; conversion is not one of the following sdlc-QLLC to SDLC llc-QLLC to LLC localAck-QLLC to local acknowledgment
Syntax: Integer 1 = unknown, 2 = sdlc, 3 = llc, 4 = localAck
Max-Access: Read-only
convQllcOperSdlcAdd
Specifies the SDLC address associated with the QLLC connection.
Syntax: Integer (0-255)
Max-Access: Read-only
convQllcOperPartner
Specifies the X.25 connection partner of the other DLC (SDLC or LLC2). It is in the form of 802.3, 802.5 MAC address.
Syntax: MacAddress
Max-Access: Read-only
convQllcOperThisRing
The Virtual ring number QLLC end-stations are on. It is used for LLC
<-> QLLC only.Syntax: Integer32
Max-Access: Read-only
convQllcOperBridgeNum
The Bridge number QLLC end-stations are on. It is used for LLC
<->QLLC only.Syntax: Integer32
Max-Access: Read-only
convQllcOperTargetRing
Specifies the ring number LLC end-stations are on. It is used for LLC
<->QLLC only.Syntax: Integer32
Max-Access: Read-only
convQllcOperLargestSDLC
Specifies the largest QLLC packet allowed to go out on the SDLC side.
Syntax: Integer32
Max-Access: Read-only
convQllcOperLargestLLC2
Specifies the largest QLLC packet allowed to go out on the LLC2 side.
Syntax: Integer32
Max-Access: Read-only
convQllcOperLSDsap
Specifies the LS destination sap address.
Syntax: Integer32
Max-Access: Read-only
convQllcOperLSSsap
Specifies the LS source sap address.
Syntax: Integer32
Max-Access: Read-only
convQllcOperLSXid
Specifies the QLLC XID that is being used for the particular connection.
Syntax: Octet string (SIZE (0 | 4))
Max-Access: Read-only
convQllcOperLnxState
Specifies the LNX state. Cisco uses similar states for both LNX and SNX.
Syntax: Integer 1 = lnxDisconnect, 2 = lnxDwQllc, 3 = lnxAwQllcPri, 4 = lnxAwNetQllcSec, 5 = lnxNetContactPending, 6 = lnxDwNet, 7 = lnxAwNet, 8 = lnxAwQllcSec, 9 = lnxAwConnect
Max-Access: Read-only
convQllcOperLsIfIndex
This object and convQllcOperLsLciVcIndex defines the corresponding row in the qllcLSOperTable in the cisco-qllc01-mib. The corresponding row is that for which this object and convQllcOperLsLciVcIndex match qllcLSOperIfIndex and qllcLSOperLciVcIndex in table qllcLSOperTable in cisco-qllc01-mib respectively.
Syntax: IfIndexType
Max-Access: Read-only
convQllcOperLsLciVcIndex
This object and convQllcOperLsLciVcIndex defines the corresponding row in the qllcLSOperTable in the cisco-qllc01-mib. The corresponding row is that for which this object and convQllcOperLsLciVcIndex match qllcLSOperIfIndex and qllcLSOperLciVcIndex in table qllcLSOperTable in cisco-qllc01-mib respectively.
Syntax: IfIndexType
Max-Access: Read-only
Snapshot Routing MIB Group
This is the MIB module for objects used to manage the Cisco Snapshot Routing MIB.
ciscoSnapshotForceActive
Forces the snapshot state to active for all entries of the ciscoSnapshotActivityTable whose ciscoSnapshotIfIndex value is specified as parameter. The interface must have been previously configured for snapshot routing, and be a client interface. Retrieval of this object returns the value of the interface that was last forced into the active state, or 0 if no interfaces have been forced into the active state since the router was reset.
Syntax: Integer32
Max-Access: Read-write
ciscoSnapshotInterfaceTable
The ciscoSnapshotInterfaceTable defines a list of pre-interface Snapshot Routing entries.
ciscoSnapshotInterfaceEntry
Specifies a pre-interface Snapshot Routing entry. A management station acting to create an entry should create the associated instance of the row status object. The management station should also modify, either in the same or in successive PDUs, the values for the other objects if the defaults are not appropriate. Once the appropriate instance of all the configuration objects have been created, either by an explicit SNMP set request or by default, the row status should be set to active to initiate the request.
Note
Syntax: CiscoSnapshotInterfaceEntry
Max-Access: Not-accessible
ciscoSnapshotIfIndex
Specifies the interface to which this entry pertains.
Syntax: InterfaceIndex
Max-Access: Not-accessible
ciscoSnapshotClient
When set to true, this router is the client snapshot router on the interface. When false, this router is the server snapshot router on the interface.
Syntax: TruthValue
Max-Access: Read-create
ciscoSnapshotDialer
Indicates whether snapshot routing on this interface uses Dial-on-Demand routing.
Syntax: TruthValue
Max-Access: Read-create
ciscoSnapshotActiveInterval
Specifies the amount of time in minutes during which routes may be exchanged between the client and server routers.
Syntax: Integer32 (5-1000)
Max-Access: Read-create
ciscoSnapshotQuietInterval
Specifies the amount of time in minutes during which routes are retained and frozen between active periods. An instance of this object may only be present if the value of the associated ciscoSnapshotClient object is true.
Syntax: Integer32 (8-100000)
Max-Access: Read-create
ciscoSnapshotRetryInterval
Specifies the amount of time in minutes to wait and retry a route exchange in the event that an active period elapses with no routes being exchanged. For example, if an interface is down (or a DDR phone number is busy, or a DDR interface is unavailable) during the active interval, instead of waiting for the amount of time specified by ciscoSnapshotQuietTime to elapse before an attempt is made to exchange routing updates again, the attempt is made after the amount of time specified by this object has elapsed. This value is calculated automatically based on the ciscoSnapshotActiveInterval. An instance of this object may only be present if the value of the associated ciscoSnapshotClient object is true.
Syntax: Integer32
Max-Access: Read-only
ciscoSnapshotIfUpAction
Specifies the action that takes place when the interface associated with this entry transitions to the "up" state while snapshot routing on the interface is in quiet mode.
A value of goActive will cause the immediate transition to the active state.
A value of noAction causes no such transition. Instead, the transition to the active state occurs normally when the current quiet period expires.
Going active immediately incurs extra routing protocol overhead, but allows a fresh set of routing updates to be exchanged each time the line is brought up. This is useful in a dial-on-demand routing environment.
An instance of this object may only be present if the value of the associated ciscoSnapshotClient object is true.
Syntax: Integer 1 = goActive, 2 = noAction
Max-Access: Read-create
ciscoSnapshotRowStatus
Specifies the status of this table entry. Once the entry status is set to active, the snapshot routing process is enabled for this interface.
Syntax: RowStatus
Max-Access: Read-create
ciscoSnapshotActivityTable
Specifies a list of snapshot routing activity entries.
Syntax: SEQUENCE OF CiscoSnapshotActivityEntry
Max-Access: Not-accessible
ciscoSnapshotActivityEntry
Specifies a snapshot routing activity entry. Entries in this table are added for active row entries in the ciscoSnapshotInterfaceTable. If a row entry in the ciscoSnapshotInterfaceTable is set to notInService, or deleted, associated entries in this table will be deleted.
Syntax: CiscoSnapshotActivityEntry
Max-Access: Not-accessible
ciscoSnapshotActivityIndex
Specifies an index value that uniquely identifies a Snapshot Activity Entry on a given interface.
Syntax: Integer32
Max-Access: Not-accessible
ciscoSnapshotActivityState
Specifies the current state of snapshot routing for this entry. active means that routing information may be exchanged. quiet, only present on a client snapshot interface, means that routes are frozen, and that no routing information may be exchanged until the active state is reentered. serverPostActive, only present on a server snapshot interface, means that the active period has expired, but routing information will still be accepted from (but not sent to) the associated client router. transitionToQuiet, and transitionToActive, only present on a client, are temporary states entered after the active state, wherein any down to up transition of the interface will cause a move to the quiet or active state, respectively. limbo is a temporary state for activity blocks that are in the process of being created or destroyed.
Syntax: Integer 1 = active, 2 = quiet, 3 = serverPostActive, 4 = transitionToQuiet, 5 = transitionToActive, 6 = limbo
Max-Access: Read-only
ciscoSnapshotActivityTimer
Specifies the time in minutes remaining in the current state.
Syntax: Integer32
Max-Access: Read-only
ciscoSnapshotExchangeTimer
Specifies the time in minutes during the last active state, in which protocol exchanges occurred. The minimum time required to allow updates to be exchanged for a "successful update cycle" is the greater of 3 minutes, or 1/2 the active time. If the ciscoSnapshotExchangeTimer is less than this, the quiet state will use the retry interval to determine when next to go active.
An instance of this object will only be present when the associated value of ciscoSnapshotClient is true for this interface.
Syntax: Integer32
Max-Access: Read-only
ciscoSnapshotDialerMap
Specifies the index of the dialer map entry associated with this snapshot activity record. A value of 0 indicates that no dialer map is associated with this entry. An instance of this object will only be present when the associated value of ciscoSnapshotClient is true.
Syntax: Integer32
Max-Access: Read-only
ciscoSnapshotSourceProtocol
Specifies the protocol of the host that initiated the snapshot routing activity associated with this record. An instance of this object will only be present when the associated value of ciscoSnapshotClient is false.
Syntax: CiscoNetworkProtocol
Max-Access: Read-only
ciscoSnapshotSourceAddress
Specifies the address of the host that initiated the snapshot routing activity associated with this record.An instance of this object will only be present when the associated value of ciscoSnapshotClient is false.
Syntax: CiscoNetworkAddress
Max-Access: Read-only
ciscoSnapshotProtocolsExchanged
Specifies an array of bits that indicates whether routing information has been exchanged for all protocols. The most significant bit of the first octet represents the protocol associated with CiscoNetworkProtocol value of 0; the least significant bit of the first octet represents the protocol associated with CiscoNetworkProtocol value of 7; the most significant bit of the second octet represents the protocol associated with the CiscoNetworkProtocol value of 8; and so forth.
Routing information for a given protocol has been exchanged if the associated bit is set. An instance of this object is only present when the associated value of ciscoSnapshotClient is true.
Syntax: Octet string
Max-Access: Read-only
Channel Interface Processor (CIP) Group
The CIP Group specifies the MIB module for objects used to manage the cisco channel interface processor card.
cipCardTable
The cipCardTable contains a list of values for the CIP card that can be obtained on a per cip-card basis and include the following variables: cipCardEntryIndex, cipCardEntryName, cipCardEntryTotalMemory, cipCardEntryFreeMemory, cipCardEntryCpuUtilization, and cipCardEntryTimeSinceLastReset. This table extends CardTable in the cisco.mib.
Syntax: SEQUENCE OF CipCardEntry
Max-Access: Not-accessible
cipCardEntryIndex
Specifies the index into the cipCardTable. (Not the physical chassis slot number but the Cisco chassis MIB cardindex.)
Syntax: UInteger32
Max-Access: Not-accessible
cipCardEntryName
Specifies the configured name for the CIP.
Syntax: DisplayString
Max-Access: Read-only
cipCardEntryTotalMemory
Specifies total memory on the card in kilobytes.
Syntax: UInteger32
Max-Access: Read-only
cipCardEntryFreeMemory
Specifies the total free memory on the card, that is the amount of memory in kilobytes not in use.
Syntax: UInteger32
Max-Access: Read-only
cipCardEntryCpuUtilization
Specifies the average percentage of time, over the last minute, that this processor was not idle.
Syntax: Integer (0-100)
Max-Access: Read-only
cipCardEntryTimeSinceLastReset
Specifies the number of seconds the CIP has been running.
Syntax: Counter32
Max-Access: Read-only
End of Table
cipCardDaughterBoardTable
This table contains a list of objects pertaining to the daughter board on the CIP card.
cipCardDtrBrdIndex
Specifies which daughter board is being referenced for a particular CIP card.
Syntax: UInteger32
Max-Access: Read-only
cipCardDtrBrdType
Indicates the channel path interface type.
Syntax: Integer 1 = escon (Enterprise System Connection), 2 = busAndTag
Max-Access: Read-only
cipCardDtrBrdStatus
Specifies that the microcode for the daughter board has been successfully loaded and is executing.
Syntax: TruthValue
Max-Access: Read-only
cipCardDtrBrdSignal
For ESCON, specifies that the LED has been seen, and synchronization has been established. ESCON is the fiber-optic connection from the IBM mainframe to the peripheral. This is layer 1 of the channel. Older technology (still in use) is called BUS and TAB and consists of two bulky copper cables. For Parallel Channel Adapter (PCA), specifies that the operational out has been sensed.
Syntax: TruthValue
Max-Access: Read-only
cipCardDtrBrdOnline
For ESCON, specifies that a path has been established with at least one channel. For PCA, specifies that the PCA is online to the channel. It will respond to at least one device address.
Syntax: TruthValue
Max-Access: Read-only
implicitIncidents
Counts the number of times the ESCON Processor recovers from an internal error.
Syntax: Counter32
Max-Access: Read-only
codeViolationErrors
Specifies the number of recognized code-violation errors. A trap is issued when this number exceeds the bit error rate threshold for ESCON. The bit error rate threshold is set at 15 error burst within a 5-minute period. An error burst is the time period of 1.5 seconds + or - 0.05 seconds during which one or more code violations errors occur.
Syntax: Counter32
Max-Access: Read-only
linkFailureSignalOrSyncLoss
Specifies the number of link failures recognized as a result of a loss of signal or loss of synchronization that persisted longer than the link interval duration. The link interval duration is 1 second with a tolerance of +1.5 seconds and -0 seconds.
Syntax: Counter32
Max-Access: Read-only
linkFailureNOSs
Specifies the number of link failures recognized as a result of the not-operational sequence (NOS).
Syntax: Counter32
Max-Access: Read-only
linkFailureSequenceTimeouts
Specifies the number of link failures recognized as a result of a connection recovery timeout or response timeout occurring while in transmit OLS state.
Syntax: Counter32
Max-Access: Read-only
linkFailureInvalidSequences
Specifies the number of link failures recognized as a result of an invalid sequence for Link-Level-Facility State. Either a UD or UDR sequence was recognized while in wait-for-offline-sequence state.
Syntax: Counter32
Max-Access: Read-only
linkIncidentTrapCause
Indicates the condition which caused the last SNMP trap.
Syntax: Integer
1 = liOther (reason other than what is defined in conditions 2-7),
2 = liStatus (indicates that the daughter board status has changed),
3 = liImplicit Incidents (indicates that a condition, that might cause the recognition of a link incident in the attached node, has occurred),
4 = liBERthreshold (indicates that the code violation error rate exceeded the threshold),
5 = liSignalOrSyncLoss (indicates a loss of signal or loss of synchronization that persisted longer than the link interval duration),
6 = liNotOperationalSequence (indicates the recognition of not-operational sequence, usually due to the operator taking the channel offline),
7 = liSequenceTimeouts (indicates a connection recovery timeout or response timeout occurring while in transmit OLS state),
8 = liInvalidSequences (indicates a UD or UDR sequence was recognized while in wait-for-offline-sequence state)Max-Access: Read-only
cipCard SubChannel Table
This table contains a list of objects pertaining to subchannel connections referenced by the CIP card or its daughter board.
cipCardSubChannelIndex
Indicates which subchannel is being referenced for a particular daughter board on a CIP card.
Syntax: UInteger32
Max-Access: Read-only
cipCardSubChannelConnections
Indicates the number of times a device was connected to the subchannel. For some devices, this correlates with the number of start subchannels.
Syntax: Counter32
Max-Access: Read-only
cipCardSubChannelCancels
Specifies the number of halt subchannels.
Syntax: Counter32
Max-Access: Read-only
cipCardSubChannelSelectiveResets
Specifies the number of selective resets.
Syntax: Counter32
Max-Access: Read-only
cipCardSubChannelSystemResets
Specifies the number of system resets.
Syntax: Counter32
Max-Access: Read-only
cipCardSubChannelDeviceErrors
Specifies the number of device level errors.
Syntax: Counter32
Max-Access: Read-only
cipCardSubChannelWriteBlocksDropped
Specifies the number of times a block was received by the channel and a router buffer was not available so the block was discarded.
Syntax: Counter32
Max-Access: Read-only
cipCardSubChannelLastSenseData
Specifies the last sense data sent to the channel by this device.
Syntax: Octet string (SIZE (2))
Access: Read-only
cipCardSubChannelLastSenseDataTime
Specifies the time when the last sense data was sent to the channel by this device.
Syntax: TimeStamp
Max-Access: Read-only
cipCardSubChannelCuBusies
Specifies the number of control unit busies sent to the channel when this device was requested.
Syntax: Counter32
Max-Access: Read-only
End of Table
cipCardClawTable
This table contains status and other information not covered in the following tables for the Common Link Access for Workstations (CLAW) protocol.
Syntax: SEQUENCE OF CipCardClawEntry
Max-Access: Not-accessible
cipCardClawIndex
Specifies which CLAW link is being referenced for a particular subchannel on a daughter board on a CIP card.
Syntax: UInteger32
Max-Access: Read-only
cipCardClawConnected
Specifies the CLAW connection status.
Syntax: TruthValue
Max-Access: Read-only
End of Table
cipCardClawConfigTable
Contains configuration information for the Common Link Access for Workstations (CLAW) protocol.
Syntax: SEQUENCE OF CipCardClawConfigEntry
Max-Access: Not-accessible
cipCardClawConfigEntry
Specifies a list of CLAW configuration values.
Syntax: CipCardClawConfigEntry
Max-Access: Not-accessible
cipCardClawConfigPath
Specifies the Hex path identifier for the switch port containing the fiber from the channel on the host to which this task connects. This is a concatenation of the switch port number, the channel logical address, and the control unit logical address. For a directly connected channel, the switch port number is usually 01.
Syntax: Octet string (SIZE (2))
Max-Access: Read-write
cipCardClawConfigDevice
Specifies Device address for the device the host will use to communicate with this task.
Syntax: Octet string (SIZE (2))
Max-Access: Read-write
cipCardClawConfigIpAddr
Specifies the IP address of the host application for this task.
Syntax: IpAddress
Max-Access: Read-write
cipCardClawConfigHostName
Specifies the CLAW host name for this CLAW device.
Syntax: DisplayString
Max-Access: Read-write
cipCardClawConfigRouterName
Specifies the CLAW router name for this CLAW device.
Syntax: DisplayString
Max-Access: Read-write
cipCardClawConfigHostAppl
Specifies the CLAW host application name for this CLAW connection.
Syntax: DisplayString
Max-Access: Read-write
cipCardClawConfigRouterAppl
Specifies the CLAW router application name for this CLAW connection.
Syntax: DisplayString
Max-Access: Read-write
End of Table
cipCardClawDataXferStatsTable
Specifies a list of objects pertaining to data transfer statistics per CLAW Logical Link.
Syntax: SEQUENCE OF CipCardClawDataXferStatsEntry
Max-Access: Not-accessible
cipCardClawDataXferStatsEntry
Specifies a list of daughter board statistics.
Syntax: CipCardClawDataXferStatsEntry
Max-Access: Not-accessible
cipCardClawDataXferStatsBlocksRead
Specifies the number of read data transfer channel command words (CCWs) from the channel perspective.
Syntax: Counter32
Max-Access: Read-only
cipCardClawDataXferStatsBlocksWritten
Specifies the number of successful write data transfer CCWs from the channel perspective.
Syntax: Counter32
Max-Access: Read-only
cipCardClawDataXferStatsBytesRead
Specifies the number of bytes successfully read from the channel perspective.
Syntax: Counter32
Max-Access: Read-only
cipCardClawDataXferStatsHCBytesRead
Specifies the number of bytes successfully read from the channel perspective. The HC (high capacity) objects are the 64-bit equivalent of their 32-bit counterparts modeled after RFC 1573.
Syntax: Counter64
Max-Access: Read-only
clawDataXferStatsBytesWritten
Specifies the number of bytes successfully written from the channel perspective.
Syntax: Counter32
Max-Access: Read-only
cipCardClawDataXferStatsHCBytesWritten
Specifies the number of bytes successfully written from the channel perspective. The HC (high capacity) objects are the 64-bit equivalent of their 32-bit counterparts modeled after RFC 1573.
Syntax: Counter64
Max-Access: Read-only
cipCardClawDataXferStatsReadBlocksDropped
Specifies the number of bytes written.
Syntax: Counter32
Max-Access: Read-only
cipCardClawDataXferStatsWriteBlocksDropped
Specifies the number of read blocks dropped.
Syntax: Counter32
Max-Access: Read-only
cipCardClawDataXferStatsBufferGetRetryCount
Specifies the number of times a buffer was requested and none was available.
Syntax: Counter32
Max-Access: Read-only
End of Table
cipCardTraps
The following notification is supported with the cipCard MIB:
cipCardLinkFailure
This trap indicates that a significant link event has been recognized, resulting in the degradation of the interface line quality.
Cisco CIP CSNA Group
The variables described in this section are used to manage the Cisco Channel Systems Network Architecture (CSNA) support on the Channel Interface Processor (CIP), also called the CSNA feature.
CipCardCsnaAdminTable
This table contains configuration information for the Channel Systems Network Architecture (CSNA) feature on the Channel Interface Processor (CIP).
Syntax: SEQUENCE OF CipCardCsnaAdminEntry
Max-Access: Not-accessible
cipCardCsnaAdminPath
The channel path for this Channel Systems Network Architecture table entry.
Syntax: ChannelPath
Max-Access: Read-create
cipCardCsnaAdminDevice
The two-octet hex device address for the device the SNA host will use to communicate with the CSNA feature on the CIP.
Syntax: ChannelDevice
Max-Access: Read-create
cipCardCsnaAdminBlockDelayTime
The block delay time is the maximum amount of time the CSNA feature can hold a set of requests before it must transmit the block to the host.
The block must be sent when this time has expired, even if the block has not reached the suggested block delay length.
Syntax: Integer (0-100)
Max-Access: Read-create
cipCardCsnaAdminBlockDelayLength
The block delay length (BDL) is the suggested size of a block before it is transmitted to the host.
The BDL is used to force a transmit of a block when all information currently being processed has been placed in the block and the real block size exceeds this BDL size. The size of the block can grow larger than the BDL size, but must never exceed the maximum block length before being transmitted.
Syntax: Integer (0-65535)
Max-Access: Read-create
cipCardCsnaAdminMaxBlockLength
The maximum block length is the maximum size that an inbound channel I/O block may attain before being sent to the host. The block must be smaller or equal to this value.
Syntax: Integer (4096-65535)
Max-Access: Read-create
cipCardCsnaAdminRowStatus
This object is used by a management station to create or delete the row entry in the cipCardCsnaAdminTable.
Upon successful creation of the row, an agent automatically creates a corresponding entry in the cipCardCsnaOperTable with the cipCardCsnaOperState equal to "inactive" (1).
The management station can initiate row deletion, by setting this value to "destroy" (6). The agent then deletes the rows corresponding to this CSNA instance from both the cipCardCsnaAdminTable and cipCardCsnaOperTable.
Syntax: RowStatus
Max-Access: Read-create
End of Table
CipCardCsnaOperTable
This table contains operation values and status information for the Channel Systems Network Architecture (CSNA) feature on the Channel Interface Processor (CIP).
Syntax: SEQUENCE OF CipCardCsnaOperEntry
Max-Access: Not-accessible
cipCardCsnaOperState
The current state of the CSNA entry.
The values have the following meanings:
closed = Link is closed
pendingOpen = An Open Subchannel command has been received from the host
open = Subchannel is open
pendingSetup = Host has queried for LAN info
setupComplete = LAN info has been sent to the host,
pendingClose = A Close Subchannel command has been received from the host.Syntax: Integer 0 = closed, 1 = pendingOpen, 2 = open, 3 = pendingSetup, 4 = setupComplete, 5 = pendingClose
Max-Access: Read-only
cipCardCsnaOperSlowDownState
The current state of the CSNA entry slow down condition. A channel turns on the slow down bit whenever insufficient buffering exists to receive data from the adjacent channel device.
The values have the following meanings:
normal = Link is not in slow down state, slowDownSent = The router has put VTAM into a slow down state, slowDownReceived = VTAM has put the router into a slow down state, slowDownSentReceived = Both VTAM and the router are in the slow down state.
Syntax: Integer 0 = normal, 1 = slowDownSent, 2 = slowDownReceived, 3 = slowDownSentReceived
Max-Access: Read-only
cipCardCsnaOperBlockDelayTime
The current block delay time value being used by this instance of CSNA path/device (subchannel).
Syntax: Integer (0-100)
Max-Access: Read-only
cipCardCsnaOperBlockDelayLength
The current block delay length being used by this instance of CSNA path/device (subchannel).
Syntax: Integer (0-65535)
Max-Access: Read-only
cipCardCsnaOperMaxBlockLength
The current maximum block length being used by this instance of CSNA path/device (subchannel).
Syntax: Integer (4096-65535)
Max-Access: Read-only
End of Table
CipCardCsnaStatsTable
This table contains statistics information for the Channel Systems Network Architecture (CSNA) feature on the Channel Interface Processor (CIP).
Syntax: SEQUENCE OF CipCardCsnaStatsEntry
Max-Access: Not-accessible
cipCardCsnaStatsBlocksTxd
The number of blocks transmitted.
Syntax: Counter32
Max-Access: Read-only
cipCardCsnaStatsBlocksRxd
The number of blocks received.
Syntax: Counter32
Max-Access: Read-only
cipCardCsnaStatsBytesTxd
The number of bytes transmitted.
Syntax: Counter32
Max-Access: Read-only
cipCardCsnaStatsHCBytesTxd
The number of bytes transmitted. This is a 64-bit (high-capacity) version of the cipCardCsnaStatsBytesTxd counter for use with SNMP Version 2 Managers.
Syntax: Counter64
Max-Access: Read-only
cipCardCsnaStatsBytesRxd
The number of bytes received.
Syntax: Counter32
Max-Access: Read-only
cipCardCsnaStatsHCBytesRxd
The number of bytes received. This is a 64-bit (high-capacity) version of the cipCardCsnaStatsBytesRxd counter for use with SNMP Version 2 Managers.
Syntax: Counter64
Max-Access: Read-only
cipCardCsnaStatsBlocksTxByBlockDelayTime
The number of blocks transmitted when the block delay time has been exceeded.
Syntax: Counter32
Max-Access: Read-only
cipCardCsnaStatsBytesTxByBlockDelayTime
The number of bytes transmitted when the block delay time has been exceeded.
Syntax: Counter32
Max-Access: Read-only
cipCardCsnaStatsHCBytesTxByBlockDelayTime
The number of bytes transmitted when the block delay time has been exceeded.
This is a 64-bit (high-capacity) version of the cipCardCsnaStatsBytesTxByBlockDelayTime counter for use with SNMP version 2 managers.
Syntax: Counter64
Max-Access: Read-only
cipCardCsnaStatsBlocksTxByBlockDelayLength
The number of blocks transmitted when the suggested block delay length has been exceeded.
Syntax: Counter32
Max-Access: Read-only
cipCardCsnaStatsBytesTxByBlockDelayLength
The number of bytes transmitted when the block delay length has been reached.
Syntax: Counter32
Max-Access: Read-only
cipCardCsnaStatsHCBytesTxByBlockDelayLength
The number of bytes transmitted when the block delay length has been reached.
This is a 64-bit (high-capacity) version of the cipCardCsnaStatsBytesTxByBlockDelayLength counter for use with SNMP version 2 managers.
Syntax: Counter64
Max-Access: Read-only
cipCardCsnaStatsBlocksTxByMaxBlockLength
The number of blocks transmitted when the maximum block length has been exceeded.
Syntax: Counter32
Max-Access: Read-only
cipCardCsnaStatsBytesTxByMaxBlockLength
The number of bytes transmitted when the max block length has been reached.
Syntax: Counter32
Max-Access: Read-only
cipCardCsnaStatsHCBytesTxByMaxBlockLength
The number of bytes transmitted when the max block length has been reached.
This is a 64-bit (high-capacity) version of the cipCardCsnaStatsBytesTxByMaxBlockLength counter for use with SNMP version 2 managers.
Syntax: Counter64
Max-Access: Read-only
cipCardCsnaStatsSlowDownsReceived
The number of times the CSNA channel device detected the slow down bit set by VTAM.
Syntax: Counter32
Max-Access: Read-only
cipCardCsnaStatsSlowDownsSent
The number of times the CSNA channel device set the slow down bit directing VTAM not to send any more blocks until the bit is cleared.
Syntax: Counter32
Max-Access: Read-only
End of Table
cipCardSessionsAdminTable
This table contains configured values for CSNA sessions supported on the Channel Interface Processor (CIP) card.
Syntax: SEQUENCE OF CipCardSessionsAdminEntry
Max-Access: Not-accessible
cipCardAdminMaxLlc2Sessions
The configured maximum number of LLC2 connections allowed on a CIP card. A value of zero indicates that the maximum should only be limited by the amount of available memory on the CIP. A value greater than zero indicates the maximum number of sessions the CIP will support given enough memory available on the CIP card.
This value can be set at any time; however, it will only affect the maximum number of LLC2 sessions supported on a CIP the first time it is set and only if the value it is being set to is greater than the current value for cipCardStatsHiWaterLlc2Sessions.
Syntax: Integer (0-4000)
Max-Access: Read-write
End of Table
cipCardSessionsOperTable
This table contains the current value for the maximum number of sessions that can be supported on the CIP card.
Syntax: SEQUENCE OF CipCardSessionsOperEntry
Max-Access: Not-accessible
cipCardOperMaxLlc2Sessions
This value indicates the current number of LLC2 sessions that can be supported on this CIP card. If this value is zero, then the limit of LLC2 sessions on the CIP card is only limited by the amount of memory available.
Syntax: Integer (0-4000)
Max-Access: Read-only
End of Table
cipCardSessionsStatsTable
This table contains the statistic value(s) for the maximum number of sessions that can be supported on the CIP card.
Syntax: SEQUENCE OF CipCardSessionsStatsEntry
Max-Access: Not-accessible
cipCardStatsHiWaterLlc2Sessions
High water LLC2 sessions count per CIP card.
If cipCardOperMaxLlc2Sessions is zero (0), then this value starts at 256 Llc2 sessions and is incremented in values of 64 as more active concurrent LLC2 sessions are established.
If cipCardOperMaxLlc2Sessions is greater then zero (0), then this value is either equal to the cipCardOperMaxLlc2Sessions—given enough memory is available on the CIP card to support that many LLC2 sessions—or the value will be less than cipCardOperMaxLlc2Sessions, reflecting the maximum number of LLC2 sessions the CIP card can support.
Syntax: Gauge32
Max-Access: Read-only
cipCardStatsLlc2SessionsAllocationErrs
The number of memory allocation errors that have occurred during attempts to create a new block of memory for the LLC2 session buffer pool.
Syntax: Counter32
Max-Access: Read-only
End of Table
CipCardCsnaConnTable
This table contains the map between VTAM (the I/O Device Address) and the internal LAN adapter/MAC Address/SAP.
Syntax: SEQUENCE OF CipCardCsnaConnEntry
Max-Access: Not-accessible
cipCardCsnaConnActiveSessions
The active sessions in this VTAM-to-internal-LAN adapter/MAC address mapping.
Syntax: Gauge32
Max-Access: Read-only
cipCardCsnaSlot
The slot number of the CIP card on which the path and device are configured.
Syntax: Integer32
Max-Access: Read-only
cipCardCsnaPort
The port number of the interface on the CIP card on which the path and device are configured.
Syntax: Integer32
Max-Access: Read-only
cipCardCsnaConnPath
The hex path identifier used by this instance of internal LAN adapter/SAP to connect SNA sessions to VTAM.
Syntax: ChannelPath
Max-Access: Read-only
cipCardCsnaConnDevice
The two-digit hex device address used by this internal LAN adapter/SAP instance to connect SNA sessions to VTAM.
Syntax: ChannelDevice
Max-Access: Read-only
End of Table
Notifications for Cisco CIP CSNA MIB
The following notifications are supported with the Cisco CIP CSNA MIB:
cipCsnaOpenDuplicateSapFailure
This trap indicates that VTAM attempted to open a SAP that was already open on another path/device (subchannel) on this CIP card.
cipCsnaLlc2ConnectionLimitExceeded
This trap indicates that a connection attempt was rejected due to a connection resource limitation.
Cisco CIP LAN Group
The variables in this section are used to manage the Cisco internal LAN support (LAN and Adapter) on the Channel Interface Processor (CIP).
CipCardLanAdminTable
This table contains configuration information for the LAN feature on the Channel Interface Processor (CIP).
Syntax: SEQUENCE OF CipCardLanAdminEntry
Max-Access: Not-accessible
cipCardLanAdminLanType
The type of emulation applied to this CIP LAN.
Syntax: Integer 1 = iso88023csmacd, 2 = iso88025tokenRing, 3 = fddi
Max-Access: Not-accessible
cipCardLanAdminLanId
The index value used with the ifIndex to uniquely identify a CIP LAN.
Syntax: Integer (1-31)
Max-Access: Not-accessible
cipCardLanAdminBridgeType
The bridging type supported by this CIP LAN.
The value of transparentOnly (1) is valid for all LAN types.
The value of sourcerouteOnly (2) is only valid for iso88025tokenRing and fddi LAN types.
The value of bothSrtAndTb (3) is valid for all iso88025tokenRing and fddi LAN types.
Syntax: Integer 1 = transparentOnly, 2 = sourcerouteOnly, 3 = transpAndSourceRoute
Max-Access: Read-create
cipCardLanAdminSrbLocalRing
The local segment (ring) number that uniquely identifies this CIP LAN.
This variable is only valid when cipCardLanAdminBridgeType is sourcerouteOnly (2) or transpAndSourceRoute (3).
Syntax: Integer (1-4095)
Max-Access: Read-create
cipCardLanAdminSrbBridgeNum
The bridge number that represents this router's bridge number.
This variable is only valid when cipCardLanAdminBridgeType is sourcerouteOnly (2) or transpAndSourceRoute (3).
Syntax: Integer (1-15)
Max-Access: Read-create
cipCardLanAdminSrbTargetRing
The target segment (ring) number that is the next hop from this segment.
This variable is only valid when cipCardLanAdminBridgeType is sourcerouteOnly (2) or transpAndSourceRoute (3).
Syntax: Integer (1-4095)
Max-Access: Read-create
cipCardLanAdminTbBridgeGrp
The transparent bridge group of which this CIP LAN is a member.
This variable is only valid when cipCardLanAdminBridgeType is transparentOnly (1) or transpAndSourceRoute (3).
Syntax: Integer (1-63)
Max-Access: Read-create
cipCardLanAdminRowStatus
This object is used by a management station to create or delete the row entry in the cipCardLanAdminTable.
Syntax: RowStatus
Max-Access: Read-create
End of Table
CipCardLanAdaptAdminTable
This table contains configuration information for the LAN adapter feature on the Channel Interface Processor (CIP).
Syntax: SEQUENCE OF CipCardLanAdaptAdminEntry
Max-Access: Not-accessible
cipCardLanAdaptAdminAdaptNo
The adapter number used when creating a CIP LAN adapter. This value is given by the instance value when this row is being created.
This number corresponds to the "ADAPNO" value used by VTAM XCA node definition.
This number uniquely identifies this adapter from all other adapters for the LAN type, which is identified in the associated CIP LAN adapter table.
Syntax: Integer (0-31)
Max-Access: Not-accessible
cipCardLanAdaptAdminMacAddress
The adapter MAC address assigned by the router administrator. It is a unique number used by protocols to address this adapter on the CIP LAN identified by the second index (cipCardLanAdminLanId). Note that in order to have duplicate MAC addresses, addresses must be on different source route bridge LANs.
Syntax: MacAddress
Max-Access: Read-create
cipCardLanAdaptAdminAdaptName
The unique adapter name assigned by the router administrator. Every interface of the router can be named by the router administrator.
The Adapter Name is used in the Hierarchy Resource List when creating a Systems Network Architecture Generic Alert for the purpose of identifying the CIP LAN adapter which generated the alert.
Syntax: DisplayString (SIZE (1-8))
Max-Access: Read-create
cipCardLanAdaptAdminRowStatus
This object is used by a Management Station to create or delete the row entry in the cipCardCsnaAdminTable.
Syntax: RowStatus
Max-Access: Read-create
End of Table
Cisco CIP TCP/IP Group
The variables in this section consist of objects used to manage the Cisco TCP/IP stack running on the Channel Interface Processor (CIP) board.
The first application to use this stack is the IBM TCP-Offload feature. This application replaces the TCP/IP stack on the IBM host with a protocol requiring lower host CPU utilization, and passes TCP/IP processing to the router.
There are multiple sets of MIB-II statistics stored by the TCP/IP implementation. Each instance of the MIB-II objects corresponds to an instantiation of the TCP/IP stack which is based on the IP address of the stack.
The IP routing table is not supported here.
cipIpTable
This table contains a list of parameters and statistics pertaining to each IP protocol stack running on the Channel Interface Processor (CIP) board. The TCP offload feature makes use of the stack. Rows are dynamically added to this table via CIP TCP application MIBs (i.e., Cisco TCP offload MIB). Use this table to view statistics and status for the IP stack.
Syntax: SEQUENCE OF CipIpEntry
Max-Access: Not-accessible
cipIpAddress
The IP address for this IP stack.
Syntax: IpAddress
Max-Access: Not-accessible
cipIpForwarding
Indicates whether this entity is acting as an IP gateway in respect to the forwarding of datagrams received by, but not addressed to, this entity. IP gateways forward datagrams. IP hosts do not (except those source-routed via the host).
Note that for some managed nodes, this object may take on only a subset of the values possible. Accordingly, it is appropriate for an agent to return a "badValue" response if a management station attempts to change this object to an inappropriate value.
Syntax: Integer 1 = forwarding (acting as a gateway), 2 = not forwarding (not acting as a gateway)
Max-Access: Read-only
cipIpDefaultTTL
The default value inserted into the Time-To-Live (TTL) field of the IP header of datagrams originated at this entity, whenever a TTL value is not supplied by the transport layer protocol.
Syntax: Integer (1-255)
Max-Access: Read-write
cipIpInReceives
The total number of input datagrams received from interfaces, including those received in error.
Syntax: Counter32
Max-Access: Read-only
cipIpInHdrErrors
The number of input datagrams discarded due to errors in their IP headers, including bad checksums, version number mismatch, other format errors, time-to-live exceeded, errors discovered in processing their IP options, etc.
Syntax: Counter32
Max-Access: Read-only
cipIpInAddrErrors
The number of input datagrams discarded because the IP address in their IP header's destination field was not a valid address to be received at this entity. This count includes invalid addresses (e.g., 0.0.0.0) and addresses of unsupported Classes (e.g., Class E). For entities which are not IP gateways and therefore do not forward datagrams, this counter includes datagrams discarded because the destination address was not a local address.
Syntax: Counter32
Max-Access: Read-only
cipIpForwDatagrams
The number of input datagrams for which this entity was not their final IP destination, as a result of which an attempt was made to find a route to forward them to that final destination. In entities that do not act as IP Gateways, this counter will include only those packets which were source-routed via this entity, and the source-route option processing was successful.
Syntax: Counter32
Max-Access: Read-only
cipIpInUnknownProtos
The number of locally-addressed datagrams received successfully but discarded because of an unknown or unsupported protocol.
Syntax: Counter32
Max-Access: Read-only
cipIpInDiscards
The number of input IP datagrams for which no problems were encountered to prevent their continued processing, but which were discarded (e.g., for lack of buffer space). This counter does not include any datagrams discarded while awaiting re-assembly.
Syntax: Counter32
Max-Access: Read-only
cipIpInDelivers
The total number of input datagrams successfully delivered to IP user-protocols (including ICMP).
Syntax: Counter32
Max-Access: Read-only
cipIpOutRequests
The total number of IP datagrams which local IP user-protocols (including ICMP) supplied to IP in requests for transmission. Note that this counter does not include any datagrams counted in ipForwDatagrams.
Syntax: Counter32
Max-Access: Read-only
cipIpOutDiscards
The number of output IP datagrams for which no problem was encountered to prevent their transmission to their destination, but which were discarded (e.g., for lack of buffer space). Note that this counter includes datagrams counted in ipForwDatagrams if any such packets meet this discretionary discard criterion.
Syntax: Counter32
Max-Access: Read-only
cipIpOutNoRoutes
The number of IP datagrams discarded because no route could be found to transmit them to their destination. This counter includes any packets counted in ipForwDatagrams that meet this "no-route" criterion, including any datagrams that a host cannot route because all its default gateways are down.
Syntax: Counter32
Max-Access: Read-only
cipIpReasmTimeout
The maximum number of seconds that received fragments are held while they are awaiting reassembly at this entity.
Syntax: Integer
Max-Access: Read-only
cipIpReasmReqds
The number of IP fragments received that needed to be reassembled at this entity.
Syntax: Counter32
Max-Access: Read-only
cipIpReasmOKs
The number of IP datagrams successfully re-assembled.
Syntax: Counter32
Max-Access: Read-only
cipIpReasmFails
The number of failures detected by the IP re-assembly algorithm (for whatever reason: timed out, errors, etc.). Note that this is not necessarily a count of discarded IP fragments because some algorithms (notably the algorithm in RFC 815) can lose track of the number of fragments by combining them as they are received.
Syntax: Counter32
Max-Access: Read-only
cipIpFragOKs
The number of IP datagrams that have been successfully fragmented at this entity.
Syntax: Counter32
Max-Access: Read-only
cipIpFragFails
The number of IP datagrams that have been discarded because they needed to be fragmented at this entity but could not be, e.g., because their Don't Fragment flag was set.
Syntax: Counter32
Max-Access: Read-only
cipIpFragCreates
The number of IP datagram fragments generated as a result of fragmentation at this entity.
Syntax: Counter32
Max-Access: Read-only
cipIpRoutingDiscards
The number of routing entries chosen to be discarded even though they are valid. One possible reason for discarding such an entry is to free up buffer space for other routing entries.
Syntax: Counter32
Max-Access: Read-only
End of Table
cipTcpStackTable
This table contains a list of parameters pertaining to each TCP stack running on the Channel Interface Processor (CIP) board. The TCP offload feature makes use of the stack. Rows are dynamically added to this table via CIP TCP application MIBs (i.e. Cisco TCP offload MIB). Use this table to view statistics and status for the TCP stack.
Syntax: SEQUENCE OF CipTcpStackEntry
Max-Access: Not-accessible
cipTcpRtoAlgorithm
The algorithm used to determine the timeout value for retransmitting unacknowledged octets.
Syntax: Integer 1 = other (none of the following), 2 = constant (a constant rto), 3 = rsre (MIL-STD-1778, Appendix B), 4 = vanj (Van Jacobson's algorithm)
Max-Access: Read-only
cipTcpRtoMin
The minimum value permitted by a TCP implementation for the retransmission timeout, measured in milliseconds. More refined semantics for objects of this type depend upon the algorithm used to determine the retransmission timeout. In particular, when the timeout algorithm is rsre (3), an object of this type has the semantics of the LBOUND quantity described in RFC 793.
Syntax: Integer32
Max-Access: Read-only
cipTcpRtoMax
The maximum value permitted by a TCP implementation for the retransmission timeout, measured in milliseconds. More refined semantics for objects of this type depend upon the algorithm used to determine the retransmission timeout. In particular, when the timeout algorithm is rsre (3), an object of this type has the semantics of the UBOUND quantity described in RFC 793.
Syntax: Integer32
Max-Access: Read-only
cipTcpMaxConn
The limit on the total number of TCP connections the entity can support. In entities where the maximum number of connections is dynamic, this object should contain the value -1.
Syntax: Integer32
Max-Access: Read-only
cipTcpActiveOpens
The number of times TCP connections have made a direct transition to the SYN-SENT state from the CLOSED state.
Syntax: Counter32
Max-Access: Read-only
cipTcpPassiveOpens
The number of times TCP connections have made a direct transition to the SYN-RCVD state from the LISTEN state.
Syntax: Counter32
Max-Access: Read-only
cipTcpAttemptFails
The number of times TCP connections have made a direct transition to the CLOSED state from either the SYN-SENT state or the SYN-RCVD state, plus the number of times TCP connections have made a direct transition to the LISTEN state from the SYN-RCVD state.
Syntax: Counter32
Max-Access: Read-only
cipTcpEstabResets
The number of times TCP connections have made a direct transition to the CLOSED state from either the ESTABLISHED state or the CLOSE-WAIT state.
Syntax: Counter32
Max-Access: Read-only
cipTcpCurrEstab
The number of TCP connections for which the current state is either ESTABLISHED or CLOSE-WAIT.
Syntax: Gauge32
Max-Access: Read-only
cipTcpInSegs
The total number of segments received, including those received in error. This count includes segments received on currently established connections.
Syntax: Counter32
Max-Access: Read-only
cipTcpOutSegs
The total number of segments sent, including those on current connections but excluding those containing only retransmitted octets.
Syntax: Counter32
Max-Access: Read-only
cipTcpRetransSegs
The total number of segments retransmitted i.e., the number of TCP segments transmitted containing one or more previously transmitted octets.
Syntax: Counter32
Max-Access: Read-only
cipTcpInErrs
The total number of segments received in error (e.g., bad TCP checksums).
Syntax: Counter32
Max-Access: Read-only
cipTcpOutRsts
The number of TCP segments sent containing the RST flag.
Syntax: Counter32
Max-Access: Read-only
End of Table
cipTcpConnTable
This table contains a list of parameters pertaining to the connections for a particular TCP Offload protocol stack running on the Channel Interface Processor (CIP) board. The TCP offload feature makes use of the stack. The TCP connection instances exist for each TCP/IP connection on the CIP. These instances are removed when the TCP connection is terminated. Use this table to view statistics and status for the TCP Offload stack.
Syntax: SEQUENCE OF CipTcpConnEntry
Max-Access: Not-accessible
cipTcpConnLocalPort
The local port number for this TCP connection.
Syntax: Integer (0-65535)
Max-Access: Not-accessible
cipTcpConnRemAddress
The remote IP address for this TCP connection.
Syntax: IpAddress
Max-Access: Not-accessible
cipTcpConnRemPort
The remote port number for this TCP connection.
Syntax: Integer (0-65535)
Max-Access: Not-accessible
cipTcpConnState
The state of this TCP connection.
The only value a management station can set is deleteTCB (12). Accordingly, it is appropriate for an agent to return a "badValue" response if a management station attempts to set this object to any other value.
If a management station sets this object to the value deleteTCB (12), then this has the effect of deleting the TCB (as defined in RFC 793) of the corresponding connection on the managed node, resulting in immediate termination of the connection.
As an implementation-specific option, an RST segment can be sent from the managed node to the other TCP endpoint (note however that RST segments are not sent reliably).
Syntax: Integer 1 = closed, 2 = listen, 3 = synSent, 4 = synReceived, 5 = established, 6 = finWait1, 7 = finWait2, 8 = closeWait, 9 = lastAck, 10 = closing, 11 = timeWait, 12 = deleteTCB
Max-Access: Read-write
cipTcpConnInHCBytes
The number of bytes sent for this TCP connection.
This is a 64-bit (high-capacity) version of the cipTcpConnInHCBytes counter for use with SNMP Version 2.
Syntax: Counter64
Max-Access: Read-only
cipTcpConnInBytes
The number of bytes sent for this TCP connection.
Note
Syntax: Counter32
Max-Access: Read-only
cipTcpConnOutHCBytes
The number of bytes received for this TCP connection.
This is a 64-bit (high-capacity) version of the cipTcpConnOutHCBytes counter for use with SNMP Version 2.
Syntax: Counter64
Max-Access: Read-only
cipTcpConnOutBytes
The number of bytes received for this TCP connection.
Note
Syntax: Counter32
Max-Access: Read-only
End of Table
cipIcmpTable
This table contains a list of parameters pertaining to each ICMP stack running on the Channel Interface Processor (CIP) board. The TCP offload feature makes use of the stack. Rows are dynamically added to this table via CIP TCP application MIBs (i.e., Cisco TCP offload MIB). Use this table to view statistics and status for the ICMP stack.
Syntax: SEQUENCE OF CipIcmpEntry
Max-Access: Not-accessible
cipIcmpInMsgs
The total number of ICMP messages the entity received. Note that this counter includes all those counted by icmpInErrors.
Syntax: Counter32
Max-Access: Read-only
cipIcmpInErrors
The number of ICMP messages that the entity received but determined as having ICMP-specific errors (bad ICMP checksums, bad length, etc.).
Syntax: Counter32
Max-Access: Read-only
cipIcmpInDestUnreachs
The number of ICMP Destination Unreachable messages received.
Syntax: Counter32
Max-Access: Read-only
cipIcmpInTimeExcds
The number of ICMP Time Exceeded messages received.
Syntax: Counter32
Max-Access: Read-only
cipIcmpInParmProbs
The number of ICMP Parameter Problem messages received.
Syntax: Counter32
Max-Access: Read-only
cipIcmpInSrcQuenchs
The number of ICMP Source Quench messages received.
Syntax: Counter32
Max-Access: Read-only
cipIcmpInRedirects
The number of ICMP Redirect messages received.
Syntax: Counter32
Max-Access: Read-only
cipIcmpInEchos
The number of ICMP Echo (request) messages received.
Syntax: Counter32
Max-Access: Read-only
cipIcmpInAddrMaskReps
The number of ICMP Address Mask Reply messages received.
Syntax: Counter32
Max-Access: Read-only
cipIcmpOutMsgs
The total number of ICMP messages which this entity attempted to send. Note that this counter includes all those counted by icmpOutErrors.
Syntax: Counter32
Max-Access: Read-only
cipIcmpOutErrors
The number of ICMP messages which this entity did not send due to problems discovered within ICMP such as a lack of buffers. This value should not include errors discovered outside the ICMP layer such as the inability of IP to route the resultant datagram. In some implementations no types of error exist that contribute to this counter's value.
Syntax: Counter32
Max-Access: Read-only
cipIcmpOutDestUnreachs
The number of ICMP Destination Unreachable messages sent.
Syntax: Counter32
Max-Access: Read-only
cipIcmpOutEchos
The number of ICMP Echo (request) messages sent.
Syntax: Counter32
Max-Access: Read-only
cipIcmpOutEchoReps
The number of ICMP Echo Reply messages sent.
Syntax: Counter32
Max-Access: Read-only
cipIcmpOutTimestamps
The number of ICMP Timestamp (request) messages sent.
Syntax: Counter32
Max-Access: Read-only
cipIcmpOutTimestampReps
The number of ICMP Timestamp Reply messages sent.
Syntax: Counter32
Max-Access: Read-only
cipIcmpOutAddrMasks
The number of ICMP Address Mask Request messages sent.
Syntax: Counter32
Max-Access: Read-only
cipIcmpOutAddrMaskReps
The number of ICMP Address Mask Reply messages sent.
Syntax: Counter32
Max-Access: Read-only
End of Table
cipUdpTable
This table contains a list of parameters pertaining to each UDP stack running on the Channel Interface Processor (CIP) board. The TCP offload feature makes use of the stack. Rows are dynamically added to this table via CIP TCP application MIBs (i.e., Cisco TCP offload MIB). Use this table to view statistics and status for the UDP stack.
Syntax: SEQUENCE OF CipUdpEntry
Max-Access: Not-accessible
cipUdpInDatagrams
The total number of UDP datagrams delivered to UDP users.
Syntax: Counter32
Max-Access: Read-only
cipUdpNoPorts
The total number of received UDP datagrams for which there was no application at the destination port.
Syntax: Counter32
Max-Access: Read-only
cipUdpInErrors
The number of received UDP datagrams that could not be delivered for reasons other than the lack of an application at the destination port.
Syntax: Counter32
Max-Access: Read-only
cipUdpOutDatagrams
The total number of UDP datagrams sent from this entity.
Syntax: Counter32
Max-Access: Read-only
End of Table
cipUdpListenersTable
This table contains a list of parameters pertaining to the listeners for a particular UDP stack running on the Channel Interface Processor (CIP) board. The TCP offload feature makes use of the stack. Use this table to view statistics and status for the UDP stack listeners table.
Syntax: SEQUENCE OF CipUdpListenersEntry
Max-Access: Not-accessible
cipUdpLocalPort
The local port number for this UDP listener.
Syntax: Integer (0-65535)
Max-Access: Read-only
End of Table
Cisco SNA LLC Group
The variables in this section are used to manage the Logical Link Control, type 2 (LLC2) stack that runs on the Channel Interface Processor (CIP) card used in providing the Systems Network Architecture (SNA) gateway to an IBM mainframe via a channel connection from the router.
LlcPortAdminTable
This table contains objects that can be changed to manage an LLC port. A change to one of these parameters may take effect in the operating port immediately or may wait until the interface is restarted, depending on the details of the implementation.
Syntax: SEQUENCE OF LlcPortAdminEntry
Max-Access: Not-accessible
llcPortVirtualIndex
This value represents a virtual LLC port. It is assigned by the agent.
This value is not used by the agent if the interface identified by the ifIndex value does not support virtual interfaces.
Syntax: Integer32 (0-65535)
Max-Access: Not-accessible
llcPortAdminName
An octet string that defines the virtual port to which this interface is assigned. It has implementation-specific significance. Its value is unique within the administered system. It must contain only ASCII-printable characters. Should an implementation choose to accept a write operation for this object, it causes the logical port definition associated with the table instance to be moved to a different physical port. A write operation shall not take effect until the port is cycled inactive.
Syntax: DisplayString (SIZE (1-8))
Max-Access: Read-write
llcPortAdminMaxSaps
The maximum number of SAPs that can be opened on this port.
Syntax: Gauge32
Max-Access: Read-write
llcPortAdminMaxCcs
The maximum number of connection components that can be opened on this port.
Syntax: Gauge32
Max-Access: Read-write
llcPortAdminMaxPDUOctets
The default maximum PDU size, in octets, that LLCs on this port can send to their remote LLC partners. This count is referred to as "N1" in the IEEE 802.2 specification.
This port default value can be overridden by a non-zero SAP default value in the llcSapAdminMaxPDUOctets object or by a non-zero value in the llcCcAdminMaxPDUOctets object.
At connection setup, the remote LLC can send, using an XID frame, the maximum PDU size that it is prepared to receive. If so, an implementation can choose to override the administered maximum PDU size with the dynamically learned value and should reflect this in the llcCcOperMaxPDUOctets object for the connection component.
The PDU size includes all octets in a frame, excluding framing characters, the MAC header, and link header.
Syntax: Integer32
Max-Access: Read-write
llcPortAdminMaxUnackedIPDUsSend
The default maximum consecutive unacknowledged I PDU frames that LLCs on this port may send to their remote LLC partners. This count is referred to as "k" in the IEEE 802.2 specification.
This port default value can be overridden by a non-zero SAP default value in the llcSapAdminMaxUnackedIPDUsSend object or by a non-zero value in the llcCcAdminMaxUnackedIPDUsSend object.
At connection setup, the remote LLC may send, using an XID frame, the maximum number of unacknowledged I PDUs it is prepared to receive. If so, an implementation may choose to override the administered maximum number of unacknowledged PDUs with the dynamically learned value and should reflect this in the llcCcOperMaxUnackedIPDUsSend object for the connection component.
Syntax: Integer (1-127)
Max-Access: Read-write
llcPortAdminMaxUnackedIPDUsRcv
The default maximum number of unacknowledged I PDUs that LLCs on this port can expect to receive from their remote LLC partners. This count is referred to as "k" in the IEEE 802.2 specification.
This port default value can be overridden by a non-zero SAP default value in the llcSapAdminMaxUnackedIPDUsRcv object or by a non-zero value in the llcCcAdminMaxUnackedIPDUsRcvd object.
At connection setup, an implementation may choose to send this value to the remote LLC, using an XID frame.
Syntax: Integer (1-127)
Max-Access: Read-write
llcPortAdminMaxRetransmits
The default value for the maximum number of times that LLCs on this port can retry a PDU following the expiration of the acknowledgment timer, the P-bit timer or the reject timer. When these retries are exhausted, the link is declared inactive. This count is referred to as "N2" in the IEEE 802.2 specification.
This port default value can be overridden by a non-zero SAP default value in the llcSapAdminMaxretransmits object or by a non-zero value in the llcCcAdminMaxRetransmits object.
Syntax: Integer32
Max-Access: Read-write
llcPortAdminAckTimer
The default value for the time interval during which the LLCs on this port expect to receive, either: 1) an acknowledgment to one or more outstanding I PDUs, or 2) a response PDU to an unnumbered command PDU.
The expiration of this timer causes the unacknowledged frames to be retransmitted (up to N2 times).
For implementations that only use a single "T1" value, this object will be used to control/read the value.
This port default value can be overridden by a non-zero value in the llcSapAdminAckTimer object or by a non-zero value in the llcCcAdminAckTimer object.
Syntax: TimeTicks
Max-Access: Read-write
llcPortAdminPbitTimer
The default value for the time interval during which the LLCs on this port expect to receive a PDU with the F bit set to "1" in response to a Type 2 command with the P bit set to "1".
The expiration of this timer causes the command with the poll bit to be retransmitted (up to N2 times).
This port default value can be overridden by a non-zero SAP default value in the llcSapAdminPbitTimer object or by a non-zero value in the llcCcAdminPbitTimer object.
Syntax: TimeTicks
Max-Access: Read-write
llcPortAdminRejTimer
The default value for the time interval during which the LLCs on this port expect to receive a reply to a REJ PDU.
The expiration of this timer causes the REJ PDU to be retransmitted (up to N2 times).
This port default value can be overridden by a non-zero SAP default value in the llcSapAdminRejTimer object or by a non-zero value in the llcCcAdminRejTimer object.
Syntax: TimeTicks
Max-Access: Read-write
llcPortAdminBusyTimer
The default value for the time interval during which the LLCs on this port expect to receive an indication that a busy condition at the remote LLC has cleared.
The expiration of this timer causes the link to be declared inactive.
This port default value can be overridden by a non-zero SAP default value in the llcSapAdminBusyTimer object or by a non-zero value in the llcCcAdminBusyTimer object.
Syntax: TimeTicks
Max-Access: Read-write
llcPortAdminInactTimer
The default value for the time interval during which the LLCs on this port expect to receive any PDU from the remote LLC.
The expiration of this timer causes the local LLC to send a PDU to the remote LLC with the P bit set to "1".
The value for llcPortAdminInactTimer must be much greater than the value for llcPortAdminDelayAckTimer.
This port default value can be overridden by a non-zero SAP default value in the llcSapAdminInactTimer object or by a non-zero value in the llcCcAdminInactTimer object.
Any value for this object less than or equal to the acknowledgment timer means that the timer is not used.
Syntax: TimeTicks
Max-Access: Read-write
llcPortAdminDelayAckCount
The default value for the maximum number of consecutive I PDUs that the LLCs on this port receive during the interval defined by llcCcOperDelayTimertime without sending an immediate acknowledgment. This must be less than or equal to the value of llcCcOperMaxUnackIPDURcv.
This port default value can be overridden by a non-zero SAP default value in the llcSapAdminDelayAckCount object or by a non-zero value in the llcCcAdminDelayCount object.
A value of one indicates that acknowledgments will be sent immediately and that the value of llcPortAdminDelayAckTimer will be ignored.
Syntax: Integer32
Max-Access: Read-write
llcPortAdminDelayAckTimer
The default value for the time interval during which the LLCs on this port delay acknowledgment of one or more I PDUs (up to the value of llcCcOperDelayAckCount).
The expiration of this timer causes the local LLC to acknowledge all unacknowledged I PDUs.
This object is associated with the llcSapAdminDelayAckCount object and is only defined if that object has a value greater than one.
Syntax: TimeTicks
Max-Access: Read-write
llcPortAdminNw
The default value for the number of IPDUs that must be acknowledged before the working window size (Ww) can be incremented by 1 when the working window is not equal to the maximum transmit window size (TW). This value controls the gradual incrementing of Ww in congestion situations.
This port default value can be overridden by a non-zero SAP default value in the llcSapAdminNw object.
Syntax: Integer32
Max-Access: Read-write
End of Table
LlcPortOperTable
This table contains current LLC port parameters.
Syntax: SEQUENCE OF LlcPortOperEntry
Max-Access: Not-accessible
llcPortOperMacAddress
This is the MAC address for this local port.
Syntax: MacAddress
Max-Access: Read-only
llcPortOperNumSaps
The number of SAPs on this port that are currently enabled. In other words, this object is a count of the number of instances of llcSapOperEntry that have a llcSapOperStatus value of "active" (2).
Syntax: Gauge32
Max-Access: Read-only
llcPortOperHiWaterNumSaps
The highest number of SAPs active on this port simultaneously. In other words, this object is a count of the number of instances of llcSapOperEntry on this port.
Syntax: Gauge32
Max-Access: Read-only
llcPortOperRimSim
This object reflects support for transmission and receipt of SIM and RIM control frames for this port.
SIM and RIM are not defined in the ANSI/IEEE 802.2 specification or in the IBM Token-Ring Architecture Reference. These control frames are used for the remote program load of IBM communications processors.
Syntax: Gauge32
Max-Access: Read-only
llcPortOperLastModifyTime
Specifies the value of sysUpTime when this port definition was last modified. If the port has not been modified, then this value is zero.
Syntax: TimeStamp
Max-Access: Read-only
End of Table
LlcPortStatsTable
This table contains statistics for a specific LLC port.
Syntax: SEQUENCE OF LlcPortStatsEntry
Max-Access: Not-accessible
llcPortStatsPDUsIn
The total number of PDUs that have been received on this port. This object is initialized to zero when the port is created.
Syntax: Counter32
Max-Access: Read-only
llcPortStatsPDUsOut
The total number of PDUs that have been transmitted on this port. This object is initialized to zero when the port is created.
Syntax: Counter32
Max-Access: Read-only
llcPortStatsOctetsIn
The total octets received from adjacent connection components on this port. This object covers the address, control, and information field of I-frames only. This object is initialized to zero when the port is created.
Syntax: Counter32
Max-Access: Read-only
llcPortStatsOctetsOut
The total octets transmitted to adjacent connection components on this port. This object covers the address, control, and information field of I-frames only. This object is initialized to zero when the port is created.
Syntax: Counter32
Max-Access: Read-only
llcPortStatsTESTCommandsIn
The total number of TEST commands received on this port.
Syntax: Counter32
Max-Access: Read-only
llcPortStatsTESTResponsesOut
The total number of TEST responses transmitted on this port in response to TEST commands received.
Syntax: Counter32
Max-Access: Read-only
llcPortStatsLocalBusies
The total number of times that the local connection components on this port have entered a busy state (RNR). This object is initialized to zero when the port is created.
Syntax: Counter32
Max-Access: Read-only
llcPortStatsUnknownSaps
The total number of times that a connection attempt, from a remote LLC station, for an unknown SAP was detected on this port.
Syntax: Counter32
Max-Access: Read-only
End of Table
LlcSapAdminTable
This table contains objects that can be changed to manage a local SAP. A change to one of these parameters can take effect in the operating SAP immediately or can wait until the interface is restarted depending on the details of the implementation.
Syntax: SEQUENCE OF LlcSapAdminEntry
Max-Access: Not-accessible
llcSapNumber
The address of this local SAP.
Syntax: Integer (1-225)
Max-Access: Not-accessible
llcSapAdminMaxPDUOctets
The default maximum I PDU size, in octets, that LLCs on this SAP can send to their remote connection component partners. This count is referred to as "N1" in the IEEE 802.2 specification.
A zero value for this object indicates that the port default, llcPortAdminMaxIPDUOctetsSend, is used as the SAP default. This SAP default value can be overridden by a non-zero value in the llcCcAdminMaxIPDUOctetsSend object.
At connection setup, the remote LLC can send, using an XID frame, the maximum I PDU size that it is prepared to receive. If so, an implementation can choose to override the administered maximum PDU size with the dynamically learned value and should reflect this in the llcCcOperMaxIPDUOctetsSend object for the connection component.
The I PDU size includes all octets in a frame, excluding framing characters, the MAC header, and link header.
Syntax: Integer32
Max-Access: Read-write
llcSapAdminMaxUnackedIPDUsSend
The default maximum consecutive unacknowledged I PDU frames that LLCs on this SAP can send to their remote LLC partners. This count is referred to as "k" in the IEEE 802.2 specification.
A zero value for this object indicates that the port default, llcPortAdminMaxUnackedIPDUsSend, is the SAP default. This SAP default value can be overridden by a non-zero value in the llcCcAdminMaxUnackedIPDUsSend object.
At connection setup, the remote LLC can us an XID frame to send the maximum number of unacknowledged I PDUs it is prepared to receive. If this occurs, an implementation can override the administered maximum number of unacknowledged PDUs with the dynamically learned value and should reflect this in the llcCcOperMaxUnackedIPDUsSend object for the connection component.
Syntax: Integer (0-127)
Max-Access: Read-write
llcSapAdminMaxUnackedIPDUsRcv
The default maximum number of unacknowledged I PDUs that LLCs on this SAP can expect to receive from their remote LLC partners. This count is referred to as "k" in the IEEE 802.2 specification.
A zero value for this object indicates that the port default, llcPortAdminMaxUnackedIPDUsRcv, is the SAP default. This SAP default value can be overridden by a non-zero value in the llcCcAdminMaxUnackedIPDUsRcv object.
At connection setup, an implementation can send this value to the remote LLC, using an XID frame.
Syntax: Integer (1-127)
Max-Access: Read-write
llcSapAdminMaxRetransmits
The default value for the maximum number of times that LLCs on this SAP retry PDUs following the expiration of the acknowledgment timer, the P-bit timer or the reject timer. When these retries are exhausted, the link is declared inactive. This count is referred to as "N2" in the IEEE 802.2 specification.
A zero value for this object indicates that the port default, llcPortAdminMaxRetransmits, is the SAP default. This SAP default value can be overridden by a non-zero value in the llcCcAdminMaxRetransmits.
Syntax: Integer32
Max-Access: Read-write
llcSapAdminAckTimer
The default value for the time interval during which the LLCs on this SAP can expect to receive either: (1) an acknowledgment to one or more outstanding I PDUs, or (2) a response PDU to an unnumbered command PDU.
The expiration of this timer causes the unacknowledged frames to be retransmitted (up to N2 times).
A zero value for this object indicates that the port default, llcPortAdminAckTimer, is the SAP default. This SAP default value can be overridden by a non-zero value in the llcCcAdminAckTimer.
Syntax: TimeTicks
Max-Access: Read-write
llcSapAdminPbitTimer
The default value for the time interval during which the LLCs on this port can expect to receive a PDU with the F bit set to "1" in response to a Type 2 command with the P bit set to "1".
The expiration of this timer causes the REJ PDU to be retransmitted (up to N2 times).
A zero value for this object indicates that the port default, llcPortAdminPbitTimer, is the SAP default. This SAP default value can be overridden by a non-zero value in the llcCcAdminPbitTimer.
Syntax: TimeTicks
Max-Access: Read-write
llcSapAdminRejTimer
The default value for the time interval during which the LLCs on this SAP can expect to receive a reply to a REJ PDU.
The expiration of this timer causes the REJ PDU to be retransmitted (up to N2 times).
A zero value for this object indicates that the port default, llcPortAdminRejTimer, is the SAP default. This SAP default value can be overridden by a non-zero value in the llcCcAdminRejTimer.
Syntax: TimeTicks
Max-Access: Read-write
llcSapAdminBusyTimer
The default value for the time interval during which the LLCs on this SAP expect to receive an indication that a busy condition at the remote LLC has cleared.
The expiration of this timer causes the link to be declared inactive.
A zero value for this object indicates that the port default, llcPortAdminBusyTimer, is the SAP default. This SAP default value can be overridden by a non-zero value in the llcCcAdminBusyTimer.
Syntax: TimeTicks
Max-Access: Read-write
llcSapAdminInactTimer
The default value for the time interval during which the LLCs on this SAP expect to receive any PDU from the remote LLC.
The expiration of this timer causes the local LLC to send a PDU to the remote LLC with the P bit set to "1".
A zero value for this object indicates that the port default, llcPortAdminInactTimer, is the SAP default. This SAP default value can be overridden by a non-zero value in the llcCcAdminInactTimer.
Any value for this object less than or equal to the acknowledgment timer means that the timer is not used.
Syntax: TimeTicks
Max-Access: Read-write
llcSapAdminDelayAckCount
The default value for the maximum number of consecutive I PDUs that the LLCs on this SAP receive during the interval defined by llcCcOperDelayTimer without sending an immediate acknowledgment. This must be less than or equal to the value of llcCcOperMaxUnackIPDURcv.
A zero value for this object indicates that the port default, llcPortAdminDelayAck, is the SAP default. This SAP default value can be overridden by a non-zero value in the llcCcAdminDelayAckCount.
A value of one indicates that acknowledgments are sent immediately and that the value of llcSapAdminDelayAckTimer is ignored.
Syntax: Integer32
Max-Access: Read-write
llcSapAdminDelayAckTimer
The default value for the time interval during which the LLCs on this SAP delay acknowledgment of one or more I PDUs (up to the value of llcCcOperDelayAckCount).
The expiration of this timer causes the local LLC to acknowledge all unacknowledged I PDUs.
This object is associated with the llcSapAdminDelayAckCount object and is only defined if that object has a value greater than one.
Syntax: TimeTicks
Max-Access: Read-write
llcSapAdminNw
The default value for the number of IPDUs that must be acknowledged before the working window size (Ww) can be incremented by 1 when the working window is not equal to the maximum transmit window size (TW). This value controls the gradual incrementing of Ww in congestion situations.
This function is not described in the IEEE 802.2 specification. However, it is listed in the IBM Token-Ring Network Architecture Reference as the Nw parameter and is widely implemented.
This SAP default value can be overridden by a non-zero Cc default value in the llcCcAdminNw object.
Max-Access: Integer32
Max-Access: Read-write
End of Table
LlcSapOperTable
This object provides the current operational parameters of a SAP opened by VTAM. Multiple LLC SAPs can be opened for each configured virtual MAC adapter on the CIP.
llcSapOperStatus
This parameter describes the actual state of this local SAP.
Syntax: Integer 1 = inactive, 2 = active
Max-Access: Read-only
llcSapOperNumCcs
The number of connection components on this SAP that are currently in one of the "connected" states. In other words, this object is a count of the number of instances of llcCcOperEntry that have a llcCcOperState value greater than or equal to "normal" (3).
Syntax: Integer32
Max-Access: Read-only
llcSapOperHiWaterNumCcs
The highest number of connection components on this SAP simultaneously in one of the "connected" states. In other words, this object is a count of the number of instances of llcCcOperEntry that have a llcCcOperState value greater than or equal to "normal" (3) concurrently on this SAP.
Syntax: Gauge32
Max-Access: Read-only
llcSapOperLlc2Support
This parameter describes whether the LLC implementation supports LLC2 connection components.
Syntax: Integer 1 = no, 2 = yes
Max-Access: Read-only
End of Table
LlcSapStatsTable
The objects in the llcSapStatsTable provide statistics related to SNA LLC2 connection setup, disconnection, and errors on a LLC2 SAP basis. These objects are available for display from an SNMP management station for each SAP opened on the CIP by VTAM.
Syntax: SEQUENCE OF LlcSapStatsEntry
Max-Access: Not-accessible
llcSapStatsLocalBusies
The total number of times that the local connection components on this SAP have entered a busy state (RNR). This object is initialized to zero when the SAP is created.
Syntax: Counter32
Max-Access: Read-only
llcSapStatsRemoteBusies
The total number of times that the adjacent (i.e. remote) connection components on this SAP have entered a busy state (RNR). This object is initialized to zero when the SAP is created.
Syntax: Counter32
Max-Access: Read-only
llcSapStatsIFramesIn
The total number of I-frames that have been received by connection components on this SAP. This object is initialized to zero when the SAP is created.
Syntax: Counter32
Max-Access: Read-only
llcSapStatsIFramesOut
The total number of I-frames that have been transmitted by connection components on this SAP. This object is initialized to zero when the SAP is created.
Syntax: Counter32
Max-Access: Read-only
llcSapStatsIOctetsIn
The total octets received from adjacent connection components on this SAP. This object covers the address, control, and information field of I-frames only. This object is initialized to zero when the SAP is created.
Syntax: Counter32
Max-Access: Read-only
llcSapStatsIOctetsOut
The total octets transmitted to adjacent connection components on this SAP. This object covers the address, control, and information field of I-frames only. This object is initialized to zero when the SAP is created.
Syntax: Counter32
Max-Access: Read-only
llcSapStatsSFramesIn
The total number of S-frames that have been received by connection components on this SAP. This object is initialized to zero when the SAP is created.
Note
Syntax: Counter32
Max-Access: Read-only
llcSapStatsSFramesOut
The total number of S-frames that have been transmitted by connection components on this SAP. This object is initialized to zero when the SAP is created.
Note
Syntax: Counter32
Max-Access: Read-only
llcSapStatsRetransmitsOut
The total number of I-frames retransmitted by all local connection components on this SAP. This object is initialized to zero when the SAP is created.
Syntax: Counter32
Max-Access: Read-only
llcSapStatsREJsIn
The total REJ frames received from all adjacent LLC connection components on this SAP since it was created.
Syntax: Counter32
Max-Access: Read-only
llcSapStatsREJsOut
The total REJ frames transmitted to an adjacent LLC connection components on this SAP since it was created.
Syntax: Counter32
Max-Access: Read-only
llcSapStatsWwCount
The total number of times, since this SAP was created, that the dynamic window algorithm has been invoked to reduce the value of Ww on any of the connection components of this SAP. This object is initialized to zero when the SAP is created.
Syntax: Counter32
Max-Access: Read-only
llcSapStatsTESTCommandsIn
The number of TEST commands this SAP has received. This value measures the number of stations in the network trying to connect. This object is initialized to zero when the SAP is created.
Syntax: Counter32
Max-Access: Read-only
llcSapStatsTESTCommandsOut
The number of TEST commands this SAP has sent. This value measures the number of other stations to which the system is trying to connect.
This object is initialized to zero when the SAP is created.
Syntax: Counter32
Max-Access: Read-only
llcSapStatsTESTResponsesIn
The number of TEST responses this SAP has received. This value measures the number of stations in the network responding to TEST commands this SAP has sent. This object is initialized to zero when the SAP is created.
Syntax: Counter32
Max-Access: Read-only
llcSapStatsTESTResponsesOut
The number of TEST responses this SAP has sent. This value measures the number of other stations trying to connect to this SAP. This object is initialized to zero when the SAP is created.
Syntax: Counter32
Max-Access: Read-only
llcSapStatsXIDCommandsIn
The number of XID commands this SAP has received. This value is a measure of the number of stations in the network trying to connect to this SAP. This object is a count of all XIDs, including SNA XID, IEEE XID, null XID, and non-activation XIDs. This object is initialized to zero when the SAP is created.
Syntax: Counter32
Max-Access: Read-only
llcSapStatsXIDCommandsOut
The number of XID commands this SAP has sent. This value is a measure of the number of other stations this SAP is trying to connect to. This object is a count of all XIDs, including SNA XID, IEEE XID, null XID, and non-activation XIDs. This object is initialized to zero when the SAP is created.
Syntax: Counter32
Max-Access: Read-only
llcSapStatsXIDResponsesIn
The number of XID responses this SAP has received. This value is a measure of the number of stations in the network responding to TEST commands this SAP has sent. This object is a count of all XIDs, including SNA XID, IEEE XID, null XID, and non-activation XIDs. This object is initialized to zero when the SAP is created.
Syntax: Counter32
Max-Access: Read-only
llcSapStatsXIDResponsesOut
The number of XID responses this SAP has sent. This value is a measure of the number of other stations trying to connect to this SAP. This object is a count of all XIDs, including SNA XID, IEEE XID, null XID, and non-activation XIDs. This object is initialized to zero when the SAP is created.
Syntax: Counter32
Max-Access: Read-only
llcSapStatsUIFramesIn
The total number of unnumber
