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.181 | ciscoWirelessLinkMetricsMIB | 4 | 141 | This is the MIB Module for the Cisco Wireless Radio Point to MultiPoint interface link metrics specification. Glossary The followin… |
| 1.3.6.1.4.1.9.9.183 | ciscoGprsAccPtMIB | 3 | 338 | This MIB module supports access point configuration for GGSN in a GPRS system. GPRS [1] is a GSM network providing mobile wireles… |
| 1.3.6.1.4.1.9.9.184 | ciscoPimMIB | 3 | 36 | This MIB module defines the cisco specific variables for Protocol Independent Multicast (PIM) management. These definitions are a… |
| 1.3.6.1.4.1.9.9.185 | ciscoBertMIB | 2 | 46 | The MIB module to configure and perform Bit Error Rate Testing (BERT) on DS3, DS1/E1 and DS0/DS0Bundle interfaces. Bit error rate… |
| 1.3.6.1.4.1.9.9.187 | ciscoBgp4MIB | 4 | 170 | An extension to the IETF BGP4 MIB module defined in RFC 1657. Following is the terminology associated with Border Gateway Proto… |
| 1.3.6.1.4.1.9.9.188 | cGtpMIB | 3 | 248 | This MIB module manages the GPRS Tunnelling Protocol (GTP) on GGSN and SGSN. GPRS provides wireless access to packet data network… |
| 1.3.6.1.4.1.9.9.189 | ciscoPortQosMIB | 3 | 114 | Cisco PORT QOS MIB - Overview This MIB module is for the management of Cisco's per port rate-limiting and traffic shaping on L3 sw… |
| 1.3.6.1.4.1.9.9.190 | ciscoVoiceAppsMIB | 3 | 40 | The MIB Module for the management of Cisco Voice Applications. This MIB is designed to work in conjunction with the SYSAPPL-MIB … |
| 1.3.6.1.4.1.9.9.191 | ciscoIpUplinkRedirectMIB | 3 | 11 | This MIB module is for the configuration of Cisco IP Uplink Redirect feature. |
| 1.3.6.1.4.1.9.9.192 | ciscoGprsChargingMIB | 3 | 315 | This MIB module manages the charging related function on the GGSN node of a GPRS system. The following diagram illustrates a simp… |
| 1.3.6.1.4.1.9.9.194 | ciscoPppoeMIB | 3 | 89 | Cisco PPPoE sessions management MIB Module. |
| 1.3.6.1.4.1.9.9.195 | ciscoEntityExtMIB | 3 | 70 | This MIB is an extension of the ENTITY-MIB specified in RFC2737. This MIB module contains Cisco-defined extensions to the entit… |
| 1.3.6.1.4.1.9.9.197 | ciscoDistDirMIB | 3 | 123 | Cisco Distributed Director MIB. The Cisco Distributed Director provides global Internet scalability and increased performance as … |
| 1.3.6.1.4.1.9.9.198 | ciscoRfSupMIB | 3 | 65 | This MIB was designed to complement the CISCO-RF-MIB by providing additional optional status and configuration control for redund… |
| 1.3.6.1.4.1.9.9.199 | ciscoSmFileDownloadMIB | 3 | 23 | The MIB module for downloading files to the Service Modules specifically designed for an architecture containing a controller car… |
| 1.3.6.1.4.1.9.9.201 | ciscoSwitchUsageMIB | 3 | 15 | This MIB defines objects related to statistics for the usage of switch fabric. The switch fabric is used by the incoming packets … |
| 1.3.6.1.4.1.9.9.202 | ciscoOscpMIB | 3 | 52 | The MIB module for managing the Cisco Optical Supervisory Channel Protocol (OSCP). The OSCP is used to determine and maintain wav… |
| 1.3.6.1.4.1.9.9.204 | ciscoXdslLineMIB | 2 | 32 | The tables defined by this MIB module contain a collection of managed objects that are general in nature and apply to different t… |
| 1.3.6.1.4.1.9.9.215 | ciscoMacNotificationMIB | 3 | 72 | This MIB module is for configuration of the MAC notification feature. MAC notification is a mechanism to inform monitoring device… |
| 1.3.6.1.4.1.9.9.216 | ciscoContentNetworkMIB | 3 | 34 | This MIB module defines objects for Content Network devices. A Content Network is a collection of devices that optimizes the deli… |
| 1.3.6.1.4.1.9.9.217 | ciscoCat6kCrossbarMIB | 3 | 210 | The Catalyst 6000 Crossbar MIB provides instrumentation for configuration and operation of the crossbar switching fabric module, … |
| 1.3.6.1.4.1.9.9.218 | ciscoIfThresholdMIB | 3 | 65 | ciscoIfthresholdMIB |
| 1.3.6.1.4.1.9.9.219 | ciscoVoiceDnisMIB | 3 | 24 | The MIB module provides management support for Dialer Number Information Service (DNIS) mapping. A DNIS entry is associated with… |
| 1.3.6.1.4.1.9.9.220 | ciscoPaeMIB | 3 | 231 | Cisco Port Access Entity (PAE) module for managing IEEE Std 802.1x. This MIB provides Port Access Entity information that are eith… |
| 1.3.6.1.4.1.9.9.221 | ciscoEnhancedMemPoolMIB | 3 | 87 | New MIB module for monitoring the memory pools of all physical entities on a managed system. |
| 1.3.6.1.4.1.9.9.222 | ciscoEnhancedWredMIB | 3 | 70 | Cisco WRED MIB - Overview Cisco Weighted Random Early Detection/Drop (WRED) is a method which avoids traffic congestion on an outp… |
| 1.3.6.1.4.1.9.9.223 | ciscoWanNcdpMIB | 3 | 58 | This MIB module is intended for the management of network clock distribution and the Network Clock Distribution Protocol (NCDP) i… |
| 1.3.6.1.4.1.9.9.224 | ciscoDevExcepReportMIB | 3 | 29 | This mib defines the SNMP objects to report exceptions to north-bound NMS. The devices implementing this MIB monitor the status of… |
| 1.3.6.1.4.1.9.9.225 | ciscoLagMIB | 3 | 56 | Cisco Link Aggregation module for managing IEEE Std 802.3ad. This MIB provides Link Aggregation information that are either exclud… |
| 1.3.6.1.4.1.9.9.226 | ciscoNDEMIB | 4 | 17 | The Netflow Data Export (NDE) MIB provides instrumentation for configuration and operation of the Netflow Data Export feature. A … |
| 1.3.6.1.4.1.9.9.227 | ciscoItpAclMIB | 3 | 45 | The MIB for managing access lists that control messages transported over Signalling System No. 7 (SS7) Network via Cisco IP Trans… |
| 1.3.6.1.4.1.9.9.228 | ciscoItpRtMIB | 3 | 47 | This MIB is for managing information required to route messages transported over Signalling System No. 7 (SS7) Network via Cisco … |
| 1.3.6.1.4.1.9.9.229 | ciscoDs1ExtMIB | 2 | 129 | The MIB module to describe DS1/E1 interface objects. This is an extension to the standard DS1/E1 MIB (RFC 2495). Unless mentioned… |
| 1.3.6.1.4.1.9.9.230 | ciscoItpActMIB | 3 | 29 | The MIB for providing information specified in ITU Q752 Monitoring and Measurements for Signalling System No. 7(SS7) Network. This… |
| 1.3.6.1.4.1.9.9.231 | ciscoItpTextualConventions | 0 | 0 | The defines textual conventions used by to manage devices related to the SS7 network. The relevant ITU documents describing this… |
| 1.3.6.1.4.1.9.9.232 | ciscoItpSpMIB | 3 | 384 | The MIB for managing Signalling Points and its associated messages transported over Signalling System No. 7 (SS7) Network via Ci… |
| 1.3.6.1.4.1.9.9.233 | ciscoItpSccpMIB | 3 | 194 | The MIB for Signaling Connection Control Part(SCCP) messages transported over Signalling System No. 7 (SS7) Network via Cisco IP … |
| 1.3.6.1.4.1.9.9.234 | ciscoWanTopologyMIB | 3 | 83 | A management station can use this MIB module for the maintenance of persistent topology information of the PNNI network. Previous… |
| 1.3.6.1.4.1.9.9.235 | ciscoImaMIB | 2 | 60 | The MIB module describes Cisco IMA objects. This is an extension to the standard of ATM Forum IMA version 1.1, AF-PHY-0086.001 Spe… |
| 1.3.6.1.4.1.9.9.236 | ciscoWanSctMgmtMIB | 2 | 18 | MIB module to manage SCT files in a node. SCTs (Service Class Templates) are nodal configuration files, which define the traffic … |
| 1.3.6.1.4.1.9.9.237 | ciscoNmsApplHealthMIB | 3 | 39 | This MIB defines Cisco NMS Application (cna) Health Status Notifications and the related objects. These notifications will be sen… |
| 1.3.6.1.4.1.9.9.238 | ciscoIGMPFilterMIB | 2 | 45 | IGMP Filter configuration MIB. This MIB provides a mechanism for users to configure the system to intercept IGMP joins for IP Mul… |
| 1.3.6.1.4.1.9.9.240 | cGgsnMIB | 3 | 389 | This MIB module manages the Gateway GPRS Support Node (GGSN) devices. A GGSN device provides interworking with external packet-dat… |
| 1.3.6.1.4.1.9.9.241 | cggsnQosMIB | 2 | 89 | This MIB module manages the Quality of Service parameters of GGSN in a GPRS system. GGSN is the Gateway GPRS Support Node in the … |
| 1.3.6.1.4.1.9.9.242 | ciscoCableAvailabilityMIB | 3 | 60 | This is the MIB module for management of Hot Standby Connection to Connection Protocol (HCCP) features. HCCP is a Cisco proprieta… |
| 1.3.6.1.4.1.9.9.243 | ciscoHealthMonitorMIB | 3 | 22 | Health Monitor MIB module. The Health Monitor uses a model based on events of varying severity and frequency, and predefined rule… |
| 1.3.6.1.4.1.9.9.244 | ciscoNbarProtocolDiscoveryMIB | 3 | 84 | Cisco NBAR Protocol Discovery MIB NBAR - Network Based Application Recognition is an intelligent classification engine that reco… |
| 1.3.6.1.4.1.9.9.245 | ciscoGtpDirectorMIB | 3 | 35 | This MIB module defines objects that are used to manage GTP Director Module. In the GPRS network, the APN is the identifier that s… |
| 1.3.6.1.4.1.9.9.246 | ciscoL2TunnelConfigMIB | 3 | 65 | This MIB module is for layer 2 tunneling related configurations on a device. Tunneling allows separate local networks to be consi… |
| 1.3.6.1.4.1.9.9.248 | ciscoItpSp2MIB | 3 | 30 | The MIB for providing information specified in ITU Q752 Monitoring and Measurements for Signaling System No. 7(SS7) Network. This … |