Table Of Contents
Binary Synchronous Communication (BSC) Group
Blocked Serial Tunnel (BSTUN) Group
Notification for Blocked Serial Tunnel Group
Channel Interface Processor (CIP) Group
Cisco CIP Channel Systems Network Architecture (CSNA) Group
Notifications for Cisco CIP CSNA MIB
Cisco Configuration Management Group
Cisco Data Link Switching (DLSw) Group
Notifications for Cisco DLSw Group
Cisco Discovery Protocol (CDP) Group
Cisco DownStream Physical Unit (DSPU) Group
Notifications for Cisco DSPU Group
Cisco Environmental Monitor Group
ciscoEnvMonTemperatureStatusTable
SNMPv2 Notifications Used in Cisco Environmental Monitoring
Flash Partition Level Information
Cisco Integrated Channel Service Unit/Data Service Unit (CSU/DSU) Group
CSU/DSU Static Configuration Table
T1 CSU/DSU Module Configuration Table
Switched 56-kpbs CSU/DSU Module Configuration Table
Switched 56-kbps CSU/DSU Module Status Table
Notifications for Cisco Integrated CSU/DSU
Cisco Integrated Services Digital Network (ISDN) Group
Trap Related to Connection Management
Notification for Cisco IP Encryption Group
Cisco LAN Emulation (LANE) Broadcast-and-Unknown Server Group
Cisco LANE Configuration Group
Cisco Remote Source-Route Bridging (RSRB) Group
Cisco Repeater (ciscoRptr) Group
Notification for Cisco Repeater Group
Cisco Round Trip Time (RTT) Monitoring Group
rttMonApplSupportedRttTypesTable
rttMonApplSupportedProtocolsTable
Notifications for Cisco Round Trip Time (RTT) Monitoring Group
Notification for Cisco SDLLC Conversion Group
Cisco Serial Tunnel (STUN) Group
Notification for Cisco Serial Tunnel Group
Cisco Systems Network Architecture (SNA) Logial Link Control (LLC) Group
Notification for Cisco SNA LLC Group
Notification for Cisco SYSLOG Message Group
Cisco Transmission Control Protocol (ciscoTCP) Group
Cisco Virtual Integrated Network Service (VINES) Group
Interface Output Counter Table
Qualified Logical Link Control (QLLC) Group
QLLC Link Station Administrative Table (qllcLSAdminTable)
QLLC Link Station Operational Table (qllcLSOperTable)
QLLC Link Station Statistics Table (qllcLSStatsTable)
QLLC Link Station Admin Group (qllcLSAdminGroup)
QLLC Link Station Operational Group (qllcLSOperGroup)
QLLC Link Station Statistics Group (qllcLSStatsGroup)
QLLC Conversion Administrative Table (convQllcAdminTable)
QLLC Conversion Operational Table (convQllcOperTable)
CiscoMgmt Variables
This chapter describes the group of MIB variables managed by Cisco Systems.
•
Binary Synchronous Communication (BSC) Group
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
Binary Synchronous Communication (BSC) Group
The variables in this section provide configuration and operational information for Cisco's Binary Synchronous Communications (BSC) implementation. Entities managed by this MIB are: BSC ports (serial interfaces) and BSC control units (stations on a port).
BSC ports are identified by the interface index. Additional information about this interface can be obtained from the Cisco Serial Interface MIB.
BSC control units are identified by the control unit address; this is the address used by blocked serial tunneling (BSTUN) to route the BSC traffic—it is therefore equivalent to the bstunRouteStationAddress in the bstunRouteTable MIB.
bscPortTable
This table contains a list of port (serial interfaces) that have been configured to support a BSC BSTUN group.
Syntax: SEQUENCE OF BscPortEntry
Max-Access: Not-accessible
bscPortRole
The router's data link control (DLC) role with respect to the attached node. (If the bscPortRole is primary, this implies that the port is connected to a remote secondary device.)
Syntax: Integer 1 = primary, 2 = secondary, 3 = contention
Max-Access: Read-only
bscPortCodeSet
The code set used for the line controls.
Syntax: Integer 1 = ebcdic, 2 = ascii
Max-Access: Read-only
bscPortPause
For primary, this is the minimum time to be taken for a cycle around the active poll table; if this time has not elapsed when the bottom of the poll table is reached, then polling will pause until this timer expires. A value of zero means there will be no pause between cycles round the poll table.
For secondary, time out is the delay taken before sending a response to a poll when it has no data frame to send. The units are tenths of a second. The default is 10 (1 second).
Syntax: Integer (1-255)
Max-Access: Read-only
bscPortServlim
This parameter is valid for primary only. It is the number of times the active poll table will be cycled before a non-responding control unit will be polled. The default is 3.
Syntax: Integer (1-50)
Max-Access: Read-only
bscPortPollTimeout
This parameter is valid for primary only. It is the time that the primary will wait for a response to a poll or select. The units are tenths of a second. The default is 10 (1 second).
Syntax: Integer (1-100)
Max-Access: Read-only
bscPortRecoveryRetries
The number of times that a recovery sequence will be retried before the connection is considered to have failed. The default is 5.
Syntax: Integer (1-100)
Max-Access: Read-only
bscPortUnknownControlUnitsReceived
The number of frames received from the serial interface with an unsupported control unit address. If this value is nonzero, it indicates a problem in the configuration.
Syntax: Counter32
Max-Access: Read-only
bscPortSoftErrors
The number of soft errors; these are errors that are recovered. This includes cyclic redundancy check (CRC) errors received, frames that were retransmitted for any reason (NAK received or the wrong ACK received), etc. The count measures the quality of the port/line, but should be considered in relation to the amount of traffic on the port (frames or bytes sent and received).
This count includes all control unit soft errors on this port, plus errors that were not for a specific control unit.
Syntax: Counter32
Max-Access: Read-only
bscPortHardErrors
The number of hard errors; these are errors that are not recovered after bscPortRecoveryRetries number of retries, and therefore the connection has been terminated. These errors could be caused by a hardware error in the line or in the remote device, or possibly the bscPortRecoveryRetries value is set too low for the quality of the line.
This count includes all control unit hard errors on this port, plus errors that were not for a specific control unit.
Syntax: Counter32
Max-Access: Read-only
bscPortProtocolViolations
The number of protocol violations. This counter is incremented when an unexpected BSC data link control character is received from the remote device; that is, the control character is invalid in the current state of the local BSC FSM.
This indicates that there is an incompatibility between the two implementations of the BSC protocol. This count includes all control unit protocol violations on this port, plus errors which were not for a specific control unit.
Syntax: Counter32
Max-Access: Read-only
End of Table
bscControlUnitTable
This table contains information about specific control units.
Syntax: SEQUENCE OF BscCUEntry
Max-Access: Not-accessible
bscCUAddress
The poll address of the BSC control unit. This address must be unique within a BSTUN group.
Syntax: Integer (1-255)
Max-Access: Not-accessible
bscCUState
The state of the BSC control unit. If "active," this indicates that the remote control unit is polling or responding to polls.
Syntax: Integer 1 = inactive, 2 = active
Max-Access: Read-only
bscCUBytesSent
The number of sent bytes (octets), including all control characters.
Syntax: Counter32
Max-Access: Read-only
bscCUBytesReceived
The number of received bytes (octets), including all control characters.
Syntax: Counter32
Max-Access: Read-only
bscCUTotalFramesSent
The number of sent frames (blocks), including all control frames.
Syntax: Counter32
Max-Access: Read-only
bscCUTotalFramesReceived
The number of received frames (blocks), including all control frames.
Syntax: Counter32
Max-Access: Read-only
bscCUDataFramesSent
The number of sent data frames (blocks).
Syntax: Counter32
Max-Access: Read-only
bscCUDataFramesReceived
The number of received data frames (blocks).
Syntax: Counter32
Max-Access: Read-only
bscCUSoftErrors
The number of soft errors; these are errors that are recovered. This includes cyclic redundancy check (CRC) errors received, frames that were retransmitted for any reason (NAK received or the wrong ACK received), etc. The count measures the quality of the connection, but should be considered in relation to the amount of traffic on the connection (frames or bytes sent and received).
Syntax: Counter32
Max-Access: Read-only
bscCUHardErrors
The number of hard errors; these are errors that have not been recovered after bscPortRecoveryRetries number of retries, and therefore the connection has been terminated.
These errors could be caused by a hardware error in the link or in the remote device; or possibly the bscPortRecoveryRetries value is set too low for the quality of the connection.
Syntax: Counter32
Max-Access: Read-only
bscCUProtocolViolations
The number of protocol violations. This counter is incremented when an unexpected BSC data link control character is received from the remote device; that is, the control character is invalid in the current state of the local BSC FSM.
This number indicates that there is an incompatibility between the two implementations of the BSC protocol.
Syntax: Counter32
Max-Access: Read-only
End of Table
Blocked Serial Tunnel (BSTUN) Group
The variables in this section provide configuration and operational information for Cisco's blocked serial tunneling (BSTUN) implementation.
bstunIPAddr
The configured IP address used by the BSTUN component in this router.
Syntax: IpAddress
Max-Access: Read-only
bstunGroupTable
This table contains objects that represent BSTUN groups configured on the router. Each BSTUN-enabled interface is assigned to a BSTUN group, and packets can only travel between BSTUN-enabled interfaces in the same group.
Syntax: SEQUENCE OF BstunGroupEntry
Max-Access: Not-accessible
bstunGroupIndex
The configured BSTUN group number. This number must match the BSTUN group number configured in the router at the other end of the BSTUN tunnel.
Syntax: Integer (1-225)
Max-Access: Not-accessible
bstunProtocolType
The protocol type for this BSTUN group.
Syntax: Integer 1 = BSC (Binary Synchronous Communications)
Max-Access: Read-only
bstunLocalAck
Indicates whether the BSTUN connection is locally acknowledged. A value of TRUE means that the BSTUN connection is locally acknowledged; FALSE means the BSTUN connection is not locally acknowledged.
Syntax: TruthValue
Max-Access: Read-only
bstunGroupUnroutableTransmit
The number of unroutable frames received by this group from the remote partner. They were unroutable because the address was not recognized; that is, there is no bstun route command configured for this address. This indicates that the configuration in this router is incompatible with the peer router.
Syntax: Counter 32
Max-Access: Read-only
bstunGroupUnroutableReceive
The number of frames received from a serial interface with an unsupported poll address. There may be several ports configured within this BSTUN group; a 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
bstunPortTable
This table contains a list of BSTUN-enabled interfaces (ports).
Syntax: SEQUENCE OF BstunPortEntry
Max-Access: Not-accessible
bstunPortGroupNumber
The group number to which the BSTUN port belongs. Frames will only be routed to other ports (on this or another router) in the same BSTUN group. This group should match the bstunGroupIndex in the bstunGroupTable.
Syntax: Integer (1-255)
Max-Access: Read-only
bstunPortDefaultPeerType
The type of identification of the remote default partner. (This is as configured with the route all command.) If the identification is IP, then the value is in bstunPortDefaultPeerIP; if it is serial or serialDirect, then the value is in bstunPortDefaultPeerSerial.
Syntax: Integer 1 = none, 2 = IP, 3 = serial, 4 = serialDirect
Max-Access: Read-only
bstunPortDefaultPeerIP
The IP address of the remote default BSTUN partner, for unrecognized addresses. This is 0.0.0.0 if the partner address type is not IP.
Syntax: IpAddress
Max-Access: Read-only
bstunPortDefaultPeerSerial
If the bstunRouteType is serial, this is the serial interface index of the point-to-point link to the remote partner. If the bstunRouteType is serialDirect, the remote partner is in the local BSTUN. If the bstunRouteType is IP, then this field is 0.
Syntax: InterfaceIndex
Max-Access: Read-only
End of Table
bstunRouteTable
This table contains information about specific poll addresses. There is one table entry for each address configured by the bstun route command.
Syntax: SEQUENCE OF BstunRouteEntry
Max-Access: Not-accessible
bstunRouteGroupIndex
The index of the BSTUN Group owning this station.
Syntax: Integer (1-255)
Max-Access: Not-accessible
bstunRouteStationAddress
The poll address of the station. 256 indicates the all parameter on the stun route command, which is the route for all unrecognized addresses.
Syntax: Integer (1-256)
Max-Access: Not-accessible
bstunRouteType
The type of identification of the remote partner. If the identification is IP, the value is in bstunRouteIP; if it is serial or serialDirect, then the value is in bstunRouteSerial.
Syntax: Integer 1 = none, 2 = ip, 3 = serial, 4 = serialDirect
Max-Access: Read-only
bstunRouteIP
The IP address of the remote BSTUN partner. This is 0.0.0.0 if the partner address type is not IP.
Syntax: IpAddress
Max-Access: Read-only
bstunRouteSerial
If bstunRouteType is serial, this is the serial interface index of the point-to-point link to the remote partner. If bstunRouteType is serialDirect, the remote partner is in the local BSTUN. If the bstunRouteType is IP, then this field is 0.
Syntax: InterfaceIndex
Max-Access: Read-only
bstunRoutePriority
The priority with which this station's traffic will be routed across the network.
Syntax: Integer 1 = low, 2 = normal, 3 = medium, 4 = high
Max-Access: Read-only
bstunRoutePeerState
The state of the peer connection through the BSTUN tunnel.
Syntax: Integer 1 = dead, 2 = closed, 3 = opening, 4 = openWait, 5 = connected, 6 = direct
Max-Access: Read-only
bstunRouteRxPackets
The number of frames received from the serial interface with this station's address.
Syntax: Counter32
Max-Access: Read-only
bstunRouteTxPackets
The number of frames transmitted at the serial interface with this station's address.
Syntax: Counter32
Max-Access: Read-only
bstunRouteRxBytes
The number of bytes received from the serial interface with this station's address.
Syntax: Counter32
Max-Access: Read-only
bstunRouteTxBytes
The number of bytes transmitted at the serial interface with this station's address.
Syntax: Counter32
Max-Access: Read-only
End of Table
Notification for Blocked Serial Tunnel Group
The following notification is supported with the BSTUN MIB:
bstunPeerStateChangeNotification
This notification indicates that the state of a BSTUN route has transitioned to active (connected) or inactive (dead or closed).
Channel Interface Processor (CIP) Group
The CIP group specifies the MIB module for objects used to manage the Cisco Channel Interface Processor card.
cipCardTable
The cipCardTable contains a list of values for the CIP card that can be obtained on a per cip-card basis and include the following variables: cipCardEntryIndex, cipCardEntryName, cipCardEntryTotalMemory, cipCardEntryFreeMemory, cipCardEntryCpuUtilization, and cipCardEntryTimeSinceLastReset. This table extends CardTable in the cisco.mib.
Syntax: SEQUENCE OF CipCardEntry
Max-Access: Not-accessible
cipCardEntryIndex
Specifies the index into the cipCardTable. (Not the physical chassis slot number but the Cisco chassis MIB cardindex.)
Syntax: Integer32
Max-Access: Not-accessible
cipCardEntryName
Specifies the configured name for the CIP.
Syntax: DisplayString (SIZE (1-32))
Max-Access: Read-only
cipCardEntryTotalMemory
Specifies total memory on the card in kilobytes.
Syntax: Integer32
Max-Access: Read-only
cipCardEntryFreeMemory
Specifies the total free memory on the card, that is the amount of memory in kilobytes not in use.
Syntax: Integer32
Max-Access: Read-only
cipCardEntryCpuUtilization
Specifies the average percentage of time, over the last minute, that this processor was not idle.
Syntax: Integer (0-100)
Max-Access: Read-only
cipCardEntryTimeSinceLastReset
Specifies the number of seconds the CIP has been running.
Syntax: Counter32
Max-Access: Read-only
cipCardEntryMajorSwRevisionNr
The major software revision number for the software loaded on the CIP.
Syntax: Integer32
Max-Access: Read-only
cipCardEntryMinorSwRevisionNr
The minor software revision number for the software loaded on the CIP.
Syntax: Integer32
Max-Access: Read-only
cipCardEntryMajorHwRevisionNr
The major hardware revision number for the software loaded on the CIP.
Syntax: Integer32
Max-Access: Read-only
cipCardEntryMinorHwRevisionNr
The minor hardware revision number for the software loaded on the CIP.
Syntax: Integer32
Max-Access: Read-only
End of Table
cipCardDaughterBoardTable
This table contains a list of objects pertaining to the daughter board on the CIP card.
cipCardDtrBrdIndex
Specifies which daughter board is being referenced for a particular CIP card.
Syntax: Integer32
Max-Access: Not-accessible
cipCardDtrBrdType
Indicates the channel path interface type.
Syntax: Integer 1 = escon (Enterprise System Connection), 2 = busAndTag
Max-Access: Read-only
cipCardDtrBrdStatus
Specifies that the microcode for the daughter board has been successfully loaded and is executing.
Syntax: TruthValue
Max-Access: Read-only
cipCardDtrBrdSignal
For ESCON, specifies that the LED has been seen, and synchronization has been established. ESCON is the fiber-optic connection from the IBM mainframe to the peripheral. This is layer 1 of the channel. Older technology (still in use) is called BUS and TAB and consists of two bulky copper cables. For Parallel Channel Adapter (PCA), specifies that the operational out has been sensed.
Syntax: TruthValue
Max-Access: Read-only
cipCardDtrBrdOnline
For ESCON, specifies that a path has been established with at least one channel. For PCA, specifies that the PCA is online to the channel. It will respond to at least one device address.
Syntax: TruthValue
Max-Access: Read-only
implicitIncidents
Counts the number of times the ESCON Processor recovers from an internal error.
Syntax: Counter32
Max-Access: Read-only
codeViolationErrors
Specifies the number of recognized code-violation errors. A trap is issued when this number exceeds the bit error rate threshold for ESCON. The bit error rate threshold is set at 15 error burst within a 5-minute period. An error burst is the time period of 1.5 seconds + or - 0.05 seconds during which one or more code violations errors occur.
Syntax: Counter32
Max-Access: Read-only
linkFailureSignalOrSyncLoss
Specifies the number of link failures recognized as a result of a loss of signal or loss of synchronization that persisted longer than the link interval duration. The link interval duration is 1 second with a tolerance of +1.5 seconds and -0 seconds.
Syntax: Counter32
Max-Access: Read-only
linkFailureNOSs
Specifies the number of link failures recognized as a result of the not-operational sequence (NOS).
Syntax: Counter32
Max-Access: Read-only
linkFailureSequenceTimeouts
Specifies the number of link failures recognized as a result of a connection recovery timeout or response timeout occurring while in transmit OLS state.
Syntax: Counter32
Max-Access: Read-only
linkFailureInvalidSequences
Specifies the number of link failures recognized as a result of an invalid sequence for Link-Level-Facility State. Either a UD or UDR sequence was recognized while in wait-for-offline-sequence state.
Syntax: Counter32
Max-Access: Read-only
linkIncidentTrapCause
Indicates the condition that caused the last SNMP trap.
Syntax: Integer
Max-Access: Read-only
End of Table
cipCard SubChannel Table
This table contains a list of objects pertaining to subchannel connections referenced by the CIP card or its daughter board.
cipCardSubChannelIndex
Indicates which subchannel is being referenced for a particular daughter board on a CIP card. This value is constructed as follows:
path * 256 + device
Path and device are the values in CipCardClawConfigTable.
Syntax: Integer32
Max-Access: Read-only
cipCardSubChannelConnections
Indicates the number of times a device was connected to the subchannel. For some devices, this correlates with the number of start subchannels.
Syntax: Counter32
Max-Access: Read-only
cipCardSubChannelCancels
Specifies the number of halt subchannels.
Syntax: Counter32
Max-Access: Read-only
cipCardSubChannelSelectiveResets
Specifies the number of selective resets.
Syntax: Counter32
Max-Access: Read-only
cipCardSubChannelSystemResets
Specifies the number of system resets.
Syntax: Counter32
Max-Access: Read-only
cipCardSubChannelDeviceErrors
Specifies the number of device level errors.
Syntax: Counter32
Max-Access: Read-only
cipCardSubChannelWriteBlocksDropped
Specifies the number of times a block was received by the channel and a router buffer was not available so the block was discarded.
Syntax: Counter32
Max-Access: Read-only
cipCardSubChannelLastSenseData
Specifies the last sense data sent to the channel by this device.
Syntax: Octet string (SIZE (2))
Access: Read-only
cipCardSubChannelLastSenseDataTime
Specifies the time when the last sense data was sent to the channel by this device.
Syntax: TimeStamp
Max-Access: Read-only
cipCardSubChannelCuBusies
Specifies the number of control unit busies sent to the channel when this device was requested.
Syntax: Counter32
Max-Access: Read-only
End of Table
cipCardClawTable
This table contains status and other information not covered in the following tables for the Common Link Access for Workstations (CLAW) protocol.
Syntax: SEQUENCE OF CipCardClawEntry
Max-Access: Not-accessible
cipCardClawIndex
Specifies which CLAW link is being referenced for a particular subchannel on a daughter board on a CIP card.
Syntax: UInteger32
Max-Access: Read-only
cipCardClawConnected
Specifies the CLAW connection status.
Syntax: TruthValue
Max-Access: Read-only
End of Table
cipCardClawConfigTable
Contains configuration information for the Common Link Access for Workstations (CLAW) protocol.
Syntax: SEQUENCE OF CipCardClawConfigEntry
Max-Access: Not-accessible
cipCardClawConfigEntry
Specifies a list of CLAW configuration values.
Syntax: CipCardClawConfigEntry
Max-Access: Not-accessible
cipCardClawConfigPath
Specifies the hex path identifier for the 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
cipCardClawConfigDevice
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
cipCardClawConfigIpAddr
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
cipCardClawConfigHostName
Specifies the CLAW host name for this CLAW device.
Syntax: DisplayString
Max-Access: Read-write
cipCardClawConfigRouterName
Specifies the CLAW router name for this CLAW device.
Syntax: DisplayString
Max-Access: Read-write
cipCardClawConfigHostAppl
Specifies the CLAW host application name for this CLAW connection.
Syntax: DisplayString
Max-Access: Read-write
cipCardClawConfigRouterAppl
Specifies the CLAW router application name for this CLAW connection.
Syntax: DisplayString
Max-Access: Read-write
End of Table
cipCardClawDataXferStatsTable
Specifies a list of objects pertaining to data transfer statistics per CLAW logical link.
Syntax: SEQUENCE OF CipCardClawDataXferStatsEntry
Max-Access: Not-accessible
cipCardClawDataXferStatsEntry
Specifies a list of daughter board statistics.
Syntax: CipCardClawDataXferStatsEntry
Max-Access: Not-accessible
cipCardClawDataXferStatsBlocksRead
Specifies the number of read data transfer channel command words (CCWs) from the channel perspective.
Syntax: Counter32
Max-Access: Read-only
cipCardClawDataXferStatsBlocksWritten
Specifies the number of successful write data transfer CCWs from the channel perspective.
Syntax: Counter32
Max-Access: Read-only
cipCardClawDataXferStatsBytesRead
Specifies the number of bytes successfully read from the channel perspective.
Syntax: Counter32
Max-Access: Read-only
cipCardClawDataXferStatsHCBytesRead
Specifies the number of bytes successfully read from the channel perspective. The HC (high capacity) objects are the 64-bit equivalent of their 32-bit counterparts modeled after RFC 1573.
Syntax: Counter64
Max-Access: Read-only
clawDataXferStatsBytesWritten
Specifies the number of bytes successfully written from the channel perspective.
Syntax: Counter32
Max-Access: Read-only
cipCardClawDataXferStatsHCBytesWritten
Specifies the number of bytes successfully written from the channel perspective. The HC (high capacity) objects are the 64-bit equivalent of their 32-bit counterparts modeled after RFC 1573.
Syntax: Counter64
Max-Access: Read-only
cipCardClawDataXferStatsReadBlocksDropped
Specifies the number of bytes written.
Syntax: Counter32
Max-Access: Read-only
cipCardClawDataXferStatsWriteBlocksDropped
Specifies the number of read blocks dropped.
Syntax: Counter32
Max-Access: Read-only
cipCardClawDataXferStatsBufferGetRetryCount
Specifies the number of times a buffer was requested and none was available.
Syntax: Counter32
Max-Access: Read-only
End of Table
cipCardApplicationTable
This table contains information about the applications loaded on the CIP.
Syntax: SEQUENCE OF CipCardApplicationEntry
Max-Access: Not-accessible
cipCardApplicationEntry
A list of application information.
Syntax: CipCardApplicationEntry
Max-Access: Not-accessible
cipCardApplicationNameIndex
The application name.
Syntax: DisplayString(SIZE (32))
Max-Access: Not-accessible
cipCardApplicationRevision
The application's software revision number.
Syntax: Integer32
Max-Access: Read-only
cipCardApplicationCompileInfo
The application's compilation information (date and user ID).
Syntax: DisplayString(SIZE (1-64))
Max-Access: Read-only
cipCardTraps
The following notification is supported with the cipCard MIB:
cipCardLinkFailure
This trap indicates that a significant link event has been recognized, resulting in the degradation of the interface line quality.
Cisco CIP Channel Systems Network Architecture (CSNA) Group
The variables described in this section are used to manage the Cisco Channel Systems Network Architecture (CSNA) support on the Channel Interface Processor (CIP), also called the CSNA feature.
CipCardCsnaAdminTable
This table contains configuration information for the Channel Systems Network Architecture (CSNA) feature on the Channel Interface Processor (CIP).
Syntax: SEQUENCE OF CipCardCsnaAdminEntry
Max-Access: Not-accessible
cipCardCsnaAdminPath
The channel path for this Channel Systems Network Architecture table entry.
Syntax: ChannelPath
Max-Access: Read-create
cipCardCsnaAdminDevice
The two-octet hex device address for the device the SNA host will use to communicate with the CSNA feature on the CIP.
Syntax: ChannelDevice
Max-Access: Read-create
cipCardCsnaAdminBlockDelayTime
The block delay time is the maximum amount of time the CSNA feature can hold a set of requests before it must transmit the block to the host.
The block must be sent when this time has expired, even if the block has not reached the suggested block delay length.
Syntax: Integer (0-100)
Max-Access: Read-create
cipCardCsnaAdminBlockDelayLength
The block delay length (BDL) is the suggested size of a block before it is transmitted to the host.
The BDL is used to force a transmit of a block when all information currently being processed has been placed in the block and the real block size exceeds this BDL size. The size of the block can grow larger than the BDL size, but must never exceed the maximum block length before being transmitted.
Syntax: Integer (0-65535)
Max-Access: Read-create
cipCardCsnaAdminMaxBlockLength
The maximum block length is the maximum size that an inbound channel I/O block may attain before being sent to the host. The block must be smaller or equal to this value.
Syntax: Integer (4096-65535)
Max-Access: Read-create
cipCardCsnaAdminRowStatus
This object is used by a management station to create or delete the row entry in the cipCardCsnaAdminTable.
Upon successful creation of the row, an agent automatically creates a corresponding entry in the cipCardCsnaOperTable with the cipCardCsnaOperState equal to "inactive" (1).
The management station can initiate row deletion, by setting this value to "destroy" (6). The agent then deletes the rows corresponding to this CSNA instance from both the cipCardCsnaAdminTable and cipCardCsnaOperTable.
Syntax: RowStatus
Max-Access: Read-create
End of Table
CipCardCsnaOperTable
This table contains operation values and status information for the Channel Systems Network Architecture (CSNA) feature on the Channel Interface Processor (CIP).
Syntax: SEQUENCE OF CipCardCsnaOperEntry
Max-Access: Not-accessible
cipCardCsnaOperState
The current state of the CSNA entry.
Syntax: Integer
Max-Access: Read-only
cipCardCsnaOperSlowDownState
The current state of the CSNA entry slow down condition. A channel turns on the slow down bit whenever insufficient buffering exists to receive data from the adjacent channel device.
Syntax: Integer
Max-Access: Read-only
cipCardCsnaOperBlockDelayTime
The current block delay time value being used by this instance of CSNA path/device (subchannel).
Syntax: Integer (0-100)
Max-Access: Read-only
cipCardCsnaOperBlockDelayLength
The current block delay length being used by this instance of CSNA path/device (subchannel).
Syntax: Integer (0-65535)
Max-Access: Read-only
cipCardCsnaOperMaxBlockLength
The current maximum block length being used by this instance of CSNA path/device (subchannel).
Syntax: Integer (4096-65535)
Max-Access: Read-only
End of Table
CipCardCsnaStatsTable
This table contains statistics information for the Channel Systems Network Architecture (CSNA) feature on the Channel Interface Processor (CIP).
Syntax: SEQUENCE OF CipCardCsnaStatsEntry
Max-Access: Not-accessible
cipCardCsnaStatsBlocksTxd
The number of blocks transmitted.
Syntax: Counter32
Max-Access: Read-only
cipCardCsnaStatsBlocksRxd
The number of blocks received.
Syntax: Counter32
Max-Access: Read-only
cipCardCsnaStatsBytesTxd
The number of bytes transmitted.
Syntax: Counter32
Max-Access: Read-only
cipCardCsnaStatsHCBytesTxd
The number of bytes transmitted. This is a 64-bit (high-capacity) version of the cipCardCsnaStatsBytesTxd counter for use with SNMP Version 2 Managers.
Syntax: Counter64
Max-Access: Read-only
cipCardCsnaStatsBytesRxd
The number of bytes received.
Syntax: Counter32
Max-Access: Read-only
cipCardCsnaStatsHCBytesRxd
The number of bytes received. This is a 64-bit (high-capacity) version of the cipCardCsnaStatsBytesRxd counter for use with SNMP Version 2 Managers.
Syntax: Counter64
Max-Access: Read-only
cipCardCsnaStatsBlocksTxByBlockDelayTime
The number of blocks transmitted when the block delay time has been exceeded.
Syntax: Counter32
Max-Access: Read-only
cipCardCsnaStatsBytesTxByBlockDelayTime
The number of bytes transmitted when the block delay time has been exceeded.
Syntax: Counter32
Max-Access: Read-only
cipCardCsnaStatsHCBytesTxByBlockDelayTime
The number of bytes transmitted when the block delay time has been exceeded.
This is a 64-bit (high-capacity) version of the cipCardCsnaStatsBytesTxByBlockDelayTime counter for use with SNMP version 2 managers.
Syntax: Counter64
Max-Access: Read-only
cipCardCsnaStatsBlocksTxByBlockDelayLength
The number of blocks transmitted when the suggested block delay length has been exceeded.
Syntax: Counter32
Max-Access: Read-only
cipCardCsnaStatsBytesTxByBlockDelayLength
The number of bytes transmitted when the block delay length has been reached.
Syntax: Counter32
Max-Access: Read-only
cipCardCsnaStatsHCBytesTxByBlockDelayLength
The number of bytes transmitted when the block delay length has been reached.
This is a 64-bit (high-capacity) version of the cipCardCsnaStatsBytesTxByBlockDelayLength counter for use with SNMP version 2 managers.
Syntax: Counter64
Max-Access: Read-only
cipCardCsnaStatsBlocksTxByMaxBlockLength
The number of blocks transmitted when the maximum block length has been exceeded.
Syntax: Counter32
Max-Access: Read-only
cipCardCsnaStatsBytesTxByMaxBlockLength
The number of bytes transmitted when the max block length has been reached.
Syntax: Counter32
Max-Access: Read-only
cipCardCsnaStatsHCBytesTxByMaxBlockLength
The number of bytes transmitted when the max block length has been reached.
This is a 64-bit (high-capacity) version of the cipCardCsnaStatsBytesTxByMaxBlockLength counter for use with SNMP version 2 managers.
Syntax: Counter64
Max-Access: Read-only
cipCardCsnaStatsSlowDownsReceived
The number of times the CSNA channel device detected the slow down bit set by VTAM.
Syntax: Counter32
Max-Access: Read-only
cipCardCsnaStatsSlowDownsSent
The number of times the CSNA channel device set the slow down bit directing VTAM not to send any more blocks until the bit is cleared.
Syntax: Counter32
Max-Access: Read-only
End of Table
cipCardSessionsAdminTable
This table contains configured values for CSNA sessions supported on the Channel Interface Processor (CIP) card.
Syntax: SEQUENCE OF CipCardSessionsAdminEntry
Max-Access: Not-accessible
cipCardAdminMaxLlc2Sessions
The configured maximum number of LLC2 connections allowed on a CIP card. A value of zero indicates that the maximum should only be limited by the amount of available memory on the CIP. A value greater than zero indicates the maximum number of sessions the CIP will support given enough memory available on the CIP card.
This value can be set at any time; however, it will only affect the maximum number of LLC2 sessions supported on a CIP the first time it is set and only if the value it is being set to is greater than the current value for cipCardStatsHiWaterLlc2Sessions.
Syntax: Integer (0-4000)
Max-Access: Read-write
End of Table
cipCardSessionsOperTable
This table contains the current value for the maximum number of sessions that can be supported on the CIP card.
Syntax: SEQUENCE OF CipCardSessionsOperEntry
Max-Access: Not-accessible
cipCardOperMaxLlc2Sessions
This value indicates the current number of LLC2 sessions that can be supported on this CIP card. If this value is zero, then the limit of LLC2 sessions on the CIP card is only limited by the amount of memory available.
Syntax: Integer (0-4000)
Max-Access: Read-only
End of Table
cipCardSessionsStatsTable
This table contains the statistic value(s) for the maximum number of sessions that can be supported on the CIP card.
Syntax: SEQUENCE OF CipCardSessionsStatsEntry
Max-Access: Not-accessible
cipCardStatsHiWaterLlc2Sessions
High water LLC2 sessions count per CIP card.
If cipCardOperMaxLlc2Sessions is zero (0), then this value starts at 256 Llc2 sessions and is incremented in values of 64 as more active concurrent LLC2 sessions are established.
If cipCardOperMaxLlc2Sessions is greater then zero (0), then this value is either equal to the cipCardOperMaxLlc2Sessions—given enough memory is available on the CIP card to support that many LLC2 sessions—or the value will be less than cipCardOperMaxLlc2Sessions, reflecting the maximum number of LLC2 sessions the CIP card can support.
Syntax: Gauge32
Max-Access: Read-only
cipCardStatsLlc2SessionsAllocationErrs
The number of memory allocation errors that have occurred during attempts to create a new block of memory for the LLC2 session buffer pool.
Syntax: Counter32
Max-Access: Read-only
End of Table
CipCardCsnaConnTable
This table contains the map between VTAM (the I/O device address) and the internal identifier—LAN adapter, media access control (MAC) address, or service access point (SAP).
Syntax: SEQUENCE OF CipCardCsnaConnEntry
Max-Access: Not-accessible
cipCardCsnaConnActiveSessions
The active sessions in this VTAM-to-internal-LAN adapter/MAC address mapping.
Syntax: Gauge32
Max-Access: Read-only
cipCardCsnaSlot
The slot number of the CIP card on which the path and device are configured.
Syntax: Integer32
Max-Access: Read-only
cipCardCsnaPort
The port number of the interface on the CIP card on which the path and device are configured.
Syntax: Integer32
Max-Access: Read-only
cipCardCsnaConnPath
The hex path identifier used by this instance of internal LAN adapter/SAP to connect SNA sessions to VTAM.
Syntax: ChannelPath
Max-Access: Read-only
cipCardCsnaConnDevice
The two-digit hex device address used by this internal LAN adapter/SAP instance to connect SNA sessions to VTAM.
Syntax: ChannelDevice
Max-Access: Read-only
End of Table
Notifications for Cisco CIP CSNA MIB
The following notifications are supported with the Cisco CIP CSNA MIB:
cipCsnaOpenDuplicateSapFailure
This trap indicates that VTAM attempted to open a SAP that was already open on another path/device (subchannel) on this CIP card.
cipCsnaLlc2ConnectionLimitExceeded
This trap indicates that a connection attempt was rejected due to a connection resource limitation.
Cisco CIP LAN Group
The variables in this section are used to manage the Cisco internal LAN support (LAN and adapter) on the Channel Interface Processor (CIP).
CipCardLanAdminTable
This table contains configuration information for the LAN feature on the Channel Interface Processor (CIP).
Syntax: SEQUENCE OF CipCardLanAdminEntry
Max-Access: Not-accessible
cipCardLanAdminLanType
The type of emulation applied to this CIP LAN.
Syntax: Integer 1 = iso88023csmacd, 2 = iso88025tokenRing, 3 = fddi
Max-Access: Not-accessible
cipCardLanAdminLanId
The index value used with the ifIndex to uniquely identify a CIP LAN.
Syntax: Integer (1-31)
Max-Access: Not-accessible
cipCardLanAdminBridgeType
The bridging type supported by this CIP LAN.
The value of transparentOnly (1) is valid for all LAN types.
The value of sourcerouteOnly (2) is only valid for iso88025tokenRing and fddi LAN types.
The value of bothSrtAndTb (3) is valid for all iso88025tokenRing and fddi LAN types.
Syntax: Integer 1 = transparentOnly, 2 = sourcerouteOnly, 3 = transpAndSourceRoute
Max-Access: Read-create
cipCardLanAdminSrbLocalRing
The local segment (ring) number that uniquely identifies this CIP LAN.
This variable is only valid when cipCardLanAdminBridgeType is sourcerouteOnly (2) or transpAndSourceRoute (3).
Syntax: Integer (1-4095)
Max-Access: Read-create
cipCardLanAdminSrbBridgeNum
The bridge number that represents this router's bridge number.
This variable is only valid when cipCardLanAdminBridgeType is sourcerouteOnly (2) or transpAndSourceRoute (3).
Syntax: Integer (1-15)
Max-Access: Read-create
cipCardLanAdminSrbTargetRing
The target segment (ring) number that is the next hop from this segment.
This variable is only valid when cipCardLanAdminBridgeType is sourcerouteOnly (2) or transpAndSourceRoute (3).
Syntax: Integer (1-4095)
Max-Access: Read-create
cipCardLanAdminTbBridgeGrp
The transparent bridge group of which this CIP LAN is a member.
This variable is only valid when cipCardLanAdminBridgeType is transparentOnly (1) or transpAndSourceRoute (3).
Syntax: Integer (1-63)
Max-Access: Read-create
cipCardLanAdminRowStatus
This object is used by a management station to create or delete the row entry in the cipCardLanAdminTable.
Syntax: RowStatus
Max-Access: Read-create
End of Table
CipCardLanAdaptAdminTable
This table contains configuration information for the LAN adapter feature on the Channel Interface Processor (CIP).
Syntax: SEQUENCE OF CipCardLanAdaptAdminEntry
Max-Access: Not-accessible
cipCardLanAdaptAdminAdaptNo
The adapter number used when creating a CIP LAN adapter. This value is given by the instance value when this row is being created.
This number corresponds to the "ADAPNO" value used by VTAM XCA node definition.
This number uniquely identifies this adapter from all other adapters for the LAN type, which is identified in the associated CIP LAN adapter table.
Syntax: Integer (0-31)
Max-Access: Not-accessible
cipCardLanAdaptAdminMacAddress
The adapter 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
cipCardLanAdaptAdminAdaptName
The unique adapter name assigned by the router administrator. Every interface of the router can be named by the router administrator.
The Adapter Name is used in the Hierarchy Resource List when creating a Systems Network Architecture Generic Alert for the purpose of identifying the CIP LAN adapter which generated the alert.
Syntax: DisplayString (SIZE (1-8))
Max-Access: Read-create
cipCardLanAdaptAdminRowStatus
This object is used by a Management Station to create or delete the row entry in the cipCardCsnaAdminTable.
Syntax: RowStatus
Max-Access: Read-create
End of Table
Cisco CIP TCP/IP Group
The variables in this section consist of objects used to manage the Cisco TCP/IP stack running on the Channel Interface Processor (CIP) board.
The first application to use this stack is the IBM TCP-Offload feature. This application replaces the TCP/IP stack on the IBM host with a protocol requiring lower host CPU utilization, and passes TCP/IP processing to the router.
There are multiple sets of MIB-II statistics stored by the TCP/IP implementation. Each instance of the MIB-II objects corresponds to 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.
cipIpTable
This table contains a list of parameters and statistics pertaining to each IP protocol stack running on the Channel Interface Processor (CIP) board. The TCP offload feature makes use of the stack. Rows are dynamically added to this table via CIP TCP application MIBs (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
cipIpAddress
The IP address for this IP stack.
Syntax: IpAddress
Max-Access: Not-accessible
cipIpForwarding
Indicates whether this entity is acting as an IP gateway in respect to the forwarding of datagrams received by, but not addressed to, this entity. IP gateways forward datagrams. IP hosts do not (except those source-routed via the host).
Note that for some managed nodes, this object may take on only a subset of the values possible. Accordingly, it is appropriate for an agent to return a "badValue" response if a management station attempts to change this object to an inappropriate value.
Syntax: Integer 1 = forwarding (acting as a gateway), 2 = not forwarding (not acting as a gateway)
Max-Access: Read-only
cipIpDefaultTTL
The default value inserted into the Time-To-Live (TTL) field of the IP header of datagrams originated at this entity, whenever a TTL value is not supplied by the transport layer protocol.
Syntax: Integer (1-255)
Max-Access: Read-write
cipIpInReceives
The total number of input datagrams received from interfaces, including those received in error.
Syntax: Counter32
Max-Access: Read-only
cipIpInHdrErrors
The number of input datagrams discarded due to errors in their IP headers, including bad checksums, version number mismatch, other format errors, time-to-live exceeded, errors discovered in processing their IP options, etc.
Syntax: Counter32
Max-Access: Read-only
cipIpInAddrErrors
The number of input datagrams discarded because the IP address in their IP header's destination field was not a valid address to be received at this entity. This count includes invalid addresses (e.g., 0.0.0.0) and addresses of unsupported Classes (e.g., Class E). For entities which are not IP gateways and therefore do not forward datagrams, this counter includes datagrams discarded because the destination address was not a local address.
Syntax: Counter32
Max-Access: Read-only
cipIpForwDatagrams
The number of input datagrams for which this entity was not their final IP destination, as a result of which an attempt was made to find a route to forward them to that final destination. In entities that do not act as IP Gateways, this counter will include only those packets which were source-routed via this entity, and the source-route option processing was successful.
Syntax: Counter32
Max-Access: Read-only
cipIpInUnknownProtos
The number of locally-addressed datagrams received successfully but discarded because of an unknown or unsupported protocol.
Syntax: Counter32
Max-Access: Read-only
cipIpInDiscards
The number of input IP datagrams for which no problems were encountered to prevent their continued processing, but which were discarded (e.g., for lack of buffer space). This counter does not include any datagrams discarded while awaiting re-assembly.
Syntax: Counter32
Max-Access: Read-only
cipIpInDelivers
The total number of input datagrams successfully delivered to IP user-protocols (including ICMP).
Syntax: Counter32
Max-Access: Read-only
cipIpOutRequests
The total number of IP datagrams which local IP user-protocols (including ICMP) supplied to IP in requests for transmission. Note that this counter does not include any datagrams counted in ipForwDatagrams.
Syntax: Counter32
Max-Access: Read-only
cipIpOutDiscards
The number of output IP datagrams for which no problem was encountered to prevent their transmission to their destination, but which were discarded (e.g., for lack of buffer space). Note that this counter includes datagrams counted in ipForwDatagrams if any such packets meet this discretionary discard criterion.
Syntax: Counter32
Max-Access: Read-only
cipIpOutNoRoutes
The number of IP datagrams discarded because no route could be found to transmit them to their destination. This counter includes any packets counted in ipForwDatagrams that meet this "no-route" criterion, including any datagrams that a host cannot route because all its default gateways are down.
Syntax: Counter32
Max-Access: Read-only
cipIpReasmTimeout
The maximum number of seconds that received fragments are held while they are awaiting reassembly at this entity.
Syntax: Integer
Max-Access: Read-only
cipIpReasmReqds
The number of IP fragments received that needed to be reassembled at this entity.
Syntax: Counter32
Max-Access: Read-only
cipIpReasmOKs
The number of IP datagrams successfully re-assembled.
Syntax: Counter32
Max-Access: Read-only
cipIpReasmFails
The number of failures detected by the IP re-assembly algorithm (for whatever reason: timed out, errors, etc.). Note that this is not necessarily a count of discarded IP fragments because some algorithms (notably the algorithm in RFC 815) can lose track of the number of fragments by combining them as they are received.
Syntax: Counter32
Max-Access: Read-only
cipIpFragOKs
The number of IP datagrams that have been successfully fragmented at this entity.
Syntax: Counter32
Max-Access: Read-only
cipIpFragFails
The number of IP datagrams that have been discarded because they needed to be fragmented at this entity but could not be, e.g., because their Don't Fragment flag was set.
Syntax: Counter32
Max-Access: Read-only
cipIpFragCreates
The number of IP datagram fragments generated as a result of fragmentation at this entity.
Syntax: Counter32
Max-Access: Read-only
cipIpRoutingDiscards
The number of routing entries chosen to be discarded even though they are valid. One possible reason for discarding such an entry is to free up buffer space for other routing entries.
Syntax: Counter32
Max-Access: Read-only
End of Table
cipTcpStackTable
This table contains a list of parameters pertaining to each TCP stack running on the Channel Interface Processor (CIP) board. The TCP offload feature makes use of the stack. Rows are dynamically added to this table via CIP TCP application MIBs (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
cipTcpRtoAlgorithm
The algorithm used to determine the timeout value for retransmitting unacknowledged octets.
Syntax: Integer 1 = other (none of the following), 2 = constant (a constant rto), 3 = rsre (MIL-STD-1778, Appendix B), 4 = vanj (Van Jacobson's algorithm)
Max-Access: Read-only
cipTcpRtoMin
The minimum value permitted by a TCP implementation for the retransmission timeout, measured in milliseconds. More refined semantics for objects of this type depend upon the algorithm used to determine the retransmission timeout. In particular, when the timeout algorithm is rsre (3), an object of this type has the semantics of the LBOUND quantity described in RFC 793.
Syntax: Integer32
Max-Access: Read-only
cipTcpRtoMax
The maximum value permitted by a TCP implementation for the retransmission timeout, measured in milliseconds. More refined semantics for objects of this type depend upon the algorithm used to determine the retransmission timeout. In particular, when the timeout algorithm is rsre (3), an object of this type has the semantics of the UBOUND quantity described in RFC 793.
Syntax: Integer32
Max-Access: Read-only
cipTcpMaxConn
The limit on the total number of TCP connections the entity can support. In entities where the maximum number of connections is dynamic, this object should contain the value -1.
Syntax: Integer32
Max-Access: Read-only
cipTcpActiveOpens
The number of times TCP connections have made a direct transition to the SYN-SENT state from the CLOSED state.
Syntax: Counter32
Max-Access: Read-only
cipTcpPassiveOpens
The number of times TCP connections have made a direct transition to the SYN-RCVD state from the LISTEN state.
Syntax: Counter32
Max-Access: Read-only
cipTcpAttemptFails
The number of times TCP connections have made a direct transition to the CLOSED state from either the SYN-SENT state or the SYN-RCVD state, plus the number of times TCP connections have made a direct transition to the LISTEN state from the SYN-RCVD state.
Syntax: Counter32
Max-Access: Read-only
cipTcpEstabResets
The number of times TCP connections have made a direct transition to the CLOSED state from either the ESTABLISHED state or the CLOSE-WAIT state.
Syntax: Counter32
Max-Access: Read-only
cipTcpCurrEstab
The number of TCP connections for which the current state is either ESTABLISHED or CLOSE-WAIT.
Syntax: Gauge32
Max-Access: Read-only
cipTcpInSegs
The total number of segments received, including those received in error. This count includes segments received on currently established connections.
Syntax: Counter32
Max-Access: Read-only
cipTcpOutSegs
The total number of segments sent, including those on current connections but excluding those containing only retransmitted octets.
Syntax: Counter32
Max-Access: Read-only
cipTcpRetransSegs
The total number of segments retransmitted—that is, the number of TCP segments transmitted containing one or more previously transmitted octets.
Syntax: Counter32
Max-Access: Read-only
cipTcpInErrs
The total number of segments received in error (for example, bad TCP checksums).
Syntax: Counter32
Max-Access: Read-only
cipTcpOutRsts
The number of TCP segments sent containing the RST flag.
Syntax: Counter32
Max-Access: Read-only
End of Table
cipTcpConnTable
This table contains a list of parameters pertaining to the connections for a particular TCP Offload protocol stack running on the Channel Interface Processor (CIP) board. The TCP offload feature makes use of the stack. The TCP connection instances exist for each TCP/IP connection on the CIP. These instances are removed when the TCP connection is terminated. Use this table to view statistics and status for the TCP Offload stack.
Syntax: SEQUENCE OF CipTcpConnEntry
Max-Access: Not-accessible
cipTcpConnLocalPort
The local port number for this TCP connection.
Syntax: Integer (0-65535)
Max-Access: Not-accessible
cipTcpConnRemAddress
The remote IP address for this TCP connection.
Syntax: IpAddress
Max-Access: Not-accessible
cipTcpConnRemPort
The remote port number for this TCP connection.
Syntax: Integer (0-65535)
Max-Access: Not-accessible
cipTcpConnState
The state of this TCP connection.
The only value a management station can set is deleteTCB (12). Accordingly, it is appropriate for an agent to return a "badValue" response if a management station attempts to set this object to any other value.
If a management station sets this object to the value deleteTCB (12), then this has the effect of deleting the TCB (as defined in RFC 793) of the corresponding connection on the managed node, resulting in immediate termination of the connection.
As an implementation-specific option, an RST segment can be sent from the managed node to the other TCP endpoint (note however that RST segments are not sent reliably).
Syntax: Integer 1 = closed, 2 = listen, 3 = synSent, 4 = synReceived, 5 = established, 6 = finWait1, 7 = finWait2, 8 = closeWait, 9 = lastAck, 10 = closing, 11 = timeWait, 12 = deleteTCB
Max-Access: Read-write
cipTcpConnInHCBytes
The number of bytes sent for this TCP connection.
This is a 64-bit (high-capacity) version of the cipTcpConnInHCBytes counter for use with SNMP Version 2.
Syntax: Counter64
Max-Access: Read-only
cipTcpConnInBytes
The number of bytes sent for this TCP connection.
Note
Syntax: Counter32
Max-Access: Read-only
cipTcpConnOutHCBytes
The number of bytes received for this TCP connection.
This is a 64-bit (high-capacity) version of the cipTcpConnOutHCBytes counter for use with SNMP Version 2.
Syntax: Counter64
Max-Access: Read-only
cipTcpConnOutBytes
The number of bytes received for this TCP connection.
Note
Syntax: Counter32
Max-Access: Read-only
End of Table
cipIcmpTable
This table contains a list of parameters pertaining to each ICMP stack running on the Channel Interface Processor (CIP) board. The TCP offload feature makes use of the stack. Rows are dynamically added to this table via CIP TCP application MIBs (i.e., Cisco TCP offload MIB). Use this table to view statistics and status for the ICMP stack.
Syntax: SEQUENCE OF CipIcmpEntry
Max-Access: Not-accessible
cipIcmpInMsgs
The total number of ICMP messages the entity received. Note that this counter includes all those counted by icmpInErrors.
Syntax: Counter32
Max-Access: Read-only
cipIcmpInErrors
The number of ICMP messages that the entity received but determined as having ICMP-specific errors (bad ICMP checksums, bad length, etc.).
Syntax: Counter32
Max-Access: Read-only
cipIcmpInDestUnreachs
The number of ICMP Destination Unreachable messages received.
Syntax: Counter32
Max-Access: Read-only
cipIcmpInTimeExcds
The number of ICMP Time Exceeded messages received.
Syntax: Counter32
Max-Access: Read-only
cipIcmpInParmProbs
The number of ICMP Parameter Problem messages received.
Syntax: Counter32
Max-Access: Read-only
cipIcmpInSrcQuenchs
The number of ICMP Source Quench messages received.
Syntax: Counter32
Max-Access: Read-only
cipIcmpInRedirects
The number of ICMP Redirect messages received.
Syntax: Counter32
Max-Access: Read-only
cipIcmpInEchos
The number of ICMP Echo (request) messages received.
Syntax: Counter32
Max-Access: Read-only
cipIcmpInAddrMaskReps
The number of ICMP Address Mask Reply messages received.
Syntax: Counter32
Max-Access: Read-only
cipIcmpOutMsgs
The total number of ICMP messages which this entity attempted to send. Note that this counter includes all those counted by icmpOutErrors.
Syntax: Counter32
Max-Access: Read-only
cipIcmpOutErrors
The number of ICMP messages which this entity did not send due to problems discovered within ICMP such as a lack of buffers. This value should not include errors discovered outside the ICMP layer such as the inability of IP to route the resultant datagram. In some implementations no types of error exist that contribute to this counter's value.
Syntax: Counter32
Max-Access: Read-only
cipIcmpOutDestUnreachs
The number of ICMP Destination Unreachable messages sent.
Syntax: Counter32
Max-Access: Read-only
cipIcmpOutEchos
The number of ICMP Echo (request) messages sent.
Syntax: Counter32
Max-Access: Read-only
cipIcmpOutEchoReps
The number of ICMP Echo Reply messages sent.
Syntax: Counter32
Max-Access: Read-only
cipIcmpOutTimestamps
The number of ICMP Timestamp (request) messages sent.
Syntax: Counter32
Max-Access: Read-only
cipIcmpOutTimestampReps
The number of ICMP Timestamp Reply messages sent.
Syntax: Counter32
Max-Access: Read-only
cipIcmpOutAddrMasks
The number of ICMP Address Mask Request messages sent.
Syntax: Counter32
Max-Access: Read-only
cipIcmpOutAddrMaskReps
The number of ICMP Address Mask Reply messages sent.
Syntax: Counter32
Max-Access: Read-only
End of Table
cipUdpTable
This table contains a list of parameters pertaining to each 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
cipUdpInDatagrams
The total number of UDP datagrams delivered to UDP users.
Syntax: Counter32
Max-Access: Read-only
cipUdpNoPorts
The total number of received UDP datagrams for which there was no application at the destination port.
Syntax: Counter32
Max-Access: Read-only
cipUdpInErrors
The number of received UDP datagrams that could not be delivered for reasons other than the lack of an application at the destination port.
Syntax: Counter32
Max-Access: Read-only
cipUdpOutDatagrams
The total number of UDP datagrams sent from this entity.
Syntax: Counter32
Max-Access: Read-only
End of Table
cipUdpListenersTable
This table contains a list of parameters pertaining to the listeners for a particular UDP stack running on the Channel Interface Processor (CIP) board. The TCP offload feature makes use of the stack. Use this table to view statistics and status for the UDP stack listeners table.
Syntax: SEQUENCE OF CipUdpListenersEntry
Max-Access: Not-accessible
cipUdpLocalPort
The local port number for this UDP listener.
Syntax: Integer (0-65535)
Max-Access: Read-only
End of Table
Cisco Configuration Management Group
The variables in this section represent the router configuration data as it can be stored in the following locations:
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.
ccmHistoryRunningLastChanged
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
ccmHistoryRunningLastSaved
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
ccmHistoryStartupLastChanged
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
ccmHistoryMaxEventEntries
The maximum number of entries that can be held in ccmHistoryEventTable.
Syntax: Integer32 (0-2147483647)
Max-Access: Read-only
ccmHistoryEventEntriesBumped
The number of times the oldest entry in ccmHistoryEventTable was deleted to make room for a new entry.
Syntax: Counter32
Max-Access: Read-only
ccmHistoryEventTable
A table of configuration events on this router.
Syntax: SEQUENCE OF CcmHistoryEventEntry
Max-Access: Not-accessible
ccmHistoryEventEntry
Information about a configuration event on this router.
Syntax: CcmHistoryEventEntry
Max-Access: Not-accessible
ccmHistoryEventIndex
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
ccmHistoryEventTime
The value of sysUpTime when the event occurred.
Syntax: TimeTicks
Max-Access: Read-only
ccmHistoryEventCommandSource
The source of the command that instigated the event.
Syntax: Integer 1 = commandLine, 2 = snmp
Max-Access: Read-only
ccmHistoryEventConfigSource
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
ccmHistoryEventTerminalType
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
ccmHistoryEventTerminalNumber
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
ccmHistoryEventTerminalUser
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
ccmHistoryEventServerAddress
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
ccmHistoryEventFile
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
ccmHistoryEventRcpUser
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
Cisco Data Link Switching (DLSw) Group
The variables in this section are used to manage data link switching (DLSw).
The DLSw MIB is organized in the following groups:
ciscoDlswNode
The ciscoDlswNode group contains nine objects and one table, ciscoDlswTrapControl, consisting of four objects.
ciscoDlswVersion
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
ciscoDlswVendorID
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
ciscoDlswVersionString
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
ciscoDlswStdPacingSupport
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
ciscoDlswStatus
The status of the DLSw part of the system. Changing the value from active to inactive causes DLSw to take the following actions:
1
2
3
4
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
ciscoDlswUpTime
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
ciscoDlswVirtualSegmentLFSize
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
ciscoDlswTrapControl
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
ciscoDlswTrapCntlTConn
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
ciscoDlswTrapCntlCircuit
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
ciscoDlswTConn
The ciscoDlswTConn group contains ciscoDlswTConnStat, ciscoDlswTConnConfigTable, ciscoDlswTConnOperTable, and ciscoDlswTConnSpecific. Two additional tables are contained in ciscoDlswTConnSpecific: ciscoDlswTConnTcpConfigTable and ciscoDlswTConnTcpOperTable.
ciscoDlswTConnStat
ciscoDlswTConnStatActiveConnections
The number of transport connections that are not in disconnected state.
Syntax: Gauge32
Max-Access: Read-only
ciscoDlswTConnStatCloseIdles
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
ciscoDlswTConnStatCloseBusys
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
ciscoDlswTConnConfigTable
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
ciscoDlswTConnConfigEntry
Each conceptual row defines a collection of transport connections.
Syntax: ciscoDlswTConnConfigEntry
Max-Access: Not-accessible
ciscoDlswTConnConfigIndex
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
ciscoDlswTConnConfigTDomain
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
ciscoDlswTConnConfigEntryType
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
ciscoDlswTConnConfigSetupType
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
ciscoDlswTConnConfigSapList
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
ciscoDlswTConnConfigOpens
Number of times transport connections entered the connected state according to the definition of this conceptual row.
Syntax: Counter32
Max-Access: Read-only
ciscoDlswTConnConfigRowStatus
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
ciscoDlswTConnOperTable
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
ciscoDlswTConnOperEntry
Syntax: ciscoDlswTConnOperEntry
Max-Access: Not-accessible
ciscoDlswTConnOperTDomain
The object identifier, which indicates the transport domain of this transport connection.
Syntax: OBJECT IDENTIFIER
Max-Access: Not-accessible
ciscoDlswTConnOperLocalTAddr
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
ciscoDlswTConnOperRemoteTAddr
The remote transport address of this transport connection.
Syntax: TAddress
Max-Access: Not-accessible
ciscoDlswTConnOperEntryTime
The value of ciscoDlswUpTime when this transport connection conceptual row was created.
Syntax: DlswTimeStamp
Max-Access: Read-only
ciscoDlswTConnOperConnectTime
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
ciscoDlswTConnOperState
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
ciscoDlswTConnOperConfigIndex
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
ciscoDlswTConnOperDiscTime
The value of ciscoDlswUpTime when ciscoDlswTConnOperState last entered disconnected state.
Syntax: DlswTimeStamp
Max-Access: Read-only
ciscoDlswTConnOperDiscReason
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
ciscoDlswTConnOperInDataPkts
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
ciscoDlswTConnOperOutDataPkts
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
ciscoDlswTConnOperInCntlPkts
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
ciscoDlswTConnOperOutCntlPkts
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
ciscoDlswTConnOperCURexSents
The number of CanUReach_ex messages sent on this transport connection.
Syntax: Counter32
Max-Access: Read-only
ciscoDlswTConnOperICRexRcvds
The number of ICanReach_ex messages received on this transport connection.
Syntax: Counter32
Max-Access: Read-only
ciscoDlswTConnOperCURexRcvds
The number of CanUReach_ex messages received on this transport connection.
Syntax: Counter32
Max-Access: Read-only
ciscoDlswTConnOperICRexSents
The number of ICanReach_ex messages sent on this transport connection.
Syntax: Counter32
Max-Access: Read-only
ciscoDlswTConnOperNQexSents
The number of NetBIOS_NQ_ex (NetBIOS Name Query-explorer) messages sent on this transport connection.
Syntax: Counter32
Max-Access: Read-only
ciscoDlswTConnOperNRexRcvds
The number of NETBIOS_NR_ex (NetBIOS Name Recognized-explorer) messages received on this transport connection.
Syntax: Counter32
Max-Access: Read-only
ciscoDlswTConnOperNQexRcvds
The number of NETBIOS_NQ_ex (NetBIOS Name Query-explorer) messages received on this transport connection.
Syntax: Counter32
Max-Access: Read-only
ciscoDlswTConnOperNRexSents
The number of NETBIOS_NR_ex (NetBIOS Name Recognized-explorer) messages sent on this transport connection.
Syntax: Counter32
Max-Access: Read-only
ciscoDlswTConnOperCirCreates
The number of times that circuits entered circuit_established state (not counting transitions from circuit_restart state).
Syntax: Counter32
Max-Access: Read-only
ciscoDlswTConnOperCircuits
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
ciscoDlswTConnSpecific consists of the two tables ciscoDlswTConnTcpConfigTable and ciscoDlswTConnTcpOperTable.
ciscoDlswTConnTcpConfigTable
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
ciscoDlswTConnTcpConfigEntry
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
ciscoDlswTConnTcpOperTable
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
ciscoDlswTConnTcpOperEntry
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
ciscoDlswInterface
The ciscoDlswInterface group consists of the ciscoDlswIFTable.
ciscoDlswIfTable
The list of interfaces on which DLSw is active.
Syntax: SEQUENCE OF ciscoDlswIfEntry
Max-Access: Not-accessible
ciscoDlswIfEntry
Syntax: ciscoDlswIfEntry
Max-Access: Not-accessible
ciscoDlswIfRowStatus
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
ciscoDlswIfVirtualSegment
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
ciscoDlswIfSapList
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
ciscoDlswCircuit
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.
ciscoDlswCircuitStat
ciscoDlswActiveCircuits
The current number of circuits in ciscoDlswCircuitTable that are not in the disconnected state.
Syntax: Gauge32
Max-Access: Read-only
ciscoDlswCircuitCreates
The total number of entries ever added to ciscoDlswCircuitTable, or reactivated when the table exits the disconnected state.
Syntax: Counter32
Max-Access: Read-only
ciscoDlswCircuitTable
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.
Not applicable
2
1
2
2
1
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
ciscoDlswCircuitEntry
Syntax: ciscoDlswCircuitEntry
Max-Access: Not-accessible
ciscoDlswCircuitS1Mac
The MAC Address of end station 1 (S1) used for this circuit.
Syntax: MacAddress
Max-Access: Not-accessible
ciscoDlswCircuitS1Sap
The SAP at end station 1 (S1) used for this circuit.
Syntax: Octet String (SIZE(1))
Max-Access: Not-accessible
ciscoDlswCircuitS1IfIndex
The IfEntry index of the local interface through which end station 1 (S1) can be reached.
Syntax: Integer (0-65000)
Max-Access: Read-only
ciscoDlswCircuitS1DlcType
The DLC protocol in use between the DLSw node and end station 1 (S1).
Syntax: DlcType
Max-Access: Read-only
ciscoDlswCircuitS1RouteInfo
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
ciscoDlswCircuitS1CircuitId
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
ciscoDlswCircuitS1Dlc
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
ciscoDlswCircuitS2Mac
The MAC address of end station 2 (S2) used for this circuit.
Syntax: MacAddress
Max-Access: Not-accessible
ciscoDlswCircuitS2Sap
The SAP at end station 2 (S2) used for this circuit.
Syntax: Octet String (SIZE(1))
Max-Access: Not-accessible
ciscoDlswCircuitS2Location
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
ciscoDlswCircuitS2TDomain
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
ciscoDlswCircuitS2TAddress
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
ciscoDlswCircuitS2CircuitId
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
ciscoDlswCircuitOrigin
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
ciscoDlswCircuitEntryTime
The value of ciscoDlswUpTime when this circuit table conceptual row was created.
Syntax: DlswTimeStamp
Max-Access: Read-only
ciscoDlswCircuitStateTime
The value of ciscoDlswUpTime when this circuit entered the current state.
Syntax: DlswTimeStamp
Max-Access: Read-only
ciscoDlswCircuitState
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
ciscoDlswCircuitPriority
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
Notifications for Cisco DLSw Group
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.
ciscoDlswTrapTConnUp
This trap is sent each time a transport connection enters the connected state.
Objects are ciscoDlswTConnOperTDomain, ciscoDlswTConnOperRemoteTAddr.
ciscoDlswTrapTConnDown
This trap is sent each time a transport connection enters the disconnected state.
Objects are ciscoDlswTConnOperTDomain, ciscoDlswTConnOperRemoteTAddr.
ciscoDlswTrapCircuitUp
This trap is sent each time a circuit enters the connected state.
Objects are ciscoDlswCircuitS1Mac, ciscoDlswCircuitS1Sap, ciscoDlswCircuitS2Mac, ciscoDlswCircuitS2Sap.
ciscoDlswTrapCircuitDown
This trap is sent each time a circuit enters the disconnected state.
Objects are ciscoDlswCircuitS1Mac, ciscoDlswCircuitS1Sap, ciscoDlswCircuitS2Mac, ciscoDlswCircuitS2Sap.
Cisco Discovery Protocol (CDP) Group
The MIB module in this section describes the management of the Cisco Discovery Protocol (CDP) in Cisco devices.
cdpInterfaceTable
The (conceptual) table containing the status of CDP on the device's interfaces.
Syntax: SEQUENCE OF CdpInterfaceEntry
Max-Access: Not-accessible
cdpInterfaceEntry
Specifies an entry (conceptual row) in the cdpInterfaceTable containing the status of CDP on an interface.
Syntax: CdpInterfaceEntry
Max-Access: Not-accessible
cdpInterfaceIfIndex
Specifies the ifIndex value of the local interface. For 802.3 Repeaters on which the repeater ports do not have ifIndex values assigned, this value is a unique value for the port, and greater than any ifIndex value supported by the repeater; in this case, the specific port is indicated by corresponding values of cdpInterfaceGroup and cdpInterfacePort, where these values correspond to the group number and port number values of RFC 1516.
Syntax: Integer32
Max-Access: Not-accessible
cdpInterfaceEnable
Provides an indication of whether the Cisco Discovery Protocol is currently running on this interface.
Syntax: TruthValue
Max-Access: Read-write
cdpInterfaceMessageInterval
Specifies the interval at which CDP messages are to be generated on this interface. The default value is 60 seconds.
Syntax: Integer (10-300). Units are in seconds.
Max-Access: Read-write
cdpInterfaceGroup
This object is only relevant to interfaces that are repeater ports on 802.3 repeaters. In this situation, it indicates the RFC1516 group number of the repeater port which corresponds to this interface.
Syntax: Integer32
Max-Access: Read-only
cdpInterfacePort
This object is only relevant to interfaces that are repeater ports on 802.3 repeaters. In this situation, it indicates the RFC1516 port number of the repeater port that corresponds to this interface.
Syntax: Integer32
Max-Access: Read-only
End of Table
cdpCacheTable
Specifies the (conceptual) table containing the cached information obtained by means of receiving CDP messages.
Syntax: SEQUENCE OF CdpCacheEntry
Max-Access: Not-accessible
cdpCacheEntry
Specifies an entry (conceptual row) in the cdpCacheTable containing the information received by means of CDP on one interface from one device.
Syntax: CdpCacheEntry
Max-Access: Not-accessible
cdpCacheIfIndex
Normally specifies the ifIndex value of the local interface. For 802.3 Repeaters for which the repeater ports do not have ifIndex values assigned, this value is a unique value for the port, and greater than any ifIndex value supported by the repeater; the specific port number, in this case, is given by the corresponding value of cdpInterfacePort.
Syntax: Integer32
Max-Access: Not-accessible
cdpCacheDeviceIndex
Specifies a unique value for each device from which CDP messages are being received.
Syntax: Integer32
Max-Access: Not-accessible
cdpCacheAddressType
Provides an indication of the type of address contained in the corresponding instance of cdpCacheAddress.
Syntax: CiscoNetworkProtocol
Max-Access: Read-only
cdpCacheAddress
Specifies the (first) network-layer address of the device's SNMP-agent as reported in the most recent CDP message. For example, if the corresponding instance of cacheAddressType had the value ip(1), then this object would be an IP-address.
Syntax: CiscoNetworkAddress
Max-Access: Read-only
cdpCacheVersion
Specifies the Version string as reported in the most recent CDP message. The zero-length string indicates no Version field (TLV) was reported in the most recent CDP message.
Syntax: DisplayString
Max-Access: Read-only
cdpCacheDeviceId
Specifies the Device-ID string as reported in the most recent CDP message. The zero-length string indicates no Device-ID field (TLV) was reported in the most recent CDP message.
Syntax: DisplayString
Max-Access: Read-only
cdpCacheDevicePort
Specifies the Port-ID string as reported in the most recent CDP message. This will typically be the value of the ifName object (for example, Ethernet0). The zero-length string indicates no Port-ID field (TLV) was reported in the most recent CDP message.
Syntax: DisplayString
Max-Access: Read-only
cdpCachePlatform
Specifies the device's hardware platform as reported in the most recent CDP message. The zero-length string indicates that no Platform field (TLV) was reported in the most recent CDP message.
Syntax: DisplayString
Max-Access: Read-only
cdpCacheCapabilities
Specifies the device's functional capabilities as reported in the most recent CDP message. For 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
Cisco DownStream Physical Unit (DSPU) Group
The variables described in this section provide the necessary information for the definition and management of DSPU objects.
dspuNodeRsrb
Specifies whether the RSRB feature is enabled for the DSPU node.
Syntax: TruthValue
Max-Access: Read-only
dspuNodeRsrbLocalVirtualRing
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
dspuNodeRsrbBridgeNumber
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
dspuNodeRsrbTargetVirtualRing
Specifies the target virtual ring number used for RSRB. TargetVirtualRing is zero if RSRB not enabled.
Syntax: Integer (0-4096)
Max-Access: Read-only
dspuNodeRsrbVirtualMacAddress
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
dspuNodeDefaultPu
Specifies if the default PU feature is enabled for the DSPU node. The default value is disabled (2).
Syntax: TruthValue
Max-Access: Read-only
dspuNodeDefaultPuWindowSize
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
dspuNodeDefaultPuMaxIframe
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
dspuNodeActivationWindow
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
dspuNodeLastConfigChgTime
Specifies the last change to DSPU configuration parameters. LastConfigChgTime reflects any change in DSPU configuration.
Syntax: TimeStamp
Max-Access: Read-only
dspuPoolClassTable
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
dspuPoolClassEntry
Each entry represents a defined pool class.
Syntax: DspuPoolClassEntry
Max-Access: Not-accessible
dspuPoolClassIndex
Specifies the index of pool class entry defined in the dpsuPoolClassTable.
Syntax: Integer32 (0-2147483647)
Max-Access: Not-accessible
dspuPoolClassName
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
dspuPooledLuTable
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
dspuPooledLuEntry
Each entry represents an LU that is defined as a member of the specified pool class.
Syntax: DspuPooledLuEntry
Max-Access: Not-accessible
dspuPooledLuPeerPuIndex
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
dspuPuAdminTable
Table listing all defined upstream or downstream PUs that are owned by the DSPU node.
Note
Syntax: SEQUENCE OF DspuPuAdminEntry
Max-Access: Not-accessible
dspuPuAdminEntry
Each entry represents a defined upstream or downstream PU.
Syntax: DspuPuAdminEntry
Max-Access: Not-accessible
dspuPuAdminIndex
Specifies the index of a PU in the dspuPuAdminTable.
Syntax: Integer32 (0-2147483647)
Max-Access: Not-accessible
dspuPuAdminName
Specifies the name of the upstream or downstream PU.
Syntax: DisplayString (SIZE (0-8))
Max-Access: Read-only
dspuPuAdminType
Specifies PU type as either upstream or downstream.
Syntax: Integer 1 = upstreamPu, 2 = dnstreamPu
Max-Access: Read-only
dspuPuAdminRemoteMacAddress
Specifies the media access control (MAC) address of the remote PU.
Syntax: MacAddress
Max-Access: Read-only
dspuPuAdminRemoteSapAddress
Specifies the SAP address of the remote PU.
Syntax: Integer (1-254)
Max-Access: Read-only
dspuPuAdminLocalSapAddress
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
dspuPuAdminXid
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
dspuPuAdminXidFmt
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
dspuPuAdminWindowSize
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
dspuPuAdminMaxIframe
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
dspuPuAdminLinkRetryCount
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
dspuPuAdminLinkRetryTimeout
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
dspuPuAdminStartPu
Specifies whether the dspuNode should attempt link activation with the remote PU.
Syntax: TruthValue
Max-Access: Read-only
dspuPuAdminDlcType
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
dspuPuAdminDlcUnit
Specifies the DLC unit used by the dspuNode for link activation with the remote PU.
Syntax: Integer (0-255)
Max-Access: Read-only
dspuPuAdminDlcPort
Specifies the DLC port used by the dspuNode for link activation with the remote PU.
Syntax: Integer (0-255)
Max-Access: Read-only
dspuPuAdminFocalPoint
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
dspuPuAdminRowStatus
Specifies the status of a row entry in the dspuPuAdminTable.
Syntax: RowStatus
Max-Access: Read-only
dspuPuAdminRemoteAddress
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
dspuPuOperTable
Table listing all active upstream or downstream PUs that are owned by the DSPU node (including default PUs).
Note
Syntax: SEQUENCE OF DspuPuOperEntry
Max-Access: Not-accessible
dspuPuOperEntry
Each entry represents an active upstream or downstream PU.
Syntax: DspuPuOperEntry
Max-Access: Not-accessible
dspuPuOperIndex
Specifies the index of a PU entry in the dspuPUOperTable.
Syntax: Integer32 (0-2147483647)
Max-Access: Read-only
dspuPuOperName
Specifies the name of the PU.
Syntax: DisplayString (SIZE (0-8))
Max-Access: Read-only
dspuPuOperType
Specifies the PU type as either upstream or downstream.
Syntax: Integer 1 = upstreamPu, 2 = dnstreamPu
Max-Access: Read-only
dspuPuOperRemoteMacAddress
Specifies the media access control (MAC) address of the remote PU.
Syntax: MacAddress
Max-Access: Read-only
dspuPuOperRemoteSapAddress
Specifies the SAP address of the remote PU.
Syntax: Integer (0-254)
Max-Access: Read-only
dspuPuOperLocalSapAddress
Specifies the SAP address of the local PU used by the dspuNode.
Syntax: Integer (1-254)
Max-Access: Read-only
dspuPuOperXid
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
dspuPuOperXidFmt
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
dspuPuOperWindowSize
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
dspuPuOperMaxIframe
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
dspuPuOperLinkRetryCount
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
dspuPuOperLinkRetryTimeout
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
dspuPuOperStartPu
Specifies whether the dspuNode should attempt link activation with the remote PU.
Syntax: TruthValue
Max-Access: Read-only
dspuPuOperDlcType
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
dspuPuOperDlcUnit
Specifies the DLC unit used by the dspuNode for link activation with the remote PU.
Syntax: Integer (0-255)
Max-Access: Read-only
dspuPuOperDlcPort
Specifies the DLC port used by the dspuNode for link activation with the remote PU.
Syntax: Integer (0-255)
Max-Access: Read-only
dspuPuOperFocalPoint
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
dspuPuOperState
Specifies the operational state of the PU as either active or inactive.
Syntax: Integer 1 = active, 2 = inactive
Max-Access: Read-only
dspuPuOperFsmState
Specifies the current FSM state of the PU.
Syntax: Integer
The defined FSM state values are defined as follows:
Max-Access: Read-only
dspuPuOperStartTime
Specifies the timestamp of PU activation—when a positive ACTPU response is received.
Syntax: TimeStamp
Max-Access: Read-only
dspuPuOperLastStateChgTime
Specifies the TimeStamp of the last PU state change between active and inactive.
Syntax: TimeStamp
Max-Access: Read-only
dspuPuOperRemoteAddress
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
dspuPuStatsTable
Table listing the statistics recorded for each PU.
Syntax: SEQUENCE OF DspuPuStatsEntry
Max-Access: Not-accessible
dspuPuStatsEntry
Each entry represents an active upstream or downstream PU and has a corresponding entry in the dspuOperPuTable.
Syntax: DspuPuStatsEntry
Max-Access: Not-accessible
dspuPuStatsSentBytes
Specifies the number of bytes sent by this PU.
Syntax: Counter32
Access: Read-only
dspuPuStatsRcvdBytes
Specifies the number of bytes received by this PU.
Syntax: Counter32
Max-Access: Read-only
dspuPuStatsSentFrames
Specifies the number of frames sent by this PU.
Syntax: Counter32
Max-Access: Read-only
dspuPuStatsRcvdFrames
Specifies the number of frames received by this PU.
Syntax: Counter32
Max-Access: Read-only
dspuPuStatsSentNegativeRsps
Specifies the number of negative responses sent by this PU.
Syntax: Counter32
Max-Access: Read-only
dspuPuStatsRcvdNegativeRsps
Specifies the number of negative responses received by this PU.
Syntax: Counter32
Max-Access: Read-only
dspuPuStatsActiveLus
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
dspuPuStatsInactiveLus
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
dspuPuStatsBindLus
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
dspuPuStatsActivationFailures
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.
Syntax: Integer
Max-Access: Read-only
End of Table
dspuLuAdminTable
Table listing all LUs owned by the PU.
Note
Syntax: SEQUENCE OF DspuLuAdminEntry
Max-Access: Not-accessible
dspuLuAdminEntry
Each entry represents a defined LU owned by the PU.
Syntax: DspuLuAdminEntry
Max-Access: Not-accessible
dspuLuAdminLuLocalAddress
Specifies the network addressable unit (NAU) address of the local LU.
Syntax: Integer (1-254)
Max-Access: Not-accessible
dspuLuAdminType
Specifies whether the LU is pooled or dedicated.
Syntax: Integer 1 = pooled, 2 = dedicated
Max-Access: Read-only
dspuLuAdminPoolClassName
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
dspuLuAdminPeerPuIndex
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
dspuLuAdminPeerLuLocalAddress
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
dspuLuAdminRowStatus
Specifies the status of a row entry in the dspuLuAdminTable.
Syntax: RowStatus
Max-Access: Read-only
End of Table
dspuLuOperTable
Table listing all LUs owned by the PU.
Note
Syntax: SEQUENCE OF DspuLuOperEntry
Max-Access: Not-accessible
dspuLuOperEntry
Each entry represents a defined LU owned by the PU.
Syntax: DspuLuOperEntry
Max-Access: Not-accessible
dspuLuOperLuLocalAddress
Specifies the NAU address of the local LU.
Syntax: Integer (1-254)
Max-Access: Read-only
dspuLuOperType
Specifies whether the LU is pooled or dedicated.
Syntax: Integer 1 = pooled, 2 = dedicated
Max-Access: Read-only
dspuLuOperPoolClassName
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
dspuLuOperPeerPuIndex
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
dspuLuOperPeerLuLocalAddress
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
dspuLuOperState
Specifies the operational state of the LU as either active or inactive.
Syntax: Integer 1 = active, 2 = inactive
Max-Access: Read-only
dspuLuOperFsmState
Specifies the current FSM state of the LU.
Syntax: Integer
Max-Access: Read-only
dspuLuOperSessionState
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.
Syntax: Integer
Max-Access: Read-only
End of Table
dspuSapTable
Table listing the SAPs that are enabled for the DSPU node.
Syntax: SEQUENCE of DspuSapEntry
Max-Access: Not-accessible
dspuSapEntry
Each entry represents an enabled SAP for the DSPU node.
Syntax: DspuSapEntry
Max-Access: Not-accessible
dspuSapAddress
Specifies the SAP address of the local SAP.
Syntax: Integer (1-254)
Max-Access: Not-accessible
dspuSapType
Specifies the local SAP type as either an upstreamSap or a downstreamSap.
Syntax: Integer 1 = upstreamSap, 2 = dnstreamSap
Max-Access: Read-only
dspuSapDlcType
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
dspuSapDlcUnit
Specifies the DLC unit of the adapter that owns the local SAP.
Syntax: Integer (0-255)
Max-Access: Read-only
dspuSapDlcPort
Specifies the DLC port of the adapter that owns the local SAP.
Syntax: Integer (0-255)
Max-Access: Read-only
dspuSapOperState
Specifies the operational state of the local SAP as follows:
•
•
•
•
Syntax: Integer 1 = sapClosed, 2 = sapOpening, 3 = sapOpened, 4 = sapClosed
Max-Access: Read-only
dspuSapRowStatus
Specifies the status of a row entry in the dspuSapTable.
Syntax: RowStatus
Max-Access: Read-only
End of Table
Notifications for Cisco DSPU Group
dspuLuStateChangeTrap
This notification indicates when the operational state of the LU changes between active and inactive. The following information is returned:
•
•
dspuLuActivationFailureTrap
This notification is generated whenever an LU activation failure is detected. The following information is returned:
•
•
•
Cisco Environmental Monitor Group
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.
ciscoEnvMonPresent
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
ciscoEnvMonVoltageStatusTable
Specifies the table of voltage status maintained by the environmental monitor.
Syntax: SEQUENCE OF CiscoEnvMonVoltageStatusEntry
Max-Access: Not-accessible
ciscoEnvMonVoltageStatusEntry
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
ciscoEnvMonVoltageStatusIndex
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
ciscoEnvMonVoltageStatusDesc
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
ciscoEnvMonVoltageStatusValue
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
ciscoEnvMonVoltageState
Specifies the current state of the testpoint being instrumented.
Syntax: CiscoEnvMonState
Max-Access: Read-only
End of Table
ciscoEnvMonTemperatureStatusTable
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
ciscoEnvMonTemperatureState
Specifies the current state of the testpoint being instrumented.
Syntax: CiscoEnvMonState
Max-Access: Read-only
End of Table
ciscoEnvMonFanStatusTable
Provides the fan status maintained by the environmental monitor.
Syntax: SEQUENCE OF CiscoEnvMonFanStatusEntry
Max-Access: Not-accessible
ciscoEnvMonFanStatusEntry
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
ciscoEnvMonFanStatusIndex
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
ciscoEnvMonFanStatusDescr
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
ciscoEnvMonFanState
Specifies the current state of the fan being instrumented.
Syntax: CiscoEnvMonState
Max-Access: Read-only
End of Table
ciscoEnvMonSupplyStatusTable
Specifies the table of power supply status maintained by the environmental monitor card.
Syntax: SEQUENCE OF CiscoEnvMonSupplyStatusEntry
Max-Access: Not-accessible
ciscoEnvMonSupplyStatusEntry
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
ciscoEnvMonSupplyStatusIndex
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
ciscoEnvMonSupplyStatusDescr
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
ciscoEnvMonSupplyState
Specifies the current state of the power supply being instrumented.
Syntax: CiscoEnvMonState
Max-Access: Read-only
End of Table
SNMPv2 Notifications Used in Cisco Environmental Monitoring
The following object identifiers are used to define SNMPv2 notifications that are backward compatible with SNMPv1 notifications, along with their associated notification enables:
ciscoEnvMonEnables
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
ciscoEnvMonNotifications
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.
ciscoEnvMonFanNotification
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.
Cisco Flash Group
The variables described in this section apply to the Cisco Flash MIB definitions.
ciscoFlashDevicesSupported
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
ciscoFlashDeviceTable
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.
Note
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
ciscoFlashDeviceEntry
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
ciscoFlashDeviceIndex
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
ciscoFlashDeviceSize
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
ciscoFlashDeviceMaxPartitions
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
ciscoFlashDevicePartitions
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
ciscoFlashDeviceChipCount
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
ciscoFlashDeviceName
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
ciscoFlashDeviceDescr
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
ciscoFlashDeviceController
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
ciscoFlashDeviceCard
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
ciscoFlashDeviceInitTime
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
ciscoFlashDeviceRemovable
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
ciscoFlashChipTable
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
Note
ciscoFlashChipEntry
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
ciscoFlashChipIndex
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
ciscoFlashChipCode
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
ciscoFlashChipDescr
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
ciscoFlashChipWriteRetries
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
ciscoFlashChipEraseRetries
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.
Note
Syntax: Counter32
Max-Access: Read-only
ciscoFlashChipMaxWriteRetries
Specifies the maximum number of write retries done at any single location before declaring a write failure.
Syntax: Integer32
Max-Access: Read-only
ciscoFlashChipMaxEraseRetries
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
Flash Partition Level Information
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.
Note
Partitioning has the following restrictions:
•
•
•
ciscoFlashPartitionTable
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
ciscoFlashPartitionEntry
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
ciscoFlashPartitionIndex
Specifies the Flash partition sequence number used to index within table of initialized Flash partitions.
Syntax: Integer32 (1-8)
Max-Access: Not-accessible
ciscoFlashPartitionStartChip
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
ciscoFlashPartitionEndChip
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
ciscoFlashPartitionSize
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
ciscoFlashPartitionFreeSpace
Specifies in bytes the free space within a Flash partition.
Note
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
ciscoFlashPartitionStatus
Specifies that Flash partition status can be one of the following:
•
The ciscoFlashDeviceProgrammingJumper, ciscoFlashChipCode, and ciscoFlashChipDescr objects can be examined to get more details on the cause of this status.
•
•
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.
Table 3-1 Partition Status
Syntax: Integer
Max-Access: Read-only
ciscoFlashPartitionName
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
ciscoFlashFileTable
This table specifies the table of information for files in a Flash partition.
Syntax: SEQUENCE OF CiscoFlashFileEntry
Max-Access: Not-accessible
ciscoFlashFileEntry
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
ciscoFlashFileIndex
Specifies the Flash file sequence number used to index within a Flash partition directory table.
Syntax: Integer32 (1-32)
Max-Access: Not-accessible
ciscoFlashFileSize
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
ciscoFlashFileChecksum
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
ciscoFlashFileStatus
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
ciscoFlashFileName
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
Flash operations are used for copying to or from Flash memory partitioning, and miscellaneous functions such as erasing and file verification.
ciscoFlashCopyTable
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
ciscoFlashCopyEntry
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
ciscoFlashCopySerialNumber
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
ciscoFlashCopyCommand
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. 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
Table 3-2 Copy Commands
ciscoFlashCopyProtocol
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
ciscoFlashCopyServerAddress
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
ciscoFlashCopySourceName
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:]filewhere 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
ciscoFlashCopyDestinationName
Specifies the destination file name. For a copy to Flash memory, the file name must be of the form
[device:][partition:]filewhere 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
ciscoFlashCopyRemoteUserName
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
Note
ciscoFlashCopyStatus
Specifies the status of the specified copy operation, as defined in .
Syntax: Integer
Max-Access: Read-only
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
ciscoFlashCopyTime
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
ciscoFlashCopyEntryStatus
Specifies the status of this table entry.
Syntax: RowStatus
Max-Access: Read-create
End of Table
ciscoFlashPartitioningTable
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
ciscoFlashPartitioningEntry
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
ciscoFlashPartitioningCommand
Specifies the partitioning command to be executed. Mandatory. If the command is unsupported, the partitioningInvalidOperation error will be reported in the operation status. shows the command and its parameters.
Syntax: Integer 1 = partition
Max-Access: Read-create
Table 3-4 Partitioning Command
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
ciscoFlashPartitioningStatus
Specifies the status of the specified partitioning operation ().
Syntax: Integer
Max-Access: Read-only
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
ciscoFlashPartitioningTime
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
ciscoFlashMiscOpTable
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
ciscoFlashMiscOpEntry
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
ciscoFlashMiscOpSerialNumber
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
ciscoFlashMiscOpCommand
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 . lists command parameters.
Syntax: Integer 1 = erase, 2 = verify, 3 = delete, 4 = undelete, 5 = squeeze
Max-Access: Read-create
Table 3-7 Flash Command Parameters
ciscoFlashMiscOpDestinationName
Specifies the destination file, or partition name. The file name must be of the following form:
[device:][partition:]filewhere 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
ciscoFlashMiscOpStatus
Specifies the status of the given operation ().
Syntax: Integer
Max-Access: Read-only
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
ciscoFlashMiscOpTime
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
ciscoFlashMiscOpEntryStatus
Specifies the status of this table entry.
Syntax: RowStatus
Max-Access: Read-create
End of Table
ciscoFlashMIBTraps
The following notifications are supported with the ciscoFlash MIB:
ciscoFlashCopyCompletionTrap
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.
ciscoFlashDeviceChangeTrap
A ciscoFlashDeviceChangeTrap is sent whenever a removable Flash device is inserted or removed.
Cisco Integrated Channel Service Unit/Data Service Unit (CSU/DSU) Group
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.
CSU/DSU Static Configuration Table
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.
ciscoICsuDsuStaticConfigTable
Syntax: SEQUENCE OF CiscoICsuDsuStaticConfigEntry
Max-Access: Not-accessible
ciscoICsuDsuStaticConfigEntry
An entry in the static configuration table for each integrated CSU/DSU.
Syntax: CiscoICsuDsuStaticConfigEntry
Max-Access: Not-accessible
ciscoICsuDsuType
Specifies the type of line interface or CSU/DSU.
Syntax: Integer 1 = fractionalT1, 2 = twoWireSwitched56k, 3 = fourWireSwitched56k, 4 = unknown
Max-Access: Read-only
ciscoICsuDsuHwRevision
The CSU/DSU hardware revision.
Syntax: DisplayString (SIZE (1-16))
Max-Access: Read-only
ciscoICsuDsuSwRevision
The CSU/DSU software revision.
Syntax: DisplayString (SIZE (1-16))
Max-Access: Read-only
ciscoICsuDsuProtocolRevision
The protocol revision of the CSU/DSU.
Syntax: DisplayString (SIZE (1-16))
Max-Access: Read-only
End of Table
CSU/DSU Test Report Table
The CSU/DSU test report table. The table contains the results of user-initiated tests, including self-test, reset, and loopback.
ciscoICsuDsuTestReportTable
Syntax: SEQUENCE OF CiscoICsuDsuTestReportEntry
Max-Access: Not-accessible
ciscoICsuDsuTestReportEntry
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
ciscoICsuDsuNumResets
The number of times CSU/DSU has been reset.
Syntax: Counter32
Max-Access: Read-only
ciscoICsuDsuTimeOfLastReset
The SysUpTime of last CSU/DSU reset.
Syntax: TimeStamp
Max-Access: Read-only
ciscoICsuDsuLoopbackStatus
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
ciscoICsuDsuLoopbackNumErrors
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
ciscoICsuDsuLoopbackDuration
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
ciscoICsuDsuLoopbackPoint
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:
The meanings of these integers for a switched 56-kbps CSU/DSU are as follows:
Max-Access: Read-only
ciscoICsuDsuLoopbackPattern
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:
The following patterns are valid only for switched 56-kbps CSU/DSUs:
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
ciscoICsuDsuLoopbackCode
Loopback code used to initiate last remote loopback. This variable is valid only if a remote loopback was last performed.
Syntax: Integer of 1, 2, or 3 representing a loopback code, as follows:
Max-Access: Read-only
ciscoICsuDsuEndTimeOfLastLoopback
SysUpTime of completion of last loopback test execution.
Syntax: TimeStamp
Max-Access: Read-only
End of Table
T1 CSU/DSU Module Configuration Table
This table contains current CSU/DSU configuration parameters for a T1 interface not covered by RFC 1406.
ciscoICsuDsuT1ConfigTable
Syntax: SEQUENCE OF CiscoICsuDsuT1ConfigEntry
Max-Access: Not-accessible
ciscoICsuDsuT1ConfigEntry
An entry in the configuration table for each integrated T1 CSU/DSU.
Syntax: CiscoICsuDsuT1ConfigEntry
Max-Access: Not-accessible
ciscoICsuDsuT1LineBuildOut
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.
Syntax: Integer of 1, 2, or 3 representing a line build-out value, as follows:
Max-Access: Read-only
ciscoICsuDsuT1DteLineCode
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.
Syntax: Integer of 1, 2, or 3 representing a loopback code, as follows:
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.
Syntax: Integer of 1, 2, 3, or 4 representing a loopback code, as follows:
Max-Access: Read-only
End of Table
T1 CSU/DSU Status Table
This table contains information about the status of the CSU/DSU on a T1 interface, including externally generated alarm conditions.
ciscoICsuDsuT1StatusTable
Syntax: SEQUENCE OF CiscoICsuDsuT1StatusEntry
Max-Access: Not-accessible
ciscoICsuDsuT1StatusEntry
An entry in the status table for each integrated T1 CSU/DSU.
Syntax: CiscoICsuDsuT1StatusEntry
Max-Access: Not-accessible
ciscoICsuDsuT1LoopStatus
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:
Syntax: Integer32
Max-Access: Read-only
ciscoICsuDsuT1LossOfSignals
The number of times a lossofSignal (LOS) event has been detected.
Syntax: Counter32
Max-Access: Read-only
ciscoICsuDsuT1LossOfFrames
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
Switched 56-kpbs CSU/DSU Module Configuration Table
This table contains current CSU/DSU configuration parameters for a switched 56-kbps network.
ciscoICsuDsuSw56kConfigTable
Syntax: SEQUENCE OF CiscoICsuDsuSw56kConfigEntry
Max-Access: Not-accessible
ciscoICsuDsuSw56kConfigEntry
An entry in the configuration table for each integrated switched 56-kbps CSU/DSU.
Syntax: CiscoICsuDsuSw56kConfigEntry
Max-Access: Not-accessible
ciscoICsuDsuSw56kNetworkType
This variable configures the DSU module for the specific type of network being used.
Syntax: Integer of 1, 2, 3, or 4 representing a network type, as follows:
Max-Access: Read-only
ciscoICsuDsuSw56kClockSource
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
ciscoICsuDsuSw56kLoopRate
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
Switched 56-kbps CSU/DSU Module Status 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.
Syntax: Integer of 1, 2, 3, 4, 5, or 6 representing a dialing status, as follows:
Max-Access: Read-only
ciscoICsuDsuSw56kLoopStatus
The current loop status or alarm condition. Represented as a sum of a bit map. The variable bit positions are:
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
Notifications for Cisco Integrated CSU/DSU
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.
Cisco Integrated Services Digital Network (ISDN) Group
This group describes the status of the ISDN Interfaces on Cisco devices.The ISDN hardware interface Basic Rate Interface (BRI) or Primary Rate Interface (PRI) is represented by the D channel. The interface has an ifType value of basicISDN(20) or primaryISDN(21). For related information, refer to RFC 1213.
Each B channel is also represented in an entry in the ifTable. The B channels has an ifType value of other(1). This model is used in defining objects and tables for management.
The ISDN MIB allows 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.
demandNbrTable
Specifies the list of neighbors from which the router accepts calls or to which it places them.
Syntax: SEQUENCE OF DemandNbrEntry
Max-Access: Not-accessible
demandNbrEntry
Specifies a single Neighbor. This entry is effectively permanent, and contains information describing the neighbor, its permissions, its last call attempt, and its cumulative effects.
Syntax: DemandNbrEntry
Max-Access: Not-accessible
demandNbrPhysIf
Specifies the ifIndex value of the physical interface the neighbor is called on. On an ISDN interface, this is the ifIndex value of the D channel.
Syntax: Integer32 (1-2147483647)
Max-Access: Not-accessible
demandNbrId
Specifies an arbitrary sequence number associated with the neighbor.
Syntax: Integer32
Max-Access: Not-accessible
demandNbrLogIf
Specifies the ifIndex value of 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
demandNbrName
Specifies the ASCII name of the neighbor.
Syntax: DisplayString
Max-Access: Read-create
demandNbrAddress
Specifies the call address at which the neighbor should be called. Consider this address as the set of characters following "ATDT" or the "phone number" included in a D channel call request.
Syntax: DisplayString
Max-Access: Read-create
demandNbrPermission
Specifies the applicable permissions.
Syntax: Integer 1 = iCanCallHim, 2 = heCanCallMe, 3 = weCanCallEachOther
Max-Access: Read-create
demandNbrMaxDuration
Maximum call duration in seconds. Zero means "unlimited".
Syntax: Integer32 (1-2147483647)
Max-Access: Read-create
demandNbrLastDuration
Specifies the duration of last call in seconds.
Syntax: Integer32 (1-2147483647)
Max-Access: Read-only
demandNbrClearReason
Specifies the ASCII reason that the last call terminated.
Syntax: DisplayString
Max-Access: Read-only
demandNbrClearCode
Specifies the encoded reason for the last call tear down.
Syntax: Octet string
Max-Access: Read-only
demandNbrSuccessCalls
Specifies the number of completed calls to neighbor since system reset.
Syntax: Counter32
Max-Access: Read-only
demandNbrFailCalls
Specifies the number of call attempts that have failed.
Syntax: Counter32
Max-Access: Read-only
demandNbrAcceptCalls
Specifies the number of calls accepted from the neighbor.
Syntax: Counter32
Max-Access: Read-only
demandNbrRefuseCalls
Specifies the number of calls from the neighbor that have been refused.
Syntax: Counter32
Max-Access: Read-only
demandNbrLastAttemptTime
Specifies the sysUpTime of last call attempt.
Syntax: TimeStamp
Max-Access: Read-only
demandNbrStatus
Enables a new vendor to manage the device using SNMP.
Syntax: RowStatus
Max-Access: Read-create
End of Table
Trap Related to Connection Management
This section describes the trap associated with the Cisco ISDN group.
demandNbrCallInformation
This trap/inform is sent to the manager whenever a successful call clears, or a failed call attempt is determined to have ultimately failed. In the event that call retry is active, then the trap is sent after all retry attempts have failed. However, only one such trap is sent in between successful call attempts; subsequent call attempts result in no trap.
Cisco Interface Queue Group
The variables described in this section are used to manage interface queuing in Cisco devices.
cQIfTable
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
cQIfQType
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
cQIfTxLimit
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
cQIfSubqueues
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
cQStatsTable
This table contains statistical objects for the subqueues of a Cisco interface.
Syntax: SEQUENCE OF CQStatsEntry
Max-Access: Not-accessible
cQStatsQNumber
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
cQStatsDepth
The number of messages in the subqueue.
Syntax: Gauge32
Max-Access: Read-only
cQStatsMaxDepth
The maximum number of messages permitted in the subqueue.
Syntax: Integer32
Max-Access: Read-only
cQStatsDiscards
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
cQRotationTable
This table describes the rotation of custom queuing on an interface.
Syntax: SEQUENCE OF CQRotationEntry
Max-Access: Not-accessible
cQRotationOctets
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
Cisco IP Encryption Group
The variables described in this section are used to manage IP encryption.
cieConfiguredAlgorithms
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
cieEncryptionKeyTimeout
The interval at which keys expire for a session and are renegotiated.
Syntax: Integer32
Max-Access: Read-only
cieNumberOfCryptoEngines
The total number of encryption engines.
Syntax: Gauge32
Max-Access: Read-only
cieEngineStatusTable
A table describing status of all encryption engines present within the router.
Syntax: SEQUENCE OF CieEngineStatusEntry
Max-Access: Not-accessible
cieEngineStatusEntry
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
cieEngineID
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
cieEngineCardIndex
Corresponds to cardIfIndex in the Chassis MIB. If the value is 0, this is a software encryption engine.
Syntax: Integer32
Max-Access: Read-only
cieEnginePublicKey
The public key for a particular encryption engine.
Syntax: Octet String (SIZE (0-1024))
Max-Access: Read-only
cieEpaTampered
Indicates whether the encryption port adaptor (EPA) has been tampered with.
Note
Syntax: TruthValue
Max-Access: Read-only
cieEpaAuthenticated
Indicates whether the encryption port adaptor (EPA) has been properly authenticated for this router.
Note
Syntax: TruthValue
Max-Access: Read-only
cieEpaMode
Indicates the current operating mode of the EPA card. This variable directly corresponds to LED status shown on the encryption port adapter (EPA).
Note
Syntax: Integer, 1 = enableActive, 2 = boot, 3 = error
Max-Access: Read-only
End of Table
cieNumberOfConnections
The total number of active, pending, and dead encryption connections.
Syntax: Gauge32
Max-Access: Read-only
cieConnTable
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
cieConnEntry
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
cieConnIndex
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
cieProtectedAddr
The IP address for protected (secure) node.
Syntax: IpAddress
Max-Access: Read-only
cieUnprotectedAddr
The IP address of the unprotected (insecure) node in the network.
Syntax: IpAddress
Max-Access: Read-only
cieConnStatus
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
ciePktsEncrypted
The total number of packets encrypted for this connection.
Syntax: Counter32
ciePktsDecrypted
The total number of packets decrypted for this connection.
Syntax: Counter32
Max-Access: Read-only
ciePktsDropped
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
cieLocalTimeEstablished
Value of sysUpTime at which the connection was established or reestablished.
Syntax: TimeStamp
Max-Access: Read-only
cieAlgorithmType
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
cieTestConnTable
A table of test encryption session entries.
Syntax: SEQUENCE OF CieTestConnEntry
Max-Access: Not-accessible
cieTestConnEntry
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
cieTestConnSerialNumber
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
cieTestConnProtectedAddr
The IP address of the protected (secure) node for the test connection.
Syntax: IpAddress
Max-Access: Read-create
cieTestConnUnprotectedAddr
The IP address of the unprotected (insecure) node for the test connection.
Syntax: IpAddress
Max-Access: Read-create
cieTestConnTrapOnCompletion
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
cieTestConnCryptoMapName
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
cieTestConnCryptoMapTagNumber
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
cieTestConnSessionStatus
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
cieTestConnEntryOwner
The entity that configured this entry.
Syntax: OwnerString
Max-Access: Read-create
cieTestConnEntryStatus
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
Notification for Cisco IP Encryption Group
The following notification is supported with the Cisco IP Encryption MIB:
cieTestCompletion
A cieTestCompletion trap is sent at the completion of an encryption session establishment if such a trap was requested when the sequence was initiated.
Cisco LAN Emulation (LANE) Broadcast-and-Unknown Server Group
The variables described in this section are used to manage LAN Emulation (LANE) broadcast-and-unknown servers.
busTable
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
busEntry
An entry (conceptual row) in the busTable.
Syntax: BusEntry
Max-Access: Not-accessible
busElanName
The emulated LAN name of the designated bridge.
Syntax: DisplayString (1-32)
Max-Access: Not-accessible
busIndex
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
busAtmAddrSpec
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
busAtmAddrMask
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
busAtmAddrActl
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
busIfIndex
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
busSubIfNum
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
busUpTime
The value of sysUpTime when this broadcast-and-unknown server became enabled.
Syntax: TimeStamp
Max-Access: Read-only
busLanType
The type of legacy LAN in which this broadcast-and-unknown server participates. The default value is dot3.
Syntax: Integer 1 = dot3, 2 = dot5
