This is the MIB module for objects used to manage RSRB.
Overview of remote source-route bridging (RSRB) management and MIB
MIB description
The RSRB MIB will include the following managed entities:
1) Virtual Rings
2) Remote Peers
3) Associated Token Rings
The goal of this MIB to to allow a management stations to
display the attributes of the local-remote RSRB peer relationship.
The following example configuration will show how the RSRB MIB can
be used to manage RSRB.
== Token Ring == CISCO A == IP Network/ == CISCO B == Token Ring
Virtual Ring
Both CISCO A and CISCO B are RSRB peers, having the same virtual ring
number. In this example information will be gatherered from CISCO A
(the local peer), and CISCO B is considered to be CISCO A's remote peer.
The first table is the virtual ring table. There is one entry for
each RSRB virtual ring the router is defined on. The fields included
in this table include
* the virtual ring number, or index
* the IP address used by the router
* the maximum outbound queue size for each RSRB remote peer
In this example the table has a single entry since CISCO A only belongs
to one RSRB virtual ring.
The next table is for each remote peer in the virtual ring. There
can be multiple RSRB remote peers. The remote peer information includes:
* an internally generated (not configured) index into the table
* the type of data encapsulation with the remote peer
* identification of how to get to the remote peer; either an IP address
or an interface index, depending upon the encapsulation type
* the state of the remote peer
* various statistics (bytes and packets sent and received, explorers
generated, outbound queue size, and packets dropped
* whether local acknowledgment is used with the remote peer
* the RSRB version of the peer
In this example there would be just one remote peer table entry,
for CISCO B.
The last table is for the real local and remote token rings associated
with the RSRB virtual ring, that this router has either had configured
or learned about dynamically. The ring information includes:
* the token ring number (index)
* the bridge number connecting the real ring to the virtual ring
* the ring entry type
* the local or remote routers mac address on the interface to the ring
* the local router's interface index, or the remote router's IP address,
depending on if this is a local or remote ring
* number of packets forwarded by the local router onto this ring
In this example CISCO A would have two ring entries: one for the local
ring it is connected to, and one for the ring CISCO B is a part of.
A management application can construct a virtual ring view either by
collecting MIB information from all routers and grouping those in the
same virtual ring together, or beginning with a particular router or
routers, and collecting MIB information about other peer routers.
Parsed from file CISCO-RSRB-MIB.mib
Module: CISCO-RSRB-MIB
ciscoRsrbMIB MODULE-IDENTITY
LAST-UPDATED "9508210000Z"
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 RSRB.
Overview of remote source-route bridging (RSRB) management and MIB
MIB description
The RSRB MIB will include the following managed entities:
1) Virtual Rings
2) Remote Peers
3) Associated Token Rings
The goal of this MIB to to allow a management stations to
display the attributes of the local-remote RSRB peer relationship.
The following example configuration will show how the RSRB MIB can
be used to manage RSRB.
== Token Ring == CISCO A == IP Network/ == CISCO B == Token Ring
Virtual Ring
Both CISCO A and CISCO B are RSRB peers, having the same virtual ring
number. In this example information will be gatherered from CISCO A
(the local peer), and CISCO B is considered to be CISCO As remote peer.
The first table is the virtual ring table. There is one entry for
each RSRB virtual ring the router is defined on. The fields included
in this table include
* the virtual ring number, or index
* the IP address used by the router
* the maximum outbound queue size for each RSRB remote peer
In this example the table has a single entry since CISCO A only belongs
to one RSRB virtual ring.
The next table is for each remote peer in the virtual ring. There
can be multiple RSRB remote peers. The remote peer information includes:
* an internally generated (not configured) index into the table
* the type of data encapsulation with the remote peer
* identification of how to get to the remote peer; either an IP address
or an interface index, depending upon the encapsulation type
* the state of the remote peer
* various statistics (bytes and packets sent and received, explorers
generated, outbound queue size, and packets dropped
* whether local acknowledgment is used with the remote peer
* the RSRB version of the peer
In this example there would be just one remote peer table entry,
for CISCO B.
The last table is for the real local and remote token rings associated
with the RSRB virtual ring, that this router has either had configured
or learned about dynamically. The ring information includes:
* the token ring number (index)
* the bridge number connecting the real ring to the virtual ring
* the ring entry type
* the local or remote routers mac address on the interface to the ring
* the local routers interface index, or the remote routers IP address,
depending on if this is a local or remote ring
* number of packets forwarded by the local router onto this ring
In this example CISCO A would have two ring entries: one for the local
ring it is connected to, and one for the ring CISCO B is a part of.
A management application can construct a virtual ring view either by
collecting MIB information from all routers and grouping those in the
same virtual ring together, or beginning with a particular router or
routers, and collecting MIB information about other peer routers.
"
REVISION "9508210000Z"
DESCRIPTION
"Specify a correct (non-negative) range for several
index objects."
View at oid-info.com
This is the MIB module for objects used to manage RSRB.
Overview of remote source-route bridging (RSRB) management and MIB
MIB description
The RSRB MIB will include the following managed entities:
1) Virtual Rings
2) Remote Peers
3) Associated Token Rings
The goal of this MIB to to allow a management stations to
display the attributes of the local-remote RSRB peer relationship.
The following example configuration will show how the RSRB MIB can
be used to manage RSRB.
== Token Ring == CISCO A == IP Network/ == CISCO B == Token Ring
Virtual Ring
Both CISCO A and CISCO B are RSRB peers, having the same virtual ring
number. In this example information will be gatherered from CISCO A
(the local peer), and CISCO B is considered to be CISCO A's remote peer.
The first table is the virtual ring table. There is one entry for
each RSRB virtual ring the router is defined on. The fields included
in this table include
* the virtual ring number, or index
* the IP address used by the router
* the maximum outbound queue size for each RSRB remote peer
In this example the table has a single entry since CISCO A only belongs
to one RSRB virtual ring.
The next table is for each remote peer in the virtual ring. There
can be multiple RSRB remote peers. The remote peer information includes:
* an internally generated (not configured) index into the table
* the type of data encapsulation with the remote peer
* identification of how to get to the remote peer; either an IP address
or an interface index, depending upon the encapsulation type
* the state of the remote peer
* various statistics (bytes and packets sent and received, explorers
generated, outbound queue size, and packets dropped
* whether local acknowledgment is used with the remote peer
* the RSRB version of the peer
In this example there would be just one remote peer table entry,
for CISCO B.
The last table is for the real local and remote token rings associated
with the RSRB virtual ring, that this router has either had configured
or learned about dynamically. The ring information includes:
* the token ring number (index)
* the bridge number connecting the real ring to the virtual ring
* the ring entry type
* the local or remote routers mac address on the interface to the ring
* the local router's interface index, or the remote router's IP address,
depending on if this is a local or remote ring
* number of packets forwarded by the local router onto this ring
In this example CISCO A would have two ring entries: one for the local
ring it is connected to, and one for the ring CISCO B is a part of.
A management application can construct a virtual ring view either by
collecting MIB information from all routers and grouping those in the
same virtual ring together, or beginning with a particular router or
routers, and collecting MIB information about other peer routers.
Parsed from file CISCO-RSRB-MIB.my.txt
Company: None
Module: CISCO-RSRB-MIB
This is the MIB module for objects used to manage RSRB.
Overview of remote source-route bridging (RSRB) management and MIB
MIB description
The RSRB MIB will include the following managed entities:
1) Virtual Rings
2) Remote Peers
3) Associated Token Rings
The goal of this MIB to to allow a management stations to
display the attributes of the local-remote RSRB peer relationship.
The following example configuration will show how the RSRB MIB can
be used to manage RSRB.
== Token Ring == CISCO A == IP Network/ == CISCO B == Token Ring
Virtual Ring
Both CISCO A and CISCO B are RSRB peers, having the same virtual ring
number. In this example information will be gatherered from CISCO A
(the local peer), and CISCO B is considered to be CISCO A's remote peer.
The first table is the virtual ring table. There is one entry for
each RSRB virtual ring the router is defined on. The fields included
in this table include
* the virtual ring number, or index
* the IP address used by the router
* the maximum outbound queue size for each RSRB remote peer
In this example the table has a single entry since CISCO A only belongs
to one RSRB virtual ring.
The next table is for each remote peer in the virtual ring. There
can be multiple RSRB remote peers. The remote peer information includes:
* an internally generated (not configured) index into the table
* the type of data encapsulation with the remote peer
* identification of how to get to the remote peer; either an IP address
or an interface index, depending upon the encapsulation type
* the state of the remote peer
* various statistics (bytes and packets sent and received, explorers
generated, outbound queue size, and packets dropped
* whether local acknowledgment is used with the remote peer
* the RSRB version of the peer
In this example there would be just one remote peer table entry,
for CISCO B.
The last table is for the real local and remote token rings associated
with the RSRB virtual ring, that this router has either had configured
or learned about dynamically. The ring information includes:
* the token ring number (index)
* the bridge number connecting the real ring to the virtual ring
* the ring entry type
* the local or remote routers mac address on the interface to the ring
* the local router's interface index, or the remote router's IP address,
depending on if this is a local or remote ring
* number of packets forwarded by the local router onto this ring
In this example CISCO A would have two ring entries: one for the local
ring it is connected to, and one for the ring CISCO B is a part of.
A management application can construct a virtual ring view either by
collecting MIB information from all routers and grouping those in the
same virtual ring together, or beginning with a particular router or
routers, and collecting MIB information about other peer routers.
ciscoRsrbMIB MODULE-IDENTITY LAST-UPDATED "9508210000Z" 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 RSRB. Overview of remote source-route bridging (RSRB) management and MIB MIB description The RSRB MIB will include the following managed entities: 1) Virtual Rings 2) Remote Peers 3) Associated Token Rings The goal of this MIB to to allow a management stations to display the attributes of the local-remote RSRB peer relationship. The following example configuration will show how the RSRB MIB can be used to manage RSRB. == Token Ring == CISCO A == IP Network/ == CISCO B == Token Ring Virtual Ring Both CISCO A and CISCO B are RSRB peers, having the same virtual ring number. In this example information will be gatherered from CISCO A (the local peer), and CISCO B is considered to be CISCO A's remote peer. The first table is the virtual ring table. There is one entry for each RSRB virtual ring the router is defined on. The fields included in this table include * the virtual ring number, or index * the IP address used by the router * the maximum outbound queue size for each RSRB remote peer In this example the table has a single entry since CISCO A only belongs to one RSRB virtual ring. The next table is for each remote peer in the virtual ring. There can be multiple RSRB remote peers. The remote peer information includes: * an internally generated (not configured) index into the table * the type of data encapsulation with the remote peer * identification of how to get to the remote peer; either an IP address or an interface index, depending upon the encapsulation type * the state of the remote peer * various statistics (bytes and packets sent and received, explorers generated, outbound queue size, and packets dropped * whether local acknowledgment is used with the remote peer * the RSRB version of the peer In this example there would be just one remote peer table entry, for CISCO B. The last table is for the real local and remote token rings associated with the RSRB virtual ring, that this router has either had configured or learned about dynamically. The ring information includes: * the token ring number (index) * the bridge number connecting the real ring to the virtual ring * the ring entry type * the local or remote routers mac address on the interface to the ring * the local router's interface index, or the remote router's IP address, depending on if this is a local or remote ring * number of packets forwarded by the local router onto this ring In this example CISCO A would have two ring entries: one for the local ring it is connected to, and one for the ring CISCO B is a part of. A management application can construct a virtual ring view either by collecting MIB information from all routers and grouping those in the same virtual ring together, or beginning with a particular router or routers, and collecting MIB information about other peer routers. " REVISION "9508210000Z" DESCRIPTION "Specify a correct (non-negative) range for several index objects." ::= { ciscoMgmt 29 }
ciscoRsrbMIB OBJECT IDENTIFIER ::= { ciscoMgmt 29 }
Automatically extracted from Cisco "SNMP v2 MIBs".
ciscoRsrbMIB MODULE-IDENTITY LAST-UPDATED "9508210000Z" 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 RSRB. Overview of remote source-route bridging (RSRB) management and MIB MIB description The RSRB MIB will include the following managed entities: 1) Virtual Rings 2) Remote Peers 3) Associated Token Rings The goal of this MIB to to allow a management stations to display the attributes of the local-remote RSRB peer relationship. The following example configuration will show how the RSRB MIB can be used to manage RSRB. == Token Ring == CISCO A == IP Network/ == CISCO B == Token Ring Virtual Ring Both CISCO A and CISCO B are RSRB peers, having the same virtual ring number. In this example information will be gatherered from CISCO A (the local peer), and CISCO B is considered to be CISCO A's remote peer. The first table is the virtual ring table. There is one entry for each RSRB virtual ring the router is defined on. The fields included in this table include * the virtual ring number, or index * the IP address used by the router * the maximum outbound queue size for each RSRB remote peer In this example the table has a single entry since CISCO A only belongs to one RSRB virtual ring. The next table is for each remote peer in the virtual ring. There can be multiple RSRB remote peers. The remote peer information includes: * an internally generated (not configured) index into the table * the type of data encapsulation with the remote peer * identification of how to get to the remote peer; either an IP address or an interface index, depending upon the encapsulation type * the state of the remote peer * various statistics (bytes and packets sent and received, explorers generated, outbound queue size, and packets dropped * whether local acknowledgment is used with the remote peer * the RSRB version of the peer In this example there would be just one remote peer table entry, for CISCO B. The last table is for the real local and remote token rings associated with the RSRB virtual ring, that this router has either had configured or learned about dynamically. The ring information includes: * the token ring number (index) * the bridge number connecting the real ring to the virtual ring * the ring entry type * the local or remote routers mac address on the interface to the ring * the local router's interface index, or the remote router's IP address, depending on if this is a local or remote ring * number of packets forwarded by the local router onto this ring In this example CISCO A would have two ring entries: one for the local ring it is connected to, and one for the ring CISCO B is a part of. A management application can construct a virtual ring view either by collecting MIB information from all routers and grouping those in the same virtual ring together, or beginning with a particular router or routers, and collecting MIB information about other peer routers. " REVISION "9508210000Z" DESCRIPTION "Specify a correct (non-negative) range for several index objects." ::= { ciscoMgmt 29 }
ciscoRsrbMIB MODULE-IDENTITY LAST-UPDATED "9508210000Z" 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 RSRB. Overview of remote source-route bridging (RSRB) management and MIB MIB description The RSRB MIB will include the following managed entities: 1) Virtual Rings 2) Remote Peers 3) Associated Token Rings The goal of this MIB to to allow a management stations to display the attributes of the local-remote RSRB peer relationship. The following example configuration will show how the RSRB MIB can be used to manage RSRB. == Token Ring == CISCO A == IP Network/ == CISCO B == Token Ring Virtual Ring Both CISCO A and CISCO B are RSRB peers, having the same virtual ring number. In this example information will be gatherered from CISCO A (the local peer), and CISCO B is considered to be CISCO A's remote peer. The first table is the virtual ring table. There is one entry for each RSRB virtual ring the router is defined on. The fields included in this table include * the virtual ring number, or index * the IP address used by the router * the maximum outbound queue size for each RSRB remote peer In this example the table has a single entry since CISCO A only belongs to one RSRB virtual ring. The next table is for each remote peer in the virtual ring. There can be multiple RSRB remote peers. The remote peer information includes: * an internally generated (not configured) index into the table * the type of data encapsulation with the remote peer * identification of how to get to the remote peer; either an IP address or an interface index, depending upon the encapsulation type * the state of the remote peer * various statistics (bytes and packets sent and received, explorers generated, outbound queue size, and packets dropped * whether local acknowledgment is used with the remote peer * the RSRB version of the peer In this example there would be just one remote peer table entry, for CISCO B. The last table is for the real local and remote token rings associated with the RSRB virtual ring, that this router has either had configured or learned about dynamically. The ring information includes: * the token ring number (index) * the bridge number connecting the real ring to the virtual ring * the ring entry type * the local or remote routers mac address on the interface to the ring * the local router's interface index, or the remote router's IP address, depending on if this is a local or remote ring * number of packets forwarded by the local router onto this ring In this example CISCO A would have two ring entries: one for the local ring it is connected to, and one for the ring CISCO B is a part of. A management application can construct a virtual ring view either by collecting MIB information from all routers and grouping those in the same virtual ring together, or beginning with a particular router or routers, and collecting MIB information about other peer routers. " REVISION "9508210000Z" DESCRIPTION "Specify a correct (non-negative) range for several index objects." ::= { ciscoMgmt 29 }
| OID | Name | Sub children | Sub Nodes Total | Description |
|---|---|---|---|---|
| 1.3.6.1.4.1.9.9.29.1 | rsrbObjects | 3 | 34 | None |
| 1.3.6.1.4.1.9.9.29.2 | rsrbNotificationPrefix | 1 | 2 | None |
| 1.3.6.1.4.1.9.9.29.3 | rsrbMibConformance | 2 | 6 | 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.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.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… |
| ... | ||||