CISCO-CIPLAN-MIB.mib object view, vendor Cisco
Introduction
Most network devices and programs ship with so-called MIB files to describe the parameters and meanings (i.e.: friendly names) which are available for monitoring via SNMP.
ActiveXperts Network Monitor 2024 can import vendor-specific MIB files, so it can be used to monitor specific OID's (Object Identifiers).
This way, you can monitor your devices, computers, etc. by selecting your relevant OID's by name.
ActiveXperts Network Monitor 2024 can import MIB file CISCO-CIPLAN-MIB and use it to monitor vendor specific OID's.
CISCO-CIPLAN-MIB file content
Object view of CISCO-CIPLAN-MIB:
| Scalar Object |
| cipCardLanAdminEntry |
.1.3.6.1.4.1.9.9.34.1.1.1.1 |
|
A list of CMCC LAN configuration values.
|
| cipCardLanAdaptAdminEntry |
.1.3.6.1.4.1.9.9.34.1.1.2.1 |
|
A list of CMCC LAN Adapter configuration values.
|
| Tabular Object |
| cipCardLanAdminLanType |
.1.3.6.1.4.1.9.9.34.1.1.1.1.1 |
|
The type of Emulation applied to this
CMCC LAN.
|
| cipCardLanAdminLanId |
.1.3.6.1.4.1.9.9.34.1.1.1.1.2 |
|
The index value used with the ifIndex
to uniquely identify a CMCC LAN.
This is just an identifier and has
no relationship to the bridging
protocols.
|
| cipCardLanAdminBridgeType |
.1.3.6.1.4.1.9.9.34.1.1.1.1.3 |
|
The bridging type supported by
this CMCC LAN.
The value of transparentOnly (1) is valid for
all LAN types.
The value of sourcerouteOnly (2) is only valid for
iso88025tokenRing and fddi LAN types.
The value of transpAndSourceRoute (3) is valid for
all iso88025tokenRing and fddi LAN types.
|
| cipCardLanAdminSrbLocalRing |
.1.3.6.1.4.1.9.9.34.1.1.1.1.4 |
|
The local Segment (Ring) number that
uniquely identify this CIP LAN.
This variable is only valid when
cipCardLanAdminBridgeType is sourcerouteOnly (2)
or transpAndSourceRoute (3).
|
| cipCardLanAdminSrbBridgeNum |
.1.3.6.1.4.1.9.9.34.1.1.1.1.5 |
|
The Bridge number that represents this routers'
bridge number.
This variable is only valid when
cipCardLanAdminBridgeType is sourcerouteOnly (2)
or transpAndSourceRoute (3).
|
| cipCardLanAdminSrbTargetRing |
.1.3.6.1.4.1.9.9.34.1.1.1.1.6 |
|
The target Segment (Ring) number that is the next
hop from this segment.
This variable is only valid when
cipCardLanAdminBridgeType is sourcerouteOnly (2)
or transpAndSourceRoute (3).
|
| cipCardLanAdminTbBridgeGrp |
.1.3.6.1.4.1.9.9.34.1.1.1.1.7 |
|
The transparent bridge group that this
CIP LAN is a member.
This variable is only valid when
cipCardLanAdminBridgeType is transparentOnly (1)
or transpAndSourceRoute (3).
|
| cipCardLanAdminRowStatus |
.1.3.6.1.4.1.9.9.34.1.1.1.1.8 |
|
This object is used by a Management Station to create
or delete the row entry in the cipCardLanAdminTable
following the the RowStatus textual convention.
|
| cipCardLanAdaptAdminAdaptNo |
.1.3.6.1.4.1.9.9.34.1.1.2.1.1 |
|
The Adapter Number used when creating
a CMCC LAN Adapter. This value is
given by the instance value when
this row is being created.
This number corresponds to the
'ADAPNO' value used VTAM XCA
node definition.
This number uniquely identify this
Adapter from all other Adapters for
the LAN type, which is identified
in the associated CMCC LAN Adapter Table.
|
| cipCardLanAdaptAdminMacAddress |
.1.3.6.1.4.1.9.9.34.1.1.2.1.2 |
|
The Adapter MAC Address is assigned
by the router administrator. It is
a unique number used by protocols to
address this Adapter on the CMCC
LAN identified by the second index
(cipCardLanAdminLanId).
NOTE: In order to have duplicate
MAC Addresses, they must
be on different Source Route
Bridge LAN's.
|
| cipCardLanAdaptAdminAdaptName |
.1.3.6.1.4.1.9.9.34.1.1.2.1.3 |
|
This name is assigned by the router
administrator and must be unique per
router. Every interface of the router
can be named by the router administrator.
This object provides a means of naming the
CMCC LAN adapter interfaces.
The Adapter Name is used in the
Hierarchy Resource List when creating a
Systems Network Architecture Generic
Alert for the purpose of identify the
CMCC LAN adapter which generated the
alert.
|
| cipCardLanAdaptAdminRowStatus |
.1.3.6.1.4.1.9.9.34.1.1.2.1.4 |
|
This object is used by a Management Station to create
or delete the row entry in the cipCardCsnaAdminTable
following the the RowStatus textual convention.
|
| Table |
| cipCardLanAdminTable |
.1.3.6.1.4.1.9.9.34.1.1.1 |
|
This table contains configuration information for
the LAN feature on the CMCC card.
|
| cipCardLanAdaptAdminTable |
.1.3.6.1.4.1.9.9.34.1.1.2 |
|
This table contains configuration information for
the LAN Adapter feature on the CMCC card.
|
| Object Identifier |
| ciscoCipLanMIB |
.1.3.6.1.4.1.9.9.34 |
|
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 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
|
| cipLanObjects |
.1.3.6.1.4.1.9.9.34.1 |
| cipLan |
.1.3.6.1.4.1.9.9.34.1.1 |
| ciscoCipLanMibConformance |
.1.3.6.1.4.1.9.9.34.2 |
| ciscoCipLanMibCompliances |
.1.3.6.1.4.1.9.9.34.2.1 |
| ciscoCipLanMibGroups |
.1.3.6.1.4.1.9.9.34.2.2 |
| Group |
| ciscoLanGroup |
.1.3.6.1.4.1.9.9.34.2.2.1 |
|
A collection of objects providing CMCC
LAN Administration.
|
| ciscoLanAdaptGroup |
.1.3.6.1.4.1.9.9.34.2.2.2 |
|
A collection of objects providing CMCC
LAN Adapter Administration.
|
