This is the MIB module for objects used to manage SDLLC.
Overview of SDLLC conversion MIB
MIB description
The SDLLC MIB includes read-only configuration and operational
information on Cisco's implementation of SDLC to LLC2 media
translation. The following example shows the entities managed
by the SDLLC MIB.
FEP/ == Token == CISCO A == WAN/RSRB == CISCO B == Serial == SDLC
Host Ring line station
|=============== LLC2 session ============|=== SDLC session ====|
In this example configuration, CISCO B is performing the SDLLC
conversion, and so we query CISCO B for this MIB.
The SDLC device believes it is talking to the host via a direct
SDLC session. The host believes it is talking to the SDLC station on
the same token ring. CISCO A is also unaware of the SDLLC conversion
going on at CISCO B; it just believes it has an RSRB session with
its peer CISCO B to bridge two token ring separated by a WAN.
So CISCO B is the only agent that can provide the SDLLC conversion
details. We can combine this MIB with the CISCO-RSRB-MIB from
either CISCO A or CISCO B to get a better picture of the network.
This MIB has two tables:
convSdllcPortTable has an entry for each serial interface for
general SDLLC information on an interface, such as administered
virtual MAC addresses and virtual ring and bridge numbers.
This table is indexed by ifIndex.
convSdllcAddrTable has an entry for each serial interface and
SDLC address pair. It contains information specific to an SDLC
address on an interface, such as the partner MAC address,
XID value, and address state. This table is indexed by ifIndex
and convSdllcAddrSdlcAddr (the address of the SDLC station).
The above configuration would have a single entry in each table.
If CISCO B had two serial lines configured for sdllc conversion,
there would be two entries per table. If there
were only one serial line, but it was multipoint and
supported two sdlc addresses on the other end of the
line, there would be a single entry in convSdllcPortTable, and
two entries in convSdllcAddrTable.
The MIB provides the following information for convSdllcPortTable:
convSdllcPortVirtMacAddr - The locally administered MAC addressed
assigned to the serial interface. Note that this address must
always end in '00'. CISCO B replaces the 00 with the sdlc
address of the serial device. For a multipoint configuration
with two SDLC stations the llc2 side will 'see' two token ring
stations with unique MAC addresses on the sdlc side.
convSdllcPortVirtRing - The locally administered token ring number
assigned to the serial interface. This gives the serial interface
a token ring appearance to the llc2 side of the conversion, so
that it appears that it is a token ring on the other side of
a bridge.
convSdllcPortBridge - The bridge number assigned to CISCO B
convSdllcPortLlc2Ring - The token ring number on the LLC2 session
side. In this case it is the RSRB virtual ring group number
between CISCO A and CISCO B.
convSdllcPortLocalAck - indicates whether local acknowledgement
of SDLLC sessions is active.
convSdllcPortLocalAckState - indicates the state of
the local acknowledgement session.
convSdllcPortMaxLlc2FrameSize - the largest I-frame size that
can be sent or received on the LLC2 session.
The MIB provides the following information for convSdllcAddrTable:
convSdllcAddrSdlcAddr - The address of the SDLC station.
convSdllcAddrPartnerMacAddr - The MAC address of the FEP, as
specified with the sdllc partner command.
convSdllcAddrXID - The IDBLK and IDNUM of the SDLC station;
these must match the VTAM configured values
convSdllcAddrState - indicates the state of the SDLLC conversion
convSdllcAddrMaxSdlcFrameSize - the largest I-frame size that
can be sent or received on the SDLC session.
Parsed from file CISCO-SDLLC-MIB.mib
Module: CISCO-SDLLC-MIB
ciscoSnaSdllcMIB MODULE-IDENTITY
LAST-UPDATED "9812170000Z"
ORGANIZATION "Cisco Systems, Inc."
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 MIB module for objects used to manage SDLLC.
Overview of SDLLC conversion MIB
MIB description
The SDLLC MIB includes read-only configuration and operational
information on Ciscos implementation of SDLC to LLC2 media
translation. The following example shows the entities managed
by the SDLLC MIB.
FEP/ == Token == CISCO A == WAN/RSRB == CISCO B == Serial == SDLC
Host Ring line station
|=============== LLC2 session ============|=== SDLC session ====|
In this example configuration, CISCO B is performing the SDLLC
conversion, and so we query CISCO B for this MIB.
The SDLC device believes it is talking to the host via a direct
SDLC session. The host believes it is talking to the SDLC station on
the same token ring. CISCO A is also unaware of the SDLLC conversion
going on at CISCO B; it just believes it has an RSRB session with
its peer CISCO B to bridge two token ring separated by a WAN.
So CISCO B is the only agent that can provide the SDLLC conversion
details. We can combine this MIB with the CISCO-RSRB-MIB from
either CISCO A or CISCO B to get a better picture of the network.
This MIB has two tables:
convSdllcPortTable has an entry for each serial interface for
general SDLLC information on an interface, such as administered
virtual MAC addresses and virtual ring and bridge numbers.
This table is indexed by ifIndex.
convSdllcAddrTable has an entry for each serial interface and
SDLC address pair. It contains information specific to an SDLC
address on an interface, such as the partner MAC address,
XID value, and address state. This table is indexed by ifIndex
and convSdllcAddrSdlcAddr (the address of the SDLC station).
The above configuration would have a single entry in each table.
If CISCO B had two serial lines configured for sdllc conversion,
there would be two entries per table. If there
were only one serial line, but it was multipoint and
supported two sdlc addresses on the other end of the
line, there would be a single entry in convSdllcPortTable, and
two entries in convSdllcAddrTable.
The MIB provides the following information for convSdllcPortTable:
convSdllcPortVirtMacAddr - The locally administered MAC addressed
assigned to the serial interface. Note that this address must
always end in
View at oid-info.com
This is the MIB module for objects used to manage SDLLC.
Overview of SDLLC conversion MIB
MIB description
The SDLLC MIB includes read-only configuration and operational
information on Cisco's implementation of SDLC to LLC2 media
translation. The following example shows the entities managed
by the SDLLC MIB.
FEP/ == Token == CISCO A == WAN/RSRB == CISCO B == Serial == SDLC
Host Ring line station
|=============== LLC2 session ============|=== SDLC session ====|
In this example configuration, CISCO B is performing the SDLLC
conversion, and so we query CISCO B for this MIB.
The SDLC device believes it is talking to the host via a direct
SDLC session. The host believes it is talking to the SDLC station on
the same token ring. CISCO A is also unaware of the SDLLC conversion
going on at CISCO B; it just believes it has an RSRB session with
its peer CISCO B to bridge two token ring separated by a WAN.
So CISCO B is the only agent that can provide the SDLLC conversion
details. We can combine this MIB with the CISCO-RSRB-MIB from
either CISCO A or CISCO B to get a better picture of the network.
This MIB has two tables:
convSdllcPortTable has an entry for each serial interface for
general SDLLC information on an interface, such as administered
virtual MAC addresses and virtual ring and bridge numbers.
This table is indexed by ifIndex.
convSdllcAddrTable has an entry for each serial interface and
SDLC address pair. It contains information specific to an SDLC
address on an interface, such as the partner MAC address,
XID value, and address state. This table is indexed by ifIndex
and convSdllcAddrSdlcAddr (the address of the SDLC station).
The above configuration would have a single entry in each table.
If CISCO B had two serial lines configured for sdllc conversion,
there would be two entries per table. If there
were only one serial line, but it was multipoint and
supported two sdlc addresses on the other end of the
line, there would be a single entry in convSdllcPortTable, and
two entries in convSdllcAddrTable.
The MIB provides the following information for convSdllcPortTable:
convSdllcPortVirtMacAddr - The locally administered MAC addressed
assigned to the serial interface. Note that this address must
always end in '00'. CISCO B replaces the 00 with the sdlc
address of the serial device. For a multipoint configuration
with two SDLC stations the llc2 side will 'see' two token ring
stations with unique MAC addresses on the sdlc side.
convSdllcPortVirtRing - The locally administered token ring number
assigned to the serial interface. This gives the serial interface
a token ring appearance to the llc2 side of the conversion, so
that it appears that it is a token ring on the other side of
a bridge.
convSdllcPortBridge - The bridge number assigned to CISCO B
convSdllcPortLlc2Ring - The token ring number on the LLC2 session
side. In this case it is the RSRB virtual ring group number
between CISCO A and CISCO B.
convSdllcPortLocalAck - indicates whether local acknowledgement
of SDLLC sessions is active.
convSdllcPortLocalAckState - indicates the state of
the local acknowledgement session.
convSdllcPortMaxLlc2FrameSize - the largest I-frame size that
can be sent or received on the LLC2 session.
The MIB provides the following information for convSdllcAddrTable:
convSdllcAddrSdlcAddr - The address of the SDLC station.
convSdllcAddrPartnerMacAddr - The MAC address of the FEP, as
specified with the sdllc partner command.
convSdllcAddrXID - The IDBLK and IDNUM of the SDLC station;
these must match the VTAM configured values
convSdllcAddrState - indicates the state of the SDLLC conversion
convSdllcAddrMaxSdlcFrameSize - the largest I-frame size that
can be sent or received on the SDLC session.
Parsed from file CISCO-SDLLC-MIB.my.txt
Company: None
Module: CISCO-SDLLC-MIB
This is the MIB module for objects used to manage SDLLC.
Overview of SDLLC conversion MIB
MIB description
The SDLLC MIB includes read-only configuration and operational
information on Cisco's implementation of SDLC to LLC2 media
translation. The following example shows the entities managed
by the SDLLC MIB.
FEP/ == Token == CISCO A == WAN/RSRB == CISCO B == Serial == SDLC
Host Ring line station
|=============== LLC2 session ============|=== SDLC session ====|
In this example configuration, CISCO B is performing the SDLLC
conversion, and so we query CISCO B for this MIB.
The SDLC device believes it is talking to the host via a direct
SDLC session. The host believes it is talking to the SDLC station on
the same token ring. CISCO A is also unaware of the SDLLC conversion
going on at CISCO B; it just believes it has an RSRB session with
its peer CISCO B to bridge two token ring separated by a WAN.
So CISCO B is the only agent that can provide the SDLLC conversion
details. We can combine this MIB with the CISCO-RSRB-MIB from
either CISCO A or CISCO B to get a better picture of the network.
This MIB has two tables:
convSdllcPortTable has an entry for each serial interface for
general SDLLC information on an interface, such as administered
virtual MAC addresses and virtual ring and bridge numbers.
This table is indexed by ifIndex.
convSdllcAddrTable has an entry for each serial interface and
SDLC address pair. It contains information specific to an SDLC
address on an interface, such as the partner MAC address,
XID value, and address state. This table is indexed by ifIndex
and convSdllcAddrSdlcAddr (the address of the SDLC station).
The above configuration would have a single entry in each table.
If CISCO B had two serial lines configured for sdllc conversion,
there would be two entries per table. If there
were only one serial line, but it was multipoint and
supported two sdlc addresses on the other end of the
line, there would be a single entry in convSdllcPortTable, and
two entries in convSdllcAddrTable.
The MIB provides the following information for convSdllcPortTable:
convSdllcPortVirtMacAddr - The locally administered MAC addressed
assigned to the serial interface. Note that this address must
always end in '00'. CISCO B replaces the 00 with the sdlc
address of the serial device. For a multipoint configuration
with two SDLC stations the llc2 side will 'see' two token ring
stations with unique MAC addresses on the sdlc side.
convSdllcPortVirtRing - The locally administered token ring number
assigned to the serial interface. This gives the serial interface
a token ring appearance to the llc2 side of the conversion, so
that it appears that it is a token ring on the other side of
a bridge.
convSdllcPortBridge - The bridge number assigned to CISCO B
convSdllcPortLlc2Ring - The token ring number on the LLC2 session
side. In this case it is the RSRB virtual ring group number
between CISCO A and CISCO B.
convSdllcPortLocalAck - indicates whether local acknowledgement
of SDLLC sessions is active.
convSdllcPortLocalAckState - indicates the state of
the local acknowledgement session.
convSdllcPortMaxLlc2FrameSize - the largest I-frame size that
can be sent or received on the LLC2 session.
The MIB provides the following information for convSdllcAddrTable:
convSdllcAddrSdlcAddr - The address of the SDLC station.
convSdllcAddrPartnerMacAddr - The MAC address of the FEP, as
specified with the sdllc partner command.
convSdllcAddrXID - The IDBLK and IDNUM of the SDLC station;
these must match the VTAM configured values
convSdllcAddrState - indicates the state of the SDLLC conversion
convSdllcAddrMaxSdlcFrameSize - the largest I-frame size that
can be sent or received on the SDLC session.
ciscoSnaSdllcMIB MODULE-IDENTITY LAST-UPDATED "9812170000Z" ORGANIZATION "Cisco Systems, Inc." 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 MIB module for objects used to manage SDLLC. Overview of SDLLC conversion MIB MIB description The SDLLC MIB includes read-only configuration and operational information on Cisco's implementation of SDLC to LLC2 media translation. The following example shows the entities managed by the SDLLC MIB. FEP/ == Token == CISCO A == WAN/RSRB == CISCO B == Serial == SDLC Host Ring line station |=============== LLC2 session ============|=== SDLC session ====| In this example configuration, CISCO B is performing the SDLLC conversion, and so we query CISCO B for this MIB. The SDLC device believes it is talking to the host via a direct SDLC session. The host believes it is talking to the SDLC station on the same token ring. CISCO A is also unaware of the SDLLC conversion going on at CISCO B; it just believes it has an RSRB session with its peer CISCO B to bridge two token ring separated by a WAN. So CISCO B is the only agent that can provide the SDLLC conversion details. We can combine this MIB with the CISCO-RSRB-MIB from either CISCO A or CISCO B to get a better picture of the network. This MIB has two tables: convSdllcPortTable has an entry for each serial interface for general SDLLC information on an interface, such as administered virtual MAC addresses and virtual ring and bridge numbers. This table is indexed by ifIndex. convSdllcAddrTable has an entry for each serial interface and SDLC address pair. It contains information specific to an SDLC address on an interface, such as the partner MAC address, XID value, and address state. This table is indexed by ifIndex and convSdllcAddrSdlcAddr (the address of the SDLC station). The above configuration would have a single entry in each table. If CISCO B had two serial lines configured for sdllc conversion, there would be two entries per table. If there were only one serial line, but it was multipoint and supported two sdlc addresses on the other end of the line, there would be a single entry in convSdllcPortTable, and two entries in convSdllcAddrTable. The MIB provides the following information for convSdllcPortTable: convSdllcPortVirtMacAddr - The locally administered MAC addressed assigned to the serial interface. Note that this address must always end in '00'. CISCO B replaces the 00 with the sdlc address of the serial device. For a multipoint configuration with two SDLC stations the llc2 side will 'see' two token ring stations with unique MAC addresses on the sdlc side. convSdllcPortVirtRing - The locally administered token ring number assigned to the serial interface. This gives the serial interface a token ring appearance to the llc2 side of the conversion, so that it appears that it is a token ring on the other side of a bridge. convSdllcPortBridge - The bridge number assigned to CISCO B convSdllcPortLlc2Ring - The token ring number on the LLC2 session side. In this case it is the RSRB virtual ring group number between CISCO A and CISCO B. convSdllcPortLocalAck - indicates whether local acknowledgement of SDLLC sessions is active. convSdllcPortLocalAckState - indicates the state of the local acknowledgement session. convSdllcPortMaxLlc2FrameSize - the largest I-frame size that can be sent or received on the LLC2 session. The MIB provides the following information for convSdllcAddrTable: convSdllcAddrSdlcAddr - The address of the SDLC station. convSdllcAddrPartnerMacAddr - The MAC address of the FEP, as specified with the sdllc partner command. convSdllcAddrXID - The IDBLK and IDNUM of the SDLC station; these must match the VTAM configured values convSdllcAddrState - indicates the state of the SDLLC conversion convSdllcAddrMaxSdlcFrameSize - the largest I-frame size that can be sent or received on the SDLC session. " REVISION "9508210000Z" DESCRIPTION "Minor cleanups to pacify mib compiler." REVISION "9812170000Z" DESCRIPTION "Removed the old description, rewrite to match the MIB structure." ::= { ciscoMgmt 28 }
ciscoSnaSdllcMIB OBJECT IDENTIFIER ::= { ciscoMgmt 28 }
Automatically extracted from Cisco "SNMP v2 MIBs".
ciscoSnaSdllcMIB MODULE-IDENTITY LAST-UPDATED "9812170000Z" ORGANIZATION "Cisco Systems, Inc." 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 MIB module for objects used to manage SDLLC. Overview of SDLLC conversion MIB MIB description The SDLLC MIB includes read-only configuration and operational information on Cisco's implementation of SDLC to LLC2 media translation. The following example shows the entities managed by the SDLLC MIB. FEP/ == Token == CISCO A == WAN/RSRB == CISCO B == Serial == SDLC Host Ring line station |=============== LLC2 session ============|=== SDLC session ====| In this example configuration, CISCO B is performing the SDLLC conversion, and so we query CISCO B for this MIB. The SDLC device believes it is talking to the host via a direct SDLC session. The host believes it is talking to the SDLC station on the same token ring. CISCO A is also unaware of the SDLLC conversion going on at CISCO B; it just believes it has an RSRB session with its peer CISCO B to bridge two token ring separated by a WAN. So CISCO B is the only agent that can provide the SDLLC conversion details. We can combine this MIB with the CISCO-RSRB-MIB from either CISCO A or CISCO B to get a better picture of the network. This MIB has two tables: convSdllcPortTable has an entry for each serial interface for general SDLLC information on an interface, such as administered virtual MAC addresses and virtual ring and bridge numbers. This table is indexed by ifIndex. convSdllcAddrTable has an entry for each serial interface and SDLC address pair. It contains information specific to an SDLC address on an interface, such as the partner MAC address, XID value, and address state. This table is indexed by ifIndex and convSdllcAddrSdlcAddr (the address of the SDLC station). The above configuration would have a single entry in each table. If CISCO B had two serial lines configured for sdllc conversion, there would be two entries per table. If there were only one serial line, but it was multipoint and supported two sdlc addresses on the other end of the line, there would be a single entry in convSdllcPortTable, and two entries in convSdllcAddrTable. The MIB provides the following information for convSdllcPortTable: convSdllcPortVirtMacAddr - The locally administered MAC addressed assigned to the serial interface. Note that this address must always end in '00'. CISCO B replaces the 00 with the sdlc address of the serial device. For a multipoint configuration with two SDLC stations the llc2 side will 'see' two token ring stations with unique MAC addresses on the sdlc side. convSdllcPortVirtRing - The locally administered token ring number assigned to the serial interface. This gives the serial interface a token ring appearance to the llc2 side of the conversion, so that it appears that it is a token ring on the other side of a bridge. convSdllcPortBridge - The bridge number assigned to CISCO B convSdllcPortLlc2Ring - The token ring number on the LLC2 session side. In this case it is the RSRB virtual ring group number between CISCO A and CISCO B. convSdllcPortLocalAck - indicates whether local acknowledgement of SDLLC sessions is active. convSdllcPortLocalAckState - indicates the state of the local acknowledgement session. convSdllcPortMaxLlc2FrameSize - the largest I-frame size that can be sent or received on the LLC2 session. The MIB provides the following information for convSdllcAddrTable: convSdllcAddrSdlcAddr - The address of the SDLC station. convSdllcAddrPartnerMacAddr - The MAC address of the FEP, as specified with the sdllc partner command. convSdllcAddrXID - The IDBLK and IDNUM of the SDLC station; these must match the VTAM configured values convSdllcAddrState - indicates the state of the SDLLC conversion convSdllcAddrMaxSdlcFrameSize - the largest I-frame size that can be sent or received on the SDLC session. " REVISION "9508210000Z" DESCRIPTION "Minor cleanups to pacify mib compiler." REVISION "9812170000Z" DESCRIPTION "Removed the old description, rewrite to match the MIB structure." ::= { ciscoMgmt 28 }
ciscoSnaSdllcMIB MODULE-IDENTITY LAST-UPDATED "9812170000Z" ORGANIZATION "Cisco Systems, Inc." 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 MIB module for objects used to manage SDLLC. Overview of SDLLC conversion MIB MIB description The SDLLC MIB includes read-only configuration and operational information on Cisco's implementation of SDLC to LLC2 media translation. The following example shows the entities managed by the SDLLC MIB. FEP/ == Token == CISCO A == WAN/RSRB == CISCO B == Serial == SDLC Host Ring line station |=============== LLC2 session ============|=== SDLC session ====| In this example configuration, CISCO B is performing the SDLLC conversion, and so we query CISCO B for this MIB. The SDLC device believes it is talking to the host via a direct SDLC session. The host believes it is talking to the SDLC station on the same token ring. CISCO A is also unaware of the SDLLC conversion going on at CISCO B; it just believes it has an RSRB session with its peer CISCO B to bridge two token ring separated by a WAN. So CISCO B is the only agent that can provide the SDLLC conversion details. We can combine this MIB with the CISCO-RSRB-MIB from either CISCO A or CISCO B to get a better picture of the network. This MIB has two tables: convSdllcPortTable has an entry for each serial interface for general SDLLC information on an interface, such as administered virtual MAC addresses and virtual ring and bridge numbers. This table is indexed by ifIndex. convSdllcAddrTable has an entry for each serial interface and SDLC address pair. It contains information specific to an SDLC address on an interface, such as the partner MAC address, XID value, and address state. This table is indexed by ifIndex and convSdllcAddrSdlcAddr (the address of the SDLC station). The above configuration would have a single entry in each table. If CISCO B had two serial lines configured for sdllc conversion, there would be two entries per table. If there were only one serial line, but it was multipoint and supported two sdlc addresses on the other end of the line, there would be a single entry in convSdllcPortTable, and two entries in convSdllcAddrTable. The MIB provides the following information for convSdllcPortTable: convSdllcPortVirtMacAddr - The locally administered MAC addressed assigned to the serial interface. Note that this address must always end in '00'. CISCO B replaces the 00 with the sdlc address of the serial device. For a multipoint configuration with two SDLC stations the llc2 side will 'see' two token ring stations with unique MAC addresses on the sdlc side. convSdllcPortVirtRing - The locally administered token ring number assigned to the serial interface. This gives the serial interface a token ring appearance to the llc2 side of the conversion, so that it appears that it is a token ring on the other side of a bridge. convSdllcPortBridge - The bridge number assigned to CISCO B convSdllcPortLlc2Ring - The token ring number on the LLC2 session side. In this case it is the RSRB virtual ring group number between CISCO A and CISCO B. convSdllcPortLocalAck - indicates whether local acknowledgement of SDLLC sessions is active. convSdllcPortLocalAckState - indicates the state of the local acknowledgement session. convSdllcPortMaxLlc2FrameSize - the largest I-frame size that can be sent or received on the LLC2 session. The MIB provides the following information for convSdllcAddrTable: convSdllcAddrSdlcAddr - The address of the SDLC station. convSdllcAddrPartnerMacAddr - The MAC address of the FEP, as specified with the sdllc partner command. convSdllcAddrXID - The IDBLK and IDNUM of the SDLC station; these must match the VTAM configured values convSdllcAddrState - indicates the state of the SDLLC conversion convSdllcAddrMaxSdlcFrameSize - the largest I-frame size that can be sent or received on the SDLC session. " REVISION "9508210000Z" DESCRIPTION "Minor cleanups to pacify mib compiler." REVISION "9812170000Z" DESCRIPTION "Removed the old description, rewrite to match the MIB structure." ::= { ciscoMgmt 28 }
| OID | Name | Sub children | Sub Nodes Total | Description |
|---|---|---|---|---|
| 1.3.6.1.4.1.9.9.28.1 | convSdllcObjects | 2 | 18 | None |
| 1.3.6.1.4.1.9.9.28.2 | convSdllcNotificationPrefix | 1 | 2 | None |
| 1.3.6.1.4.1.9.9.28.3 | sdllcMibConformance | 2 | 5 | None |
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.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.34 | ciscoCipLanMIB | 2 | 24 | This is the Management Information Base (MIB) module for objects used to manage the cisco internal LAN support in Cisco Mainframe… |
| 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… |
| ... | ||||