Reference record for OID 1.3.6.1.4.1.9.9.34

parent: 1.3.6.1.4.1.9.9 (ciscoMgmt)
node code: 34
node name: ciscoCipLanMIB
dot oid: 1.3.6.1.4.1.9.9.34
type: OBJECT IDENTIFIER
asn1 oid: {iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprise(1) cisco(9) ciscoMgmt(9) ciscoCipLanMIB(34)}

{iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprises(1) cisco(9) ciscoMgmt(9) ciscoCipLanMIB(34)}

{iso(1) org(3) dod(6) internet(1) private(4) enterprise(1) cisco(9) ciscoMgmt(9) ciscoCipLanMIB(34)}

{iso(1) org(3) dod(6) internet(1) private(4) enterprises(1) cisco(9) ciscoMgmt(9) ciscoCipLanMIB(34)}

{iso(1) iso-identified-organization(3) dod(6) internet(1) private(4) enterprise(1) cisco(9) ciscoMgmt(9) ciscoCipLanMIB(34)}

{iso(1) iso-identified-organization(3) dod(6) internet(1) private(4) enterprises(1) cisco(9) ciscoMgmt(9) ciscoCipLanMIB(34)}
iri oid: /iso/identified-organization/dod/internet/private/enterprise/cisco/ciscoMgmt/ciscoCipLanMIB

/iso/identified-organization/dod/internet/private/enterprises/cisco/ciscoMgmt/ciscoCipLanMIB

/iso/org/dod/internet/private/enterprise/cisco/ciscoMgmt/ciscoCipLanMIB

/iso/org/dod/internet/private/enterprises/cisco/ciscoMgmt/ciscoCipLanMIB

/iso/iso-identified-organization/dod/internet/private/enterprise/cisco/ciscoMgmt/ciscoCipLanMIB

/iso/iso-identified-organization/dod/internet/private/enterprises/cisco/ciscoMgmt/ciscoCipLanMIB
iri by oid_info: /ISO/Identified-Organization/6/1/4/1/9/9/34

Description by circitor

This is the Management Information Base (MIB)
module for objects used to manage the cisco internal
LAN support in Cisco Mainframe Channel Connection
(CMCC) environments.

1) LAN
2) Adapter

The following example configuration of a router that
shows the entities managed by the CIPLAN MIB.

Router A

|
| | | |
| |
| | | Adapter |
| | | 400000000401 | / \ | |
| | | ADAPNO 0 |
| |
| | | Adapter |
| | | 400000000402 | \ / | |
| | | ADAPNO 1 |
| |
| | Token Ring | |
| | LAN 0 | |
| | | |
| |
| |
| | | Adapter |
| | | 400000000401 | | |
| | | ADAPNO 3 |
| |
| |
| | | |
| | Token Ring | |
| | LAN 1 | |
| | | |
| | | |
| |
| | | Adapter | | | |
| | | 0200000000C1 |
| | | ADAPNO 4 | | | |
| |
| | Ethernet | |
| | LAN 0 | |
| | | |
| | | |
| |
| | | Adapter | / \ | |
| | | 400000000001 |===| |=====| |
| | | ADAPNO 5 | \ / | |
| |
| | | |
| | FDDI | |
| | LAN 0 | |
| | | |
| | CMCC CARD 6 | |
|
| |

NOTE: A special ifIndex has been created to address
internal LAN objects that are on the CMCC card.

Physically the CMCC card would have two ifIndex's
of type `other` for each CMCC Slot/Daughter Board.
The additional ifIndex is made looks like the
physical with the Daughter Board being replaced
with a simple integer. For example:

If the CMCC is in slot/bay 6; The first daughter
board would have the ifIndex of 6/0. The
second daughter board would have the ifIndex
of 6/1. The internal objects on this CMCC card
would have the ifIndex of 6/2.

The ifIndex is an INTEGER to which the values will
be translated to agent specific number by the
agent itself.

The first table is the LAN Admin table.
Each entry created in this table will represent a
internal CIP LAN that will be used by MAC adapters
to bridge data to and from the host.
The indices of the table are:
* The special ifIndex that addresses the virtual
objects on a CMCC card
* The LAN type (token-ring, ethernet, fddi)
* The unique LAN identifier
NOTE: This value is used to uniquely identify
each and every LAN based on LAN type
and on a single CMCC card.
The fields included in this table represent:
* The LAN type used as on index
* The unique LAN identifier used as an index
* The bridging type
* For Source Route Bridging, the local ring number
* For Source Route Bridging, the next bridge number
* For Source Route Bridging, the target ring number
* For Transparent Bridging, the bridge group
* The row control variable
In the example above, four entries would exist.
The first entry would be:
- ifIndex is created by the agent
- LAN type of token ring
- LAN identifier of 0
- bridging type of Source Route
- local ring number 1000
- next bridge number is unknown
- target ring number is unknown
- transparent bridge group has no meaning
The second entry would be:
- ifIndex is created by the agent
- LAN type of token ring
- LAN identifier of 1
- bridging type of Source Route
- local ring number 1001
- next bridge number is unknown
- target ring number is unknown
- transparent bridge group has no meaning
The third entry would be:
- ifIndex is created by the agent
- LAN type of ethernet
- LAN identifier of 0
- bridging type of transparent
- local ring number has no meaning
- next bridge number has no meaning
- target ring number has no meaning
- transparent bridge group is unknown
The fourth entry would be:
- ifIndex is created by the agent
- LAN type of fddi
- LAN identifier of 0
- bridging type of transparent
- local ring number has no meaning
- next bridge number has no meaning
- target ring number has no meaning
- transparent bridge group is unknown

The last table is the CIP LAN Adapter Admin table.
Each entry created in this table will represent a
LAN adapter on one of the CMCC internal LAN's
defined in the first table.
The indices of the table are:
* The special ifIndex that addresses the virtual
objects on a CMCC card
* The LAN type (token-ring, ethernet, fddi)
* The unique LAN identifier from the first table
* The unique Adapter Number for this LAN type
NOTE: When multiple LANs of the same type
exist, this number must be kept unique
by the agent. (The LAN type is defined
by the Virtual LAN Admin table.)
The fields included in this table represent:
* The unique Adapter Number for this LAN type
as defined by the LAN Admin Entry
corresponding the the first two indices in
this table
* The MAC Address for this Adapter; this
MAC Address is unique for all Adapters
define on this LAN, but does not need to be
unique across LANs for redundancy
* The Adapter name
* The row control variable
In the example above, five entries would exist.
The first entry would be:
- ifIndex is created by the agent
- the LAN type from the first table
- the LAN identifier from the first table = 0
- adapter number of 0
- Mac Address of 400000000401
- Configured Name
The second entry would be:
- ifIndex is created by the agent
- the LAN type from the first table
- the LAN identifier from the first table = 0
- adapter number of 1
- Mac Address of 400000000402
- Configured Name
The first entry would be:
- ifIndex is created by the agent
- the LAN type from the first table
- the LAN identifier from the first table = 1
- adapter number of 2
- Mac Address of 400000000401
- Configured Name
The first entry would be:
- ifIndex is created by the agent
- the LAN type from the first table
- the LAN identifier from the first table = 0
- adapter number of 3
- Mac Address of 0200000000C1
- Configured Name
The first entry would be:
- ifIndex is created by the agent
- the LAN type from the first table
- the LAN identifier from the first table = 0
- adapter number of 4
- Mac Address of 400000000001
- Configured Name

Parsed from file CISCO-CIPLAN-MIB.mib
Module: CISCO-CIPLAN-MIB

Description by oid_info

ciscoCipLanMIB MODULE-IDENTITY LAST-UPDATED "9504280000Z" 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 internal LAN support in Cisco Mainframe Channel Connection (CMCC) environments. 1) LAN 2) Adapter The following example configuration of a router that shows the entities managed by the CIPLAN MIB. Router A ----------------------------------------- | ------------------------------------- | | | | | | | ------------------- | | | | | Adapter | -- | | | | | 400000000401 | / | | | | | ADAPNO 0 |---| Ring | | | | | ------------------- | |----| | | | | Adapter |---| 1000 | | | | | | 400000000402 | / | | | | | ADAPNO 1 | -- | | | | ------------------- | | | | Token Ring | | | | LAN 0 | | | | | | | | -- | | | | ------------------- / | | | | | Adapter |---| Ring | | | | | | 400000000401 | | |----| | | | | ADAPNO 3 |---| 1001 | | | | | ------------------- / | | | | -- | | | | | | | | Token Ring | | | | LAN 1 | | | | | | | | | | | | ------------------- | | | | | Adapter | | | | | | | 0200000000C1 |---------------| | | | | ADAPNO 4 | | | | | | ------------------- | | | | Ethernet | | | | LAN 0 | | | | | | | | | | | | ------------------- = | | | | | Adapter | / | | | | | 400000000001 |===| |=====| | | | | ADAPNO 5 | / | | | | ------------------- = | | | | | | | | FDDI | | | | LAN 0 | | | | | | | | CMCC CARD 6 | | | ------------------------------------- | | | ----------------------------------------- NOTE: A special ifIndex has been created to address internal LAN objects that are on the CMCC card. Physically the CMCC card would have two ifIndexs of type `other` for each CMCC Slot/Daughter Board. The additional ifIndex is made looks like the physical with the Daughter Board being replaced with a simple integer. For example: If the CMCC is in slot/bay 6; The first daughter board would have the ifIndex of 6/0. The second daughter board would have the ifIndex of 6/1. The internal objects on this CMCC card would have the ifIndex of 6/2. The ifIndex is an INTEGER to which the values will be translated to agent specific number by the agent itself. The first table is the LAN Admin table. Each entry created in this table will represent a internal CIP LAN that will be used by MAC adapters to bridge data to and from the host. The indices of the table are: * The special ifIndex that addresses the virtual objects on a CMCC card * The LAN type (token-ring, ethernet, fddi) * The unique LAN identifier NOTE: This value is used to uniquely identify each and every LAN based on LAN type and on a single CMCC card. The fields included in this table represent: * The LAN type used as on index * The unique LAN identifier used as an index * The bridging type * For Source Route Bridging, the local ring number * For Source Route Bridging, the next bridge number * For Source Route Bridging, the target ring number * For Transparent Bridging, the bridge group * The row control variable In the example above, four entries would exist. The first entry would be: - ifIndex is created by the agent - LAN type of token ring - LAN identifier of 0 - bridging type of Source Route - local ring number 1000 - next bridge number is unknown - target ring number is unknown - transparent bridge group has no meaning The second entry would be: - ifIndex is created by the agent - LAN type of token ring - LAN identifier of 1 - bridging type of Source Route - local ring number 1001 - next bridge number is unknown - target ring number is unknown - transparent bridge group has no meaning The third entry would be: - ifIndex is created by the agent - LAN type of ethernet - LAN identifier of 0 - bridging type of transparent - local ring number has no meaning - next bridge number has no meaning - target ring number has no meaning - transparent bridge group is unknown The fourth entry would be: - ifIndex is created by the agent - LAN type of fddi - LAN identifier of 0 - bridging type of transparent - local ring number has no meaning - next bridge number has no meaning - target ring number has no meaning - transparent bridge group is unknown The last table is the CIP LAN Adapter Admin table. Each entry created in this table will represent a LAN adapter on one of the CMCC internal LANs defined in the first table. The indices of the table are: * The special ifIndex that addresses the virtual objects on a CMCC card * The LAN type (token-ring, ethernet, fddi) * The unique LAN identifier from the first table * The unique Adapter Number for this LAN type NOTE: When multiple LANs of the same type exist, this number must be kept unique by the agent. (The LAN type is defined by the Virtual LAN Admin table.) The fields included in this table represent: * The unique Adapter Number for this LAN type as defined by the LAN Admin Entry corresponding the the first two indices in this table * The MAC Address for this Adapter; this MAC Address is unique for all Adapters define on this LAN, but does not need to be unique across LANs for redundancy * The Adapter name * The row control variable In the example above, five entries would exist. The first entry would be: - ifIndex is created by the agent - the LAN type from the first table - the LAN identifier from the first table = 0 - adapter number of 0 - Mac Address of 400000000401 - Configured Name The second entry would be: - ifIndex is created by the agent - the LAN type from the first table - the LAN identifier from the first table = 0 - adapter number of 1 - Mac Address of 400000000402 - Configured Name The first entry would be: - ifIndex is created by the agent - the LAN type from the first table - the LAN identifier from the first table = 1 - adapter number of 2 - Mac Address of 400000000401 - Configured Name The first entry would be: - ifIndex is created by the agent - the LAN type from the first table - the LAN identifier from the first table = 0 - adapter number of 3 - Mac Address of 0200000000C1 - Configured Name The first entry would be: - ifIndex is created by the agent - the LAN type from the first table - the LAN identifier from the first table = 0 - adapter number of 4 - Mac Address of 400000000001 - Configured Name " REVISION "9801060000Z" DESCRIPTION "With the addition of Ciscos new Channel Port Adapter cards, all the references to CIP in the MIB description and object descriptions are changed to CMCC (Cisco Mainframe Channel Connection). The object names in the form of cip... or cipCard... will remain the same, but will be valid objects for the Channel Port Adapter cards." REVISION "9504280000Z" DESCRIPTION "Initial version of this MIB module."
View at oid-info.com

Description by mibdepot

Description by cisco

Information by circitor

ciscoCipLanMIB MODULE-IDENTITY LAST-UPDATED "9504280000Z" 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 internal LAN support in Cisco Mainframe Channel Connection (CMCC) environments. 1) LAN 2) Adapter The following example configuration of a router that shows the entities managed by the CIPLAN MIB. Router A | | | | | | | | | | Adapter | | | | 400000000401 | / \ | | | | | ADAPNO 0 | | | | | | Adapter | | | | 400000000402 | \ / | | | | | ADAPNO 1 | | | | | Token Ring | | | | LAN 0 | | | | | | | | | | | | | Adapter | | | | 400000000401 | | | | | | ADAPNO 3 | | | | | | | | | | | Token Ring | | | | LAN 1 | | | | | | | | | | | | | | | Adapter | | | | | | | 0200000000C1 | | | | ADAPNO 4 | | | | | | | | Ethernet | | | | LAN 0 | | | | | | | | | | | | | | | Adapter | / \ | | | | | 400000000001 |===| |=====| | | | | ADAPNO 5 | \ / | | | | | | | | | | FDDI | | | | LAN 0 | | | | | | | | CMCC CARD 6 | | | | | NOTE: A special ifIndex has been created to address internal LAN objects that are on the CMCC card. Physically the CMCC card would have two ifIndex's of type `other` for each CMCC Slot/Daughter Board. The additional ifIndex is made looks like the physical with the Daughter Board being replaced with a simple integer. For example: If the CMCC is in slot/bay 6; The first daughter board would have the ifIndex of 6/0. The second daughter board would have the ifIndex of 6/1. The internal objects on this CMCC card would have the ifIndex of 6/2. The ifIndex is an INTEGER to which the values will be translated to agent specific number by the agent itself. The first table is the LAN Admin table. Each entry created in this table will represent a internal CIP LAN that will be used by MAC adapters to bridge data to and from the host. The indices of the table are: * The special ifIndex that addresses the virtual objects on a CMCC card * The LAN type (token-ring, ethernet, fddi) * The unique LAN identifier NOTE: This value is used to uniquely identify each and every LAN based on LAN type and on a single CMCC card. The fields included in this table represent: * The LAN type used as on index * The unique LAN identifier used as an index * The bridging type * For Source Route Bridging, the local ring number * For Source Route Bridging, the next bridge number * For Source Route Bridging, the target ring number * For Transparent Bridging, the bridge group * The row control variable In the example above, four entries would exist. The first entry would be: - ifIndex is created by the agent - LAN type of token ring - LAN identifier of 0 - bridging type of Source Route - local ring number 1000 - next bridge number is unknown - target ring number is unknown - transparent bridge group has no meaning The second entry would be: - ifIndex is created by the agent - LAN type of token ring - LAN identifier of 1 - bridging type of Source Route - local ring number 1001 - next bridge number is unknown - target ring number is unknown - transparent bridge group has no meaning The third entry would be: - ifIndex is created by the agent - LAN type of ethernet - LAN identifier of 0 - bridging type of transparent - local ring number has no meaning - next bridge number has no meaning - target ring number has no meaning - transparent bridge group is unknown The fourth entry would be: - ifIndex is created by the agent - LAN type of fddi - LAN identifier of 0 - bridging type of transparent - local ring number has no meaning - next bridge number has no meaning - target ring number has no meaning - transparent bridge group is unknown The last table is the CIP LAN Adapter Admin table. Each entry created in this table will represent a LAN adapter on one of the CMCC internal LAN's defined in the first table. The indices of the table are: * The special ifIndex that addresses the virtual objects on a CMCC card * The LAN type (token-ring, ethernet, fddi) * The unique LAN identifier from the first table * The unique Adapter Number for this LAN type NOTE: When multiple LANs of the same type exist, this number must be kept unique by the agent. (The LAN type is defined by the Virtual LAN Admin table.) The fields included in this table represent: * The unique Adapter Number for this LAN type as defined by the LAN Admin Entry corresponding the the first two indices in this table * The MAC Address for this Adapter; this MAC Address is unique for all Adapters define on this LAN, but does not need to be unique across LANs for redundancy * The Adapter name * The row control variable In the example above, five entries would exist. The first entry would be: - ifIndex is created by the agent - the LAN type from the first table - the LAN identifier from the first table = 0 - adapter number of 0 - Mac Address of 400000000401 - Configured Name The second entry would be: - ifIndex is created by the agent - the LAN type from the first table - the LAN identifier from the first table = 0 - adapter number of 1 - Mac Address of 400000000402 - Configured Name The first entry would be: - ifIndex is created by the agent - the LAN type from the first table - the LAN identifier from the first table = 1 - adapter number of 2 - Mac Address of 400000000401 - Configured Name The first entry would be: - ifIndex is created by the agent - the LAN type from the first table - the LAN identifier from the first table = 0 - adapter number of 3 - Mac Address of 0200000000C1 - Configured Name The first entry would be: - ifIndex is created by the agent - the LAN type from the first table - the LAN identifier from the first table = 0 - adapter number of 4 - Mac Address of 400000000001 - Configured Name " REVISION "9801060000Z" DESCRIPTION "With the addition of Cisco's new Channel Port Adapter cards, all the references to CIP in the MIB description and object descriptions are changed to CMCC (Cisco Mainframe Channel Connection). The object names in the form of cip... or cipCard... will remain the same, but will be valid objects for the Channel Port Adapter cards." REVISION "9504280000Z" DESCRIPTION "Initial version of this MIB module." ::= { ciscoMgmt 34 }

Information by cisco_v1

ciscoCipLanMIB OBJECT IDENTIFIER ::= { ciscoMgmt 34 }

Information by oid_info

Automatically extracted from Cisco "SNMP v2 MIBs".

Information by mibdepot

ciscoCipLanMIB MODULE-IDENTITY LAST-UPDATED "9504280000Z" 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 internal LAN support in Cisco Mainframe Channel Connection (CMCC) environments. 1) LAN 2) Adapter The following example configuration of a router that shows the entities managed by the CIPLAN MIB. Router A | | | | | | | | | | Adapter | | | | 400000000401 | / \ | | | | | ADAPNO 0 | | | | | | Adapter | | | | 400000000402 | \ / | | | | | ADAPNO 1 | | | | | Token Ring | | | | LAN 0 | | | | | | | | | | | | | Adapter | | | | 400000000401 | | | | | | ADAPNO 3 | | | | | | | | | | | Token Ring | | | | LAN 1 | | | | | | | | | | | | | | | Adapter | | | | | | | 0200000000C1 | | | | ADAPNO 4 | | | | | | | | Ethernet | | | | LAN 0 | | | | | | | | | | | | | | | Adapter | / \ | | | | | 400000000001 |===| |=====| | | | | ADAPNO 5 | \ / | | | | | | | | | | FDDI | | | | LAN 0 | | | | | | | | CMCC CARD 6 | | | | | NOTE: A special ifIndex has been created to address internal LAN objects that are on the CMCC card. Physically the CMCC card would have two ifIndex's of type `other` for each CMCC Slot/Daughter Board. The additional ifIndex is made looks like the physical with the Daughter Board being replaced with a simple integer. For example: If the CMCC is in slot/bay 6; The first daughter board would have the ifIndex of 6/0. The second daughter board would have the ifIndex of 6/1. The internal objects on this CMCC card would have the ifIndex of 6/2. The ifIndex is an INTEGER to which the values will be translated to agent specific number by the agent itself. The first table is the LAN Admin table. Each entry created in this table will represent a internal CIP LAN that will be used by MAC adapters to bridge data to and from the host. The indices of the table are: * The special ifIndex that addresses the virtual objects on a CMCC card * The LAN type (token-ring, ethernet, fddi) * The unique LAN identifier NOTE: This value is used to uniquely identify each and every LAN based on LAN type and on a single CMCC card. The fields included in this table represent: * The LAN type used as on index * The unique LAN identifier used as an index * The bridging type * For Source Route Bridging, the local ring number * For Source Route Bridging, the next bridge number * For Source Route Bridging, the target ring number * For Transparent Bridging, the bridge group * The row control variable In the example above, four entries would exist. The first entry would be: - ifIndex is created by the agent - LAN type of token ring - LAN identifier of 0 - bridging type of Source Route - local ring number 1000 - next bridge number is unknown - target ring number is unknown - transparent bridge group has no meaning The second entry would be: - ifIndex is created by the agent - LAN type of token ring - LAN identifier of 1 - bridging type of Source Route - local ring number 1001 - next bridge number is unknown - target ring number is unknown - transparent bridge group has no meaning The third entry would be: - ifIndex is created by the agent - LAN type of ethernet - LAN identifier of 0 - bridging type of transparent - local ring number has no meaning - next bridge number has no meaning - target ring number has no meaning - transparent bridge group is unknown The fourth entry would be: - ifIndex is created by the agent - LAN type of fddi - LAN identifier of 0 - bridging type of transparent - local ring number has no meaning - next bridge number has no meaning - target ring number has no meaning - transparent bridge group is unknown The last table is the CIP LAN Adapter Admin table. Each entry created in this table will represent a LAN adapter on one of the CMCC internal LAN's defined in the first table. The indices of the table are: * The special ifIndex that addresses the virtual objects on a CMCC card * The LAN type (token-ring, ethernet, fddi) * The unique LAN identifier from the first table * The unique Adapter Number for this LAN type NOTE: When multiple LANs of the same type exist, this number must be kept unique by the agent. (The LAN type is defined by the Virtual LAN Admin table.) The fields included in this table represent: * The unique Adapter Number for this LAN type as defined by the LAN Admin Entry corresponding the the first two indices in this table * The MAC Address for this Adapter; this MAC Address is unique for all Adapters define on this LAN, but does not need to be unique across LANs for redundancy * The Adapter name * The row control variable In the example above, five entries would exist. The first entry would be: - ifIndex is created by the agent - the LAN type from the first table - the LAN identifier from the first table = 0 - adapter number of 0 - Mac Address of 400000000401 - Configured Name The second entry would be: - ifIndex is created by the agent - the LAN type from the first table - the LAN identifier from the first table = 0 - adapter number of 1 - Mac Address of 400000000402 - Configured Name The first entry would be: - ifIndex is created by the agent - the LAN type from the first table - the LAN identifier from the first table = 1 - adapter number of 2 - Mac Address of 400000000401 - Configured Name The first entry would be: - ifIndex is created by the agent - the LAN type from the first table - the LAN identifier from the first table = 0 - adapter number of 3 - Mac Address of 0200000000C1 - Configured Name The first entry would be: - ifIndex is created by the agent - the LAN type from the first table - the LAN identifier from the first table = 0 - adapter number of 4 - Mac Address of 400000000001 - Configured Name " REVISION "9801060000Z" DESCRIPTION "With the addition of Cisco's new Channel Port Adapter cards, all the references to CIP in the MIB description and object descriptions are changed to CMCC (Cisco Mainframe Channel Connection). The object names in the form of cip... or cipCard... will remain the same, but will be valid objects for the Channel Port Adapter cards." REVISION "9504280000Z" DESCRIPTION "Initial version of this MIB module." ::= { ciscoMgmt 34 }

Information by cisco

ciscoCipLanMIB MODULE-IDENTITY LAST-UPDATED "9504280000Z" 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 internal LAN support in Cisco Mainframe Channel Connection (CMCC) environments. 1) LAN 2) Adapter The following example configuration of a router that shows the entities managed by the CIPLAN MIB. Router A | | | | | | | | | | Adapter | | | | 400000000401 | / \ | | | | | ADAPNO 0 | | | | | | Adapter | | | | 400000000402 | \ / | | | | | ADAPNO 1 | | | | | Token Ring | | | | LAN 0 | | | | | | | | | | | | | Adapter | | | | 400000000401 | | | | | | ADAPNO 3 | | | | | | | | | | | Token Ring | | | | LAN 1 | | | | | | | | | | | | | | | Adapter | | | | | | | 0200000000C1 | | | | ADAPNO 4 | | | | | | | | Ethernet | | | | LAN 0 | | | | | | | | | | | | | | | Adapter | / \ | | | | | 400000000001 |===| |=====| | | | | ADAPNO 5 | \ / | | | | | | | | | | FDDI | | | | LAN 0 | | | | | | | | CMCC CARD 6 | | | | | NOTE: A special ifIndex has been created to address internal LAN objects that are on the CMCC card. Physically the CMCC card would have two ifIndex's of type `other` for each CMCC Slot/Daughter Board. The additional ifIndex is made looks like the physical with the Daughter Board being replaced with a simple integer. For example: If the CMCC is in slot/bay 6; The first daughter board would have the ifIndex of 6/0. The second daughter board would have the ifIndex of 6/1. The internal objects on this CMCC card would have the ifIndex of 6/2. The ifIndex is an INTEGER to which the values will be translated to agent specific number by the agent itself. The first table is the LAN Admin table. Each entry created in this table will represent a internal CIP LAN that will be used by MAC adapters to bridge data to and from the host. The indices of the table are: * The special ifIndex that addresses the virtual objects on a CMCC card * The LAN type (token-ring, ethernet, fddi) * The unique LAN identifier NOTE: This value is used to uniquely identify each and every LAN based on LAN type and on a single CMCC card. The fields included in this table represent: * The LAN type used as on index * The unique LAN identifier used as an index * The bridging type * For Source Route Bridging, the local ring number * For Source Route Bridging, the next bridge number * For Source Route Bridging, the target ring number * For Transparent Bridging, the bridge group * The row control variable In the example above, four entries would exist. The first entry would be: - ifIndex is created by the agent - LAN type of token ring - LAN identifier of 0 - bridging type of Source Route - local ring number 1000 - next bridge number is unknown - target ring number is unknown - transparent bridge group has no meaning The second entry would be: - ifIndex is created by the agent - LAN type of token ring - LAN identifier of 1 - bridging type of Source Route - local ring number 1001 - next bridge number is unknown - target ring number is unknown - transparent bridge group has no meaning The third entry would be: - ifIndex is created by the agent - LAN type of ethernet - LAN identifier of 0 - bridging type of transparent - local ring number has no meaning - next bridge number has no meaning - target ring number has no meaning - transparent bridge group is unknown The fourth entry would be: - ifIndex is created by the agent - LAN type of fddi - LAN identifier of 0 - bridging type of transparent - local ring number has no meaning - next bridge number has no meaning - target ring number has no meaning - transparent bridge group is unknown The last table is the CIP LAN Adapter Admin table. Each entry created in this table will represent a LAN adapter on one of the CMCC internal LAN's defined in the first table. The indices of the table are: * The special ifIndex that addresses the virtual objects on a CMCC card * The LAN type (token-ring, ethernet, fddi) * The unique LAN identifier from the first table * The unique Adapter Number for this LAN type NOTE: When multiple LANs of the same type exist, this number must be kept unique by the agent. (The LAN type is defined by the Virtual LAN Admin table.) The fields included in this table represent: * The unique Adapter Number for this LAN type as defined by the LAN Admin Entry corresponding the the first two indices in this table * The MAC Address for this Adapter; this MAC Address is unique for all Adapters define on this LAN, but does not need to be unique across LANs for redundancy * The Adapter name * The row control variable In the example above, five entries would exist. The first entry would be: - ifIndex is created by the agent - the LAN type from the first table - the LAN identifier from the first table = 0 - adapter number of 0 - Mac Address of 400000000401 - Configured Name The second entry would be: - ifIndex is created by the agent - the LAN type from the first table - the LAN identifier from the first table = 0 - adapter number of 1 - Mac Address of 400000000402 - Configured Name The first entry would be: - ifIndex is created by the agent - the LAN type from the first table - the LAN identifier from the first table = 1 - adapter number of 2 - Mac Address of 400000000401 - Configured Name The first entry would be: - ifIndex is created by the agent - the LAN type from the first table - the LAN identifier from the first table = 0 - adapter number of 3 - Mac Address of 0200000000C1 - Configured Name The first entry would be: - ifIndex is created by the agent - the LAN type from the first table - the LAN identifier from the first table = 0 - adapter number of 4 - Mac Address of 400000000001 - Configured Name " REVISION "9801060000Z" DESCRIPTION "With the addition of Cisco's new Channel Port Adapter cards, all the references to CIP in the MIB description and object descriptions are changed to CMCC (Cisco Mainframe Channel Connection). The object names in the form of cip... or cipCard... will remain the same, but will be valid objects for the Channel Port Adapter cards." REVISION "9504280000Z" DESCRIPTION "Initial version of this MIB module." ::= { ciscoMgmt 34 }

First Registration Authority (recovered by parent 1.3.6.1.4.1.9)

Greg Satz

Current Registration Authority (recovered by parent 1.3.6.1.4.1.9)

Cisco Systems, Inc.

Children (2)

OID	Name	Sub children	Sub Nodes Total	Description
1.3.6.1.4.1.9.9.34.1	cipLanObjects	1	17	None
1.3.6.1.4.1.9.9.34.2	ciscoCipLanMibConformance	2	5	None

Brothers (645)

To many brothers! Only 100 nearest brothers are shown.

OID	Name	Sub children	Sub Nodes Total	Description
...
1.3.6.1.4.1.9.9.6	ciscoTcpMIB	3	20	An extension to the IETF MIB module for managing TCP implementations
1.3.6.1.4.1.9.9.10	ciscoFlashMIB	2	164	This MIB provides for the management of Cisco Flash Devices.
1.3.6.1.4.1.9.9.13	ciscoEnvMonMIB	4	68	The MIB module to describe the status of the Environmental Monitor on those devices which support one.
1.3.6.1.4.1.9.9.16	ciscoPingMIB	3	31	Modified description of ciscoPingAddress object.
1.3.6.1.4.1.9.9.17	ciscoVinesMIB	2	188	" REVISION "9506070000Z
1.3.6.1.4.1.9.9.18	ciscoIsdnuIfMIB	3	29	ISDN BRI integrated U Interface MIB module. This MIB manages the ISDN BRI integrated U Interface in the router.
1.3.6.1.4.1.9.9.19	ciscoSnapshotMIB	2	28	Snapshot routing MIB
1.3.6.1.4.1.9.9.20	channel	2	169	This is the MIB module for objects used to manage the Cisco Mainframe Channel Connection (CMCC) cards.
1.3.6.1.4.1.9.9.22	ciscoRptrMIB	3	32	" REVISION "9512050000Z
1.3.6.1.4.1.9.9.23	ciscoCdpMIB	2	78	The MIB module for management of the Cisco Discovery Protocol in Cisco devices.
1.3.6.1.4.1.9.9.24	ciscoDspuMIB	2	150	Used to define and manage DSPU objects.
1.3.6.1.4.1.9.9.25	ciscoImageMIB	2	10	Router image MIB which identify the capabilities and characteristics of the image
1.3.6.1.4.1.9.9.26	ciscoIsdnMib	3	34	The MIB module to describe the status of the ISDN Interfaces on the routers.
1.3.6.1.4.1.9.9.27	ciscoCallHistoryMib	2	40	The MIB module to describe and store the call information of the routers for accounting purposes.
1.3.6.1.4.1.9.9.28	ciscoSnaSdllcMIB	3	28	`ciscoSnaSdllcMIB MODULE-IDENTITY LAST-UPDATED "9812170000Z" ORGANIZATION "Cisco Systems, Inc." CONTACT-INFO " Cisco Systems Cus…`
1.3.6.1.4.1.9.9.29	ciscoRsrbMIB	3	45	This is the MIB module for objects used to manage RSRB. Overview of remote source-route bridging (RSRB) management and MIB MIB …
1.3.6.1.4.1.9.9.30	ciscoStunMIB	3	41	The MIB module for serial Tunneling. Overview of STUN MIB MIB description The STUN MIB provides the configuration and operationa…
1.3.6.1.4.1.9.9.31	ciscoTcpOffloadMIB	2	20	This is the MIB module for objects used to manage the cisco tcp offload feature. The IBM mainframe (host) supports TCP/IP. As a …
1.3.6.1.4.1.9.9.32	ciscoCipTcpIpMIB	2	88	This is the MIB module for objects used to manage the cisco TCP/IP stack running on the Cisco Mainframe Channel Connection (CMCC)…
1.3.6.1.4.1.9.9.33	ciscoCipCsnaMIB	3	66	None
1.3.6.1.4.1.9.9.35	ciscoBstunMIB	3	71	The MIB module for Block Serial Tunneling. Overview of BSTUN MIB MIB description The BSTUN MIB provides the configuration and o…
1.3.6.1.4.1.9.9.36	ciscoBscMIB	2	46	The MIB module for BSC. Overview of BSC MIB MIB description The BSC MIB provides the configuration and operational information on…
1.3.6.1.4.1.9.9.37	ciscoQueueMIB	3	23	This is the MIB module for objects used to manage interface queuing in Cisco devices.
1.3.6.1.4.1.9.9.38	ciscoLecsMIB	2	77	The MIB module for the management of LANE Configuration in Cisco devices.
1.3.6.1.4.1.9.9.39	ciscoLesMIB	2	82	The MIB module for the management of LANE Service in Cisco devices.
1.3.6.1.4.1.9.9.40	ciscoBusMIB	2	37	The MIB module for the management of LANE broadcast and unknown servers.
1.3.6.1.4.1.9.9.41	ciscoSyslogMIB	3	49	The MIB module to describe and store the system messages generated by the IOS and any other OS which supports syslogs.
1.3.6.1.4.1.9.9.42	ciscoRttMonMIB	3	816	This module defines a MIB for Round Trip Time (RTT) monitoring of a list of targets, using a variety of protocols. The table struc…
1.3.6.1.4.1.9.9.43	ciscoConfigManMIB	3	75	Configuration management MIB. The MIB represents a model of configuration data that exists in various locations: running in use b…
1.3.6.1.4.1.9.9.44	ciscoICsuDsuMIB	4	70	Integrated CSU/DSU MIB module. For T1 and Switched 56 kbps interfaces.
1.3.6.1.4.1.9.9.45	ciscoAtmIfPhysMIB	2	39	A minimal set of managed objects for tracking the status of DS3/E3/DS1/E1 and SONET interfaces.
1.3.6.1.4.1.9.9.46	ciscoVtpMIB	3	261	The MIB module for entities implementing the VTP protocol and Vlan management.
1.3.6.1.4.1.9.9.47	ciscoModemMgmtMIB	3	112	This MIB module provides modem call related data for tracking the progress and status of a call.
1.3.6.1.4.1.9.9.48	ciscoMemoryPoolMIB	3	32	MIB module for monitoring memory pools
1.3.6.1.4.1.9.9.49	ciscoFrameRelayMIB	2	158	Cisco Frame Relay MIB
1.3.6.1.4.1.9.9.50	ciscoAtmServiceRegistryMIB	2	14	A MIB module to allow an NMS to monitor and configure the information which an ATM switch makes available via the ILMI's Service …
1.3.6.1.4.1.9.9.51	ciscoAtmSwAddrMIB	2	11	ATM Switch address MIB
1.3.6.1.4.1.9.9.52	ciscoIpEncryptionMIB	3	51	Used to manage the encryption feature.
1.3.6.1.4.1.9.9.53	ciscoVmpsMIB	3	55	The MIB module for the management of the VLAN Membership Policy Server.
1.3.6.1.4.1.9.9.54	ciscoTn3270ServerMIB	3	105	The MIB module for TN3270 Server. MIB description The PU and LU MIB are defined in RFC 1666. This MIB provides additional informa…
1.3.6.1.4.1.9.9.55	ciscoAsppMIB	2	29	The ASPP MIB provides the configuration and operational information on asynchronous polled protocols such as the asynchronous sec…
1.3.6.1.4.1.9.9.56	ciscoVlanBridgingMIB	2	13	A set of managed objects for optimizing access to bridging related data from RFC 1493. This MIB is modeled after portions of RFC…
1.3.6.1.4.1.9.9.57	ciscoCompressionServiceAdapterMIB	2	19	Used to manage the compression service adapter.
1.3.6.1.4.1.9.9.59	ciscoStackMakerMIB	2	15	The MIB module for Cisco Systems' StackMaker.
1.3.6.1.4.1.9.9.60	ciscoAtmDualPhyMIB	3	26	Initial version of this MIB module. Phy definition Throughout this document phy is used as an abbreviation for Physical Interface.…
1.3.6.1.4.1.9.9.61	ciscoAccessEnvMonMIB	3	13	The MIB module to describe the additional status of the Environmental Monitor on those Cisco Access devices which support one.
1.3.6.1.4.1.9.9.62	ciscoVoiceAnalogIfMIB	2	90	Analog Voice Interface MIB module. This MIB manages the E&M, FXO, FXS Interfaces in the router.
1.3.6.1.4.1.9.9.63	ciscoVoiceDialControlMIB	3	377	This MIB module enhances the IETF Dial Control MIB (RFC2128) by providing management of voice telephony peers on both a circuit-s…
1.3.6.1.4.1.9.9.64	ciscoVoiceInterfaceMIB	2	24	Common Voice Interface MIB module. The MIB module manages the common voice related parameters for both voice analog and ISDN inte…
1.3.6.1.4.1.9.9.65	ciscoPnniMIB	2	49	The MIB module for managing Cisco specific extensions to the ATM Forum PNNI MIB.
1.3.6.1.4.1.9.9.66	ciscoAal5MIB	2	25	Cisco Enterprise AAL5 MIB file that provide AAL5 specific information that are either excluded by RFC 1695 or specific to Cisco p…
1.3.6.1.4.1.9.9.67	ciscoAtmAccessListMIB	2	39	A cisco ATM access list mib module.
1.3.6.1.4.1.9.9.68	ciscoVlanMembershipMIB	3	90	The MIB module for the management of the VLAN Membership within the frame work of Cisco VLAN Architecture, v 2.0 by Keith McClog…
1.3.6.1.4.1.9.9.69	ciscoLecDataVccMIB	3	13	This MIB module is a Cisco extension to the ATM Forum's LANE Client MIB. This extension identifies those VCCs which are being us…
1.3.6.1.4.1.9.9.72	ciscoCipCmpcMIB	3	46	This is the Management Information Base (MIB) module for objects used to manage the Cisco Multi-Path Channel (MPC) support on Cis…
1.3.6.1.4.1.9.9.73	ciscoCipTgMIB	2	98	This is the Management Information Base (MIB) module for objects used to manage Transmission Groups (TGs) in Cisco Mainframe Chan…
1.3.6.1.4.1.9.9.74	ciscoDlswExtMIB	3	134	The MIB module for management of Cisco specific Data Link Switching protocol enhancements. DLSw is described in RFC 1795 and RFC…
1.3.6.1.4.1.9.9.76	ciscoDlcSwitchMIB	2	55	This is the MIB module for objects used to manage FRAS sessions to the endstation. These objects are specific to downstream or end…
1.3.6.1.4.1.9.9.77	ciscoLecExtMIB	3	12	This MIB module is a Cisco extension to the ATM Forum's LANE Client MIB.
1.3.6.1.4.1.9.9.78	ciscoAtmSigDiagMIB	2	58	The MIB module to facilitate the diagnosis of failures of ATM Signalling requests. Through this MIB, an ATM device retains infor…
1.3.6.1.4.1.9.9.80	ciscoFtpClientMIB	2	29	The MIB module for invoking Internet File Transfer Protocol (FTP) operations for network management purposes.
1.3.6.1.4.1.9.9.81	ciscoBulkFileMIB	3	63	The MIB module for creating and deleting bulk files of SNMP data for file transfer.
1.3.6.1.4.1.9.9.82	ciscoStpExtensionsMIB	3	300	The MIB module for managing Cisco extensions to the 802.1D Spanning Tree Protocol (STP).
1.3.6.1.4.1.9.9.83	ciscoWredMIB	2	26	Cisco WRED MIB - Overview Cisco Weighted Random Early Detection/Drop is a method which avoids traffic congestion on an output int…
1.3.6.1.4.1.9.9.84	ciscoIpStatMIB	2	34	Cisco IP Statistics MIB - Overview This MIB incorporates objects to provide support for the Cisco IP statistics as implemented in…
...