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.514 ciscoLwappTextualConventions00 This module defines textual conventions used
throughout the Cisco enterprise MIBs
designed for implementation on Central
Controlle…
1.3.6.1.4.1.9.9.515 ciscoLwappWebAuthMIB4133 This MIB is intended to be implemented on all those
devices operating as Central controllers, that
terminate the Light Weight Acc…
1.3.6.1.4.1.9.9.516 ciscoLwappLinkTestMIB357 This MIB is intended to be implemented on all those
devices operating as Central controllers, that
terminate the Light Weight Acc…
1.3.6.1.4.1.9.9.517 ciscoLwappReapMIB3342 This MIB is intended to be implemented on all those
devices operating as Central Controllers (CC) that
terminate the Light Weight…
1.3.6.1.4.1.9.9.518 ciscoLwappMfpMIB468 This MIB is intended to be implemented on all those
devices operating as Central Controllers (CC) that
terminate the Light Weight…
1.3.6.1.4.1.9.9.519 ciscoLwappIdsMIB328 This MIB is intended to be implemented on all those
devices operating as Central Controllers (CC) that
terminate the Light Weight…
1.3.6.1.4.1.9.9.520 ciscoLwappCcxRmMIB345 This MIB is intended to be implemented on all those
devices operating as Central controllers, that
terminate the Light Weight Acc…
1.3.6.1.4.1.9.9.521 ciscoLwappWlanSecurityMIB377 This MIB is intended to be implemented on all those
devices operating as Central controllers, that
terminate the Light Weight Acc…
1.3.6.1.4.1.9.9.522 ciscoLwappDot11ClientCalibMIB355 This MIB is intended to be implemented on all those
devices operating as Central controllers, that
terminate the Light Weight Acc…
1.3.6.1.4.1.9.9.523 ciscoLwappClRoamMIB363 This MIB is intended to be implemented on all those
devices operating as Central controllers, that
terminate the Light Weight Acc…
1.3.6.1.4.1.9.9.524 ciscoLwappQosMIB3491 This MIB is intended to be implemented on all those
devices operating as Central controllers, that
terminate the Light Weight Acc…
1.3.6.1.4.1.9.9.525 ciscoLwappTsmMIB357 This MIB is intended to be implemented on all those
devices operating as Central controllers, that
terminate the Light Weight Acc…
1.3.6.1.4.1.9.9.529 ciscoItpMsuRatesMIB361 This MIB provides information used to manage the number
of MTP3 MSUs transmitted and received per processor. Many
of the higher …
1.3.6.1.4.1.9.9.530 ciscoNacTcMIB00 This module defines the textual conventions for
Cisco Network Admission Control(NAC) system.

The Cisco Network Admission Control …
1.3.6.1.4.1.9.9.532 ciscoNATExtMIB313 This MIB is an extension to the NAT-MIB.
This MIB module includes objects for
providing the NAT related statistics.

Acronyms:

NAT…
1.3.6.1.4.1.9.9.533 ciscoCbpTargetMIB325 This MIB module defines the managed objects for
representing targets which have class-based policy
mappings. A target can be any…
1.3.6.1.4.1.9.9.543 ciscoLicenseMgmtMIB3131 The MIB module for managing licenses on the system.
The licensing mechanism provides flexibility to
enforce licensing for various…
1.3.6.1.4.1.9.9.548 ciscoErrDisableMIB345 This MIB module provides the ability for a Network
Management Station (NMS) to configure and monitor the
error-disable feature vi…
1.3.6.1.4.1.9.9.572 ciscoRttMonIPExtMIB257 This MIB contains extensions to tables in CISCO-RTTMON-MIB
to support IP-layer extensions, specifically IPv6 addresses
and other …
1.3.6.1.4.1.9.9.573 ciscoQosTcMIB00 This module defines the textual conventions used within
Cisco Qos MIBs.
1.3.6.1.4.1.9.9.576 ciscoLwappMobilityMIB3106 This MIB is intended to be implemented on all those
devices operating as Central Controllers (CC) that

terminate the Light Weight…
1.3.6.1.4.1.9.9.577 ciscoLwappAclMIB347 This MIB is intended to be implemented on all those
devices operating as Central Controllers (CC) that
terminate the Light Weight…
1.3.6.1.4.1.9.9.578 ciscoRoutePoliciesMIB35 This module provides a subtree to define OIDs so that
various routing 'policies' used by Cisco routers can be
expressed. This mod…
1.3.6.1.4.1.9.9.580 ciscoSwitchQosMIB3295 This MIB module extends the CISCO-CLASS-BASED-QOS-MIB
by defining configuration and statistics information
specific to the qualit…
1.3.6.1.4.1.9.9.583 ciscoGslbTcMIB00 This MIB module defines Textual Conventions and
OBJECT-IDENTITIES for use in documents defining
management information base (MIBs…
1.3.6.1.4.1.9.9.584 ciscoEntityDiagTcMIB00 This module defines the textual conventions used within
Cisco Entity Diag MIB.
1.3.6.1.4.1.9.9.585 ciscoIpSlaEthernetMIB3245 This MIB module consists of two parts.

1) Auto-Ethernet-CFM Control:
|
|

2) ethernetJitter Stats:
|
|

The first part defines a mechani…
1.3.6.1.4.1.9.9.586 ciscoNotificationControlMIB228 This MIB provides network management support to regulate
the transmission of notifications generated by a
system providing networ…
1.3.6.1.4.1.9.9.589 ciscoGslbSystemMIB3103 This MIB module defines objects for network and system
information of Global Server Load Balancer(GSLB) as a
network device. A G…
1.3.6.1.4.1.9.9.590 ciscoCvpMIB3255 The Cisco Unified Customer Voice Portal (CVP) application
integrates with both traditional time-division multiplexing
(TDM) and I…
1.3.6.1.4.1.9.9.592 ciscoPrefPathMIB356 The MIB module for the management of
preferred path. This MIB enables managers
to configure and monitor Preferred Path
parameters.
…
1.3.6.1.4.1.9.9.593 ciscoFcSdvMIB328 This MIB instrumentation is for managing Fibre
Channel (FC) SAN Device Virtualization (SDV)
solution on Cisco Fibre Channel devic…
1.3.6.1.4.1.9.9.594 ciscoApplicationAccelerationMIB337 This is a MIB for managing Application Acceleration System(s).
This MIB includes instrumentation for providing the
performance st…
1.3.6.1.4.1.9.9.595 ciscoGslbDnsMIB3165 The MIB defines objects for status and statistics
information of DNS related operations of
Global Server Load Balancer(GSLB). Th…
1.3.6.1.4.1.9.9.597 ciscoContentServicesMIB3349 Content Service is a capability to examine IP/TCP/UDP headers,
payload and enable billing based on the content being provided.

Ab…
1.3.6.1.4.1.9.9.598 ciscoLwappAAAMIB3150 This MIB is intended to be implemented on all those
devices operating as Central Controllers (CC), that
terminate the Light Weigh…
1.3.6.1.4.1.9.9.599 ciscoLwappDot11ClientMIB4523 This MIB is intended to be implemented on all those
devices operating as Central controllers, that
terminate the Light Weight Acc…
1.3.6.1.4.1.9.9.600 ciscoGslbHealthMonMIB390 The MIB defines objects related to global keepalive
properties in GSLB devices. It contains the tables
for keep alive configurat…
1.3.6.1.4.1.9.9.601 ciscoResilientEthernetProtocolMIB377 This MIB module defines objects required for managing
Resilient Ethernet Protocol (REP).

Resilient Ethernet Protocol (REP) is a C…
1.3.6.1.4.1.9.9.602 ciscoPacketCaptureMIB3103 The MIB module for the management of packet capture
feature.
1.3.6.1.4.1.9.9.603 ciscoThreatMitigationServiceMIB368 This MIB provides management information about the Threat
Mitigation Service(TMS) entity named 'Consumer'. TMS is part
of Cisco's…
1.3.6.1.4.1.9.9.604 cdot1CfmMIB3166 Connectivity Fault Management module for managing IEEE 802.1ag
1.3.6.1.4.1.9.9.606 ciscoLwappMeshLinkTestMIB346 ciscoLwappMeshLinkTestMIB MODULE-IDENTITY
LAST-UPDATED "200702050000Z"
ORGANIZATION "Cisco Systems Inc."
CONTACT-INFO
"Cisco Sy…
1.3.6.1.4.1.9.9.607 ciscoDot11HtPhyMIB371 This MIB is intended to be implemented on Cisco's
WLAN devices that provide the wired uplink to wireless
clients through the high…
1.3.6.1.4.1.9.9.610 ciscoLwappRogueMIB4134 This MIB is intended to be implemented on all those
devices operating as Central Controllers, that
terminate the Light Weight Acc…
1.3.6.1.4.1.9.9.611 ciscoLwappDot11ClientCCXTextualConventions00 This module defines the textual conventions used
throughout the Cisco enterprise MIBs designed for
implementation on Central Cont…
1.3.6.1.4.1.9.9.612 ciscoLwappDot11MIB3158 This MIB is intended to be implemented on all those
devices operating as Central controllers, that
terminate the Light Weight Acc…
1.3.6.1.4.1.9.9.613 ciscoEvcMIB3156 Metro Ethernet services can support a wide range of
applications and subscriber needs easily, efficiently
and cost-effectively. …
1.3.6.1.4.1.9.9.614 ciscoLwappDot11LdapMIB333 This MIB is intended to be implemented on all those
devices operating as Central controllers, that
terminate the Light Weight Acc…
1.3.6.1.4.1.9.9.615 ciscoLwappRrmMIB3175 This MIB is intended to be implemented on all those
devices operating as Central controllers, that
terminate the Light Weight Acc…