|
|
This chapter describes the group of MIB variables managed by Cisco Systems.
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.
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
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
The code set used for the line controls.
Syntax: Integer 1 = ebcdic, 2 = ascii
Max-Access: Read-only
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
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
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
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 nonzero, it indicates a problem in the configuration.
Syntax: Counter32
Max-Access: Read-only
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
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
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
This table contains information about specific control units.
Syntax: SEQUENCE OF BscCUEntry
Max-Access: Not-accessible
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
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
The number of sent bytes (octets), including all control characters.
Syntax: Counter32
Max-Access: Read-only
The number of received bytes (octets), including all control characters.
Syntax: Counter32
Max-Access: Read-only
The number of sent frames (blocks), including all control frames.
Syntax: Counter32
Max-Access: Read-only
The number of received frames (blocks), including all control frames.
Syntax: Counter32
Max-Access: Read-only
The number of sent data frames (blocks).
Syntax: Counter32
Max-Access: Read-only
The number of received data frames (blocks).
Syntax: Counter32
Max-Access: Read-only
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
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
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
The variables in this section provide configuration and operational information for Cisco's blocked serial tunneling (BSTUN) implementation.
The configured IP address used by the BSTUN component in this router.
Syntax: IpAddress
Max-Access: Read-only
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
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
The protocol type for this BSTUN group.
Syntax: Integer 1 = BSC (Binary Synchronous Communications)
Max-Access: Read-only
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
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
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 nonzero 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
This table contains a list of BSTUN-enabled interfaces (ports).
Syntax: SEQUENCE OF BstunPortEntry
Max-Access: Not-accessible
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
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
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
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
End of Table
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
The index of the BSTUN Group owning this station.
Syntax: Integer (1-255)
Max-Access: Not-accessible
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
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
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
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
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
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
The number of frames received from the serial interface with this station's address.
Syntax: Counter32
Max-Access: Read-only
The number of frames transmitted at the serial interface with this station's address.
Syntax: Counter32
Max-Access: Read-only
The number of bytes received from the serial interface with this station's address.
Syntax: Counter32
Max-Access: Read-only
The number of bytes transmitted at the serial interface with this station's address.
Syntax: Counter32
Max-Access: Read-only
End of Table
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).
The CIP group specifies the MIB module for objects used to manage the Cisco Channel Interface Processor card.
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
Specifies the index into the cipCardTable. (Not the physical chassis slot number but the Cisco chassis MIB cardindex.)
Syntax: Integer32
Max-Access: Not-accessible
Specifies the configured name for the CIP.
Syntax: DisplayString (SIZE (1-32))
Max-Access: Read-only
Specifies total memory on the card in kilobytes.
Syntax: Integer32
Max-Access: Read-only
Specifies the total free memory on the card, that is the amount of memory in kilobytes not in use.
Syntax: Integer32
Max-Access: Read-only
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
The major software revision number for the software loaded on the CIP.
Syntax: Integer32
Max-Access: Read-only
The minor software revision number for the software loaded on the CIP.
Syntax: Integer32
Max-Access: Read-only
The major hardware revision number for the software loaded on the CIP.
Syntax: Integer32
Max-Access: Read-only
The minor hardware revision number for the software loaded on the CIP.
Syntax: Integer32
Max-Access: Read-only
End of Table
This table contains a list of objects pertaining to the daughter board on the CIP card.
Specifies which daughter board is being referenced for a particular CIP card.
Syntax: Integer32
Max-Access: Not-accessible
Indicates the channel path interface type.
Syntax: Integer 1 = escon (Enterprise System Connection), 2 = busAndTag
Max-Access: Read-only
Specifies that the microcode for the daughter board has been successfully loaded and is executing.
Syntax: TruthValue
Max-Access: Read-only
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
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
Counts the number of times the ESCON Processor recovers from an internal error.
Syntax: Counter32
Max-Access: Read-only
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
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
Specifies the number of link failures recognized as a result of the not-operational sequence (NOS).
Syntax: Counter32
Max-Access: Read-only
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
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
Indicates the condition that caused the last SNMP trap.
Integer
| 1 = liOther | Reason other than what is defined in conditions 2-7. |
| 2 = liStatus | Indicates that the daughterboard 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 a nonoperational 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
End of Table
This table contains a list of objects pertaining to subchannel connections referenced by the CIP card or its daughter board.
Indicates which subchannel is being referenced for a particular daughter board on a CIP card. This value is constructed as follows:
path * 256 + device
Path and device are the values in CipCardClawConfigTable.
Syntax: Integer32
Max-Access: Read-only
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
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
Specifies the number of system resets.
Syntax: Counter32
Max-Access: Read-only
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
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
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
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
Specifies the CLAW connection status.
Syntax: TruthValue
Max-Access: Read-only
End of Table
Contains configuration information for the Common Link Access for Workstations (CLAW) protocol.
Syntax: SEQUENCE OF CipCardClawConfigEntry
Max-Access: Not-accessible
Specifies a list of CLAW configuration values.
Syntax: CipCardClawConfigEntry
Max-Access: Not-accessible
Specifies the hex path identifier for the ESCON director switch port containing the fiber from the channel on the host to which this CIP CLAW task connects.
This identifier is a concatenation of the switch port number, the channel logical address used by the host to associate a logical partition (LPAR) with the control unit, and the control unit logical address (address of a logical control unit used by the host to associate a group of physical devices).
For a directly connected channel, the switch port number is usually 01.
Syntax: Octet string (SIZE (2))
Max-Access: Read-write
The two-digit hex device address for the device the SNA host will use to communicate with the CLAW task on the CIP. The address must be even.
Syntax: Octet string (SIZE (2))
Max-Access: Read-write
Specifies the IP address of the host application for the CIP CLAW task as specified in the HOME statement of the PROFILE TCPIP.
Syntax: IpAddress
Max-Access: Read-write
Specifies the CLAW host name for this CLAW device.
Syntax: DisplayString
Max-Access: Read-write
Specifies the CLAW router name for this CLAW device.
Syntax: DisplayString
Max-Access: Read-write
Specifies the CLAW host application name for this CLAW connection.
Syntax: DisplayString
Max-Access: Read-write
Specifies the CLAW router application name for this CLAW connection.
Syntax: DisplayString
Max-Access: Read-write
End of Table
Specifies a list of objects pertaining to data transfer statistics per CLAW logical link.
Syntax: SEQUENCE OF CipCardClawDataXferStatsEntry
Max-Access: Not-accessible
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
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
This table contains information about the applications loaded on the CIP.
Syntax: SEQUENCE OF CipCardApplicationEntry
Max-Access: Not-accessible
A list of application information.
Syntax: CipCardApplicationEntry
Max-Access: Not-accessible
The application name.
Syntax: DisplayString(SIZE (32))
Max-Access: Not-accessible
The application's software revision number.
Syntax: Integer32
Max-Access: Read-only
The application's compilation information (date and user ID).
Syntax: DisplayString(SIZE (1-64))
Max-Access: Read-only
The following notification is supported with the cipCard MIB:
This trap indicates that a significant link event has been recognized, resulting in the degradation of the interface line quality.
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.
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
The channel path for this Channel Systems Network Architecture table entry.
Syntax: ChannelPath
Max-Access: Read-create
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
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
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
The current state of the CSNA entry.
Integer
| 0 = closed | The link is closed. |
| 1 = pendingOpen | An Open Subchannel command has been received from the host. |
| 2 = open | Subchannel is open. |
| 3 = pendingSetup | The host has queried for LAN information. |
| 4 = setupComplete | LAN information has been sent to the host. |
| 5 = pendingClose | A Close Subchannel command has been received from the host. |
Max-Access: Read-only
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.
Integer
| 0 = normal | The link is not in slowdown state. |
| 1 = slowDownSent | The router has put VTAM into a slowdown state. |
| 2 = slowDownReceived | VTAM has put the router into a slowdown state. |
| 3 = slowDownSentReceived | Both VTAM and the router are in the slowdown state. |
Max-Access: Read-only
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
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
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
The number of blocks transmitted.
Syntax: Counter32
Max-Access: Read-only
The number of blocks received.
Syntax: Counter32
Max-Access: Read-only
The number of bytes transmitted.
Syntax: Counter32
Max-Access: Read-only
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
The number of bytes received.
Syntax: Counter32
Max-Access: Read-only
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
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
This table contains configured values for CSNA sessions supported on the Channel Interface Processor (CIP) card.
Syntax: SEQUENCE OF CipCardSessionsAdminEntry
Max-Access: Not-accessible
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
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
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
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
This table contains the map between VTAM (the I/O device address) and the internal identifier--LAN adapter, media access control (MAC) address, or service access point (SAP).
Syntax: SEQUENCE OF CipCardCsnaConnEntry
Max-Access: Not-accessible
The active sessions in this VTAM-to-internal-LAN adapter/MAC address mapping.
Syntax: Gauge32
Max-Access: Read-only
The slot number of the CIP card on which the path and device are configured.
Syntax: Integer32
Max-Access: Read-only
The port number of the interface on the CIP card on which the path and device are configured.
Syntax: Integer32
Max-Access: Read-only
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
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
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.
The variables in this section are used to manage the Cisco internal LAN support (LAN and adapter) on the Channel Interface Processor (CIP).
This table contains configuration information for the LAN feature on the Channel Interface Processor (CIP).
Syntax: SEQUENCE OF CipCardLanAdminEntry
Max-Access: Not-accessible
The type of emulation applied to this CIP LAN.
Syntax: Integer 1 = iso88023csmacd, 2 = iso88025tokenRing, 3 = fddi
Max-Access: Not-accessible
The index value used with the ifIndex to uniquely identify a CIP LAN.
Syntax: Integer (1-31)
Max-Access: Not-accessible
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
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
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
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
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
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
This table contains configuration information for the LAN adapter feature on the Channel Interface Processor (CIP).
Syntax: SEQUENCE OF CipCardLanAdaptAdminEntry
Max-Access: Not-accessible
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 media access control (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
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
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
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 a replication of the TCP/IP stack that is based on the IP address of the stack.
The IP routing table is not supported here.
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 (the Cisco TCP offload MIB). Use this table to view statistics and status for the IP stack.
Syntax: SEQUENCE OF CipIpEntry
Max-Access: Not-accessible
The IP address for this IP stack.
Syntax: IpAddress
Max-Access: Not-accessible
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
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
The total number of input datagrams received from interfaces, including those received in error.
Syntax: Counter32
Max-Access: Read-only
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
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
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
The number of locally-addressed datagrams received successfully but discarded because of an unknown or unsupported protocol.
Syntax: Counter32
Max-Access: Read-only
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
The total number of input datagrams successfully delivered to IP user-protocols (including ICMP).
Syntax: Counter32
Max-Access: Read-only
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
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
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
The maximum number of seconds that received fragments are held while they are awaiting reassembly at this entity.
Syntax: Integer
Max-Access: Read-only
The number of IP fragments received that needed to be reassembled at this entity.
Syntax: Counter32
Max-Access: Read-only
The number of IP datagrams successfully re-assembled.
Syntax: Counter32
Max-Access: Read-only
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
The number of IP datagrams that have been successfully fragmented at this entity.
Syntax: Counter32
Max-Access: Read-only
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
The number of IP datagram fragments generated as a result of fragmentation at this entity.
Syntax: Counter32
Max-Access: Read-only
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
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 (the Cisco TCP offload MIB). Use this table to view statistics and status for the TCP stack.
Syntax: SEQUENCE OF CipTcpStackEntry
Max-Access: Not-accessible
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
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
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
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
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
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
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
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
The number of TCP connections for which the current state is either ESTABLISHED or CLOSE-WAIT.
Syntax: Gauge32
Max-Access: Read-only
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
The total number of segments sent, including those on current connections but excluding those containing only retransmitted octets.
Syntax: Counter32
Max-Access: Read-only
The total number of segments retransmitted--that is, the number of TCP segments transmitted containing one or more previously transmitted octets.
Syntax: Counter32
Max-Access: Read-only
The total number of segments received in error (for example, bad TCP checksums).
Syntax: Counter32
Max-Access: Read-only
The number of TCP segments sent containing the RST flag.
Syntax: Counter32
Max-Access: Read-only
End of Table
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
The local port number for this TCP connection.
Syntax: Integer (0-65535)
Max-Access: Not-accessible
The remote IP address for this TCP connection.
Syntax: IpAddress
Max-Access: Not-accessible
The remote port number for this TCP connection.
Syntax: Integer (0-65535)
Max-Access: Not-accessible
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
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
The number of bytes sent for this TCP connection.
Syntax: Counter32
Max-Access: Read-only
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
The number of bytes received for this TCP connection.
Syntax: Counter32
Max-Access: Read-only
End of Table
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
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
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
The number of ICMP Destination Unreachable messages received.
Syntax: Counter32
Max-Access: Read-only
The number of ICMP Time Exceeded messages received.
Syntax: Counter32
Max-Access: Read-only
The number of ICMP Parameter Problem messages received.
Syntax: Counter32
Max-Access: Read-only
The number of ICMP Source Quench messages received.
Syntax: Counter32
Max-Access: Read-only
The number of ICMP Redirect messages received.
Syntax: Counter32
Max-Access: Read-only
The number of ICMP Echo (request) messages received.
Syntax: Counter32
Max-Access: Read-only
The number of ICMP Address Mask Reply messages received.
Syntax: Counter32
Max-Access: Read-only
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
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
The number of ICMP Destination Unreachable messages sent.
Syntax: Counter32
Max-Access: Read-only
The number of ICMP Echo (request) messages sent.
Syntax: Counter32
Max-Access: Read-only
The number of ICMP Echo Reply messages sent.
Syntax: Counter32
Max-Access: Read-only
The number of ICMP Timestamp (request) messages sent.
Syntax: Counter32
Max-Access: Read-only
The number of ICMP Timestamp Reply messages sent.
Syntax: Counter32
Max-Access: Read-only
The number of ICMP Address Mask Request messages sent.
Syntax: Counter32
Max-Access: Read-only
The number of ICMP Address Mask Reply messages sent.
Syntax: Counter32
Max-Access: Read-only
End of Table
This table contains a list of parameters pertaining to each User Datagram Protocol (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 (the Cisco TCP Offload MIB). Use this table to view statistics and status for the UDP stack.
Syntax: SEQUENCE OF CipUdpEntry
Max-Access: Not-accessible
The total number of UDP datagrams delivered to UDP users.
Syntax: Counter32
Max-Access: Read-only
The total number of received UDP datagrams for which there was no application at the destination port.
Syntax: Counter32
Max-Access: Read-only
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
The total number of UDP datagrams sent from this entity.
Syntax: Counter32
Max-Access: Read-only
End of Table
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
The local port number for this UDP listener.
Syntax: Integer (0-65535)
Max-Access: Read-only
End of Table
The variables in this section represent the router configuration data as it can be stored in the following locations:
| Running | The configuration in volatile memory and in use by the running system. |
| Terminal | The configuration as typed in by an operator or sent to a terminal. |
| Local | The configuration saved locally in nonvolatile RAM (NVRAM) or in Flash memory. |
| Remote | The configuration saved to a server on the network. |
The purpose of the Configuration MIB is to track the changes and saves of the running configuration, in relationship to the running configuration. Changes that originate from the terminal for individual parameters and complete replacement of the configuration can be tracked, along with the destination to which that a configuration is saved. Once outside the view of the local system (for example, a file on a remote system), the MIB does not have the ability to track the configuration.
The Configuration MIB does not track parameter changes made via SNMP, other than the complete replacement of the configuration.
The value of sysUpTime when the running configuration was last changed.
If the value of ccmHistoryRunningLastChanged is greater than ccmHistoryRunningLastSaved, the configuration has been changed but not saved.
Syntax: TimeTicks
Max-Access: Read-only
The value of sysUpTime when the running configuration was last saved (written).
If the value of ccmHistoryRunningLastChanged is greater than ccmHistoryRunningLastSaved, the configuration has been changed but not saved.
What constitutes a safe saving of the running configuration is a management policy issue beyond the scope of this MIB. For some installations, writing the running configuration to a terminal may be a way of capturing and saving it. Others may use local or remote storage. Thus any write operation is considered "saving" for the purposes of the MIB.
Syntax: TimeTicks
Max-Access: Read-only
The value of sysUpTime when the startup configuration was last written to. In general, the startup configuration is the default configuration used to cold-start the system. The configuration might have been changed when the running configuration was saved, or by a copy from another location.
Syntax: TimeTicks
Max-Access: Read-only
The maximum number of entries that can be held in ccmHistoryEventTable.
Syntax: Integer32 (0-2147483647)
Max-Access: Read-only
The number of times the oldest entry in ccmHistoryEventTable was deleted to make room for a new entry.
Syntax: Counter32
Max-Access: Read-only
A table of configuration events on this router.
Syntax: SEQUENCE OF CcmHistoryEventEntry
Max-Access: Not-accessible
Information about a configuration event on this router.
Syntax: CcmHistoryEventEntry
Max-Access: Not-accessible
A monotonically increasing integer for the sole purpose of indexing events. When it reaches the maximum value (an unlikely event), the agent wraps the value back to 1 and may flush existing entries.
Syntax: Integer32 (1-2147483647)
Max-Access: Not-accessible
The value of sysUpTime when the event occurred.
Syntax: TimeTicks
Max-Access: Read-only
The source of the command that instigated the event.
Syntax: Integer 1 = commandLine, 2 = snmp
Max-Access: Read-only
The configuration data source for the event.
Syntax: HistoryEventMedium
Max-Access: Read-only
ccmHistoryEventConfigDestination
The configuration data destination for the event.
Syntax: HistoryEventMedium
Max-Access: Read-only
If the value of ccmHistoryEventCommandSource is commandLine, this variable indicates the terminal type. Otherwise, this variable equals notApplicable.
Syntax: Integer 1 = notApplicable, 2 = unknown, 3 = console, 4 = terminal, 5 = virtual, 6 = auxiliary
Max-Access: Read-only
If the value of ccmHistoryEventCommandSource is commandLine, this variable indicates the terminal number. The value is -1 if not available or not applicable.
Syntax: Integer32
Max-Access: Read-only
If the value of ccmHistoryEventCommandSource is commandLine, this variable indicates the name of the user logged in. The length is zero if not available or not applicable.
Syntax: DisplayString (SIZE (0-64))
Max-Access: Read-only
ccmHistoryEventTerminalLocation
If the value of ccmHistoryEventCommandSource is commandLine, this variable indicates the hard-wired location of the terminal or the remote host for an incoming connection. The length is zero if not available or not applicable.
Syntax: DisplayString (SIZE (0-64))
Max-Access: Read-only
ccmHistoryEventCommandSourceAddress
If the value of ccmHistoryEventTerminalType is virtual, this variable indicates the Internet address of the connected system. If the value of ccmHistoryEventCommandSource is snmp, this variable indicates the Internet address of the requestor. The value is 0.0.0.0 if not available or not applicable.
Syntax: IpAddress
Max-Access: Read-only
ccmHistoryEventVirtualHostName
If the value of ccmHistoryEventTerminalType is virtual, this variable indicates the host name of the connected system. The length is zero if not available or not applicable.
Syntax: DisplayString (SIZE (0-64))
Max-Access: Read-only
If the value of ccmHistoryEventConfigSource or ccmHistoryEventConfigDestination is networkTftp or networkRcp, this variable indicates the Internet address of the storage file server. The value is 0.0.0.0 if not applicable or not available.
Syntax: IpAddress
Max-Access: Read-only
If the value of ccmHistoryEventConfigSource or ccmHistoryEventConfigDestination is networkTftp or networkRcp, this variable indicates the configuration file name at the storage file server. The length is zero if not available or not applicable.
Syntax: DisplayString (SIZE (0-64))
Max-Access: Read-only
If the value of ccmHistoryEventConfigSource or ccmHistoryEventConfigDestination is networkRcp, this variable indicates the remote user name. The length is zero if not applicable or not available.
Syntax: DisplayString (SIZE (0-64))
Max-Access: Read-only
End of Table
The variables in this section are used to manage data link switching (DLSw).
The DLSw MIB is organized in the following groups:
| ciscoDlswNode | Information about this DLSw. |
| ciscoDlswTConn | Information about adjacent DLSw partners. |
| ciscoDlswInterface | Information about the interfaces on which DLSw is active. |
| ciscoDlswCircuit | Information about established circuits. |
The ciscoDlswNode group contains nine objects and one table, ciscoDlswTrapControl, consisting of four objects.
The particular version of the DLSw standard supported by this DLSw. The first octet is a hexadecimal value representing the DLSw standard version number of this DLSw, and the second is a hexadecimal value representing the DLSw standard release number. This information is reported in DLSw Capabilities Exchange messages. (Reference: RFC 1795)
Syntax: Octet String (SIZE (2))
Max-Access: Read-only
The manufacturer's IEEE-assigned organizationally unique identifier (OUI) of this DLSw. This information is reported in DLSw Capabilities Exchange messages. (Reference: RFC 1795)
Syntax: Octet String (SIZE (3))
Max-Access: Read-only
Product-specific information about this DLSw--for example, product name, code release, and fix level. This information is reported in Capabilities Exchange messages. (Reference: RFC 1795)
Syntax: DisplayString (SIZE (0-255))
Max-Access: Read-only
Circuit pacing, as defined in the DLSw Standard, allows each of the two DLSw nodes on a circuit to control the amount of data the other is permitted to send to it. This object reflects the level of support an implementation has for this protocol. The value 1 means the node has no support for the standard circuit pacing flows; it may use RFC 1434+ methods only, or a proprietary flow control scheme. The value 2 means the node supports the standard scheme and can vary the window sizes it grants as a data receiver. The value 3 means the node supports the standard scheme but never varies its receive window size.
Syntax: Integer 1 = none (does not support DLSw Standard pacing scheme), 2 = adaptiveRcvWindow (the receive window size varies), 3 = fixedRcvWindow (the receive window size remains constant)
Max-Access: Read-only
The status of the DLSw part of the system. Changing the value from active to inactive causes DLSw to take the following actions:
Because these are destructive actions, the user should query the circuit and transport connection tables in advance to understand the effect these actions will have. Changing the value from inactive to active causes DLSw to come up in its initial state--that is, with transport connections established and ready to bring up circuits.
Syntax: Integer 1 = active, 2 = inactive
Max-Access: Read-only
The time (in hundredths of a second) since the DLSw portion of the system was last reinitialized. That is, if ciscoDlswStatus is in the active state, this variable shows the time at which the ciscoDlswStatus entered the active state. It remains zero if ciscoDlswStatus is in the inactive state.
Syntax: TimeTicks
Max-Access: Read-only
The largest frame (LF) size this DLSw can forward on any path through itself. This value can include the data-link control (DLC) header and INFO field but not media access control (MAC)-level or framing octets). This object can represent any box-level frame size forwarding restriction, for example, from the use of fixed-size buffers. Some DLSw implementations have no such restriction.
This value affects the LF size of circuits during circuit creation. The LF size of an existing circuit can be found in the routing information field (RIF). The default value is lfs65535.
Syntax: LFSize
Max-Access: Read-only
ciscoDlswResourceNBExclusivity
The value of true indicates that the NetBIOS names configured in ciscoDlswDirNBTable are the only ones accessible via this DLSw.
If a node supports sending run-time Capabilities Exchange messages, changes to this object should cause that action. The implementation must determine when to start the run-time capabilities exchange.
Syntax: TruthValue
Max-Access: Read-only
ciscoDlswResourceMacExclusivity
The value of true indicates that the MAC addresses configured in the ciscoDlswDirMacTable are the only ones accessible via this DLSw.
If a node supports sending run-time Capabilities Exchange messages, changes to this object should cause that action. The implementation must determine when to start the run-time capabilities exchange.
Syntax: TruthValue
Max-Access: Read-only
ciscoDlswTrapCntlTConnPartnerReject
Indicates whether the DLSw is permitted to emit partner reject-related traps. With the value of enabled the DLSw emits all partner reject related traps. With the value of disabled the DLSw does not emit any partner reject related traps. With the value of partial the DLSw emits partner reject traps only for Capabilities Exchange (CapEx) reject messages. The changes take effect immediately.
Syntax: Integer 1 = enabled, 2 = disabled, 3 = partial
Max-Access: Read-only
ciscoDlswTrapCntlTConnProtViolation
Indicates whether the DLSw is permitted to generate protocol-violation traps on events such as window size violations. The changes take effect immediately.
Syntax: TruthValue
Max-Access: Read-only
Indicates whether the DLSw is permitted to emit transport connection up and down traps. With the value of enabled the DLSw emits traps when connections enter connected and disconnected states. With the value of disabled the DLSw does not emit traps when connections enter connected and disconnected states. With the value of partial the DLSw emits transport connection down traps only when the connection is closed with a busy message. The changes take effect immediately.
Syntax: Integer 1 = enabled, 2 = disabled, 3 = partial
Max-Access: Read-only
Indicates whether the DLSw is permitted to generate circuit up and down traps. With the value of enabled the DLSw emits traps when circuits enter connected and disconnected states. With the value of disabled the DLSw does not emit traps when circuits enter connected and disconnected states. With the value of partial the DLSw emits traps only for those circuits that are initiated by this DLSw--for example, for circuits originating the CUR_CS message. The changes take effect immediately.
Syntax: Integer 1 = enabled, 2 = disabled, 3 = partial
Max-Access: Read-only
End of Table
The ciscoDlswTConn group contains ciscoDlswTConnStat, ciscoDlswTConnConfigTable, ciscoDlswTConnOperTable, and ciscoDlswTConnSpecific. Two additional tables are contained in ciscoDlswTConnSpecific: ciscoDlswTConnTcpConfigTable and ciscoDlswTConnTcpOperTable.
ciscoDlswTConnStatActiveConnections
The number of transport connections that are not in disconnected state.
Syntax: Gauge32
Max-Access: Read-only
The number of times transport connections in this node exited the connected state with zero active circuits on the transport connection.
Syntax: Counter32
Max-Access: Read-only
The number of times transport connections in this node exited the connected state with some nonzero number of active circuits on the transport connection. Normally, this means the transport connection failed unexpectedly.
Syntax: Counter32
Max-Access: Read-only
End of Table
This table defines the transport connections that are initiated or accepted by this DLSw. The structure of masks allows wildcard definition for a collection of transport connections by a conceptual row. For a specific transport connection, there may be multiple conceptual rows that match the transport address. The best match is the one that determines the characteristics of the transport connection.
Syntax: SEQUENCE OF ciscoDlswTConnConfigEntry
Max-Access: Not-accessible
Each conceptual row defines a collection of transport connections.
Syntax: ciscoDlswTConnConfigEntry
Max-Access: Not-accessible
The index to the conceptual row of the table.
Nonpositive numbers are not allowed. Objects are defined that point to conceptual rows of this table with this index value. Zero is used to denote that no corresponding row exists.
Index values are assigned by the managed station. These values should not be reused but should continue to increase in value until they wrap.
Syntax: Integer (1-65000)
Max-Access: Not-accessible
The object identifier, which indicates the transport domain of this conceptual row.
Syntax: OBJECT IDENTIFIER
Max-Access: Read-only
ciscoDlswTConnConfigLocalTAddr
The local transport address for this conceptual row of the transport connection definition.
Syntax: TAddress
Max-Access: Read-only
ciscoDlswTConnConfigRemoteTAddr
The remote transport address. Together with the ciscoDlswTConnConfigRemoteTAddrMask, the object instance of this conceptual row identifies a collection of the transport connections that are either initiated by this DLSw or initiated by a partner DLSw and accepted by this DLSw.
Syntax: TAddress
Max-Access: Read-only
ciscoDlswTConnConfigLastModifyTime
The value of ciscoDlswUpTime when the value of any object in this conceptual row was last changed. This value may be compared to ciscoDlswTConnOperConnectTime to determine whether values in this row are completely valid for a transport connection created using this row definition.
Syntax: DlswTimeStamp
Max-Access: Read-only
The type of entry in the associated conceptual row. The value of individual means that the entry applies to a specific partner DLSw node as identified by ciscoDlswTConnConfigRemoteTAddr and ciscoDlswTConnConfigTDomain. The value of global means that the entry applies to all partner DLSw nodes of the TDomain. The value of group means that the entry applies to a specific set of DLSw nodes in the TDomain. Any group definitions are enterprise-specific and are pointed to by ciscoDlswTConnConfigGroupDefinition. In the cases of global and group, the value in ciscoDlswTConnConfigRemoteTAddr may not have any significance.
Syntax: Integer 1 = individual, 2 = global, 3 = group
Max-Access: Read-only
ciscoDlswTConnConfigGroupDefinition
For conceptual rows of individual and global as specified in ciscoDlswTConnConfigEntryType, the instance of this object is 0.0. For conceptual rows of group, the instance points to the specific group definition.
Syntax: InstancePointer
Max-Access: Read-only
The behavior of the collection of transport connections that this conceptual row defines. The value of activePersistent, activeOnDemand, or passive means this DLSw will accept any transport connections, initiated by partner DLSw nodes, which are defined by this conceptual row. The value of activePersistent means this DLSw will also initiate the transport connections of this conceptual row and retry periodically if necessary. The value of activeOnDemand means this DLSw will initiate a transport connection of this conceptual row if a directory cache of hits exists. The value of other is implementation- specific. The value of excluded means that the specified node is not allowed to be a partner to this DLSw node. To take a certain conceptual row definition out of service, a value of notInService for ciscoDlswTConnConfigRowStatus should be used.
Syntax: Integer 1 = other, 2 = activePersistent, 3 = activeOnDemand, 4 = passive, 5 = excluded
Max-Access: Read-only
The SAP list indicates which SAPs are advertised to the transport connection defined by this conceptual row. Only SAPs with even numbers are represented, in the form of the most significant bit of the first octet representing the SAP 0, the next most significant bit representing the SAP 2, to the least significant bit of the last octet representing the SAP 254. Data link switching (DLSw) is allowed for any SAP that has 1 in its corresponding bit, but is not allowed otherwise. The whole SAP list must be changed if one SAP is changed. Changing the SAP list affects only new circuit establishment and has no effect on established circuits.
This list can be used to restrict specific partners from knowing about all the SAPs used by DLSw on all its interfaces. (These are represented in ciscoDlswIfSapList for each interface.) For instance, you may want to run NetBIOS with some partners but not others.
If a node supports sending run-time Capabilities Exchange messages, changes to this object should cause that action. The implementation must determine when to start the run-time capabilities exchange.
The default value AA000000000000000000000000000000 (AA plus 30 zeros) indicates support for SAPs 0, 4, 8, and C.
Syntax: Octet String (SIZE(16))
Max-Access: Read-only
ciscoDlswTConnConfigAdvertiseMacNB
The value of true indicates that defined local MAC addresses and NetBIOS names are advertised to a partner node via initial and (if supported) run-time Capabilities Exchange messages. The default value is true.
Syntax: TruthValue
Max-Access: Read-only
ciscoDlswTConnConfigInitCirRecvWndw
The initial circuit receive pacing window size, in the unit of Switch-to-Switch Protocol (SSP) messages, to be used for future transport connections activated by means of this table row. The managed node sends this value as its initial receive pacing window size in its initial Capabilities Exchange message. Changing this value does not affect the initial circuit receive pacing window size of currently active transport connections. If the standard window pacing scheme is not supported, the value is zero.
A larger receive window value may be appropriate for partners that are reachable only via physical paths that have longer network delays. The default value is 1.
Syntax: Integer (0-65535)
Max-Access: Read-only
Number of times transport connections entered the connected state according to the definition of this conceptual row.
Syntax: Counter32
Max-Access: Read-only
This object is used by a management station to create or delete the row entry in the ciscoDlswTConnConfigTable following the RowStatus textual convention. The value of notInService is used to take a conceptual row definition out of use.
Syntax: RowStatus
Max-Access: Read-only
End of Table
A list of transport connections. It is optional but desirable for an implementation to keep an entry for some period of time after the transport connection is disconnected. Retaining the entry allows a network management station to capture additional useful information about the connection, in particular, statistical information and the cause of the disconnection.
Note the following about the transport connection operation table:
Syntax: SEQUENCE OF ciscoDlswTConnOperEntry
Max-Access: Not-accessible
Syntax: ciscoDlswTConnOperEntry
Max-Access: Not-accessible
The object identifier, which indicates the transport domain of this transport connection.
Syntax: OBJECT IDENTIFIER
Max-Access: Not-accessible
The local transport address for this transport connection. This value can be different from ciscoDlswTConnConfigLocalAddr if the value of the latter is changed after this transport connection was established.
Syntax: TAddress
Max-Access: Read-only
The remote transport address of this transport connection.
Syntax: TAddress
Max-Access: Not-accessible
The value of ciscoDlswUpTime when this transport connection conceptual row was created.
Syntax: DlswTimeStamp
Max-Access: Read-only
The value of ciscoDlswUpTime when this transport connection last entered the connected state. A value of zero means this transport connection has never been established.
Syntax: DlswTimeStamp
Max-Access: Read-only
The state of this transport connection. The transport connection enters the connecting state when DLSw makes a connection request to the transport layer. Once an initial Capabilities Exchange message is sent, the transport connection enters the initCapExchange state. When partner capabilities have been determined and the transport connection is ready for sending CanUReach (CUR) messages, it moves to the connected state. When DLSw is in the process of bringing down the connection, it is in the disconnecting state. When the transport layer indicates one of its connections is disconnected, the transport connection moves to the disconnected state.
Whereas all of the values are returned in response to a management protocol retrieval operation, only two values may be specified in a management protocol set operation: quiescing and disconnecting. Changing the value to quiescing prevents new circuits from being established, and causes a transport disconnection when the last circuit on the connection goes away. Changing the value to disconnecting forces all circuits to be off immediately, and bring the connection to the disconnected state.
Syntax: Integer 1 = connecting, 2 = initCapExchange, 3 = connected, 4 = quiescing, 5 = disconnecting, 6 = disconnected
Max-Access: Read-only
The value of ciscoDlswTConnConfigIndex of the ciscoDlswTConnConfigEntry that governs the configuration information used by this ciscoDlswTConnOperEntry. A management station can therefore normally examine both configured and operational information for this transport connection.
This value is zero if the corresponding ciscoDlswTConnConfigEntry was deleted after the creation of this ciscoDlswTConnOperEntry. If some fields in the former were changed but the conceptual row was not deleted, some configuration information may not be valid for this operational transport connection. A network management application can compare ciscoDlswTConnOperConnectTime and ciscoDlswTConnConfigLastModifyTime to determine if this condition exists.
Syntax: Integer (1-65000)
Max-Access: Read-only
ciscoDlswTConnOperFlowCntlMode
The flow control mechanism in use on this transport connection. This value is undetermined before the mode of flow control can be established on a new transport connection--that is, after a Capabilities Exchange message is sent but before a Capabilities Exchange message or other Switch-to-Switch Protocol (SSP) control messages have been received. Pacing indicates that the standard RFC 1795 pacing mechanism is in use. Other may be either the RFC 1434+ xBusy mechanism operating to a back-level DLSw, or a vendor-specific flow control method. Whether it is xBusy or not can be determined from ciscoDlswTConnOperPartnerVersion.
Syntax: Integer 1 = undetermined, 2 = pacing (DLSw standard flow control), 3 = other (non-DLSw standard flow control)
Max-Access: Read-only
ciscoDlswTConnOperPartnerVersion
This value identifies which version (first octet) and release (second octet) of the DLSw standard is supported by this partner DLSw. This information is obtained from a DLSw Capabilities Exchange message received from the partner DLSw. A string of zero length is returned before a Capabilities Exchange message is received, or if one is never received. A conceptual row with a ciscoDlswTConnOperState of connected but a zero length partner version indicates that the partner is a nonstandard DLSw partner.
If an implementation chooses to keep ciscoDlswTConnOperEntrys in the disconnected state, this value should remain unchanged. (Reference: RFC 1795)
Syntax: Octet String (SIZE (0 | 2))
Max-Access: Read-only
ciscoDlswTConnOperPartnerVendorID
The IEEE-assigned organizationally unique identifier (OUI) of the maker of this partner DLSw. This information is obtained from a DLSw Capabilities Exchange message received from the partner DLSw. A string of zero length is returned before a Capabilities Exchange message is received, or if one is never received.
If an implementation chooses to keep ciscoDlswTConnOperEntrys in the disconnected state, this value should remain unchanged.
Syntax: Octet String (SIZE (0 | 3))
Max-Access: Read-only
ciscoDlswTConnOperPartnerVersionStr
The particular product version--for example, the product name, code level, or fix level of this partner DLSw. The format of the actual version string is vendor-specific. This information is obtained from a DLSw Capabilities Exchange message received from the partner DLSw. A string of zero length is returned before a Capabilities Exchange message is received, if one is never received, or if one is received but does not contain a version string.
If an implementation chooses to keep ciscoDlswTConnOperEntrys in the disconnected state, this value should remain unchanged. (Reference: RFC 1795)
Syntax: DisplayString (SIZE (0-253))
Max-Access: Read-only
ciscoDlswTConnOperPartnerInitPacingWndw
The value of the partner initial receive pacing window. This window is the initial send pacing window for all new circuits on this transport connection, as modified and granted by the first flow control indication the partner sends on each circuit. This information is obtained from a DLSw Capabilities Exchange message received from the partner DLSw. A value of zero is returned before a Capabilities Exchange message is received, or if one is never received.
If an implementation chooses to keep ciscoDlswTConnOperEntrys in the disconnected state, this value should remain unchanged. (Reference: RFC 1795)
Syntax: Integer (0-65535)
Max-Access: Read-only
ciscoDlswTConnOperPartnerSapList
The Supported SAP List received in the Capabilities Exchange message from the partner DLSw. This list has the same format described for ciscoDlswTConnConfigSapList. A string of zero length is returned before a Capabilities Exchange message is received, or if one is never received.
If an implementation chooses to keep ciscoDlswTConnOperEntrys in the disconnected state, this value should remain unchanged.
Syntax: Octet String (SIZE (0 | 16))
Max-Access: Read-only
ciscoDlswTConnOperPartnerNBExcl
The value of true signifies that the NetBIOS names received from this partner in the NetBIOS name list in its Capabilities Exchange message are the only NetBIOS names reachable by that partner. False indicates that other NetBIOS names may be reachable. False should be returned before a Capabilities Exchange message is received, if one is never received, or if one is received without a NB Name Exclusivity control vector (CV).
If an implementation chooses to keep ciscoDlswTConnOperEntrys in the disconnected state, this value should remain unchanged.
Syntax: TruthValue
Max-Access: Read-only
ciscoDlswTConnOperPartnerMacExcl
The value of true signifies that the media access control (MAC) addresses received from this partner in the MAC address list in its Capabilities Exchange message are the only MAC addresses reachable by that partner. False indicates that other MAC addresses may be reachable. False should be returned before a Capabilities Exchange message is received, if one is never received, or if one is received without a MAC Address Exclusivity control vector.
If an implementation chooses to keep ciscoDlswTConnOperEntrys in the disconnected state, this value should remain unchanged.
Syntax: TruthValue
Max-Access: Read-only
ciscoDlswTConnOperPartnerNBInfo
This DLSw must determine whether to keep none, some, or all of the NetBIOS name list that was received in the Capabilities Exchange message sent by this partner DLSw. This object identifies how much information was kept by this DLSw. These names are stored as userConfigured remote entries in ciscoDlswDirNBTable. A value of 4, notApplicable, should be returned before a Capabilities Exchange message is received, or if one is never received.
If an implementation chooses to keep ciscoDlswTConnOperEntrys in the disconnected state, this value should remain unchanged.
Syntax: Integer 1 = none (none is kept), 2 = partial (partial list is kept), 3 = complete (complete list is kept), 4 = notApplicable
Max-Access: Read-only
ciscoDlswTConnOperPartnerMacInfo
This DLSw must determine whether to keep none, some, or all of the media access control (MAC) address list that was received in the Capabilities Exchange message sent by this partner DLSw. This object identifies how much information was kept by this DLSw. These names are stored as userConfigured remote entries in ciscoDlswDirMACTable. A value of 4, notApplicable, should be returned before a Capabilities Exchange message is received, or if one is never received.
If an implementation chooses to keep ciscoDlswTConnOperEntrys in the disconnected state, this value should remain unchanged.
Syntax: Integer 1 = none (none is kept), 2 = partial (partial list is kept), 3 = complete (complete list is kept), 4 = notApplicable
Max-Access: Read-only
The value of ciscoDlswUpTime when ciscoDlswTConnOperState last entered disconnected state.
Syntax: DlswTimeStamp
Max-Access: Read-only
The reason that either prevented the transport connection from entering the connected state, or caused the transport connection to enter the disconnected state.
Syntax: Integer 1 = other, 2 = capExFailed, 3 = transportLayerDisc, 4 = operatorCommand, 5 = lastCircuitDiscd, 6 = protocolError
Max-Access: Read-only
ciscoDlswTConnOperDiscActiveCir
The number of circuits active (not in disconnected state) at the time the transport connection was last disconnected. This value is zero if the transport connection has never been connected.
Syntax: Integer (0-65000)
Max-Access: Read-only
The number of Switch-to-Switch Protocol (SSP) messages of type DGRMFRAME, DATAFRAME, or INFOFRAME received on this transport connection.
Syntax: Counter32
Max-Access: Read-only
The number of Switch-to-Switch Protocol (SSP) messages of type DGRMFRAME, DATAFRAME, or INFOFRAME transmitted on this transport connection.
Syntax: Counter32
Max-Access: Read-only
ciscoDlswTConnOperInDataOctets
The number of octets in Switch-to-Switch Protocol (SSP) messages of type DGRMFRAME, DATAFRAME, or INFOFRAME received on this transport connection. Each message is counted starting with the first octet following the SSP message header.
Syntax: Counter32
Max-Access: Read-only
ciscoDlswTConnOperOutDataOctets
The number of octets in Switch-to-Switch Protocol (SSP) messages of type DGRMFRAME, DATAFRAME, or INFOFRAME transmitted on this transport connection. Each message is counted starting with the first octet following the SSP message header.
Syntax: Counter32
Max-Access: Read-only
The number of Switch-to-Switch Protocol (SSP) messages received on this transport connection which were not of type DGRMFRAME, DATAFRAME, or INFOFRAME.
Syntax: Counter32
Max-Access: Read-only
The number of Switch-to-Switch Protocol (SSP) messages of transmitted on this transport connection which were not of type DGRMFRAME, DATAFRAME, or INFOFRAME.
Syntax: Counter32
Max-Access: Read-only
The number of CanUReach_ex messages sent on this transport connection.
Syntax: Counter32
Max-Access: Read-only
The number of ICanReach_ex messages received on this transport connection.
Syntax: Counter32
Max-Access: Read-only
The number of CanUReach_ex messages received on this transport connection.
Syntax: Counter32
Max-Access: Read-only
The number of ICanReach_ex messages sent on this transport connection.
Syntax: Counter32
Max-Access: Read-only
The number of NetBIOS_NQ_ex (NetBIOS Name Query-explorer) messages sent on this transport connection.
Syntax: Counter32
Max-Access: Read-only
The number of NETBIOS_NR_ex (NetBIOS Name Recognized-explorer) messages received on this transport connection.
Syntax: Counter32
Max-Access: Read-only
The number of NETBIOS_NQ_ex (NetBIOS Name Query-explorer) messages received on this transport connection.
Syntax: Counter32
Max-Access: Read-only
The number of NETBIOS_NR_ex (NetBIOS Name Recognized-explorer) messages sent on this transport connection.
Syntax: Counter32
Max-Access: Read-only
The number of times that circuits entered circuit_established state (not counting transitions from circuit_restart state).
Syntax: Counter32
Max-Access: Read-only
The number of currently active circuits on this transport connection, where active means not in disconnected state.
Syntax: Gauge32
Max-Access: Read-only
End of Table
ciscoDlswTConnSpecific consists of the two tables ciscoDlswTConnTcpConfigTable and ciscoDlswTConnTcpOperTable.
This table defines the TCP transport connections that are either initiated by or accepted by this DLSw. It augments the entries in ciscoDlswTConnConfigTable whose domain is ciscoDlswTCPDomain.
Syntax: SEQUENCE OF ciscoDlswTConnTcpConfigEntry
Max-Access: Not-accessible
Each conceptual row defines parameters that are specific to ciscoDlswTCPDomain transport connections.
Syntax: ciscoDlswTConnTcpConfigEntry
Max-Access: Not-accessible
ciscoDlswTConnTcpConfigKeepAliveInt
The time in seconds between TCP keepalive messages when no traffic is flowing. Zero signifies no keepalive protocol. Changes take effect only for new TCP connections. The default value is 0.
Syntax: Integer (0-1800)
Max-Access: Read-only
ciscoDlswTConnTcpConfigTcpConnections
The preferred number of TCP connections within a TCP transport connection. The actual number used is negotiated at Capabilities Exchange time. Changes take effect only for new transport connections. The default value is 2.
Syntax: Integer (1-16)
Max-Access: Read-only
ciscoDlswTConnTcpConfigMaxSegmentSize
The number of bytes that this node is willing to receive over the read TCP connection(s). Changes take effect for new transport connections. The default value is 4096.
Syntax: Integer (0-65535)
Max-Access: Read-only
End of Table
A list of TCP transport connections. It is optional but desirable for an implementation to keep an entry for some period of time after the transport connection is disconnected. Retaining an entry allows a network management station to capture additional useful information about the connection, in particular, statistical information and the cause of the disconnection.
Syntax: SEQUENCE OF ciscoDlswTConnTcpOperEntry
Max-Access: Not-accessible
Syntax: ciscoDlswTConnTcpOperEntry
Max-Access: Not-accessible
ciscoDlswTConnTcpOperKeepAliveInt
The time in seconds between TCP keepalive messages when no traffic is flowing. Zero signifies no keepalive protocol is operating.
Syntax: Integer (0-1800)
Max-Access: Read-only
ciscoDlswTConnTcpOperPrefTcpConnections
The number of TCP connections preferred by this DLSw partner, as received in its Capabilities Exchange message.
Syntax: Integer (1-16)
Max-Access: Read-only
ciscoDlswTConnTcpOperTcpConnections
The actual current number of TCP connections within this transport connection.
Syntax: Integer (1-16)
Max-Access: Read-only
End of Table
The ciscoDlswInterface group consists of the ciscoDlswIFTable.
The list of interfaces on which DLSw is active.
Syntax: SEQUENCE OF ciscoDlswIfEntry
Max-Access: Not-accessible
Syntax: ciscoDlswIfEntry
Max-Access: Not-accessible
This object is used by a management station to create or delete the row entry in the ciscoDlswIfTable following the RowStatus textual convention.
Syntax: RowStatus
Max-Access: Read-only
The segment number that uniquely identifies the virtual segment to which this DLSw interface is connected. Current source routing protocols limit this value to the range 0 through 4095. (The value 0 is used by some management applications for special test cases.) A value of 65535 signifies that no virtual segment is assigned to this interface. For instance, in a non-source routing environment, segment number assignment is not required. The default value is 65535.
Syntax: Integer (0-4095 | 65535)
Max-Access: Read-only
The SAP list indicates which SAPs are allowed to be data link switched through this interface. This list has the same format described for ciscoDlswTConnConfigSapList.
The implementation must determine when changes to this object take effect. Turning off a particular SAP can destroy active circuits that are using that SAP. The implementation may reject such changes until no circuits are active if it so chooses. In this case, the management station must close the circuits first, using ciscoDlswCircuitState.
The default value, AA000000000000000000000000000000 (AA plus 30 zeros) indicates support for SAPs 0, 4, 8, and C.
Syntax: Octet String (SIZE(16))
Max-Access: Read-only
End of Table
A circuit is the end-to-end association of two data link switching entities through one or two DLSw nodes. It is the concatenation of two data links, optionally with an intervening transport connection. The origin of the circuit is the end station that initiates the circuit. The target of the circuit is the end station that receives the initiation.
The ciscoDlswCircuit group consists of ciscoDlswCircuitStat and ciscoDlswCircuitTable.
The current number of circuits in ciscoDlswCircuitTable that are not in the disconnected state.
Syntax: Gauge32
Max-Access: Read-only
The total number of entries ever added to ciscoDlswCircuitTable, or reactivated when the table exits the disconnected state.
Syntax: Counter32
Max-Access: Read-only
This table is the DLSw entity's view of circuits. A conceptual row in the table is associated with each data link.
The following chart lists the various possible combinations of origin and target media access control (MAC) locations and the number of entries in this circuit table. IfIndex and RouteInfo are applied only if the location is local. TDomain and TAddr are applied only if thelocation is remote.
| Number of Entries in the Circuit Table | |||
|---|---|---|---|
| Origin End Station Location | ||
| Target End Station Location | internal | local | remote |
| internal | Not applicable | 2 | 1 |
| local | 2 | 2 | 1 |
| remote | 1 | 1 | Not applicable |
Most of the statistics related to circuits can be collected from LLC-2 link station table.
The Cisco DLSw circuit table is the circuit representation in the DLSw entity. Virtual data links are used to represent any internal end stations. A conceptual row is associated with each data link. Thus, any circuit without an intervening transport connection has two conceptual rows.
The table consists of the circuits being established, established circuits, and, as an implementation option, circuits that have been disconnected. For circuits carried over transport connections, an entry is created after the CanUReach (CUR_cs) message was sent or received. For circuits between two locally attached devices, or internal virtual MAC addresses, an entry is created when the equivalent of CUR_cs sent or received status is reached.
End station 1 (S1) and end station 2 (S2) are used to represent the two end stations of the circuit. S1 is always an end station that is locally attached. S2 may be locally attached or remote. If it is locally attached, the circuit is represented by two rows indexed by (A, B) and (B, A) where A and B are the relevant MACs and SAPs.
The table may be used to store the causes of disconnection of circuits. Cisco recommends that the oldest disconnected circuit entry be removed from this table when the memory space of disconnected circuits is needed.
Syntax: SEQUENCE OF ciscoDlswCircuitEntry
Max-Access: Not-accessible
Syntax: ciscoDlswCircuitEntry
Max-Access: Not-accessible
The MAC Address of end station 1 (S1) used for this circuit.
Syntax: MacAddress
Max-Access: Not-accessible
The SAP at end station 1 (S1) used for this circuit.
Syntax: Octet String (SIZE(1))
Max-Access: Not-accessible
The IfEntry index of the local interface through which end station 1 (S1) can be reached.
Syntax: Integer (0-65000)
Max-Access: Read-only
The DLC protocol in use between the DLSw node and end station 1 (S1).
Syntax: DlcType
Max-Access: Read-only
If source-route bridging (SRB) is in use between the DLSw node and end station 1 (S1), this is the routing information field describing the path between the two devices. Otherwise, the value is an octet string of zero length.
Syntax: Octet String (SIZE (0-30))
Max-Access: Read-only
The circuit ID assigned by this DLSw node to this circuit. The first four octets are the DLC port ID, and the second four octets are the Data Link Correlator. If the DLSw Switch-to-Switch Protocol (SSP) was not used to establish this circuit, the value is a string of zero length.
Syntax: Octet String (SIZE (0 | 8))
Max-Access: Read-only
Points to a conceptual row of the underlying data link control (DLC) MIB, which could either be the standard Synchronous Data Link Control (SDLC) or Logical Link Control (LLC) MIBs, or an enterprise-specific DLC MIB.
Syntax: InstancePointer
Max-Access: Read-only
The MAC address of end station 2 (S2) used for this circuit.
Syntax: MacAddress
Max-Access: Not-accessible
The SAP at end station 2 (S2) used for this circuit.
Syntax: Octet String (SIZE(1))
Max-Access: Not-accessible
The location of end station 2 (S2). If the location of S2 is local, the interface information is available in the conceptual row whose end station 1 (S1) and S2 are the S2 and the S1 of this conceptual row, respectively.
Syntax: EndStationLocation
Max-Access: Read-only
If the location of end station 2 (S2) is remote, this value is the transport domain of the transport protocol the circuit is running over. Otherwise, the value is 0.0.
Syntax: OBJECT IDENTIFIER
Max-Access: Read-only
If the location of end station 2 (S2) is remote, this object contains the address of the partner DLSw; otherwise, it is an octet string of zero length.
Syntax: TAddress
Max-Access: Read-only
The circuit ID assigned to this circuit by the partner DLSw node. The first four octets are the DLC port ID, and the second four octets are the Data Link Correlator. If the DLSw Switch-to-Switch Protocol (SSP) was not used to establish this circuit, the value is a string of zero length.
Syntax: Octet String (SIZE (0 | 8))
Max-Access: Read-only
This object specifies which of the two end stations initiated the establishment of this circuit.
Syntax: Integer 1 = s1, 2 = s2
Max-Access: Read-only
The value of ciscoDlswUpTime when this circuit table conceptual row was created.
Syntax: DlswTimeStamp
Max-Access: Read-only
The value of ciscoDlswUpTime when this circuit entered the current state.
Syntax: DlswTimeStamp
Max-Access: Read-only
The current state of this circuit. The implementation may choose to keep entries for some period of time after circuit disconnect, so the network management station can gather the time and cause of disconnection.
While all the specified values may be returned from a GET operation, the only settable value is disconnectPending. When this value is set, DLSw should perform the appropriate action given its previous state. For example, DLSw sends a HALT_DL message if the state was connected, to bring the circuit down to the disconnected state. Both the partner DLSw and local end station(s) should be notified as appropriate.
This MIB provides no facility to reestablish a disconnected circuit, because in DLSw this function should be performed by the end station.
Syntax: Integer 1 = disconnected, 2 = circuitStart, 3 = resolvePending, 4 = circuitPending, 5 = circuitEstablished, 6 = connectPending, 7 = contactPending, 8 = connected, 9 = disconnectPending, 10 = haltPending, 11 = haltPendingNoack, 12 = circuitRestart, 13 = restartPending
Max-Access: Read-only
The transmission priority of this circuit as understood by this DLSw node. This value is determined by the two DLSw nodes at circuit startup time. If this DLSw node does not support DLSw circuit priority, the value unsupported should be returned.
Syntax: Integer 0 = unsupported, 1 = low, 2 = medium, 3 = high, 4 = highest
Max-Access: Read-only
ciscoDlswCircuitFCSendGrantedUnits
The number of paced Switch-to-Switch Protocol (SSP) messages that this DLSw is currently authorized to send on this circuit before it must stop and wait for an additional flow control indication from the partner DLSw.
The value zero should be returned if this circuit is not running the DLSw pacing protocol.
Syntax: Integer (0-65535)
Max-Access: Read-only
ciscoDlswCircuitFCSendCurrentWndw
The current window size that this DLSw is using in its role as a data sender. This is the value by which this DLSw can increase the number of messages it is authorized to send if it receives a flow control indication with the bits specifying "repeat window."
The value zero should be returned if this circuit is not running the DLSw pacing protocol.
Syntax: Integer (0-65535)
Max-Access: Read-only
ciscoDlswCircuitFCRecvGrantedUnits
The current number of paced Switch-to-Switch Protocol (SSP) messages that this DLSw has authorized the partner DLSw to send on this circuit before the partner DLSw must stop and wait for an additional flow control indication from this DLSw.
The value zero should be returned if this circuit is not running the DLSw pacing protocol.
Syntax: Integer (0-65535)
Max-Access: Read-only
ciscoDlswCircuitFCRecvCurrentWndw
The current window size that this DLSw is using in its role as a data receiver. This is the number of additional paced Switch-to-Switch Protocol (SSP) messages that this DLSw can authorize its DLSw partner to send if this DLSw sends a flow control indication with the bits specifying "repeat window."
The value zero should be returned if this circuit is not running the DLSw pacing protocol.
Syntax: Integer (0-65535)
Max-Access: Read-only
ciscoDlswCircuitFCLargestRecvGranted
The largest receive window size granted by this DLSw during the current activation of this circuit. This is not the largest number of messages granted at any time, but the largest window size as represented by FCIND operator bits.
The value zero should be returned if this circuit is not running the DLSw pacing protocol.
Syntax: Gauge32
Max-Access: Read-only
ciscoDlswCircuitFCLargestSendGranted
The largest send window size (with respect to this DLSw) granted by the partner DLSw during the current activation of this circuit.
The value zero should be returned if this circuit is not running the DLSw pacing protocol.
Syntax: Gauge32
Max-Access: Read-only
ciscoDlswCircuitFCHalveWndwSents
The number of Halve Window operations this DLSw has sent on this circuit, in its role as a data receiver.
The value zero should be returned if this circuit is not running the DLSw pacing protocol.
Syntax: Counter32
Max-Access: Read-only
ciscoDlswCircuitFCResetOpSents
The number of Reset Window operations this DLSw has sent on this circuit, in its role as a data receiver.
The value zero should be returned if this circuit is not running the DLSw pacing protocol.
Syntax: Counter32
Max-Access: Read-only
ciscoDlswCircuitFCHalveWndwRcvds
The number of Halve Window operations this DLSw has received on this circuit, in its role as a data sender.
The value zero should be returned if this circuit is not running the DLSw pacing protocol.
Syntax: Counter32
Max-Access: Read-only
ciscoDlswCircuitFCResetOpRcvds
The number of Reset Window operations this DLSw has received on this circuit, in its role as a data sender.
The value zero should be returned if this circuit is not running the DLSw pacing protocol.
Syntax: Counter32
Max-Access: Read-only
ciscoDlswCircuitDiscReasonLocal
The reason why this circuit was last disconnected, as seen by this DLSw node.
This object is present only if the implementation retains circuit table entries for some period after circuit disconnect.
Syntax: Integer 1 = endStationDiscRcvd, 2 = endStationDlcError, 3 = protocolError, 4 = operatorCommand, 5 = haltDlRcvd, 6 = haltDlNoAckRcvd, 7 = transportConnClosed
Max-Access: Read-only
ciscoDlswCircuitDiscReasonRemote
The generic reason why this circuit was last disconnected, as reported by the DLSw partner in a HALT_DL or HALT_DL_NOACK. If the partner does not send a reason code in these messages, or the DLSw implementation does not report receiving one, the value unknown is returned.
This object is present only if the implementation retains circuit table entries for some period after circuit disconnection.
Syntax: Integer 0 = unknown, 1 = endStationDiscRcvd, 2 = endStationDlcError, 3 = protocolError, 4 = operatorCommand
Max-Access: Read-only
ciscoDlswCircuitDiscReasonRemoteData
Implementation-specific data reported by the DLSw partner in a HALT_DL or HALT_DL_NOACK, to help specify how and why this circuit was last disconnected. If the partner does not send this data in these messages, or the DLSw implementation does not report receiving it, a string of zero length is returned.
This object is present only if the implementation retains circuit table entries for some period after circuit disconnection.
Syntax: Octet String (SIZE (0 | 4))
Max-Access: Read-only
End of Table
This section defines the well-known notifications sent by DLSw agents. Care must be taken to ensure that no particular notification is sent to a single receiving entity more often than once every 5 seconds.
Traps include
ciscoDlswTrapTConnPartnerReject
This trap is sent each time a transport connection is rejected by a partner DLSw during Capabilities Exchanges.
Objects are ciscoDlswTConnOperTDomain, ciscoDlswTConnOperRemoteTAddr.
ciscoDlswTrapTConnProtViolation
This trap is sent each time a protocol violation is detected for a transport connection.
Objects are ciscoDlswTConnOperTDomain, ciscoDlswTConnOperRemoteTAddr.
This trap is sent each time a transport connection enters the connected state.
Objects are ciscoDlswTConnOperTDomain, ciscoDlswTConnOperRemoteTAddr.
This trap is sent each time a transport connection enters the disconnected state.
Objects are ciscoDlswTConnOperTDomain, ciscoDlswTConnOperRemoteTAddr.
This trap is sent each time a circuit enters the connected state.
Objects are ciscoDlswCircuitS1Mac, ciscoDlswCircuitS1Sap, ciscoDlswCircuitS2Mac, ciscoDlswCircuitS2Sap.
This trap is sent each time a circuit enters the disconnected state.
Objects are ciscoDlswCircuitS1Mac, ciscoDlswCircuitS1Sap, ciscoDlswCircuitS2Mac, ciscoDlswCircuitS2Sap.
The MIB module in this section describes the management of the Cisco Discovery Protocol (CDP) in Cisco devices.
The (conceptual) table containing the status of CDP on the device's interfaces.
Syntax: SEQUENCE OF CdpInterfaceEntry
Max-Access: Not-accessible
Specifies an entry (conceptual row) in the cdpInterfaceTable containing the status of CDP on an interface.
Syntax: CdpInterfaceEntry
Max-Access: Not-accessible
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
Provides an indication of whether the Cisco Discovery Protocol is currently running on this interface.
Syntax: TruthValue
Max-Access: Read-write
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
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
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
Specifies the (conceptual) table containing the cached information obtained by means of receiving CDP messages.
Syntax: SEQUENCE OF CdpCacheEntry
Max-Access: Not-accessible
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
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
Specifies a unique value for each device from which CDP messages are being received.
Syntax: Integer32
Max-Access: Not-accessible
Provides an indication of the type of address contained in the corresponding instance of cdpCacheAddress.
Syntax: CiscoNetworkProtocol
Max-Access: Read-only
Specifies the (first) network-layer address of the device's SNMP-agent as reported in the most recent CDP message. For example, if the corresponding instance of cacheAddressType had the value ip(1), then this object would be an IP-address.
Syntax: CiscoNetworkAddress
Max-Access: Read-only
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
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
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
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
Specifies the device's functional capabilities as reported in the most recent CDP message. For the 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
The variables described in this section provide the necessary information for the definition and management of DSPU objects.
Specifies whether the RSRB feature is enabled for the DSPU node.
Syntax: TruthValue
Max-Access: Read-only
Specifies local virtual ring number used by DSPU node. LocalVirtualRing is zero if RSRB is not enabled.
Syntax: Integer (0-4096)
Max-Access: Read-only
Specifies the bridge number connecting the DSPU LocalVirtualRing with the RSRB TargetVirtualRing. Currently, the only valid bridge number supported is 1. The bridge number must be 1 if RSRB is enabled. The bridge number is zero if RSRB is not enabled.
Syntax: Integer (0-15)
Max-Access: Read-only
Specifies the target virtual ring number used for RSRB. TargetVirtualRing is zero if RSRB not enabled.
Syntax: Integer (0-4096)
Max-Access: Read-only
Specifies the virtual media access control (MAC) address of the DSPU node. VirtualMacAddress is zero if RSRB is not enabled
Syntax: MacAddress
Max-Access: Read-only
Specifies if the default PU feature is enabled for the DSPU node. The default value is disabled (2).
Syntax: TruthValue
Max-Access: Read-only
Specifies the send/receive window size to be used across the link between the default PU and a remote PU.
Syntax: Integer (1-127)
Max-Access: Read-only
Specifies the maximum size of an I-frame that can be transmitted/received across the link between the default PU and a remote PU.
Syntax: Integer (64-18432)
Max-Access: Read-only
Specifies the value of the activation pacing window. The pacing window is used by the DSPU node to limit the number of activation RUs sent for a given SAP before waiting for responses from the remote.
Syntax: Integer (1-65535)
Max-Access: Read-only
Specifies the last change to DSPU configuration parameters. LastConfigChgTime reflects any change in DSPU configuration.
Syntax: TimeStamp
Max-Access: Read-only
Specifies a table listing defined pool classes for the DSPU node. A pool class is defined at the DSPU node as a pool of upstream LUs that can be shared among downstream PUs.
Each entry in the table represents a separate pool class definition.
Syntax: SEQUENCE OF DspuPoolClassEntry
Max-Access: Not-accessible
Each entry represents a defined pool class.
Syntax: DspuPoolClassEntry
Max-Access: Not-accessible
Specifies the index of pool class entry defined in the dpsuPoolClassTable.
Syntax: Integer32 (0-2147483647)
Max-Access: Not-accessible
Specifies the name identifier of the pool class.
Syntax: DisplayString (SIZE (0-10))
Max-Access: Read-only
dspuPoolClassInactivityTimeout
Specifies the value (in minutes) of the inactivity timeout that will be applied to active LU sessions assigned from the pool class. The inactivity timeout feature for pooled LUs is disabled if the Inactivity Timeout value is zero.
Syntax: Integer (0-255)
Max-Access: Read-only
dspuPoolClassOperUpStreamLuDefs
Specifies the number of upstream LUs defined in the pool class.
Syntax: Integer32
Max-Access: Read-only
dspuPoolClassOperDnStreamLuDefs
Specifies the number of downstream LUs defined in the pool class.
Syntax: Integer32
Max-Access: Read-only
End of Table
Table listing all LUs defined in a specified pool class.
The entries in the table provide information such that the downstream LUs in the pool can be correlated with the upstream LUs to which they might be assigned and vice versa.
If all upstream LUs have been assigned, downstream LUs might be waiting for assignment.
If there are no downstream LUs waiting for assignment, upstream LUs might be unassigned.
Syntax: SEQUENCE OF DspuPooledLuEntry
Max-Access: Not-accessible
Each entry represents an LU that is defined as a member of the specified pool class.
Syntax: DspuPooledLuEntry
Max-Access: Not-accessible
Specifies the index (dspuPuOperIndex) of the peer PU that owns the peer LU. The PeerPuIndex is zero if the peer LU has not been assigned.
Syntax: Integer32
Max-Access: Read-only
dspuPooledLuPeerLuLocalAddress
Specifies the NAU address (dspuLuOperLuLocalAddress) of the peer LU. The PeerLuLocalAddress is zero if peer LU has not been assigned.
Syntax: Integer (0-254)
Max-Access: Read-only
End of Table
Table listing all defined upstream or downstream PUs that are owned by the DSPU node.
Syntax: SEQUENCE OF DspuPuAdminEntry
Max-Access: Not-accessible
Each entry represents a defined upstream or downstream PU.
Syntax: DspuPuAdminEntry
Max-Access: Not-accessible
Specifies the index of a PU in the dspuPuAdminTable.
Syntax: Integer32 (0-2147483647)
Max-Access: Not-accessible
Specifies the name of the upstream or downstream PU.
Syntax: DisplayString (SIZE (0-8))
Max-Access: Read-only
Specifies PU type as either upstream or downstream.
Syntax: Integer 1 = upstreamPu, 2 = dnstreamPu
Max-Access: Read-only
Specifies the media access control (MAC) address of the remote PU.
Syntax: MacAddress
Max-Access: Read-only
Specifies the SAP address of the remote PU.
Syntax: Integer (1-254)
Max-Access: Read-only
Specifies the SAP address of the local PU. The default value of the local SAP address is 8.
Syntax: Integer (1-254)
Max-Access: Read-only
For upstream PUs, specifies the XID that will be sent to the remote PU. For downstream PUs, specifies the XID that must be received from the remote PU.
Syntax: Integer32
Max-Access: Read-only
Specifies the type of XID format used during activation of the link between this dspuNode and the remote PU.
Syntax: Integer 1 = formatUnknown, 2 = format0, 3 = format3
Max-Access: Read-only
Specifies the send/receive window size to be used across the link between this dspuNode and the remote PU.
Syntax: Integer (1-127)
Max-Access: Read-only
Specifies the maximum size of an I-frame that can be transmitted/received across the link between this dspuNode and the remote PU.
Syntax: Integer (64-18432)
Max-Access: Read-only
Specifies the number of times that the DSPU node will attempt to activate the link between the dspuNode and the remote PU.
Syntax: Integer (0-255)
Max-Access: Read-only
Specifies the value (in seconds) for the delay between link activation attempts between the dspuNode and the remote PU.
Syntax: Integer (1-600)
Max-Access: Read-only
Specifies whether the dspuNode should attempt link activation with the remote PU.
Syntax: TruthValue
Max-Access: Read-only
Specifies the DLC type used by the dspuNode for link activation with the remote PU.
Syntax: Integer 1 = undefined, 2 = sdlc, 5 = Ethernet, 6 = tokenRing, 8 = rsrb, 9 = Framerelay, 10 = FDDI
Max-Access: Read-only
Specifies the DLC unit used by the dspuNode for link activation with the remote PU.
Syntax: Integer (0-255)
Max-Access: Read-only
Specifies the DLC port used by the dspuNode for link activation with the remote PU.
Syntax: Integer (0-255)
Max-Access: Read-only
Specifies whether the PU serves as a focal point for alert notification forwarding. Only an upstream PU can be defined as a focal point. Downstream PUs can never be defined as a focal point. The DSPU node can define only one upstream PU as a focal point PU.
Syntax: TruthValue
Max-Access: Read-only
Specifies the status of a row entry in the dspuPuAdminTable.
Syntax: RowStatus
Max-Access: Read-only
Specifies the poll address, data-link connection identifier (DLCI), or subscriber address associated with the remote PU.
Syntax: DisplayString (SIZE (0-20))
Max-Access: Read-only
End of Table
Table listing all active upstream or downstream PUs that are owned by the DSPU node (including default PUs).
Syntax: SEQUENCE OF DspuPuOperEntry
Max-Access: Not-accessible
Each entry represents an active upstream or downstream PU.
Syntax: DspuPuOperEntry
Max-Access: Not-accessible
Specifies the index of a PU entry in the dspuPUOperTable.
Syntax: Integer32 (0-2147483647)
Max-Access: Read-only
Specifies the name of the PU.
Syntax: DisplayString (SIZE (0-8))
Max-Access: Read-only
Specifies the PU type as either upstream or downstream.
Syntax: Integer 1 = upstreamPu, 2 = dnstreamPu
Max-Access: Read-only
Specifies the media access control (MAC) address of the remote PU.
Syntax: MacAddress
Max-Access: Read-only
Specifies the SAP address of the remote PU.
Syntax: Integer (0-254)
Max-Access: Read-only
Specifies the SAP address of the local PU used by the dspuNode.
Syntax: Integer (1-254)
Max-Access: Read-only
For upstream PUs, specifies the XID that was sent to the remote PU. For downstream PUs, specifies the XID that was received from the remote PU.
Syntax: Integer32
Max-Access: Read-only
Specifies the type of XID format used during activation of the link between this dspuNode and the remote PU.
Syntax: Integer 1 = formatUnknown, 2 = format0, 3 = format3
Max-Access: Read-only
Specifies the send/receive window size used across the link between this dspuNode and the remote PU.
Syntax: Integer (1-127)
Max-Access: Read-only
Specifies the maximum size of an I-frame that can be transmitted/received across the link between this dspuNode and the remote PU.
Syntax: Integer (64-18432)
Max-Access: Read-only
Specifies the number of times that the DSPU node will attempt to activate the link between the dspuNode and the remote PU.
Syntax: Integer (0-255)
Max-Access: Read-only
Specifies the value (in seconds) for the delay between link activation attempts between the dspuNode and the remote PU.
Syntax: Integer (1-600)
Max-Access: Read-only
Specifies whether the dspuNode should attempt link activation with the remote PU.
Syntax: TruthValue
Max-Access: Read-only
Specifies the DLC type used by the dspuNode for link activation with the remote PU.
Syntax: Integer 1 = undefined, 2 = sdlc, 5 = Ethernet, 6 = tokenRing, 8 = rsrb, 9 = Framerelay, 10 = FDDI
Max-Access: Read-only
Specifies the DLC unit used by the dspuNode for link activation with the remote PU.
Syntax: Integer (0-255)
Max-Access: Read-only
Specifies the DLC port used by the dspuNode for link activation with the remote PU.
Syntax: Integer (0-255)
Max-Access: Read-only
Specifies if the PU serves as a focal point for alert notification forwarding. Only an upstream PU can be defined as a focal point. Downstream PUs can never be defined as a focal point. The DSPU node may define only one upstream PU as a focal point PU.
Syntax: TruthValue
Max-Access: Read-only
Specifies the operational state of the PU as either active or inactive.
Syntax: Integer 1 = active, 2 = inactive
Max-Access: Read-only
Specifies the current FSM state of the PU.
Syntax: Integer
The defined FSM state values are defined as follows:
| 1 = linkReset | Link is in reset state--not connected |
| 2 = linkPendConnOut | Pending ConnectOut to establish link |
| 3 = linkPendConnIn | Pending ConnectIn to establish link |
| 4 = linkPendXid | Pending XID negotiation on the link |
| 5 = linkXidNeg | XID negotiation proceeding on link |
| 6 = linkConnOut | ConnectOut link activation |
| 7 = linkConnIn | ConnectIn link activation |
| 8 = linkConnected | Link connected; PU inactive |
| 9 = puPendAct | Link connected; PU pending activation |
| 10 = puActive | Link connected; PU active |
| 11 = puBusy | Link connected; PU busy |
| 12 = puPendInact | Link connected; PU pending deactivation |
| 13 = linkPendDisc | Pending disconnect of link |
| 14 = linkPendClose | Pending close of link station |
Max-Access: Read-only
Specifies the timestamp of PU activation--when a positive ACTPU response is received.
Syntax: TimeStamp
Max-Access: Read-only
Specifies the TimeStamp of the last PU state change between active and inactive.
Syntax: TimeStamp
Max-Access: Read-only
Specifies the poll address, data-link connection identifier (DLCI), or subscriber address associated with the remote PU.
Syntax: DisplayString (SIZE 0-20))
Max-Access: Read-only
End of Table
Table listing the statistics recorded for each PU.
Syntax: SEQUENCE OF DspuPuStatsEntry
Max-Access: Not-accessible
Each entry represents an active upstream or downstream PU and has a corresponding entry in the dspuOperPuTable.
Syntax: DspuPuStatsEntry
Max-Access: Not-accessible
Specifies the number of bytes sent by this PU.
Syntax: Counter32
Access: Read-only
Specifies the number of bytes received by this PU.
Syntax: Counter32
Max-Access: Read-only
Specifies the number of frames sent by this PU.
Syntax: Counter32
Max-Access: Read-only
Specifies the number of frames received by this PU.
Syntax: Counter32
Max-Access: Read-only
Specifies the number of negative responses sent by this PU.
Syntax: Counter32
Max-Access: Read-only
Specifies the number of negative responses received by this PU.
Syntax: Counter32
Max-Access: Read-only
Specifies the number of active LUs on this PU (an LU becomes active when a positive ACTLU response is received).
Syntax: Counter32
Max-Access: Read-only
Specifies the number of inactive LUs on this PU (an LU is inactive until an ACTLU request or a positive ACLTU response is received).
Syntax: Counter32
Max-Access: Read-only
Specifies the number of LUs on this PU which are active-in-session (an LU is active-in-session when a BIND request is received).
Syntax: Counter32
Max-Access: Read-only
Specifies the number of activation failures for this PU.
Syntax: Counter32
Max-Access: Read-only
dspuPuStatsLastActivationFailureReason
Specifies the reason for last activation failure of this PU.
Integer
| 1 = noError | No PU activation failure has been detected. |
| 2 = otherError | Undefined error detected during PU activation. |
| 3 = internalError | Internal resources error detected during PU activation. |
| 4 = configuration error | PU could not be activated. |
| 5 = puNegativeResponse | Negative ACTPU response received from remote PU. |
| 6 = puAlreadyActive | PU is already active. |
Max-Access: Read-only
End of Table
Table listing all LUs owned by the PU.
Syntax: SEQUENCE OF DspuLuAdminEntry
Max-Access: Not-accessible
Each entry represents a defined LU owned by the PU.
Syntax: DspuLuAdminEntry
Max-Access: Not-accessible
Specifies the network addressable unit (NAU) address of the local LU.
Syntax: Integer (1-254)
Max-Access: Not-accessible
Specifies whether the LU is pooled or dedicated.
Syntax: Integer 1 = pooled, 2 = dedicated
Max-Access: Read-only
Specifies the pool class to which the LU is defined as a member. The dspuLuAdminPoolClassName is valid for pooled LUs only.
Syntax: DisplayString (SIZE (0-10))
Max-Access: Read-only
For downstream LUs, the PeerPuIndex identifies the upstream PU that owns the upstream LU to which this downstream LU is assigned.
For upstream LUs, the PeerPuIndex identifies the downstream PU that owns the downstream LU to which this upstream LU is assigned.
The PeerPuIndex is valid for dedicated LUs only; otherwise, the PeerPuIndex is zero.
Syntax: Integer32
Max-Access: Read-only
For downstream LUs, the PeerLuLocalAddress identifies the NAU address of the upstream LU to which this downstream LU is assigned. For upstream LUs, the PeerLuLocalAddress identifies the NAU address of the downstream LU to which this upstream LU is assigned. The dspuLuAdminPeerLuLocalAddress is valid for dedicated LUs only; otherwise, the PeerLuLocalAddress is zero.
Syntax: Integer (1-254)
Max-Access: Read-only
Specifies the status of a row entry in the dspuLuAdminTable.
Syntax: RowStatus
Max-Access: Read-only
End of Table
Table listing all LUs owned by the PU.
Syntax: SEQUENCE OF DspuLuOperEntry
Max-Access: Not-accessible
Each entry represents a defined LU owned by the PU.
Syntax: DspuLuOperEntry
Max-Access: Not-accessible
Specifies the NAU address of the local LU.
Syntax: Integer (1-254)
Max-Access: Read-only
Specifies whether the LU is pooled or dedicated.
Syntax: Integer 1 = pooled, 2 = dedicated
Max-Access: Read-only
Specifies the pool class of which the LU is a member. The dspuLuOperPoolClassName is valid for pooled LUs only.
Syntax: DisplayString (SIZE (0-10))
Max-Access: Read-only
For downstream LUs, the PeerPuIndex identifies the upstream PU that owns the upstream LU to which this downstream LU is assigned.
For upstream LUs, the PeerPuIndex identifies the downstream PU that owns the downstream LU to which this upstream LU is assigned.
If the PeerPuIndex is zero, the LU is a pooled LU and has not been assigned a peer LU from the pool.
Syntax: Integer32
Max-Access: Read-only
For downstream LUs, the PeerLuLocalAddress identifies the NAU address of the upstream LU to which this downstream LU is assigned.
For upstream LUs, the PeerLuLocalAddress identifies the NAU address of the downstream LU to which this upstream LU is assigned. If the PeerLuLocalAddress is zero, the LU is a pooled LU and has not been assigned a peer LU from the pool.
Syntax: Integer (1-254)
Max-Access: Read-only
Specifies the operational state of the LU as either active or inactive.
Syntax: Integer 1 = active, 2 = inactive
Max-Access: Read-only
Specifies the current FSM state of the LU.
Integer
| 1 = reset | Neither dnLu nor upLu is active. |
| 2 = dnLuStarted | dnLu is active; upLu is inactive. |
| 3 = upLuActive | upLu is active; dnLu is inactive. |
| 4 = dnLuPendAct | dnLu is awating activation; upLu is active and unavailable. |
| 5 = dnLuActUnav | dnLu is active and unavailable; upLu is active and available. |
| 6 = upLuPendAvail | upLu is awating availablility. |
| 7 = bothAvail | Both upLu and dnLu are active and available. |
| 8 = dnLuPendInact | dnLu is awating inactivation. |
| 9 = upLuPendInact | upLu is awating inactivation. |
| 10 = luInactivityTimeout | Inactivity Timeout occurred on a LU-to-LU session. |
| 11 = dnInactivityPendInact | dnLu is awating inactivation from an inactivity timeout. |
Max-Access: Read-only
Specifies the operational state of the LU session as either bound or unbound.
Syntax: Integer 1 = bound, 2 = unbound
Max-Access: Read-only
dspuLuOperLastActivationFailureReason
Specifies the reason for the last activation failure of this PU.
Integer
| 1 = noError | No LU activation failure has been detected. |
| 2 = otherError | An undefined error was detected during LU activation. |
| 3 = luNegativeResponse | A negative ACTLU (activate logical unit) response was received from the remote LU. |
Max-Access: Read-only
End of Table
Table listing the SAPs that are enabled for the DSPU node.
Syntax: SEQUENCE of DspuSapEntry
Max-Access: Not-accessible
Each entry represents an enabled SAP for the DSPU node.
Syntax: DspuSapEntry
Max-Access: Not-accessible
Specifies the SAP address of the local SAP.
Syntax: Integer (1-254)
Max-Access: Not-accessible
Specifies the local SAP type as either an upstreamSap or a downstreamSap.
Syntax: Integer 1 = upstreamSap, 2 = dnstreamSap
Max-Access: Read-only
Specifies the DLC type of the adapter that owns the local SAP.
Syntax: Integer 1 = undefined, 2 = sdlc, 5 = Ethernet, 6 = tokenring, 8 = rsrb, 9 = Framerelay, 10 = FDDI
Max-Access: Read-only
Specifies the DLC unit of the adapter that owns the local SAP.
Syntax: Integer (0-255)
Max-Access: Read-only
Specifies the DLC port of the adapter that owns the local SAP.
Syntax: Integer (0-255)
Max-Access: Read-only
Specifies the operational state of the local SAP as follows:
Syntax: Integer 1 = sapClosed, 2 = sapOpening, 3 = sapOpened, 4 = sapClosed
Max-Access: Read-only
Specifies the status of a row entry in the dspuSapTable.
Syntax: RowStatus
Max-Access: Read-only
End of Table
This notification indicates when the operational state of the LU changes between active and inactive. The following information is returned:
This notification is generated whenever an LU activation failure is detected. The following information is returned:
The environmental monitor card is provided only with the Cisco AGS+ router. This card checks input air temperature and air flow through the system card cage and card cage backplane power supplies. It also provides nonvolatile and system bus memory for the system. The Cisco 7000 and Cisco 7010 have built-in environmental monitoring functionality, and so do not use the card. The Cisco 7000 and Cisco 7010 routers provide environmental monitoring, reporting, and if necessary, system shutdown.
The Cisco AGS+ router is not supported in Cisco IOS Release 11.1. The variables listed in this section apply to the Cisco 7000 or Cisco 7010 router, or both.
The following MIB module describes the status of the Environmental Monitor on those devices that support one.
Specifies the type of environmental monitor located in the chassis. An oldAgs environmental monitor card is identical to an ags environmental card except that it is not capable of supplying data, and hence no instance of the remaining objects in this MIB will be returned in response to an SNMP query. Note that only a firmware upgrade is required to convert an oldAgs into an ags card.
Syntax: Integer, 1 = oldAgs, 2 = ags, 3 = c7000
Max-Access: Read-only
Specifies the table of voltage status maintained by the environmental monitor.
Syntax: SEQUENCE OF CiscoEnvMonVoltageStatusEntry
Max-Access: Not-accessible
An entry in the voltage status table, representing the status of the associated testpoint maintained by the environmental monitor.
Syntax: CiscoEnvMonVoltageStatusEntry
Max-Access: Not-accessible
Specifies a unique index for the testpoint being instrumented. This index is for SNMP purposes only and has no intrinsic meaning.
Syntax: Integer32
Max-Access: Not-accessible
Provides a textual description of the testpoint being instrumented. This description is a short textual label, suitable as a human-sensible identification for the rest of the information in the entry.
Syntax: DisplayString
Max-Access: Read-only
Specifies the current measurement in millivolts of the testpoint being instrumented.
Syntax: CiscoSignedGauge
Max-Access: Read-only
ciscoEnvMonVoltageThresholdLow
Specifies the lowest value in millivolts that the associated instance of the object ciscoEnvMonVoltageStatusValue can obtain before an emergency shutdown of the managed device is initiated.
Syntax: Integer32
Max-Access: Read-only
ciscoEnvMonVoltageThresholdHigh
The highest value in millivolts that the associated instance of the object ciscoEnvMonVoltageStatusValue can obtain before an emergency shutdown of the managed device is initiated.
Syntax: Integer32
Max-Access: Read-only
ciscoEnvMonVoltageLastShutdown
The value in millivolts of the associated instance of the object ciscoEnvMonVoltageStatusValue at the time an emergency shutdown of the managed device was last initiated. This value is stored in nonvolatile RAM and hence is able to survive the shutdown.
Syntax: Integer32
Max-Access: Read-only
Specifies the current state of the testpoint being instrumented.
Syntax: CiscoEnvMonState
Max-Access: Read-only
End of Table
Specifies the table of ambient temperature status maintained by the environmental monitor.
Syntax: SEQUENCE OF CiscoEnvMonTemperatureStatusEntry
Max-Access: Not-accessible
ciscoEnvMonTemperatureStatusEntry
An entry in the ambient temperature status table, representing the status of the associated testpoint maintained by the environmental monitor.
Syntax: CiscoEnvMonTemperatureStatusEntry
Max-Access: Not-accessible
ciscoEnvMonTemperatureStatusIndex
Specifies the unique index for the testpoint being instrumented. This index is for SNMP purposes only and has no intrinsic meaning.
Syntax: Integer32
Max-Access: Not-accessible
ciscoEnvMonTemperatureStatusDescr
Specifies the textual description of the testpoint being instrumented. This description is a short textual label, suitable as a human-sensible identification for the rest of the information in the entry.
Syntax: DisplayString
Max-Access: Read-only
ciscoEnvMonTemperatureStatusValue
Specifies the current measurement in degrees Celsius of the testpoint being instrumented.
Syntax: Gauge32
Max-Access: Read-only
ciscoEnvMonTemperatureThreshold
Specifies the highest value in degrees Celsius that the associated instance of the object ciscoEnvMonTemperatureStatusValue can obtain before an emergency shutdown of the managed device is initiated.
Syntax: Integer32
Max-Access: Read-only
ciscoEnvMonTemperatureLastShutdown
Specifies the value in degrees Celsius of the associated instance of the object ciscoEnvMonTemperatureStatusValue at the time an emergency shutdown of the managed device was last initiated. This value is stored in nonvolatile RAM and hence is able to survive the shutdown.
Syntax: Integer32
Max-Access: Read-only
Specifies the current state of the testpoint being instrumented.
Syntax: CiscoEnvMonState
Max-Access: Read-only
End of Table
Provides the fan status maintained by the environmental monitor.
Syntax: SEQUENCE OF CiscoEnvMonFanStatusEntry
Max-Access: Not-accessible
Specifies an entry in the fan status table, representing the status of the associated fan maintained by the environmental monitor.
Syntax: CiscoEnvMonFanStatusEntry
Max-Access: Not-accessible
Specifies a unique index for the fan being instrumented. This index is for SNMP purposes only and has no intrinsic meaning.
Syntax: Integer32
Max-Access: Not-accessible
Provides a textual description of the fan being instrumented. This description is a short textual label, suitable as a human-sensible identification for the rest of the information in the entry.
Syntax: DisplayString
Max-Access: Read-only
Specifies the current state of the fan being instrumented.
Syntax: CiscoEnvMonState
Max-Access: Read-only
End of Table
Specifies the table of power supply status maintained by the environmental monitor card.
Syntax: SEQUENCE OF CiscoEnvMonSupplyStatusEntry
Max-Access: Not-accessible
Specifies an entry in the power supply status table, representing the status of the associated power supply maintained by the environmental monitor card.
Syntax: CiscoEnvMonSupplyStatusEntry
Max-Access: Not-accessible
Specifies a unique index for the power supply being instrumented. This index is for SNMP purposes only and has no intrinsic meaning.
Syntax: Integer32
Max-Access: Not-accessible
Provides a textual description of the power supply being instrumented. This description is a short textual label, suitable as a human-sensible identification for the rest of the information in the entry.
Syntax: DisplayString
Max-Access: Read-only
Specifies the current state of the power supply being instrumented.
Syntax: CiscoEnvMonState
Max-Access: Read-only
End of Table
The following object identifiers are used to define SNMPv2 notifications that are backward compatible with SNMPv1 notifications, along with their associated notification enables:
ciscoEnvMonEnableShutdownNotification
This variable indicates whether the system produces the ciscoEnvMonShutdownNotification.
Syntax: TruthValue
Max-Access: Read-write
ciscoEnvMonEnableVoltageNotification
Specifies whether the system produces the ciscoEnvMonVoltageNotification. A false value will prevent voltage notifications from being generated by this system.
Syntax: TruthValue
Max-Access: Read-write
ciscoEnvMonEnableTemperatureNotification
Specifies whether the system produces the ciscoEnvMonTemperatureNotification. A false value will prevent temperature notifications from being generated by this system.
Syntax: TruthValue
Max-Access: Read-write
ciscoEnvMonEnableFanNotification
Specifies whether the system produces the ciscoEnvMonFanNotification. A false value will prevent fan notifications from being generated by this system.
Syntax: TruthValue
Max-Access: Read-write
ciscoEnvMonEnableRedundantSupplyNotification
Specifies whether the system produces the ciscoEnvMonRedundantSupplyNotification. A false value will prevent redundant supply notifications from being generated by this system.
Syntax: TruthValue
Max-Access: Read-write
ciscoEnvMonShutdownNotification
A ciscoEnvMonShutdownnotification is sent if the environmental monitor detects a testpoint reaching a critical state and is about to initiate a shutdown. This notification contains no objects so that it can be encoded and sent in the shortest amount of time possible. Even so, management applications should not rely on receiving such a notification because it might not be sent before the shutdown completes.
ciscoEnvMonVoltageNotification
A ciscoEnvMonVoltageNotification is sent if the voltage measured at a given testpoint is outside the normal range for the testpoint. (In other words, is at the warning, critical, or shutdown stage.) Because such a notification is usually generated before the shutdown state is reached, it can convey more data and has a better chance of being sent than does the ciscoEnvMonShutdownNotification. The ciscoEnvMonVoltage includes the following variable bindings (varBinds): ciscoEnvMonVoltageStatusDescr, ciscoEnvMonVoltageStatusValue, and ciscoEnvMonVoltageState. (The varBinds comprise the data of an SNMP v.1 protocol data unit (PDU). Each varBind associates a particular variable with its current value--with the exception of get and get-next requests, for which the value is ignored).
ciscoEnvMonTemperatureNotification
A ciscoEnvMonTemperatureNotification is sent if the temperature measured at a given testpoint is outside the normal range for the testpoint (in other words, the testpoint is at the warning, critical, or shutdown stage). Because such a notification is usually generated before the shutdown state is reached, it can convey more data and has a better chance of being sent than does the ciscoEnvMonShutdownNotification. The ciscoEnvMonTemperatureNotification includes the following varBinds: ciscoEnvMonTemperatureStatusDescr, ciscoEnvMonTemperatureStatusValue, and ciscoEnvMonTemperatureState.
A ciscoEnvMonFanNotification is sent if any fan in the fan arrays fails. Because such a trap is usually generated before the shutdown state is reached, it can convey more data and has a better chance of being sent than does the ciscoEnvMonShutdownNotification. The ciscoEnvMonFanNotification includes the following varBinds: ciscoEnvMonFanStatusDescr, and ciscoEnvMonFanState.
ciscoEnvMonRedundantSupplyNotification
A ciscoEnvMonRedundantSupplyNotification is sent if the redundant power supply (where extant) fails. Because such a notification is usually generated before the shutdown state is reached, it can convey more data and has a better chance of being sent than does the ciscoEnvMonShutdownNotification. The ciscoEnvMonRedundantSupplyNotification has the following varBinds included: ciscoEnvMonSupplyStatusDescr, and ciscoEnvMonSupplyState.
The variables described in this section apply to the Cisco Flash MIB definitions.
Specifies the number of Flash devices supported by the system. If the system does not support any Flash devices, this MIB is not loaded on that system. The value of this object is therefore at least 1.
Syntax: Integer32 (1-32)
Max-Access: Read-only
Specifies the table of Flash device properties for each initialized Flash device. Each Flash device installed in a system is detected, sized, and initialized when the system image boots up. For removable Flash devices, the device properties are dynamically deleted and recreated as the device is removed and inserted. In this case, the newly inserted device may not be the same as the one that was removed earlier.
The ciscoFlashDeviceInitTime object is available for a management station to determine the time at which a device was initialized, and thereby detect the change of a removable device. A removable device that has not been installed will also have an entry in this table. This entry notifies a management station of a removable device that has been removed.
Because a removed device obviously cannot be sized and initialized, the table entry for such a device will have ciscoFlashDeviceSize, ciscoFlashDeviceMinPartitionSize, ciscoFlashDeviceMaxPartitions, ciscoFlashDevicePartitions, and ciscoFlashDeviceChipCount equal to zero. ciscoFlashDeviceRemovable will be true to indicate it is removable.
Syntax: SEQUENCE OF CiscoFlashDeviceEntry
Max-Access: Not-accessible
Specifies an entry in the table of Flash device properties for each initialized Flash device. Each entry can be randomly accessed by using ciscoFlashDeviceIndex as an index into the table. Note that removable devices have an entry in the table even when they are removed. However, a non-removable device that is not installed does not have an entry in the table.
Syntax: CiscoFlashDeviceEntry
Max-Access: Not-accessible
Specifies the Flash device sequence number to index within the table of initialized Flash devices. The lowest value should be 1. The highest should be less than or equal to the value of the ciscoFlashDevicesSupported object.
Syntax: Integer32 (1-32)
Max-Access: Not-accessible
Specifies the total size in bytes of the Flash device. For a removable device, the size will be zero if the device has been removed.
Syntax: Integer32
Max-Access: Read-only
ciscoFlashDeviceMinPartitionSize
Specifies that this object will give the minimum partition size supported for this device. For systems that execute code directly out of Flash, the minimum partition size needs to be the bank size. (Bank size is equal to the size of a chip multiplied by the width of the device. In most cases, the device width is 4 bytes, and so the bank size would be four times the size of a chip). This has to be so because all programming commands affect the operation of an entire chip (in the case of Cisco chips, an entire bank is affected because all operations are done on the entire width of the device) even though the actual command may be localized to a small portion of each chip. So when executing code out of Flash, one needs to be able to write and erase some portion of Flash without affecting the code execution.
For systems that execute code out of DRAM or ROM, it is possible to partition Flash with a finer granularity (for example, at erase sector boundaries) if the system code supports such granularity.
This object will let a management entity know the minimum partition size as defined by the system. If the system does not support partitioning, the value in bytes will be equal to the device size in ciscoFlashDeviceSize. The maximum number of partitions that can be configured will be equal to the minimum number of ciscoFlashDeviceMaxPartitions and the quotient that is derived when ciscoFlashDeviceSize is divided by ciscoFlashDeviceMinPartitionSize.
Syntax: Integer32
Max-Access: Read-only
Specifies the maximum number of partitions supported by the system for this Flash memory device. The default is 1, which actually means that partitioning is not supported. Note that this value will be defined by system limitations, not by the Flash memory device itself (for example, the system may impose a limit of two partitions even though the device may be large enough to be partitioned into four based on the smallest partition unit supported). On systems that execute code out of Flash memory, partitioning is a way of creating multiple file systems in the Flash memory device so that writing into or erasing of one file system can be done while executing code residing in another file system. For systems executing code out of dynamic RAM (DRAM), partitioning gives a way of subdividing a large Flash memory device for easier management of files.
Syntax: Integer32 (1-8)
Max-Access: Read-only
Specifies the Flash device partitions that are actually present. The number of partitions cannot exceed the minimum number of ciscoFlashDeviceMaxPartitions and the quotient that is derived when ciscoFlashDeviceSize is divided by ciscoFlashDeviceMinPartitionSize.
The number of partitions will be equal to at least 1 when the partition spans the entire device (actually no partitioning). A partition in turn will contain one or more minimum partition units where a minimum partition unit is defined by ciscoFlashDeviceMinPartitionSize.
Syntax: Integer32
Max-Access: Read-only
Specifies the total number of chips within the Flash device. The purpose of this object is to provide a management station with information on how much chip information to expect. In addition, this object can help double-check the chip index against an upper limit when randomly retrieving chip information for a partition.
Syntax: Integer32 (1-64)
Max-Access: Read-only
Specifies the name of the Flash device. This name refers to the device within the system. Flash operations get directed to a device based on this name. The system has a concept of a default device. This device would be the primary in case of multiple devices. The system directs an operation to the default device whenever a device name is not specified. The device name is therefore mandatory except when the operation is being done on the default device, or, the system supports only a single Flash device. The device name is always available for a removable device, even when the device has been removed.
Syntax: DisplayString (SIZE (0-16))
Max-Access: Read-only
Description of a Flash device. The description explains the Flash device and its purpose. Current values are
The ciscoFlashDeviceDescr, ciscoFlashDeviceController (if applicable), and ciscoFlashDeviceCard objects are expected to give collectively all information about a Flash device.
The device description will always be available for a removable device, even when the device has been removed.
Syntax: DisplayString (SIZE (0-64))
Max-Access: Read-only
Specifies the Flash device controller (in other words, the card that actually controls Flash read/write/erase). This object is relevant for AGS+ systems where Flash may be controlled by the MC+, STR or the Environmental Monitor cards--cards that may not actually contain the Flash chips.
For systems that have removable PCMCIA flash cards that are controlled by a PCMCIA controller chip, this object may contain a description of that controller chip.
Where irrelevant (in other words, when flash is a direct memory mapped device accessed directly by the main processor), this object has an empty (NULL) string.
Syntax: DisplayString (SIZE (0-64))
Max-Access: Read-only
Specifies an instance of a card entry in the cardTable. The card entry gives details about the card on which the Flash device is actually located. For most systems, this is usually the main processor board. On AGS+ systems, Flash is located on a separate multibus card such as the MC. This object will therefore be used essentially to index into cardTable to retrieve details about the card such as cardDescr, cardSlotNumber, and so forth.
Syntax: InstancePointer
Max-Access: Read-only
ciscoFlashDeviceProgrammingJumper
Specifies the state of a jumper (if present and can be determined) that controls the programming voltage called Vpp to the Flash device. Vpp is required for programming (erasing and writing) Flash. For certain older technology chips, it is also required for identifying the chips (which in turn is required to identify which programming algorithms to use; different chips require different algorithms and commands).
The purpose of the jumper, on systems where it is available, is to write protect a Flash device. On most of the newer remote access routers, this jumper is unavailable since users are not expected to visit remote sites just to install and remove the jumpers when upgrading software in the Flash device. The unknown value (3) will be returned for such systems and can be interpreted to mean that a programming jumper is not present or not required on those systems.
On systems where the programming jumper state can be read back by means of a hardware register, the installed(1) or notInstalled(2) value will be returned.
This object is expected to be used in conjunction with the ciscoFlashPartitionStatus object whenever that object has the readOnly(1) value. In such a case, this object will indicate whether the programming jumper is a possible reason for the readOnly state.
Syntax: Integer 1 = installed, 2 = notInstalled, 3 = unknown
Max-Access: Read-only
Specifies the system time at which the device was initialized. For fixed devices, this will be the system time at boot up. For removable devices, it will be the time at which the device was inserted, which may be boot up time, or a later time (if device was inserted later). If a device (fixed or removable) was repartitioned, it will be the time of repartitioning.
The purpose of this object is to help a management station determine whether a removable device has been changed. The application should retrieve this object prior to any operation and compare with the previously retrieved value. Note that this time will not be real time but a running time maintained by the system. This running time starts from zero when the system boots up. For a removable device that has been removed, this value will be zero.
Syntax: TimeStamp
Max-Access: Read-only
Specifies whether the Flash device is removable. Generally, only PCMCIA Flash cards will be treated as removable. Socketed Flash chips and Flash SIMM modules will not be treated as removable. Simply put, only those Flash devices that can be inserted or removed without opening the hardware casing will be considered removable. Further, removable Flash devices are expected to have the necessary hardware support including (1) on-line removal and insertion, and (2) interrupt generation on removal or insertion.
Syntax: TruthValue
Max-Access: Read-only
End of Table
Specifies the table of Flash memory device chip properties for each initialized Flash memory device. This table is intended primarily to support error diagnosis.
Syntax: SEQUENCE OF CiscoFlashChipEntry
Max-Access: Not-accessible
Specifies an entry in the table of chip information for each Flash device initialized in the system. An entry is indexed by two objects: 1) the device index and 2) the chip index within that device.
Syntax: CiscoFlashChipEntry
Max-Access: Not-accessible
Specifies the chip sequence number within selected Flash device. Used to index within chip info table. Value starts from 1 and should not be greater than ciscoFlashDeviceChipCount for that device.
When retrieving chip information for chips within a partition, the sequence number should lie between ciscoFlashPartitionStartChip & ciscoFlashPartitionEndChip (both inclusive).
Syntax: Integer32 (1-64)
Max-Access: Not-accessible
Specifies the manufacturer and device code for a chip. The lower byte will contain the device code.The upper byte will contain the manufacturer code. If a chip code is unknown because it could not be queried out of the chip, the value of this object will be 00:00.
Syntax: FlashChipCode
Max-Access: Read-only
Specifies the flash chip name corresponding to the chip code. The name will contain the manufacturer and the chip type. It will be of the form Intel 27F008SA.
In the case where a chip code is unknown, this object will be an empty (NULL) string. In the case where the chip code is known but the chip is not supported by the system, this object will be an empty (NULL) string.
A management station is therefore expected to use the chip code and the chip description in conjunction to provide additional information whenever the ciscoFlashPartitionStatus object has the readOnly(1) value.
Syntax: DisplayString (SIZE (0-32))
Max-Access: Read-only
Specifies a cumulative count (since last system boot up or initialization) of the number of write retries that were done in the chip. If no writes have been done to Flash, the count will be zero. Typically, a maximum of 25 retries are done on a single location before flagging a write error. A management station is expected to get this object for each chip in a partition after a write failure in that partition. To keep a track of retries for a given write operation, the management station would have to retrieve the values for the concerned chips before and after any write operation.
Syntax: Counter32
Max-Access: Read-only
Specifies a cumulative count (since last system boot up or initialization) of the number of erase retries that were done in the chip. Typically, a maximum of 2000 retries are done in a single erase zone (which may be a full chip or a portion, depending on the chip technology) before flagging an erase error.
A management station is expected to get this object for each chip in a partition after an erase failure in that partition. To keep a track of retries for a given erase operation, the management station would have to retrieve the values for the concerned chips before and after any erase operation.
Syntax: Counter32
Max-Access: Read-only
Specifies the maximum number of write retries done at any single location before declaring a write failure.
Syntax: Integer32
Max-Access: Read-only
Specifies the maximum number of erase retries done within an erase sector before declaring an erase failure.
Syntax: Integer32
Max-Access: Read-only
End of Table
A Flash partition is a logical sub-division of a Flash device and may or may not be equal to the entire device itself. When there is no explicit partitioning done, a single partition is assumed to exist, spanning the entire device.
Partitioning has the following restrictions:
This table specifies the Flash device partition properties for each initialized Flash partition. Whenever there is no explicit partitioning done, a single partition spanning the entire device will be assumed to exist. There will therefore always be at least one partition on a device.
Syntax: SEQUENCE OF CiscoFlashPartitionEntry
Max-Access: Not-accessible
Specifies an entry in the table of Flash partition properties for each initialized Flash partition. Each entry will be indexed by a device number and a partition number within the device.
Syntax: CiscoFlashPartitionEntry
Max-Access: Not-accessible
Specifies the Flash partition sequence number used to index within table of initialized Flash partitions.
Syntax: Integer32 (1-8)
Max-Access: Not-accessible
Specifies the chip sequence number of first chip in partition. Used as an index into the chip table.
Syntax: Integer32 (1-64)
Max-Access: Read-only
Specifies the chip sequence number of last chip in partition. Used as an index into the chip table.
Syntax: Integer32 (1-64)
Max-Access: Read-only
Specifies in bytes the Flash partition size. It should be an integral multiple of ciscoFlashDeviceMinPartitionSize. If there is a single partition, this size will be equal to ciscoFlashDeviceSize.
Syntax: Integer32
Max-Access: Read-only
Specifies in bytes the free space within a Flash partition.
Certain file systems may also have partition or device header overhead to be considered when computing the free space. Free space will be computed as total partition size minus size of all existing files (valid/invalid/deleted files and including file header of each file), size of any partition header, and size of header of next file to be copied in. In short, this object will give the size of the largest file that can be copied in. The management entity will not be expected to know or use any overheads such as file and partition header lengths, because such overheads may vary from file system to file system. Deleting files from Flash memory does not free up space in Flash memory. A partition must be erased or squeezed for space to be reclaimed by deleted files. Not all file systems support the squeeze operation.
Deleted files in Flash memory do not free up space. A partition has to be erased in order to reclaim the space occupied by files. (The irspFileSystem file system provides an alternate method, through the squeeze command, of reclaiming free space occupied by deleted files. However, support for this file system may not be available on all systems.)
Syntax: Gauge32
Max-Access: Read-only
ciscoFlashPartitionFileCount
Specifies the count of all files in a flash partition. Both good and bad (deleted or invalid checksum) files will be included in this count.
Syntax: Integer32
Max-Access: Read-only
ciscoFlashPartitionChecksumAlgorithm
Specifies the checksum algorithm identifier for checksum method used by the file system. Normally, this would be fixed for a particular file system. When a file system writes a file to Flash memory, it checksums the data written. The checksum then serves as a way to validate the data read back whenever the file is opened for reading.
Because there is no way, when using TFTP, to guarantee that a network download has been error-free (since UDP checksums may not have been enabled), this object together with the ciscoFlashFileChecksum object provides a method for any management station to regenerate the checksum of the original file on the server and compare checksums to ensure that the file download to Flash memory was error free.
simpleChecksum represents a simple 1s complement addition of short word values. Other algorithm values will be added as necessary.
Syntax: Integer, 1 = simpleChecksum, 2 = undefined, 3 = simpleCRC
Max-Access: Read-only
Specifies that Flash partition status can be one of the following:
Syntax: Integer 1 = ReadOnly, 2 = runFromFlash, 3 = readWrite
Max-Access: Read-only
ciscoFlashPartitionUpgradeMethod
Specifies the Flash partition upgrade method, In other words, specifies the method by which new files can be downloaded into the partition.
FLH stands for Flash Load Helper, a feature provided on run-from-Flash systems for upgrading Flash memory. This feature uses the bootstrap code in ROMs to help in automatic download.
This object should be retrieved if the partition status is runFromFlash (2). If the partition status is readOnly (1), the upgrade method would depend on the reason for the readOnly status. For example, it may simply be a matter of installing the programming jumper, or it may require execution of a version of software that supports the Flash chips.
| Partition Status | Meaning |
|---|---|
| 1 = unknown | The current system image does not know how Flash can be programmed. A possible method would be to reload the ROM image and perform the upgrade manually. |
| 2 = urxbootFLH | The Flash Load Helper is available to download files to Flash. A copy-to-flash command can be used and this system image will automatically reload the Rxboot image in ROM and direct it to carry out the download request. |
| 3 = udirect | Will be done directly by this image. |
Syntax: Integer
Max-Access: Read-only
Specifies the Flash partition name used to refer to a partition by the system. This can be any alpha-numeric character string of the form AAAAAAAAnn, where A represents an optional alpha character and n a numeric character.
Numeric characters must always form the trailing part of the string. The system will strip off the alpha characters and use the numeric portion to map to a partition index.
Flash operations get directed to a device partition based on this name. The system has a concept of a default partition. This would be the first partition in the device. The system directs an operation to the default partition whenever a partition name is not specified. The partition name is therefore mandatory except when the operation is being done on the default partition, or the device has just one partition (is not partitioned).
Syntax: DisplayString (SIZE (0-16))
Max-Access: Read-only
ciscoFlashPartitionNeedErasure
This object indicates whether a partition requires erasure before any write operations can be done in it.
A management station should therefore retrieve this object prior to attempting any write operation. A partition requires erasure after it becomes full (free space left is less than or equal to the file system file header size).
A partition also requires erasure if the system does not find the existence of any file system when it boots up.
The partition may be erased explicitly through the erase(5) command, or by using the copyToFlashWithErase(1) command. If a copyToFlashWithoutErase(2) command is issued when this object has the TRUE value, the command will fail.
Syntax: TruthValue
Max-Access: Read-only
ciscoFlashPartitionFileNameLength
Maximum file name length supported by the file system. Max file name length will depend on the file system implemented. Today, all file systems support a max length of at least 48 bytes. A management entity must use this object when prompting a user for, or deriving, the Flash file name length.
Syntax: Integer32 (1-256)
Max-Access: Read-only
End of Table
This table specifies the table of information for files in a Flash partition.
Syntax: SEQUENCE OF CiscoFlashFileEntry
Max-Access: Not-accessible
Specifies an entry in the table of Flash file properties for each initialized Flash partition. Each entry represents a file and gives details about the file. An entry is indexed using the device number, partition number within the device, and file number within the partition.
Syntax: CiscoFlashFileEntry
Max-Access: Not-accessible
Specifies the Flash file sequence number used to index within a Flash partition directory table.
Syntax: Integer32 (1-32)
Max-Access: Not-accessible
Specifies the size of the file in bytes. Note that this size does not include the size of the file system file header. File size will always be nonzero.
Syntax: Integer32
Max-Access: Read-only
Specifies a file checksum stored in the file header. This checksum is computed and stored when the file is written into Flash memory. It serves to validate the data written into Flash memory. Whereas the system will generate and store the checksum internally in hexadecimal form, this object will provide the checksum in a string form. The checksum will be available for all valid and invalid-checksum files.
Syntax: ChecksumString
Max-Access: Read-only
Specifies the status of a file. A file could be explicitly deleted if the file system supports such a user command facility. Alternately, an existing good file would be automatically deleted if another good file with the same name were copied in. Note that deleted files continue to occupy prime Flash real estate.
A file is marked as having an invalid checksum if any checksum mismatch was detected while writing or reading the file. Incomplete files (files truncated either because of lack of free space, or a network download failure) are also written with a bad checksum and marked as invalid.
Syntax: Integer, 1 = deleted, 2 = invalidChecksum, 3 = valid
Max-Access: Read-only
Specifies the Flash file name as specified by the user copying in the file. The name should not include the colon (:) character as it is a special separator character used to delineate the device name, partition name, and the file name.
Syntax: DisplayString (SIZE (1-255))
Max-Access: Read-only
End of Table
Flash operations are used for copying to or from Flash memory partitioning, and miscellaneous functions such as erasing and file verification.
This table specifies Flash copy operation entries. Each entry represents a Flash copy operation (to or from Flash) that has been initiated.
Syntax: SEQUENCE OF CiscoFlashCopyEntry
Max-Access: Not-accessible
Specifies a Flash copy operation entry. Each entry consists of a command, a source, and optional parameters such as protocol to be used, a destination, a server address, and so forth.
To create an entry, a management station first generates a pseudo-random serial number to be used as the index to this sparse table. The station then creates the associated instance of the row status object. It must also, either in the same or in successive PDUs, create the associated instance of the command and parameter objects. Then it should modify the default values for any of the parameter objects if the defaults are not appropriate.
Once the appropriate instances of all the command 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 operation. Note that this entire procedure may be initiated by means of a single set request which specifies a row status of createAndGo as well as specifies valid values for the non-defaulted parameter objects.
Once an operation has been activated, it cannot be stopped. Once the operation completes, the management station should retrieve the value of the status object (and time if desired), and delete the entry. In order to prevent old entries from clogging the table, entries will be aged out, but an entry will never be deleted within 5 minutes of completing.
Syntax: CiscoFlashCopyEntry
Max-Access: Not-accessible
Specifies a unique entry in the table. When initiating a copy operation a management station should use a pseudo-random value for this object when creating or modifying an instance of a ciscoFlashCopyEntry.
Syntax: Integer32
Max-Access: Not-accessible
Specifies the copy command to be executed. Mandatory. Note that it is possible for a system to support multiple file systems (different file systems on different Flash devices, or different file systems on different partitions within a device). Each such file system may support only a subset of these commands. If a command is unsupported, the invalidOperation (3) error will be reported in the operation status. Table 3-2 lists the copy commands and their parameters.
Syntax: Integer 1 = copyToFlashWithErase (copy {tftp|rcp} flash), 2 = copyToFlashWithoutErase (copy {tftp|rcp} flash), 3 = copyFromFlash (copy flash {tftp|rcp|lex}), 4 = copyFromFlhLog (copy flhlog tftp)
Max-Access: Read-create
| Command | Remarks |
|---|---|
| copyToFlashWithErase | Copy a file to Flash; erase Flash before copy. Use the TFTP or rcp protocol. Parameters include CopyProtocol, CopyServerAddress, CopySourceName, CopyDestinationName (optional), CopyRemoteUserName (optional), CopyNotifyOnCompletion (optional) |
| copyToFlashWithoutErase | Copy a file to Flash; do not erase. Note that this command will fail if the PartitionNeedErasure object specifies that the partition being copied to needs erasure. Use the TFTP or rcp protocol. Parameters include CopyProtocol, CopyServerAddress, CopySourceName, CopyDestinationName (optional), CopyRemoteUserName (optional), CopyNotifyOnCompletion (optional) |
| copyFromFlash | Copy a file from Flash using the TFTP, rcp or lex protocol. Note that the lex protocol can only be used to copy to a lex device. Parameters include CopyProtocol, CopySourceName, CopyDestinationName (optional), CopyRemoteUserName (optional), CopyNotifyOnCompletion (optional) |
| copyFromFlhLog | Copy contents of FLH log to server using TFTP protocol. Parameters include CopyProtocol, CopyServerAddress, CopyDestinationName, CopyNotifyOnCompletion (optional) |
Specifies the protocol to be used for any copy. Optional. Will default to tftp if not specified. Because feature support depends on a software release, version number within the release, platform, and maybe the image type (subset type), a management station would be expected to somehow determine the protocol support for a command.
Syntax: Integer 1 = tftp, 2 = rcp, 3 = lex
Max-Access: Read-create
Specifies the server address to be used for any copy. Optional. Will default to 'FFFFFFFF'H (or 255.255.255.255).
Syntax: IpAddress
Max-Access: Read-create
Specifies the source file name, either in Flash memory or on a server, depending on the type of copy command. Mandatory. For a copy from Flash memory, the file name must be of the form
[device:][partition:]file
where device is a value obtained from FlashDeviceName, partition is obtained from FlashPartitionName and file is the name of a file in Flash.
A management station could derive its own partition name as per the description for the ciscoFlashPartitionName object. If device is not specified, the default Flash device will be assumed.
If partition is not specified, the default partition will be assumed. If a device is not partitioned into two or more partitions, this value can be left out.
For a copy to Flash memory, the file name will assigned according to the file naming conventions and path to the file on the server.
Syntax: DisplayString (SIZE (1-255))
Max-Access: Read-create
Specifies the destination file name. For a copy to Flash memory, the file name must be of the form
[device:][partition:]file
where device is a value obtained from FlashDeviceName, partition is obtained from FlashPartitionName, and file is any character string that does not have embedded colon characters. A management station could derive its own partition name as per the description for the ciscoFlashPartitionName object.
If device is not specified, the default Flash device will be assumed. If partition is not specified, the default partition will be assumed. If a device is not partitioned into two or more partitions, this value can be left out. If file is not specified, it will default to file specified in ciscoFlashCopySourceName.
For a copy from Flash memory by means of tftp or rcp, the file name will be as per the file naming conventions and destination sub-directory on the server. If not specified, file from the source file name will be used.
For a copy from Flash memory by means of lex, this string will consist of numeric characters specifying the interface on the lex box that will receive the source flash image.
Syntax: DisplayString (SIZE (0-255))
Access: Read-create
Specifies the remote user name for copy by means of the rcp protocol. Optional. This object will be ignored for protocols other than rcp. If specified, it will override the remote user-name configured through the rcmd remote-username username configuration command. The remote user-name is sent as the server user-name in an rcp command request sent by the system to a remote rcp server.
Syntax: DisplayString (SIZE (1-255))
Max-Access: Read-create
Specifies the status of the specified copy operation, as defined in Table 3-2.
Syntax: Integer
Max-Access: Read-only
| Status Message | Meaning |
|---|---|
| 1 = copyInProgress | Specified operation is active. |
| 2 = copyOperationSuccess | Specified operation is supported and completed successfully. |
| 3 = copyInvalidOperation | Command invalid or command-protocol-device combination unsupported. |
| 4 = copyInvalidProtool | Invalid protocol specified. |
| 5 = copyInvalidSourceName | Invalid source file name specified For the copy from flash to lex operation, this error code will be returned when the source file is not a valid lex image. |
| 6 = copyInvalidDestName | Invalid target name (file or partition or device name) specified. For the copy from flash to lex operation, this error code will be returned when no lex devices are connected to the router or when an invalid lex interface number has been specified in the destination string. |
| 7 = copyInvalidServerAddress | Invalid server address specified. |
| 8 = copyDeviceBusy | Specified device is in use and locked by another process. |
| 9 = copyDeviceOpenError | Invalid device name. |
| 10 = copyDeviceError | Device read, write or erase error. |
| 11 = copyDeviceNotProgrammable | Device is read-only but a write or erase operation was specified. |
| 12 = copyDeviceFull | Device is filled to capacity. |
| 13 = copyFileOpenError | Invalid file name; file not found in partition. |
| 14 = copyFileTransferError | File transfer was unsuccessful; network failure. |
| 15 = copyFileChecksumError | File checksum in Flash failed. |
| 16 = copyNoMemory | System running low on memory. |
| 17 = copyUnknownFailure | Failure unknown. |
ciscoFlashCopyNotifyOnCompletion
Specifies whether a notification should be generated on the completion of the copy operation. If specified, ciscoFlashCopyCompletionTrap will be generated. It is the responsibility of the management entity to ensure that the SNMP administrative model is configured in such a way as to allow the notification to be delivered.
Syntax: TruthValue
Max-Access: Read-create
Specifies the time taken for the copy operation. This object will be like a stopwatch, starting when the operation starts, stopping when the operation completes. If a management entity keeps a database of completion times for various operations, it can then use the stopwatch capability to display percentage completion time.
Syntax: TimeTicks
Max-Access: Read-only
Specifies the status of this table entry.
Syntax: RowStatus
Max-Access: Read-create
End of Table
Specifies a table of Flash partitioning operation entries. Each entry represents a Flash partitioning operation that has been initiated.
Syntax: SEQUENCE OF CiscoFlashPartitioningEntry
Max-Access: Not-accessible
Specifies a Flash partitioning operation entry. Each entry consists of the command, the target device, the partition count, and optionally the partition sizes.
To create an entry a management station should first generate a pseudo-random serial number to be used as the index to this sparse table. The station should then create the associated instance of the row status object. It must also, either in the same or in successive PDUs, create the associated instance of the command and parameter objects. And it should modify the default values for any of the parameter objects if the defaults are not appropriate.
Once the appropriate instances of all the command 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 operation. Note that this entire procedure may be initiated via a single set request that specifies a row status of createAndGo and specifies valid values for the non-defaulted parameter objects.
Once an operation has been activated, it cannot be stopped. Once the operation completes, the management station should retrieve the value of the status object (and time if desired), and delete the entry. In order to prevent old entries from clogging the table, entries will be aged out, but an entry will never be deleted within 5 minutes of completing.
Syntax: CiscoFlashPartitioningEntry
Max-Access: Not-accessible
ciscoFlashPartitioningSerialNumber
Specifies the object which identifies a unique entry in the partitioning operations table. A management station wishing to initiate a partitioning operation should use a pseudo-random value for this object when creating or modifying an instance of a ciscoFlashPartitioningEntry.
Syntax: Integer32
Max-Access: Not-accessible
Specifies the partitioning command to be executed. Mandatory. If the command is unsupported, the partitioningInvalidOperation error will be reported in the operation status.Table 3-4 shows the command and its parameters.
Syntax: Integer 1 = partition
Max-Access: Read-create
| Command | Remarks | Parameters |
|---|---|---|
| partition | Partition a Flash device. All the prerequisites for partitioning must be met for this command to succeed. | PartitioningDestinationName, PartitioningPartitionCount, PartitioningPartitionSizes (optional), PartitioningNotifyOnCompletion (optional) |
ciscoFlashPartitioningDestinationName
Specifies the destination device name. This name will be the value obtained from FlashDeviceName. If the name is not specified, the default Flash device will be assumed.
Syntax: DisplayString (SIZE (0-255))
Max-Access: Read-create
ciscoFlashPartitioningPartitionCount
Specifies the number of partitions to be created. Its value cannot exceed the value of ciscoFlashDeviceMaxPartitions.
To undo partitioning (revert to a single partition), this object must have the value 1.
Syntax: Integer32
Max-Access: Read-create
ciscoFlashPartitioningPartitionSizes
Specifies the size of each partition to be created. The size of each partition will be in units of ciscoFlashDeviceMinPartitionSize. The value of this object will be in the form:
<part1>:<part2>...:<partn>
If partition sizes are not specified, the system will calculate default sizes based on the partition count, the minimum partition size, and the device size. Partition size need not be specified when undoing partitioning (partition count is 1). If partition sizes are specified, the number of sizes specified must exactly match the partition count. If not, the partitioning command will be rejected with the invalidPartitionSizes error.
Syntax: DisplayString
Max-Access: Read-create
Specifies the status of the specified partitioning operation (Table 3-5).
Syntax: Integer
Max-Access: Read-only
| Operation | Meaning |
|---|---|
| 1 = partitioningInProgress | The specified operation is active. |
| 2 = partitioningOperationSuccess | The specified operation has completed successfully. |
| 3 = partitioningInvalidOperation | Command invalid or command-protocol-device combination unsupported. |
| 4 = partitioningInvalidDestName | Invalid target name (file or partition or device name) specified. |
| 5 = partitioningInvalidPartitionCount | Invalid partition count specified for the partitioning command. |
| 6 = partitioningInvalidPartitionSizes | Invalid partition size, or invalid count of partition sizes. |
| 7 = partitioningDeviceBusy | The specified device is in use and locked by another process. |
| 8 = partitioningDeviceOpenError | Invalid device name. |
| 9 = partitioningDeviceEror | Device read, write or erase error. |
| 10 = partitioningNoMemoy | System running low on memory. |
| 11 = partitioningUnknownFailure | Failure unknown. |
ciscoFlashPartitioningNotifyOnCompletion
Specifies whether a notification should be generated on the completion of the partitioning operation. If specified, ciscoFlashPartitioningCompletionTrap will be generated. It is the responsibility of the management entity to ensure that the SNMP administrative model is configured in such a way as to allow the notification to be delivered.
Syntax: TruthValue
Max-Access: Read-create
Specifies the time taken for the operation. This object will be like a stopwatch, starting when the operation starts, stopping when the operation completes. If a management entity keeps a database of completion times for various operations, it can then use the stopwatch capability to display percentage completion time.
Syntax: TimeTicks
Max-Access: Read-only
ciscoFlashPartitioningEntryStatus
Specifies the status of this table entry.
Syntax: RowStatus
Max-Access: Read-create
End of Table
Specifies a table of miscellaneous Flash operation entries. Each entry represents a Flash operation that has been initiated.
Syntax: SEQUENCE OF CiscoFlashMiscOpEntry
Max-Access: Not-accessible
Specifies a Flash operation entry. Each entry consists of a command, a target, and any optional parameters.
To create an entry, a management station should first generate a pseudo-random serial number to be used as the index to this sparse table. The station should then create the associated instance of the row status object. It must also, either in the same or in successive PDUs, create the associated instance of the command and parameter objects. And it should also modify the default values for any of the parameter objects if the defaults are not appropriate.
Once the appropriate instances of all the command 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 operation. Note that this entire procedure may be initiated via a single set request which specifies a row status of createAndGo and specifies valid values for the non-defaulted parameter objects.
Once an operation has been activated, it cannot be stopped.
Once the operation completes, the management station should retrieve the value of the status object (and time if desired), and delete the entry. In order to prevent old entries from clogging the table, entries will be aged out, but an entry will never be deleted within 5 minutes of completing.
Syntax: CiscoFlashMiscOpEntry
Max-Access: Not-accessible
Specifies a unique entry in the table. When initiating a Flash operation a management station should use a pseudo-random value for this object when creating or modifying an instance of a ciscoFlashMiscOpEntry.
Syntax: Integer32
Max-Access: Not-accessible
Specifies the command to be executed. Mandatory. Note that it is possible for a system to support multiple file systems (different file systems on different Flash devices, or different file systems on different partitions within a device). Each such file system may support only a subset of these commands. If a command is unsupported, the miscOpInvalidOperation (3) error will be reported in the operation status. Commands are explained in Table 3-6. Table 3-7 lists command parameters.
| Command | Remarks |
|---|---|
| erase | Erase flash. |
| verify | Verify flash file checksum. |
| delete | Delete a file. |
| undelete | Revive a deleted file. Note that there are limits on the number of times a file can be deleted and undeleted. When this limit is exceeded, the system will return the appropriate error. |
| squeeze | Recover space occupied by deleted files. This command preserves the good files, erases out the file system, then restores the preserved good files. |
Syntax: Integer 1 = erase, 2 = verify, 3 = delete, 4 = undelete, 5 = squeeze
Max-Access: Read-create
| Command | Parameters |
|---|---|
| erase | MiscOpDestinationName, MiscOpNotifyOnCompletion (optional) |
| verify | MiscOpDestinationName, MiscOpNotifyOnCompletion (optional) |
| delete | MiscOpDestinationName, MiscOpNotifyOnCompletion (optional) |
| undelete | MiscOpDestinationName, MiscOpNotifyOnCompletion (optional) |
| squeeze | MiscOpDestinationName, MiscOpNotifyOnCompletion (optional) |
ciscoFlashMiscOpDestinationName
Specifies the destination file, or partition name. The file name must be of the following form:
[device:][partition:]file
where device is a value obtained from FlashDeviceName, partition is obtained from FlashPartitionName, and file is the name of a file in Flash. While leading and/or trailing white spaces are acceptable, no white spaces are allowed within the path itself.
A management station could derive its own partition name as per the description for the ciscoFlashPartitionName object. If device is not specified, the default Flash device will be assumed.
If partition is not specified, the default partition will be assumed. If a device is not partitioned into two or more partitions, this value can be left out.
For an operation on a partition, such as the erase command, this object would specify the partition name in the form:
[device:][partition:]
Syntax: DisplayString (SIZE (0-255))
Max-Access: Read-create
Specifies the status of the given operation (Table 3-8).
Syntax: Integer
Max-Access: Read-only
| Operation | Meaning |
|---|---|
| 1 = miscOpInProgress | Specified operation is active. |
| 2 = miscOpOperationSuccess | Specified operation has completed successfully. |
| 3 = miscOpInvalidOperation | Command invalid or command-protocol-device combination unsupported. |
| 4 = miscOpInvalidDestName | Invalid target name (file or partition or device name) specified. |
| 5 = miscOpDeviceBusy | Specified device is in use and locked by another process. |
| 6 = miscOpDeviceOpenError | Invalid device name. |
| 7 = miscOpDeviceError | Device read, write or erase error. |
| 8 = miscOpDeviceNotProgrammable | Device is read-only but a write or erase operation was specified. |
| 9 = miscOpFileOpenError | Invalid file name; file not found in partition. |
| 10 = miscOpFileDeleteFailure | File could not be deleted; delete count exceeded. |
| 11 = miscOpFileUndeleteFailure | File could not be undeleted; undelete count exceeded. |
| 12 = miscOpFileChecksumError | File has a bad checksum. |
| 13 = miscOpNoMemory | System running low on memory. |
| 14 = miscOpUnknownFailure | Failure unknown. |
| 18 = miscOpSqueezeFailure | The squeeze operation failed. |
| 19 = miscOpNoSuchFile | A valid but nonexistent filename was specified. |
ciscoFlashMiscOpNotifyOnCompletion
Specifies whether a notification should be generated on the completion of an operation. If specified, ciscoFlashMiscOpCompletionTrap will be generated. It is the responsibility of the management entity to ensure that the SNMP administrative model is configured in such a way as to allow the notification to be delivered.
Syntax: TruthValue
Max-Access: Read-create
Specifies the time taken for the operation. This object will be like a stopwatch, starting when the operation starts, stopping when the operation completes. If a management entity keeps a database of completion times for various operations, it can then use the stopwatch capability to display percentage completion time.
Syntax: TimeTicks
Max-Access: Read-only
Specifies the status of this table entry.
Syntax: RowStatus
Max-Access: Read-create
End of Table
The following notifications are supported with the ciscoFlash MIB:
A ciscoFlashCopyCompletionTrap is sent at the completion of a Flash copy operation if such a trap was requested when the operation was initiated.
ciscoFlashPartitioningCompletionTrap
A ciscoFlashPartitioningCompletionTrap is sent at the completion of a partitioning operation if such a trap was requested when the operation was initiated.
ciscoFlashMiscOpCompletionTrap
A ciscoFlashMiscOpCompletionTrap is sent at the completion of a miscellaneous Flash operation (enumerated in ciscoFlashMiscOpCommand) if such a trap was requested when the operation was initiated.
A ciscoFlashDeviceChangeTrap is sent whenever a removable Flash device is inserted or removed.
The integrated CSU/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.
The CSU/DSU static configuration table contains items that are statically configured and cannot be changed by a user without physically changing the CSU/DSU.
Syntax: SEQUENCE OF CiscoICsuDsuStaticConfigEntry
Max-Access: Not-accessible
An entry in the static configuration table for each integrated CSU/DSU.
Syntax: CiscoICsuDsuStaticConfigEntry
Max-Access: Not-accessible
Specifies the type of line interface or CSU/DSU.
Syntax: Integer 1 = fractionalT1, 2 = twoWireSwitched56k, 3 = fourWireSwitched56k, 4 = unknown
Max-Access: Read-only
The CSU/DSU hardware revision.
Syntax: DisplayString (SIZE (1-16))
Max-Access: Read-only
The CSU/DSU software revision.
Syntax: DisplayString (SIZE (1-16))
Max-Access: Read-only
The protocol revision of the CSU/DSU.
Syntax: DisplayString (SIZE (1-16))
Max-Access: Read-only
End of Table
The CSU/DSU test report table. The table contains the results of user-initiated tests, including self-test, reset, and loopback.
Syntax: SEQUENCE OF CiscoICsuDsuTestReportEntry
Max-Access: Not-accessible
An entry in the test report table for each integrated CSU/DSU.
Syntax: CiscoICsuDsuTestReportEntry
Max-Access: Not-accessible
ciscoICsuDsuLastSelfTestResult
The result of the last self-test. The value is represented as a sum of a bit map. The variable bit positions are as follows:
1 = Flash Checksum bad. Catastrophic error.
2 = EPROM Checksum bad. Catastrophic error.
4 = RAM Tests failed. Catastrophic error.
8 = ROM Checksum bad. Catastrophic error.
16 = DteLoss. Could not put data terminal equipment (DTE) into loopback. Noncatastrophic error.
32 = patternLossDuringTest. Put DTE into loopback but found bit error rate tester (BERT) errors. Noncatastrophic error.
Syntax: Integer32
Max-Access: Read-only
ciscoICsuDsuTimeOfLastSelfTest
The SysUpTime of the last self-test execution (LastSelfTest).
Syntax: TimeStamp
Max-Access: Read-only
The number of times CSU/DSU has been reset.
Syntax: Counter32
Max-Access: Read-only
The SysUpTime of last CSU/DSU reset.
Syntax: TimeStamp
Max-Access: Read-only
The current status of the loopback test. The remaining loopback results are valid only if the status is completed or failed.
Syntax: Integer 1 = completed, 2 = inProgress, 3 = neverPerformed, 4 = failed
Max-Access: Read-only
The number of bit errors that occurred in the last successful loopback test. This variable is valid only if a remote loopback test with a pattern was performed.
Syntax: Integer32
Max-Access: Read-only
The duration of the last successful loopback test, in hundredths of seconds. Note that the CSU/DSU can lose framing during the test. If so, the duration represents the time between reframing and the end of the test. As a result, you cannot calculate the start time of the last loopback by subtracting this duration from the end time of the last loopback.
Syntax: TimeTicks
Max-Access: Read-only
The point in the network where the last loopback test was performed.
Syntax: Integer of 1, 2, 3, 4, 5, 6, or 7 which represents a point on either a T1 CSU//DSU or a switched 56-kbps CSU/DSU.
The meanings for a T1 CSU/DSU are as follows:
| 1 = dtePayload | Local DSU loopback. The configured fractions of the DS1 signal are looped back as the receive signal. Used to verify the operation of the DSU portion of the local CSU/DSU. |
| 2 = dteFull | Local CSU loopback. The DS1 transmit signal is looped back as the receive signal. It runs at full bandwidth irrespective of the number of fractions configured. Used to verify operation of the local CSU/DSU. |
| 3 = lineFull | The DS1 signal received from the network is transmitted back to the network. The signal is regenerated but not reframed. Loopback is performed at the CSU. Used to verify the operation of a T1 network. |
| 4 = linePayload | The DS1 signal received from the network is transmitted back to the network. Data is regenerated and reframed with any LCV or CRC errors corrected. Loopback is performed at the DSU. Used to verify the operation of the local CSU/DSU and a T1 network. |
| 5 = remoteSmartJack | The remote smart jack--a wall socket device installed by the telephone company (telco) to delineate the network between customer premises equipment (CPE) and telco equipment-- used to loop back the DS1 signal. This is similar to remoteFull loopback except that the signal is looped at the smart jack before reaching the remote CSU/DSU. Used to verify the operation of the local CSU/DSU and a T1 network. |
| 6 = remoteFull | The remote unit placed in lineFull loopback. Used to verify operation of the local CSU/DSU and a T1 network. |
| 7 = remotePayload | The remote unit placed in linePayload loopback. Used to verify the operation of the local CSU/DSU, T1 network, and remote CSU/DSU. |
The meanings of these integers for a switched 56-kbps CSU/DSU are as follows:
| 2 = dteFull | Local CSU loopback. The transmit signal is looped back as the receive signal at a point close to the physical network interface. Used to verify operation of the the local CSU/DSU. |
| 3 = lineFull | CSU/DSU is split into separate DTE and loop the interface sections. The signal received from the network is transmitted back to the network. Data received from DTE is transmitted back to DTE. Used to verify operation of the local CSU/DSU and network from a remote site. |
| 4 = linePayload | The signal received from the network is looped back at the DTE interface and transmitted back to the network. Data received from the DTE is ignored. Used to verify operation of the local CSU/DSU and network from a remote site. |
| 7 = remotePayload | Similar to linePayload except that the remote unit is placed into loopback. Used to verify operation of the local CSU/DSU, T1 network, and remote CSU/DSU. |
Max-Access: Read-only
Test pattern used for locally initiated remote loopback. Valid only if a remote loopback was last performed.
Syntax: Integer of 1, 2, 3, 4, 5, 6, 7, 8, 9, 10, 11, 12, 13, 14, 15, or 16 which represents a pattern for either a T1 CSU/DSU or switched 56-kpbs CSU/DSU.
The following pattern is valid for T1 or switched 56k CSU/DSUs:
| 1 = noPattern | No specific pattern is used; data is provided by the DTE. Used to loop back transmit data. |
The following patterns are valid only for T1 CSU/DSUs:
| 2 = patternQRW | Quasi-random word pattern. Used to measure bit error rates. |
| 3 = pattern0In1 | The repeated binary pattern of "0" or all zeros. Typically used for verification of B8ZS optioning of the T1 facility. |
| 4 = pattern1In1 | The repeated binary pattern of "1" or all ones. Typically used for signal power measurements. |
| 5 = pattern1In2 | The repeated binary pattern of "01". Typically used in testing for bridge taps. |
| 6 = pattern1In3 | The repeated binary pattern of "001". Typically used to terminate a remote loopback. |
| 7 = pattern1In5 | The repeated binary pattern of "00001". Typically used to put the remote unit in loopback. |
| 8 = pattern1In8 | The repeated binary pattern of "00000001". Typically used to stress the timing recovery circuits of repeaters and other intermediate equipment |
| 9 = pattern3In24 | The repeated binary pattern of "000000000000000000000111" or hexadecimal "000007". Typically used to test for ones density (consecutive zeros) tolerance on alternate mark inversion (AMI) lines. |
| 10 = patternUser | A user-defined pattern. |
The following patterns are valid only for switched 56-kbps CSU/DSUs:
| 11 = pattern2047 | 2047-bit long pseudorandom pattern containing a maximum of 10 sequential zeros and 11 sequential ones. |
| 12 = pattern511 | 511-bit long pseudorandom pattern containing a maximum of 8 sequential zeros and 9 sequential ones. |
| 13 = patternStressDDS1 | Digital Data System (DDS) stress test pattern #1. |
| 14 = patternStressDDS2 | DDS stress test pattern #2. |
| 15 = patternStressDDS3 | DDS stress test pattern #3. |
| 16 = patternStressDDS4 | DDS stress test pattern #4. |
Max-Access: Read-only
ciscoICsuDsuUserDefinedPattern
User Defined Loopback Pattern. This variable is valid only if ciscoICsuDsuLoopbackPattern is patternUser.
Syntax: DisplayString (SIZE (1-24))
Max-Access: Read-only
Loopback code used to initiate last remote loopback. This variable is valid only if a remote loopback was last performed.
Integer of 1, 2, or 3 representing a loopback code, as follows:
| 1 = standard | Standard loopback code. Usually consists of the repeated binary pattern of "00001". |
| 2 = alternate | Alternate loopback code. Usually the inverse of the standard pattern, or "11110". |
| 3 = v54 | V.54 pattern. Used for fractional loopback. |
Max-Access: Read-only
ciscoICsuDsuEndTimeOfLastLoopback
SysUpTime of completion of last loopback test execution.
Syntax: TimeStamp
Max-Access: Read-only
End of Table
This table contains current CSU/DSU configuration parameters for a T1 interface not covered by RFC 1406.
Syntax: SEQUENCE OF CiscoICsuDsuT1ConfigEntry
Max-Access: Not-accessible
An entry in the configuration table for each integrated T1 CSU/DSU.
Syntax: CiscoICsuDsuT1ConfigEntry
Max-Access: Not-accessible
Line build-out (LBO) is loss inserted by the CSU in order to meet the 15-to-22.5-decibel (dB) loss requirement of the premises remote-end section. This value is selected so that the sum of the phone company loss, cable length loss, and line build-out is greater than 15 dB but less than 22.5 dB.
Integer of 1, 2, or 3 representing a line build-out value, as follows:
| 1 = buildOut0 | Insert 0 dB. |
| 2 = buildOut7p5 | Insert 7.5 dB. |
| 3 = buildOut15 | Insert 15 dB. |
Max-Access: Read-only
Indicates whether the data terminal equipment (DTE) line code is inverted or not.
When fractional timeslots are configured for 64-kps and alternate mark inversion (AMI) linecode, a combination of inverting the DTE line code along with the proper line High-Level Data Link Control (HDLC) or Synchronous Data Link Control (SDLC) protocol might be necessary to meet the ones density constraint.
Syntax: Integer 1 = normal, 2 = inverted
Max-Access: Read-only
ciscoICsuDsuT1SupportRemoteAlarmIndication
Determines if the unit will generate or detect a remote alarm indication (RAI) signal, also known as a yellow alarm. In D4 framing format, data terminal equipment (DTE) (including Frame Relay equipment) that uses the HDLC or SDLC protocol can generate patterns as part of its normal traffic. These patterns might be interpreted as yellow alarms and can disrupt data traffic.
Syntax: TruthValue
Max-Access: Read-only
ciscoICsuDsuT1FullBandwidthRemoteLoopcode
Loopback code to be accepted from remote end to place the unit in and out of full bandwidth loopback.
Integer of 1, 2, or 3 representing a loopback code, as follows:
| 1 = standard | Standard loopback code. Usually consists of the repeated binary pattern of "00001". |
| 2 = alternate | Alternate loopback code. Usually the inverse of the standard pattern or "11110". |
| 3 = disabled | No code is accepted, disabling a request for remote loopback. |
Max-Access: Read-only
ciscoICsuDsuT1PayloadRemoteLoopcode
Loopback code to be accepted from remote end to place the unit in and out of payload or fractional loopback.
Integer of 1, 2, 3, or 4 representing a loopback code, as follows:
| 1 = standard | Standard loopback code. Usually consists of the repeated binary pattern of "00001". |
| 2 = alternate | Alternate loopback code. Usually the inverse of the standard pattern or "11110". |
| 3 = disabled | No code is accepted, disabling a request for remote loopback. |
| 4 = v54 | V.54 pattern. Used for fractional loopback. |
Max-Access: Read-only
End of Table
This table contains information about the status of the CSU/DSU on a T1 interface, including externally generated alarm conditions.
Syntax: SEQUENCE OF CiscoICsuDsuT1StatusEntry
Max-Access: Not-accessible
An entry in the status table for each integrated T1 CSU/DSU.
Syntax: CiscoICsuDsuT1StatusEntry
Max-Access: Not-accessible
The current loop status of a T1 CSU/DSU. This value is represented as a sum of a bit map. The variable bit positions are as follows:
| 1 = lossofSignal | (LOS); unable to detect the DS1 signal. |
| 2 = lossofFrame | (LOF); unable to synchronize on the DS1 signal. |
| 4 = detectedRemoteAlarmIndication | (RAI); indicates that the transmitting equipment has lost its incoming signal. RAI is commonly called a yellow alarm. |
| 8 = detectedAlarmIndicationSignal | (AIS); indicates that there is a transmission interruption located either at the equipment originating the AIS signal or upstream of that equipment. Indicated by an unframed, all-ones signal. Also known as a blue alarm. |
| 16 = placedInLoopback | Line placed in loopback from remote. |
Syntax: Integer32
Max-Access: Read-only
The number of times a lossofSignal (LOS) event has been detected.
Syntax: Counter32
Max-Access: Read-only
The number of times a lossofFrame (LOF) event has been detected.
Syntax: Counter32
Max-Access: Read-only
ciscoICsuDsuT1RemoteAlarmIndications
The number of times a RemoteAlarmIndication (RAI) signal or yellow alarm has been received.
Syntax: Counter32
Max-Access: Read-only
ciscoICsuDsuT1AlarmIndicationSignals
The number of times an Alarm Indication Signal (AIS) or blue alarm has been received.
Syntax: Counter32
Max-Access: Read-only
End of Table
This table contains current CSU/DSU configuration parameters for a switched 56-kbps network.
Syntax: SEQUENCE OF CiscoICsuDsuSw56kConfigEntry
Max-Access: Not-accessible
An entry in the configuration table for each integrated switched 56-kbps CSU/DSU.
Syntax: CiscoICsuDsuSw56kConfigEntry
Max-Access: Not-accessible
This variable configures the DSU module for the specific type of network being used.
Integer of 1, 2, 3, or 4 representing a network type, as follows:
| 1 = dds | AT&T's Dataphone Digital Service, generically known as Digital Data System. Requires a 4-wire interface. |
| 2 = att | AT&T's Switched 56 Network. Operates over a 2-wire or 4-wire interface. |
| 3 = sprint | Sprint Switched 56 Network. Operates over a 2-wire or 4-wire interface. |
| 4 = otherCarrier | Indicates another carrier is being used. |
Max-Access: Read-only
Specifies the timing source for the DSU. The internal value indicates timing provided by DSU; line indicates timing provided by network receive signal.
Syntax: Integer 1 = internal, 2 = line
Max-Access: Read-only
The loop rate option selects the network loop operating speed. Only a ciscoICsuDsuSw56kNetworkType of dds supports all listed loop rates; att and sprint network types support only bps56k, or 56 kilobits per second.
Syntax: Integer 1 = bps2400, 2 = bps4800, 3 = bps9600, 4 = bps19k, 5 = bps38k, 6 = bps56k, 7 = bps64k
Max-Access: Read-only
ciscoICsuDsuSw56kScramblerEnabled
Indicates if line code scrambling is enabled. Scrambling is used to prevent data terminal equipment (DTE) data sequences that mimic network loop maintenance functions from activating loopback. This variable is supported only when operating in Digital Data System (DDS) mode at 64-kbps (also known as clear channel mode).
Syntax: TruthValue
Max-Access: Read-only
ciscoICsuDsuSw56kRemoteLoopbackEnabled
Indicates if a request for remote digital loopback will be accepted.
Syntax: TruthValue
Max-Access: Read-only
End of Table
This table contains information about the status of the CSU/DSU on a switched 56-kbps network, including externally generated alarm conditions.
ciscoICsuDsuSw56kLineStatusTable
Syntax: SEQUENCE OF CiscoICsuDsuSw56kLineStatusEntry
Max-Access: Not-accessible
ciscoICsuDsuSw56kLineStatusEntry
An entry in the status table for each integrated switched 56-kbps CSU/DSU.
Syntax: CiscoICsuDsuSw56kLineStatusEntry
Max-Access: Not-accessible
ciscoICsuDsuSw56kDialingStatus
This variable indicates dialing status information.
Integer of 1, 2, 3, 4, 5, or 6 representing a dialing status, as follows:
| 1 = idle | On-hook with no call in progress. |
| 2 = dialing | Dialing a number. |
| 3 = onLine | Online and passing data. |
| 4 = noWinkFromSwitch | No wink from switch (cleared after 5 seconds). Wink is a DC signaling method in which the polarity of the line is temporarily reversed and then returned to its original polarity as an acknowledgment. |
| 5 = numberBusy | Number is busy (cleared after 5 seconds). |
| 6 = noAnswer | No answer (cleared after 5 seconds). |
Max-Access: Read-only
The current loop status or alarm condition. Represented as a sum of a bit map. The variable bit positions are:
| 1 = oosOofFromNetwork | The DSU is receiving out of service/out of frame code from the network, indicating network trouble. This can be a problem with a device at the remote DSU. The most common cause of this error is either that the remote DSU is powered off or that the remote telephone company (telco) connection is open. |
| 2 = noReceiveSignal | The DSU has detected sealing current from the central office, but the receive level is below -45db. |
| 4 = noSealingCurrent | The DSU does not detect sealing current on the loop interface. This is normal for a private network. |
| 8 = noFrameSync | At 64-kbps data rates, the local loop operates at 72 kbps with a framing pattern added to maintain byte alignment with the network. This condition is reported if the DSU cannot find the framing pattern. |
| 16 = attemptingToRateAdap | Set in autorate mode when the DSU is searching for the loop rate. |
| 32 = rtTestFromTelco | Set when the DSU is in a telco-initiated RT test. |
| 64 = llTestFromTelco | Set when the DSU in telco-initiated LL test or when the transmit and receive pairs are reversed. |
| 128 = rdlFromRemoteDSU | Set when remote digital loopback initiated from remote DSU. |
Syntax: Integer32
Max-Access: Read-only
ciscoICsuDsuSw56kReceivedOosOofs
The number of times out of sync (OOS) / out of frame (OOF) code has been received.
Syntax: Counter32
Max-Access: Read-only
ciscoICsuDsuSw56kLostSealingCurrents
The number of times the DSU detects lost sealing current.
Syntax: Counter32
Max-Access: Read-only
ciscoICsuDsuSw56kLostReceiveSignals
The number of times the DSU detects lost receive signal.
Syntax: Counter32
Max-Access: Read-only
ciscoICsuDsuSw56kLostFrameSyncs
The number of times the DSU detects lost frame synchronization.
Syntax: Counter32
Max-Access: Read-only
ciscoICsuDsuSw56kLoopRateSearches
The number of times the DSU attempted loop rate search.
Syntax: Counter32
Max-Access: Read-only
End of Table
The following notifications and notification enables are supported with the Integrated CSU/DSU MIB.
ciscoICsuDsuEnableT1LoopStatusNotification
Indicates whether or not a T1 alarm notification will be generated by this system.
Syntax: TruthValue
Max-Access: Read-write
ciscoICsuDsuEnableSw56LoopStatusNotification
Indicates whether or not a switched 56-kbps alarm notification will be generated by this system.
Syntax: TruthValue
Max-Access: Read-write
ciscoICsuDsuT1LoopStatusNotification
Indicates a change in T1 loop status.
ciscoICsuDsuSw56kLoopStatusNotification
Indicates a change in switched 56-kbps loop status.
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 sublayers. 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.
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
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
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
Specifies an arbitrary sequence number associated with the neighbor.
Syntax: Integer32
Max-Access: Not-accessible
Specifies the ifIndex value of a 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
Specifies the ASCII name of the neighbor.
Syntax: DisplayString
Max-Access: Read-create
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
Specifies the applicable permissions.
Syntax: Integer 1 = iCanCallHim, 2 = heCanCallMe, 3 = weCanCallEachOther
Max-Access: Read-create
Maximum call duration in seconds. Zero means "unlimited".
Syntax: Integer32 (1-2147483647)
Max-Access: Read-create
Specifies the duration of last call in seconds.
Syntax: Integer32 (1-2147483647)
Max-Access: Read-only
Specifies the ASCII reason that the last call terminated.
Syntax: DisplayString
Max-Access: Read-only
Specifies the encoded reason for the last call tear down.
Syntax: Octet string
Max-Access: Read-only
Specifies the number of completed calls to neighbor since system reset.
Syntax: Counter32
Max-Access: Read-only
Specifies the number of call attempts that have failed.
Syntax: Counter32
Max-Access: Read-only
Specifies the number of calls accepted from the neighbor.
Syntax: Counter32
Max-Access: Read-only
Specifies the number of calls from the neighbor that have been refused.
Syntax: Counter32
Max-Access: Read-only
Specifies the sysUpTime of last call attempt.
Syntax: TimeStamp
Max-Access: Read-only
Enables a new vendor to manage the device using SNMP.
Syntax: RowStatus
Max-Access: Read-create
End of Table
This section describes the trap associated with the Cisco ISDN group.
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.
The variables described in this section are used to manage interface queuing in Cisco devices.
This table contains objects that describe the queues on a Cisco interface.
An interface queue is modeled as a collection of one or more secondary queues that feed into a device's hardware queue. The hardware queue has a maximum depth set by the MCI tx-queue-limit command or equivalent. The secondary queues (also known as the "hold queue") have maximum depths set by the hold-queue command or equivalent.
This table parallels the ifTable, and indicates the type of queuing in use on the interface, number of queues, and similar parameters.
Syntax: SEQUENCE OF CQIfEntry
Max-Access: Not-accessible
The type of queuing used in the hold queue.
First-in, first-out queuing implies that the interface always transmits messages in the order that they are received.
Priority queuing sorts messages out by the use of access lists. Messages in a higher priority queue are always sent in preference to messages in a lower priority queue.
Custom queuing sorts messages out by the use of access lists. Sub-queues are selected in round robin order as either the sub-queue is drained or a given number of octets is moved from the sub-queue to the transmission queue.
Weighted fair queuing sorts messages by "conversation," which is source-destination pair of addresses and sockets or ports, as defined by the network layer protocol. Messages are removed from queues in a sequence that gives each conversation a proportion of the available bandwidth.
Syntax: CQAlgorithm
Max-Access: Read-only
The maximum number of messages placed into the hardware transmission queue. This is a first-come, first-serve queue, fed by the hold queue. If the hold queue contains information, this queue is presumably full.
Syntax: Integer32
Max-Access: Read-only
The number of sub-queues of which the hold queue is built. This is a constant for each value of cQIfQType.
Syntax: Integer32
Max-Access: Read-only
End of Table
This table contains statistical objects for the subqueues of a Cisco interface.
Syntax: SEQUENCE OF CQStatsEntry
Max-Access: Not-accessible
The number of the queue within the queue set.
In first-in, first-out queuing, this value is always 2.
In priority queuing, it corresponds to the various priorities:
In custom queuing, it is the queue number referenced in the access list.
In weighted fair queuing, it is the queue number associated with the traffic stream (conversation) identified.
Syntax: Integer32
Max-Access: Not-accessible
The number of messages in the subqueue.
Syntax: Gauge32
Max-Access: Read-only
The maximum number of messages permitted in the subqueue.
Syntax: Integer32
Max-Access: Read-only
The number of messages discarded from this queue since restart by reason of enqueue when cQStatsDepth is equal to or greater than cQStatsMaxDepth.
Syntax: Counter32
Max-Access: Read-only
End of Table
This table describes the rotation of custom queuing on an interface.
Syntax: SEQUENCE OF CQRotationEntry
Max-Access: Not-accessible
The number of octets which can be transmitted from a custom queuing subqueue before it must yield to another queue.
Syntax: Integer32
Max-Access: Read-only
End of Table
The variables described in this section are used to manage IP encryption.
The type of encryption configured on a particular router, encoded as a bit-string.
A router can support multiple encryption algorithms--for example, 56-bit Data Encryption Standard (DES) with 8-bit cipher feedback and 40-bit DES with 6-bit cipher feedback.
Syntax: BITS, 0 = des56bitCfb64, 1 = des56bitCfb8, 2 = des40bitCfb64, 3 = des40bitCfb8
Max-Access: Read-only
The interval at which keys expire for a session and are renegotiated.
Syntax: Integer32
Max-Access: Read-only
The total number of encryption engines.
Syntax: Gauge32
Max-Access: Read-only
A table describing status of all encryption engines present within the router.
Syntax: SEQUENCE OF CieEngineStatusEntry
Max-Access: Not-accessible
Each entry in this table describes the public key associated with each engine, with its unique ID. If encryption is hardware assisted, each entry also describes the status of the encryption port adaptor.
Syntax: CieEngineStatusEntry
Max-Access: Not-accessible
The unique value identifying the encryption engine. For Route Processor (RP) systems, and other software-only platforms, this value is the processor ID. For the encryption port adapter (EPA), this value is a unique ID retrieved from the EPA.
Syntax: Integer32
Max-Access: Read-only
Corresponds to cardIfIndex in the Chassis MIB. If the value is 0, this is a software encryption engine.
Syntax: Integer32
Max-Access: Read-only
The public key for a particular encryption engine.
Syntax: Octet String (SIZE (0-1024))
Max-Access: Read-only
Indicates whether the encryption port adaptor (EPA) has been tampered with.
Syntax: TruthValue
Max-Access: Read-only
Indicates whether the encryption port adaptor (EPA) has been properly authenticated for this router.
Syntax: TruthValue
Max-Access: Read-only
Indicates the current operating mode of the EPA card. This variable directly corresponds to LED status shown on the encryption port adapter (EPA).
Syntax: Integer, 1 = enableActive, 2 = boot, 3 = error
Max-Access: Read-only
End of Table
The total number of active, pending, and dead encryption connections.
Syntax: Gauge32
Max-Access: Read-only
A table that describes all encrypted IP traffic created by the router, between the protected entity (cieProtectedAddr) and the unprotected entity (cieUnprotectedAddr). Each entry in this table describes a virtual encrypted IP tunnel.
Syntax: SEQUENCE OF CieConnEntry
Max-Access: Not-accessible
This entry describes a connection: the protected and unprotected node, status of the connection, number of packets encrypted per connection, number of packets decrypted per connection, and algorithm used for encrypting data. Each entry also contains a pointer to the encryption engine that is performing the encryption.
Syntax: CieConnEntry
Max-Access: Not-accessible
An integer that increases by a constant value for the purpose of indexing the cieConnTable. When it reaches the maximum value, the agent wraps the value back to 1 and may flush existing entries.
Syntax: Integer32 (1-2147483647)
Max-Access: Not-accessible
The IP address for protected (secure) node.
Syntax: IpAddress
Max-Access: Read-only
The IP address of the unprotected (insecure) node in the network.
Syntax: IpAddress
Max-Access: Read-only
An integer describing a status or type of connection. The pending and bad connections may be removed after 4 minutes of nonactivity. Open (active) connections may be removed if they have not transmitted or received traffic in the last cieEncryptionKeyTimeout minutes.
Syntax: Integer, 1 = pendingConnection, 2 = openConnection, 3 = exchangeKeys, 4 = badConnection
Max-Access: Read-only
The total number of packets encrypted for this connection.
Syntax: Counter32
The total number of packets decrypted for this connection.
Syntax: Counter32
Max-Access: Read-only
The total number of packets dropped for this connection. The packets are dropped only in cases where encryption keys are not established between the protected entity and the unprotected entity. An increase in this value indicates the possibility of misconfigured keys.
Syntax: Counter32
Max-Access: Read-only
Value of sysUpTime at which the connection was established or reestablished.
Syntax: TimeStamp
Max-Access: Read-only
The type of encryption algorithm used for this connection.
Syntax: Integer 1 = des56bitCfb64, 2 = des56bitCfb8, 3 = des40bitCfb64, 4 = des40bitdesCfb8
Max-Access: Read-only
End of Table
A table of test encryption session entries.
Syntax: SEQUENCE OF CieTestConnEntry
Max-Access: Not-accessible
An encryption test entry.
A management station that wishes to create an entry must first generate a pseudorandom serial number to be used as the index to this sparse table. The station must then create the associated instance of the row status and row owner objects. It must also, either in the same or in successive protocol data units (PDUs), create the associated instance of the address objects.
Once the appropriate instance of each configuration object has been created (such as by an explicit SNMP set request), the row status must be set to active to initiate the request. This entire procedure can be initiated via a single set request, which specifies a row status of createAndGo.
Once the connection sequence has been activated, it cannot be stopped--it will run until an encryption connection has been established between source and destination.
Once the sequence is completed, the management station must retrieve the values of the status objects of interest and must then delete the entry. To prevent old entries from clogging the table, entries are aged-out 30 minutes after they are created.
Syntax: SEQUENCE OF CieTestConnEntry
Max-Access: Not-accessible
Object that specifies a unique entry in the cieTestConnTable. A management station that wishes to initiate an encryption session test operation must use a pseudorandom value for this object when creating an instance of a cieTestConnEntry. The RowStatus semantics of the cieTestConnEntryStatus object prevents access conflicts.
Syntax: Integer32 (1-2147483647)
Max-Access: Not-accessible
The IP address of the protected (secure) node for the test connection.
Syntax: IpAddress
Max-Access: Read-create
The IP address of the unprotected (insecure) node for the test connection.
Syntax: IpAddress
Max-Access: Read-create
Specifies whether or not a cieTestCompletion trap is to be issued on completion of a test encryption session. If such a trap is desired, the management entity must ensure that the SNMP administrative model is configured in such a way as to allow the trap to be delivered.
Syntax: TruthValue
Max-Access: Read-create
Specifies the name of the encryption map already configured on the router. An encryption map specifies an encryption policy, such as the type of algorithm to be used and the name of the peer router.
Syntax: DisplayString
Max-Access: Read-create
Specifies the tag number of the encryption map already configured on the router. An encryption map along with its tag number fully specifies the encryption policy, such as the type of algorithm to be used, the name of the peer router, and the access list.
Syntax: Integer32 (1-2147483647)
Max-Access: Read-create
Set to a value that indicates whether an encryption session was successfully established or failed or whether the connection establishment process is in progress. If the specified encryption map is not configured, the value is set to badCryptoMapName.
Syntax: Integer, 1 = inProgress, 2 = fail, 3 = success, 4 = badCryptoMapName
Max-Access: Read-only
The entity that configured this entry.
Syntax: OwnerString
Max-Access: Read-create
The status of this table entry. Once the entry status is set to active, the associate entry cannot be modified until the sequence completes--cieTestConnSessionStatus has a value other than inProgress.
Syntax: RowStatus
Max-Access: Read-create
End of Table
The following notification is supported with the Cisco IP Encryption MIB:
A cieTestCompletion trap is sent at the completion of an encryption session establishment if such a trap was requested when the sequence was initiated.
The variables described in this section are used to manage LAN Emulation (LANE) broadcast-and-unknown servers.
A (conceptual) table representing all the instances of broadcast-and-unknown servers on the designated device. This table may or may not allow the creation of rows, depending on whether the LANE service elements allow the separate creation of LANE server and broadcast-and-unknown server components. In the event that separate components are not allowed then the MINIMUM-ACCESS detailed in the MODULE-COMPLIANCE should be used by those broadcast-and-unknown server implementations.
Syntax: SEQUENCE OF BusEntry
Max-Access: Not-accessible
An entry (conceptual row) in the busTable.
Syntax: BusEntry
Max-Access: Not-accessible
The emulated LAN name of the designated bridge.
Syntax: DisplayString (1-32)
Max-Access: Not-accessible
A unique identifier for this particular broadcast-and-unknown server on this emulated LAN. This value must remain constant while the entry is in existence and during the operation of the agent, but it is allowed to change after a reboot. For implementations that do not support more than one broadcast-and-unknown server entity per emulated LAN per device, it is sufficient to always report 1 for this object and only to accept the value 1 for row creation.
Syntax: Integer (1-2147483647)
Max-Access: Not-accessible
The primary Asynchronous Transfer Mode (ATM) address of the broadcast-and-unknown server on the interface of interest. Note that setting this object will have the side effect of reinitializing the broadcast-and-unknown server and consequently dropping all clients connected to it. If this object is not specified at row creation time, then the broadcast-and-unknown server will choose a value for itself and attempt to register with the switch with that value. If an address is specified that is not acceptable to the switch, then the busOperStatus will remain inactive until an acceptable address is set.
Syntax: AtmLaneAddress
Max-Access: Read-create
An address mask that, when used with the busAtmAddrSpec, specifies the portion of the broadcast-and-unknown server's ATM address that is to be configured. Note that setting this object will result in the reinitialization of the broadcast-and-unknown server, consequently dropping all clients connected to it. At row creation time, you cannot set this object without also supplying a value for busAtmAddrSpec.
If the broadcast-and-unknown server's ATM address is omitted at creation time, then this object's value defaults to all zeros (none of the busAtmAddrSpec value is relevant). If the broadcast-and-unknown server's ATM address is specified at creation time but this object is omitted, then this object's value defaults to all ones (all of the busAtmAddrSpec is relevant).
Syntax: OCTET STRING (SIZE (0 | 20))
Max-Access: Read-create
The resultant ATM address in use by the broadcast-and-unknown server. This object is a product of the specified ATM address, mask, and interaction with the switch via the Interim Local Management Interface (ILMI).
Syntax: AtmLaneAddress
Max-Access: Read-only
The primary interface that a broadcast-and-unknown server will forward traffic over. The value specified for this object must equate to a value of ifIndex in the ifTable. This MIB does not mandate that the ifTable be from RFC 1573 or RFC 1213. In the event that RFC 1573 is used, the index should pertain to the ATM adaptation layer 5 (AAL5) entity acting on behalf of the broadcast-and-unknown server. For RFC 1213 the interface will be for that particular ATM port. This object can be specified only upon row creation and cannot be altered thereafter.
Syntax: Integer32
Max-Access: Read-create
Specifies the subinterface number that the broadcast-and-unknown server will reside on. This subinterface may be shared with a LANE client or broadcast-and-unknown server of the same emulated LAN but is not required to do so. If no value is specified for this object at row creation time, then a subinterface will be chosen by the agent. This object may be specified only at row creation time and cannot be altered thereafter.
Syntax: Integer32
Max-Access: Read-create
The value of sysUpTime when this broadcast-and-unknown server became enabled.
Syntax: TimeStamp
Max-Access: Read-only
The type of legacy LAN in which this broadcast-and-unknown server participates. The default value is dot3.
Syntax: Integer 1 = dot3, 2 = dot5
Max-Access: Read-create
The maximum frame size that the emulated LAN may accept. The default value is 1516.
Syntax: Integer 1516 = dot3, 4544 = tr4Mb, 9234 = rfc1626, 18190 = tr16Mb
Max-Access: Read-create
The maximum number of seconds a broadcast-and-unknown server will hold onto a packet for forwarding until it is dropped. Dropping a packet will result in the incrementing of the busFrmTimeOuts counter. The default value is 1.
Syntax: Integer (1-4)
Max-Access: Read-create
The number of octets that this broadcast-and-unknown server has forwarded since its initialization.
Syntax: Counter32
Max-Access: Read-only
The number of frames that the broadcast-and-unknown server has forwarded that were unicast data frames, including all control frames (that is, they were flooded from the client).
Syntax: Counter32
Max-Access: Read-only
The number of frames that the broadcast-and-unknown server has forwarded that were multicast frames.
Syntax: Counter32
Max-Access: Read-only
The number of frames dropped by the broadcast-and-unknown server due to a timeout.
Syntax: Counter32
Max-Access: Read-only
The virtual path identifier for the Multicast Forward virtual channel connection (VCC).
Syntax: CiscoVpiInteger
Max-Access: Read-only
The virtual channel identifier for the Multicast Forward VCC.
Syntax: CiscoVciInteger
Max-Access: Read-only
The actual state of the broadcast-and-unknown server, which may differ from that of the busAdminStatus object. This difference can occur when the interface ifOperStatus value is down but the corresponding busAdminStatus value is active.
Syntax: Integer 1 = active, 2 = inactive
Max-Access: Read-only
The desired state of the designated broadcast-and-unknown server as prescribed by the operator. Normally, the actions of the agent will eventually produce this desired state in the busOperStatus. The default value is active.
Syntax: Integer 1 = active, 2 = inactive
Max-Access: Read-create
The status of the broadcast-and-unknown server entry. This object cannot be set to active until the busIfIndex object has an appropriate value. Note that implementations that do not support separate LANE server and broadcast-and-unknown server entities may refuse row creation in this table. Creation of broadcast-and-unknown server entities for those implementation is facilitated in the LANE server MIB.
Syntax: RowStatus
Max-Access: Read-create
End of Table
The variables in this section are used to manage LAN emulation (LANE) configuration server and the configuration data it utilizes.
A management station that wishes to set up a LANE configuration server on the current device using this MIB should perform the following steps as described in the following text. Some parts are order-dependent while others are not.
Step 1 Make an entry in the lecsConfigTblTable.
A default emulated LAN name is not required. If one is not provided, then the lecsConfigTblTable will be sparse. This step is not necessary if an entry already exists in the table.
Step 2 Add an entry to the lecsTable.
For the LANE configuration server to be functional, the lecsEntry must reference an entry in the lecsConfigTblTable. A lecsEntry can be created, however, without the existence of a corresponding lecsConfigTblEntry.
Step 3 Bind ATM addresses to the entry in the lecsTable, using the lecsAtmAddrTable.
Entries added to the lecsAtmAddrTable will dictate the ATM addresses upon which a LANE configuration server will receive requests. Configuration requests are received and processed only when entries exist in both the lecsTable and lecsAtmAddrTable.
The real data that is referenced within the configuration frames is located in the lecsElanConfigTable, lecsMacConfigTable, and lecsAtmAddrConfigTable. The management station must create entries in these tables, as appropriate, to model the corresponding LANE setup. These tables may only be filled once a lecsConfigTblEntry has been created to hold them.
The (conceptual) table containing the interface specific information of the LANE configuration server on a particular device and its associated statistics for that interface.
Syntax: SEQUENCE OF LecsEntry
Max-Access: Not-accessible
An entry (conceptual row) in the lecsTable, containing information of a LANE configuration server for a particular interface. Note that deleting an entry will have the side effect of deleting corresponding entries in the lecsAtmAddrTable.
Syntax: LecsEntry
Max-Access: Not-accessible
The textual name used to identify a configuration table in use by the designated LANE configuration server. Note that this value must be a reference to an entry in the lecsConfigTblTable.
Syntax: DisplayString (SIZE (1-32))
Max-Access: Read-create
The value of sysUpTime when this entry was created. Note that changing the value of the lecsAdminStatus will not affect the value of this object. This object is set only at row creation time, whether it results from explicit use of Simple Network Management Protocol (SNMP), from the command line interface (CLI), or from initialization at boot time.
Syntax: TimeStamp
Max-Access: Read-only
The number of LE_CONFIGURE_REQUESTs that have been received by this LANE configuration server on this designated interface.
Syntax: Counter32
Max-Access: Read-only
Then number of packets sent to the LANE configuration server from the lower layers that were not correctly formatted configuration requests.
Syntax: Counter32
Max-Access: Read-only
The number of LE_CONFIGURE_RESPONSEs sent by this particular LANE configuration server whose status was other than success.
Syntax: Counter32
Max-Access: Read-only
The cause for rejection of the last LE_CONFIGURE_REQUEST. This is the value of the status field that was sent in the rejection LE_CONFIGURE_RESPONSE. If the configuration server has never issued a failed response, then this object has the value of 0.
Syntax: Integer32
Max-Access: Read-only
The ATM address of the LANE client whose last configuration request was rejected. This ATM address is for the LANE client who was delivered the last LE_CONFIGURE_RESPONSE that caused the lecsOutConfigFails object to increment. This value is taken directly from the LE_CONFIGURE_REQUEST and is not guaranteed to be correctly identify a LANE client.
Syntax: AtmLaneAddress
Max-Access: Read-only
The actual state of the LANE configuration server which may differ from that of the lecsAdminStatus object. This difference can occur when the interface ifOperStatus value is down but the corresponding lecsAdminStatus value is active.
Syntax: Integer 1 = active, 2 = inactive
Max-Access: Read-only
The desired state of the LANE configuration server on this interface as prescribed by the operator. Normally, the actions of the agent will eventually produce this desired state in the lecsOperStatus. The default value is active.
Syntax: Integer 1 = active, 2 = inactive
Max-Access: Read-create
The status object for the lecsEntry. Note that the lecsConfigTableName need not be specified at row creation time. In that case, the row will be sparse (the column will not be present). A LANE configuration server without a mapping to a configuration table will drop any incoming requests without notification.
Syntax: RowStatus
Max-Access: Read-create
An indication of whether the LANE configuration server is acting as the operative master or is a redundant slave.
Syntax: TruthValue
Max-Access: Read-only
End of Table
A (conceptual) table of ATM addresses that are listened to by LANE configuration servers on this device.
Syntax: SEQUENCE OF LecsAtmAddrEntry
Max-Access: Not-accessible
An entry (conceptual row) that denotes an ATM address, on a particular interface, that a LANE configuration server monitors. Note that an entry in the lecsTable must exist for the corresponding ifIndex first before any ATM addresses can be assigned to it.
Syntax: LecsAtmAddrEntry
Max-Access: Not-accessible
An arbitrary number that uniquely corresponds to a value of lecsAtmAddrActual for a designated interface. Note that lecsAtmAddrActual could not be used for the index since it may not be known at the time of row creation (to be resolved through interaction with the switch). This value must remain constant while the device is running. It is not guaranteed to be constant between reboots of the device.
Syntax: Integer32 (1-2147483674)
Max-Access: Not-accessible
An ATM address specified by the network or local management that, with the ATM address mask, determines a portion of the ATM address that the LANE configuration server on the designated interface uses to accept configure requests on. If this object is omitted at row creation time, then the LANE configuration server will try to determine an ATM address, through the Internal Local Management Interface (ILMI), on its own.
When the LANE configuration server is configured to have one ATM address (one entry in this table), modifying this object results in the LANE configuration server reinitializing and dropping all connections to it.
Syntax: AtmLaneAddress
Max-Access: Read-create
A bit mask signifying what portion of the specified ATM address is relevant. If the ATM address is not specified at row creation time, then this object's value defaults to all zeros (no portion of the lecsAtmAddrSpec value is relevant). If the ATM address is specified but this object is omitted at row creation time, then this object's value defaults to all ones (all of the specified lecsAtmAddrSpec value is relevant).
This object cannot be specified at row creation time without a value of the lecsAtmAddrSpec object also being specified. When the LANE configuration server is configured to have one ATM address (one entry in this table), modifying this object results in the LANE configuration server reinitializing and dropping all connections to it.
Syntax: (OCTET STRING (SIZE (0 | 20))
Max-Access: Read-create
The resulting address on which the LANE configuration server is accepting configuration requests for the designated interface. This address is the result of the specified ATM address, its mask and interaction through the Internal Local Management Interface (ILMI) with the switch. This object is valid only when the corresponding lecsOperStatus is active.
Syntax: AtmLaneAddress
Max-Access: Read-only
Once a (conceptual) row is created, the LANE configuration server, if active, interacts through the Internal Local Management Interface (ILMI) and registers the address with the switch. The value of this object denotes what phase the current address is in, whether the lecsAtmAddrActual is valid or not, whether the address has been registered through the ILMI, and whether the address has been registered with signaling.
Syntax: Integer 1 = actualValueInvalid, 2 = actualValueValid, 3 = registeredWithSignalling, 4 = regSigAndValid, 5 = registeredWithIlmi, 6 = regIlmiAndValid, 7 = regSigandIlmi, 8 = regSigIlmiAndValid
Max-Access: Read-only
The status object for the lecsAtmAddrTable.
Syntax: RowStatus
Max-Access: Read-create
End of Table
This (conceptual) table allows a manager to view the LAN emulation (LANE) components that have established Configure Direct connections to the LANE configuration server over the designated interface.
Syntax: SEQUENCE OF LecsConfigDirectConnEntry
Max-Access: Not-accessible
An entry (conceptual row) that denotes a connection to the LANE configuration server in the form of a Configure Direct virtual channel connection (VCC). It is important to note that the lecsConfigDirectConnSrc and lecsConfigDirectConnDst are significant only when the virtual circuit is a switched virtual circuit (SVC). When the row represents a permanent virtual circuit (PVC), then these two columns will be omitted from the row, resulting in a sparse table.
Syntax: LecsConfigDirectConnEntry
Max-Access: Not-accessible
The virtual path identifier (VPI) of the designated connection to the LANE configuration server.
Syntax: VpiInteger (0-255)
Max-Access: Not-accessible
The virtual channel identifier (VCI) of the designated connection to the LANE configuration server.
Syntax: VciInteger (0-65535)
Max-Access: Not-accessible
The type of virtual connection that the designated Configure Direct virtual channel connection (VCC) uses. If this object has the value pvc then the lecsConfigDirectConnSrc and lecsConfigDirectConnDst are not be replicated.
Syntax: Integer 1 = pvc, 2 = svc
Max-Access: Read-only
The calling party ID if the virtual circuit is a switched virtual circuit (SVC). If the virtual circuit is a permanent virtual circuit (PVC), then this object is not instantiated for the designated virtual circuit.
Syntax: AtmLaneAddress
Max-Access: Read-only
The called party ID if the virtual circuit. If the virtual circuit is a permanent virtual circuit (PVC), then this object is not instantiated for the designated virtual circuit.
Syntax: AtmLaneAddress
Max-Access: Read-only
The type of entity on the other end of the virtual circuit.
Syntax: Integer 1 = lane-client, 2 = lane-server, 3 = lane-config, 4 = unknown
Max-Access: Read-only
End of Table
A (conceptual) table of the configuration tables in existence on the device. An entry must exist in this table before it can be used in the lecsTable, lecsElanConfigTable, lecsMacConfigTable, or lecsAtmAddrConfigTable.
Syntax: SEQUENCE OF LecsConfigTblEntry
Max-Access: Not-accessible
An entry (conceptual row) that denotes a configuration table.
Syntax: LecsConfigTblEntry
Max-Access: Not-accessible
The textual name used to identify a configuration table.
Syntax: DisplayString (SIZE (1-32))
Max-Access: Not-accessible
The emulated LAN name assigned to LAN Emulation clients that do not specify what emulated LAN they wish to join when issuing a configuration request. It is important to understand when the default emulated LAN name will be used. If the LANE client specifies an emulated LAN name in its configuration request and a different mapping or a conflicting mapping is present for that LANE client, then the default emulated LAN is not used and a failure reply is returned.
If the LANE client does not specify the emulated LAN name in the configuration request and no mapping is performed within the LANE configuration server, then the default emulated LAN name is used and a successful reply is returned (provided the rest of the request is valid). If no default emulated LAN is specified for this configuration table, then a LANE client, with no mapping to any emulated LAN will be rejected from configuration regardless of the parameters of the configuration request. The default value (''H) indicates that no default emulated LAN name is selected.
The default emulated LAN cannot have an access type of closed. Attempting to set the default emulated LAN type to a closed emulated LAN results in an error.
Syntax: DisplayString (SIZE (0-32))
Max-Access: Read-create
The status object associated with the designated entry. A value for lecsConfigTblDefaultElanName cannot be specified at row creation time because it points to an entry in the lecsElanConfigTable that depends on this designated entry. A management station wishing to set the lecsConfigTblDefaulElanName must do so in subsequent SET requests to the now active row.
Syntax: RowStatus
Max-Access: Read-create
End of Table
A (conceptual) configuration table that represents the names of the emulated LANs known to a LANE configuration server and their corresponding LANE server ATM addresses.
Syntax: SEQUENCE OF LecsElanConfigEntry
Max-Access: Not-accessible
An entry (conceptual row) in the emulated LAN configuration table representing a mapping from an emulated LAN name to a LANE server ATM address. Note that a value of the emulated LAN name must exist in this table before it can be used within the lecsMacConfigTable or the lecsAtmAddrConfigTable. Also note that the IMPLIED indexing of this table will not translate to the Simple Network Management Protocol, version 1 (SNMPv1) Structure of Management Information (SMI).
Syntax: LecsElanConfigEntry
Max-Access: Not-accessible
The name assigned to an emulated LAN in this configuration entry.
Syntax: DisplayString (SIZE (1-32))
Max-Access: Not-accessible
The ATM address of the LANE server associated with the emulated LAN of this entry.
Syntax: AtmLaneAddress
Max-Access: Read-create
The access of the emulated LAN to configure requests. A closed emulated LAN (similar to a closed user group) is prevented from being used as the default emulated LAN and also may not be asked for in the LE_CONFIGURE_REQUEST solely by emulated LAN name. Only clients that provide an ATM address or media access control (MAC) address that has been configured for the closed emulated LAN are given a successful LE_CONFIGURE_RESPONSE. The default value is open.
Syntax: Integer 1 = open, 2 = closed
Max-Access: Read-create
This object can be active only once when a valid value of lecsElanLesAtmAddr is filled in.
Syntax: RowStatus
Max-Access: Read-create
End of Table
A (conceptual) table utilized by a LANE configuration server to map a registered media access control (MAC) address of a LANE client to an emulated LAN name. This table is used by the LANE configuration server to assign a LANE client to an emulated LAN. However, not all configurable LANE clients are required to be in this table. Instead, they may opt to use the lecsAtmAddrConfigTable, or rely on the default emulated LAN set in the lecsConfigTblTable. A LANE server may also opt to use this table to determine whether a LANE client is authorized to join an emulated LAN.
Syntax: SEQUENCE OF LecsMacConfigEntry
Max-Access: Not-accessible
An entry (conceptual row) of a mapping between a media access control (MAC) address in primary utilization by a LANE client and an emulated LAN name.
Syntax: LecsMacConfigEntry
Max-Access: Not-accessible
A media access control (MAC) address to be associated with an emulated LAN name.
Syntax: MacAddress
Max-Access: Not-accessible
An emulated LAN name that is returned to a LANE client that provides the corresponding media access control (MAC) address in a configuration request. Only emulated LAN names within the lecsElanConfigTable are acceptable values for this object. If this object is left unspecified at row creation, then it will take on the value of the lecsConfigTblDefaultElanName from the designated configuration table.
Syntax: DisplayString (SIZE (1-32))
Max-Access: Read-create
The value of sysUpTime when this entry was last used to map a media access control (MAC) address to an emulated LAN name. Managers may opt to use this object to remove entries that have not been used for a prolonged period of time.
Syntax: TimeStamp
Max-Access: Read-only
The row cannot be set to active until an appropriate value exists for lecsMacConfigElanName. This value may be provided by the agent if a value for the lecsConfigTblDefaultElanName exists for the designated lecsConfigTblName.
Syntax: RowStatus
Max-Access: Read-create
End of Table
This (conceptual) table is used by the LANE configuration server to map between an ATM address of a LANE client and emulated LAN name.
Syntax: SEQUENCE OF LecsAtmAddrConfigEntry
Max-Access: Not-accessible
An entry (conceptual row) of the configuration table that maps between an ATM address of a LANE client and emulated LAN name.
Syntax: LecsAtmAddrConfigEntry
Max-Access: Not-accessible
An ATM address of a LANE client that when combined with an address mask is used to determine which emulated LAN the LANE client should belong to.
Syntax: Octet String (SIZE (20))
Max-Access: Not-accessible
An ATM address mask associated with the LANE client ATM address of this entry. Bits in this mask that are set to zero indicate that corresponding bit locations in the comparison ATM address are to be ignored for the purposes of matching. A mask of all zeros is the trivial case of having all comparisons match, while a mask of all ones indicates that the two ATM addresses must match exactly. This object is useful because ATM addresses are a composite negotiated by the switch and connected device. Wildcarding the prefix of an address indicates a preference of where a LANE client is to join regardless of the switch it is attached from. Wildcarding the ESI and selector byte indicates that a LANE client is to join a certain emulated LAN based on the switch it is attached to.
Syntax: Octet String (SIZE (20))
Max-Access: Not-accessible
The emulated LAN name to be returned to a configuration request that has specified an ATM address that matches the address-mask pair in this entry. Only emulated LAN names within the lecsElanConfigTable are acceptable values for this object. If this object is left unspecified at row creation, then it takes on the value of the lecsConfigTblDefaultElanName from the designated configuration table.
Syntax: DisplayString (SIZE (1-32))
Max-Access: Read-create
The value of sysUpTime corresponding to the time this entry was last used. The manager may opt to use this object to remove entries that have not been used for a prolonged period of time.
Syntax: TimeStamp
Max-Access: Read-only
The status of this entry (conceptual row) in the lecsAtmAddrConfigTable. The row cannot be set to active until an appropriate value exists for lecsAtmAddrConfigElanName. This value may be provided by the agent if a value for the lecsConfigTblDefaultElanName exists for the designated lecsConfigTblName.
Syntax: RowStatus
Max-Access: Read-create
End of Table
A table of LANE servers servicing an emulated LAN.
Syntax: SEQUENCE OF LecsLesConfigEntry
Max-Access: Not-accessible
An entry (conceptual row) in the lecsLesConfigTable.
Syntax: LecsLesConfigEntry
Max-Access: Not-accessible
The ATM address of a LANE server configured to service this emulated LAN.
Syntax: Octet String (SIZE(20))
Max-Access: Not-accessible
The relative priority of the LANE server. The lower this number is, the more priority is given the LANE server for servicing the emulated LAN. A higher-priority LANE server supersedes one of lower priority in operation of the emulated LAN.
Syntax: Integer (0-10000)
Max-Access: Read-create
The present state of the given LANE server. The active LANE server is servicing the emulated LAN, inactive LANE servers are connected but not accepting joins, and not-connected LANE servers are not accounted for.
Syntax: Integer 1 = active, 2 = inactive, 3 = not-connected
Max-Access: Read-only
The status of the conceptual row.
Syntax: RowStatus
Max-Access: Read-create
End of Table
The variables described in this section are used to manage LAN Emulation (LANE) servers (LANE servers) in Cisco devices.
A (conceptual) table containing all instances of LANE servers on this device.
Syntax: SEQUENCE OF LesEntry
Max-Access: Not-accessible
An entry (conceptual row) in the lesTable.
Syntax: LesEntry
Max-Access: Not-accessible
The name associated with the emulated LAN that this LANE server services.
Syntax: DisplayString (SIZE (1-32))
Max-Access: Not-accessible
A unique identifier for this LANE server servicing this emulated LAN. This value must remain constant while the entry is in existence and during the operation of the agent, but it is allowed to change after reboot. For implementations that do not allow more than one LANE server entity per emulated LAN per device, it is sufficient to always report 1 for this object and to accept only one for row creation.
Syntax: Integer32 (1-2147483647)
Max-Access: Not-accessible
The ATM address of the designated LANE server. Note that setting this object also reinitializes the LANE server and consequently drops all clients connected to it. If this object is not specified at row creation time, then the LANE server chooses a value for itself and attempts to register with the switch with that value. If an address is specified that is not acceptable to the switch, then the lesOperStatus remains inactive until an acceptable address is set.
Syntax: AtmLaneAddress
Max-Access: Read-create
An address mask that when used with the lesAtmAddrSpec specifies the portion of the LANE server ATM address that is to be configured. Setting this object also reinitializes the LANE server, consequently dropping all clients connected to it. You cannot set this object at row creation time without also supplying a value for the lesAtmAddrSpec object.
If the LANE server ATM address is omitted at creation time then this object's value defaults to all zeros (none of the lesAtmAddrSpec value is relevant). If the LANE server ATM address is specifed at creation time but this object is omitted, then this object's value defaults to all ones (all of the lesAtmAddrSpec is relevant).
Syntax: OCTET STRING (SIZE (0 | 20))
Max-Access: Read-create
The resultant ATM address in use by the LANE server. This object is a product of the specified ATM address, mask, and interaction with the switch via the Interim Local Management Interface (ILMI).
Syntax: AtmLaneAddress
Max-Access: Read-only
The primary interface that a LANE server will accept control connections on. The value specified for this object must equate to a value of ifIndex in the ifTable. This MIB does not mandate that the ifTable be from RFC 1573 or RFC 1213. If RFC 1573 is used, the index should pertain to the ATM adaptation layer 5 (AAL5) entity acting on behalf of the LANE server. For RFC 1213, the interface is for that particular ATM port. This object can be specified only upon row creation and cannot be altered thereafter.
Syntax: Integer32
Max-Access: Read-create
Specifies the subinterface number that the LANE server will reside on. This subinterface may be shared with a LANE client or broadcast-and-unknown server of the same emulated LAN but is not required to do so. If no value is specified for this object at row creation time, then a subinterface is chosen by the agent. This object may be specified only at row creation time and cannot be altered thereafter.
Syntax: Integer32
Max-Access: Read-create
For those implementations that do not allow the separate creation or deletion of the LANE server and broadcast-and-unknown server this object allows the operator to specify the ATM address of the broadcast-and-unknown server at LANE server creation time. For implementations that allow separate process creation, this object is optional. Otherwise, this is the ATM address of the designated broadcast-and-unknown server. Setting this object also reinitializes the broadcast-and-unknown server and consequently drops all clients connected to it. If this object is not specified at row creation time, then the broadcast-and-unknown server chooses a value for itself and attempts to register with the switch with that value. If an address is specified that is not acceptable to the switch, then the busOperStatus remains inactive until an acceptable address is set.
Syntax: AtmLaneAddress
Max-Access: Read-create
An address mask that when used with the lesColocatedBusAtmAddr specifies the portion of the broadcast-and-unknown server's ATM address desired by management. Setting this object also reinitializes the broadcast-and-unknown server and consequently drops all clients connected to it. You cannot set this object at row creation time without also supplying a value for the lesColocBusAtmAddrSpec object.
If the broadcast-and-unknown server's ATM address is omitted at creation time then this object's value defaults to all zeros (none of the lecColocBusAtmAddrSpec value is relevant). If the broadcast-and-unknown server's ATM address is specifed at creation time but this object is omitted, then this object's value defaults to all ones (all of the lesColocBusAtmAddrSpec is relevant).
Syntax: Octet String (SIZE (0 | 20))
Max-Access: Read-create
The ATM address in use by the broadcast-and-unknown server. This object is a product of the specified ATM address, its mask, and interaction with the switch through the Interim Local Management Interface (ILMI).
Syntax: AtmLaneAddress
Max-Access: Read-only
The value of sysUpTime when this LANE server became activated.
Syntax: TimeStamp
Max-Access: Read-only
The type of legacy LAN that this LANE server emulates. The default value is dot3.
Syntax: Integer 1 = dot3, 2 = dot5
Max-Access: Read-create
The maximum frame size that the specified LAN type can accept. The default value is 1516.
Syntax: Integer 1516 = dot3, 4544 = tr4Mb, 9234 = rfc1626, 18190 = tr16Mb
Max-Access: Read-create
The number of seconds that must elapse before a Join request can be timed out. The default value is 120.
Syntax: Integer (10-300)
Max-Access: Read-create
The ATM address associated with the LANE configuration server used by this LANE server. If no LANE configuration server is in use by the LANE server then this object has the value of all zeros--that is, 0x0000nnn and so on. If the LANE server retrieves the address of the LANE configuration server through the Interim Local Management Interface (ILMI), then this object may be left unspecified at row activation. If the ILMI fails, then the lesOperStatus will be inactive (2) and this column still not present.
Syntax: AtmLaneAddress
Max-Access: Read-create
The virtual path identifier (VPI) of the Control Distribute virtual channel connection (VCC) to all clients, if it exits.
Syntax: CiscoVpiInteger
Max-Access: Read-only
The virtual channel identifier of the Control Distribute virtual channel connection (VCC) to all clients, if it exists.
Syntax: CiscoVciInteger
Max-Access: Read-only
The actual state of the LANE server which may differ from that of the lesAdminStatus object. This difference can occur when the interface ifOperStatus is down but the corresponding lesAdminStatus is active.
Syntax: Integer 1 = active, 2 = inactive
Max-Access: Read-only
The desired state of the designated LANE server as prescribed by the operator. Normally, the actions of the agent eventually produce the desired state in the lesOperStatus.
Syntax: Integer 1 = active, 2 = inactive
Max-Access: Read-create
The status of this entry (conceptual row). This row cannot be set to active until an appropriate value of lesIfIndex has been specified.
Syntax: RowStatus
Max-Access: Read-create
End of Table
A (conceptual) table of statistics associated with LANE Servers instances on the device.
Syntax: SEQUENCE OF LesStatsEntry
Max-Access: Not-accessible
A (conceptual) row in the lesStatsTable that corresponds to the statistics kept by a particular instance of a LANE server.
Syntax: LesStatsEntry
Max-Access: Not-accessible
The number of frames received by the LANE server that were either malformed or did not follow standard protocol (for example, receiving a LANE-ARP request for a multicast address).
Syntax: Counter32
Max-Access: Read-only
The ATM address of the LANE client whose last frame to the LANE server resulted in an increment to the lesInErrors counter.
Syntax: AtmLaneAddress
Max-Access: Read-only
The number of Flush replies that were received by the LANE server and forwarded onto its clients.
Syntax: Counter32
Max-Access: Read-only
The number of LE_JOIN_REQUESTs received by this LANE server since activation.
Syntax: Counter32
Max-Access: Read-only
The number of rejection LE_JOIN_RESPONSEs transmitted by this LANE server since activation.
Syntax: Counter32
Max-Access: Read-only
The cause for the transmission of the last rejection LE_JOIN_RESPONSE. This is the value of the status field within the rejection response. If the server has never issued a rejection response, then this object has the value of 0.
Syntax: Integer32
Max-Access: Read-only
The ATM address of the client whose last LE_JOIN_REQUEST resulted in a rejection by this server. If the server has never issued a rejection response, then this object has the value of all zeros--that is, 0x000nnn and so on.
Syntax: AtmLaneAddress
Max-Access: Read-only
The number of LE_CONFIGURE_REQUESTs sent by this LANE server since activation.
Syntax: Counter32
Max-Access: Read-only
The number of successful LE_CONFIGURE_RESPONSEs received by this LANE server since activation.
Syntax: Counter32
Max-Access: Read-only
The number of rejection LE_CONFIGURE_RESPONSEs received by this LANE server since activation.
Syntax: Counter32
Max-Access: Read-only
The number of LE_REGISTER_REQUESTs received by this LANE server since activation.
Syntax: Counter32
Max-Access: Read-only
The number of rejection LE_REGISTER_RESPONSEs transmitted by this LANE server since activation.
Syntax: Counter32
Max-Access: Read-only
The cause for the transmission of the last rejection LE_REGISTER_RESPONSE. This variable has the value of the status field within the last failure register response. If the server has never issued a failed registration response, then the value of this object is 0.
Syntax: Integer32
Max-Access: Read-only
The ATM address of the client whose last LE_REGISTER_REQUEST to this LANE server resulted in failure. If the server has never issued a failed registration response, then the value of this object is all zeros--that is, 0x0000nnn and so on.
Syntax: AtmLaneAddress
Max-Access: Read-only
The number of valid LE_UNREGISTER_REQUESTs received by this LANE server since activation.
Syntax: Counter32
Max-Access: Read-only
The number of LE_ARP_REQUESTs received by this LANE server since activation and responded to directly. This number applies to all LE_ARP requests for addresses registered by LANE clients with the LANE server. A LANE server is not required to answer LE_ARP requests directly and may forward the request on to the Control Distribute virtual channel connection (VCC) regardless. This counter does not apply to those requests from the broadcast-and-unknown server (for example, the broadcast address).
Syntax: Counter32
Max-Access: Read-only
The number of LE_ARP requests received by the LANE server for the broadcast address. These requests are responded to with the broadcast-and-unknown server's ATM address.
Syntax: Counter32
Max-Access: Read-only
The number of LE_ARP_REQUEST frames forwarded onto the Control Distribute virtual channel connection (VCC).
Syntax: Counter32
Max-Access: Read-only
The number of LE_ARP_RESPONSEs received by this LANE server and forwarded onto the Control Distribute virtual channel connection (VCC).
Syntax: Counter32
Max-Access: Read-only
The number of negative LE_ARP requests received by this LANE server and forwarded on to the Control Distribute virtual channel connection (VCC).
Syntax: Counter32
Max-Access: Read-only
The number of LE_TOPOLOGY_REQUESTs received by this LANE server since activation.
Syntax: Counter32
Max-Access: Read-only
End of Table
A (conceptual) table listing the clients associated with a LANE server. The local or network management may not create rows in this table, but may only inspect or remove LANE clients that are currently joined with the LANE server.
Syntax: SEQUENCE OF LesClientEntry
Max-Access: Not-accessible
An entry (conceptual) row that denotes a client that is joined with the LANE server.
Syntax: LesClientEntry
Max-Access: Not-accessible
The LANE client ID selected for a LANE client by the LANE server during the JOIN phase.
Syntax: Integer (0001-65279) -- 0x0001 to 0xFFEF
Max-Access: Not-accessible
The primary ATM address associated with the designated LANE client.
Syntax: AtmLaneAddress
Max-Access: Read-only
The current state of the LANE client. The busConnect state is monitorable only if the broadcast-and-unknown server is colocated with the LANE server. If it is not, then the client state should proceed immediately to operational within this table (though it may not do so in actuality). No relation exists between the client's internal state and the state reflected here. The state here is only the LANE server's observed state of the LANE client.
Syntax: Integer 1 = connected, 2 = joinRecv, 3 = verify, 4 = addLec, 5 = busConnect, 6 = operational, 7 = terminating
Max-Access: Read-only
The interface of the bidirectional control direct connection between the LANE client and LANE server.
Syntax: Integer32
Max-Access: Read-only
The virtual path identifier (VPI) of the bidirectional control direct connection between the LANE client and LANE server.
Syntax: CiscoVpiInteger
Max-Access: Read-only
The virtual channel identifier (VCI) of the bidirectional control direct connection between the LANE client and LANE server.
Syntax: CiscoVciInteger
Max-Access: Read-only
The status of the (conceptual) row. This object may return only the active (1) state. The only value that may be written to this object is the destroy (6) state which causes the client to be dropped from the emulated LAN.
Syntax: RowStatus
Max-Access: Read-write
End of Table
A (conceptual) table of media access control (MAC) addresses registered with the LANE server by its clients.
Syntax: SEQUENCE OF LesMacRegEntry
Max-Access: Not-accessible
An entry (conceptual row) that denotes a registered media access control (MAC) address and the ATM address that corresponds to it.
Syntax: LesMacRegEntry
Max-Access: Not-accessible
The media access control (MAC) address of a registered client.
Syntax: MacAddress
Max-Access: Not-accessible
The ATM address of the LANE client that corresponds to the registered media access control (MAC) address.
Syntax: AtmLaneAddress
Max-Access: Read-only
The LANE client ID of the client who registered the designated media access control (MAC) address.
Syntax: Integer (0001-65279) (0x0001 to 0xFFEF)
Max-Access: Read-only
End of Table
The variables described in this section are used to manage modems in the Cisco AS5200 universal access server.
The number of modems that are currently installed within this system.
Syntax: Gauge32
Max-Access: Read-only
The number of modem groups that are currently configured within this system. The maximum value for this object is cmSystemInstalledModem.
Syntax: Gauge32
Max-Access: Read-only
A passive software watchdog timer value used to recover a modem that enters into an unexpected state and becomes suspended. When this watchdog timer times out, the modem-associated call processing state will be set back to IDLE, all related time-division multiplexing (TDM) paths are restored to default configurations, and all actions related to call processing stop for the modem.
Syntax: Integer32
Max-Access: Read-write
The ideal time interval between modem status polling via the out-of-band management port.
Syntax: Integer32 (2-60)
Max-Access: Read-write
The maximum number of retries executed when a reply event is not received for a message sent to the modem through the out-of-band management port. If an expected reply event is not received, the message is sent to the modem again.
Syntax: Integer32 (0-10)
Max-Access: Read-write
Table of descriptive and status information about the groups of modems.
Syntax: SEQUENCE OF CmGroupEntry
Max-Access: Not-accessible
An entry in the table, containing information about a single group of modems.
Syntax: CmGroupEntry
Max-Access: Not-accessible
The group containing the modems for which this entry contains information.
Syntax: Unsigned32
Max-Access: Not-accessible
The total number of modem devices that are configured in the group.
Syntax: Integer32
Max-Access: Read-only
Table of information about the modem members in modem groups.
Syntax: SEQUENCE OF CmGroupMemberEntry
Max-Access: Not-accessible
An entry in the table, containing information about modem members in a group. The modem groups are currently created when associated asynchronous interface groups are configured via the command line interface (CLI) command interface group-async and not via SNMP.
Syntax: CmGroupMemberEntry
Max-Access: Not-accessible
The slot number of the modem feature card in the group.
Syntax: Unsigned32
Max-Access: Not-accessible
The modem port number of a modem feature card in the group.
Syntax: Unsigned32
Max-Access: Read-only
End of Table
A collection of objects that describe the status of the modem.
Syntax: SEQUENCE OF CmLineStatusEntry
Max-Access: Not-accessible
An entry in the table, containing status information about a single modem.
Syntax: CmLineStatusEntry
Max-Access: Not-accessible
The interface that this modem is connected.
Syntax: InterfaceIndex
Max-Access: Read-only
The number of the modem group that the modem may be in.
Syntax: Integer32
Max-Access: Read-only
A textual description to identify the modem, including the manufacturer's name and type of modem.
Syntax: DisplayString (SIZE (0-79))
Max-Access: Read-only
A textual description of the modem, including hardware revision number, firmware revision number, feature set, and optionally, serial number.
Syntax: DisplayString (SIZE (0-79))
Max-Access: Read-only
Specifies whether this modem is a manageable modem. A manageable modem allows a device to be accessed through an out-of-band management port. Through this port, the modem statistics can be retrieved and a directly connected session can provide test and debugging ability. This object specifies whether this modem is a manageable modem.
Syntax: TruthValue
Max-Access: Read-only
Indicates the current state of modem. The meaning of each state code is explained below.
Integer of 1, 2, 3, 4, 5, 6, 7, 8, 9, or 10 representing a modem state as follows:
| 1 = unknown | The current state of the modem is unknown. |
| 2 = onHook: | The condition similar to that created when you hang up a telephone receiver. The call cannot enter a connected state when the modem is in onHook state. |
| 3 = offHook | Not connected. The condition similar to that created when you pick up a telephone receiver to dial or answer a call. |
| 4 = connected | The modem is in a state in which it can transmit or receive data over the communications line. |
| 5 = busiedOut | The modem is busied out (taken out of service) and cannot make outgoing calls or receive incoming calls. |
| 6 = disabled | The modem is in a reset state and is nonfunctional. This state can be set and cleared via the cmHoldReset. variable. |
| 7 = bad | The modem is suspected or proven to be inoperable. The operator can take the modem out of service and mark the modem as bad via the cmBad variable. |
| 8 = loopback | The modem is in a state in which it is currently running back-to-back loopback testing. |
| 9 = downloadFirmware | The modem is in a state in which it is currently downloading the firmware. |
| 10 = downloadFirmwareFailed | The modem is not operational because the downloading of firmware to it has failed. |
Max-Access: Read-only
Specifies the direction of the current or previous call. The modem can be used either for an incoming call or outgoing call.
Syntax: Integer, 1 = incoming, 2 = outgoing, 3 = none
Max-Access: Read-only
Indicates the reason that the last connection or call attempt disconnected. The meaning of each reason code is explained below.
Integer of 1, 2, 3, 4, 5, 6, 7, 8, 9, 10, 11, 12, 13, 14, 15, 16, 17, or 18 representing a reason for modem disconnection, as follows:
| 1 = unknown | The failure reason is unknown, or there has been no previous call. |
| 2 = lostCarrier | The call was disconnected because of the loss of carrier. |
| 3 = noCarrier | The dial-out attempt failed because the modem detected no carrier. |
| 4 = noDialTone | The dial-out attempt failed because the modem failed to detect a dial tone. |
| 5 = busy | The call attempt failed because the modem detected a busy signal. |
| 6 = modemWatchdogTimeout | The modem internal watchdog timer has expired. |
| 7 = dtrDrop | Data terminal ready (DTR) has been turned off while the modem is to disconnect on DTR drop. |
| 8 = userHangup | Normal disconnection occurred because the user hung up. |
| 9 = compressionProblem | The call was disconnected due to a problem detected during compression in the modem. |
| 10 = retrainFailure | The modem did not successfully train and reach data mode on the previous connections. |
| 11 = remoteLinkDisconnect | The remote link disconnected the connection. |
| 12 = abort | The call was abnormally terminated. |
| 13 = inactivityTimeout | The modem automatically hung up because data was not sent or received within the inactivity timeout period. |
| 14 = dialStringError | The dialed phone number was invalid. |
| 15 = linkFailure | The modem detected a link failure. |
| 16 = modulationError | The modem detected a modulation error. |
| 17 = dialTimeout | The modem timed-out while attempting to dial. |
| 18 = remoteHangup | The remote side hung up the connection. |
Max-Access: Read-only
Specifies the call duration of the current or previous call.
Syntax: TimeTicks
Max-Access: Read-only
The dialed outgoing telephone number of the current or previous call.
Syntax: DisplayString (SIZE (0-64))
Max-Access: Read-only
The incoming caller identification of the current or previous call.
Syntax: DisplayString (SIZE (0-64))
Max-Access: Read-only
The modem modulation scheme used in the current or previous call. This object exists only for manageable modems.
Syntax: Integer, 1 = unknown, 2 = bell103a, 3 = bell212a, 4 = v21, 5 = v22, 6 = v22bis, 7 = v32, 8 = v32bis, 9 = vfc, 10 = v34
Max-Access: Read-only
The modem protocol used in the current or previous call. This object exists only for manageable modems.
Syntax: Integer,1 = normal, 2 = direct, 3 = reliableMNP, 4 = reliableLAPM
Max-Access: Read-only
The speed of modem transmission for the current or previous call in bits per second. This object exists only for manageable modems.
Syntax: Gauge32
Max-Access: Read-only
The speed of modem reception for the current or previous call in bits per second. This object exists only for manageable modems.
Syntax: Gauge32
Max-Access: Read-only
The modem transmit analog signal level in the current or previous call in dBm. This object exists only for manageable modems.
Syntax: Integer32 (0 | -43 through -9)
Max-Access: Read-only
The modem receive analog signal level in the current or previous call in dBm. This object exists only for manageable modems.
Syntax: Integer32 (0 | -43 through -9)
Max-Access: Read-only
End of Table
A collection of objects that describe the configuration information of the modem.
Syntax: SEQUENCE OF CmLineConfigEntry
Max-Access: Not-accessible
An entry in the table, containing configuration information about a single modem.
Syntax: CmLineConfigEntry
Max-Access: Not-accessible
Specifies whether the directly connected session is permitted to be used at this modem.
When cmManageable = true, a directly connected session is used for test and debugging purpose via modem AT commands through the out-of-band management port.
Syntax: TruthValue
Max-Access: Read-write
Specifies whether this status polling feature is enabled at this modem.
When cmManageable = true, modem status and events can be polled through the out-of-band management port.
Syntax: TruthValue
Max-Access: Read-write
Puts a modem out of service, so that modem cannot make calls or answer calls. If the modem to be taken out of service is handling a call, the busyout action is taken after the current call is disconnected. After a modem is taken out of service, the following commands can be applied to it--clear modem, modem bad, copy modem, test modem back-to-back. This action is called a nice or graceful busyout.
The value of true (1) indicates that the busyout request has been issued to the modem, but the busyout could be pending. The management entity needs to query the cmState to see if the modem is successfully out of service. The value of false (2) indicates that the modem is not issued the busyout request.
Syntax: TruthValue
Max-Access: Read-write
Puts modem out of service, so that the modem cannot make calls or answer calls. The shutdown action brings the modem out of service immediately without waiting for the call to be ended normally. After a modem is shut down, the following commands can be applied to it--clear modem, modem bad, copy modem, test modem back-to-back. This action is called a hard busyout.
The value of true (1) indicates that the shutdown request has been issued to the modem. The value of false (2) indicates that no shutdown request has been issued to the modem.
Syntax: TruthValue
Max-Access: Read-write
Puts the modem into reset mode until an inverse command brings the modem out of reset mode. While in reset mode, this modem cannot be used and is nonfunctional.
This object is valid only when the modem is in an onHook, busiedOut, or disabled state. The value of true (1) attempts to put the modem in reset mode, the value of false (2) takes the modem out of reset.
Syntax: TruthValue
Max-Access: Read-write
Holds a modem out of service and marks the modem as suspected or proven to be inoperable. During the router start-up and initialization sequence, modem back-to-back tests mark failing modems as inoperable or bad. The management entity also can use this action to lock out a suspicious modem or unlock a modem for further debugging or test. Although this action can be accompanied by the reset action to put a modem out of service, this action does not perform the reset. A normally operable (good) modem can start handling calls again after it exits reset mode. However, an inoperable modem must be taken out of bad modem mode by the management entity before it can handle calls again.
This object is valid only when the modem is in an onHook or busiedOut state. The value of true (1) indicates the modem is suspected to be inoperable and its state is set to bad. The value of false (2) indicates the modem has not been suspected of being inoperable, or has been re-marked as good.
Syntax: TruthValue
Max-Access: Read-write
End of Table
A collection of objects that describe the status of the modem.
Syntax: SEQUENCE OF CmLineStatisticsEntry
Max-Access: Not-accessible
An entry in the table, containing status information about a single modem.
Syntax: CmLineStatisticsEntry
Max-Access: Not-accessible
A counter to count the number of incoming calls for which ringing was detected but that were not answered at this modem.
Syntax: Counter32
Max-Access: Read-only
A counter to count the number of incoming connection requests that this modem answered in which it could not train with the other data communications equipment (DCE). This object exists only for manageable modems.
Syntax: Counter32
Max-Access: Read-only
cmIncomingConnectionCompletions
A counter to count the number of incoming connection requests that this modem answered and successfully trained with the other data communications equipment (DCE). This object exists only for manageable modems.
Syntax: Counter32
Max-Access: Read-only
A counter to count the number of outgoing calls from this modem in which it successfully went off hook and dialed, but which it could not train with the other data communications equipment (DCE). This object exists only for manageable modems.
Syntax: Counter32
Max-Access: Read-only
cmOutgoingConnectionCompletions
A counter to count the number of outgoing calls from this modem that resulted in the modem's successfully training with the other data communications equipment (DCE). This object exists only for manageable modems.
Syntax: Counter32
Max-Access: Read-only
A counter to count the number of call attempts that failed because the modem did not go off hook, or because no dial tone was present.
Syntax: Counter32
Max-Access: Read-only
A counter to count the number of times the dial tone was expected but not received. This object exists only for manageable modems.
Syntax: Counter32
Max-Access: Read-only
A counter to count the number of times the dial timeout occurred. This object exists only for manageable modems.
Syntax: Counter32
Max-Access: Read-only
The number of times the call processing watchdog timer expired.
Syntax: Counter32
Max-Access: Read-only
The number of connections initially established at a modulation speed of 2400 bps or less. This object exists only for manageable modems.
Syntax: Counter32
Max-Access: Read-only
The number of connections initially established at a modulation speed of greater than 2400 bps and less than 14400 bps.This object exists only for manageable modems.
Syntax: Counter32
Max-Access: Read-only
The number of connections initially established at a modulation speed of greater than 14400 bps. This object exists only for manageable modems.
Syntax: Counter32
Max-Access: Read-only
A counter to count the number of times that the disconnection reason is no carrier. This object exists only for manageable modems.
Syntax: Counter32
Max-Access: Read-only
A counter to count the number of times that the disconnection reason is link failure. This object exists only for manageable modems.
Syntax: Counter32
Max-Access: Read-only
A counter to count the number of times that the out-of-band protocol error occurred.This object exists only for manageable modems.
Syntax: Counter32
Max-Access: Read-only
A counter to count the number of times that the out-of-band protocol time-out error occurred. This object exists only for manageable modems.
Syntax: Counter32
Max-Access: Read-only
End of Table
The variables described in this section apply to the Cisco Ping MIB definitions.
Provides a table of ping request entries. The ping group consists of a single table, the ciscoPingTable, and includes the ciscoPing entries described in this subsection.
Syntax: SEQUENCE OF CiscoPingEntry
Max-Access: Not-accessible
The address of the device to be pinged. An instance of this object cannot be created until the associated instance of ciscoPingProtocol is created. Once an instance of this object is created, its value cannot be changed.
Syntax: CiscoNetworkAddress
Max-Access: Read-Write
Provides a ping request entry. A management station choosing to create an entry should first generate a pseudo-random serial number to be used as the index to this sparse table. The station should then create the associated instance of the row status and row owner objects. It must also, either in the same or in successive protocol data units (PDUs), create the associated instance of the protocol and address objects. It should also modify the default values for the other configuration objects if the defaults are not appropriate.
Once the appropriate instance of all the configuration objects has 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 that this entire procedure can be initiated by means of a single set request which specifies a row status of createAndGo as well as specifies values for the non-defaulted configuration objects.
Once the ping sequence has been activated, it cannot be stopped; it will run until the configured number of packets have been sent.
Once the sequence completes, the management station should retrieve the values of the status objects of interest, and should then delete the entry. In order to prevent old entries from clogging the table, entries will be aged out, but an entry will never be deleted within 5 minutes of completing.
Syntax: CiscoPingEntry
Max-Access: Not-accessible
Specifies the protocol stack over which the ping packet is being sent. For Release 10.2, Cisco supports the SNMP ping over IP, IPX, AppleTalk, CLNS, DECnet, and VINES.
Syntax: Cisco Network Protocol
Max-Access: Read-Create
Specifies a unique entry in the ciscoPingTable. A management station choosing to initiate a ping operation should use a pseudo-random value for this object when creating or modifying an instance of a ciscoPingEntry. The RowStatus semantics of the ciscoPingEntryStatus object will prevent access conflicts.
Syntax: Integer32
Max-Access: Not-accessible
Specifies the number of ping packets to send to the target in this sequence.
Syntax: Integer32
Max-Access: Read-create
Specifies the size of ping packets to send to the target in this sequence. The lower and upper boundaries of this object are protocol-dependent. An instance of this object cannot be modified unless the associated instance of ciscoPingProtocol has been created (so as to allow protocol-specific range checking on the new value).
Syntax: Integer32
Max-Access: Read-create
Specifies the amount of time to wait for a response to a transmitted packet before declaring the packet dropped.
Syntax: Integer32
Max-Access: Read-create
Specifies the minimum amount of time to wait before sending the next packet in a sequence after receiving a response or declaring a timeout for a previous packet. The actual delay may be greater due to internal task scheduling.
Syntax: Integer32
Max-Access: Read-create
Specifies whether a ciscoPingCompletion trap should be issued on completion of the sequence of pings. If such a trap is sought, it is the responsibility of the management entity to ensure that the SNMP administrative model is configured in such a way as to allow the trap to be delivered.
Syntax: TruthValue
Max-Access: Read-create
Specifies the number of ping packets that have been sent to the target in this sequence.
Syntax: Counter32
Max-Access: Read-only
Specifies the number of ping packets that have been received from the target in this sequence.
Syntax: Counter32
Max-Access: Read-only
Specifies the minimum round trip time of all the packets sent in this sequence. This object will not be created until the first ping response in a sequence is received.
Syntax: Integer
Max-Access: Read-only
The average round trip time of all the packets sent in this sequence. This object will not be created until the first ping response in a sequence is received.
Syntax: Integer
Max-Access: Read-only
The maximum round trip time of all the packets sent in this sequence. This object will not be created until the first ping response in a sequence is received.
Syntax: Integer
Max-Access: Read-only
Specifies a setting of true when all the packets in this sequence have been answered or have timed out.
Syntax: TruthValue
Max-Access: Read-only
Specifies the entity that configured this device.
Syntax: OwnerString
Max-Access: Read-create
Specifies the status of this table entry. Once the entry status is set to active, the associate entry cannot be modified until the sequence is completed (in other words, ciscoPingCompleted is true).
Syntax: RowStatus
Max-Access: Read-create
End of Table
The variables described in this section allow a management station to display the attributes of the local-remote RSRB peer relationship for virtual rings, remote peers, and associated Token Rings.
This table contains configuration information for the virtual rings in the router.
Syntax: SEQUENCE OF RsrbVirtRingEntry
Max-Access: Not-accessible
The configured number of the virtual ring in which this peer is participating.
Syntax: Integer32
Max-Access: Not-accessible
The IP address configured for this RSRB local peer.
Syntax: IpAddress
Max-Access: Read-only
The maximum number of packets that can be held in any single outbound TCP queue to a remote peer before packets are discarded. This value indicates the configured or default value.
Syntax: Integer32
Max-Access: Read-only
End of Table
This table contains information about RSRB remote peers for a virtual ring.
Syntax: SEQUENCE OF RsrbRemotePeerEntry
Max-Access: Not-accessible
An arbitrary index that uniquely identifies a remote peer within a virtual ring.
Syntax: Integer32
Max-Access: Not-accessible
How traffic is encapsulated for RSRB:
tcp = IP datagrams over a TCP connection, serial = point-to-point (serial) direct encapsulation, lan = direct encapsulation over a LAN, fst = IP datagrams over a Fast Sequenced Transport connection, frameRelay = direct encapsulation over Frame Relay.
Syntax: Integer 1 = tcp, 2 = serial, 3 = lan, 4 = fst, 5 = frameRelay
Max-Access: Read-only
The IP address used by this RSRB remote peer. This field is meaningful only for TCP and FST encapsulation. For other encapsulation types 0.0.0.0 is returned.
Syntax: IpAddress
Max-Access: Read-only
The local interface index value to this RSRB remote peer. Same value as used for accessing the Interface MIB for the same interface. This field is meaningful only for serial, LAN, and Frame Relay encapsulation. For other encapsulation types 0 is returned.
Syntax: InterfaceIndex
Max-Access: Read-only
The current state of the RSRB session with this remote peer.
Syntax: Integer 1 = dead, 2 = closed, 3 = opening, 4 = openWaitXport, 5 = waitRemoteRsp, 6 = remoteResponded, 7 = remoteOpened, 8 = draining, 9 = connected
Max-Access: Read-only
The number of packets received from a remote peer.
Syntax: Counter32
Max-Access: Read-only
The number of packets transmitted to a remote peer.
Syntax: Counter32
Max-Access: Read-only
The number of bytes received from a remote peer.
Syntax: Counter32
Max-Access: Read-only
The number of bytes transmitted to a remote peer.
Syntax: Counter32
Max-Access: Read-only
The number of explorer packets received from a remote peer.
Syntax: Counter32
Max-Access: Read-only
The number of packets being held by the local router in the TCP output queue to this remote peer.
Syntax: Gauge32
Max-Access: Read-only
The number of received packets discarded by the local router. The reasons for packets being dropped include, but are not limited to, problems with the configuration, queue overflow, and protocol errors.
Syntax: Counter32
Max-Access: Read-only
Indicates whether local acknowledgment is used for the sessions going to the remote peer.
TRUE indicates that a local acknowledgment is used. FALSE indicates that a local acknowledgment is not used.
Syntax: TruthValue
Max-Access: Read-only
The version of RSRB used between local and remote peers. Generally peers can communicate if they are within one version of each other. The value returned is the lower version of the two peers.
Syntax: Integer32
Max-Access: Read-only
End of Table
This table contains information about local and remote rings associated with a virtual ring.
Syntax: SEQUENCE OF RsrbRingEntry
Max-Access: Not-accessible
The configured ring number that uniquely identifies this network segment or ring within the bridged Token Ring network.
Syntax: Integer32
Max-Access: Not-accessible
The configured number of the bridge that connects this entry's ring to the virtual ring.
Syntax: Integer32
Max-Access: Read-only
Indicates whether the entry represents a local or remote ring. TRUE indicates a local ring. FALSE indicates a remote ring.
Syntax: TruthValue
Max-Access: Read-only
The ring type.
Syntax: Integer 1 = static (statically defined ring) 2 = dynamic (dynamically discovered ring) 3 = sdllc (SDLLC virtual ring)
4 = qllc (QLLC virtual ring)
5 = virtual ring (local only)
Max-Access: Read-only
The media access control (MAC) address of either the local router's interface to the ring for local ring entries, or the remote peer's interface to the ring for remote ring entries. Not valid for entry types sdllc and qllc, for these types "00 00 00 00 00 00" will be returned.
Syntax: MacAddress
Max-Access: Read-only
For local ring entries, the local interface into the ring. This is the same value used for accessing the Interface MIB for the same interface. Not meaningful for remote ring entries, for these types 0 will be returned.
Syntax: InterfaceIndex
Max-Access: Read-only
For remote ring entries, the IP address of the remote RSRB peer. Not meaningful for local ring entries, for these, 0.0.0.0 will be returned.
Syntax: IpAddress
Max-Access: Read-only
The number of packets forwarded by the local router onto this ring.
Syntax: Counter32
Max-Access: Read-only
End of Table
The following notification is supported with the RSRB MIB:
rsrbPeerStateChangeNotification
This trap indicates that the state of an RSRB remote peer has transitioned to active (connected) or inactive (dead or closed).
The Cisco Repeater group specifies proprietary MIB extensions to RFC 1516. These extensions support the standard repeater (hub), including the Cisco 2516; features such as link-test, auto-polarity, and source-address control; and the MDI/MDI-X switch status.
Table of descriptive and status information about the ports.
Syntax: SEQUENCE OF CiscoRptrPortEntry
Max-Access: Not-accessible
An entry in the table, containing information about a single port.
Syntax: CiscoRptrPortEntry
Max-Access: Not-accessible
Specifies the port's MDI/MDI-X switching status. The crossover(2) status indicates the port is configured to be in MDI-X mode (crossover function is enabled to allow for connection to a chained hub). The normal(1) status indicates the port is configured to be standard MDI as defined by the 10BaseT Standard. The notSwitchable(3) status indicates the port is not switchable between MDI and MDI-X mode.
Syntax: Integer 1 = normal, 2 = crossover, 3 = notSwitchable
Max-Access: Read-only
Specifies whether the Link Integrity Test function is enabled for the port as specified by the 10BaseT Standard. When the link-test function is enabled, the absence of the link-test pulses and receive data on the port will cause the port to go into a link fail state. In this state, the data transmission, data reception, and collision detection functions are disabled until valid data or four consecutive link test pulses appear on RXD+/- pair of the port. With the Link Integrity Test function disabled, the data driver, receiver, and collision detection remain enabled regardless of the presence or absence of data or Link Test pulses on the port.
Syntax: TruthValue
Max-Access: Read-write
Specifies the status of the Link Test function for the port. False indicates valid data or that four consecutive Link Test pulses have been detected on the port. True indicates the failure of the link test function for the port. In the link test fail state, data transmission, data reception, and collision detection functions are disabled until valid data or four consecutive link test pulses appear on the RXD+/- pair of the port.
Syntax: TruthValue
Max-Access: Read-only
ciscoRptrPortAutoPolarityEnabled
Specifies whether the Automatic Receiver Polarity Reversal is enabled for the port. This feature provides the ability to invert the polarity of the signals appearing at the RXD+/- pair of the port prior to retransmission if the polarity of the received signal is reversed (such as in the case of wiring error).
Syntax: TruthValue
Max-Access: Read-write
ciscoRptrPortAutoPolarityCorrected
Specifies the status of the Automatic Receiver Polarity Reversal for the port. True indicates that the polarity of the port has been detected as reversed and is corrected. False indicates that the polarity for the port has correct polarity.
Syntax: TruthValue
Max-Access: Read-only
Specifies whether the source address control feature is enabled for the port. This feature provides the ability to control which device's specific media access control (MAC) address is allowed access to the network. If the management entity specified an address via ciscoRptrPortAllowedSrcAddr, only the device with the configured MAC address is allowed access to the network. If the management entity does not specified an address, the allowed source address is learned from the last source address if valid; otherwise, the allowed source address is learned from the MAC address of the first valid packet detected on the port. When another MAC address other than the allowed source address is detected on the port, the port is partitioned.
Syntax: TruthValue
Max-Access: Read-write
For write access, this object specifies the allowed source address that is to be configured for source address control feature for the port. For read access, if no allowed source address was specified by the manager, the agent will return the learned address to control. Otherwise, the specified allowed source address is returned if configured by the management entity.
Syntax: Octet string (SIZE (0 | 6))
Max-Access: Read-write
ciscoRptrPortAllowedSrcAddrStatus
Specifies the status of ciscoRptrPortAllowedSrcAddr for the port. allowedSrcAddrConfig(1) status indicates that the allowed source address was explicitly configured by management entity. The allowedSrcAddrLearn(2) status indicates that the allowed source address was learned for the port. The allowedSrcAddrUndefined(3) status indicates that currently there is no restriction on the source address for the port.
Syntax: Integer 1 = allowedSrcAddrConfig, 2 = allowedSrcAddrLearn, 3 = allowedSrcAddrUndefined
Max-Access: Read-only
ciscoRptrPortLastIllegalSrcAddr
Specifies the last illegal source address that caused this port to be partitioned. If the port is never partitioned due to source address control, the agent returns a string of length zero.
Syntax: Octet string (SIZE (0 | 6))
Max-Access: Read-only
ciscoRptrPortIllegalAddrTrapAcked
Specifies whether an acknowledgment is sent by a network management system (NMS) to indicate that an illegal source address trap was received.
Integer of 1, 2, or 3 representing transmisson or nontransmission of an acknowledgement:
| 1 = acked | Set by an NMS to acknowledge reception of an illegal source address. When this flag is set, no more traps are sent for the port. |
| 2 = no-acked-sending | Set by the Simple Network Management Protocol (SNMP) agent to indicate that it is sending a trap to one or more NMSs. The trap is sent based upon the trap algorithm specified by ciscoRptrTrapAlgorithm. |
| 3 = no-acked-no-sending | Set by the SNMP agent when there is no trap to be sent or if the trap was already sent out. |
Max-Access: Read-write
ciscoRptrPortIllegalAddrTrapEnabled
Specifies whether or not to send the illegal source address trap for the port.
When this variable is enabled, one or more illegal source address traps are generated if there is a mismatch of source address. Traps are sent based on the algorithm specified by ciscoRptrTrapAlgorithm defined in the GLOBAL section.
When this variable is disabled, no traps are sent.
Syntax: TruthValue
Max-Access: Read-write
ciscoRptrPortIllegalAddrFirstHeard
The timestamp for the very first time that the current illegal source address was detected on the port. The timestamp is given by the value of MIB-II sysUpTime at which this occurence happens. If no illegal source address is detected on the port, this value is set to 0.
Syntax: TimeStamp
Max-Access: Read-only
ciscoRptrPortIllegalAddrLastHeard
The timestamp for the last time that the current illegal source address was detected on the port. The timestamp is given by the value of MIB-II sysUpTime at which this occurence happens. If no illegal source address occurred, this value is set to 0.
Syntax: TimeStamp
Max-Access: Read-only
ciscoRptrPortLastIllegalAddrCount
The count of consecutive occurences of the last illegal source address on the port. When an illegal address is detected, this count is incremented approximately every minute.
Syntax: Gauge32
Max-Access: Read-only
ciscoRptrPortIllegalAddrTotalCount
The total count of all occurrences of any illegal source addresses detected on the port since startup.
Syntax: Counter32
Max-Access: Read-only
End of Table
Specifies how often traps are sent by the Simple Network Management Protocol (SNMP) agent: once means that the trap is sent once; decay means that the same trap is sent multiple times, at an approximate exponentially decaying rate. For example, the first trap is sent immediately, the second trap is sent at 2 minutes, the third trap is sent at 4 minutes, and so on. The rate is capped at 32 minutes.
Syntax: Integer 1 = once, 2 = decay
Max-Access: Read-write
When the illegal media access control (MAC) source address violation is detected, the port is partitioned for 1 minute. In addition, this trap notification is generated. Note that rptrPortGroupIndex, and rptrPortIndex are the instances of ciscoRptrPortLastIllegalSrcAddr.
The variables described in this section provide configuration and operational information for Round Trip Time (RTT) monitoring of a list of targets, using a variety of protocols.
RTT monitoring application version string.
The format is: version.release.patch-level: textual-description--for example, 1.0.0: Initial RTT Application.
Syntax: DisplayString
Max-Access: Read-only
The maximum size of the data portion an echo packet supported by this RTT application. This value is the maximum that can be specified by the sum of the Asymmetric Request/Response (ARR) header and either rttMonEchoAdminPktDataRequestSize or rttMonEchoAdminPktDataResponseSize in the rttMonCtrlAdminTable.
This object is undefined for conceptual RTT control rows when the RttMonRttType object is set to fileIO or script.
Syntax: Integer (0-16384)
Max-Access: Read-only
The last time at which a set operation occurred on any of the objects in this MIB. The managing application can inspect this value to determine whether changes have been made without retrieving the entire administration portion of this MIB.
This object applies to all settable objects in this MIB, including the Reset objects that could clear saved history or statistics.
Syntax: TimeStamp
Max-Access: Read-only
The maximum number of entries that can be added to the rttMonCtrlAdminTable.
Syntax: Integer32 (1-256)
Max-Access: Read-only
When this variable is set to reset, the entire RTT application goes through a reset sequence, making a best effort to revert to its startup condition. All rows in the Overall Control Group are immediately deleted, together with any associated rows in the Statistics Collection Group, and History Collection Group. All open connections are also closed. Finally, the rttMonApplPreConfigedTable is reset (see rttMonApplPreConfigedReset).
Syntax: RttReset
Max-Access: Read-write
When this variable is set to reset, the RTT application resets the Application Preconfigured MIB section.
This action forces the RTT application to delete all entries in the rttMonApplPreConfigedTable and then to repopulate the table with the current configuration.
This object provides a mechanism to load and unload user scripts and file paths.
Syntax: RttReset
Max-Access: Read-write
A table that contains the supported RTT Monitor Types. See the RttMonRttType textual convention for the definition of each type.
Syntax: SEQUENCE OF RttMonApplSupportedRttTypesEntry
Max-Access: Not-accessible
rttMonApplSupportedRttTypesEntry
A list that presents the valid RTT monitor types.
Syntax: RttMonApplSupportedRttTypesEntry
Max-Access: Not-accessible
This object indexes the supported RttMonRttType types.
Syntax: RttMonRttType
Max-Access: Not-accessible
rttMonApplSupportedRttTypesValid
This object defines the supported RttMonRttType types.
Syntax: TruthValue
Max-Access: Read-only
End of Table
A table that contains the supported RTT monitoring protocols. See the RttMonProtocol textual convention under "Syntax" in the "Terminology" section of the "Overview" chapter for the definition of each protocol.
Syntax: SEQUENCE OF RttMonApplSupportedProtocolsEntry
Max-Access: Not-accessible
rttMonApplSupportedProtocolsEntry
A list that presents the valid RTT monitoring protocols.
Syntax: RttMonApplSupportedProtocolsEntry
Max-Access: Not-accessible
This object indexes the supported RttMonProtocol protocols.
Syntax: RttMonProtocol
Max-Access: Not-accessible
rttMonApplSupportedProtocolsValid
This object defines the supported RttMonProtocol protocols.
Syntax: TruthValue
Max-Access: Read-only
End of Table
A table that contains the previously configured script names and file I/O targets.
These script names and file I/O targets are installed via a mechanism different from the RTT application, and are specific to each platform.
Syntax: SEQUENCE OF RttMonApplPreConfigedEntry
Max-Access: Not-accessible
A list of objects that describe the previously configured script names and file I/O targets.
Syntax: RttMonApplPreConfigedEntry
Max-Access: Not-accessible
The type of value being stored in the rttMonApplPreConfigedName object.
Syntax: Integer, 1 = filePath, 2 = scriptName
Max-Access: Not-accessible
One of the following, depending on the value of the rttMonApplPreConfigedType object:
Syntax: DisplayString (SIZE(0-255))
Max-Access: Not-accessible
When this row exists, this value is true. This object exists only to create a valid row in this table.
Syntax: TruthValue
Max-Access: Read-only
End of Table
A table of RTT monitoring definitions.
The RTT administration control is in multiple tables. This first table is used to create a conceptual RTT control row. The following tables contain objects that configure scheduling, information gathering, and notification and trigger generation. All tables create the same conceptual RTT control row as this table using this table's index as their own index.
This table is limited in size by the agent implementation. The object rttMonApplNumCtrlAdminEntry reflects this table's maximum number of entries.
Syntax: SEQUENCE OF RttMonCtrlAdminEntry
Max-Access: Not-accessible
A base list of objects that define a conceptual RTT control row.
Syntax: RttMonCtrlAdminEntry
Max-Access: Not-accessible
Uniquely identifies a row in the rttMonCtrlAdminTable.
This is a pseudorandom number selected by the management station for creating a row via the rttMonCtrlAdminStatus object. If the pseudorandom number is already in use, an inconsistentValue return code is returned when the createAndGo or createAndWait set operation is attempted on the rttMonCtrlAdminStatus object.
Syntax: Integer32 (1-2147483647)
Max-Access: Not-accessible
Identifies the entity that created this table row. See the OwnerString textual convention under "Syntax" in the "Terminology" section of the "Overview" chapter for further details.
Syntax: OwnerString
Max-Access: Read-create
A string used by a managing application to identify the RTT target. This string is inserted into notifications, but has no other significance to the agent.
Syntax: DisplayString (SIZE (0-16))
Max-Access: Read-create
The type of RTT operation to be performed. This value must be set in the same protocol data unit (PDU) or before any type-specific configuration is set. The default value is echo.
Syntax: RttMonRttType
Max-Access: Read-create
See rttMonReactAdminThresholdType and rttMonHistoryAdminFilter for this object's definition and usage. The default value is 5000.
Syntax: Integer32 (0-2147483647)
Max-Access: Read-create
Specifies the duration, in seconds, between the initiation of each RTT operation.
This object cannot be set to a value that specifies a shorter duration than rttMonCtrlAdminTimeout.
When the RttMonRttType specifies a synchronous operation, the next RTT operation might be blocked by an RTT operation that has not yet completed. In this case, the value of the rttMonStatsCollectBusies counter in rttMonStatsCaptureTable is incremented instead, and the next RTT operation that is attempted occurs at the next rttMonCtrlAdminFrequency expiration. This behavior occurs, for example, when the RttMonRttType is echo and the RttMonProtocol is snaLU0EchoAppl.
When the rttMonCtrlAdminRttType object is defined to be pathEcho, the suggested value for this object is greater than rttMonCtrlAdminTimeout value times the maximum number of expected hops to the target. The default value is 60.
Syntax: Integer32 (0-604800)
Max-Access: Read-create
Specifies the duration to wait for an RTT operation completion. The value of this object cannot be set to a value that would specify a duration exceeding rttMonCtrlAdminFrequency. The default value is 5000.
Syntax: Integer32 (0-604800000)
Max-Access: Read-create
When set to true, the resulting data in each RTT operation is compared with the expected data. This comparison includes checking header information (if possible) and exact packet size. Any mismatch is recorded in the rttMonStatsCollectVerifyErrors object.
Some RttMonRttTypes may not support this option. When a type does not support this option, the agent sets this object to false. The management application must check for this transition to false.
Syntax: TruthValue
Max-Access: Read-create
The status of the conceptual RTT control row.
For this object to become active, the following row objects must be defined:
All other objects can assume default values. A default conceptual RTT control row will be placed into a pending state via the rttMonCtrlOperState object.
Most conceptual RTT control row objects cannot be modified once this conceptual RTT control row has been created. The objects that can change are the following:
Once this object is in active status, it cannot be set to notInService while the rttMonCtrlOperState is in active state. Thus the rttMonCtrlOperState object must be changed first.
This object can be set to destroy from any value at any time. The default value is createAndGo.
Syntax: RowStatus
Max-Access: Read-create
End of Table
A table of RTT monitoring echo and pathEcho specific definitions.
When the RttMonRttType is not echo or pathEcho, this table is not valid.
This table is controlled via the rttMonCtrlAdminTable. Entries in this table are created via the rttMonCtrlAdminStatus object.
Syntax: SEQUENCE OF RttMonEchoAdminEntry
Max-Access: Not-accessible
A list of objects that define specific configuration for echo and pathEcho RttMonRttType conceptual RTT control rows.
Syntax: RttMonEchoAdminEntry
Max-Access: Not-accessible
Specifies the protocol to be used to perform the timed echo or pathEcho request/response.
If the RttMonRttType is set to echo or pathEcho when this protocol does not support the type, a badValue error is returned. The default value is notApplicable.
Syntax: RttMonProtocol
Max-Access: Read-create
A string that specifies the address of the target for an RTT echo or pathEcho operation.
Syntax: RttMonTargetAddress
Max-Access: Read-create
rttMonEchoAdminPktDataRequestSize
The number of octets to be placed into the Asymmetric Response/Request (ARR) data portion of the request message, when using an "Appl" suffixed rttMonEchoAdminProtocol (ARR supported protocol).
For non-ARR protocols RTT request/response, this value represents the native payload size, if supported. The default value is 1.
Syntax: Integer32 (0-16384)
Max-Access: Read-create
rttMonEchoAdminPktDataResponseSize
The number of octets to be placed into the Asymmetric Response/Request (ARR) data portion of the response message. This value is passed to the RTT echo server via a field in the ARR header.
For a non-ARR RTT request/response--for example, an IP Internet Control Message Protocol (ICMP) echo (ipIcmpecho)--this agent forces this value to match the value of rttMonEchoAdminPktDataRequestSize, if native payloads are supported. The default value is 0.
Syntax: Integer32 (0-16384)
Max-Access: Read-create
End of Table
A table of RTT monitoring fileIO specific definitions.
When the RttMonRttType is not fileIO this table is not valid.
This table is controlled via the rttMonCtrlAdminTable. Entries in this table are created via the rttMonCtrlAdminStatus object.
Syntax: SEQUENCE OF RttMonFileIOAdminEntry
Max-Access: Not-accessible
A list of objects that define specific configuration for fileIO RttMonRttType conceptual RTT control rows.
Syntax: RttMonFileIOAdminEntry
Max-Access: Not-accessible
The fully qualified file path that is the target of the RTT monitoring operation.
This value must match one of the rttMonApplPreConfigedName entries.
Syntax: DisplayString (SIZE(0-255))
Max-Access: Read-create
The size of the file to write or read from the file server. The default value is n256.
Syntax: Integer, 1 = n256, 2 = n1k, 3 = n64k, 4 = n128k, 5 = n256k
Max-Access: Read-create
The file I/O action to be performed. The default value is read.
Syntax: Integer, 1 = write, 2 = read, 3 = writeRead
Max-Access: Read-create
End of Table
A table of RTT monitoring script specific definitions.
When the RttMonRttType is not script this table is not valid.
This table is controlled via the rttMonCtrlAdminTable. Entries in this table are created via the rttMonCtrlAdminStatus object.
Syntax: SEQUENCE OF RttMonScriptAdminEntry
Max-Access: Not-accessible
A list of objects that define specific configuration for the script RttMonRttType conceptual RTT control rows.
Syntax: RttMonScriptAdminEntry
Max-Access: Not-accessible
The name of the script that is used to generate RTT operations.
This object must match one of the rttMonApplPreConfigedName entries.
Syntax: DisplayString (SIZE(0-255))
Max-Access: Read-create
rttMonScriptAdminCmdLineParams
The command line parameters passed to the rttMonScriptAdminName object when it is being executed.
Syntax: DisplayString (SIZE(0-255))
Max-Access: Read-create
End of Table
A table of RTT monitoring definitions for scheduling.
This table is controlled via the rttMonCtrlAdminTable. Entries in this table are created via the rttMonCtrlAdminStatus object.
Syntax: SEQUENCE OF RttMonScheduleAdminEntry
Max-Access: Not-accessible
A list of objects that define specific configuration for the scheduling of RTT operations.
Syntax: RttMonScheduleAdminEntry
Max-Access: Not-accessible
This object value is placed into the rttMonCtrlOperRttLife object when the rttMonCtrlOperState object changes to active or pending.
The value 2147483647 has a special meaning. When this object is set to 2147483647, the rttMonCtrlOperRttLife object will not decrement, thus the lifetime will never end. The default value is 3600.
Syntax: Integer32 (0-2147483647)
Max-Access: Read-create
rttMonScheduleAdminRttStartTime
The time when this conceptional row activates.
This is the value of MIB-II's sysUpTime in the future. When sysUpTime equals this value this object causes the activation of this conceptual row.
If an agent can determine the date and time, the agent can store this object as DateAndTime. This allows the agent to completely reset (restart) and still be able to start conceptual RTT rows at the intended time. However, if the agent cannot store the date and time and the agent resets, all entries must take on one of the special values defined below.
The first special value allows this conceptual RTT control row to immediately change the rttMonCtrlOperState object into active state when the rttMonCtrlAdminStatus object transitions to active. This special value is defined to be a value of this object that, when initially set, is 1.
The second special value allows this conceptual RTT control row to immediately change the rttMonCtrlOperState object into pending state when the rttMonCtrlAdminStatus object transitions to active. Also, when the rttMonCtrlOperRttLife object counts down to zero (not when set to zero), this special value causes this conceptual RTT control row to retransition the rttMonCtrlOperState object into pending state. This special value is defined to be a value of this object that, when initially set, is smaller than the current sysUpTime (with the exception of 1, as defined earlier). The default value is 0.
Syntax: TimeTicks
Max-Access: Read-create
rttMonScheduleAdminConceptRowAgeout
The amount of time this conceptual RTT control row exists when not in an active rttMonCtrlOperState.
When this conceptual RTT control row enters an active state, this timer is reset and suspended. When the row enters a state other than active, the timer is restarted.
When this value is set to zero, this entry will never age out. The default value is 3600.
Syntax: Integer32 (0-2073600)
Max-Access: Read-create
End of Table
A table of RTT monitoring notification and trigger definitions.
All notifications and reactions are applied to all RTT end-to-end operations. For this reason, they do not apply to hops along a path to the target, when RttMonRttType is pathEcho.
The format and content of SNA network management vector transport (NMVT) messages are not defined within this module.
However, Alert NMVT messages and traps are sent when an abnormal condition occurs--that is, when the rttMonCtrlOperConnectionLostOccurred, rttMonCtrlOperTimeoutOccurred, or rttMonCtrlOperOverThresholdOccurred object is changed to true. Moreover, resolution NMVT messages and traps are sent when that condition clears, and the rttMonCtrlOperConnectionLostOccurred, rttMonCtrlOperTimeoutOccurred, or rttMonCtrlOperOverThresholdOccurred object is changed back to false.
When rttMonReactAdminActionType is set to one of the following, the corresponding rows in the rttMonReactTriggerAdminTable defined via the rttMonCtrlAdminIndex become active:
This table augments the rttMonCtrlAdminTable.
Syntax: SEQUENCE OF RttMonReactAdminEntry
Max-Access: Not-accessible
A list of objects that define RTT reaction operations.
Syntax: RttMonReactAdminEntry
Max-Access: Not-accessible
rttMonReactAdminConnectionEnable
This object is valid only when the RttMonRttType is either echo or pathEcho.
If true, a reaction is generated when an RTT operation to a rttMonEchoAdminTargetAddress (echo type) causes rttMonCtrlOperConnectionLostOccurred to change its value. Thus connections to intermediate hops do not cause this value to change.
Syntax: TruthValue
Max-Access: Read-create
This object applies to all RttMonRttTypes.
If true, a reaction is generated when an RTT operation causes rttMonCtrlOperTimeoutOccurred to change its value.
When the RttMonRttType is pathEcho, timeouts to intermediate hops do not cause rttMonCtrlOperTimeoutOccurred to change its value.
Syntax: TruthValue
Max-Access: Read-create
This object applies to all RttMonRttTypes.
This object specifies the conditions under which rttMonCtrlOperOverThresholdOccurred is changed. The default value is never.
Syntax: Integer of 1, 2, 3, 4, or 5 representing conditions under which the variable that indicates whether threshold values were exceeded are set:
| 1 = never | rttMonCtrlOperOverThresholdOccurred is never set. |
| 2 = immediate | rttMonCtrlOperOverThresholdOccurred is set to true when an operation completion time exceeds rttMonCtrlAdminThreshold; conversely, rttMonCtrlOperOverThresholdOccurred is set to false when an operation completion time falls below rttMonReactAdminThresholdFalling. |
| 3 = consecutive | rttMonCtrlOperOverThresholdOccurred is set to true when an operation completion time exceeds rttMonCtrlAdminThreshold on rttMonReactAdminThresholdCount consecutive RTT operations; conversely, rttMonCtrlOperOverThresholdOccurred is set to false when an operation completion times fall under the rttMonReactAdminThresholdFalling for the same number of consecutive operations |
| 4 = xOfy | rttMonCtrlOperOverThresholdOccurred is set to true when x (as specified by rttMonReactAdminThresholdCount) out of the last y (as specified by frttMonReactAdminThresholdCount2) operation completion times exceed rttMonCtrlAdminThreshold; conversely, it is set to false when x out of the last y operation completion time falls below rttMonReactAdminThresholdFalling.
When the value of x is greater than y, the probe never generates a reaction. |
| 5 = average | rttMonCtrlOperOverThresholdOccurred is set to true when the running average of the previous rttMonReactAdminThresholdCount operation completion times exceeds rttMonCtrlAdminThreshold; conversely, it is set to false when the running average falls below rttMonReactAdminThresholdFalling. |
If this type value is changed by a management station, rttMonCtrlOperOverThresholdOccurred is set to false, but no reaction is generated if the prior value of rttMonCtrlOperOverThresholdOccurred was true.
Max-Access: Read-create
rttMonReactAdminThresholdFalling
See rttMonReactAdminThresholdType for more information. The default value is 3000.
Syntax: Integer32 (0-2147483647)
Max-Access: Read-create
rttMonReactAdminThresholdCount
See rttMonReactAdminThresholdType for more information. The default value is 5.
Syntax: Integer32 (1-16)
Max-Access: Read-create
rttMonReactAdminThresholdCount2
See rttMonReactAdminThresholdType for more information. The default value is 5.
Syntax: Integer32 (1-16)
Max-Access: Read-create
Specifies what reaction or reactions, if any, to generate if an operation violates one of the watched conditions. The default value is none.
Integer of 1, 2, 3, 4, 5, 6, 7, or 8 representing types of system response to an operation violation, as follows:
| 1 = none | No reaction is generated. |
| 2 = trapOnly | A trap is generated. |
| 3 = nmvtOnly | An SNA network management vector transport (NMVT) is generated. |
| 4 = triggerOnly | All trigger actions defined for this entry are initiated. |
| 5 = trapAndNmvt | Both a trap and an SNA NMVT are generated. |
| 6 = trapAndTrigger | Both a trap and all trigger actions are initiated. |
| 7 = nmvtAndTrigger | Both an NMVT and all trigger actions are initiated. |
| 8 = trapNmvtAndTrigger | An NMVT, trap, and all trigger actions are initiated. |
A trigger action is defined via the rttMonReactTriggerAdminTable.
Max-Access: Read-create
End of Table
A table of RTT monitoring statistics definitions.
The definitions in this table control the type and number of entries that are placed into the rttMonStatsCaptureTable.
The statistics capture table is a rollover table. When the rttMonStatisticsAdminNumHourGroups index value exceeds its value defined in this table, the oldest corresponding group will be deleted and is replaced with the new group. All other indices will only fill to their maximum size.
This table augments the rttMonCtrlAdminTable.
Syntax: SEQUENCE OF RttMonStatisticsAdminEntry
Max-Access: Not-accessible
A list of objects that define RTT statistics capture operations.
Syntax: RttMonStatisticsAdminEntry
Max-Access: Not-accessible
rttMonStatisticsAdminNumHourGroups
The maximum number of hourly groups of paths to record before rolling over.
The value of 1 is not advisable because the group will close and immediately be deleted before the network management station can retrieve the statistics.
The value used in the rttMonStatsCaptureTable to uniquely identify this group is the rttMonStatsCaptureStartTimeIndex.
When this object is set to the value of zero, all rttMonStatsCaptureTable data capturing is shut off.
If the value of rttMonStatisticsAdminNumHourGroups is larger than the RTT application can support, this value is set to the maximum value for the application. The default value is 2.
Syntax: Integer32 (0-512)
Max-Access: Read-create
When RttMonRttType is pathEcho this variable is the maximum number of statistics paths to record per hourly group. This value directly represents the path to a target. For all other RttMonRttTypes this value will be forced to 1 by the agent.
Because this index does not roll over, only the first rttMonStatisticsAdminNumPaths are kept.
If the value of rttMonStatisticsAdminNumPaths is larger than the RTT application can support, the agent sets this value to the maximum value for the application. The default value is 5.
Syntax: Integer32 (1-128)
Max-Access: Read-create
When RttMonRttType is pathEcho this variable is the maximum number of statistics hops to record per path group. Because this value directly represents the number of hops along a path to a target, we can support only 512 hops. For all other RttMonRttTypes, the agent forces this value to 1.
Because this index does not roll over, only the first rttMonStatisticsAdminNumHops value is kept.
If the value of rttMonStatisticsAdminNumHops is larger than the RTT application can support, the agent sets this value to the maximum value for the application. The default value is 16.
Syntax: Integer32 (1-512)
Max-Access: Read-create
rttMonStatisticsAdminNumDistBuckets
The maximum number of statistical distribution accumulation fields, or buckets, to accumulate.
Because this index does not roll over, only the first rttMonStatisticsAdminNumDistBuckets value is kept.
The last rttMonStatisticsAdminNumDistBucket contains all entries from its distribution interval start point to infinity.
If the value of rttMonStatisticsAdminNumDistBuckets is larger than the RTT application can support, the agent sets this value to the maximum value for the application. The default value is 1.
Syntax: Integer32 (1-512)
Max-Access: Read-create
rttMonStatisticsAdminDistInterval
The statistical distribution buckets interval used when the value of rttMonStatisticsAdminNumDistBuckets is greater than 1.
rttMonStatisticsAdminNumDistBuckets = 5 buckets
rttMonStatisticsAdminDistInterval = 10 milliseconds
| Bucket 1 | Bucket 2 | Bucket 3 | Bucket 4 | Bucket 5 | | 0-9 ms | 10-19 ms | 20-29 ms | 30-39 ms | 40-Inf ms |
rttMonStatisticsAdminNumDistBuckets = 1 buckets
rttMonStatisticsAdminDistInterval = 10 milliseconds
| Bucket 1 | | 0-Inf ms |
This odd example shows that the value of rttMonStatisticsAdminDistInterval does not apply when the value of rttMonStatisticsAdminNumDistBuckets is 1. The default value is 20.
Syntax: Integer32 (1-100)
Max-Access: Read-create
End of Table
A table of RTT monitoring history definitions.
The definitions in this table control the types and number of entries that are placed into the rttMonHistoryCollectionTable.
The history collection table is a rollover table. When the rttMonHistoryAdminNumLives index value exceeds its value defined in this table, the oldest corresponding lives group is deleted and is replaced with the new lives group. All other indices will only fill to their maximum size.
This table augments the rttMonCtrlAdminTable.
Syntax: SEQUENCE OF RttMonHistoryAdminEntry
Max-Access: Not-accessible
A list of objects that define history collection for RTT operations.
Syntax: RttMonHistoryAdminEntry
Max-Access: Not-accessible
The maximum number of history "lives" to record. A life is the amount of time during which an RTT monitoring conceptual row can conduct operations, and is defined by the countdown (or transition) to zero by the rttMonCtrlOperRttLife object. A new life is created when the same conceptual RTT control row is restarted via the transition of the rttMonCtrlOperRttLife object and its subsequent countdown.
The value of zero shuts off all rttMonHistoryAdminTable data collection.
If the value of rttMonHistoryAdminNumLives is larger than the RTT application can support, the agent sets this value to the maximum value. The default value is 0.
Syntax: Integer32 (0-255)
Max-Access: Read-create
The maximum number of history buckets to record. When the RttMonRttType is pathEcho, this value directly represents a path to a target. For all other RttMonRttTypes this value should be set to 1.
Because this index does not roll over, only the first rttMonHistoryAdminNumBuckets is kept per life.
If the value of rttMonHistoryAdminNumBuckets is larger than the RTT application can support, the agent sets this value to the maximum value. The default value is 50.
Syntax: Integer32 (1-2147483647)
Max-Access: Read-create
The maximum number of history samples to record per bucket. When the RttMonRttType is pathEcho, this value directly represents the number of hops along a path to a target. For this reason, we can support only 512 hops. For all other RttMonRttTypes the agent forces this value to 1.
If the value of rttMonHistoryAdminNumSamples is larger than the RTT application can support, the agent sets this value to the maximum value. The default value is 16.
Syntax: Integer32 (1-512)
Max-Access: Read-create
Defines a filter for adding RTT results to the history buffer. The default value is none.
Integer of 1, 2, 3, or 4 representing which results of operations to record, as follows:
| 1 = none | No history is recorded |
| 2 = all | The results of all completion times and failed completions are recorded. |
| 3 = overThreshold | The results of completion times over rttMonCtrlAdminThreshold are recorded. |
| 4 = failures | The results of failed operations only are recorded. |
Max-Access: Read-create
End of Table
A table that contains the operational values for the probe, and the conceptual RTT control row.
This table augments the rttMonCtrlAdminTable.
Syntax: SEQUENCE OF RttMonCtrlOperEntry
Max-Access: Not-accessible
A list of objects that describe the current state of the probe, and the conceptual RTT control row.
Syntax: RttMonCtrlOperEntry
Max-Access: Not-accessible
rttMonCtrlOperModificationTime
The time that the probe was modified. This value is updated whenever an object in the conceptual RTT control row is changed or updated.
Syntax: TimeStamp
Max-Access: Read-only
A string that can be used as an aid in tracing problems. The contents of this field depend on the type of target (rttMonEchoAdminProtocol).
When rttMonEchoAdminProtocol is either snaLU2EchoAppl, or snaLU0EchoAppl, this object contains the name of the logical unit (LU) being used for this RTT session, once the session has been established. You can correlate this LU name to the connection information stored in the mainframe host.
When rttMonEchoAdminProtocol is snaLU62EchoAppl, this object contains the LU name being used for this RTT session, once the session has been established. This LU name can be used by the management application to correlate to the connection information stored at this SNMP agent via the Advanced Program-to-Program Communication (APPC) or Advanced Peer-to-Peer Networking (APPN) MIB.
When rttMonEchoAdminProtocol is not one of the previously mentioned values, this value is null.
This object is meant to contain information that has significance to a human operator.
Syntax: DisplayString (SIZE(0-51))
Max-Access: Read-only
The time the probe was last reset. This object is set when the rttMonCtrlOperState is set to reset.
Syntax: TimeStamp
Max-Access: Read-only
The number of octets currently in use by this composite conceptual RTT row. A composite conceptual row includes the control, statistics, and history conceptual rows combined and contains all octets that are addressed via the rttMonCtrlAdminIndex in this MIB.
Syntax: Gauge32
Max-Access: Read-only
rttMonCtrlOperConnectionLostOccurred
Specifies whether an RTT connection fails or lost, or is reestablished.
This object is set to true when the RTT connection fails to be established or is lost, and set to false when a connection is reestablished. This object changes value only when the RttMonRttType is echo or pathEcho.
When the RttMonRttType is pathEcho, connection loss applies only to the rttMonEchoAdminTargetAddress and not to intermediate hops to the target.
When this value changes and rttMonReactAdminConnectionEnable is true, a reaction occurs.
If a trap is sent, it is an rttMonConnectionChangeNotification.
Syntax: TruthValue
Max-Access: Read-only
Specifies whether an RTT operation timed out. This object changes its value for all RttMonRttTypes.
This object is set to true when an operation times out, and is set to false when an operation completes under rttMonCtrlAdminTimeout. When this value changes, a reaction might occur, as defined by rttMonReactAdminTimeoutEnable.
When the RttMonRttType is pathEcho, this timeout applies only to the rttMonEchoAdminTargetAddress and not to intermediate hops to the target.
If a trap is sent, it is an rttMonTimeoutNotification.
Syntax: TruthValue
Max-Access: Read-only
rttMonCtrlOperOverThresholdOccurred
This object changes its value for all RttMonRttTypes.
This object is changed when RTT operation completion times exceed the threshold, as defined by the threshold variables. The conditions under which this object changes from true to false are defined rttMonReactAdminThresholdType.
If a trap is sent, it is an rttMonThresholdNotification.
Syntax: TruthValue
Max-Access: Read-only
The total number of RTT operations that have been attempted.
This value is incremented for each start of an RTT operation--when rttMonCtrlAdminRttType is set to pathEcho. This value is incremented once for the whole path, and not for every hop along the path.
This object has the special behavior defined in the note on rollovers at the beginning of this section "Cisco Round Trip Time (RTT) Monitoring Group."
This value is not affected by the rollover of a statistics hourly group.
Syntax: Integer32 (0-2147483647)
Max-Access: Read-only
The number of seconds remaining for RTT operations for this conceptual row. This object is decremented every second, until it reaches zero. When the value of this object is zero, RTT operations for this row are suspended. This object either reaches zero by a countdown or changes to zero when set by the rttMonCtrlOperState.
When this object reaches zero the agent must change the rttMonCtrlOperState to inactive.
When the rttMonCtrlOperState object is active and the rttMonReactTriggerOperState object changes to active, this object is not updated with the current value of rttMonCrtlAdminRttLife object.
Syntax: Integer32 (0-2147483647)
Max-Access: Read-only
Used to manage the state of the probe that is implementing conceptual RTT control row.
Integer of 1, 2, 3, 4, 5, or 6, representing probe states, as follows:
| 1 = reset | Reset this entry, transition to pending. See the list following this table for the effects of this setting. |
| 2 = orderlyStop | Shut down this entry at the end of the next RTT operation attempt; transition to inactive. |
| 3 = immediateStop | Shut down this entry immediately (if possible); transition to inactive. |
| 4 = pending | This conceptual RTT control row is waiting for further control either via the rttMonScheduleAdminTable, or the rttMonReactAdminTable and the rttMonReactTriggerAdminTable, configured together to cause activation.
This value is not directly settable, but the state of the probe can change to pending when the probe is set to reset, or if the conceptual row had its original startup time set to a value smaller than the sysUptime. (See the rttMonScheduleAdminRttStartTime object description.) |
| 5 = inactive | This conceptual RTT control row is waiting for further control via the rttMonScheduleAdminTable.
This value is not directly settable, but the state of the probe can change to inactive when the probe is set to orderlyStop or immediateStop, or when the rttMonCtrlOperRttLife object reaches zero. |
| 6 = active | This conceptual RTT control row is currently active. This value is not directly settable. |
When its operation state is set to reset, the probe takes the following actions:
Probe reset can be used to synchronize various RTT definitions, so that the RTT requests occur simultaneously, or as simultaneously as possible.
When its operation state is changed to inactive (via a state change to orderlyStop or immediateStop or when rttMonCtrlOperRttLife reaches zero), the probe takes the following actions:
Table 3-9 summarizes rttMonCtrlOperState when certain actions occur and the state is either pending, inactive, or active.
| State | |||
|---|---|---|---|
| Action | pending | inactive | active |
| Operation state of the probe is set to reset | noError
State reset to pending. | inconsistent value | noError
State changes to pending. |
| Operation state of the probe is set to orderlyStop or to immediateStop | noError
State changes to inactive. | noError
State remains inactive. | noError
State changes to inactive. |
| Event causes trigger state to transition to active | State changes to active. | State remains inactive. | State remains active.1 |
| Administrative status of the conceptual RTT monitoring control row changes to active, and RttStartTime is a special value of 1. | State changes to active. | State changes to active. | See footnote2 |
| Administrative status of the conceptual RTT monitoring control row changes to active, and RttStartTime is a special value of less than the current time, excluding 1. | State changes to active. | State changes to active. | See footnote2 |
| Administrative status of the conceptual RTT monitoring control row changes to notInService. | State remains pending. | State remains inactive. | See footnote3 |
| Administrative status of the conceptual RTT monitoring control row changes to delete. | State changes to inactive. | State remains inactive. | State changes to inactive. |
| Administrative status of the conceptual RTT monitoring control is active, and the RttStartTime arrives. | State changes to active. | State changes to active. | State remains active.1 |
| RowAgeout expires. | State changes to inactive. | State remains inactive. | State changes to inactive. |
| OperRttLife counts down to zero. | N/A | N/A | State changes to inactive. |
Max-Access: Read-write
End of Table
A table that contains the status of latest RTT operation.
When the RttMonRttType is pathEcho, operations performed to the hops along the path are recorded in this table.
This table augments the RTT definition table, rttMonCtrlAdminTable.
Syntax: SEQUENCE OF RttMonLatestRttOperEntry
Max-Access: Not-accessible
A list of objects that record the latest RTT operation.
Syntax: RttMonLatestRttOperEntry
Max-Access: Not-accessible
rttMonLatestRttOperCompletionTime
The completion time of the latest RTT operation that completed successfully.
Syntax: Gauge32
Access: Read-only
A sense code for the completion status of the latest RTT operation.
Syntax: RttResponseSense
Max-Access: Read-only
rttMonLatestRttOperApplSpecificSense
An application-specific sense code for the completion status of the latest RTT operation. This object is valid only when the rttMonLatestRttOperSense object is set to applicationSpecific. Otherwise, this object's value is not valid.
Syntax: Integer32 (1001-2147483647)
Max-Access: Read-only
rttMonLatestRttOperSenseDescription
A sense description for the completion status of the latest RTT operation when the rttMonLatestRttOperSense object is set to applicationSpecific.
Syntax: DisplayString (SIZE(0-255))
Max-Access: Read-only
The value of the agent system time at the time of the latest RTT operation.
Syntax: TimeStamp
Max-Access: Read-only
When the RttMonRttType is echo or pathEcho, this is a string that specifies the address of the target for this RTT operation. When the RttMonRttType is not echo or pathEcho, this object is null.
This value is the address of the hop along the path to the rttMonEchoAdminTargetAddress address. It can include rttMonEchoAdminTargetAddress address, or it can consist only of the rttMonEchoAdminTargetAddress, when the path information is not collected. This behavior is defined by the rttMonCtrlAdminRttType object.
The interpretation of this string depends on the type of RTT operation selected, as specified by the rttMonEchoAdminProtocol object.
Syntax: RttMonTargetAddress
Max-Access: Read-only
End of Table
A table that contains the list of conceptual RTT control rows that start to collect data when a reaction condition is violated and when rttMonReactAdminActionType is set to one of the following:
The goal of this table is to define one or more additional conceptual RTT control rows that become active and start to collect additional history and statistics (depending on the row's configuration values) when a problem has been detected.
If the conceptual RTT control row is undefined, and a trigger occurs, no action takes place.
If the conceptual RTT control row is scheduled to start at a later time, triggering that row has no effect.
If the conceptual RTT control row is currently active, triggering that row has no effect on that row, but the rttMonReactTriggerOperState object changes to active.
An entry in this table can only be triggered when it is not currently in a triggered state. The object rttMonReactTriggerOperState reflects the state of each entry in this table.
Syntax: SEQUENCE OF RttMonReactTriggerAdminEntry
Max-Access: Not-accessible
A list of objects that are triggered when a reaction condition is violated.
Syntax: RttMonReactTriggerAdminEntry
Max-Access: Not-accessible
rttMonReactTriggerRttMonCtrlAdminIndex
Points to a single conceptual RTT control row. If this row does not exist and this value is triggered, no action results.
The conceptual RTT control row is triggered for the rttMonCtrlOperRttLife length. If this conceptual RTT control row is already active, rttMonCtrlOperRttLife is not updated, and its life continues as previously defined.
Syntax: Integer32 (1-2147483647)
Max-Access: Not-accessible
Used to create trigger entries. The default value is createAndGo.
Syntax: RowStatus
Max-Access: Read-create
End of Table
A table that contains the operational state of each entry in the rttMonReactTriggerAdminTable.
This table augments the RTT trigger definition table, rttMonReactTriggerAdminTable.
Syntax: SEQUENCE OF RttMonReactTriggerOperEntry
Max-Access: Not-accessible
A list of state objects for the rttMonReactTriggerAdminTable.
Syntax: RttMonReactTriggerOperEntry
Max-Access: Not-accessible
Specifies the status of the RTT trigger.
This object takes on the value active when its associated entry in the rttMonReactTriggerAdminTable has been triggered.
When the associated entry in the rttMonReactTriggerAdminTable is not under a trigger state, this object is pending.
When this object is in the active state, its associated entry cannot be retriggered.
Syntax: Integer, 1 = active, 2 = pending
Max-Access: Read-only
The statistics capture database.
This table contains summarized information of the results for a conceptual RTT control row. A rolling accumulated history of this information is maintained in a series of one or more hourly groups. Each group contains a series of one or more paths, each path contains a series of one or more hops, and each hop contains a series of one or more statistics distribution buckets.
Each conceptual statistics row has a current hourly group, into which RTT results are accumulated. At the end of each hour a new hourly group is created which then becomes current. The counters and accumulators in the new group are initialized to zero. The previous group or groups are kept in the table until the table contains rttMonStatisticsAdminNumHourGroups groups for the conceptual statistics row; at this point, the oldest group is discarded and is replaced by the newly created one. The hourly group is uniquely identified by the rttMonStatsCaptureStartTimeIndex object.
If the activity for a conceptual RTT control row ceases because the rttMonCtrlOperState object transitions to inactive, the corresponding current hourly group in this table is frozen, and a new hourly group is created when activity is resumed.
If the activity for a conceptual RTT control row ceases because the rttMonCtrlOperState object transitions to pending, this table is cleared and reset to its initial state.
When the RttMonRttType is pathEcho, the path exploration RTT requests statistics are not accumulated in this table.
Using this rttMonStatsCaptureTable, a managing application can retrieve summarized data from accurately measured periods, which is synchronized across multiple conceptual RTT control rows. Because the new hourly group creation is performed on a 60-minute period, the managing station has enough time to collect the data, and need not be concerned with the vagaries of network delays and lost protocol data units (PDUs) when trying to get matching data. Also, the managing station can spread the data gathering over a longer period, and need not create for a flood of get requests in a short period.
Syntax: SEQUENCE OF RttMonStatsCaptureEntry
Max-Access: Not-accessible
A list of objects that accumulate the results of a series of RTT operations over a 60-minute time period.
The statistics capture table is a rollover table. When the number of rttMonStatsCaptureStartTimeIndex groups exceeds the rttMonStatisticsAdminNumHourGroups value, the oldest corresponding hourly group is deleted and is replaced with the new rttMonStatsCaptureStartTimeIndex hourly group.
All other indices fill to their maximum size.
The statistics capture table has the following five indices:
Syntax: RttMonStatsCaptureEntry
Max-Access: Not-accessible
rttMonStatsCaptureStartTimeIndex
The time when this row was created.
This object is the second index of the rttMonStatsCaptureTable.
When the number of rttMonStatsCaptureStartTimeIndex groups exceeds the rttMonStatisticsAdminNumHourGroups value, the oldest rttMonStatsCaptureStartTimeIndex group is removed and replaced with the new entry.
When the RttMonRttType is pathEcho, this object also uniquely defines a group of paths. See the rttMonStatsCaptureEntry object for more information.
Syntax: TimeStamp
Max-Access: Not-accessible
When the RttMonRttType is pathEcho, this object uniquely defines a path for a given value of rttMonStatsCaptureStartTimeIndex. For all other values of RttMonRttType, this object is 1.
For a particular value of rttMonStatsCaptureStartTimeIndex, the agent assigns a value of 1 to the first instance of a path, a value of 2 to the second instance, and so on. The sequence increments until the number of paths equals the rttMonStatisticsAdminNumPaths value. At that point, no new paths are kept for the current rttMonStatsCaptureStartTimeIndex group.
This value directly represents the path to a target. We can support only 128 paths.
Syntax: Integer32 (1-128)
Max-Access: Not-accessible
When the RttMonRttType is pathEcho, this object uniquely defines a hop for a given value of rttMonStatsCapturePathIndex. For all other values of RttMonRttType, this object is 1.
For a particular value of rttMonStatsCapturePathIndex, the agent assigns a value of 1 to the first instance of a hop, a value of 2 to the second instance, and so on. The sequence increments until the number of hops equals the rttMonStatisticsAdminNumHops value. At that point, no new hops are kept for the current rttMonStatsCapturePathIndex.
This value directly represents a hop along the path to a target. We can support only 512 hops.
This value shows the order along the path to a target.
Syntax: Integer32 (1-512)
Max-Access: Not-accessible
Uniquely defines a statistical distribution bucket for a given value of rttMonStatsCaptureHopIndex.
For a particular value of rttMonStatsCaptureHopIndex, the agent assigns a value of 1 to the first instance of a distribution, a value of 2 to the second instance, and so on. The sequence increments until the number of statistics distribution intervals equals the rttMonStatisticsAdminNumDistBuckets value. At that point, all values that fall above the last interval are placed into the last interval.
Each of these statistics distribution buckets contains the results of each completion as defined by rttMonStatisticsAdminDistInterval object.
Syntax: Integer32 (1-512)
Max-Access: Not-accessible
The number of RTT operations that have completed without an error and without timing out.
This object has the special behavior defined in the note on rollovers at the beginning of this section "Cisco Round Trip Time (RTT) Monitoring Group."
Syntax: Integer32 (0-2147483647)
Max-Access: Read-only
rttMonStatsCaptureOverThresholds
The number of RTT operations successfully completed, but in excess of rttMonCtrlAdminThreshold. This number is a subset of the accumulation of all rttMonStatsCaptureCompletions. The operation time of these completed operations is accumulated.
This object has the special behavior defined in the note on rollovers at the beginning of this section "Cisco Round Trip Time (RTT) Monitoring Group."
Syntax: Integer32 (0-2147483647)
Max-Access: Read-only
rttMonStatsCaptureSumCompletionTime
The accumulated completion time of RTT operations that complete successfully.
Syntax: Gauge32
Max-Access: Read-only
rttMonStatsCaptureSumCompletionTime2Low
The low-order 32 bits of the accumulated squares of completion times (in milliseconds) of RTT operations that complete successfully.
Low and high order are defined where the binary number looks as follows:
For example, the number 4294967296 has all low-order bits as 0 and the rightmost high-order bit as 1 (zeros,1).
Syntax: Gauge32
Max-Access: Read-only
rttMonStatsCaptureSumCompletionTime2High
The high-order 32 bits of the accumulated squares of completion times (in milliseconds) of RTT operations that complete successfully. See the rttMonStatsCaptureSumCompletionTime2Low object for a definition of low and high order.
Syntax: Gauge32
Max-Access: Read-only
rttMonStatsCaptureCompletionTimeMax
The maximum completion time of any RTT operation that completes successfully.
Syntax: Gauge32
Max-Access: Read-only
rttMonStatsCaptureCompletionTimeMin
The minimum completion time of any RTT operation that completes successfully.
Syntax: Gauge32
Max-Access: Read-only
End of Table
The statistics collection database.
This table behaves like the rttMonStatsCaptureTable, except that it does not keep statistical distribution information.
For a complete table description, see the rttMonStatsCaptureTable object.
Syntax: SEQUENCE OF RttMonStatsCollectEntry
Max-Access: Not-accessible
A list of objects that accumulate the results of a series of RTT operations over a 60-minute time period.
This entry behaves like the rttMonStatsCaptureEntry, except that it does not keep statistical distribution information. For a complete entry description, see the rttMonStatsCaptureEntry object.
Syntax: RttMonStatsCollectEntry
Max-Access: Not-accessible
rttMonStatsCollectNumDisconnects
When the RttMonRttType is echo or pathEcho, this object represents the number of times that the target or hop along the path to a target becomes disconnected. For all other values of RttMonRttType, this object remains zero.
For connectionless protocols, this has no meaning, and consequently remains 0. When rttMonEchoAdminProtocol is snaRUEcho, this variable is the number of times that an LU-system services control point (SSCP) session was lost. When the rttMonEchoAdminProtocol is either snaLU0EchoAppl, snaLu62Echo, or snaLU62EchoAppl, this variable is the number of times that an LU-LU session was lost.
Because this error does not indicate any information about the failure of an RTT operation, no response time information for this instance will be recorded in the appropriate objects.
If this error occurs and the rttMonStatsCapturePathIndex cannot be determined, this error is accumulated in the source-to-target path that will always exist.
This object has the special behavior defined in the note on rollovers at the beginning of this section "Cisco Round Trip Time (RTT) Monitoring Group."
Syntax: Integer32 (0-2147483647)
Max-Access: Read-only
The number of occasions when an RTT operation was not completed before a timeout occurred--before rttMonCtrlAdminTimeout was exceeded.
Because the RTT operation was never completed, the completion times of these operations are not accumulated, nor do they increment the rttMonStatsCaptureCompletions value in any of the statistics distribution buckets.
This object has the special behavior defined in the note on rollovers at the beginning of this section "Cisco Round Trip Time (RTT) Monitoring Group."
Syntax: Integer32 (0-2147483647)
Max-Access: Read-only
The number of occasions when an RTT operation could not be initiated because a previous RTT operation had not completed.
When the RttMonRttType is pathEcho, this object can occur for both connection-oriented protocols and connectionless protocols.
When the RttMonRttType is echo, this object can occur only for connection-oriented protocols such as SNA.
When a new operation cannot be started, this object increments and the operation is omitted. (The next operation will start at the next frequency.) Because an RTT operation was never initiated, the completion times of these operations are not accumulated, nor do they increment the rttMonStatsCaptureCompletions value.
If this error occurs when the RttMonRttType is pathEcho, and the rttMonStatsCapturePathIndex cannot be determined, this error is accumulated in the source-to-target path that will always exist.
This object has the special behavior defined in the note on rollovers at the beginning of this section "Cisco Round Trip Time (RTT) Monitoring Group."
Syntax: Integer32 (0-2147483647)
Max-Access: Read-only
rttMonStatsCollectNoConnections
When the RttMonRttType is echo or pathEcho, this object is the number of occasions when an RTT operation could not be initiated because the connection to the target was not established. For all other RttMonRttTypes this object remains zero.
This object cannot occur for connectionless protocols, but it can occur for connection-oriented protocols such as SNA.
Because an RTT operation was never initiated, the completion times of these operations are not accumulated, nor do they increment the rttMonStatsCaptureCompletions value.
If this error occurs and the rttMonStatsCapturePathIndex cannot be determined, this error is accumulated in the source-to-target path that will always exist.
This object has the special behavior defined in the note on rollovers at the beginning of this section "Cisco Round Trip Time (RTT) Monitoring Group."
Syntax: Integer32 (0-2147483647)
Max-Access: Read-only
The number of occasions when an RTT operation could not be initiated because some necessary internal resource (for example, memory or SNA subsystem) was not available, or because the operation completion could not be recognized.
Because an RTT operation was never initiated or was not recognized, the completion times of these operations are not accumulated, nor do they increment the rttMonStatsCaptureCompletions value in the expected distribution bucket.
If this error occurs when the RttMonRttType is pathEcho and the rttMonStatsCapturePathIndex cannot be determined, this error is accumulated in the source-to-target path that will always exist.
This object has the special behavior defined in the note on rollovers at the beginning of this section "Cisco Round Trip Time (RTT) Monitoring Group."
Syntax: Integer32 (0-2147483647)
Max-Access: Read-only
rttMonStatsCollectSequenceErrors
When the RttMonRttType is echo or pathEcho, this object is the number of RTT operation completions received with an unexpected sequence identifier. For all other values of RttMonRttType this object remains zero.
This object can occur for the following reasons:
The completion times of these operations are not accumulated, nor do they increment the rttMonStatsCaptureCompletions value in the expected distribution bucket.
This object has the special behavior defined in the note on rollovers at the beginning of this section "Cisco Round Trip Time (RTT) Monitoring Group."
Syntax: Integer32 (0-2147483647)
Max-Access: Read-only
rttMonStatsCollectVerifyErrors
The number of RTT operation completions received with data that does not compare with the expected data. The completion times of these operations are not accumulated, nor do they increment the rttMonStatsCaptureCompletions value in the expected distribution bucket.
This object has the special behavior defined in the note on rollovers at the beginning of this section "Cisco Round Trip Time (RTT) Monitoring Group."
Syntax: Integer32 (0-2147483647)
Max-Access: Read-only
A string that specifies the address of the target for the this RTT operation.
This object applies only when the RttMonRttType is echo or pathEcho. For all other values of the RttMonRttType, this is null.
The value of this object is the address of the hop along the path to the rttMonEchoAdminTargetAddress address. It can include rttMonEchoAdminTargetAddress, or it can consist only of rttMonEchoAdminTargetAddress when the path information is not collected. This behavior is defined by the rttMonCtrlAdminRttType object.
The interpretation of this string depends on the type of RTT monitoring operation selected, as specified by the rttMonEchoAdminProtocol object.
Syntax: RttMonTargetAddress
Max-Access: Read-only
End of Table
The statistics totals database.
This table behaves like the rttMonStatsCaptureTable, except that it keeps 60-minute group values only. For a complete table description, see the rttMonStatsCaptureTable object.
Syntax: SEQUENCE OF RttMonStatsTotalsEntry
Max-Access: Not-accessible
A list of objects that accumulate the results of a series of RTT operations over a 60-minute time period.
This entry behaves like as the rttMonStatsCaptureEntry, except that it keeps 60-minute group values only.
For a complete entry description, see the rttMonStatsCaptureEntry object.
Syntax: RttMonStatsTotalsEntry
Max-Access: Not-accessible
The length of time since this conceptual statistics row was created.
Syntax: TimeInterval
Max-Access: Read-only
The number of RTT operations that have been initiated.
This number includes all RTT operations that fail for whatever reason.
This object has the special behavior defined in the note on rollovers at the beginning of this section "Cisco Round Trip Time (RTT) Monitoring Group."
Syntax: Integer32 (0-2147483647)
Max-Access: Read-only
End of Table
The history collection database.
The history table contains a point-by-point rolling history of the most recent RTT operations for each conceptual RTT control row. The rolling history of this information is maintained in a series of one or more lives, each containing a one or more buckets. Each bucket contains one or more samples.
Each conceptual history row can have lives. A life is defined by the rttMonCtrlOperRttLife object. A new life is created when rttMonCtrlOperState changes to active. When the number of lives becomes greater than rttMonHistoryAdminNumLives value, the oldest life is discarded and a new life is created by incrementing the index.
The path exploration RTT operation is kept as an entry in this table.
Syntax: SEQUENCE OF RttMonHistoryCollectionEntry
Max-Access: Not-accessible
A list of history objects that are recorded for each RTT operation.
The history collection table has the following four indices:
Syntax: RttMonHistoryCollectionEntry
Max-Access: Not-accessible
rttMonHistoryCollectionLifeIndex
Uniquely defines a life for a conceptual history row.
For a particular value of rttMonHistoryCollectionLifeIndex, the agent assigns the first value of 1, the second value of 2, and so on. The sequence increments, despite the removal of older (lower) values from the table.
Syntax: Integer32 (1-2147483647)
Max-Access: Not-accessible
rttMonHistoryCollectionBucketIndex
When the RttMonRttType is pathEcho, this object uniquely defines a bucket for a given value of rttMonHistoryCollectionLifeIndex. For all other RttMonRttType values, this value is the number of operations per a lifetime.
For a particular value of rttMonHistoryCollectionLifeIndex, the agent assigns the first value of 1, the second value of 2, and so on. The sequence increments until the number of buckets equals rttMonHistoryAdminNumBuckets. At that point, no new buckets are created for the current rttMonHistoryCollectionLifeIndex.
Syntax: Integer32 (1-2147483647)
Max-Access: Not-accessible
rttMonHistoryCollectionSampleIndex
Uniquely defines a row for a given value of rttMonHistoryCollectionBucketIndex.
For a particular value of rttMonHistoryCollectionBucketIndex, the agent assigns the first value of 1, the second value of 2, and so on. The sequence increments until the number of samples equals rttMonHistoryAdminNumSamples. At that point, no new samples are created for the current rttMonHistoryCollectionBucketIndex.
When the RttMonRttType is pathEcho, this value directly represents the number of hops along a path to a target. We can support only 512 hops. For all other values of the RttMonRttType, this object is 1.
Syntax: Integer32 (1-512)
Max-Access: Not-accessible
rttMonHistoryCollectionSampleTime
The time that the RTT operation was initiated.
Syntax: TimeStamp
Max-Access: Read-only
rttMonHistoryCollectionAddress
When the RttMonRttType is echo or pathEcho, this object is a string that specifies the address of the target for this RTT operation. For all other values of RttMonRttType, this string is null.
This value is the address of the hop along the path to the rttMonEchoAdminTargetAddress. It can include rttMonEchoAdminTargetAddress address, or it can consist only of the rttMonEchoAdminTargetAddress, when the path information is not collected. This behavior is defined by the rttMonCtrlAdminRttType object.
The interpretation of this string depends on the type of RTT operation selected, as specified by the rttMonEchoAdminProtocol object.
Syntax: RttMonTargetAddress
Max-Access: Read-only
rttMonHistoryCollectionCompletionTime
The operation completion time of the RTT operation. If the RTT operation fails--rttMonHistoryCollectionSense is any value other than ok--this object has a value of 0.
Syntax: Gauge32
Max-Access: Read-only
A sense code for the completion status of the RTT operation.
Syntax: RttResponseSense
Max-Access: Read-only
rttMonHistoryCollectionApplSpecificSense
An application-specific sense code for the completion status of the last RTT operation. This object is valid only when the rttMonHistoryCollectionSense object is set to applicationSpecific. Otherwise, this object's value is not valid.
Syntax: Integer32 (1001-2147483647)
Max-Access: Read-only
rttMonHistoryCollectionSenseDescription
A sense description for the completion status of the last RTT operation when the rttMonHistoryCollectionSense object is set to applicationSpecific.
Syntax: DisplayString (SIZE(0-255))
Max-Access: Read-only
End of Table
The following notifications are supported with the Cisco Round Trip Time (RTT) Monitoring Group.
rttMonConnectionChangeNotification
This notification is valid only when the RttMonRttType is echo or pathEcho.
Indicates that a connection to a target (not to a hop along the path to a target) has either failed on establishment or has been lost. This notification also indicates when a lost connection is reestablished. Each occurrence indicates that the value of rttMonCtrlOperConnectionLostOccurred has changed.
If history is not being collected, or if the RttMonRttType is not echo or pathEcho, the rttMonHistoryCollectionAddress is null.
The following objects are bound into the notification PDU (trap): rttMonCtrlAdminTag, rttMonHistoryCollectionAddress, and rttMonCtrlOperConnectionLostOccurred.
Indicates the occurrence of a timeout for an RTT operation, and the clearing of such a condition by a subsequent RTT operation. Each occurrence indicates that the value of rttMonCtrlOperTimeoutOccurred has changed.
When the RttMonRttType is pathEcho, this notification is sent only when the timeout occurs during an operation to the target and not to a hop along the path to the target. This restriction also applies to the clearing of the timeout.
If history is not being collected, or if the RttMonRttType is not echo or pathEcho, the rttMonHistoryCollectionAddress is null.
The following objects are bound into the notification PDU (trap): rttMonCtrlAdminTag, rttMonHistoryCollectionAddress, and rttMonCtrlOperTimeoutOccurred.
Indicates the occurrence of a threshold violation for an RTT operation, and that the previous violation has subsided for a subsequent RTT operation. Each occurrence indicates that the value of rttMonCtrlOperOverThresholdOccurred has changed.
When the RttMonRttType is pathEcho, this notification is sent only when the threshold violation occurs during an operation to the target and not to a hop along the path to the target. This restriction also applies to the subsiding of a threshold condition.
If history is not being collected, or if the RttMonRttType is not echo or pathEcho, the rttMonHistoryCollectionAddress is null.
The following objects are bound into the notification PDU (trap): rttMonCtrlAdminTag, rttMonHistoryCollectionAddress, and rttMonCtrlOperOverThresholdOccurred.
The variables described in this section are used to manage read-only configuration and operational information of Cisco's implementation of translation between Synchronous Data Link Control (SDLC) media and Logical Link Control, type 2 (LLC2) media.
This table contains objects for the interfaces and SDLC addresses configured for SDLLC conversion.
Syntax: SEQUENCE OF ConvSdllcPortEntry
Max-Access: Not-accessible
The local administered virtual MAC address for the device on the serial interface.
Syntax: MacAddress
Max-Access: Read-only
The virtual ring number assigned to the serial interface.
Syntax: Integer32
Max-Access: Read-only
The bridge number assigned to SDLLC conversion.
Syntax: Integer32
Max-Access: Read-only
The ring number assigned to the LLC2 side of the SDLLC conversion.
Syntax: Integer32
Max-Access: Read-only
Indicates whether all SDLLC sessions are locally acknowledged.
TRUE indicates that SDLLC sessions are locally acknowledged; FALSE indicates that SDLLC sessions are not locally acknowledged.
Syntax: TruthValue
Max-Access: Read-only
The state of the local acknowledgment session between two stations.
Integer
| 1 = disconnected | LAK not connected, but peers may be |
| 2 = localDiscWait | Waiting for local peer to disconnect |
| 3 = remDiscWait | Waiting for remote peer to disconnect |
| 4 = remWait | Waiting for peer to open |
| 5 = localWait | Waiting for local LLC2 to open |
| 6 = connectPending | Synchronize the stations before final connection |
| 7 = connected | Full data transfer possible |
| 8 = remQOnWait | Waiting for Quench on acknowledgment |
| 9 = remQOffWait | Waiting for Quench off acknowledgment |
| 10 = quenched | Both stations are quenched, and expect no data |
| 255 = unknown | State is unknown or not applicable |
Max-Access: Read-only
The largest information frame (I-frame) size that can be sent or received on the LLC2 session.
Syntax: Integer32
Max-Access: Read-only
End of Table
This table contains objects for the SDLC addresses configured for SDLLC conversion on a particular interface.
Syntax: SEQUENCE OF ConvSdllcAddrEntry
Max-Access: Not-accessible
The address of the SDLC station.
Syntax: Integer (0-255)
Max-Access: Not-accessible
The MAC address of the LLC2 station, for device-initiated SDLLC connections.
Syntax: MacAddress
Max-Access: Read-only
The XID value that is associated with the SDLC station. This value must match the host configured value.
Syntax: Octet string (SIZE (4))
Max-Access: Read-only
The current state of the SDLLC connection.
Integer
| 1 = disconnected | Session disconnected |
| 2 = sdlcDisconnecting | Disconnect pending SDLC side |
| 3 = sdlcPriConnecting | Connect pending SDLC primary side |
| 4 = netDisconnecting | Disconnect pending network side |
| 5 = netConnecting | Connect pending network side |
| 6 = sdlcSecConnecting | Connect pending SDLC secondary side |
| 7 = connected | Session connected |
Max-Access: Read-only
The largest information frame (I-frame) size that can be sent or received on the SDLC session.
Syntax: Integer32
Max-Access: Read-only
End of Table
The following notification is supported in the Cisco SDLLC Conversion MIB:
convSdllcPeerStateChangeNotification
This notification indicates that the state of an SDLLC peer has transitioned to active (connected) or inactive (disconnected).
The variables in this section provide configuration and operational information for Cisco's serial tunneling (STUN) implementation.
This table contains objects that represent STUN groups configured on the router. Each STUN-enabled interface is assigned to a STUN group, and packets can only travel between STUN-enabled interfaces in the same group.
Syntax: SEQUENCE OF StunGroupEntry
Max-Access: Not-accessible
The configured STUN group number.
Syntax: Integer (1-255)
Max-Access: Not-accessible
The protocol type for this STUN group.
Integer
| 1 = basic | Non-SDLC, such as HDLC |
| 2 = sdlc | SDLC |
| 3 = sdlctg | SNA transmission group |
| 4 = custom | Customer-defined protocol |
Max-Access: Read-only
End of Table
This table contains a list of STUN-enabled interfaces (ports).
Syntax: SEQUENCE OF StunPortEntry
Max-Access: Not-accessible
The group number to which the stun port belongs. Frames will only be routed to other ports (on this or another router) in the same STUN group. This group must match a stunGroupIndex in the stunGroupTable.
Syntax: Integer (1-255)
Max-Access: Read-only
The type of identification of the default partner for unrecognized addresses. If there is no default route then the stunRouteType field of stunPortDefaultRemote is "other".
If ip then the value is in stunRouteIP. If the value is serial or serialDirect then the value is in stunRouteSerial.
Syntax: Integer 1 = other, 2 = ip, 3 = direct, 4 = frameRelay
Max-Access: Read-only
The IP address of the remote default STUN partner, for unrecognized addresses. 0.0.0.0 is returned if the default route type is not IP.
Syntax: IpAddress
Max-Access: Read-only
stunPortDefaultPeerSerialInterface
If the stunRouteType is serial, then this is the serial interface index of the point-to-point link to the remote partner. If the stunRouteType is serialDirect, then the partner is in the local STUN. If the stunRouteType is ip then this field is 0.
Syntax: InterfaceIndex
Max-Access: Read-only
End of Table
This table contains information about specific SDLC addresses. There is one table entry for each SDLC address configured by the stun route command.
Syntax: SEQUENCE OF StunRouteEntry
Max-Access: Not-accessible
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
The type of identification of the remote partner.
Syntax: Integer 1 = other, 2 = ip, 3 = direct, 4 = frameRelay
Max-Access: Read-only
The IP address of the remote STUN partner. It is 0.0.0.0 if partner type is not IP.
Syntax: IpAddress
Max-Access: Read-only
The local interface index to the remote partner. Zero (0) is returned if the partner type is not direct or frameRelay.
Syntax: InterfaceIndex
Max-Access: Read-only
The priority with which this station's traffic is routed across the network.
Syntax: Integer 1 = low, 2 = normal, 3 = medium, 4 = high
Max-Access: Read-only
The state of the peer connection through the STUN tunnel.
Syntax: Integer 1 = dead, 2 = closed, 3 = opening, 4 = openWait, 5 = connected, 6 = direct
Max-Access: Read-only
Indicates whether the STUN connection is locally acknowledged. A value of TRUE means the STUN connection is locally acknowledged. A value of FALSE means the STUN connection is not locally acknowledged.
Syntax: TruthValue
Max-Access: Read-only
The number of frames received from the serial interface with this station's address.
Syntax: Counter32
Max-Access: Read-only
The number of frames transmitted at the serial interface with this station's address.
Syntax: Counter32
Max-Access: Read-only
The number of bytes received from the serial interface with this station's address.
Syntax: Counter32
Max-Access: Read-only
The number of bytes transmitted at the serial interface with this station's address.
Syntax: Counter32
Max-Access: Read-only
End of Table
The following notification is supported with the Cisco STUN MIB:
stunPeerStateChangeNotification
This notification indicates that the state of a STUN route has transitioned to active (connected) or inactive (dead or closed).
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.
The SNA LLC Group is comprised of the llcPortGroup, llcSapGroup, and llcCcGroup.
The LLC Port group includes llcPortAdminTable, llcPortOperTable, and llcPortStatsTable.
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
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
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
The maximum number of SAPs that can be opened on this port.
Syntax: Gauge32
Max-Access: Read-write
The maximum number of connection components that can be opened on this port.
Syntax: Gauge32
Max-Access: Read-write
The default maximum protocol data unit (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 nonzero SAP default value in the llcSapAdminMaxPDUOctets object or by a nonzero 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 new value in the llcCcOperMaxPDUOctets object for the connection component.
The PDU size includes all octets in a frame, but excludes framing characters, the media access control (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 nonzero SAP default value in the llcSapAdminMaxUnackedIPDUsSend object or by a nonzero 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 nonzero SAP default value in the llcSapAdminMaxUnackedIPDUsRcv object or by a nonzero 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
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 nonzero SAP default value in the llcSapAdminMaxretransmits object or by a nonzero value in the llcCcAdminMaxRetransmits object.
Syntax: Integer32
Max-Access: Read-write
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 is used to control/read the value.
This port default value can be overridden by a nonzero value in the llcSapAdminAckTimer object or by a nonzero value in the llcCcAdminAckTimer object.
Syntax: TimeTicks
Max-Access: Read-write
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 nonzero SAP default value in the llcSapAdminPbitTimer object or by a nonzero value in the llcCcAdminPbitTimer object.
Syntax: TimeTicks
Max-Access: Read-write
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 nonzero SAP default value in the llcSapAdminRejTimer object or by a nonzero value in the llcCcAdminRejTimer object.
Syntax: TimeTicks
Max-Access: Read-write
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 nonzero SAP default value in the llcSapAdminBusyTimer object or by a nonzero value in the llcCcAdminBusyTimer object.
Syntax: TimeTicks
Max-Access: Read-write
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 nonzero SAP default value in the llcSapAdminInactTimer object or by a nonzero 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
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 nonzero SAP default value in the llcSapAdminDelayAckCount object or by a nonzero value in the llcCcAdminDelayCount object.
A value of 1 indicates that acknowledgments are sent immediately and that the value of llcPortAdminDelayAckTimer is ignored.
Syntax: Integer32
Max-Access: Read-write
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
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 nonzero SAP default value in the llcSapAdminNw object.
Syntax: Integer32
Max-Access: Read-write
End of Table
This table contains current LLC port parameters.
Syntax: SEQUENCE OF LlcPortOperEntry
Max-Access: Not-accessible
This is the media access control (MAC) address for this local port.
Syntax: MacAddress
Max-Access: Read-only
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
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
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
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
This table contains statistics for a specific LLC port.
Syntax: SEQUENCE OF LlcPortStatsEntry
Max-Access: Not-accessible
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
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
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
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
The total number of TEST commands received on this port.
Syntax: Counter32
Max-Access: Read-only
The total number of TEST responses transmitted on this port in response to TEST commands received.
Syntax: Counter32
Max-Access: Read-only
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
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
The LLC SAP group contains llcSapAdminTable, llcSapOperTable, and llcSapStatsTable.
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 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
The address of this local SAP.
Syntax: Integer (1-225)
Max-Access: Not-accessible
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 nonzero 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,but excludes framing characters, the media access control (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 nonzero 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
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 nonzero 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
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 nonzero value in the llcCcAdminMaxRetransmits.
Syntax: Integer32
Max-Access: Read-write
The default value for the time interval during which the LLCs on this SAP can expect to receive either: an acknowledgment to one or more outstanding I PDUs, or 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 nonzero value in the llcCcAdminAckTimer.
Syntax: TimeTicks
Max-Access: Read-write
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 nonzero value in the llcCcAdminPbitTimer.
Syntax: TimeTicks
Max-Access: Read-write
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 nonzero value in the llcCcAdminRejTimer.
Syntax: TimeTicks
Max-Access: Read-write
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 nonzero value in the llcCcAdminBusyTimer.
Syntax: TimeTicks
Max-Access: Read-write
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 nonzero 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
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 value 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 nonzero 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
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
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 nonzero Cc default value in the llcCcAdminNw object.
Max-Access: Integer32
Max-Access: Read-write
End of Table
This object provides the current operational parameters of a SAP opened by VTAM. Multiple LLC SAPs can be opened for each configured virtual media access control (MAC) adapter on the CIP.
This parameter describes the actual state of this local SAP.
Syntax: Integer 1 = inactive, 2 = active
Max-Access: Read-only
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
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
This parameter describes whether the LLC implementation supports LLC2 connection components.
Syntax: Integer 1 = no, 2 = yes
Max-Access: Read-only
End of Table
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
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
The total number of times that the adjacent (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
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
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
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
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
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.
Syntax: Counter32
Max-Access: Read-only
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.
Syntax: Counter32
Max-Access: Read-only
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
The total REJ frames received from all adjacent LLC connection components on this SAP since it was created.
Syntax: Counter32
Max-Access: Read-only
The total REJ frames transmitted to an adjacent LLC connection components on this SAP since it was created.
Syntax: Counter32
Max-Access: Read-only
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
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
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
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
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
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 nonactivation XIDs. This object is initialized to zero when the SAP is created.
Syntax: Counter32
Max-Access: Read-only
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 nonactivation XIDs. This object is initialized to zero when the SAP is created.
Syntax: Counter32
Max-Access: Read-only
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 nonactivation XIDs. This object is initialized to zero when the SAP is created.
Syntax: Counter32
Max-Access: Read-only
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 nonactivation XIDs. This object is initialized to zero when the SAP is created.
Syntax: Counter32
Max-Access: Read-only
The total number of unnumbered information (UI) frames received on a local SAP.
Syntax: Counter32
Max-Access: Read-only
The total number of unnumbered information (UI) frames sent on a local SAP.
Syntax: Counter32
Max-Access: Read-only
The total octets received from adjacent connection components on this SAP. This object covers the address, control, and information field of UI-frames only. This object is initialized to zero when the SAP is created.
Syntax: Counter32
Max-Access: Read-only
The total octets transmitted to adjacent connection components on this SAP. This object covers the address, control, and information field of UI-frames only. This object is initialized to zero when the SAP is created.
Syntax: Counter32
Max-Access: Read-only
The total number of successful connections that have been established on this SAP since the SAP was created.
A successful connection is indicated by a successful SABME/UA exchange.
Syntax: Counter32
Max-Access: Read-only
The total number of unsuccessful connections that have been attempted on this SAP since the SAP was created.
An unsuccessful connection attempt is indicated by a SABME/DM exchange or a SABME/timeout.
Syntax: Counter32
Max-Access: Read-only
The total number of normal disconnections that have been performed on this SAP since the SAP was created.
A normal disconnection is indicated by a successful DISC/UA exchange or merely a DISC sent or received.
Syntax: Counter32
Max-Access: Read-only
The total number of abnormal disconnections (resulting from a FRMR being sent) that have been performed on this SAP since the SAP was created.
Syntax: Counter32
Max-Access: Read-only
The total number of abnormal disconnections (resulting from a FRMR being received) that have been performed on this SAP since the SAP was created.
Syntax: Counter32
Max-Access: Read-only
The total number of abnormal disconnections (resulting from a timer expiration) that have been performed on this SAP since the SAP was created.
Syntax: Counter32
Max-Access: Read-only
The total number of disconnect mode responses that have been received for CCs in ABM mode on this SAP since the SAP was created.
Syntax: Counter32
Max-Access: Read-only
The total number of SABMEs that have been received for CCs in already in ABM mode on this SAP since the SAP was created.
Syntax: Counter32
Max-Access: Read-only
End of Table
The LLC connection component group contains llcCcAdminTable, llcCcOperTable, and llcCcStatsTable.
This table contains objects that can be changed to manage an LLC connection component. A change to one of these parameters may take effect in the operating link immediately or may wait until the link is restarted depending on the details of the implementation.
The entries in llcCcAdminTable can be created either by an agent or a management station. The management station can create an entry in llcCcAdminTable by setting the appropriate value in llcCcAdminRowStatus.
Most of the objects in this read-create table have corresponding read-only objects in the llcCcOperTable that reflect the current operating value.
The operating values may be different from these configured values if changed by XID negotiation or if a configured parameter was changed after the link was started.
Syntax: SEQUENCE OF LlcCcAdminEntry
Max-Access: Not-accessible
The remote media access control (MAC) address for this connection component. This value is provided by the SNMP agent.
Syntax: MacAddress
Max-Access: Not-accessible
The address of the remote SAP for this Connection Component. This value is provided by the SNMP agent.
Syntax: Integer (1-225)
Max-Access: Not-accessible
This object controls the resetting of the connection component. Setting this value to yes (2) results in the connection component being reset, llcCcOperState transitioning to a value of aDm (1), and the value of llcCcAdminBounce being set back to no (1).
Syntax: Integer 1 = no, 2 = yes
Max-Access: Read-create
The maximum I PDU size, in octets, that this LLC SAP can send to its remote connection component partner. This count is referred to as N1 in the IEEE 802.2 specification.
This object contains an administrative value that is applied the next time this connection is established. A zero value for this object indicates that the SAP default, llcSapAdminMaxIPDUOctetsSend, is used.
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 new cLUW in the llcCcOperMaxIPDUOctetsSend object for the connection component.
The I PDU size includes all octets in a frame, but excludes framing characters, the media access control (MAC) header, and link header.
Syntax: Integer32
Max-Access: Read-create
The maximum consecutive unacknowledged I PDU frames that this LLC can send to its remote LLC partner. This count is referred to as k in the IEEE 802.2 specification.
This object contains an administrative value that is applied the next time this connection is established. A zero value for this object indicates that the SAP default, llcSapAdminMaxUnackedIPDUsSend, is used.
At connection setup, the remote LLC can use an XID frame to send the maximum number of unacknowledged I PDUs that it is prepared to receive. If this occurs, 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 (0-127)
Max-Access: Read-create
The maximum number of unacknowledged I PDUs that this LLC can receive from its remote LLC partner. This count is referred to as k in the IEEE 802.2 specification.
This object contains an administrative value that is applied the next time this connection is established. A zero value for this object indicates that the SAP default, llcSapAdminMaxUnackedIPDUsRcv, is used.
At connection setup, an implementation may choose to send this value to the remote LLC, using an XID frame.
Syntax: Integer (0-127)
Max-Access: Read-create
The maximum number of times that this LLC retries 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.
This object contains an administrative value that is applied the next time this connection is established. A zero value for this object indicates that the SAP default, llcSapAdminMaxRetransmits, is used.
Syntax: Integer32
Max-Access: Read-create
The time interval during which this LLC expects to receive either: an acknowledgment to one or more outstanding I PDUs, or a response PDU to an unnumbered command PDU.
The expiration of this timer causes the unacknowledged frames to be retransmitted (up to N2 times).
This object contains an administrative value that is applied the next time this connection is established. A zero value for this object indicates that the SAP default, llcSapAdminAckTimer, is used.
Syntax: TimeTicks
Max-Access: Read-create
The time interval during which this LLC 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).
This object contains an administrative value that is applied the next time this connection is established. A zero value for this object indicates that the SAP default, llcSapAdminPbitTimer, is used.
Syntax: TimeTicks
Max-Access: Read-create
The time interval during which this LLC expects 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 object contains an administrative value that is applied the next time this connection is established. A zero value for this object indicates that the SAP default, llcSapAdminRejTimer, is used.
Syntax: TimeTicks
Max-Access: Read-create
The time interval during which this LLC expects 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 object contains an administrative value that is applied the next time this connection is established. A zero value for this object indicates that the SAP default, llcSapAdminBusyTimer, is used.
Syntax: TimeTicks
Max-Access: Read-create
The time interval during which this LLC expects 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."
This object contains an administrative value that is applied the next time this connection is established. A zero value for this object indicates that the SAP default, llcSapAdminInactTimer, is used.
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-create
The maximum number of consecutive I PDUs that this LLC receives during the interval defined by llcCcOperDelayTimer without sending an immediate acknowledgment. This must be less than or equal to the value of llcCcOperMaxUnackIPDURcv.
This object contains an administrative value that is applied the next time this connection is established. A zero value for this object indicates that the SAP default, llcSapAdminDelayAck, is used.
A value of 1 indicates that acknowledgments are sent immediately and that the value of llcCcAdminDelayAckTimer is ignored.
Syntax: Integer32
Max-Access: Read-create
The time interval during which this LLC delays 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 contains an administrative value that is applied the next time this connection is established.
This object is associated with the llcCcAdminDelayAckCount object and is only defined if that object has a value greater than 1.
Syntax: TimeTicks
Max-Access: Read-create
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.
Syntax: Integer32
Max-Access: Read-create
This object is used by a management station to create or delete the row entry in llcCcAdminTable.
Upon successful creation of the row, an agent automatically creates a corresponding entry in the llcCcOperTable with llcCcOperState equal to "aDM" (1).
Syntax: RowStatus
Max-Access: Read-create
End of Table
The objects in this table represent operational configuration parameters and status of the LLC2 connections. The values displayed for an LLC2 connection may be different from the values configured on a virtual media access control (MAC) adapter on the CIP because virtual telecommunications access method (VTAM) software can override the router-configured LLC2 parameters.
Syntax: SEQUENCE OF LlcCcOperEntry
Max-Access: Not-accessible
Specifies the operational state of the LLC connection. If the connection component is disabled, llcCcOperState transitions to aDM (1). If the connection component is enabled, llcCcOperState transitions to normal (3).
Syntax: Integer 1 = aDM, 2 = setup, 3 = normal, 4 = busy, 5 = reject, 6 = await, 7 = awaitBusy, 8 = awaitReject, 9 = dConn, 10 = reset, 11 = error, 12 = conn, 13 = resetCheck, 14 = resetWait
Max-Access: Read-only
The maximum I PDU size, in octets, that this LLC SAP can send to its remote connection component partner. This count is referred to as N1 in the IEEE 802.2 specification.
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 may choose to override the administered maximum PDU size with the dynamically learned value and should reflect that new value in this object.
The I PDU size includes all octets in a frame, but excludes framing characters, the media access control (MAC) header and link header.
Syntax: Integer32
Max-Access: Read-only
The maximum I PDU size, in octets, that this LLC can expect to receive from its remote LLC partner. This count is referred to as N1 in the IEEE 802.2 specification.
The I PDU size includes all octets in a frame with the exception of the framing characters, the media access control (MAC) header and the link header.
Syntax: Integer32
Max-Access: Read-only
The maximum consecutive unacknowledged I PDU frames that this LLC can send to its remote LLC partner. This count is referred to as k in the IEEE 802.2 specification.
At connection setup, the remote LLC can send, using an XID frame, the maximum number of unacknowledged I PDUs it is prepared to receive. If so, an implementation can override the administered maximum number of unacknowledged PDUs with the dynamically learned value and should reflect that in this object.
Syntax: Integer (1-127)
Max-Access: Read-only
The maximum number of unacknowledged I PDUs that this LLC can expect to receive from its remote LLC partner. This count is referred to as k in the IEEE 802.2 specification.
Syntax: Integer (1-127)
Max-Access: Read-only
The maximum number of times that this LLC retries 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.
Syntax: Integer32
Max-Access: Read-only
The time interval during which this LLC expects to receive either: an acknowledgment to one or more outstanding I PDUs, or a response PDU to an unnumbered command PDU.
The expiration of this timer causes the unacknowledged frames to be retransmitted (up to N2 times).
Syntax: TimeTicks
Max-Access: Read-only
The time interval during which this LLC 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).
Syntax: TimeTicks
Max-Access: Read-only
The time interval during which this LLC expects to receive a reply to a REJ PDU.
The expiration of this timer causes the REJ PDU to be retransmitted (up to N2 times).
Syntax: TimeTicks
Max-Access: Read-only
The time interval during which this LLC expects 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.
Syntax: TimeTicks
Max-Access: Read-only
The time interval during which this LLC expects 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."
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-only
The maximum number of consecutive I PDUs that this LLC receives during the interval defined by llcCcOperDelayTimer without sending an immediate acknowledgment. This must be less than or equal to the value of llcCcOperMaxUnackIPDURcv.
A value of one indicates that acknowledgments are sent immediately and that the value of llcCcOperDelayAckTimer should be ignored.
Syntax: Integer32
Max-Access: Read-only
The time interval during which this LLC delays 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 llcCcOperDelayAckCount object and only has meaning if that object has a value greater than 1.
Syntax: TimeTicks
Max-Access: Read-only
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.
Syntax: Integer32
Max-Access: Read-only
Maximum number of sequentially numbered IPDUs that the connection component can have outstanding (unacknowledged) at any given time. Ww is initialized to the value of llcCcOperMaxUnackedIPDUsSend when the link is established. When the dynamic window algorithm is invoked, Ww varies from 1 up to llcCcOperMaxUnackedIPDUsSend.
Each time the llcCcOperWw value is decreased, the reason is recorded in llcCcOperLastWwCause, and llcCcStatWwCount is incremented by 1.
Syntax: Integer (1-127)
Max-Access: Read-only
Specifies the value of sysUpTime when this connection was created.
Syntax: TimeStamp
Max-Access: Read-only
Specifies the value of sysUpTime the last time this connection component was modified. If the connection has not been modified, then this value is zero.
Syntax: TimeStamp
Max-Access: Read-only
Specifies the value of sysUpTime when this LLC connection component last failed. If the connection component does not fail, then this value is zero.
Syntax: TimeStamp
Max-Access: Read-only
This enumerated object reflects the cause of the last failure of this LLC connection component. If the connection component has not failed, then this object will have a value of undefined (1).
Syntax: Integer 1 = undefined, 2 = rxFRMR, 3 = txFRMR, 4 = noResponse, 5 = protocolErr, 6 = noActivity, 7 = discReceived, 8 = dmReceived, 9 = retriesExpired
Max-Access: Read-only
The information field of the FRMR frame if the last failure for this LLC connection component was as a result of an invalid frame. Otherwise, this field has no meaning.
Syntax: Octet string
Max-Access: Read-only
The reason that the llcCcOperWw was reduced the last time this occurred.
Syntax: Integer 1 = neverInvoked, 2 = lostData, 3 = macLayerCongestion, 4 = other
Max-Access: Read-only
End of Table
The objects in this table provide statistics for LLC2 connections on the Channel Interface Processor (CIP).
Syntax: SEQUENCE OF LlcCcStatsEntry
Max-Access: Not-accessible
The total number of times that the local LLC connection component has entered a busy state (RNR) since connection component startup. At connection component startup time, this object must be initialized to zero.
Syntax: Counter32
Max-Access: Read-only
The total number of times that an adjacent (remote) LLC connection component has entered a busy state (RNR) since connection component startup. At connection component startup time, this object must be initialized to zero.
Syntax: Counter32
Max-Access: Read-only
The total I-frames received from an adjacent LLC connection component since connection component startup. At connection component startup time, this object must be initialized to zero.
Syntax: Counter32
Max-Access: Read-only
The total I-frames transmitted to an adjacent LLC connection component since connection component startup. At connection component startup time, this object must be initialized to zero.
Syntax: Counter32
Max-Access: Read-only
The total octets contained in I-frames received from an adjacent LLC connection component since connection component startup. At connection component startup time, this object must be initialized to zero.
Syntax: Counter32
Max-Access: Read-only
The total octets contained in I-frames transmitted to an adjacent LLC connection component since connection component startup. At connection component startup time, this object must be initialized to zero.
Syntax: Counter32
Max-Access: Read-only
The total number of S-frames that have been received by this connection component. This object is initialized to zero when the connection component is created.
Syntax: Counter32
Max-Access: Read-only
The total number of S-frames that have been transmitted by this connection component. This object is initialized to zero when the connection component is created.
Syntax: Counter32
Max-Access: Read-only
The total number of I-frames retransmitted by the local connection component. This object is initialized to zero when the connection component is created.
Syntax: Counter32
Max-Access: Read-only
The total REJ frames received from an adjacent LLC connection component since connection component startup.
Syntax: Counter32
Max-Access: Read-only
The total REJ frames transmitted to an adjacent LLC connection component since connection component startup.
Syntax: Counter32
Max-Access: Read-only
The total number of times, since connection component startup, that the dynamic window algorithm has been invoked to reduce the value of Ww. At connection component startup, this object must be initialized to zero.
Syntax: Counter32
Max-Access: Read-only
End of Table
The following notification is supported with the Cisco SNA LLC MIB:
This trap indicates that the state of an LLC connection component has transitioned to normal (3) or aDM (1).
This is the MIB module for objects used to manage the Cisco Snapshot Routing MIB.
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 must 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
The ciscoSnapshotInterfaceTable defines a list of preinterface snapshot routing entries.
Specifies a preinterface 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 protocol data units (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 Simple Network Management Protocol (SNMP) set request or by default, the row status should be set to active to initiate the request.
Syntax: CiscoSnapshotInterfaceEntry
Max-Access: Not-accessible
Specifies the interface to which this entry pertains.
Syntax: InterfaceIndex
Max-Access: Not-accessible
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
Indicates whether snapshot routing on this interface uses dial-on-demand routing.
Syntax: TruthValue
Max-Access: Read-create
Specifies the amount of time in minutes during which routes can be exchanged between the client and server routers.
Syntax: Integer32 (5-1000)
Max-Access: Read-create
Specifies the amount of time in minutes during which routes are retained and frozen between active periods. An instance of this object is present only if the value of the associated ciscoSnapshotClient object is true.
Syntax: Integer32 (8-100000)
Max-Access: Read-create
Specifies the amount of time in minutes during which the router can wait and retry an exchange of routing updates when an active period elapses without such an exchange.
For example, no route exchanges take place during an active interval if an interface is down, a dial-on-demand routing (DDR) phone number is busy, or a DDR interface is unavailable. In this case, the router automatically attempts to exchange routing updates again after the amount of time specified by this object has elapsed, instead of waiting for the amount of time specified by ciscoSnapshotQuietTime.
This value is calculated automatically based on the ciscoSnapshotActiveInterval. An instance of this object is present only if the value of the associated ciscoSnapshotClient object is true.
Syntax: Integer32
Max-Access: Read-only
Specifies the action that takes place when the interface associated with this entry changes to the up state while snapshot routing on the interface is in quiet mode.
A value of goActive causes 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 behavior is useful in a dial-on-demand routing environment.
An instance of this object is present only if the value of the associated ciscoSnapshotClient object is true.
Syntax: Integer 1 = goActive, 2 = noAction
Max-Access: Read-create
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
End of Table
Specifies a list of snapshot routing activity entries.
Syntax: SEQUENCE OF CiscoSnapshotActivityEntry
Max-Access: Not-accessible
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 are deleted.
Syntax: CiscoSnapshotActivityEntry
Max-Access: Not-accessible
Specifies an index value that uniquely identifies a snapshot routing activity entry on a given interface.
Syntax: Integer32
Max-Access: Not-accessible
Specifies the current state of snapshot routing for this entry.
Integer of 1, 2, 3, 4, 5, or 6 representing a routing state as follows:
| 1 = active | Routing information can be exchanged. |
| 2 = quiet | Routers are frozen. No routing information can be exchanged until the router reenters active state. This state is present only in a client snapshot interface. |
| 3 = serverPostActive | The active period has expired; however, routing information is still accepted from--but not sent to--the associated client router. This state is present only on a server shapshot interface. |
| 4 = transitionToQuiet | Any change of the interface from up to down causes a move to the quiet state. This temporary state is present only on a client snapshot interface. |
| 5 = transitionToActive | Any change of the interface from down to up causes a move to the active state. This temporary state is present only on a client snapshot interface. |
| 6 = limbo | A temporary state for activity blocks that are being created or destroyed. |
Max-Access: Read-only
Specifies the time in minutes remaining in the current state.
Syntax: Integer32
Max-Access: Read-only
Specifies the time in minutes during which protocol exchanges occurred in the last active state. The minimum time required for an update exchange to occur in a successful update cycle is 3 minutes, or 1/2 the active time, whichever is greater. If the ciscoSnapshotExchangeTimer is less than this value, the quiet state uses the retry interval to determine when next to go active.
An instance of this object is present only when the associated value of ciscoSnapshotClient is true for this interface.
Syntax: Integer32
Max-Access: Read-only
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 is present only when the associated value of ciscoSnapshotClient is true.
Syntax: Integer32
Max-Access: Read-only
Specifies the protocol of the host that initiated the snapshot routing activity associated with this record. An instance of this object is present only when the associated value of ciscoSnapshotClient is false.
Syntax: CiscoNetworkProtocol
Max-Access: Read-only
Specifies the address of the host that initiated the snapshot routing activity associated with this record. An instance of this object is present only 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 a CiscoNetworkProtocol value of 0. The least significant bit of the first octet represents the protocol associated with a CiscoNetworkProtocol value of 7. The most significant bit of the second octet represents the protocol associated with a 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 present only when the associated value of ciscoSnapshotClient is true.
Syntax: Octet string
Max-Access: Read-only
End of Table
The Cisco SYSLOG Message MIB is used to gather system log messages generated by Cisco IOS software, which generates a variety of textual messages. The Cisco IOS software can be configured to send messages to a SYSLOG server. With the Cisco SYSLOG Message MIB, these same messages can also be retrieved via the SNMP. Messages generated by the Cisco IOS software are called SYSLOG messages.
All Cisco IOS SYSLOG messages have the attributes of timestamp (optional), facility name (where the message came from), severity, message name, and message text. For example, "%SYS-5-CONFIG_I: Configured from console ..." indicates facility = SYS, severity = 5, and message name = CONFIG-I.
The number of clogMessageGenerated notifications that have been sent. If notifications are being received, you can periodically poll this object to determine if any notifications were missed. If they were, you can poll the clogHistoryTable for the missed messages.
Syntax: Counter32
Max-Access: Read-only
Indicates whether clogMessageGenerated notifications are sent when a SYSLOG message is generated by the device. Disabling notifications does not prevent SYSLOG messages from being added to the clogHistoryTable.
Syntax: TruthValue
Max-Access: Read-write
Determines which SYSLOG severity levels are to be processed. Any SYSLOG message with a severity value greater than this value is ignored by the agent. The default value is warning.
Syntax: SyslogSeverity
Max-Access: Read-write
The number of SYSLOG messages that were ignored. A message is ignored if it has a severity value greater than clogMaxSeverity.
Syntax: Counter32
Max-Access: Read-only
The number of SYSLOG messages that could not be processed due to a lack of system resources. This lack of resources is most likely to occur at the same time that SYSLOG messages are generated to indicate a lack of resources. Increases in this object's value might indicate that system resource levels should be examined via other MIB objects. A message that is dropped does not appear in the history table, and no notification is sent for this message.
Syntax: Counter32
Max-Access: Read-only
The upper limit on the number of entries that the clogHistoryTable can contain. A value of 0 prevents any history from being retained. When this table is full, the oldest entry is deleted and a new one created. The default value is 1.
Syntax: Integer32 (0-500)
Max-Access: Read-write
The number of entries that have been removed from the clogHistoryTable to make room for new entries. This object can be used to determine whether the polling frequency on the history table is fast enough or whether the size of the history table is large enough to accommodate all messages generated between polls.
Syntax: Counter32
Max-Access: Read-only
A table of SYSLOG messages generated by this device. All SYSLOG messages for which the severity is less than or equal to clogMaxSeverity are entered into this table.
Syntax: SEQUENCE OF ClogHistoryEntry
Max-Access: Not-accessible
A SYSLOG message that was previously generated by this device. Each entry is indexed by a message index.
Syntax: ClogHistoryEntry
Max-Access: Not-accessible
For the purpose of indexing messages, an integer that increases by a value of 1 for each new message. When it reaches the maximum value, the agent wraps the value back to 1.
Syntax: Integer32 (1-2147483647)
Max-Access: Not-accessible
Name of the facility that generated this message.
Syntax: DisplayString (SIZE (1-20))
Max-Access: Read-only
The severity of the message.
Syntax: SyslogSeverity
Max-Access: Read-only
A textual identification for the message type. A facility name in conjunction with a message name uniquely identifies a message type.
Syntax: DisplayString (SIZE (1-30))
Max-Access: Read-only
The text of the message. If the text of the message exceeds 255 bytes, the message is truncated to 254 bytes and an asterisk (*) character is appended to indicate that the message has been truncated.
Syntax: DisplayString (SIZE (1-255))
Max-Access: Read-only
The value of sysUpTime when this message was generated.
Syntax: TimeStamp
Max-Access: Read-only
End of Table
End of Table
The following notification is supported with the Cisco SYSLOG Message MIB.
When a SYSLOG message is generated by the device, a clogMessageGenerated notification is sent. The sending of these notifications can be enabled or disabled via the clogNotificationsEnabled object.
The variables described in this section provide the necessary information for the definition and management of ciscoTCP objects. The ciscoTCP variables succeed the TCP variables found in the Local Variables subtree.
The ciscoTcpConnTable augments the tcpConnTable defined in RFC 1213. The ciscoTcpConnTable contains TCP connection-specific information.
Specifies the number of bytes input on this TCP connection.
Syntax: Counter32
Max-Access: Read-only
Specifies the number of bytes output on this TCP connection.
Syntax: Counter32
Max-Access: Read-only
Specifies the number of packets input on this TCP connection.
Syntax: Counter32
Max-Access: Read-only
Specifies the number of packets output on this TCP connection.
Syntax: Counter32
Max-Access: Read-only
Specifies the amount of time this TCP connection has been established.
Syntax: TimeTicks
Max-Access: Read-only
Specifies a "smoothed" round-trip time, in milliseconds, for this TCP connection.
Syntax: Integer32
Max-Access: Read-only
End of Table
This variables in this section provide configuration information for the TCP offload feature on the Channel Interface Processor (CIP) in the Cisco router. TCP offload is used on an IBM mainframe (host) that supports TCP. A way to save cycles on the host is to run the TCP/IP stack on the 3172. This offloads the host from protocol processing.
This table contains configuration parameters for the TCP offload feature on the Channel Interface Processor (CIP). Changes to these parameters take effect immediately.
The management station can create an entry in this table by setting the appropriate value in cipCardOffloadConfigRowStatus.
Syntax: SEQUENCE OF CipCardOffloadConfigEntry
Max-Access: Not-accessible
The hex path identifier for the Enterprise System Connection (ESCON) director switch port containing the fiber from the channel on the host to which this CIP Common Link Access for Workstations (CLAW) protocol task connects.
This is a concatenation of the switch port number, the channel logical address (used by the host to associate a logical partition (LPAR) with the control unit), and the control unit logical address (address of a logical control unit used by the host to associate a group of physical devices).
For a directly connected channel, the switch port number is usually 01.
Syntax: Octet string (SIZE (2))
Max-Access: Read-create
The two-digit hex device address for the device the SNA host will use to communicate with the offload task on the CIP. The address must be even.
Syntax: Octet string (SIZE (2))
Max-Access: Read-create
The IP address of the host application for the offload task as specified in the HOME statement of the PROFILE TCPIP.
Syntax: IpAddress
Max-Access: Read-create
The host name parameter as specified in the DEVICE statement of the PROFILE TCPIP.
Syntax: DisplayString (SIZE (1-10))
Max-Access: Read-create
cipCardOffloadConfigRouterName
The workstation name parameter as specified in the DEVICE statement of the mainframe PROFILE TCPIP.
Syntax: DisplayString (SIZE (1-10))
Max-Access: Read-create
cipCardOffloadConfigLinkHostAppl
The name of the application providing the IP link services, as specified in the mainframe configuration.
Syntax: DisplayString (SIZE (1-10))
Max-Access: Read-create
cipCardOffloadConfigLinkRouterAppl
The name of the router application providing the IP link services, as specified in the mainframe configuration.
Syntax: DisplayString (SIZE (1-10))
Max-Access: Read-create
cipCardOffloadConfigAPIHostAppl
The name of the mainframe application providing the application programming interface (API) services, as specified in the mainframe configuration.
Syntax: DisplayString (SIZE (1-10))
Max-Access: Read-create
cipCardOffloadConfigAPIRouterAppl
The name of the router application providing the API services, as specified in the mainframe configuration.
Syntax: DisplayString (SIZE (1-10))
Max-Access: Read-create
cipCardOffloadConfigBroadcastEnable
Controls processing of broadcast frames for the path/device that this instance of offload is configured on. Enable turns broadcast processing on.
Syntax: TruthValue
Max-Access: Read-create
This object is used by a management station to create or delete the row entry in cipCardOffloadConfigTable.
Syntax: RowStatus
Max-Access: Read-create
End of Table
The variables in this section are used to manage TN3270 servers.
A list of TN3270 server and dependent LU requester (DLUR) global information.
Syntax: SEQUENCE OF Tn3270sGlobalEntry
Max-Access: Not-accessible
Parameters values for a group.
Syntax: Tn3270sGlobalEntry
Max-Access: Not-accessible
Index used to uniquely identify each TN3270 server instance. This index value is not reused when the server is shut down and a new instance invoked.
Syntax: Tn3270sUnsigned32
Max-Access: Not-accessible
The identity of the card running the server.
Syntax: Tn3270sCpuCard
Max-Access: Read-only
The maximum number of logical units (LUs) supported by the server.
Syntax: Tn3270sUnsigned32 (1-65535)
Max-Access: Read-only
The number of LUs currently in use on the server.
Syntax: Gauge32 (0-65535)
Max-Access: Read-only
The timestamp that the TN3270 server started.
Syntax: TimeStamp
Max-Access: Read-only
The default TCP port of this TN3270 server that is inherited by the physical unit (PU) if it does not have a TCP port explicitly defined in the router configuration for this PU.
Syntax: Tn3270sTCPPort
Max-Access: Read-only
The number of seconds of LU inactivity (from either host or client) before the TN3270 session is disconnected. Zero seconds means that LU sessions by default are not disconnected when inactive, regardless of the amount of idle time spent.
Syntax: Integer (0-65534)
Max-Access: Read-only
The number of seconds of inactivity from the client side that the TN3270 server allows to elapse before sending a DO-TIMING-MARK request to the TN3270 client. If the client does not reply within 30 minutes of such a request being sent, the server disconnects the TN3270 session. Zero seconds indicates that no keepalives will be sent.
Syntax: Integer (0-65534)
Max-Access: Read-only
Indicates whether a TN3270 session is disconnected upon an UNBIND request.
The keep value indicates that no automatic disconnection is made by the server upon receipt of an UNBIND, while disconnect indicates that the session is disconnected upon receipt of an UNBIND.
Syntax: Integer 1 = keep, 2 = disconnect
Max-Access: Read-only
Indicates whether "leftover" LUs are made available to TN3270 sessions that do not request a specific LU or LU pool.
A leftover LU is one for which all of the following conditions are true:
The deny value indicates that the leftover LUs are not given to a generic pool so that the PU is not automatically fully populated with 255 local address definitions.
The permit value indicates that leftover LUs are made available to TN3270 users who want "generic" sessions. All LUs in the generic pool are by definition DDDLU capable.
Syntax: Integer 1 = permit, 2 = deny
Max-Access: Read-only
Indicates whether to send a timing mark to solicit a response before sending a response to the host. The value true indicates that a timing mark is sent, while false indicates that it is not sent.
By using a timing mark, an application can determine the response time from the client. Some existing clients do not implement the timing mark correctly and will not work with this server if this parameter is set to true.
Syntax: TruthValue
Max-Access: Read-only
End of Table
A list of statistics for each TN3270 server's listening IP address-TCP port pair.
Syntax: SEQUENCE OF Tn3270sStatsEntry
Max-Access: Not-accessible
Parameters that describe the statistics of the IP stacks.
Syntax: Tn3270sStatsEntry
Max-Access: Not-accessible
The IP address of this TN3270 server listen endpoint.
Syntax: IpAddress
Max-Access: Not-accessible
The TCP port in this TN3270 server listen endpoint.
Syntax: Tn3270sTCPPort
Max-Access: Not-accessible
Number of TN3270 sessions configured that are available to be used by TN3270 clients.
Syntax: Gauge32
Max-Access: Read-only
Spare number of TN3270 sessions available for connection at query time.
Syntax: Gauge32
Max-Access: Read-only
Total number of TN3270 session Connects-in received.
Syntax: Counter32
Max-Access: Read-only
Total number of TN3270 sessions disconnected.
Syntax: Counter32
Max-Access: Read-only
tn3270sStatsTN3270ConnectsFailed
Total number of attempted sessions that failed to negotiate TN3270/E or were rejected by the control point.
Syntax: Counter32
Max-Access: Read-only
tn3270sStatsInboundTransactions
Total number of inbound transactions--identified by an end-of-record (EOR) identifier-- processed.
Syntax: Counter32
Max-Access: Read-only
tn3270sStatsOutboundTransactions
Total number of outbound transactions --identified by an end-of-record (EOR) identifier-- processed.
Syntax: Counter32
Max-Access: Read-only
tn3270sStatsSampledInboundTransactions
Total number of sampled inbound transactions--identified by an end-of-record (EOR) identifier--on which response time is computed since the TN3270 server last restarted its listening IP address-TCP port pair.
Syntax: Counter32
Max-Access: Read-only
tn3270sStatsNetSampledInboundTransactionRespTime
Total response time for all sampled inbound transactions for which response time is computed. The average response time is calculated by the division of this value by the value of tn3270sStatsSampledInboundTransactions.
Syntax: Tn3270sUnsigned32
Max-Access: Read-only
tn3270sStatsSampledOutboundTransactions
Total number of sampled outbound transactions--identified by an end-of-record (EOR) identifier--on which response time is computed.
Syntax: Counter32
Max-Access: Read-only
tn3270sStatsNetSampledOutboundTransactionRespTime
Total response time for all sampled outbound transactions on which response time is computed. The average outbound response time is calculated by the division of this value by the value of tn3270sStatsSampledOutboundTransactions.
Syntax: Tn3270sUnsigned32
Max-Access: Read-only
End of Table
This table contains objects that are PU configuration parameters not defined in the network addressable unit (NAU) MIB, Advanced Peer-to-Peer Networking (APPN) MIB, or dependent LU requestor (DLUR) MIB.
Syntax: SEQUENCE OF Tn3270sPuEntry
Max-Access: Not-accessible
A list of TN3270 server PU parameters.
Syntax: Tn3270sPuEntry
Max-Access: Not-accessible
Index used to uniquely identify each node instance. This index is the same as snaNodeAdminIndex in the network addressable unit (NAU) MIB.
Syntax: Tn3270sPUIndex
Max-Access: Not-accessible
The IP address of this TN3270 server.
Syntax: IpAddress
Max-Access: Read-only
The TCP port of this TN3270 server's Telnet session.
Syntax: Tn3270sTCPPort
Max-Access: Read-only
The number of seconds of LU inactivity (from either host or client) before the TN3270 session is disconnected. Zero seconds means that LU sessions, by default, are not disconnected when inactive, regardless of the amount of idle time spent.
The value 65535 (not valid in server context) indicates that the idle time value must be taken from the server context.
Syntax: Integer (0-65535)
Max-Access: Read-only
The number of seconds of inactivity from the client side that the TN3270 server allows to elapse before sending a DO-TIMING-MARK request to the TN3270 client. If the client does not reply within 30 minutes of such a TIMING-MARK request being sent, the server disconnects the TN3270 session. Zero seconds indicates that no keepalives will be sent.
The value 65535 (not valid in server context) indicates that the default keepalive value for an LU is taken from the value defined in the server context for this Channel Interface Processor (CIP) card.
Syntax: Integer (0-65535)
Max-Access: Read-only
This variable indicates whether a TN3270 session will be disconnected upon receipt of an UNBIND request.
The value keep indicates that no automatic disconnection is made by the server upon receipt of an UNBIND; disconnect indicates that the session will be disconnected upon receipt of an UNBIND; inherit indicates that the default keepalive value of an LU is taken from whatever value had been defined in the server context for this Channel Interface Processor (CIP) card.
Syntax: Integer 1 = keep, 2 = disconnect, 3 = inherit
Max-Access: Read-only
This variable indicates whether leftover LUs are made available to TN3270 sessions that do not request a specific LU or LU pool.
A leftover LU is one for which all of the following conditions are true:
The value inherit indicates that the value of tn3270sPuGenericPool is the same as tn3270sGlobalGenericPool. The value deny indicates that the leftover LUs are not given to a generic pool so that the PU is not automatically fully populated with 255 local address definitions. The value permit indicates that leftover LUs should be made available to TN3270 users who want "generic" sessions. All LUs in the generic pool are by definition DDDLU capable.
Syntax: Integer 1 = permit, 2 = deny, 3 = inherit
Max-Access: Read-only
The current PU state. This variable has a different meaning for a direct or dependent LU requestor (DLUR) PU before a link station is established. For a DLUR PU, the PU is in a reset state; for a direct PU the state is either test or xid.
Integer of 1, 2, 3, 4, 5, 6, 7, or 8 representing a PU state, as follows:
| 1 = shut | The PU is configured but in shut state. |
| 2 = reset | The link station of this PU is not active. |
| 3 = inactive | The PU is not activated, and the link station or DLUR state is unknown. |
| 4 = test | The PU is sending a TEST message to establish link. |
| 5 = xid | The TEST message is responded to and an XID message is sent. |
| 6 = pActpu | The link station is up, but no ACTPU (activate physical unit) request is received. |
| 7 = active | An ACTPU is received and acknowledged positively. |
| 8 = actBusy | The PU is waiting for the host to acknowledge the system services control point (SSCP)-PU data. |
Max-Access: Read-only
Defines whether the connection to the host is via dependent LU requester (DLUR) or a direct link. If the connection is via a DLUR, the LU name prefix (LU seed), and local and remote media access control point (MAC) or service access point (SAP) addresses on this table are undefined.
Syntax: Integer 1 = dlur, 2 = direct
Max-Access: Read-only
For a direct PU, this variable defines the LU name prefix (LU seed) that is concatenated with the local address to form a unique name.
Syntax: DisplayString ( SIZE ( 1-6 ) )
Max-Access: Read-only
Service access point (SAP) address of the local direct PU.
Syntax: Integer (1-254)
Max-Access: Read-only
Service access point (SAP) address of the remote PU, valid for a direct PU only.
Syntax: Integer (1-254)
Max-Access: Read-only
Media access control (MAC) address of the remote PU, valid for a direct PU only.
Syntax: MacAddress
Max-Access: Read-only
End of Table
A list of IP-to-LU mapping entries.
Syntax: SEQUENCE OF Tn3270sIpEntry
Max-Access: Not-accessible
A list of entries to relate a client IP address to the LU.
Syntax: Tn3270sIpEntry
Max-Access: Not-accessible
The IP address of the TN3270 client.
Syntax: IpAddress
Max-Access: Not-accessible
The TCP port of the TN3270 client.
Syntax: Tn3270sTCPPort
Max-Access: Not-accessible
The PU index associated with network addressable unit (NAU) and PU objects.
Syntax: Tn3270sPUIndex
Max-Access: Read-only
The LU index associated with network addressable unit (NAU) and LU objects.
Syntax: Tn3270sLUIndex
Max-Access: Read-only
End of Table
This table contains objects that help map an LU to a client IP-port pair. It also provides other useful parameters not available elsewhere.
Syntax: SEQUENCE OF Tn3270sLuEntry
Max-Access: Not-accessible
Parameters values for a group.
Syntax: Tn3270sLuEntry
Max-Access: Not-accessible
Index used to uniquely identify each PU instance. This object is the same as snaNodeAdminIndex in the network addressable unit (NAU) MIB.
Syntax: Tn3270sPUIndex
Max-Access: Not-accessible
Index used to uniquely identify the LU instance within a PU.
Syntax: Tn3270sLUIndex
Max-Access: Not-accessible
The IP address of the TN3270 client connected to this LU.
Syntax: IpAddress
Max-Access: Read-only
The TCP port of the TN3270 client connected to this LU.
Syntax: Tn3270sTCPPort
Max-Access: Read-only
Indicates whether the TN3270 session negotiated is TN3270, TN3270E, or never connected.
Syntax: Integer 1 = tn3270, 2 = tn3270e, 3 = neverConnect
Max-Access: Read-only
Terminal type or model number of the incoming TN3270 client.
Syntax: DisplayString ( SIZE ( 1-17 ) )
Max-Access: Read-only
The value identifies the current LU state.
Integer of 1, 2, 3, 4, 5, 6, 7, 8, 9, 10, 11, 12, or 13 representing an LU state, as follows:
| 1 = inactive | LU did not receive an ACTLU (activate local unit) request. |
| 2 = active | LU received an ACTLU and acknowledged positively. |
| 3 = pSdt | LU is bound but has no SDT (start data traffic) message yet. |
| 4 = act/session | LU is bound and in session. |
| 5 = pActlu | Telnet connected in and is waiting for an ACTLU. |
| 6 = pNotifyAv | LU waiting for notification from the host of its availability. |
| 7 = pNotifyUa | LU waiting for notification from the host that it is unavailable. |
| 8 = pReset | LU waiting for a buffer to send a DACTLU (deactivate logical unit) response. |
| 9 = pPsid | LU waiting for a network management vector transport (NMVT) Reply PSID response. |
| 10 = pBind | LU waiting for host to send a bind request. |
| 11 = pUnbind | LU waiting for host unbind response. |
| 12 = unbindWt | LU waiting for client to acknowledge disconnection. |
| 13 = sdtWt | LU waiting for client to acknowledge SDT. |
Max-Access: Read-only
The number of inbound frames allowed to be sent to the host without receipt of a pacing response from the host.
Syntax: Integer (0-63)
Max-Access: Read-only
The number of inbound frames queued and waiting for a host pacing response. The inbound data is queued after inbound pacing credit is exhausted.
Syntax: Integer (0-63)
Max-Access: Read-only
The number of TCP packets in the server queued for transmission to the client.
Syntax: Integer (0-63)
Max-Access: Read-only
Time since last activity was recorded on this LU.
Syntax: Integer (0-65535)
Max-Access: Read-only
Indicates whether LU is dynamic or static.
The value dynamic indicates that the LU is configured as a dynamic definition of dependent LU (DDDLU). The value static indicates that the LU is configured as specific. The host sends an ACTLU (activate logical unit) request as soon as the PU is active.
Syntax: Integer 1 = dynamic, 2 = static
Max-Access: Read-only
The link index into the Advanced Peer-to-Peer Networking (APPN) MIB for the link on which bind flowed. This object is valid only for a dependent LU requester (DLUR) LU.
Syntax: Integer (0-65535)
Max-Access: Read-only
The session identifier on a PU 2.1 link.
Syntax: Integer (0-65535)
Max-Access: Read-only
Time at which the last data was logged for this LU.
Syntax: TimeStamp
Max-Access: Read-only
An array of octets indicating the latest events that happened in this LU. Octet 1 is the most recent event, octet 2 the next most recent, and so on. Although the maximum number of events kept is 16, the actual number of events kept can be lower. When more events are generated than are kept, the oldest ones are discarded.
Events are encoded as follows:
| 1 | Inactivity timer expired. |
| 2 | Dynamic timer expired. |
| 3 | ACTLU (activate logical unit) request received from host. |
| 4 | Bind request received from host. |
| 5 | Clear request received from host. |
| 6 | DACTLU (deactivate logical unit) request received from host. |
| 7 | Hierarchical reset request received from PU (warn ACTPU). |
| 8 | SDT request received from host. |
| 9 | Unbind request received from host. |
| 10 | Notify response received from host. |
| 11 | Reply PSID negative response from host received. |
| 12 | Reply PSID positive response from host received. |
| 13 | Unbind response from host received. |
| 14 | Hierarchical reset request received from PU. |
| 15 | Connection request received from client. |
| 16 | Disconnection request received from client. |
| 17 | Timing-mark response received from client. |
| 18 | Flow-control timer expired. |
| 19 | Negative response sent to host. |
| 20 | Negative response received from host. |
| 21 | Data contention happened. |
| 22 | No buffer is available for the LU to send a response. |
| 23 | SNA response received while inbound. |
Syntax: Octet String ( SIZE ( 0-16 ) )
Max-Access: Read-only
End of Table
The MIB module in this section describes the management of VINES routing information in Cisco devices.
Specifies the VINES network number of this router.
Syntax: VinesNetworkNumber
Max-Access: Read-only
Specifies the VINES host (subnetwork) number of this router.
Syntax: VinesHostNumber
Max-Access: Read-only
Specifies the next VINES client host (subnetwork) number to be assigned by this router.
Syntax: VinesHostNumber
Max-Access: Read-only
The Cisco VINES Neighbor table contains the objects listed in this section.
Specifies the number of neighbors in the neighbor table, cvForwNeighborTable.
Syntax: Gauge32
Max-Access: Read-only
Specifies the number of paths in the neighbor table, cvForwNeighborTable.
Syntax: Gauge32
Max-Access: Read-only
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
Specifies a table of information about neighbors of this router.
Syntax: SEQUENCE OF CvForwNeighborEntry
Max-Access: Not-accessible
Specifies the network part of the neighbor's VINES internet address.
Syntax: VinesNetworkNumber
Max-Access: Not-accessible
Specifies the host part of the neighbor's VINES internet address.
Syntax: VinesHostNumber
Max-Access: Not-accessible
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
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
Specifies the version of RTP through which the entry was learned.
Syntax: Integer32 (0-255)
Max-Access: Read-only
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
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
Specifies the expected one-way delay to send a message to this neighbor.
Syntax: VinesMetric
Max-Access: Read-only
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
The VINES Route table contains the objects specified in this section.
Specifies the number of routers (servers) in the route table, cvForwRouteTable.
Syntax: Gauge32
Max-Access: Read-only
Specifies the number of routes in the route table, cvForwRouteTable.
Syntax: Gauge32
Max-Access: Read-only
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
Specifies the number of seconds until the next routing update.
Syntax: Gauge32
Max-Access: Read-only
Specifies a table of information about routes from this router to other VINES networks.
Syntax: SEQUENCE OF CvForwRouteEntry
Max-Access: Not-accessible
Specifies the remote network's VINES network number.
Syntax: VinesNetworkNumber
Max-Access: Not-accessible
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
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
Specifies the version of RTP through which the entry was learned.
Syntax: Integer32 (0-255)
Max-Access: Read-only
Specifies whether this route is the one to use next to get to the remote network.
Syntax: TruthValue
Max-Access: Read-only
Specifies whether this route will be used to forward a broadcast from a serverless network.
Syntax: TruthValue
Max-Access: Read-only
Specifies whether this route is temporarily being suppressed as normal operation before eventually advertising it.
Syntax: TruthValue
Max-Access: Read-only
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
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
Specifies the expected one-way delay, in milliseconds, to send a message on this route.
Syntax: VinesMetric
Max-Access: Read-only
Specifies the number of times the route has been used to forward a message.
Syntax: Counter32
Max-Access: Read-only
End of Table
The global total counters used by the Cisco VINES MIB contains objects listed in this section.
Specifies the total count of number of VINES input packets.
Syntax: Counter32
Max-Access: Read-only
Specifies the total count of number of VINES output packets.
Syntax: Counter32
Max-Access: Read-only
Specifies the total count of VINES input packets for this host.
Syntax: Counter32
Max-Access: Read-only
Specifies the total count of number of VINES packets forwarded.
Syntax: Counter32
Max-Access: Read-only
Specifies the total count of number of VINES input broadcast packets.
Syntax: Counter32
Max-Access: Read-only
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
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
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
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
Specifies the total count of VINES input packets with header errors.
Syntax: Counter32
Max-Access: Read-only
Specifies the total count of VINES input packets with checksum errors.
Syntax: Counter32
Max-Access: Read-only
Specifies the total count of VINES input packets that have exceeded the maximum hop count.
Syntax: Counter32
Max-Access: Read-only
Specifies the total count of VINES packets dropped due to no route.
Syntax: Counter32
Max-Access: Read-only
Specifies the total count of VINES packets dropped due to output encapsulation failed.
Syntax: Counter32
Max-Access: Read-only
Specifies the total count of unknown VINES input packets.
Syntax: Counter32
Max-Access: Read-only
Specifies the total count of VINES ICP packets received.
Syntax: Counter32
Max-Access: Read-only
Specifies the total count of VINES ICP packets generated.
Syntax: Counter32
Max-Access: Read-only
Specifies the total count of VINES ICP Metric Notification packets generated.
Syntax: Counter32
Max-Access: Read-only
Specifies the total count of VINES media access control (MAC) level Echo packets received.
Syntax: Counter32
Max-Access: Read-only
Specifies the total count of VINES media access control (MAC) level Echo packets generated.
Syntax: Counter32
Max-Access: Read-only
Specifies the total count of VINES Echo packets received.
Syntax: Counter32
Max-Access: Read-only
Specifies the total count of VINES Echo packets generated.
Syntax: Counter32
Max-Access: Read-only
Specifies the total count of proxy packets sent.
Syntax: Counter32
Max-Access: Read-only
Specifies the total count of responses to proxy packets.
Syntax: Counter32
Max-Access: Read-only
The Interface Configuration table (cvInterface) contains the objects listed in this section.
Specifies the VINES protocol metric value.
Syntax: VinesMetric
Max-Access: Read-only
Specifies the VINES protocol default encapsulation.
Syntax: Integer 1 = ARPA, 2 = TokenRing, 3 = SNAP
Max-Access: Read-only
Specifies the VINES protocol outgoing access list number.
Syntax: Integer32
Max-Access: Read-only
Specifies the VINES protocol propagation control.
Syntax: Integer 1 = never, 2 = always, 3 = dynamic
Max-Access: Read-only
Specifies the VINES protocol arp replies enabled.
Syntax: Integer 1 = never, 2 = always, 3 = dynamic
Max-Access: Read-only
Specifies that VINES protocol serverless support is enabled.
Syntax: Integer 1 = never, 2 = dynamic, 3 = always, 4 = alwaysBroadcast
Max-Access: Read-only
Specifies the VINES protocol redirect interval in milliseconds.
Syntax: Integer32
Max-Access: Read-only
Specifies that the VINES protocol split horizon is disabled.
Syntax: TruthValue
Max-Access: Read-only
Specifies whether the VINES protocol line is up or down.
Syntax: TruthValue
Max-Access: Read-only
Specifies whether the VINES protocol fast switching is supported.
Syntax: TruthValue
Max-Access: Read-only
Specifies whether the VINES protocol fast switching was requested.
Syntax: TruthValue
Max-Access: Read-only
Specifies the VINES protocol filter on received routing information source address.
Syntax: Integer32
Max-Access: Read-only
Specifies the VINES protocol filter on received routing information content.
Syntax: Integer32
Max-Access: Read-only
Specifies the VINES protocol filter on transmitted routing information content.
Syntax: Integer32
Max-Access: Read-only
End of Table
The Interface Input Counter table (cvIfCountInTable) contains the objects listed in this section.
Specifies the VINES protocol count of input packets that were discarded because the interface was not configured.
Syntax: Counter32
Max-Access: Read-only
Specifies the VINES protocol count of input packets with format errors.
Syntax: Counter32
Max-Access: Read-only
Specifies the VINES protocol count of input packets destined for this router.
Syntax: Counter32
Max-Access: Read-only
Specifies the VINES protocol input broadcast count.
Syntax: Counter32
Max-Access: Read-only
Specifies the VINES protocol count of input packets forwarded to another interface.
Syntax: Counter32
Max-Access: Read-only
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
Specifies the VINES protocol count of input packets that were dropped due to a zero hop count.
Syntax: Counter32
Max-Access: Read-only
Specifies the VINES protocol count of input packets with checksum errors.
Syntax: Counter32
Max-Access: Read-only
Specifies the VINES protocol count of input ARP Query Request messages.
Syntax: Counter32
Max-Access: Read-only
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
Specifies the VINES protocol count of input illegal ARP messages.
Syntax: Counter32
Max-Access: Read-only
Specifies the VINES protocol count of input ICP error messages.
Syntax: Counter32
Max-Access: Read-only
Specifies the VINES protocol count of input ICP metric messages.
Syntax: Counter32
Max-Access: Read-only
Specifies the VINES protocol count of input illegal ICP messages.
Syntax: Counter32
Max-Access: Read-only
Specifies the VINES protocol count of input IPC messages.
Syntax: Counter32
Max-Access: Read-only
Specifies the VINES protocol count of input RTP type 0 messages.
Syntax: Counter32
Max-Access: Read-only
Specifies the VINES protocol count of input RTP Request messages.
Syntax: Counter32
Max-Access: Read-only
Specifies the VINES protocol count of input RTP type 2 messages.
Syntax: Counter32
Max-Access: Read-only
Specifies the VINES protocol count of input RTP type 3 messages.
Syntax: Counter32
Max-Access: Read-only
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
Specifies the VINES protocol count of input illegal RTP messages.
Syntax: Counter32
Max-Access: Read-only
Specifies the VINES protocol count of input SPP messages.
Syntax: Counter32
Max-Access: Read-only
Specifies the VINES protocol count of input packets of unknown VINES protocols.
Syntax: Counter32
Max-Access: Read-only
Specifies the VINES protocol count of input packets of unknown VINES IPC ports.
Syntax: Counter32
Max-Access: Read-only
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
Specifies the VINES protocol count of input IPC echo messages.
Syntax: Counter32
Max-Access: Read-only
Specifies the VINES protocol count of input media access control (MAC) layer echo frames.
Syntax: Counter32
Max-Access: Read-only
Specifies the VINES protocol count of responses to proxy packets.
Syntax: Counter32
Max-Access: Read-only
End of Table
The VINES Interface Output Counter table (cvIfCountOutTable) contains the objects in this section.
Specifies the VINES protocol unicast packets generated.
Syntax: Counter32
Max-Access: Read-only
Specifies the VINES protocol broadcast packets generated.
Syntax: Counter32
Max-Access: Read-only
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
Specifies the VINES protocol output access list failures.
Syntax: Counter32
Max-Access: Read-only
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
Specifies the VINES protocol count of output ARP Query Request messages.
Syntax: Counter32
Max-Access: Read-only
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
Specifies the VINES protocol count of output IPC Error messages.
Syntax: Counter32
Max-Access: Read-only
Specifies the VINES protocol count of output IPC metric messages.
Syntax: Counter32
Max-Access: Read-only
Specifies the VINES protocol count of output ICP messages.
Syntax: Counter32
Max-Access: Read-only
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
Specifies the VINES protocol count of output RTP type 2 messages.
Syntax: Counter32
Max-Access: Read-only
Specifies the VINES protocol count of output RTP type 3 messages.
Syntax: Counter32
Max-Access: Read-only
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
Specifies the VINES protocol count of output SPP messages.
Syntax: Counter32
Max-Access: Read-only
Specifies the VINES protocol count of output IPC echo messages.
Syntax: Counter32
Max-Access: Read-only
Specifies the VINES protocol count of output IPCMAC layer echo frames.
Syntax: Counter32
Max-Access: Read-only
Specifies the VINES protocol count of proxy packets sent.
Syntax: Counter32
Max-Access: Read-only
End of Table
The QLLC MIB includes a managed entity or link station (LS). The managed entity includes objects needed to configure and monitor the logical connections.
This table contains objects that can be changed for each QLLC entry. Changing one of these parameters will take effect in the operating link station immediately. Each QLLC connection will have an entry in this table.
Syntax: SEQUENCE OF QllcLSAdminEntry
Access: Not-accessible
Specifies the interface index value for the QLLC connection.
Syntax: IfIndexType
Max-Access: Read-write
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
Specifies the circuit type on this interface.
Syntax: Integer 1 = switchedVC, 2 = permanentVC
Max-Access: Read-write
Specifies the role that the QLLC link station shall assume.
Syntax: Integer 1 = primary, 2 = secondary, 3 = peerToPeer
Max-Access: Read-write
Specifies the X.25 address associated with the QLLC connection.
Syntax: X121Address
Max-Access: Read-write
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
Specifies the largest QLLC packet allowed to go out on the QLLC/X.25 side.
Syntax: Integer32
Max-Access: Read-write
End of Table
Specifies an entry for each QLLC connection.
Specifies the interface index value for the QLLC connection.
Syntax: IfIndexType
Max-Access: Read-only
Specifies the virtual circuit number for the logical channel identifier on this interface.
Syntax: IfIndexType
Max-Access: Read-only
Specifies the circuit type on this interface.
Syntax: Integer 1 = switchedVC, 2 = permanentVC
Max-Access: Read-only
Specifies the role of the QLLC link station.
Syntax: Integer 1 = primary, 2 = secondary, 3 = peerToPeer
Max-Access: Read-only
Specifies the remote X.25 address associated with the QLLC connection.
Syntax: X121Address
Max-Access: Read-only
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
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
Specifies the largest QLLC packet allowed to go out on the QLLC/X.25 side.
Syntax: Integer32
Max-Access: Read-only
End of Table
The qllcLSStatsTable defines link station statistics kept for each QLLC connection.
Specifies the link station statistics.
Syntax: QllcLSStatsEntry
Max-Access: Not-accessible
Specifies the interface index value for the QLLC connection.
Syntax: IfIndexType
Max-Access: Read-only
Specifies the virtual circuit number for the logical channel identifier on this interface.
Syntax: IfIndexType
Max-Access: Read-only
Specifies the number of XIDs received from the link station on this virtual circuit.
Syntax: Counter32
Max-Access: Read-only
Specifies the number of XIDs sent to the link station on this virtual circuit.
Syntax: Counter32
Max-Access: Read-only
Specifies the number of TEST packets received from the link station on this virtual circuit.
Syntax: Counter32
Max-Access: Read-only
Specifies the number of TEST packets sent to the link station from this virtual circuit.
Syntax: Counter32
Max-Access: Read-only
Specifies the number of times the connection quenched off for this connection.
Syntax: Counter32
Max-Access: Read-only
Specifies the number of times the connection quenched on for this connection.
Syntax: Counter32
Max-Access: Read-only
Specifies the total number of information packets received on this interface.
Syntax: Counter32
Max-Access: Read-only
Specifies the total number of information packets sent on this interface.
Syntax: Counter32
Max-Access: Read-only
Specifies the total number of bytes in the information packets received on this connection.
Syntax: Counter32
Max-Access: Read-only
Specifies the total number of bytes in the information packets sent on this connection.
Syntax: Counter32
Max-Access: Read-only
Specifies the number of QSMs received on this connection.
Syntax: Counter32
Max-Access: Read-only
Specifies the number of QSMs sent on this connection.
Syntax: Counter32
Max-Access: Read-only
Specifies the number of DISCs received on this connection.
Syntax: Counter32
Max-Access: Read-only
Specifies the number of DISCs sent on this connection.
Syntax: Counter32
Max-Access: Read-only
Specifies the number of DMs received on this connection.
Syntax: Counter32
Max-Access: Read-only
Specifies the number of DMs sent on this connection.
Syntax: Counter32
Max-Access: Read-only
Specifies the number of FRMRs received on this connection.
Syntax: Counter32
Max-Access: Read-only
Specifies the number of FRMRs sent on this connection.
Syntax: Counter32
Max-Access: Read-only
Specifies the number of packets dropped due to buffer allocation or other internal problems.
Syntax: Counter32
Max-Access: Read-only
Specifies the number of HDLC protocol errors detected.
Syntax: Counter32
Max-Access: Read-only
End of Table
This group specifies a collection of objects providing configuration capability.
Specifies the interface index value for the QLLC connection.
Syntax: IfIndexType
Max-Access: Read-write
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
Specifies the circuit type on this interface.
Syntax: Integer 1 = switchedVC, 2 = permanentVC
Max-Access: Read-write
Specifies the role that the QLLC link station assumes.
Syntax: Integer 1 = primary, 2 = secondary, 3 = peerToPeer
Max-Access: Read-write
Specifies the X.25 address associated with the QLLC connection.
Syntax: X121Address
Max-Access: Read-write
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
Specifies the largest QLLC packet allowed to go out on the QLLC/X.25 side.
Syntax: Integer32
Max-Access: Read-write
This group specifies a collection of objects providing operational control capability.
Specifies the interface index value for the QLLC connection.
Syntax: IfIndexType
Max-Access: Read-only
Specifies the virtual circuit number for the logical channel identifier on this interface.
Syntax: IfIndexType
Max-Access: Read-only
Specifies the circuit type on this interface.
Syntax: Integer 1 = switchedVC, 2 = permanentVC
Max-Access: Read-only
Specifies the role of the QLLC link station.
Syntax: Integer 1 = primary, 2 = secondary, 3 = peerToPeer
Max-Access: Read-only
Specifies the remote X.25 address associated with the QLLC connection.
Syntax: X121Address
Max-Access: Read-only
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
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
Specifies the largest QLLC packet allowed to go out on the QLLC/X.25 side.
Syntax: Integer32
Max-Access: Read-only
This group specifies a collection of objects providing statistics.
Specifies the link station statistics.
Syntax: QllcLSStatsEntry
Max-Access: Not-accessible
Specifies the interface index value for the QLLC connection.
Syntax: IfIndexType
Max-Access: Read-only
Specifies the virtual circuit number for the logical channel identifier on this interface.
Syntax: IfIndexType
Max-Access: Read-only
Specifies the number of XIDs received from the link station on this virtual circuit.
Syntax: Counter32
Max-Access: Read-only
Specifies the number of XIDs sent to the link station on this virtual circuit.
Syntax: Counter32
Max-Access: Read-only
Specifies the number of TEST packets received from the link station on this virtual circuit.
Syntax: Counter32
Max-Access: Read-only
Specifies the number of TEST packets sent to the link station from this virtual circuit.
Syntax: Counter32
Max-Access: Read-only
Specifies the number of times the connection quenched off for this connection.
Syntax: Counter32
Max-Access: Read-only
Specifies the number of times the connection quenched on for this connection.
Syntax: Counter32
Max-Access: Read-only
Specifies the total number of information packets received on this interface.
Syntax: Counter32
Max-Access: Read-only
Specifies the total number of information packets sent on this interface.
Syntax: Counter32
Max-Access: Read-only
Specifies the total number of bytes in the information packets received on this connection.
Syntax: Counter32
Max-Access: Read-only
Specifies the total number of bytes in the information packets sent on this connection.
Syntax: Counter32
Max-Access: Read-only
Specifies the number of QSMs received on this connection.
Syntax: Counter32
Max-Access: Read-only
Specifies the number of QSMs sent on this connection.
Syntax: Counter32
Max-Access: Read-only
Specifies the number of DISCs received on this connection.
Syntax: Counter32
Max-Access: Read-only
Specifies the number of DISCs sent on this connection.
Syntax: Counter32
Max-Access: Read-only
Specifies the number of DMs received on this connection.
Syntax: Counter32
Max-Access: Read-only
Specifies the number of DMs sent on this connection.
Syntax: Counter32
Max-Access: Read-only
Specifies the number of FRMRs received on this connection.
Syntax: Counter32
Max-Access: Read-only
Specifies the number of FRMRs sent on this connection.
Syntax: Counter32
Max-Access: Read-only
Specifies the number of packets dropped due to buffer allocation or other internal problems.
Syntax: Counter32
Max-Access: Read-only
Specifies the number of HDLC protocol errors detected.
Syntax: Counter32
Max-Access: Read-only
The Qualified Logical Link Control (QLLC) SNA conversion group provides data link layer support for SNA communication. The QLLC SNA Conversion 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:
The permissions allowed on these objects are as follows:
This is the MIB module for objects used to manage QLLC-to-SDLC and QLLC-to-LLC2 conversion.
This table contains objects that can be changed for each QLLC entry. A change to one of these parameters will take effect in the operating link station immediately. Each QLLC connection will have an entry in this table.
Syntax: SEQUENCE OF ConvQllcAdminEntry
Max-Access: Not-accessible
Specifies configured parameter values for a specific QLLC connection.
Syntax: ConvQllcAdminEntry
Max-Access: Not-accessible
Specifies the virtual address assigned to the QLLC connection. It is in the form of 802.3, 802.5 media access control (MAC) address.
Syntax: MacAddress
Max-Access: Read-write
Specifies the conversion that is being used. The conversion is from QLLC to one of the following: unknown, 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
Specifies the SDLC address associated with the QLLC connection.
Syntax: Integer (0-255)
Max-Access: Read-write
Specifies the X.25 connection partner of the other DLC (SDLC or LLC2). It is in the form of 802.3, 802.5 media access control (MAC) address.
Syntax: MacAddress
Max-Access: Read-write
Specifies that the Virtual ring number QLLC end-stations are on. It is used for LLC-to-QLLC only.
Syntax: Integer32
Max-Access: Read-write
Specifies the bridge number QLLC end-stations are on. It is used for LLC-to-QLLC conversions only.
Syntax: Integer32
Max-Access: Read-write
Specifies the ring number LLC end-stations are on. It is used for LLC-to-QLLC conversions only.
Syntax: Integer32
Max-Access: Read-write
Specifies the largest QLLC packet allowed to go out on the SDLC side.
Syntax: Integer32
Max-Access: Read-write
Specifies the largest QLLC packet allowed to go out on the LLC2 side.
Syntax: Integer32
Max-Access: Read-write
Specifies the link station destination SAP (DSAP) address.
Syntax: Integer32
Max-Access: Read-write
Specifies the link station source SAP (SSAP)address.
Syntax: Integer32
Max-Access: Read-write
Specifies the QLLC XID that is being used for the particular connection.
Syntax: Octet string (SIZE (0 | 4))
Max-Access: Read-write
End of Table
This table contains objects for each QLLC connection.
Syntax: SEQUENCE OF ConvQllcOperEntry
Max-Access: Not-accessible
Specifies the operational values for a specific QLLC connection.
Syntax: ConvQllcOperEntry
Max-Access: Not-accessible
Specifies the virtual address assigned to the QLLC connection. It is in the form of 802.3, 802.5 media access control (MAC) address.
Syntax: MacAddress
Max-Access: Read-only
Specifies the conversion that is being used. The conversion is from QLLC to one of the following: unknown, 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-only
Specifies the SDLC address associated with the QLLC connection.
Syntax: Integer (0-255)
Max-Access: Read-only
Specifies the X.25 connection partner of the other DLC (SDLC or LLC2). It is in the form of 802.3, 802.5 media access control (MAC) address.
Syntax: MacAddress
Max-Access: Read-only
The virtual ring number QLLC end-stations are on. It is used for LLC-to-QLLC conversions only.
Syntax: Integer32
Max-Access: Read-only
The bridge number QLLC end-stations are on. It is used for LLC-to-QLLC conversions only.
Syntax: Integer32
Max-Access: Read-only
Specifies the ring number LLC end-stations are on. It is used for LLC-to-QLLC conversions only.
Syntax: Integer32
Max-Access: Read-only
Specifies the largest QLLC packet allowed to go out on the SDLC side.
Syntax: Integer32
Max-Access: Read-only
Specifies the largest QLLC packet allowed to go out on the LLC2 side.
Syntax: Integer32
Max-Access: Read-only
Specifies the link station destination sap address.
Syntax: Integer32
Max-Access: Read-only
Specifies the link station source sap address.
Syntax: Integer32
Max-Access: Read-only
Specifies the QLLC XID that is being used for the particular connection.
Syntax: Octet string (SIZE (0 | 4))
Max-Access: Read-only
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
This object and convQllcOperLsLciVcIndex define the corresponding row in the qllcLSOperTable in the Qualified Logical Link Control (QLLC) Group (CISCO-QLLC01-MIB). The corresponding row is that for which this object and convQllcOperLsLciVcIndex match qllcLSOperIfIndex and qllcLSOperLciVcIndex in the qllcLSOperTable in the Qualified Logical Link Control (QLLC) Group, respectively.
Syntax: IfIndexType
Max-Access: Read-only
This object and convQllcOperLsLciVcIndex define the corresponding row in the qllcLSOperTable in the Qualified Logical Link Control (QLLC) Group (CISCO-QLLC01-MIB). The corresponding row is that for which this object and convQllcOperLsLciVcIndex match qllcLSOperIfIndex and qllcLSOperLciVcIndex in the qllcLSOperTable in the Qualified Logical Link Control (QLLC) Group, respectively.
Syntax: IfIndexType
Max-Access: Read-only
End of Table
|
|