CISCO-SNA-LLC-MIB

Integer32 (0..65535)

This value represents a virtual LLC port. It is assigned by the agent. This value is set to 0 by the agent for interfaces identified by the ifIndex value that do not support virtual interfaces.

DisplayStringRepresents textual information taken from the NVT ASCII character set, as defined in pages 4, 10-11 of RFC 854. To summarize RFC 854, the NVT ASCII repertoire specifies: - the use of character codes 0-127 (decimal) - the graphics characters (32-126) are interpreted as US ASCII - NUL, LF, CR, BEL, BS, HT, VT and FF have the special meanings specified in RFC 854 - the other 25 codes have no standard interpretation - the sequence 'CR LF' means newline - the sequence 'CR NUL' means carriage-return - an 'LF' not preceded by a 'CR' means moving to the same column on the next line. - the sequence 'CR x' for any x other than LF or NUL is illegal. (Note that this also means that a string may end with either 'CR LF' or 'CR NUL', but not with CR.) Any object defined using this syntax may not exceed 255 characters in length. SIZE (1..8) · OCTET STRING · hint 255a

An octet string that defines the virtual port to which this interface is assigned. Its value shall be unique within the administered system. It must contain only ASCII printable characters. A write operation shall not take effect until the port is cycled inactive.

Gauge32

This parameter specifies the maximum number of SAPs that can be defined for this port.

Gauge32

This parameter specifies the maximum number of connection components that can be administratively defined for this port.

Integer32 · octets

Reference: ISO 8802-2 : 1989, ANSI/IEEE 802.2 - 1989 Section 7.8.3 Maximum Number of Octets in an I PDU, N1.

This object denotes the default maximum I PDU size, in octets, that LLCs on this port may send to their remote LLC partners. This count is referred to as 'N1' in the IEEE 802.2 specification [5]. This port default value may be overridden by a non-zero SAP default value in the llcSapAdminMaxIPDUOctetsSend object or by a non-zero value in the llcCcAdminMaxIPDUOctetsSend object. At connection setup, the remote LLC may send, using an XID frame, the maximum I PDU size which it is prepared to receive. If so, an implementation may choose to override the administered maximum PDU size with the dynamically learned value and should reflect this in the llcCcOperMaxIPDUOctetsSend object for the connection component. The I PDU size includes all octets in a frame, excluding framing characters, the MAC header and link header.

INTEGER (1..127) · Integer32

Reference: ISO 8802-2 : 1989, ANSI/IEEE 802.2 - 1989 Section 7.8.4 Maximum Number of Outstanding I PDUs, k.

This object denotes the default maximum consecutive unacknowledged I PDU frames that LLCs on this port may send to their remote LLC partners. This count is referred to as 'k' in the IEEE 802.2 specification [5]. This port default value may be overridden by a non-zero SAP default value in the llcSapAdminMaxUnackedIPDUsSend object or by a non-zero value in the llcCcAdminMaxUnackedIPDUsSend object. At connection setup, the remote LLC may send, using an XID frame, the maximum number of unacknowledged I PDUs which it is prepared to receive. If so, an implementation may choose to override the administered maximum number of unacknowledged PDUs with the dynamically learned value and should reflect this in the llcCcOperMaxUnackedIPDUsSend object for the connection component.

INTEGER (1..127) · Integer32

Reference: ISO 8802-2 : 1989, ANSI/IEEE 802.2 - 1989 Section 7.8.4 Maximum Number of Outstanding I PDUs, k.

This object denotes the default maximum number of unacknowledged I PDUs that LLCs on this port can expect to receive from their remote LLC partners. This count is referred to as 'k' in the IEEE 802.2 specification [5]. This port default value may be overridden by a non-zero SAP default value in the llcSapAdminMaxUnackedIPDUsRcv object or by a non-zero value in the llcCcAdminMaxUnackedIPDUsRcvd object. At connection setup, an implementation may choose to send this value to the remote LLC, using an XID frame.

Integer32

Reference: ISO 8802-2 : 1989, ANSI/IEEE 802.2 - 1989 Section 7.8.2 Maximum Number of Transmissions, N2.

This object denotes the default value for the maximum number of times which LLCs on this port shall retry a PDU following the expiration of the acknowledgement timer, the P-bit timer or the reject timer. When these retries are exhausted, the link shall be declared inactive. This count is referred to as 'N2' in the IEEE 802.2 specification [5]. This port default value may be overridden by a non-zero SAP default value in the llcSapAdminMaxretransmits object or by a non-zero value in the llcCcAdminMaxRetransmits object.

TimeTicks

Reference: ISO 8802-2 : 1989, ANSI/IEEE 802.2 - 1989 Section 7.8.1.1 Acknowledgment Timer

This object denotes the default value for the time interval during which the LLCs on this port shall expect to receive either: 1) an acknowledgement to one or more outstanding I PDUs. or 2) a response PDU to an unnumbered command PDU. The expiration of this timer shall cause the unacknowledged frames to be retransmitted (up to N2 times). For Implementations that only use a single 'T1' Value (ref. IBM Token-Ring Network technical reference Chapter 11). This object will be used to control/read the value. This port default value may be overridden by a non-zero value in the llcSapAdminAckTimer object or by a non-zero value in the llcCcAdminAckTimer object.

TimeTicks

Reference: ISO 8802-2 : 1989, ANSI/IEEE 802.2 - 1989 Section 7.8.1.2 P-Bit Timer

This object denotes the default value for the time interval during which the LLCs on this port shall expect to receive a PDU with the F bit set to '1' in response to a Type 2 command with the P bit set to '1'. The expiration of this timer shall cause the command with the poll bit to be retransmitted (up to N2 times). This port default value may be overridden by a non-zero SAP default value in the llcSapAdminPbitTimer object or by a non-zero value in the llcCcAdminPbitTimer object.

TimeTicks

Reference: ISO 8802-2 : 1989, ANSI/IEEE 802.2 - 1989 Section 7.8.1.3 Reject Timer

This object denotes the default value for the time interval during which the LLCs on this port shall expect to receive a reply to a REJ PDU. The expiration of this timer shall cause the REJ PDU to be retransmitted (up to N2 times). This port default value may be overridden by a non-zero SAP default value in the llcSapAdminRejTimer object or by a non-zero value in the llcCcAdminRejTimer object.

TimeTicks

Reference: ISO 8802-2 : 1989, ANSI/IEEE 802.2 - 1989 Section 7.8.1.4 Busy-State Timer

This object denotes the default value for the time interval during which the LLCs on this port shall expect to receive an indication that a busy condition at the remote LLC has cleared. The expiration of this timer shall cause the link to be declared inactive. This port default value may be overridden by a non-zero SAP default value in the llcSapAdminBusyTimer object or by a non-zero value in the llcCcAdminBusyTimer object.

TimeTicks

Reference: IBM Token-Ring Network Architecture Ref. SC30-3374 Chapter 11: Operation of Link Stations Inactivity Timer (Ti)

This object denotes the default value for the time interval during which the LLCs on this port shall expect to receive any PDU from the remote LLC. This function is not described in the IEEE 802.2 specification [5]. It is listed in the IBM Token-Ring Network Architecture [6] Reference as the Ti parameter and is widely implemented. The expiration of this timer shall cause the local LLC to send a PDU to the remote LLC with the P bit set to '1'. The value for llcPortAdminInactTimer must be much greater than the value for llcPortAdminDelayAckTimer. This port default value may be overridden by a non-zero SAP default value in the llcSapAdminInactTimer object or by a non-zero value in the llcCcAdminInactTimer object. Any value for this object less than or equal to the acknowledgement timer shall mean that the timer is not used.

Integer32

Reference: IBM Token-Ring Network Architecture Ref. SC30-3374 Chapter 11: Operation of Link Stations Number of I-Format LPDUs Received before Sending Acknowledgment (N3)

This object denotes the default value for the maximum number of consecutive I PDUs which the LLCs on this port shall receive during the interval defined by llcCcOperDelayTimertime without sending an immediate acknowledgement. This must be less than or equal to the value of llcCcOperMaxUnackIPDURcv. This function is not described in the IEEE 802.2 specification [5]. It is listed in the IBM Token-Ring Network Architecture Reference [6] as the N3 parameter and is widely implemented. This port default value may be overridden by a non-zero SAP default value in the llcSapAdminDelayAckCount object or by a non-zero value in the llcCcAdminDelayCount object. A value of one indicates that acknowledgments will be sent immediately and that the value of llcPortAdminDelayAckTimer shall be ignored.

TimeTicks

Reference: IBM Token-Ring Network Architecture Ref. SC30-3374 Chapter 11: Operation of Link Stations Receiver Acknowledgment Timer (T2)

This object denotes the default value for the time interval during which the LLCs on this port shall delay acknowledgment of one or more I PDUs (up to the value of llcCcOperDelayAckCount). This function is not described in the IEEE 802.2 specification [5]. It is listed in the IBM Token-Ring Network Architecture Reference [6] as the T2 parameter and is widely implemented. The expiration of this timer shall cause the local LLC to acknowledge all unacknowledged I PDUs. This object is associated with the llcSapAdminDelayAckCount object and is only defined if that object has a value greater than one.

Integer32

Reference: IBM Token-Ring Network Architecture Ref. SC30-3374 Chapter 11: Operation of Link Stations Number of Acknowledgments Needed to Increment Ww (Nw)

This object denotes the default value for the number of IPDUs that must be acknowledged before the working window size (Ww) can be incremented by 1 when the working window is not equal to the maximum transmit window size (TW). It controls the gradual incrementing of Ww in congestion situations. This function is not described in the IEEE 802.2 specification [5]. However, it is listed in the IBM Token-Ring Network Architecture Reference [6] as the Nw parameter and is widely implemented. This port default value may be overridden by a non-zero SAP default value in the llcSapAdminNw object.

MacAddressRepresents an 802 MAC address represented in the `canonical' order defined by IEEE 802.1a, i.e., as if it were transmitted least significant bit first, even though 802.5 (in contrast to other 802.x protocols) requires MAC addresses to be transmitted most significant bit first. SIZE (6) · OCTET STRING · hint 1x:

This is the MAC Address for this local port.

Gauge32

This object defines the number of SAPs on this port that are currently enabled. In other words, this object is a count of the number of instances of llcSapOperEntry that have a llcSapOperStatus value of 'active(2)'.

Gauge32

This object reflects the highest number of SAPs active on this Port simultaneously. In other words, this object is a count of the number of instances of llcSapOperEntry on this Port.

INTEGER1 = no2 = yes · Integer32

This object reflects support for transmission and receipt of SIM and RIM control frames for this port. SIM and RIM are not defined in the ANSI/IEEE 802.2 specification [5] nor in the IBM Token Ring Architecture Reference [6]. These control frames are used for the remote program load of IBM communications processors.

TimeStampThe value of the sysUpTime object at which a specific occurrence happened. The specific occurrence must be defined in the description of any object defined using this type. If sysUpTime is reset to zero as a result of a re- initialization of the network management (sub)system, then the values of all TimeStamp objects are also reset. However, after approximately 497 days without a re- initialization, the sysUpTime object will reach 2^^32-1 and then increment around to zero; in this case, existing values of TimeStamp objects do not change. This can lead to ambiguities in the value of TimeStamp objects. · TimeTicks

This object describes the value of sysUpTime when this port definition was last modified. If the port has not been modified, then this value shall be zero.

Counter32

This object reflects the total number of PDUs that have been received on this port. This object is initialized to zero when the port is created.

Counter32

This object reflects the total number of PDUs that have been transmitted on this port. This object is initialized to zero when the port is created.

Counter32 · octets

This object reflects the total octets received on this port. This object is initialized to zero when the port is created.

Counter32 · octets

This object reflects the total octets transmitted on this port. This object is initialized to zero when the port is created.

Counter32

This object reflects the total number of TEST commands received on this port.

Counter32

This object reflects the total number of TEST responses transmitted on this port in response to TEST commands received.

Counter32

This object reflects the total number of times that the local connection components on this port have entered a busy state (RNR). This object is initialized to zero when the port is created.

Counter32

This object reflects the total number of times that a connection attempt, from a remote LLC station, for an unknown SAP was detected on this port.

INTEGER (1..255) · Integer32

The address of this local SAP.

Integer32 · octets

This object denotes the default maximum I PDU size, in octets, that LLCs on this SAP may send to their remote connection component partners. This count is referred to as 'N1' in the IEEE 802.2 specification [5]. A zero value for this object indicates that the port default, llcPortAdminMaxIPDUOctetsSend, shall be used as the SAP default. This SAP default value may be overridden by a non-zero value in the llcCcAdminMaxIPDUOctetsSend object. At connection setup, the remote LLC may send, using an XID frame, the maximum I PDU size which it is prepared to receive. If so, an implementation may choose to override the administered maximum PDU size with the dynamically learned value and should reflect this in the llcCcOperMaxIPDUOctetsSend object for the connection component. The I PDU size includes all octets in a frame, excluding framing characters, the MAC header and link header.

INTEGER (0..127) · Integer32

This object denotes the default maximum consecutive unacknowledged I PDU frames that LLCs on this SAP may send to their remote LLC partners. This count is referred to as 'k' in the IEEE 802.2 specification [5]. A zero value for this object indicates that the port default, llcPortAdminMaxUnackedIPDUsSend, shall be used as the SAP default. This SAP default value may be overridden by a non-zero value in the llcCcAdminMaxUnackedIPDUsSend object. At connection setup, the remote LLC may send, using an XID frame, the maximum number of unacknowledged I PDUs which it is prepared to receive. If so, an implementation may choose to override the administered maximum number of unacknowledged PDUs with the dynamically learned value and should reflect this in the llcCcOperMaxUnackedIPDUsSend object for the connection component.

INTEGER (0..127) · Integer32

This object denotes the default maximum number of unacknowledged I PDUs that LLCs on this SAP can expect to receive from their remote LLC partners. This count is referred to as 'k' in the IEEE 802.2 specification [5]. A zero value for this object indicates that the port default, llcPortAdminMaxUnackedIPDUsRcv, shall be used as the SAP default. This SAP default value may be overridden by a non-zero value in the llcCcAdminMaxUnackedIPDUsRcv object. At connection setup, an implementation may choose to send this value to the remote LLC, using an XID frame.

Integer32

This object denotes the default value for the maximum number of times that LLCs on this SAP shall retry PDUs following the expiration of the acknowledgement timer, the P-bit timer or the reject timer. When these retries are exhausted, the link shall be declared inactive. This count is referred to as 'N2' in the IEEE 802.2 specification [5]. A zero value for this object indicates that the port default, llcPortAdminMaxRetransmits, shall be used as the SAP default. This SAP default value may be overridden by a non-zero value in the llcCcAdminMaxRetransmits.

TimeTicks

This object denotes the default value for the time interval during which the LLCs on this SAP shall expect to receive either: 1) an acknowledgement to one or more outstanding I PDUs. or 2) a response PDU to an unnumbered command PDU. The expiration of this timer shall cause the frame unacknowledged frames to be retransmitted (up to N2 times). A zero value for this object indicates that the port default, llcPortAdminAckTimer, shall be used as the SAP default. This SAP default value may be overridden by a non-zero value in the llcCcAdminAckTimer.

TimeTicks

This object denotes the default value for the time interval during which the LLCs on this port shall expect to receive a PDU with the F bit set to '1' in response to a Type 2 command with the P bit set to '1'. The expiration of this timer shall cause the REJ PDU to be retransmitted (up to N2 times). A zero value for this object indicates that the port default, llcPortAdminPbitTimer, shall be used as the SAP default. This SAP default value may be overridden by a non-zero value in the llcCcAdminPbitTimer.

TimeTicks

This object denotes the default value for the time interval during which the LLCs on this SAP shall expect to receive a reply to a REJ PDU. The expiration of this timer shall cause the REJ PDU to be retransmitted (up to N2 times). A zero value for this object indicates that the port default, llcPortAdminRejTimer, shall be used as the SAP default. This SAP default value may be overridden by a non-zero value in the llcCcAdminRejTimer.

TimeTicks

This object denotes the default value for the time interval during which the LLCs on this SAP shall expect to receive an indication that a busy condition at the remote LLC has cleared. The expiration of this timer shall cause the link to be declared inactive. A zero value for this object indicates that the port default, llcPortAdminBusyTimer, shall be used as the SAP default. This SAP default value may be overridden by a non-zero value in the llcCcAdminBusyTimer.

TimeTicks

This object denotes the default value for the time interval during which the LLCs on this SAP shall expect to receive any PDU from the remote LLC. This function is not described in the IEEE 802.2 specification [5] but is widely implemented. The expiration of this timer shall cause the local LLC to send a PDU to the remote LLC with the P bit set to '1'. A zero value for this object indicates that the port default, llcPortAdminInactTimer, shall be used as the SAP default. This SAP default value may be overridden by a non-zero value in the llcCcAdminInactTimer. Any value for this object less than or equal to the acknowledgement timer shall mean that the timer is not used.

Integer32

This object denotes the default value for the maximum number of consecutive I PDUs which the LLCs on this SAP shall receive during the interval defined by llcCcOperDelayTimer without sending an immediate acknowledgement. This must be less than or equal to the value of llcCcOperMaxUnackIPDURcv. This function is not described in the IEEE 802.2 specification [5] but is widely implemented. A zero value for this object indicates that the port default, llcPortAdminDelayAck, shall be used as the SAP default. This SAP default value may be overridden by a non-zero value in the llcCcAdminDelayAckCount. A value of one indicates that acknowledgments will be sent immediately and that the value of llcSapAdminDelayAckTimer shall be ignored.

TimeTicks

Reference: IBM Token-Ring Network Architecture Ref. SC30-3374 Chapter 11: Operation of Link Stations Receiver Acknowledgment Timer (T2)

This object denotes the default value for the time interval during which the LLCs on this SAP shall delay acknowledgment of one or more I PDUs (up to the value of llcCcOperDelayAckCount). This function is not described in the IEEE 802.2 specification [5]. It is listed in the IBM Token-Ring Network Architecture Reference [6] as the T2 parameter and is widely implemented. The expiration of this timer shall cause the local LLC to acknowledge all unacknowledged I PDUs. This object is associated with the llcSapAdminDelayAckCount object and is only defined if that object has a value greater than one.

Integer32

Reference: IBM Token-Ring Network Architecture Ref. SC30-3374 Chapter 11: Operation of Link Stations Number of Acknowledgments Needed to Increment Ww (Nw)

This object denotes the default value for the number of IPDUs that must be acknowledged before the working window size (Ww) can be incremented by 1 when the working window is not equal to the maximum transmit window size (TW). It controls the gradual incrementing of Ww in congestion situations. This function is not described in the IEEE 802.2 specification [5]. However, it is listed in the IBM Token-Ring Network Architecture Reference [6] as the Nw parameter and is widely implemented. This SAP default value may be overridden by a non-zero Cc default value in the llcCcAdminNw object.

INTEGER1 = inactive2 = active · Integer32

This parameter describes the actual state of this local SAP.

Integer32

This object defines the number of connection components on this SAP that are currently in one of the 'connected' states. In other words, this object is a count of the number of instances of llcCcOperEntry that have a llcCcOperState value greater than or equal to 'normal(3)'.

Gauge32

This object reflects the highest number of connection components on this SAP simultaneously in one of the 'connected' states. In other words, this object is a count of the number of instances of llcCcOperEntry that have a llcCcOperState value greater than or equal to 'normal(3)' concurrently on this SAP.

INTEGER1 = no2 = yes · Integer32

This parameter describes whether or not the LLC implementation supports LLC2 connection components.

Counter32

This object reflects the total number of times that the local connection components on this SAP have entered a busy state (RNR). This object is initialized to zero when the SAP is created.

Counter32

This object reflects the total number of times that the adjacent (i.e. remote) connection components on this SAP have entered a busy state (RNR). This object is initialized to zero when the SAP is created.

Counter32

This object reflects the total number of I-Frames that have been received by connection components on this SAP. This object is initialized to zero when the SAP is created.

Counter32

This object reflects the total number of I-Frames that have been transmitted by connection components on this SAP. This object is initialized to zero when the SAP is created.

Counter32

This object reflects the total octets received from adjacent connection components on this SAP. This object covers the address, control, and information field of I-Frames only. This object is initialized to zero when the SAP is created.

Counter32

This object reflects the total octets transmitted to adjacent connection components on this SAP. This object covers the address, control, and information field of I-Frames only. This object is initialized to zero when the SAP is created.

Counter32

This object reflects the total number of S-Frames that have been received by connection components on this SAP. This object is initialized to zero when the SAP is created. Note - the ratio of the number of I-Frames to S-Frames might serve as a measure of link efficiency and, for instance, could be used to tune the acknowledgement timer.

Counter32

This object reflects the total number of S-Frames that have been transmitted by connection components on this SAP. This object is initialized to zero when the SAP is created. Note - the ratio of the number of I-Frames to S-Frames might serve as a measure of link efficiency and, for instance, could be used to tune the acknowledgement timer.

Counter32

This object reflects the total number of I-Frames retransmitted by all local connection components on this SAP. This object is initialized to zero when the SAP is created.

Counter32

This object reflects the total REJ frames received from all adjacent LLC connection components on this SAP since it was created.

Counter32

This object reflects the total REJ frames transmitted to an adjacent LLC connection components on this SAP since it was created.

Counter32

This object reflects the total number of times, since this SAP was created, that the dynamic window algorithm has been invoked to reduce the value of Ww on any of the connection components of this SAP. This object is initialized to zero when the SAP is created. This function is not described in the IEEE 802.2 specification [5], but is widely implemented.

Counter32

This object denotes the number of TEST commands this SAP has received and is a measure of the number of stations in the network trying to connect up. This object is initialized to zero when the SAP is created.

Counter32

This object denotes the number of TEST commands this SAP has sent and is a measure of the number of other stations we are trying to connect to. This object is initialized to zero when the SAP is created.

Counter32

This object denotes the number of TEST responses this SAP has received and is a measure of the number of stations in the network responding to TEST commands this SAP has sent. This object is initialized to zero when the SAP is created.

Counter32

This object denotes the number of TEST responses this SAP has sent and is a measure of the number of other stations trying to connect to this SAP. This object is initialized to zero when the SAP is created.

Counter32

This object denotes the number of XID commands this SAP has received and is a measure of the number of stations in the network trying to connect to this SAP. This object is a count of all XIDs, including SNA XID, IEEE XID, null XID, and non-activation XIDs. This object is initialized to zero when the SAP is created.

Counter32

This object denotes the number of XID commands this SAP has sent and is a measure of the number of other stations this SAP is trying to connect to. This object is a count of all XIDs, including SNA XID, IEEE XID, null XID, and non-activation XIDs. This object is initialized to zero when the SAP is created.

Counter32

This object denotes the number of XID responses this SAP has received and is a measure of the number of stations in the network responding to TEST commands this SAP has sent. This object is a count of all XIDs, including SNA XID, IEEE XID, null XID, and non-activation XIDs. This object is initialized to zero when the SAP is created.

Counter32

This object denotes the number of XID responses this SAP has sent and is a measure of the number of other stations trying to connect to this SAP. This object is a count of all XIDs, including SNA XID, IEEE XID, null XID, and non-activation XIDs. This object is initialized to zero when the SAP is created.

Counter32

This object reflects the total number of unnumbered information (UI) frames received on a local SAP.

Counter32

This object reflects the total number of unnumbered information (UI) frames sent on a local SAP.

Counter32

This object reflects the total octets received from adjacent connection components on this SAP. This object covers the address, control, and information field of UI-Frames only. This object is initialized to zero when the SAP is created.

Counter32

This object reflects the total octets transmitted to adjacent connection components on this SAP. This object covers the address, control, and information field of UI-Frames only. This object is initialized to zero when the SAP is created.

Counter32

This object reflects the total number of successful connections that have been established on this SAP since the SAP was created. A successful connection is indicated by a successful SABME/UA exchange.

Counter32

This object reflects the total number of unsuccessful connections that have been attempted on this SAP since the SAP was created. An unsuccessful connection attempt is indicated by a SABME/DM exchange or a SABME/timeout.

Counter32

This object reflects the total number of normal disconnections that have been performed on this SAP since the SAP was created. A normal disconnection is indicated by a successful DISC/UA exchange or merely a DISC sent or received.

Counter32

This object reflects the total number of abnormal disconnections (resulting from a FRMR being sent) that have been performed on this SAP since the SAP was created.

Counter32

This object reflects the total number of abnormal disconnections (resulting from a FRMR being received) that have been performed on this SAP since the SAP was created.

Counter32

This object reflects the total number of abnormal disconnections (resulting from a timer expiration) that have been performed on this SAP since the SAP was created.

Counter32

This object reflects the total number of Disconnect Mode responses that have been received for CCs in ABM mode on this SAP since the SAP was created.

Counter32

This object reflects the total number of SABMEs that have been received for CCs in already in ABM mode on this SAP since the SAP was created.

MacAddressRepresents an 802 MAC address represented in the `canonical' order defined by IEEE 802.1a, i.e., as if it were transmitted least significant bit first, even though 802.5 (in contrast to other 802.x protocols) requires MAC addresses to be transmitted most significant bit first. SIZE (6) · OCTET STRING · hint 1x:

This value is the remote MAC address for this Connection Component. This value is provided by the SNMP agent.

INTEGER (1..255) · Integer32

This value is the address of the remote SAP for this Connection Component. This value is provided by the SNMP agent.

INTEGER1 = no2 = yes · Integer32

This object controls the resetting of the connection component. Setting this value to yes(2) results in the connection component being reset, llcCcOperState transitioning to a value of aDm(1), and the value of llcCcAdminBounce being set back to no(1).

Integer32 · octets

This object denotes the maximum I PDU size, in octets, that this LLC SAP may send to its remote connection component partner. This count is referred to as 'N1' in the IEEE 802.2 specification [5]. This object contains an administrative value which will be applied the next time this connection is established. A zero value for this object indicates that the SAP default, llcSapAdminMaxIPDUOctetsSend, shall be used. At connection setup, the remote LLC may send, using an XID frame, the maximum I PDU size which it is prepared to receive. If so, an implementation may choose to override the administered maximum PDU size with the dynamically learned value and should reflect this in the llcCcOperMaxIPDUOctetsSend object for the connection component. The I PDU size includes all octets in a frame, excluding framing characters, the MAC header and link header.

INTEGER (0..127) · Integer32

This object denotes the maximum consecutive unacknowledged I PDU frames that this LLC may send to its remote LLC partner. This count is referred to as 'k' in the IEEE 802.2 specification [5]. This object contains an administrative value which will be applied the next time this connection is established. A zero value for this object indicates that the SAP default, llcSapAdminMaxUnackedIPDUsSend, shall be used. At connection setup, the remote LLC may send, using an XID frame, the maximum number of unacknowledged I PDUs which it is prepared to receive. If so, an implementation may choose to override the administered maximum number of unacknowledged PDUs with the dynamically learned value and should reflect this in the llcCcOperMaxUnackedIPDUsSend object for the connection component.

INTEGER (0..127) · Integer32

This object denotes the maximum number of unacknowledged I PDUs that this LLC can expect to receive from its remote LLC partner. This count is referred to as 'k' in the IEEE 802.2 specification [5]. This object contains an administrative value which will be applied the next time this connection is established. A zero value for this object indicates that the SAP default, llcSapAdminMaxUnackedIPDUsRcv, shall be used. At connection setup, an implementation may choose to send this value to the remote LLC, using an XID frame.

Integer32

This object denotes the value for the maximum number of times that this LLC shall retry PDUs following the expiration of the acknowledgement timer, the P-bit timer or the reject timer. When these retries are exhausted, the link shall be declared inactive. This count is referred to as 'N2' in the IEEE 802.2 specification [5]. This object contains an administrative value which will be applied the next time this connection is established. A zero value for this object indicates that the SAP default, llcSapAdminMaxRetransmits, shall be used.

TimeTicks

This object denotes the value for the time interval during which this LLC shall expect to receive either: 1) an acknowledgement to one or more outstanding I PDUs. or 2) a response PDU to an unnumbered command PDU. The expiration of this timer shall cause the frame unacknowledged frames to be retransmitted (up to N2 times). This object contains an administrative value which will be applied the next time this connection is established. A zero value for this object indicates that the SAP default, llcSapAdminAckTimer, shall be used.

TimeTicks

This object denotes the value for the time interval during which this LLC shall expect to receive a PDU with the F bit set to '1' in response to a Type 2 command with the P bit set to '1'. The expiration of this timer shall cause the REJ PDU to be retransmitted (up to N2 times). This object contains an administrative value which will be applied the next time this connection is established. A zero value for this object indicates that the SAP default, llcSapAdminPbitTimer, shall be used.

TimeTicks

This object denotes the value for the time interval during which this LLC shall expect to receive a reply to a REJ PDU. The expiration of this timer shall cause the REJ PDU to be retransmitted (up to N2 times). This object contains an administrative value which will be applied the next time this connection is established. A zero value for this object indicates that the SAP default, llcSapAdminRejTimer, shall be used.

TimeTicks

This object denotes the value for the time interval during which this LLC shall expect to receive an indication that a busy condition at the remote LLC has cleared. The expiration of this timer shall cause the link to be declared inactive. This object contains an administrative value which will be applied the next time this connection is established. A zero value for this object indicates that the SAP default, llcSapAdminBusyTimer, shall be used.

TimeTicks

This object denotes the value for the time interval during which this LLC shall expect to receive any PDU from the remote LLC. This function is not described in the IEEE 802.2 specification [5] but is widely implemented. The expiration of this timer shall cause the local LLC to send a PDU to the remote LLC with the P bit set to '1'. This object contains an administrative value which will be applied the next time this connection is established. A zero value for this object indicates that the SAP default, llcSapAdminInactTimer, shall be used. Any value for this object less than or equal to the acknowledgement timer shall mean that the timer is not used.

Integer32

This object denotes the value for the maximum number of consecutive I PDUs which this LLC shall receive during the interval defined by llcCcOperDelayTimer without sending an immediate acknowledgement. This must be less than or equal to the value of llcCcOperMaxUnackIPDURcv. This function is not described in the IEEE 802.2 specification [5] but is widely implemented. This object contains an administrative value which will be applied the next time this connection is established. A zero value for this object indicates that the SAP default, llcSapAdminDelayAck, shall be used. A value of one indicates that acknowledgments will be sent immediately and that the value of llcCcAdminDelayAckTimer shall be ignored.

TimeTicks

Reference: IBM Token-Ring Network Architecture Ref. SC30-3374 Chapter 11: Operation of Link Stations Receiver Acknowledgment Timer (T2)

This object denotes the value for the time interval during which this LLC shall delay acknowledgment of one or more I PDUs (up to the value of llcCcOperDelayAckCount). This function is not described in the IEEE 802.2 specification [5]. It is listed in the IBM Token-Ring Network Architecture Reference [6] as the T2 parameter and is widely implemented. The expiration of this timer shall cause the local LLC to acknowledge all unacknowledged I PDUs. This object contains an administrative value which will be applied the next time this connection is established. This object is associated with the llcCcAdminDelayAckCount object and is only defined if that object has a value greater than one.

Integer32

Reference: IBM Token-Ring Network Architecture Ref. SC30-3374 Chapter 11: Operation of Link Stations Number of Acknowledgments Needed to Increment Ww (Nw)

This object denotes the value for the number of IPDUs that must be acknowledged before the working window size (Ww) can be incremented by 1 when the working window is not equal to the maximum transmit window size (TW). It controls the gradual incrementing of Ww in congestion situations. This function is not described in the IEEE 802.2 specification [5]. However, it is listed in the IBM Token-Ring Network Architecture Reference [6] as the Nw parameter and is widely implemented.

RowStatus1 = active2 = notInService3 = notReady4 = createAndGo5 = createAndWait6 = destroyThe RowStatus textual convention is used to manage the creation and deletion of conceptual rows, and is used as the value of the SYNTAX clause for the status column of a conceptual row (as described in Section 7.7.1 of [2].) The status column has six defined values: - `active', which indicates that the conceptual row is available for use by the managed device; - `notInService', which indicates that the conceptual row exists in the agent, but is unavailable for use by the managed device (see NOTE below); 'notInService' has no implication regarding the internal consistency of the row, availability of resources, or consistency with the current state of the managed device; - `notReady', which indicates that the conceptual row exists in the agent, but is missing information necessary in order to be available for use by the managed device (i.e., one or more required columns in the conceptual row have not been instanciated); - `createAndGo', which is supplied by a management station wishing to create a new instance of a conceptual row and to have its status automatically set to active, making it available for use by the managed device; - `createAndWait', which is supplied by a management station wishing to create a new instance of a conceptual row (but not make it available for use by the managed device); and, - `destroy', which is supplied by a management station wishing to delete all of the instances associated with an existing conceptual row. Whereas five of the six values (all except `notReady') may be specified in a management protocol set operation, only three values will be returned in response to a management protocol retrieval operation: `notReady', `notInService' or `active'. That is, when queried, an existing conceptual row has only three states: it is either available for use by the managed device (the status column has value `active'); it is not available for use by the managed device, though the agent has sufficient information to attempt to make it so (the status column has value `notInService'); or, it is not available for use by the managed device, and an attempt to make it so would fail because the agent has insufficient information (the state column has value `notReady'). NOTE WELL This textual convention may be used for a MIB table, irrespective of whether the values of that table's conceptual rows are able to be modified while it is active, or whether its conceptual rows must be taken out of service in order to be modified. That is, it is the responsibility of the DESCRIPTION clause of the status column to specify whether the status column must not be `active' in order for the value of some other column of the same conceptual row to be modified. If such a specification is made, affected columns may be changed by an SNMP set PDU if the RowStatus would not be equal to `active' either immediately before or after processing the PDU. In other words, if the PDU also contained a varbind that would change the RowStatus value, the column in question may be changed if the RowStatus was not equal to `active' as the PDU was received, or if the varbind sets the status to a value other than 'active'. Also note that whenever any elements of a row exist, the RowStatus column must also exist. To summarize the effect of having a conceptual row with a status column having a SYNTAX clause value of RowStatus, consider the following state diagram: STATE +--------------+-----------+-------------+------------- | A | B | C | D | |status col.|status column| |status column | is | is |status column ACTION |does not exist| notReady | notInService| is active --------------+--------------+-----------+-------------+------------- set status |noError ->D|inconsist- |inconsistent-|inconsistent- column to | or | entValue| Value| Value createAndGo |inconsistent- | | | | Value| | | --------------+--------------+-----------+-------------+------------- set status |noError see 1|inconsist- |inconsistent-|inconsistent- column to | or | entValue| Value| Value createAndWait |wrongValue | | | --------------+--------------+-----------+-------------+------------- set status |inconsistent- |inconsist- |noError |noError column to | Value| entValue| | active | | | | | | or | | | | | | | |see 2 ->D|see 8 ->D| ->D --------------+--------------+-----------+-------------+------------- set status |inconsistent- |inconsist- |noError |noError ->C column to | Value| entValue| | notInService | | | | | | or | | or | | | | | |see 3 ->C| ->C|see 6 --------------+--------------+-----------+-------------+------------- set status |noError |noError |noError |noError ->A column to | | | | or destroy | ->A| ->A| ->A|see 7 --------------+--------------+-----------+-------------+------------- set any other |see 4 |noError |noError |see 5 column to some| | | | value | | see 1| ->C| ->D --------------+--------------+-----------+-------------+------------- (1) goto B or C, depending on information available to the agent. (2) if other variable bindings included in the same PDU, provide values for all columns which are missing but required, and all columns have acceptable values, then return noError and goto D. (3) if other variable bindings included in the same PDU, provide legal values for all columns which are missing but required, then return noError and goto C. (4) at the discretion of the agent, the return value may be either: inconsistentName: because the agent does not choose to create such an instance when the corresponding RowStatus instance does not exist, or inconsistentValue: if the supplied value is inconsistent with the state of some other MIB object's value, or noError: because the agent chooses to create the instance. If noError is returned, then the instance of the status column must also be created, and the new state is B or C, depending on the information available to the agent. If inconsistentName or inconsistentValue is returned, the row remains in state A. (5) depending on the MIB definition for the column/table, either noError or inconsistentValue may be returned. (6) the return value can indicate one of the following errors: wrongValue: because the agent does not support notInService (e.g., an agent which does not support createAndWait), or inconsistentValue: because the agent is unable to take the row out of service at this time, perhaps because it is in use and cannot be de-activated. (7) the return value can indicate the following error: inconsistentValue: because the agent is unable to remove the row at this time, perhaps because it is in use and cannot be de-activated. (8) the transition to D can fail, e.g., if the values of the conceptual row are inconsistent, then the error code would be inconsistentValue. NOTE: Other processing of (this and other varbinds of) the set request may result in a response other than noError being returned, e.g., wrongValue, noCreation, etc. Conceptual Row Creation There are four potential interactions when creating a conceptual row: selecting an instance-identifier which is not in use; creating the conceptual row; initializing any objects for which the agent does not supply a default; and, making the conceptual row available for use by the managed device. Interaction 1: Selecting an Instance-Identifier The algorithm used to select an instance-identifier varies for each conceptual row. In some cases, the instance- identifier is semantically significant, e.g., the destination address of a route, and a management station selects the instance-identifier according to the semantics. In other cases, the instance-identifier is used solely to distinguish conceptual rows, and a management station without specific knowledge of the conceptual row might examine the instances present in order to determine an unused instance-identifier. (This approach may be used, but it is often highly sub-optimal; however, it is also a questionable practice for a naive management station to attempt conceptual row creation.) Alternately, the MIB module which defines the conceptual row might provide one or more objects which provide assistance in determining an unused instance-identifier. For example, if the conceptual row is indexed by an integer-value, then an object having an integer-valued SYNTAX clause might be defined for such a purpose, allowing a management station to issue a management protocol retrieval operation. In order to avoid unnecessary collisions between competing management stations, `adjacent' retrievals of this object should be different. Finally, the management station could select a pseudo-random number to use as the index. In the event that this index was already in use and an inconsistentValue was returned in response to the management protocol set operation, the management station should simply select a new pseudo-random number and retry the operation. A MIB designer should choose between the two latter algorithms based on the size of the table (and therefore the efficiency of each algorithm). For tables in which a large number of entries are expected, it is recommended that a MIB object be defined that returns an acceptable index for creation. For tables with small numbers of entries, it is recommended that the latter pseudo-random index mechanism be used. Interaction 2: Creating the Conceptual Row Once an unused instance-identifier has been selected, the management station determines if it wishes to create and activate the conceptual row in one transaction or in a negotiated set of interactions. Interaction 2a: Creating and Activating the Conceptual Row The management station must first determine the column requirements, i.e., it must determine those columns for which it must or must not provide values. Depending on the complexity of the table and the management station's knowledge of the agent's capabilities, this determination can be made locally by the management station. Alternately, the management station issues a management protocol get operation to examine all columns in the conceptual row that it wishes to create. In response, for each column, there are three possible outcomes: - a value is returned, indicating that some other management station has already created this conceptual row. We return to interaction 1. - the exception `noSuchInstance' is returned, indicating that the agent implements the object-type associated with this column, and that this column in at least one conceptual row would be accessible in the MIB view used by the retrieval were it to exist. For those columns to which the agent provides read-create access, the `noSuchInstance' exception tells the management station that it should supply a value for this column when the conceptual row is to be created. - the exception `noSuchObject' is returned, indicating that the agent does not implement the object-type associated with this column or that there is no conceptual row for which this column would be accessible in the MIB view used by the retrieval. As such, the management station can not issue any management protocol set operations to create an instance of this column. Once the column requirements have been determined, a management protocol set operation is accordingly issued. This operation also sets the new instance of the status column to `createAndGo'. When the agent processes the set operation, it verifies that it has sufficient information to make the conceptual row available for use by the managed device. The information available to the agent is provided by two sources: the management protocol set operation which creates the conceptual row, and, implementation-specific defaults supplied by the agent (note that an agent must provide implementation-specific defaults for at least those objects which it implements as read-only). If there is sufficient information available, then the conceptual row is created, a `noError' response is returned, the status column is set to `active', and no further interactions are necessary (i.e., interactions 3 and 4 are skipped). If there is insufficient information, then the conceptual row is not created, and the set operation fails with an error of `inconsistentValue'. On this error, the management station can issue a management protocol retrieval operation to determine if this was because it failed to specify a value for a required column, or, because the selected instance of the status column already existed. In the latter case, we return to interaction 1. In the former case, the management station can re-issue the set operation with the additional information, or begin interaction 2 again using `createAndWait' in order to negotiate creation of the conceptual row. NOTE WELL Regardless of the method used to determine the column requirements, it is possible that the management station might deem a column necessary when, in fact, the agent will not allow that particular columnar instance to be created or written. In this case, the management protocol set operation will fail with an error such as `noCreation' or `notWritable'. In this case, the management station decides whether it needs to be able to set a value for that particular columnar instance. If not, the management station re-issues the management protocol set operation, but without setting a value for that particular columnar instance; otherwise, the management station aborts the row creation algorithm. Interaction 2b: Negotiating the Creation of the Conceptual Row The management station issues a management protocol set operation which sets the desired instance of the status column to `createAndWait'. If the agent is unwilling to process a request of this sort, the set operation fails with an error of `wrongValue'. (As a consequence, such an agent must be prepared to accept a single management protocol set operation, i.e., interaction 2a above, containing all of the columns indicated by its column requirements.) Otherwise, the conceptual row is created, a `noError' response is returned, and the status column is immediately set to either `notInService' or `notReady', depending on whether it has sufficient information to (attempt to) make the conceptual row available for use by the managed device. If there is sufficient information available, then the status column is set to `notInService'; otherwise, if there is insufficient information, then the status column is set to `notReady'. Regardless, we proceed to interaction 3. Interaction 3: Initializing non-defaulted Objects The management station must now determine the column requirements. It issues a management protocol get operation to examine all columns in the created conceptual row. In the response, for each column, there are three possible outcomes: - a value is returned, indicating that the agent implements the object-type associated with this column and had sufficient information to provide a value. For those columns to which the agent provides read-create access (and for which the agent allows their values to be changed after their creation), a value return tells the management station that it may issue additional management protocol set operations, if it desires, in order to change the value associated with this column. - the exception `noSuchInstance' is returned, indicating that the agent implements the object-type associated with this column, and that this column in at least one conceptual row would be accessible in the MIB view used by the retrieval were it to exist. However, the agent does not have sufficient information to provide a value, and until a value is provided, the conceptual row may not be made available for use by the managed device. For those columns to which the agent provides read-create access, the `noSuchInstance' exception tells the management station that it must issue additional management protocol set operations, in order to provide a value associated with this column. - the exception `noSuchObject' is returned, indicating that the agent does not implement the object-type associated with this column or that there is no conceptual row for which this column would be accessible in the MIB view used by the retrieval. As such, the management station can not issue any management protocol set operations to create an instance of this column. If the value associated with the status column is `notReady', then the management station must first deal with all `noSuchInstance' columns, if any. Having done so, the value of the status column becomes `notInService', and we proceed to interaction 4. Interaction 4: Making the Conceptual Row Available Once the management station is satisfied with the values associated with the columns of the conceptual row, it issues a management protocol set operation to set the status column to `active'. If the agent has sufficient information to make the conceptual row available for use by the managed device, the management protocol set operation succeeds (a `noError' response is returned). Otherwise, the management protocol set operation fails with an error of `inconsistentValue'. NOTE WELL A conceptual row having a status column with value `notInService' or `notReady' is unavailable to the managed device. As such, it is possible for the managed device to create its own instances during the time between the management protocol set operation which sets the status column to `createAndWait' and the management protocol set operation which sets the status column to `active'. In this case, when the management protocol set operation is issued to set the status column to `active', the values held in the agent supersede those used by the managed device. If the management station is prevented from setting the status column to `active' (e.g., due to management station or network failure) the conceptual row will be left in the `notInService' or `notReady' state, consuming resources indefinitely. The agent must detect conceptual rows that have been in either state for an abnormally long period of time and remove them. It is the responsibility of the DESCRIPTION clause of the status column to indicate what an abnormally long period of time would be. This period of time should be long enough to allow for human response time (including `think time') between the creation of the conceptual row and the setting of the status to `active'. In the absence of such information in the DESCRIPTION clause, it is suggested that this period be approximately 5 minutes in length. This removal action applies not only to newly-created rows, but also to previously active rows which are set to, and left in, the notInService state for a prolonged period exceeding that which is considered normal for such a conceptual row. Conceptual Row Suspension When a conceptual row is `active', the management station may issue a management protocol set operation which sets the instance of the status column to `notInService'. If the agent is unwilling to do so, the set operation fails with an error of `wrongValue' or `inconsistentValue'. Otherwise, the conceptual row is taken out of service, and a `noError' response is returned. It is the responsibility of the DESCRIPTION clause of the status column to indicate under what circumstances the status column should be taken out of service (e.g., in order for the value of some other column of the same conceptual row to be modified). Conceptual Row Deletion For deletion of conceptual rows, a management protocol set operation is issued which sets the instance of the status column to `destroy'. This request may be made regardless of the current value of the status column (e.g., it is possible to delete conceptual rows which are either `notReady', `notInService' or `active'.) If the operation succeeds, then all instances associated with the conceptual row are immediately removed. · Integer32

This object is used by a management station to create or delete the row entry in llcCcAdminTable following the RowStatus textual convention. Upon successful creation of the row, an agent automatically creates a corresponding entry in the llcCcOperTable with llcCcOperState equal to 'aDM (1)'.

INTEGER1 = aDM2 = setup3 = normal4 = busy5 = reject6 = await7 = awaitBusy8 = awaitReject9 = dConn10 = reset11 = error12 = conn13 = resetCheck14 = resetWait · Integer32

Reference: ISO 8802-2 : 1989, ANSI/IEEE 802.2 - 1989 Section 7.9.2.1. Connection Component State Descriptions

This object describes the operational state of the LLC connection. If the connection component is disabled, llcCcOperState will transition to aDM(1). If the connection component is enabled, llcCcOperState will transition to normal(3).

Integer32

This object denotes the maximum I PDU size, in octets, that this LLC SAP may send to its remote connection component partner. This count is referred to as 'N1' in the IEEE 802.2 specification [5]. At connection setup, the remote LLC may send, using an XID frame, the maximum I PDU size which it is prepared to receive. If so, an implementation may choose to override the administered maximum PDU size with the dynamically learned value and should reflect that in this object. The I PDU size includes all octets in a frame, excluding framing characters, the MAC header and link header.

Integer32

This object denotes the maximum I PDU size, in octets, that this LLC can expect to receive from its remote LLC partner. This count is referred to as 'N1' in the IEEE 802.2 specification [5] The I PDU size includes all octets in a frame with the exception of the framing characters, the MAC header and the link header.

INTEGER (1..127) · Integer32

This object denotes the maximum consecutive unacknowledged I PDU frames that this LLC may send to its remote LLC partner. This count is referred to as 'k' in the IEEE 802.2 specification [5]. At connection setup, the remote LLC may send, using an XID frame, the maximum number of unacknowledged I PDUs which it is prepared to receive. If so, an implementation may choose to override the administered maximum number of unacknowledged PDUs with the dynamically learned value and should reflect that in this object.

INTEGER (1..127) · Integer32

This object denotes the maximum number of unacknowledged I PDUs that this LLC can expect to receive from its remote LLC partner. This count is referred to as 'k' in the IEEE 802.2 specification [5].

Integer32

This object denotes the value for the maximum number of times that this LLC shall retry PDUs following the expiration of the acknowledgement timer, the P-bit timer or the reject timer. When these retries are exhausted, the link shall be declared inactive. This count is referred to as 'N2' in the IEEE 802.2 specification [5].

TimeTicks

This object denotes the value for the time interval during which this LLC shall expect to receive either: 1) an acknowledgement to one or more outstanding I PDUs. or 2) a response PDU to an unnumbered command PDU. The expiration of this timer shall cause the frame unacknowledged frames to be retransmitted (up to N2 times).

TimeTicks

This object denotes the value for the time interval during which this LLC shall expect to receive a PDU with the F bit set to '1' in response to a Type 2 command with the P bit set to '1'. The expiration of this timer shall cause the REJ PDU to be retransmitted (up to N2 times).

TimeTicks

This object denotes the value for the time interval during which this LLC shall expect to receive a reply to a REJ PDU. The expiration of this timer shall cause the REJ PDU to be retransmitted (up to N2 times).

TimeTicks

This object denotes the value for the time interval during which this LLC shall expect to receive an indication that a busy condition at the remote LLC has cleared. The expiration of this timer shall cause the link to be declared inactive.

TimeTicks

This object denotes the value for the time interval during which this LLC shall expect to receive any PDU from the remote LLC. This function is not described in the IEEE 802.2 specification [5] but is widely implemented. The expiration of this timer shall cause the local LLC to send a PDU to the remote LLC with the P bit set to '1'. Any value for this object less than or equal to the acknowledgement timer shall mean that the timer is not used.

Integer32

This object denotes the value for the maximum number of consecutive I PDUs which this LLC shall receive during the interval defined by llcCcOperDelayTimer without sending an immediate acknowledgement. This must be less than or equal to the value of llcCcOperMaxUnackIPDURcv. This function is not described in the IEEE 802.2 specification [5] but is widely implemented. A value of one indicates that acknowledgments will be sent immediately and that the value of llcCcOperDelayAckTimer should be ignored.

TimeTicks

This object denotes the value for the time interval during which this LLC shall delay acknowledgment of one or more I PDUs (up to the value of llcCcOperDelayAckCount). This function is not described in the IEEE 802.2 specification [5] but is widely implemented. The expiration of this timer shall cause the local LLC to acknowledge all unacknowledged I PDUs. This object is associated with the llcCcOperDelayAckCount object and only has meaning if that object has a value greater than one.

Integer32

Reference: IBM Token-Ring Network Architecture Ref. SC30-3374 Chapter 11: Operation of Link Stations Number of Acknowledgments Needed to Increment Ww (Nw)

This object denotes the value for the number of IPDUs that must be acknowledged before the working window size (Ww) can be incremented by 1 when the working window is not equal to the maximum transmit window size (TW). It controls the gradual incrementing of Ww in congestion situations. This function is not described in the IEEE 802.2 specification [5], but is widely implemented.

INTEGER (1..127) · Integer32

Reference: IBM Token-Ring Network Architecture Ref. SC30-3374 Chapter 8: LLC Frames Working Window Size, Ww

Maximum number of sequentially numbered IPDUs that the connection component may have outstanding (unacknowledged) at any given time. Ww is initialized to the value of llcCcOperMaxUnackedIPDUsSend when the link is established. When the dynamic window algorithm is invoked, Ww varies from 1 up to llcCcOperMaxUnackedIPDUsSend. Each time the llcCcOperWw value is decreased, the reason is recorded in llcCcOperLastWwCause, and llcCcStatWwCount is incremented by 1. This function is not described in the IEEE 802.2 specification [5], but is widely implemented.

TimeStampThe value of the sysUpTime object at which a specific occurrence happened. The specific occurrence must be defined in the description of any object defined using this type. If sysUpTime is reset to zero as a result of a re- initialization of the network management (sub)system, then the values of all TimeStamp objects are also reset. However, after approximately 497 days without a re- initialization, the sysUpTime object will reach 2^^32-1 and then increment around to zero; in this case, existing values of TimeStamp objects do not change. This can lead to ambiguities in the value of TimeStamp objects. · TimeTicks

This object describes the value of sysUpTime when this connection was created.

TimeStampThe value of the sysUpTime object at which a specific occurrence happened. The specific occurrence must be defined in the description of any object defined using this type. If sysUpTime is reset to zero as a result of a re- initialization of the network management (sub)system, then the values of all TimeStamp objects are also reset. However, after approximately 497 days without a re- initialization, the sysUpTime object will reach 2^^32-1 and then increment around to zero; in this case, existing values of TimeStamp objects do not change. This can lead to ambiguities in the value of TimeStamp objects. · TimeTicks

This object describes the value of sysUpTime the last time this connection component was modified. If the connection has not been modified, then this value shall be zero.

TimeStampThe value of the sysUpTime object at which a specific occurrence happened. The specific occurrence must be defined in the description of any object defined using this type. If sysUpTime is reset to zero as a result of a re- initialization of the network management (sub)system, then the values of all TimeStamp objects are also reset. However, after approximately 497 days without a re- initialization, the sysUpTime object will reach 2^^32-1 and then increment around to zero; in this case, existing values of TimeStamp objects do not change. This can lead to ambiguities in the value of TimeStamp objects. · TimeTicks

This object describes the value of sysUpTime when this LLC connection component last failed. If the connection component has not failed, then this value shall be zero.

INTEGER1 = undefined2 = rxFRMR3 = txFRMR4 = discReceived5 = discSent6 = retriesExpired7 = forcedShutdown · Integer32

This enumerated object reflects the cause of the last failure of this LLC connection component. If the connection component has not failed, then this object will have a value of undefined(1).

OCTET STRING SIZE (3)

This object reflects the information field of the FRMR frame if the last failure for this LLC connection component was as a result of an invalid frame. Otherwise, this field has no meaning.

INTEGER1 = neverInvoked2 = lostData3 = macLayerCongestion4 = other · Integer32

Reference: IBM Token-Ring Network Architecture Ref. SC30-3374 Chapter 11: Operation of Link Stations The Dynamic Window Algorithm.

This object indicates the reason that the llcCcOperWw was reduced the last time this occurred.

Counter32

This object reflects the total number of times that the local connection component has entered a busy state (RNR). This object is initialized to zero when the connection component is created.

Counter32

This object reflects the total number of times that the adjacent (i.e. remote) connection component has entered a busy state (RNR). This object is initialized to zero when the connection component is created.

Counter32

This object reflects the total number of I-Frames that have been received by the connection component. This object is initialized to zero when the connection component is created.

Counter32

This object reflects the total number of I-Frames that have been transmitted by this connection component. This object is initialized to zero when the connection component is created.

Counter32

This object reflects the total octets received from the adjacent connection component. This object covers the address, control, and information field of I-Frames only. This object is initialized to zero when the connection component is created.

Counter32

This object reflects the total octets transmitted to the adjacent connection component. This object covers the address, control, and information field of I-Frames only. This object is initialized to zero when the connection component is created.

Counter32

This object reflects the total number of S-Frames that have been received by this connection component. This object is initialized to zero when the connection component is created. Note - the ratio of the number of I-Frames to S-Frames might serve as a measure of link efficiency and, for instance, could be used to tune the acknowledgement timer.

Counter32

This object reflects the total number of S-Frames that have been transmitted by this connection component. This object is initialized to zero when the connection component is created. Note - the ratio of the number of I-Frames to S-Frames might serve as a measure of link efficiency and, for instance, could be used to tune the acknowledgement timer.

Counter32

This object reflects the total number of I-Frames retransmitted the local connection component. This object is initialized to zero when the connection component is created.

Counter32

This object reflects the total REJ frames received from an adjacent LLC connection component since connection component startup.

Counter32

This object reflects the total REJ frames transmitted to an adjacent LLC connection component since connection component startup.

Counter32

This object reflects the total number of times, since connection component startup, that the dynamic window algorithm has been invoked to reduce the value of Ww. At connection component startupm this object must be initialized to zero. This function is not described in the IEEE 802.2 specification [5], but is widely implemented.