Reference record for OID 1.3.6.1.4.1.9.9.370

Parent
1.3.6.1.4.1.9.9 (ciscoMgmt)
Node code
370
Node name
ciscoSslProxyMIB
Numeric OID
1.3.6.1.4.1.9.9.370
URN notation
urn:oid:1.3.6.1.4.1.9.9.370
Type
OBJECT IDENTIFIER
ASN.1 notation

{1 3 6 1 4 1 9 9 370}

  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprise(1) cisco(9) ciscoMgmt(9) ciscoSslProxyMIB(370)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprise(1) me1200(9) ciscoMgmt(9) ciscoSslProxyMIB(370)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprises(1) cisco(9) ciscoMgmt(9) ciscoSslProxyMIB(370)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprises(1) me1200(9) ciscoMgmt(9) ciscoSslProxyMIB(370)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) ldap-enterprise(1) cisco(9) ciscoMgmt(9) ciscoSslProxyMIB(370)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) ldap-enterprise(1) me1200(9) ciscoMgmt(9) ciscoSslProxyMIB(370)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) vendor-objects(1) cisco(9) ciscoMgmt(9) ciscoSslProxyMIB(370)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) vendor-objects(1) me1200(9) ciscoMgmt(9) ciscoSslProxyMIB(370)}
  • {iso(1) org(3) dod(6) internet(1) private(4) enterprise(1) cisco(9) ciscoMgmt(9) ciscoSslProxyMIB(370)}
  • {iso(1) org(3) dod(6) internet(1) private(4) enterprise(1) me1200(9) ciscoMgmt(9) ciscoSslProxyMIB(370)}
  • {iso(1) org(3) dod(6) internet(1) private(4) enterprises(1) cisco(9) ciscoMgmt(9) ciscoSslProxyMIB(370)}
  • {iso(1) org(3) dod(6) internet(1) private(4) enterprises(1) me1200(9) ciscoMgmt(9) ciscoSslProxyMIB(370)}
  • {iso(1) org(3) dod(6) internet(1) private(4) ldap-enterprise(1) cisco(9) ciscoMgmt(9) ciscoSslProxyMIB(370)}
  • {iso(1) org(3) dod(6) internet(1) private(4) ldap-enterprise(1) me1200(9) ciscoMgmt(9) ciscoSslProxyMIB(370)}
  • {iso(1) org(3) dod(6) internet(1) private(4) vendor-objects(1) cisco(9) ciscoMgmt(9) ciscoSslProxyMIB(370)}
  • {iso(1) org(3) dod(6) internet(1) private(4) vendor-objects(1) me1200(9) ciscoMgmt(9) ciscoSslProxyMIB(370)}
  • Additional combinations skipped.
OID-IRI notation
  • /1/3/6/1/4/1/9/9/370
  • /ISO/Identified-Organization/6/1/4/1/9/9/370
  • /ISO/3/6/1/4/1/9/9/370
Named path variants
  • /iso/identified-organization/dod/internet/private/enterprise/cisco/ciscoMgmt/ciscoSslProxyMIB
  • /iso/identified-organization/dod/internet/private/enterprise/me1200/ciscoMgmt/ciscoSslProxyMIB
  • /iso/identified-organization/dod/internet/private/enterprise/Cisco/ciscoMgmt/ciscoSslProxyMIB
  • /iso/identified-organization/dod/internet/private/enterprises/cisco/ciscoMgmt/ciscoSslProxyMIB
  • /iso/identified-organization/dod/internet/private/enterprises/me1200/ciscoMgmt/ciscoSslProxyMIB
  • /iso/identified-organization/dod/internet/private/enterprises/Cisco/ciscoMgmt/ciscoSslProxyMIB
  • /iso/identified-organization/dod/internet/private/ldap-enterprise/cisco/ciscoMgmt/ciscoSslProxyMIB
  • /iso/identified-organization/dod/internet/private/ldap-enterprise/me1200/ciscoMgmt/ciscoSslProxyMIB
  • /iso/identified-organization/dod/internet/private/ldap-enterprise/Cisco/ciscoMgmt/ciscoSslProxyMIB
  • /iso/identified-organization/dod/internet/private/vendor-objects/cisco/ciscoMgmt/ciscoSslProxyMIB
  • /iso/identified-organization/dod/internet/private/vendor-objects/me1200/ciscoMgmt/ciscoSslProxyMIB
  • /iso/identified-organization/dod/internet/private/vendor-objects/Cisco/ciscoMgmt/ciscoSslProxyMIB
  • /iso/org/dod/internet/private/enterprise/cisco/ciscoMgmt/ciscoSslProxyMIB
  • /iso/org/dod/internet/private/enterprise/me1200/ciscoMgmt/ciscoSslProxyMIB
  • /iso/org/dod/internet/private/enterprise/Cisco/ciscoMgmt/ciscoSslProxyMIB
  • /iso/org/dod/internet/private/enterprises/cisco/ciscoMgmt/ciscoSslProxyMIB
  • Additional combinations skipped.

Descriptions

Descriptions may differ between sources. The primary description is shown first.

Primary description: Circitor

This MIB module is for managing a Secure Socket Layer
(SSL) Proxy device which terminates and accelarates
SSL and Transport Layer Security (TLS) transactions.

The proxy device can act as a SSL server or a SSL client
depending on the configuration and the application.

In one application, the device acts as a proxy SSL
server. It terminates SSL handshakes and TCP connections
initiated by SSL clients. The device is configured with
a key and a certificate bearing the identity of the SSL
server. The device uses this identity to establish the
SSL session on behalf of the server, offloading the key
establishment and data encryption and decryption work.

After the SSL session has been successfully established
between the client and the proxy device, the device
starts to receive and decrypt the encrypted data sent
from the client and forward to the server. The device
forwards the clear data to the server on a backend
connection. Clear data sent from the server is encrypted
by the proxy device before it is forwarded to the SSL
client.

Optionally, the proxy device is configured to reencrypt
the decrypted data sent from the client to the server.
The proxy device acts as a SSL client to initiate a SSL
session to the server. The decrypted data is encrypted
within this SSL session to be forwarded to the server.
The encrypted data sent from the server to the device
is decrypted and then reencrypted before it is
forwarded to the client.

In another application, the proxy device forwards data
generated by one or more sources to the destination
via a SSL session. The proxy device acts as a SSL
client and intiates a SSL session to the next hop
device. When data is received from the source, the
proxy device forwards the data to the next hop using
the SSL session. The next hop can continue to forward
the data if it is not the destination.

The proxy device supports a number of proxy services.
Each proxy service defines the role of the proxy device,
whether it acts as a SSL server or a SSL client. The
rest of the configuration include cryptographic and
protocol parameters.

This MIB is used for monitoring the configuration,
statuses and statistics of the proxy services and
the protocols including TCP, SSL and TLS.

Parsed from file CISCO-SSL-PROXY-MIB.mib
Module: CISCO-SSL-PROXY-MIB

Source file: Download CISCO-SSL-PROXY-MIB.mib

Publisher path: Mibs; 117,360 bytes

Alternative description: Cisco

This MIB module is for managing a Secure Socket Layer
(SSL) Proxy device which terminates and accelarates
SSL and Transport Layer Security (TLS) transactions.

The proxy device can act as a SSL server or a SSL client
depending on the configuration and the application.

In one application, the device acts as a proxy SSL
server. It terminates SSL handshakes and TCP connections
initiated by SSL clients. The device is configured with
a key and a certificate bearing the identity of the SSL
server. The device uses this identity to establish the
SSL session on behalf of the server, offloading the key
establishment and data encryption and decryption work.

After the SSL session has been successfully established
between the client and the proxy device, the device
starts to receive and decrypt the encrypted data sent
from the client and forward to the server. The device
forwards the clear data to the server on a backend
connection. Clear data sent from the server is encrypted
by the proxy device before it is forwarded to the SSL
client.

Optionally, the proxy device is configured to reencrypt
the decrypted data sent from the client to the server.
The proxy device acts as a SSL client to initiate a SSL
session to the server. The decrypted data is encrypted
within this SSL session to be forwarded to the server.
The encrypted data sent from the server to the device
is decrypted and then reencrypted before it is
forwarded to the client.

In another application, the proxy device forwards data
generated by one or more sources to the destination
via a SSL session. The proxy device acts as a SSL
client and intiates a SSL session to the next hop
device. When data is received from the source, the
proxy device forwards the data to the next hop using
the SSL session. The next hop can continue to forward
the data if it is not the destination.

The proxy device supports a number of proxy services.
Each proxy service defines the role of the proxy device,
whether it acts as a SSL server or a SSL client. The
rest of the configuration include cryptographic and
protocol parameters.

This MIB is used for monitoring the configuration,
statuses and statistics of the proxy services and
the protocols including TCP, SSL and TLS.

Source file: Download CISCO-SSL-PROXY-MIB.my · Publisher's file

Copy from Netdisco; File: cisco/CISCO-SSL-PROXY-MIB.my; 138,661 bytes

Vendor MIB copy from the Netdisco archive.

Related source files and packages:

Source file: Download CISCO-SSL-PROXY-MIB · Publisher's file

Copy from Observium Community; File: cisco/CISCO-SSL-PROXY-MIB; 138,661 bytes

Vendor MIB copy from the Observium Community archive. Cisco support.

Related source files and packages:

Source file: Download CISCO-SSL-PROXY-MIB.my · Publisher's file

Publisher path: cisco/cisco-mibs/main/v2/CISCO-SSL-PROXY-MIB.my; 138,661 bytes

Alternative description: MIBdepot

This MIB module is for managing a Secure Socket Layer
(SSL) Proxy device which terminates and accelarates
SSL and Transport Layer Security (TLS) transactions.

The proxy device can act as a SSL server or a SSL client
depending on the configuration and the application.

In one application, the device acts as a proxy SSL
server. It terminates SSL handshakes and TCP connections
initiated by SSL clients. The device is configured with
a key and a certificate bearing the identity of the SSL
server. The device uses this identity to establish the
SSL session on behalf of the server, offloading the key
establishment and data encryption and decryption work.

After the SSL session has been successfully established
between the client and the proxy device, the device
starts to receive and decrypt the encrypted data sent
from the client and forward to the server. The device
forwards the clear data to the server on a backend
connection. Clear data sent from the server is encrypted
by the proxy device before it is forwarded to the SSL
client.

Optionally, the proxy device is configured to reencrypt
the decrypted data sent from the client to the server.
The proxy device acts as a SSL client to initiate a SSL
session to the server. The decrypted data is encrypted
within this SSL session to be forwarded to the server.
The encrypted data sent from the server to the device
is decrypted and then reencrypted before it is
forwarded to the client.

In another application, the proxy device forwards data
generated by one or more sources to the destination
via a SSL session. The proxy device acts as a SSL
client and intiates a SSL session to the next hop
device. When data is received from the source, the
proxy device forwards the data to the next hop using
the SSL session. The next hop can continue to forward
the data if it is not the destination.

The proxy device supports a number of proxy services.
Each proxy service defines the role of the proxy device,
whether it acts as a SSL server or a SSL client. The
rest of the configuration include cryptographic and
protocol parameters.

This MIB is used for monitoring the configuration,
statuses and statistics of the proxy services and
the protocols including TCP, SSL and TLS.

Source file: Download CISCO-SSL-PROXY-MIB.my.txt

File: cisco/CISCO-SSL-PROXY-MIB.my.txt; 111,496 bytes

Information from Circitor

ciscoSslProxyMIB        MODULE-IDENTITY
        LAST-UPDATED        "200310270000Z"
        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: cs-ssl@cisco.com" 
        DESCRIPTION
                "This MIB module is for managing a Secure Socket Layer
                (SSL) Proxy device which terminates and accelarates
                SSL and Transport Layer Security (TLS) transactions. 

                The proxy device can act as a SSL server or a SSL client
                depending on the configuration and the application.

                In one application, the device acts as a proxy SSL 
                server. It terminates SSL handshakes and TCP connections
                initiated by SSL clients. The device is configured with
                a key and a certificate bearing the identity of the SSL
                server. The device uses this identity to establish the 
                SSL session on behalf of the server, offloading the key
                establishment and data encryption and decryption work.

                After the SSL session has been successfully established
                between the client and the proxy device, the device 
                starts to receive and decrypt the encrypted data sent 
                from the client and forward to the server. The device 
                forwards the clear data to the server on a backend 
                connection. Clear data sent from the server is encrypted
                by the proxy device before it is forwarded to the SSL 
                client.
  
                Optionally, the proxy device is configured to reencrypt
                the decrypted data sent from the client to the server. 
                The proxy device acts as a SSL client to initiate a SSL
                session to the server. The decrypted data is encrypted 
                within this SSL session to be forwarded to the server. 
                The encrypted data sent from the server to the device 
                is decrypted and then reencrypted before it is 
                forwarded to the client.
 
                In another application, the proxy device forwards data
                generated by one or more sources to the destination 
                via a SSL session. The proxy device acts as a SSL 
                client and intiates a SSL session to the next hop 
                device. When data is received from the source, the 
                proxy device forwards the data to the next hop using 
                the SSL session.  The next hop can continue to forward 
                the data if it is not the destination.

                The proxy device supports a number of proxy services.
                Each proxy service defines the role of the proxy device,
                whether it acts as a SSL server or a SSL client. The 
                rest of the configuration include cryptographic and 
                protocol parameters.

                This MIB is used for monitoring the configuration, 
                statuses and statistics of the proxy services and 
                the protocols including TCP, SSL and TLS."

        REVISION            "200310270000Z"
        DESCRIPTION
                "Initial version of this MIB module."
        ::= { ciscoMgmt 370 }

Information from Cisco SMIv1

Source file: Download CISCO-SSL-PROXY-MIB-V1SMI.my · Publisher's file

Publisher path: cisco/cisco-mibs/main/v1/CISCO-SSL-PROXY-MIB-V1SMI.my; 109,307 bytes

Source file: Download CISCO-SSL-PROXY-MIB-V1SMI.my.txt

File: cisco/CISCO-SSL-PROXY-MIB-V1SMI.my.txt; 95,195 bytes

ciscoSslProxyMIB OBJECT IDENTIFIER ::= { ciscoMgmt 370 }

Information from OID Repository

Vendor: Cisco
Module: CISCO-SSL-PROXY-MIB

[Automatically extracted from oidview.com]

Information from MIBdepot

ciscoSslProxyMIB MODULE-IDENTITY
    LAST-UPDATED    "200310270000Z"
    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: cs-ssl@cisco.com"
    DESCRIPTION
        "This MIB module is for managing a Secure Socket Layer
        (SSL) Proxy device which terminates and accelarates
        SSL and Transport Layer Security (TLS) transactions. 

        The proxy device can act as a SSL server or a SSL client
        depending on the configuration and the application.

        In one application, the device acts as a proxy SSL 
        server. It terminates SSL handshakes and TCP connections
        initiated by SSL clients. The device is configured with
        a key and a certificate bearing the identity of the SSL
        server. The device uses this identity to establish the 
        SSL session on behalf of the server, offloading the key
        establishment and data encryption and decryption work.

        After the SSL session has been successfully established
        between the client and the proxy device, the device 
        starts to receive and decrypt the encrypted data sent 
        from the client and forward to the server. The device 
        forwards the clear data to the server on a backend 
        connection. Clear data sent from the server is encrypted
        by the proxy device before it is forwarded to the SSL 
        client.

        Optionally, the proxy device is configured to reencrypt
        the decrypted data sent from the client to the server. 
        The proxy device acts as a SSL client to initiate a SSL
        session to the server. The decrypted data is encrypted 
        within this SSL session to be forwarded to the server. 
        The encrypted data sent from the server to the device 
        is decrypted and then reencrypted before it is 
        forwarded to the client.

        In another application, the proxy device forwards data
        generated by one or more sources to the destination 
        via a SSL session. The proxy device acts as a SSL 
        client and intiates a SSL session to the next hop 
        device. When data is received from the source, the 
        proxy device forwards the data to the next hop using 
        the SSL session.  The next hop can continue to forward 
        the data if it is not the destination.

        The proxy device supports a number of proxy services.
        Each proxy service defines the role of the proxy device,
        whether it acts as a SSL server or a SSL client. The 
        rest of the configuration include cryptographic and 
        protocol parameters.

        This MIB is used for monitoring the configuration, 
        statuses and statistics of the proxy services and 
        the protocols including TCP, SSL and TLS."
    REVISION        "200310270000Z"
    DESCRIPTION
        "Initial version of this MIB module."
    ::= { ciscoMgmt 370 }

Information from Cisco

ciscoSslProxyMIB MODULE-IDENTITY
    LAST-UPDATED    "201209180000Z"
    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: cs-ssl@cisco.com"
    DESCRIPTION
        "This MIB module is for managing a Secure Socket Layer
        (SSL) Proxy device which terminates and accelarates
        SSL and Transport Layer Security (TLS) transactions. 

        The proxy device can act as a SSL server or a SSL client
        depending on the configuration and the application.

        In one application, the device acts as a proxy SSL 
        server. It terminates SSL handshakes and TCP connections
        initiated by SSL clients. The device is configured with
        a key and a certificate bearing the identity of the SSL
        server. The device uses this identity to establish the 
        SSL session on behalf of the server, offloading the key
        establishment and data encryption and decryption work.

        After the SSL session has been successfully established
        between the client and the proxy device, the device 
        starts to receive and decrypt the encrypted data sent 
        from the client and forward to the server. The device 
        forwards the clear data to the server on a backend 
        connection. Clear data sent from the server is encrypted
        by the proxy device before it is forwarded to the SSL 
        client.

        Optionally, the proxy device is configured to reencrypt
        the decrypted data sent from the client to the server. 
        The proxy device acts as a SSL client to initiate a SSL
        session to the server. The decrypted data is encrypted 
        within this SSL session to be forwarded to the server. 
        The encrypted data sent from the server to the device 
        is decrypted and then reencrypted before it is 
        forwarded to the client.

        In another application, the proxy device forwards data
        generated by one or more sources to the destination 
        via a SSL session. The proxy device acts as a SSL 
        client and intiates a SSL session to the next hop 
        device. When data is received from the source, the 
        proxy device forwards the data to the next hop using 
        the SSL session.  The next hop can continue to forward 
        the data if it is not the destination.

        The proxy device supports a number of proxy services.
        Each proxy service defines the role of the proxy device,
        whether it acts as a SSL server or a SSL client. The 
        rest of the configuration include cryptographic and 
        protocol parameters.

        This MIB is used for monitoring the configuration, 
        statuses and statistics of the proxy services and 
        the protocols including TCP, SSL and TLS."
    REVISION        "201209180000Z"
    DESCRIPTION
        "Added the following mib groups:
        cspSslResourceLimitNotifGroup 
        cspSslResourceLimitNotifObjectsGroup"
    REVISION        "200909220000Z"
    DESCRIPTION
        "Added following OBJECT IDENTIFIER.
        - cspHttpHeaderInsertedInfo
        - cspHttpRedirectInfo
        - cspHttpHeaderInsertedSslInfoStats
        - cspHttpHeaderInsertedSslClientCertStats
        - cspHttpRedirectClientCertAuthFailedStats

        Added the following OBJECT-GROUPs
        - cspHttpHeaderInsertedSslInfoGroup
        - cspHttpHeaderInsertedSslClientCertGroup
        - cspHttpRedirectInfoGroup

        Deprecated MODULE-COMPLIANCE cspMIBCompliance

        Added new MODULE-COMPLIANCE cspMIBComplianceRev1"
    REVISION        "200310270000Z"
    DESCRIPTION
        "Initial version of this MIB module."
    ::= { ciscoMgmt 370 }

First Registration Authority (inferred from ancestor 1.3.6.1.4.1.9)

Greg Satz

Current Registration Authority (inferred from ancestor 1.3.6.1.4.1.9)

Cisco Systems, Inc.

Direct children (3)

OIDNameDirect childrenDescendantsDescription
1.3.6.1.4.1.9.9.370.0 cspMIBNotifications33
1.3.6.1.4.1.9.9.370.1 cspMIBObjects21342
1.3.6.1.4.1.9.9.370.2 cspMIBConformance224

Siblings (706)

OIDNameDirect childrenDescendantsDescription
1.3.6.1.4.1.9.9.249 ciscoEnhancedImageMIB244 Initial version of the MIB. This MIB has Image table
containing the following information related to the
running IOS image
1. Enti…
1.3.6.1.4.1.9.9.252 cTapMIB380 This module manages Cisco's intercept feature.
1.3.6.1.4.1.9.9.253 ciscoItpXuaMIB3250 The MIB for MTP3 User Adaptation (M3UA) and SCCP User
Adaptation (SUA) for Cisco's IP Transfer Point (ITP)
implementation.

The Cis…
1.3.6.1.4.1.9.9.254 ciscoSlbExtMIB3425 The extended MIB for managing Server Load Balancing
Manager(s). This MIB extends the SLB management
functionality in the CISCO-SL…
1.3.6.1.4.1.9.9.255 ciscoFabricMcastMIB330 Fabric Multicast Resource MIB module.
This MIB module is used for managing/tracking the fabric
multicast resource related informa…
1.3.6.1.4.1.9.9.256 ciscoFabricMcastApplMIB316 Fabric multicast resource MIB module.
This MIB module is used for managing/tracking the fabric
multicast resource application rel…
1.3.6.1.4.1.9.9.257 ciscoFabricHfrMIB390 Cisco Enhanced Benes fabric MIB module.
This MIB module is used for managing/tracking the Ehanced
Benes Fabric entities and/or fa…
1.3.6.1.4.1.9.9.259 ciscoPsaMicrocodeMIB324 Cisco PSA Microcode MIB - Overview

The PSA is the Packet Switching ASIC used
in module like engine 2(E2) line cards in GSR
for IP …
1.3.6.1.4.1.9.9.260 ciscoSsgMIB3218 The MIB Module manages Service Selection Gateway(SSG)
devices.

Service Selection Gateway(SSG) is a switching solution
for service…
1.3.6.1.4.1.9.9.261 ciscoPtopoExtnMIB218 This MIB module contains extensions to the PTOPO-MIB that
provide support to distinguish between bidirectional and
unidirectional…
1.3.6.1.4.1.9.9.262 ciscoVoaMIB214 This MIB module defines objects to configure and manage the
Variable Optical Attenuator (VOA) modules.

VOA modules are typically …
1.3.6.1.4.1.9.9.263 ciscoIgmpSnoopingMIB3286 The MIB module for IGMP Snooping feature.

Internet Group Management Protocol (IGMP) is the protocol used
by IPv4 end hosts to ind…
1.3.6.1.4.1.9.9.264 ciscoOpticalMonitorMIB372 This MIB module defines objects to monitor optical
characteristics and set corresponding thresholds on the
optical interfaces in …
1.3.6.1.4.1.9.9.265 ciscoEntityPfeMib358 The Packet Forwarding Engine technology are Cisco developed
Network Processors, which accelerates certain features in
order to pr…
1.3.6.1.4.1.9.9.268 ciscoWlanVlanMIB341 This MIB module provides network management
support for device VLAN configuration on
IEEE 802.11 wireless LAN.

ACRONYMS
AES
Advanced…
1.3.6.1.4.1.9.9.269 ciscoTBridgeDevIfMIB220 This MIB module provides network management support
for configuration and status information of devices
supporting transparent br…
1.3.6.1.4.1.9.9.270 ciscoSyslogEventExtMIB221 This MIB module extends the Cisco Syslog
MIB and provides network management support
to handle and process Syslog messages as
devi…
1.3.6.1.4.1.9.9.271 ciscoL2DevMonMIB324 This MIB module is for monitoring of active
layer 2 devices by hot standby layer 2 devices
and the configuration of hot standby s…
1.3.6.1.4.1.9.9.272 ciscoDot11IfMIB3212 This MIB module provides network management
support for Cisco IEEE 802.11 Wireless LAN
type device (Access Point) radio interface…
1.3.6.1.4.1.9.9.273 ciscoDot11AssociationMIB2107 This MIB module provides network management
information on IEEE 802.11 wireless device
association management and data packet for…
1.3.6.1.4.1.9.9.275 ciscoBcpMIB225 This MIB module describes the Managed Objects for
of Bridge Control Protocol (RFC2878). This MIB is
influenced by RFC1474.
1.3.6.1.4.1.9.9.276 ciscoIfExtensionMIB3147 A MIB module for extending the IF-MIB (RFC2863)
to add objects which provide additional information
about interfaces not availabl…
1.3.6.1.4.1.9.9.277 ciscoDdpIappMIB322 This MIB module describes the management support for
the Inter-Access Point Protocol (IAPP). IAPP is a
Cisco propriety Data Deli…
1.3.6.1.4.1.9.9.278 ciscoIpProtocolMIB363 The MIB module is for management of information
to support packet filtering on IP protocols.

The cippfIpProfileTable allows users…
1.3.6.1.4.1.9.9.279 ciscoAtmQosMIB367 The MIB is created to provide ATM QoS information in
these areas:

1. Traffic shaping on a per-VC basis
2. Traffic shaping on a pe…
1.3.6.1.4.1.9.9.280 ciscoOutageMIB375 This MIB module describes, stores, and reports outage
related information generated by individual hardware
and software component…
1.3.6.1.4.1.9.9.281 ciscoFabricC12kMIB3135 Cisco Fabric MIB module for c12000 series of routers.
This MIB module is used for managing/tracking the c12000
fabric entities an…
1.3.6.1.4.1.9.9.282 ciscoVsanMIB2104 The MIB module for the management of the Virtual Storage
Networks (VSANs) within the frame work of Cisco's VSAN
Architecture. T…
1.3.6.1.4.1.9.9.284 ciscoFcRouteMIB255 The MIB module for configuring and displaying FC (Fibre
Channel) Route Information.
1.3.6.1.4.1.9.9.285 ciscoPortChannelMIB243 The MIB module for management of Port Channel ports.
In addition to this MIB, CISCO-FC-FE-MIB and interface
mib (rfc2863) will al…
1.3.6.1.4.1.9.9.286 ciscoWwnmgrMIB238 The World Wide Name (WWN) in the fibre channel networking
technology is equivalent to the MAC address in Ethernet.
There are six …
1.3.6.1.4.1.9.9.287 ciscoFspfMIB495 Fabric Shortest Path First (FSPF) MIB.
1.3.6.1.4.1.9.9.288 ciscoRadiusMIB396 MIB module for monitoring and configuring
authentication and logging services using RADIUS
(Remote Authentication Dial In User Se…
1.3.6.1.4.1.9.9.289 ciscoFcFeMIB2352 This is the Cisco fibre element management MIB module.
It covers:
- Cisco extension to the interface MIB ( IF-MIB )
- Contains all…
1.3.6.1.4.1.9.9.290 ciscoVirtualNwIfMIB222 The MIB module for management of virtual network
interfaces to VSAN and VLAN.
1.3.6.1.4.1.9.9.292 ciscoRscnMIB267 The MIB module for the management of the Fibre
Channel's Registered State Change Notification
(RSCN) functionality, which is spec…
1.3.6.1.4.1.9.9.293 ciscoNsMIB267 The MIB module for the management of the Cisco
Name Server which realizes the FC-GS3
requirements for Name Server (NS).
1.3.6.1.4.1.9.9.294 ciscoZsMIB2271 The MIB module for the management of zoning within
the framework of Cisco's Zoning Server (ZS) Archi-
tecture which realizes the …
1.3.6.1.4.1.9.9.295 ciscoFcPingMIB237 The MIB module for the management of the
Fibre Channel Ping functionality.
1.3.6.1.4.1.9.9.296 ciscoFcTraceRouteMIB231 The MIB module for the management of the
Fibre Channel Trace Route functionality.
1.3.6.1.4.1.9.9.297 ciscoFcsMIB2122 The MIB module for the management of a Fabric
Configuration Server (FCS). An FCS is defined
by the FC-GS3 standard. This MIB ena…
1.3.6.1.4.1.9.9.299 ciscoExtScsiMIB268 The Cisco extension to CISCO-SCSI-MIB
which is a copy of the Internet draft,
the SCSI-MIB, from the IETF.

Glossary of terms used i…
1.3.6.1.4.1.9.9.300 ciscoCallHomeMIB3327 The MIB module for the management of Call Home feature
within the framework of Cisco's Call Home architecture.
Customers deployin…
1.3.6.1.4.1.9.9.301 ciscoSyslogExtMIB244 MIB module for configuring and monitoring System Log
related management parameters as defined by RFC 3164.
1.3.6.1.4.1.9.9.302 ciscoDmMIB288 The MIB module for the domain management functionality
defined by the Fibre Channel standards (FC-SW2). For the
purposes of this …
1.3.6.1.4.1.9.9.305 ciscoSystemExtMIB3113 MIB module for monitoring High Availability, SNMP SET
errors and bandwidths. This mib module also provides the
information on co…
1.3.6.1.4.1.9.9.309 ciscoIPIfMIB340 The MIB module for configuring IP characteristics
of the interfaces of a device.
1.3.6.1.4.1.9.9.311 ciscoEpmNotificationMIB348 Notifications directly from hardware and software and processed
notifications from various management applications can be furthe…
1.3.6.1.4.1.9.9.312 ciscoDataCollectionMIB384 The MIB module allows a management application to
select a set of MIB object instances whose values need
to be collected on a per…
1.3.6.1.4.1.9.9.313 ciscoL2ControlMIB3113 The CISCO-L2-CONTROL-MIB is used to control some layer 2
functions, including MAC limit function and unicast
flooding. This devi…