The MIB module for management of Cisco specific Data Link
Switching protocol enhancements. DLSw is described in
RFC 1795 and RFC 2024.
DLSw+ Defined
Data link switching Plus (DLSw+) is a means of transporting
Systems Network Architecture (SNA) and NetBIOS traffic over
an IP network. The end systems can attach to the network over
Token Ring, Ethernet, Synchronous Data Link Control
(SDLC) protocol, or Qualified Logical Link Control (QLLC).
DLSw+ switches between diverse media, and locally terminates
the data links, keeping acknowledgments, keepalives, and polling
off of the WAN. Local termination of data links also
eliminates data link control time-outs that can occur during
transient network congestion or when rerouting around failed
links. Finally, DLSw+ provides a mechanism for dynamically
searching a network for SNA or NetBIOS resources and
includes caching algorithms that minimize the broadcast traffic
required.
In this document, DLSw+ routers are referred to as
peers, or partners. The connection between two DLSw+
routers is referred to as a peer connection. A DLSw circuit is
comprised of the data link control connection between the
originating end system and the originating router, the connection
between the two routers (typically a TCP connection), and
the data link control connection between the target router and
the target end system. A single peer connection can carry
multiple circuits.
The transport connection between DLSw+ routers can vary according
to the needs of the network and is not tied to TCP/IP
as the DLSw standard is. Cisco supports four different transport
protocols between DLSw+ routers:
TCP/IP-for transport of SNA and NetBIOS traffic across WANs where
local acknowledgment is required to minimize
unnecessary traffic and prevent data-link control timeouts and
where non-disruptive rerouting around link failures is
critical. This transport option is required when DLSw+ is
operating in DLSw standards mode.
FST/IP-for transport across WANs with an arbitrary topology and
with sufficient bandwidth to accommodate SNA
and NetBIOS traffic. This solution allows for rerouting around
link failures, but recovery may be disruptive depending
on the time required to find an alternate path. This option does
not support local acknowledgment of frames.
Direct-encapsulation for transport across a point-to-point or
Frame Relay connection where the benefits of an
arbitrary topology are not important and where nondisruptive
rerouting around link failures is not required. This option
does not support local acknowledgment of frames.
DLSw Lite-also known as Logical Link Control, Type2 (LLC2)
encapsulation -for transport across a point-to-point
connection (currently only Frame Relay is supported) where
local acknowledgment and reliable transport are
important, but where nondisruptive rerouting around link
failures is not required. DLSw Lite uses RFC 1490
encapsulation of LLC2.
Parsed from file CISCO-DLSW-EXT-MIB.mib
Module: CISCO-DLSW-EXT-MIB
ciscoDlswExtMIB MODULE-IDENTITY
LAST-UPDATED "9703110000Z"
ORGANIZATION "Cisco IBU 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
"The MIB module for management of Cisco specific Data Link
Switching protocol enhancements. DLSw is described in
RFC 1795 and RFC 2024.
DLSw+ Defined
Data link switching Plus (DLSw+) is a means of transporting
Systems Network Architecture (SNA) and NetBIOS traffic over
an IP network. The end systems can attach to the network over
Token Ring, Ethernet, Synchronous Data Link Control
(SDLC) protocol, or Qualified Logical Link Control (QLLC).
DLSw+ switches between diverse media, and locally terminates
the data links, keeping acknowledgments, keepalives, and polling
off of the WAN. Local termination of data links also
eliminates data link control time-outs that can occur during
transient network congestion or when rerouting around failed
links. Finally, DLSw+ provides a mechanism for dynamically
searching a network for SNA or NetBIOS resources and
includes caching algorithms that minimize the broadcast traffic
required.
In this document, DLSw+ routers are referred to as
peers, or partners. The connection between two DLSw+
routers is referred to as a peer connection. A DLSw circuit is
comprised of the data link control connection between the
originating end system and the originating router, the connection
between the two routers (typically a TCP connection), and
the data link control connection between the target router and
the target end system. A single peer connection can carry
multiple circuits.
The transport connection between DLSw+ routers can vary according
to the needs of the network and is not tied to TCP/IP
as the DLSw standard is. Cisco supports four different transport
protocols between DLSw+ routers:
TCP/IP-for transport of SNA and NetBIOS traffic across WANs where
local acknowledgment is required to minimize
unnecessary traffic and prevent data-link control timeouts and
where non-disruptive rerouting around link failures is
critical. This transport option is required when DLSw+ is
operating in DLSw standards mode.
FST/IP-for transport across WANs with an arbitrary topology and
with sufficient bandwidth to accommodate SNA
and NetBIOS traffic. This solution allows for rerouting around
link failures, but recovery may be disruptive depending
on the time required to find an alternate path. This option does
not support local acknowledgment of frames.
Direct-encapsulation for transport across a point-to-point or
Frame Relay connection where the benefits of an
arbitrary topology are not important and where nondisruptive
rerouting around link failures is not required. This option
does not support local acknowledgment of frames.
DLSw Lite-also known as Logical Link Control, Type2 (LLC2)
encapsulation -for transport across a point-to-point
connection (currently only Frame Relay is supported) where
local acknowledgment and reliable transport are
important, but where nondisruptive rerouting around link
failures is not required. DLSw Lite uses RFC 1490
encapsulation of LLC2."
REVISION "9703110000Z"
DESCRIPTION
"Initial version of this MIB module."
View at oid-info.com
The MIB module for management of Cisco specific Data Link
Switching protocol enhancements. DLSw is described in
RFC 1795 and RFC 2024.
DLSw+ Defined
Data link switching Plus (DLSw+) is a means of transporting
Systems Network Architecture (SNA) and NetBIOS traffic over
an IP network. The end systems can attach to the network over
Token Ring, Ethernet, Synchronous Data Link Control
(SDLC) protocol, or Qualified Logical Link Control (QLLC).
DLSw+ switches between diverse media, and locally terminates
the data links, keeping acknowledgments, keepalives, and polling
off of the WAN. Local termination of data links also
eliminates data link control time-outs that can occur during
transient network congestion or when rerouting around failed
links. Finally, DLSw+ provides a mechanism for dynamically
searching a network for SNA or NetBIOS resources and
includes caching algorithms that minimize the broadcast traffic
required.
In this document, DLSw+ routers are referred to as
peers, or partners. The connection between two DLSw+
routers is referred to as a peer connection. A DLSw circuit is
comprised of the data link control connection between the
originating end system and the originating router, the connection
between the two routers (typically a TCP connection), and
the data link control connection between the target router and
the target end system. A single peer connection can carry
multiple circuits.
The transport connection between DLSw+ routers can vary according
to the needs of the network and is not tied to TCP/IP
as the DLSw standard is. Cisco supports four different transport
protocols between DLSw+ routers:
TCP/IP-for transport of SNA and NetBIOS traffic across WANs where
local acknowledgment is required to minimize
unnecessary traffic and prevent data-link control timeouts and
where non-disruptive rerouting around link failures is
critical. This transport option is required when DLSw+ is
operating in DLSw standards mode.
FST/IP-for transport across WANs with an arbitrary topology and
with sufficient bandwidth to accommodate SNA
and NetBIOS traffic. This solution allows for rerouting around
link failures, but recovery may be disruptive depending
on the time required to find an alternate path. This option does
not support local acknowledgment of frames.
Direct-encapsulation for transport across a point-to-point or
Frame Relay connection where the benefits of an
arbitrary topology are not important and where nondisruptive
rerouting around link failures is not required. This option
does not support local acknowledgment of frames.
DLSw Lite-also known as Logical Link Control, Type2 (LLC2)
encapsulation -for transport across a point-to-point
connection (currently only Frame Relay is supported) where
local acknowledgment and reliable transport are
important, but where nondisruptive rerouting around link
failures is not required. DLSw Lite uses RFC 1490
encapsulation of LLC2.
Parsed from file CISCO-DLSW-EXT-MIB.my.txt
Company: None
Module: CISCO-DLSW-EXT-MIB
The MIB module for management of Cisco specific Data Link
Switching protocol enhancements. DLSw is described in
RFC 1795 and RFC 2024.
DLSw+ Defined
Data link switching Plus (DLSw+) is a means of transporting
Systems Network Architecture (SNA) and NetBIOS traffic over
an IP network. The end systems can attach to the network over
Token Ring, Ethernet, Synchronous Data Link Control
(SDLC) protocol, or Qualified Logical Link Control (QLLC).
DLSw+ switches between diverse media, and locally terminates
the data links, keeping acknowledgments, keepalives, and polling
off of the WAN. Local termination of data links also
eliminates data link control time-outs that can occur during
transient network congestion or when rerouting around failed
links. Finally, DLSw+ provides a mechanism for dynamically
searching a network for SNA or NetBIOS resources and
includes caching algorithms that minimize the broadcast traffic
required.
In this document, DLSw+ routers are referred to as
peers, or partners. The connection between two DLSw+
routers is referred to as a peer connection. A DLSw circuit is
comprised of the data link control connection between the
originating end system and the originating router, the connection
between the two routers (typically a TCP connection), and
the data link control connection between the target router and
the target end system. A single peer connection can carry
multiple circuits.
The transport connection between DLSw+ routers can vary according
to the needs of the network and is not tied to TCP/IP
as the DLSw standard is. Cisco supports four different transport
protocols between DLSw+ routers:
TCP/IP-for transport of SNA and NetBIOS traffic across WANs where
local acknowledgment is required to minimize
unnecessary traffic and prevent data-link control timeouts and
where non-disruptive rerouting around link failures is
critical. This transport option is required when DLSw+ is
operating in DLSw standards mode.
FST/IP-for transport across WANs with an arbitrary topology and
with sufficient bandwidth to accommodate SNA
and NetBIOS traffic. This solution allows for rerouting around
link failures, but recovery may be disruptive depending
on the time required to find an alternate path. This option does
not support local acknowledgment of frames.
Direct-encapsulation for transport across a point-to-point or
Frame Relay connection where the benefits of an
arbitrary topology are not important and where nondisruptive
rerouting around link failures is not required. This option
does not support local acknowledgment of frames.
DLSw Lite-also known as Logical Link Control, Type2 (LLC2)
encapsulation -for transport across a point-to-point
connection (currently only Frame Relay is supported) where
local acknowledgment and reliable transport are
important, but where nondisruptive rerouting around link
failures is not required. DLSw Lite uses RFC 1490
encapsulation of LLC2.
ciscoDlswExtMIB MODULE-IDENTITY LAST-UPDATED "9703110000Z" ORGANIZATION "Cisco IBU 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 "The MIB module for management of Cisco specific Data Link Switching protocol enhancements. DLSw is described in RFC 1795 and RFC 2024. DLSw+ Defined Data link switching Plus (DLSw+) is a means of transporting Systems Network Architecture (SNA) and NetBIOS traffic over an IP network. The end systems can attach to the network over Token Ring, Ethernet, Synchronous Data Link Control (SDLC) protocol, or Qualified Logical Link Control (QLLC). DLSw+ switches between diverse media, and locally terminates the data links, keeping acknowledgments, keepalives, and polling off of the WAN. Local termination of data links also eliminates data link control time-outs that can occur during transient network congestion or when rerouting around failed links. Finally, DLSw+ provides a mechanism for dynamically searching a network for SNA or NetBIOS resources and includes caching algorithms that minimize the broadcast traffic required. In this document, DLSw+ routers are referred to as peers, or partners. The connection between two DLSw+ routers is referred to as a peer connection. A DLSw circuit is comprised of the data link control connection between the originating end system and the originating router, the connection between the two routers (typically a TCP connection), and the data link control connection between the target router and the target end system. A single peer connection can carry multiple circuits. The transport connection between DLSw+ routers can vary according to the needs of the network and is not tied to TCP/IP as the DLSw standard is. Cisco supports four different transport protocols between DLSw+ routers: TCP/IP-for transport of SNA and NetBIOS traffic across WANs where local acknowledgment is required to minimize unnecessary traffic and prevent data-link control timeouts and where non-disruptive rerouting around link failures is critical. This transport option is required when DLSw+ is operating in DLSw standards mode. FST/IP-for transport across WANs with an arbitrary topology and with sufficient bandwidth to accommodate SNA and NetBIOS traffic. This solution allows for rerouting around link failures, but recovery may be disruptive depending on the time required to find an alternate path. This option does not support local acknowledgment of frames. Direct-encapsulation for transport across a point-to-point or Frame Relay connection where the benefits of an arbitrary topology are not important and where nondisruptive rerouting around link failures is not required. This option does not support local acknowledgment of frames. DLSw Lite-also known as Logical Link Control, Type2 (LLC2) encapsulation -for transport across a point-to-point connection (currently only Frame Relay is supported) where local acknowledgment and reliable transport are important, but where nondisruptive rerouting around link failures is not required. DLSw Lite uses RFC 1490 encapsulation of LLC2." REVISION "9703110000Z" DESCRIPTION "Initial version of this MIB module." ::= { ciscoMgmt 74 }
ciscoDlswExtMIB OBJECT IDENTIFIER ::= { ciscoMgmt 74 }
Automatically extracted from Cisco "SNMP v2 MIBs".
ciscoDlswExtMIB MODULE-IDENTITY LAST-UPDATED "9703110000Z" ORGANIZATION "Cisco IBU 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 "The MIB module for management of Cisco specific Data Link Switching protocol enhancements. DLSw is described in RFC 1795 and RFC 2024. DLSw+ Defined Data link switching Plus (DLSw+) is a means of transporting Systems Network Architecture (SNA) and NetBIOS traffic over an IP network. The end systems can attach to the network over Token Ring, Ethernet, Synchronous Data Link Control (SDLC) protocol, or Qualified Logical Link Control (QLLC). DLSw+ switches between diverse media, and locally terminates the data links, keeping acknowledgments, keepalives, and polling off of the WAN. Local termination of data links also eliminates data link control time-outs that can occur during transient network congestion or when rerouting around failed links. Finally, DLSw+ provides a mechanism for dynamically searching a network for SNA or NetBIOS resources and includes caching algorithms that minimize the broadcast traffic required. In this document, DLSw+ routers are referred to as peers, or partners. The connection between two DLSw+ routers is referred to as a peer connection. A DLSw circuit is comprised of the data link control connection between the originating end system and the originating router, the connection between the two routers (typically a TCP connection), and the data link control connection between the target router and the target end system. A single peer connection can carry multiple circuits. The transport connection between DLSw+ routers can vary according to the needs of the network and is not tied to TCP/IP as the DLSw standard is. Cisco supports four different transport protocols between DLSw+ routers: TCP/IP-for transport of SNA and NetBIOS traffic across WANs where local acknowledgment is required to minimize unnecessary traffic and prevent data-link control timeouts and where non-disruptive rerouting around link failures is critical. This transport option is required when DLSw+ is operating in DLSw standards mode. FST/IP-for transport across WANs with an arbitrary topology and with sufficient bandwidth to accommodate SNA and NetBIOS traffic. This solution allows for rerouting around link failures, but recovery may be disruptive depending on the time required to find an alternate path. This option does not support local acknowledgment of frames. Direct-encapsulation for transport across a point-to-point or Frame Relay connection where the benefits of an arbitrary topology are not important and where nondisruptive rerouting around link failures is not required. This option does not support local acknowledgment of frames. DLSw Lite-also known as Logical Link Control, Type2 (LLC2) encapsulation -for transport across a point-to-point connection (currently only Frame Relay is supported) where local acknowledgment and reliable transport are important, but where nondisruptive rerouting around link failures is not required. DLSw Lite uses RFC 1490 encapsulation of LLC2." REVISION "9703110000Z" DESCRIPTION "Initial version of this MIB module." ::= { ciscoMgmt 74 }
ciscoDlswExtMIB MODULE-IDENTITY LAST-UPDATED "9703110000Z" ORGANIZATION "Cisco IBU 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 "The MIB module for management of Cisco specific Data Link Switching protocol enhancements. DLSw is described in RFC 1795 and RFC 2024. DLSw+ Defined Data link switching Plus (DLSw+) is a means of transporting Systems Network Architecture (SNA) and NetBIOS traffic over an IP network. The end systems can attach to the network over Token Ring, Ethernet, Synchronous Data Link Control (SDLC) protocol, or Qualified Logical Link Control (QLLC). DLSw+ switches between diverse media, and locally terminates the data links, keeping acknowledgments, keepalives, and polling off of the WAN. Local termination of data links also eliminates data link control time-outs that can occur during transient network congestion or when rerouting around failed links. Finally, DLSw+ provides a mechanism for dynamically searching a network for SNA or NetBIOS resources and includes caching algorithms that minimize the broadcast traffic required. In this document, DLSw+ routers are referred to as peers, or partners. The connection between two DLSw+ routers is referred to as a peer connection. A DLSw circuit is comprised of the data link control connection between the originating end system and the originating router, the connection between the two routers (typically a TCP connection), and the data link control connection between the target router and the target end system. A single peer connection can carry multiple circuits. The transport connection between DLSw+ routers can vary according to the needs of the network and is not tied to TCP/IP as the DLSw standard is. Cisco supports four different transport protocols between DLSw+ routers: TCP/IP-for transport of SNA and NetBIOS traffic across WANs where local acknowledgment is required to minimize unnecessary traffic and prevent data-link control timeouts and where non-disruptive rerouting around link failures is critical. This transport option is required when DLSw+ is operating in DLSw standards mode. FST/IP-for transport across WANs with an arbitrary topology and with sufficient bandwidth to accommodate SNA and NetBIOS traffic. This solution allows for rerouting around link failures, but recovery may be disruptive depending on the time required to find an alternate path. This option does not support local acknowledgment of frames. Direct-encapsulation for transport across a point-to-point or Frame Relay connection where the benefits of an arbitrary topology are not important and where nondisruptive rerouting around link failures is not required. This option does not support local acknowledgment of frames. DLSw Lite-also known as Logical Link Control, Type2 (LLC2) encapsulation -for transport across a point-to-point connection (currently only Frame Relay is supported) where local acknowledgment and reliable transport are important, but where nondisruptive rerouting around link failures is not required. DLSw Lite uses RFC 1490 encapsulation of LLC2." REVISION "9703110000Z" DESCRIPTION "Initial version of this MIB module." ::= { ciscoMgmt 74 }
| OID | Name | Sub children | Sub Nodes Total | Description |
|---|---|---|---|---|
| 1.3.6.1.4.1.9.9.74.1 | ciscoDlswExtMIBObjects | 7 | 116 | None |
| 1.3.6.1.4.1.9.9.74.2 | cdeTrapsPrefix | 1 | 3 | None |
| 1.3.6.1.4.1.9.9.74.3 | cdeMIBConformance | 2 | 12 | 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.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.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.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… |
| 1.3.6.1.4.1.9.9.85 | ciscoCasIfMIB | 2 | 119 | Channel Associated Signal Interface MIB module. This MIB manages the generic CAS (Channel Associated Signal)or DS0 clear channel … |
| 1.3.6.1.4.1.9.9.86 | ciscoDspMgmtMIB | 4 | 141 | ciscoDspMgmtMIB MODULE-IDENTITY LAST-UPDATED "200008140000Z" ORGANIZATION "Cisco Systems, Inc." CONTACT-INFO " Cisco Systems Cu… |
| 1.3.6.1.4.1.9.9.87 | ciscoC2900MIB | 3 | 133 | The MIB module for Catalyst 2900 enterprise specific information |
| 1.3.6.1.4.1.9.9.88 | ciscoAtmExtMIB | 3 | 50 | ciscoAtmExtMIB MODULE-IDENTITY LAST-UPDATED "9706200000Z" ORGANIZATION "Cisco Systems, Inc." CONTACT-INFO " Cisco Systems Custo… |
| 1.3.6.1.4.1.9.9.89 | csCugMIB | 2 | 24 | This MIB module is for closed user group support (virtual private networks). |
| 1.3.6.1.4.1.9.9.91 | entitySensorMIB, ciscoEntitySensorMIB | 3 | 42 | The CISCO-ENTITY-SENSOR-MIB is used to monitor the values of sensors in the Entity-MIB (RFC 2037) entPhysicalTable. |
| 1.3.6.1.4.1.9.9.92 | ciscoEntityAssetMIB | 3 | 29 | Monitor the asset information of items in the ENTITY-MIB (RFC 2037) entPhysical table. |
| 1.3.6.1.4.1.9.9.94 | ciscoAtmPvcMIB | 2 | 19 | PVC's (Permanent Virtual Channel) can carry bridged PDUs (BPDUs) using the encapsulation method detailed in RFC1483. This is an alt… |
| 1.3.6.1.4.1.9.9.95 | ciscoAlpsMIB | 3 | 222 | The MIB module for Airline Protocol Support. ************************************************************** * … |
| 1.3.6.1.4.1.9.9.96 | ciscoConfigCopyMIB | 3 | 40 | This MIB facilitates writing of configuration files of an SNMP Agent running Cisco's IOS in the following ways: to and from the n… |
| 1.3.6.1.4.1.9.9.97 | ciscoSwitchEngineMIB | 3 | 385 | This MIB module defines management objects for Cisco Layer 2/3 switches. These devices may either have a single (central) switch… |
| 1.3.6.1.4.1.9.9.98 | ciscoPagpMIB | 2 | 52 | The MIB module for configuration of Fast Etherchannel and the operation of the Port Aggregation Protocol (PAgP). These features a… |
| 1.3.6.1.4.1.9.9.99 | ciscoLocalDirectorMIB | 3 | 88 | The MIB module to view information about LocalDirector. The Cisco LocalDirector is a device designed for the purpose of load balan… |
| 1.3.6.1.4.1.9.9.101 | ciscoSwitchCgmpMIB | 2 | 18 | Switch-side Cisco Group Management Protocol MIB for Layer 2 Switch devices. |
| 1.3.6.1.4.1.9.9.102 | ciscoMediaMailDialControlMIB | 2 | 63 | This MIB module enhances the IETF Dial Control MIB (RFC2128) for providing management of dial peers on both a circuit-switched te… |
| 1.3.6.1.4.1.9.9.103 | ciscoRmonConfigMIB | 3 | 123 | This module defines configuration extensions for some of the IETF RMON MIBs. The following terms are used throughout this MIB: A S… |
| 1.3.6.1.4.1.9.9.105 | ciscoC8500RedundancyMIB | 3 | 49 | This MIB allows management of redundancy of CPU and switch cards for the Catalyst 8540 switch, and other products with similar im… |
| 1.3.6.1.4.1.9.9.106 | ciscoHsrpMIB | 3 | 38 | ciscoHsrpMIB MODULE-IDENTITY LAST-UPDATED "9808030000Z" ORGANIZATION "Cisco Systems, Inc." CONTACT-INFO " Cisco Systems Custome… |
| 1.3.6.1.4.1.9.9.107 | ciscoHsrpExtMIB | 2 | 36 | ciscoHsrpExtMIB MODULE-IDENTITY LAST-UPDATED "9808030000Z" ORGANIZATION "Cisco Systems, Inc." CONTACT-INFO " Cisco Systems Cust… |
| 1.3.6.1.4.1.9.9.109 | ciscoProcessMIB | 3 | 187 | The MIB module to describe active system processes. |
| 1.3.6.1.4.1.9.9.110 | ciscoAtmSwitchFrRmMIB | 3 | 30 | This MIB module describes a set of objects used for switch Resource Management (RM) for Frame Relay/Frame based User-to-Network (… |
| 1.3.6.1.4.1.9.9.112 | ciscoAtmSwitchFrIwfMIB | 2 | 109 | A MIB module for managing Frame Relay to ATM interworking connections, and Frame Relay to Frame Relay switched connections via an… |
| 1.3.6.1.4.1.9.9.113 | ciscoCarMIB | 2 | 36 | Cisco CAR MIB - Overview Cisco Weighted Rate-limit, known as Commited Access Rate (CAR), is a traffic control method which uses a… |
| 1.3.6.1.4.1.9.9.114 | ciscoCableSpectrumMIB | 3 | 162 | This is the MIB Module for Cable Spectrum Management for DOCSIS-compliant Cable Modem Termination Systems (CMTS). Spectrum manage… |
| 1.3.6.1.4.1.9.9.115 | ciscoCasaFaMIB | 3 | 78 | This MIB module in conjunction with the CISCO-CASA-MIB, defines the SNMP management information base for managing the Cisco Appli… |
| 1.3.6.1.4.1.9.9.116 | ciscoDocsExtMIB | 3 | 235 | This is the MIB module for the Cisco specific extension objects of Data Over Cable Service, Radio Frequency interface. There is … |
| 1.3.6.1.4.1.9.9.117 | ciscoEntityFRUControlMIB | 3 | 147 | The CISCO-ENTITY-FRU-CONTROL-MIB is used to monitor and configure operational status of Field Replaceable Units (FRUs) and other … |
| 1.3.6.1.4.1.9.9.118 | ciscoUdldpMIB | 3 | 51 | Cisco Uni Direction Link Detection Protocol MIB |
| 1.3.6.1.4.1.9.9.120 | ciscoNetworkRegistrarMIB | 3 | 125 | MIB for Cisco Network Registrar (CNR). |
| 1.3.6.1.4.1.9.9.121 | ciscoAtmNetworkClockMIB | 3 | 53 | The MIB module for management of network clock distribution and the Network Clock Distribution Protocol (NCDP) in Cisco de… |
| 1.3.6.1.4.1.9.9.122 | ciscoCasaMIB | 3 | 78 | This MIB contains the basic objects for managing a Cisco Appliance Services Architecture (CASA) Entity. A CASA Entity can be a Ma… |
| 1.3.6.1.4.1.9.9.124 | ciscoCallResourcePoolMIB | 3 | 114 | The MIB module for call resource pool management. This MIB supports the resource pool manager feature of CISCO IOS. This feature … |
| ... | ||||