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
(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
(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:
- Netdisco archive revision metadata (not a manufacturer release date)File: repos/netdisco/netdisco-mibs/commits/master; 15,422 bytes
- Netdisco MIB distribution at the selected archive revision38.9 MiB
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:
- Observium Community original distribution archivePublisher Last-Modified: Tue, 05 May 2026 13:47:48 GMT; 127.4 MiB
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
(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
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)
Current Registration Authority (inferred from ancestor 1.3.6.1.4.1.9)
Direct children (3)
| OID | Name | Direct children | Descendants | Description |
|---|---|---|---|---|
| 1.3.6.1.4.1.9.9.370.0 | cspMIBNotifications | 3 | 3 | |
| 1.3.6.1.4.1.9.9.370.1 | cspMIBObjects | 21 | 342 | |
| 1.3.6.1.4.1.9.9.370.2 | cspMIBConformance | 2 | 24 |
Siblings (706)
| OID | Name | Direct children | Descendants | Description |
|---|---|---|---|---|
| 1.3.6.1.4.1.9.9.128 | ciscoVlanIfTableRelationshipMIB | 1 | 12 | ciscoVlanIftableRelationshipMIB |
| 1.3.6.1.4.1.9.9.129 | ciscoAtmVirtualIfMIB | 2 | 139 | The MIB module to manage ATM Virtual interface objects. ATM virtual interfaces are configured on a physical line. |
| 1.3.6.1.4.1.9.9.130 | ciscoAdslDmtLineMIB | 3 | 72 | This MIB module serves as an enterprise-specific extension of the ADSL-LINE-MIB. The structure of this MIB module shadows the st… |
| 1.3.6.1.4.1.9.9.131 | ciscoSystemMIB | 3 | 57 | The systemGroup (see RFC 1907) provides a standard set of basic system information. This MIB module contains Cisco-defined exten… |
| 1.3.6.1.4.1.9.9.132 | ciscoDs3MIB | 2 | 140 | The MIB module to describe DS3 line objects. This is an extension to the standard DS3 MIB(RFC 2496). |
| 1.3.6.1.4.1.9.9.133 | ciscoAtmCellLayerMIB | 1 | 138 | The MIB module to describe ATM cell layer objects and statistics of a physical line. |
| 1.3.6.1.4.1.9.9.134 | ciscoClusterMIB | 3 | 49 | The MIB module for the management of a group of devices called a 'cluster'. A cluster comprises: 1. A command switch, which is a… |
| 1.3.6.1.4.1.9.9.135 | ciscoWirelessP2pBpiMIB | 3 | 66 | This is the MIB Module for the Baseline Privacy Interface (BPI) at Point to Point Wireless Radio Card. This is a specialization o… |
| 1.3.6.1.4.1.9.9.136 | ciscoWirelessIfMIB | 3 | 325 | This is the MIB Module for the Cisco Wireless Radio Point to Point interface specification. I) Relationship of the Cisco Wireless… |
| 1.3.6.1.4.1.9.9.137 | ciscoWirelessTextualConventions | 0 | 0 | This module defines textual conventions used in Cisco Wireless MIBs. |
| 1.3.6.1.4.1.9.9.138 | ciscoEntityAlarmMIB | 3 | 66 | This MIB module defines the managed objects that support the monitoring of alarms generated by physical entities contained by the… |
| 1.3.6.1.4.1.9.9.139 | ciscoEntityProvMIB | 3 | 13 | This MIB module defines the objects that support provisioning of 'container' class physical entities. Provisioning sets up a 'co… |
| 1.3.6.1.4.1.9.9.140 | ciscoCopsClientMIB | 3 | 43 | This MIB module is for configuration & statistic query of Common Open Policy Service(COPS) client feature on the Cisco device. C… |
| 1.3.6.1.4.1.9.9.141 | ciscoVSIControllerMIB | 2 | 21 | This MIB module is used for configuring ATM Capable Switch to be aware of VSI Controller information. Terminolgies used: VSI … |
| 1.3.6.1.4.1.9.9.144 | ciscoTransactionConnectionMIB | 2 | 66 | The MIB module for retrieving Cisco Transaction Connection configuration and status. Cisco Transaction Connection routes transac… |
| 1.3.6.1.4.1.9.9.145 | ciscoWanModuleMIB | 3 | 32 | The MIB to configure Connection Specific parameters and statistics related information in a Service Module. The Service Module(SM… |
| 1.3.6.1.4.1.9.9.146 | ciscoCallApplicationMIB | 2 | 548 | This MIB allows management of call applications on a network device. A 'call application' is a software module that processes cal… |
| 1.3.6.1.4.1.9.9.147 | ciscoFirewallMIB | 3 | 77 | MIB module for monitoring Cisco Firewalls. |
| 1.3.6.1.4.1.9.9.148 | ciscoBgpPolAcctMIB | 2 | 15 | BGP policy based accounting information |
| 1.3.6.1.4.1.9.9.149 | ciscoAdslLineCapMIB | 3 | 46 | This MIB module serves as an enterprise-specific extension of the ADSL-LINE-MIB. The structure of this MIB module shadows the st… |
| 1.3.6.1.4.1.9.9.150 | ciscoAAASessionMIB | 3 | 31 | This MIB module provides data for accounting sessions based on Authentication, Authorization, Accounting (AAA) protocols. Referenc… |
| 1.3.6.1.4.1.9.9.151 | ciscoL2L3IfConfigMIB | 2 | 11 | Interface switchport mode configuration management MIB. This MIB is used to monitor and control configuration of interface switch… |
| 1.3.6.1.4.1.9.9.152 | ciscoSipUaMIB | 4 | 557 | Cisco User Agent Session Initiation Protocol (SIP) MIB module. SIP is an application-layer signalling protocol for creating, mod… |
| 1.3.6.1.4.1.9.9.154 | ciscoIdslLineMIB | 3 | 148 | This MIB module describes IDSL (ISDN Digital Line Subscriber) line interfaces. The structure of this module resembles that of th… |
| 1.3.6.1.4.1.9.9.155 | ciscoSdslLineMIB | 3 | 170 | This MIB module describes all variations of the symmetric DSL line interfaces. The structure of this module resembles and mainta… |
| 1.3.6.1.4.1.9.9.156 | ciscoCcmMIB | 3 | 487 | The MIB Module for the management of a Cisco Unified Communications Manager (CUCM) application running with a Cisco Communication… |
| 1.3.6.1.4.1.9.9.157 | ciscoCdmaPdsnMIB | 3 | 984 | This MIB is to support the CDMA PDSN (Packet Data Serving Node) feature. A CDMA2000 network supports wireless data communication… |
| 1.3.6.1.4.1.9.9.158 | ciscoAAAClientMIB | 3 | 25 | This MIB module provides data for authentication method priority based on Authentication, Authorization, Accounting (AAA) protoco… |
| 1.3.6.1.4.1.9.9.159 | ciscoQosPolicyConfigMIB | 3 | 35 | This MIB module defines managed objects that support the policy source configuration of Quality of Service (QoS) on the device. T… |
| 1.3.6.1.4.1.9.9.160 | ciscoCircuitInterfaceMIB | 2 | 11 | The MIB module to configure the circuit description for an interface. The circuit description can be used to describe and identify… |
| 1.3.6.1.4.1.9.9.161 | ciscoSlbMIB | 3 | 279 | The MIB for managing Server Load Balancing Manager(s), such as the Cisco IOS SLB product. This MIB includes instrumentation for t… |
| 1.3.6.1.4.1.9.9.162 | ciscoVsiMasterMIB | 3 | 109 | This MIB module contains objects related to the master side of the the Virtual Switch Interface protocol used for control of ATM … |
| 1.3.6.1.4.1.9.9.163 | ciscoCallTrackerMIB | 3 | 104 | CISCO-CALL-TRACKER-MIB |
| 1.3.6.1.4.1.9.9.164 | ciscoCallTrackerTCPMIB | 3 | 25 | This MIB module provides TCP service connection related data for tracking the progress and status of a call. This module extends t… |
| 1.3.6.1.4.1.9.9.165 | ciscoCallTrackerModemMIB | 3 | 97 | This MIB module provides modem call related data for tracking the progress and status of a call. This module extends tables defin… |
| 1.3.6.1.4.1.9.9.166 | ciscoCBQosMIB | 2 | 562 | Cisco Class-Based QoS MIB ********************************** Overview ********************************** This MIB provides read acc… |
| 1.3.6.1.4.1.9.9.167 | ciscoWirelessDocsIfMib | 3 | 140 | This is the MIB Module for MCNS compliant Radio Frequency (RF) interfaces in wireless point-to-multipoint subscriber units (SU) a… |
| 1.3.6.1.4.1.9.9.168 | ciscoNtpMIB | 3 | 87 | This MIB module defines a MIB which provides mechanisms to monitor an NTP server. The MIB is derived from the Technical Report #Ma… |
| 1.3.6.1.4.1.9.9.169 | ciscoWirelessDocsExtMIB | 3 | 99 | This MIB module defines Cisco-specific objects that add to the functionality defined in CISCO-WIRELESS-DOCS-IF-MIB. These objects … |
| 1.3.6.1.4.1.9.9.170 | ciscoWirelessPhyMIB | 2 | 112 | This is the MIB Module for the Cisco Wireless Radio Point to MultiPoint interface. |
| 1.3.6.1.4.1.9.9.171 | ciscoIpSecFlowMonitorMIB | 3 | 507 | This is a MIB Module for monitoring the structures in IPSec-based Virtual Private Networks. The MIB has been designed to be adopt… |
| 1.3.6.1.4.1.9.9.172 | ciscoIpSecPolMapMIB | 3 | 21 | The MIB module maps the IPSec entities created dynamically to the policy entities that caused them. This is an appendix to the IPS… |
| 1.3.6.1.4.1.9.9.173 | ciscoPrivateVlanMIB | 2 | 56 | The MIB module to support Private VLAN feature on Cisco's switching devices. |
| 1.3.6.1.4.1.9.9.174 | ciscoMobileIpMIB | 3 | 533 | An extension to the IETF MIB module defined in RFC-2006 for managing Mobile IP implementations. Mobile IP introduces the followin… |
| 1.3.6.1.4.1.9.9.175 | ciscoIfLinkConfigMIB | 2 | 15 | The MIB module for configuration of bulk distribution (de-multiplexing of traffic from higher-bandwidth to lower-bandwidth interf… |
| 1.3.6.1.4.1.9.9.176 | ciscoRFMIB | 3 | 117 | This MIB provides configuration control and status for the Redundancy Framework (RF) subsystem. RF provides a mechanism for logic… |
| 1.3.6.1.4.1.9.9.177 | ciscoSaaApmMIB | 3 | 38 | Acronyms and Terms: SAA - Service Assurance Agent APM - Application Performance Monitoring A MIB for controlling SAA APM. APM provi… |
| 1.3.6.1.4.1.9.9.178 | ciscoContentEngineMIB | 3 | 263 | The MIB module for the Cisco Content Engine from Cisco Systems, Inc. |
| 1.3.6.1.4.1.9.9.179 | ciscoCatOSAclQosMIB | 3 | 470 | This MIB module is for Access Control Lists(ACLs) configuration of Quality of Service (QoS) as well as Security feature on the Ci… |
| 1.3.6.1.4.1.9.9.180 | ciscoWirelessRfMetricsMIB | 5 | 99 | This is the MIB Module for the Cisco Wireless Radio Point to MultiPoint interface specification. |