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.616 ciscoLwappMeshMIB3215 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.617 ciscoLwappMeshStatsMIB499 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.618 ciscoLwappSysMIB3310 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.619 ciscoLwappLocalAuthMIB354 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.620 ciscoLwappMeshBatteryMIB334 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.621 ciscoH324DialControlMIB234 This MIB module enhances the IETF Dial Control MIB
(RFC2128) by providing H.324 call information over
a telephony network.

ITU-T R…
1.3.6.1.4.1.9.9.622 ciscoLwappDot11ClientTsMIB334 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.623 ciscoLwappCdpMIB356 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.624 ciscoIpSlaTCMIB00 This MIB contains textual conventions used by
CISCO IPSLA MIBs.

Acronyms:
FEC: Forward Equivalence Class
LPD: Label Path Discovery
L…
1.3.6.1.4.1.9.9.626 ciscoDot11HtMacMIB340 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.627 ciscoDot11RadarMIB325 This MIB module is for IEEE 802.11a/h Root device,
i.e. Access Point (AP) or Root Bridge. This MIB
allows dynamic frequency selec…
1.3.6.1.4.1.9.9.628 ciscoServiceControlSubscribersMIB337 This MIB provides global and specific information on
subscribers managed by a service control entity, which is a
network element …
1.3.6.1.4.1.9.9.630 ciscoTelnetServerMIB334 MIB module for displaying and configuring
Telnet related features in a device.
Telnet is a program to log into another computer o…
1.3.6.1.4.1.9.9.631 ciscoServiceControlLinkMIB321 This MIB module provides information about the status and
configuration of links used by service control entities.

The link on a …
1.3.6.1.4.1.9.9.632 ciscoSmeMIB354 MIB module to manage Storage Media Encryption (SME) service.
SME is an encryption service provided by an encryption node
residing…
1.3.6.1.4.1.9.9.633 ciscoIpSlaAutoMIB357 This module defines the MIB for IP SLA Automation. IP SLA
Automation consists of the following:
1. Use of grouping - Group is an …
1.3.6.1.4.1.9.9.634 ciscoServiceControlTpStatsMIB339 This MIB provides information and statistics on the traffic
processor(s) of a service control entity, which is a network
element …
1.3.6.1.4.1.9.9.635 ciscoIpSlaJitterMIB357 This MIB module defines templates for IP SLA operations of UDP
Jitter and ICMP Jitter.

The UDP Jitter operation is designed to me…
1.3.6.1.4.1.9.9.636 ciscoIpSlaEchoMIB371 This MIB module defines the templates for IP SLA operations of
ICMP echo, UDP echo and TCP connect.

The ICMP echo operation measu…
1.3.6.1.4.1.9.9.637 ciscoServiceControlRdrMIB356 This MIB module defines objects describing statistics and
configuration relating to the Raw Data Record Formatter running
on a se…
1.3.6.1.4.1.9.9.638 ciscoAgwMIB3324 This module manages Cisco's WiMAX ASN Gateway (ASN-GW).
A WiMAX network supports wireless data communication through
WiMAX radio …
1.3.6.1.4.1.9.9.639 ciscoOtnIfMIB3164 This MIB module defines the managed objects for physical layer
characteristics of DWDM optical channel interfaces and performanc…
1.3.6.1.4.1.9.9.640 ciscoImageLicenseMgmtMIB331 The MIB module for managing the running image level
of a Cisco device. Cisco's licensing mechanism provides
flexibility to run a …
1.3.6.1.4.1.9.9.642 ciscoBridgeDomainMIB324 A bridge domain is one of the means by which it is possible
to define a broadcast domain on a bridging device. It is an
alternati…
1.3.6.1.4.1.9.9.643 ciscoTelepresenceMIB3119 The MIB module defines the managed objects for a
Telepresence system.

Telepresence refers to a set of technologies which
allow a p…
1.3.6.1.4.1.9.9.644 ciscoTelepresenceCallMIB3178 The MIB module defines the managed objects for
Telepresence calls.

Telepresence refers to a set of technologies which
allow a pers…
1.3.6.1.4.1.9.9.645 ciscoEtherExtMIB318 The MIB module to describe generic objects for
ethernet-like network interfaces.

This MIB provides ethernet-like network interfac…
1.3.6.1.4.1.9.9.646 ciscoAonStatusMIB380 This MIB module defines managed objects that facilitate the
management of AON node.

The information available through this MIB in…
1.3.6.1.4.1.9.9.647 ciscoGgsnExtMIB3212 This MIB module extends the CISCO-GGSN-MIB.

This MIB module manages the Gateway GPRS Support
Node (GGSN) devices.

A GGSN device pr…
1.3.6.1.4.1.9.9.648 ciscoVirtualInterfaceMIB232 The MIB module for creation and deletion of Virtual Interfaces
and Virtual Interface Groups. In addition to this MIB,
interface …
1.3.6.1.4.1.9.9.650 ciscoL4L7moduleRedundancyMIB371 The L4-7 SLB devices are used
for scaling websites, building web
enabled applications, and migrating
to web services. The followin…
1.3.6.1.4.1.9.9.651 ciscoCommonRolesExtMIB337 A MIB Module for managing the roles that are common
between access methods like Command Line Interface (CLI),
SNMP and XML interf…
1.3.6.1.4.1.9.9.652 ciscoSwitchStatsMIB3106 The MIB module provides management information for
configuration and monitoring of traffic statistics
on Cisco's switching device…
1.3.6.1.4.1.9.9.653 ciscoAdmissionPolicyMIB336 This MIB module defines managed objects that facilitate
the management of policies upon host(s) admission to
a network.

The inform…
1.3.6.1.4.1.9.9.654 ciscoMabMIB320 MIB module for monitoring and configuring MAC
Authentication Bypass (MAB) feature in the system.

MAC Auth Bypass feature provides…
1.3.6.1.4.1.9.9.655 ciscoDigitalMediaSystemsMIB3195 Acronyms and Definitions

The following acronyms and terms are used in this
document:

DMS: Digital Media Systems

DAM: Digital As…
1.3.6.1.4.1.9.9.656 ciscoAuthFrameworkMIB3117 MIB module for Authentication Framework in the system.

Authentication Framework provides generic configurations
for authenticatio…
1.3.6.1.4.1.9.9.657 ciscoSbcCallStatsMIB3201 The main purpose of this MIB is to define the statistics
information for Session Border Controller application. The
statistics ar…
1.3.6.1.4.1.9.9.658 ciscoSessBorderCtrlrEventMIB3208 The main purpose of this MIB is to define the SNMP
notifications and alarms generated by Session Border Controller
application an…
1.3.6.1.4.1.9.9.660 ciscoNportVirtualizationMIB319 The MIB module for the management of N_port
Virtualization or NPV within the framework of Cisco's
N_port virtualization (NPV) Arc…
1.3.6.1.4.1.9.9.661 ciscoWan3gMIB3378 This MIB module provides network management
support for Cisco cellular 3G WAN products.

*** ABBREVIATIONS, ACRONYMS, AND SYMBOLS …
1.3.6.1.4.1.9.9.662 ciscoCbpTcMIB00 This MIB module defines textual conventions used by the
CISCO-CBP-BASE-CFG-MIB, CISCO-CBP-BASE-MON-MIB, and any MIB
modules exten…
1.3.6.1.4.1.9.9.663 ciscoSwitchHardwareCapacityMIB3147 This MIB module defines the managed objects for hardware
capacity of Cisco switching devices. The hardware
capacity information c…
1.3.6.1.4.1.9.9.664 ciscoMmodalContactAppsMIB3359 The Cisco Unified Multi-Modal Contact Applications (MMCA) platform is
a highly scalable, modular, extensible, open and secure pl…
1.3.6.1.4.1.9.9.667 ciscoServiceControllerMIB231 This MIB module defines objects describing traffic controllers
used by a service control entity.

A service control entity is a ne…
1.3.6.1.4.1.9.9.668 ciscoP2PIfMIB316 The Point to Point Interface MIB module.
This MIB manages the generic objects for
Serial link or SONET/SDH like point to point ne…
1.3.6.1.4.1.9.9.669 ciscoCdmaPdsnExtMIB3178 This MIB is an extension to the
CISCO-CDMA-PDSN-MIB. A CDMA
network supports wireless data
communication through 3G CDMA radio
acc…
1.3.6.1.4.1.9.9.670 ciscoReportIntervalTcMIB00 CISCO-REPORT-INTERVAL-TC-MIB
1.3.6.1.4.1.9.9.672 ciscoMobilityTapMIB324 This module manages Cisco's intercept feature for
Mobility Gateway Products.

This MIB is used along with CISCO-TAP2-MIB MIB to
int…
1.3.6.1.4.1.9.9.673 ciscoFCoEMIB245 This MIB module is for configuring and monitoring Fibre Channel
over Ethernet (FCoE) related entities. This MIB defines the
Virtu…