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.384 ciscoDot11AntennaMIB211 This MIB is intended to be implemented on 802.11
Access Points and Wireless Bridges to provide
information about the antennas con…
1.3.6.1.4.1.9.9.385 ciscoUnityMIB3101 The MIB Module for the management of Cisco Unity server.
Cisco Unity is a Unified Communications solution that provides
advanced,…
1.3.6.1.4.1.9.9.386 ciscoModuleAutoShutdownMIB336 The CISCO-MODULE-AUTO-SHUTDOWN-MIB is used to configure
the module automatic shutdown feature. Modules will be
reset by the syste…
1.3.6.1.4.1.9.9.387 ciscoNetflowMIB3206 The Netflow MIB provides a simple and easy method
to get NetFlow cache information, current NetFlow
configuration and statistics.…
1.3.6.1.4.1.9.9.388 ciscoVirtualSwitchMIB3128 This MIB module defines the managed objects that support the
virtual switch architecture.

The virtual switch concept combines sev…
1.3.6.1.4.1.9.9.389 ciscoVoiceCasModuleMIB322 This MIB is used to support Programmable
CAS signaling Bit configuration on modules
that support voice traffic.

This MIB will enab…
1.3.6.1.4.1.9.9.390 ciscoCableDiagMIB333 This MIB module defines objects for managing cable
diagnostic test capabilites supported by the Cisco devices.

Cable diagnostic t…
1.3.6.1.4.1.9.9.391 ciscoFcspMIB346 MIB module for managing Fibre Channel Security for the
fibre channel devices.

This MIB is used to configure and monitor the
Fibre-…
1.3.6.1.4.1.9.9.392 ciscoRemoteAccessMonitorMIB3200 Acronyms and Definitions
The following acronyms and terms are used in this
document:

IPSec: Secure IP Protocol

VPN: Virtual Priv…
1.3.6.1.4.1.9.9.393 ciscoVoiceConnectivityMIB344 This MIB module provides connectivity related
information for devices (e.g., 'connectivity between
voice gateway, phones, gatekee…
1.3.6.1.4.1.9.9.394 ciscoIpTapMIB328 This module manages Cisco's intercept feature for IP.

This MIB is used along with CISCO-TAP2-MIB to
intercept IP traffic. CISCO-T…
1.3.6.1.4.1.9.9.395 cisco802TapMIB320 This module manages Cisco's intercept feature for
802 (layer 2) streams.

This MIB is used along with CISCO-TAP2-MIB to
intercept 8…
1.3.6.1.4.1.9.9.396 ciscoMlrMIB3190 The MIB for providing information about Multi-layer
Routing(MLR). This MIB will provide information used to
control and measure S…
1.3.6.1.4.1.9.9.397 ciscoH225MIB1176 Cisco H225 MIB module. This module consists of H225
call signaling and H225 RAS (Registration, Admission
and Status). These are p…
1.3.6.1.4.1.9.9.398 ciscoMauExtMIB323 A MIB module for extending the MAU-MIB (RFC 3636)
to add objects which provide additional management
information about MAU or Jac…
1.3.6.1.4.1.9.9.399 ciscoTap2MIB369 This module manages Cisco's intercept feature.
This MIB replaces CISCO-TAP-MIB. This MIB defines
a generic stream table that cont…
1.3.6.1.4.1.9.9.400 ciscoUserConnectionTapMIB213 This module manages Cisco's intercept feature for
user connections.

This MIB is used along with CISCO-TAP2-MIB to
intercept user t…
1.3.6.1.4.1.9.9.401 ciscoBridgeExtMIB334 A MIB module for extending BRIDGE-MIB specified in RFC 1493.
1.3.6.1.4.1.9.9.402 ciscoPowerEthernetExtMIB383 A MIB module for extending the POWER-ETHERNET-MIB
(RFC3621) to add objects which provide additional
management information about …
1.3.6.1.4.1.9.9.405 ciscoDnsServerMIB3408 The MIB module for entities implementing the server side
of the Domain Name System (DNS) protocol.
P. Mockapetris, 'Domain names …
1.3.6.1.4.1.9.9.407 ciscoAtmTrunkStatMIB3101 The MIB module contains ATM Trunk statistics.

TERMINOLOGY

PVC: Permanent Virtual Circuit
OAM: Operation and Management
CRC: Cyclic…
1.3.6.1.4.1.9.9.408 ciscoSnmpNotificationExtMIB313 This MIB extends the functionality provided
by SNMP-NOTIFICATION-MIB.
This MIB provides for the aging of the
notification filters …
1.3.6.1.4.1.9.9.409 ciscoSnmpVacmExtMIB211 The management information definitions to extend
the View-based Access Control Model (RFC3415) for
SNMP.

This MIB extends the 'SN…
1.3.6.1.4.1.9.9.411 ciscoVlanTranslationMIB327 The MIB module for the management of VLAN translations.

VLAN translation refers to the ability of the device
to translate between…
1.3.6.1.4.1.9.9.412 ciscoSnmpTargetExtMIB230 This MIB is an extension of the SNMP-TARGET-MIB
specified in RFC3413.

This MIB module contains Cisco-defined extension
to the sn…
1.3.6.1.4.1.9.9.413 ciscoDot11SsidSecMIB271 This MIB module provides network management
support for Cisco IEEE 802.11 Wireless LAN
devices association and authentication.

ACR…
1.3.6.1.4.1.9.9.414 ciscoPoePdMIB317 This MIB is intended for devices powered by
external power sources, in particular Power
Over Ethernet (PoE or formerly called inl…
1.3.6.1.4.1.9.9.415 ciscoWlanManMIB313 This MIB module provides network management
and configuration support for IEEE 802.11
Wireless LAN devices.

ACRONYMS

HTTP
Hypertext …
1.3.6.1.4.1.9.9.416 ciscoDot11QosMIB349 This MIB module provides network management
support for QoS on wireless LAN devices. The
objects defined in this MIB provide equ…
1.3.6.1.4.1.9.9.420 ciscoUnityExpressMIB3179 The MIB Module for the management of the Cisco Unity
Express (CUE) service. CUE is a voicemail service that
runs in a Cisco rout…
1.3.6.1.4.1.9.9.421 ciscoDpvmMIB355 The MIB module for the management of the
Dynamic Port Vsan Membership (DPVM) module.
DPVM provides the ability to assign (virtual
…
1.3.6.1.4.1.9.9.422 ciscoIPsecTc00 This MIB module defines the textual conventions
used in the IPsec suite of MIBs. This includes
Internet DOI numbers defined in RF…
1.3.6.1.4.1.9.9.423 ciscoIkeConfigMIB393 This is a MIB Module for configuring and viewing IKE
parameters and policies.

Acronyms
The following acronyms are used in this do…
1.3.6.1.4.1.9.9.424 ciscoCableMeteringMIB353 This is the MIB module for Usage Based Metering for the
DOCSIS-compliant Cable Modem Termination Systems (CMTS).

Usage Based Mete…
1.3.6.1.4.1.9.9.426 ciscoLinkErrorMonitorMIB334 The MIB module for managing Link Error Monitoring
Feature on devices.

Link Error Monitoring Feature provides a mechanism
to monito…
1.3.6.1.4.1.9.9.427 ciscoZsExtMIB333 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.428 ciscoIkeFlowExtMIB318 This MIB module is an extension to
CISCO-IKE-FLOW-MIB and contains Cisco Specific
extensions for monitoring IKE.

It is for monito…
1.3.6.1.4.1.9.9.429 ciscoIkeFlowMIB380 This is a MIB module for monitoring the structures
and status of IPsec control flows based on Internet
Key Exchange protocol. The…
1.3.6.1.4.1.9.9.430 ciscoFcDeviceAliasMIB314 The MIB module for the management of Device
Aliases in a Fibre Channel Fabric. A Fibre
Channel fabric consists of devices such as
…
1.3.6.1.4.1.9.9.431 ciscoIPsecProvisioningMIB398 IPSec is the next-generation network layer crypto
framework described in RFC2401-2411.
This MIB defines the IPsec configurations.
…
1.3.6.1.4.1.9.9.432 ciscoEnhancedIpsecFlowMIB3330 This is a MIB Module for monitoring the structures
and status of IPSec-based networks. The MIB has been
designed to be adopted as…
1.3.6.1.4.1.9.9.433 ciscoCFSMIB3102 This MIB applies to one or more of a set of devices
which have connectivity through some kind of 'fabric'.
Many features which ru…
1.3.6.1.4.1.9.9.434 ciscoIpNetworkDiscoveryMIB, ciscoIsnsIpNetDiscoveryMIB358 MIB to provide the information about the disjoint
IP networks connected to the various gigabit ethernet
interfaces in the 'Fabric…
1.3.6.1.4.1.9.9.435 ciscoFcMulticastMIB314 MIB module for monitoring and configuring
Fibre Channel Multicast feature.
1.3.6.1.4.1.9.9.436 ciscoDNSClientMIB328 The MIB module for entities implementing the client
side of the Domain Name System (DNS) protocol.
1.3.6.1.4.1.9.9.437 ciscoPortTrackMIB218 A MIB to configure the Port-Track feature.

When a link goes down, all the services which depend
on the link are notified of the o…
1.3.6.1.4.1.9.9.438 ciscoIPsecSignalingMIB3140 This MIB Module models status, performance and failures
of a protocol with the generic characteristics of signalling
protocols us…
1.3.6.1.4.1.9.9.439 ciscoCcmeMIB3338 This MIB allows management of Cisco CallManager Express
(CCME) feature in Cisco IOS. CCME is optional software
feature that enabl…
1.3.6.1.4.1.9.9.441 ciscoSrstMIB3149 This MIB allows management of Cisco Survivable Remote
Site Telephony (SRST) feature in Cisco IOS. SRST is
an optional software fe…
1.3.6.1.4.1.9.9.443 ciscoCommonMgmtMIB337 MIB module for integrating different elements of
managing a device. For example, different device access
methods like SNMP, CLI, …