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.445 ciscoQinqVlanMIB325 This MIB defines configuration and monitoring capabilities
relating to 802.1QinQ interfaces. QinQ interfaces are capable
of term…
1.3.6.1.4.1.9.9.447 ciscoScsiFlowMIB399 A SCSI Flow is described as a SCSI Initiator
SCSI Target combination. This MIB is used to
configure and monitor SCSI Flows.

Gloss…
1.3.6.1.4.1.9.9.448 ciscoSsmProvMIB226 This MIB is used to provision features
on a Data Path Processor (DPP) of a Storage Service
Module (SSM). A DPP is assigned to a c…
1.3.6.1.4.1.9.9.449 ciscoEigrpMIB3110 Enhanced Interior Gateway Protocol (EIGRP) is a Cisco
proprietary distance vector routing protocol. It is based on
the Diffusin…
1.3.6.1.4.1.9.9.450 ciscoCableAdmCtrlMIB3123 This MIB module defines the managed objects enabling
the management of Cable Modem Termination System
(CMTS) admission control.

CM…
1.3.6.1.4.1.9.9.451 ciscoIpUrpfMIB347 Unicast Reverse Path Forwarding (URPF) is a function
that checks the validity of the source address of IP
packets received on an …
1.3.6.1.4.1.9.9.454 ciscoDot11LbsMIB323 This MIB module supports network management
for Location Based Services on IEEE 802.11 wireless
LAN devices. Location Based Serv…
1.3.6.1.4.1.9.9.455 ciscoImageTc00 ciscoImageTc MODULE-IDENTITY
LAST-UPDATED "200501120000Z"
ORGANIZATION "Cisco Systems, Inc."
CONTACT-INFO
"Cisco Systems
Custom…
1.3.6.1.4.1.9.9.456 ciscoDot11WidsMIB350 This MIB is intended to be implemented on the
following IOS based network entities for the purpose
of providing network managemen…
1.3.6.1.4.1.9.9.457 ciscoWdsIdsMIB218 This MIB is intended to be implemented on all
IOS based network entities that provide Wireless
Domain Services, for the purpose o…
1.3.6.1.4.1.9.9.458 ciscoApplianceRedundancyMIB347 This mib defines the SNMP objects to report the status of
High Availability (HA) functionality in Cisco network
management applia…
1.3.6.1.4.1.9.9.459 ciscoBitsClockMIB321 This MIB provides information on Building Integrated
Timing Supply(BITS) clocking sources and modes of
operations. It is used to…
1.3.6.1.4.1.9.9.460 ciscoTpcMIB324 The MIB module for Third Party Copy(TPC):
Third Party Copy derives its name from the fact
that there are three entities involved …
1.3.6.1.4.1.9.9.461 ciscoEtherCfmMIB339 This MIB module defines the managed objects
and notifications for Ethernet Connectivity
Fault Management (CFM).

CFM is an end-to-e…
1.3.6.1.4.1.9.9.463 ciscoSanTapMIB330 MIB module to provide information about the SanTap
service configuration.

SanTap is a fibre channel switch based capability that
p…
1.3.6.1.4.1.9.9.466 ciscoEthernetAccessMIB220 The tables defined by this MIB module contain a collection
of managed objects that are general in nature and apply to
an edge dev…
1.3.6.1.4.1.9.9.467 ciscoCryptoAcceleratorMIB3107 The MIB module for monitoring the identity, status,
activity and faults of crypto accelerator (CA) modules
used in devices implem…
1.3.6.1.4.1.9.9.468 ciscoContextMappingMIB235 A single SNMP agent sometimes needs to support multiple
instances of the same MIB module, and does so through the
use of multiple…
1.3.6.1.4.1.9.9.470 ciscoEnhancedSlbMIB3106 The MIB for managing Server Load Balancing
Manager(s), and products supporting Server
Load Balancing(SLB) features.

This MIB exten…
1.3.6.1.4.1.9.9.471 ciscoFlexLinksMIB336 This MIB module is for configuration and status query
of Flex Links feature on the Cisco device.

Flex Links are a pair of Layer 2…
1.3.6.1.4.1.9.9.472 ciscoModuleVirtualizationMIB335 This MIB provides a way to create virtual contexts,
and managing them. A virtual context is logical
partition of a physical devi…
1.3.6.1.4.1.9.9.473 ciscoCcaMIB3200 The Cisco Contact Center Applications (CCCA) Management
Information Base (MIB) module defines management
instrumentation for appl…
1.3.6.1.4.1.9.9.474 ciscoFilterGroupMIB355 The MIB module is for creating and configuring
object groups to support packet filtering and
access control on IP and other proto…
1.3.6.1.4.1.9.9.479 ciscoCableWidebandMIB377 This is the MIB module for the support of Channel Bonding
Protocol for the Cable Modem Termination System (CMTS).

Wideband DOCSIS…
1.3.6.1.4.1.9.9.480 ciscoL4L7moduleResourceLimitMIB4100 The MIB module for managing resource classes
and configuring limits(max/min) to different
resources. The resource referenced in …
1.3.6.1.4.1.9.9.482 ciscoInterfaceTopNExtMIB316 This MIB module is an extension to INTERFACETOPN-MIB.
It provides additional management information for
sorting device interfaces.
1.3.6.1.4.1.9.9.483 ciscoIpRanBackHaulMIB3248 This MIB provides information on the IP-RAN traffic
from cell site to aggregation site in the following
situations. In an GSM en…
1.3.6.1.4.1.9.9.484 ciscoNacNadMIB3157 This MIB module is for the configuration of a Network
Access Device (NAD) on the Cisco Network Admission
Control (NAC) system.

End…
1.3.6.1.4.1.9.9.485 ciscoRttMonTCMIB00 This MIB contains textual conventions used by
CISCO-RTTMON-MIB, CISCO-RTTMON-RTP-MIB and
CISCO-RTTMON-ICMP-MIB, but they are not …
1.3.6.1.4.1.9.9.486 ciscoRttMonIcmpMIB37 An extension to the CISCO-RTTMON-MIB for ICMP
operations. The ICMP Jitter operation provides capability
to measure metrics such a…
1.3.6.1.4.1.9.9.487 ciscoRttMonRtpMIB38 An extension to the CISCO-RTTMON-MIB for Cisco IP SLA
RTP operation, Real-Time Transport Protocol(RFC 1889). This
operation provi…
1.3.6.1.4.1.9.9.488 ciscoFirewallTc00 This MIB module defines textual conventions that
are commonly used in modeling management information
pertaining to configuration…
1.3.6.1.4.1.9.9.490 ciscoNetintMIB311 This MIB module is for Network Interrupt information
on Cisco device.
1.3.6.1.4.1.9.9.491 ciscoUnifiedFirewallMIB3360 Overview of Cisco Firewall MIB
==============================
This MIB Module models status and performance
statistics pertaining …
1.3.6.1.4.1.9.9.492 ciscoCefMIB3192 Cisco Express Forwarding (CEF) describes a high speed
switching mechanism that a router uses to forward packets
from the inbound …
1.3.6.1.4.1.9.9.493 ciscoCefTextualConventions00 ciscoCeftextualConventions
1.3.6.1.4.1.9.9.494 ciscoEntityRedunTcMIB00 This module defines the textual conventions used within
Cisco Entity Redundancy MIBs.
1.3.6.1.4.1.9.9.495 ciscoPsdClientMIB344 This MIB module manages the client side
functionality of the Persistent Storage Device(PSD).

This MIB instrumentation is for conf…
1.3.6.1.4.1.9.9.497 cGgsnSAMIB3247 This MIB module manages the service-aware feature of
Gateway GPRS Support Node (GGSN).

This MIB is an enhancement of the CISCO-GG…
1.3.6.1.4.1.9.9.498 ciscoEntityRedunMIB393 This management information module supports
configuration, control and monitoring of redundancy
protection for various kinds of c…
1.3.6.1.4.1.9.9.500 ciscoStackWiseMIB3111 This MIB module contain a collection of managed objects
that apply to network devices supporting the Cisco
StackWise(TM) technolo…
1.3.6.1.4.1.9.9.504 ciscoSwitchMulticastMIB3108 This MIB module defines management objects for the
Multicast Switching features on Cisco Layer 2/3
devices.

Definition of some of …
1.3.6.1.4.1.9.9.505 cpkiMIB344 A networking device may provide several security services
and protocols like SSL, SSH, IPSec/IKE etc. which need
identities …
1.3.6.1.4.1.9.9.507 ciscoPolicyGroupMIB335 The MIB module is for configuration of policy and
policy group. A policy group can be described as a set
of entities identified b…
1.3.6.1.4.1.9.9.508 ciscoSlbHealthMonMIB362 An extension to the CISCO-SLB-EXT-MIB for SLB
health monitoring probes.

SLB: Server Load Balancing. Server load balancing
provides…
1.3.6.1.4.1.9.9.509 ciscoWdsInfoMIB3141 This MIB is intended to be implemented on all Cisco
network entities that provide Wireless Domain Services
(WDS). The WDS provide…
1.3.6.1.4.1.9.9.510 ciscoErmMIB, ciscoVoiceLmrMIB3176 This MIB module provides management of voice tone
signal as static injected tone for Land Mobile Radio
The tone signal includes …
1.3.6.1.4.1.9.9.511 ciscoCbpTargetTCMIB00 This MIB module defines Textual Conventions for
representing targets which have class based policy
mappings. A target can be any …
1.3.6.1.4.1.9.9.512 ciscoLwappWlanMIB3378 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.513 ciscoLwappApMIB51009 This MIB is intended to be implemented on all those
devices operating as Central Controllers (CC) that
terminate the Light Weight…