This indicates which subchannel is being referenced
for a particular daughter board on a CMCC card.
This value is constructed as follows:
path * 256 + device
Path and device are the values in
CipCardClawConfigTable.
Parsed from file CISCO-CHANNEL-MIB.mib
Module: CISCO-CHANNEL-MIB
This indicates which subchannel is being referenced
for a particular daughter board on a CMCC card.
This value is constructed as follows:
path * 256 + device
Path and device are the values in
CipCardClawConfigTable.
cipCardSubChannelIndex OBJECT-TYPE
SYNTAX Integer32 (0..2147483647)
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"This indicates which subchannel is being referenced
for a particular daughter board on a CMCC card.
This value is constructed as follows:
path * 256 + device
Path and device are the values in
CipCardClawConfigTable."
Also defined as:
ciscoCipCsnaMIB MODULE-IDENTITY
LAST-UPDATED "9508210000Z"
ORGANIZATION "cisco IBM engineering Working Group"
CONTACT-INFO
" Cisco Systems
Customer Service
Postal: 170 W Tasman Drive
San Jose, CA 95134
USA
Tel: +1 800 553-NETS
E-mail: [email protected]"
DESCRIPTION
"This is the Management Information Base (MIB)
module for objects used to manage the cisco Systems
Network Architecture (SNA) support on Cisco Mainframe
Channel Connection (CMCC) cards, also called the
CIP-SNA feature.
---------------------------------------------------
| Acronym Definitions: |
| CMCC = Cisco Mainframe Channel Connection |
| CIP = Channel Interface Processor |
| CTA = Channel Transport Architecture |
| SNA = Systems Network Architecture |
| CIP-SNA = CNA = CSNA = SNA Support on |
| a CMCC card |
---------------------------------------------------
This mib consists of the following tables:
1) CSNA Administration
2) CSNA Operational
3) CSNA Statistics
4) Max Sessions Administration
5) Max Sessions Operational
8) LLC2/CSNA Connection mapping
The following is a set of IBM channel terminology:
1) The Channel Subsystem is the way a host performs
I/O.
2) A Channel Path is the path to the Channel Control
Unit. In the Cisco CMCC environment, this is the
path of the channel to the physical router, itself.
This path is needed because the physical channel may
be directed (switched) through a device called
an ESCON director. The path defined from the
host to the Control Unit can be different than
the path from the Control Unit to the host.
For an in-depth definition of how this number
is derived, see the cipCardCsnaAdminPath object.
3) A Sub-Channel and Device are exactly the same
thing. The term Sub-Channel was introduced
for ESCON (IBMs serial fiber optic) channel
interface. Previously the term Device was used,
and it mapped directly to hardware (in most
situations) via a Parallel Channel Adapter
(PCA). Another name for PCA is Bus & Tag. In
the Cisco CMCC environment, the Sub-Channel is
controlled by the Channel Systems Network
Architecture (CSNA) feature. For an
in-depth definition of how this number is
derived, see the cipCardCsnaAdminDevice object.
NOTE: The terminology of Sub-Channel and
Sub-Channel Index are two completely different
entities! See below for Sub-Channel Index.
4) An I/O Device is the entity that is addressed by
the combination of Sub-Channel and Device. This
directly maps to the cipCardCsnaAdminTable.
NOTE: The Channel Systems Network Architecture
(CSNA) feature may have multiple
sub-channels/devices defined for its control.
Also NOTE: That we have defined an object with
the name cipCardSubChannelIndex and this object
is the two hex octet Channel Path values concatenated
with the second hex (the first octet is not used)
octet Device value and then converted to an
INTEGER (Unsigned).
The exact description is taken from the
CISCO-CHANNEL-MIB
cipCardSubChannelIndex OBJECT-TYPE
SYNTAX INTEGER
MAX-ACCESS read-only
STATUS current
DESCRIPTION
This indicates which subchannel is being referenced
for a particular daughter board on a CMCC card.
This value is constructed as follows:
path * 256 + device
Path and device are the values in
CipCardClawConfigTable.
View at oid-info.com
This indicates which subchannel is being referenced
for a particular daughter board on a CMCC card.
This value is constructed as follows:
path * 256 + device
Path and device are the values in
CipCardClawConfigTable.
Parsed from file CISCO-CHANNEL-MIB.my.txt
Company: None
Module: CISCO-CHANNEL-MIB
This indicates which subchannel is being referenced
for a particular daughter board on a CMCC card.
This value is constructed as follows:
path * 256 + device
Path and device are the values in
CipCardClawConfigTable.
cipCardSubChannelIndex OBJECT-TYPE SYNTAX Integer32 (0..2147483647) MAX-ACCESS read-only STATUS current DESCRIPTION "This indicates which subchannel is being referenced for a particular daughter board on a CMCC card. This value is constructed as follows: path * 256 + device Path and device are the values in CipCardClawConfigTable." ::= {cipCardSubChannelEntry 1}
cipCardSubChannelIndex OBJECT-TYPE SYNTAX Integer32(0..2147483647) ACCESS read-only STATUS mandatory DESCRIPTION "This indicates which subchannel is being referenced for a particular daughter board on a CMCC card. This value is constructed as follows: path * 256 + device Path and device are the values in CipCardClawConfigTable." ::= { cipCardSubChannelEntry 1 }
Automatically extracted from Cisco "SNMP v2 MIBs".
cipCardSubChannelIndex OBJECT-TYPE SYNTAX Integer32 (0..2147483647) MAX-ACCESS read-only STATUS current DESCRIPTION "This indicates which subchannel is being referenced for a particular daughter board on a CMCC card. This value is constructed as follows: path * 256 + device Path and device are the values in CipCardClawConfigTable." ::= {cipCardSubChannelEntry 1}
ciscoCipCsnaMIB MODULE-IDENTITY LAST-UPDATED "9508210000Z" ORGANIZATION "cisco IBM engineering Working Group" CONTACT-INFO " Cisco Systems Customer Service Postal: 170 W Tasman Drive San Jose, CA 95134 USA Tel: +1 800 553-NETS E-mail: [email protected]" DESCRIPTION "This is the Management Information Base (MIB) module for objects used to manage the cisco Systems Network Architecture (SNA) support on Cisco Mainframe Channel Connection (CMCC) cards, also called the CIP-SNA feature. | Acronym Definitions: | | CMCC = Cisco Mainframe Channel Connection | | CIP = Channel Interface Processor | | CTA = Channel Transport Architecture | | SNA = Systems Network Architecture | | CIP-SNA = CNA = CSNA = SNA Support on | | a CMCC card | This mib consists of the following tables: 1) CSNA Administration 2) CSNA Operational 3) CSNA Statistics 4) Max Sessions Administration 5) Max Sessions Operational 8) LLC2/CSNA Connection mapping The following is a set of IBM channel terminology: 1) The Channel Subsystem is the way a host performs I/O. 2) A Channel Path is the path to the Channel Control Unit. In the Cisco CMCC environment, this is the path of the channel to the physical router, itself. This path is needed because the physical channel may be directed (switched) through a device called an ESCON director. The path defined from the host to the Control Unit can be different than the path from the Control Unit to the host. For an in-depth definition of how this number is derived, see the cipCardCsnaAdminPath object. 3) A Sub-Channel and Device are exactly the same thing. The term Sub-Channel was introduced for ESCON (IBM's serial fiber optic) channel interface. Previously the term Device was used, and it mapped directly to hardware (in most situations) via a Parallel Channel Adapter (PCA). Another name for PCA is Bus & Tag. In the Cisco CMCC environment, the Sub-Channel is controlled by the Channel Systems Network Architecture (CSNA) feature. For an in-depth definition of how this number is derived, see the cipCardCsnaAdminDevice object. NOTE: The terminology of Sub-Channel and Sub-Channel Index are two completely different entities! See below for Sub-Channel Index. 4) An I/O Device is the entity that is addressed by the combination of Sub-Channel and Device. This directly maps to the cipCardCsnaAdminTable. NOTE: The Channel Systems Network Architecture (CSNA) feature may have multiple sub-channels/devices defined for its control. Also NOTE: That we have defined an object with the name cipCardSubChannelIndex and this object is the two hex octet Channel Path values concatenated with the second hex (the first octet is not used) octet Device value and then converted to an INTEGER (Unsigned). The exact description is taken from the CISCO-CHANNEL-MIB cipCardSubChannelIndex OBJECT-TYPE SYNTAX INTEGER MAX-ACCESS read-only STATUS current DESCRIPTION This indicates which subchannel is being referenced for a particular daughter board on a CMCC card. This value is constructed as follows: path * 256 + device Path and device are the values in CipCardClawConfigTable. ::= { cipCardSubChannelEntry 1 }
| OID | Name | Sub children | Sub Nodes Total | Description |
|---|---|---|---|---|
| 1.3.6.1.4.1.9.9.20.1.3.1.1.1 | cipCsnaObjects | 3 | 54 | None |
| 1.3.6.1.4.1.9.9.20.1.3.1.1.2 | cipCsnaNotificationPrefix | 1 | 3 | None |
| 1.3.6.1.4.1.9.9.20.1.3.1.1.3 | ciscoCipCsnaMibConformance | 2 | 6 | None |
| OID | Name | Sub children | Sub Nodes Total | Description |
|---|---|---|---|---|
| 1.3.6.1.4.1.9.9.20.1.3.1.2 | cipCardSubChannelConnections | 0 | 0 | Number of times a device was connected to the subchannel. For some devices, this correlates with the number of start subchannels. |
| 1.3.6.1.4.1.9.9.20.1.3.1.3 | cipCardSubChannelCancels | 0 | 0 | Number of halt subchannels. |
| 1.3.6.1.4.1.9.9.20.1.3.1.4 | cipCardSubChannelSelectiveResets | 0 | 0 | Number of selective resets. |
| 1.3.6.1.4.1.9.9.20.1.3.1.5 | cipCardSubChannelSystemResets | 0 | 0 | Number of system resets. |
| 1.3.6.1.4.1.9.9.20.1.3.1.6 | cipCardSubChannelDeviceErrors | 0 | 0 | Number of device level errors. |
| 1.3.6.1.4.1.9.9.20.1.3.1.7 | cipCardSubChannelWriteBlocksDropped | 0 | 0 | Number of times a block was received by the channel and a router buffer was not available so the block was discarded. |
| 1.3.6.1.4.1.9.9.20.1.3.1.8 | cipCardSubChannelLastSenseData | 0 | 0 | This is the last sense data sent to the channel by this device. |
| 1.3.6.1.4.1.9.9.20.1.3.1.9 | cipCardSubChannelLastSenseDataTime | 0 | 0 | This indicates the time when the last sense data was sent to the channel by this device. |
| 1.3.6.1.4.1.9.9.20.1.3.1.10 | cipCardSubChannelCuBusies | 0 | 0 | This is the number of control unit busies sent to the channel when this device was requested. |
| 1.3.6.1.4.1.9.9.20.1.3.1.11 | cipCardSubChannelCmdRetries | 0 | 0 | Number of times the subchannel went into command retry state. The sum of this value and cipCardSubChannelConnections gives the num… |
| 1.3.6.1.4.1.9.9.20.1.3.1.12 | cipCardSubChannelResetEvent | 0 | 0 | A state that a device gets into after a system reset and is cleared by a resetting event unit check. |
| 1.3.6.1.4.1.9.9.20.1.3.1.13 | cipCardSubChannelShortBusy | 0 | 0 | A transient state that a device can get into during processing of various resets. |
| 1.3.6.1.4.1.9.9.20.1.3.1.14 | cipCardSubChannelCMDRetry | 0 | 0 | A state that a device can get into if the mainframe tries to write data to the CMCC when the CMCC has no buffers for it or if the… |
| 1.3.6.1.4.1.9.9.20.1.3.1.15 | cipCardSubChannelBufferWait | 0 | 0 | A state that a device can get into when the mainframe tries to write data to the CMCC and the CMCC has no buffers for all of the … |
| 1.3.6.1.4.1.9.9.20.1.3.1.16 | cipCardSubChannelStatPending | 0 | 0 | Indicates that the CMCC has status to present for a particular device. The indication is cleared when the mainframe excepts the … |
| 1.3.6.1.4.1.9.9.20.1.3.1.17 | cipCardSubChannelSuspend | 0 | 0 | Indicates that the device task has decided to suspend data transfer for a particular device. |
| 1.3.6.1.4.1.9.9.20.1.3.1.18 | cipCardSubChannelFBLWait | 0 | 0 | A state that a device can get into when the mainframe tries to write data to the CMCC and the CMCC has no buffers for all of the … |