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.314 | ciscoCasIfExtMIB | 3 | 225 | The MIB module is an extension of CISCO-CAS-IF-MIB. It defines the attributes of a voice interface. |
| 1.3.6.1.4.1.9.9.315 | ciscoPortSecurityMIB | 3 | 89 | The MIB module for managing Cisco Port Security. |
| 1.3.6.1.4.1.9.9.317 | ciscoIscsiGwMIB | 3 | 145 | MIB module for monitoring and configuring iSCSI gateway functions. An iSCSI gateway represents FC (Fibre Channel) targets/initiat… |
| 1.3.6.1.4.1.9.9.318 | ciscoXgcpMIB | 3 | 120 | This MIB is an enhancement for existing XGCP-MIB. xGCP is a set of protocols, for example SGCP (Simple Gateway Control Protocol) … |
| 1.3.6.1.4.1.9.9.319 | ciscoPropAtmIfMIB | 3 | 57 | This MIB is designed for Propietary ATM (propAtm) interfaces. The propAtm interfaces are identified in the ifTable entries with if… |
| 1.3.6.1.4.1.9.9.321 | ciscoMgcMIB | 3 | 43 | This MIB is used to support MGC(call agent) and MGC Group configuration. The MGC or MGC group configuration is performed under a s… |
| 1.3.6.1.4.1.9.9.322 | ccacSysMIB | 2 | 60 | This MIB module provides provisioning and monitoring Call Admission Control (CAC). |
| 1.3.6.1.4.1.9.9.323 | ciscoVoiceAalxProfileMIB | 3 | 87 | This MIB defines the objects specific to voice over ATM or voice over IP. Those objects are related to the following areas: 1. COD… |
| 1.3.6.1.4.1.9.9.324 | ciscoMediaGatewayMIB | 3 | 107 | The MIB module for managing Trunk Media Gateway. A Media Gateway is a network element that provides conversion between the audio … |
| 1.3.6.1.4.1.9.9.325 | ciscoXgcpExtMIB | 2 | 65 | This MIB module is an extension to CISCO-XGCP-MIB. It defines the parameters related to the following aspects in xGCP protocols: *… |
| 1.3.6.1.4.1.9.9.326 | ciscoIpLocalPoolMIB | 3 | 57 | This MIB defines the configuration and monitoring capabilities relating to local IP pools. Local IP pools have the following char… |
| 1.3.6.1.4.1.9.9.329 | ciscoFcipMgmtExtMIB | 3 | 75 | A MIB module for extending the CISCO-FCIP-MGMT-MIB to add objects which provide additional information about FCIP interfaces not … |
| 1.3.6.1.4.1.9.9.330 | ciscoSysInfoLogMIB | 3 | 44 | This MIB provides the configuration of System Information Logging feature, which allows a certain number of commands to be execut… |
| 1.3.6.1.4.1.9.9.331 | ciscoCsgMIB | 3 | 86 | This MIB supports the Cisco Content Services Gateway (CSG) product. It includes five traps and four tables that enable querying C… |
| 1.3.6.1.4.1.9.9.332 | ciscoGsp2MIB | 3 | 91 | 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.333 | ciscoGactMIB | 3 | 40 | 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.334 | ciscoGrtMIB | 3 | 150 | 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.335 | ciscoGsccpMIB | 3 | 293 | The MIB for signalling Connection Control Part(SCCP) messages transported over Signalling System No. 7 (SS7) Network via Cisco IP… |
| 1.3.6.1.4.1.9.9.336 | ciscoGspMIB | 3 | 273 | 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.339 | ciscoSecureShellMIB | 2 | 40 | MIB module for displaying and configuring accounting and Secure Shell (SSH) related features in a device. SSH is a program to log … |
| 1.3.6.1.4.1.9.9.340 | ciscoLreCpeMIB | 3 | 21 | The MIB module for the Cisco Long Reach Ethernet Customer Premise Equipment device information. *** ABBREVIATIONS, ACRONYMS, AND … |
| 1.3.6.1.4.1.9.9.341 | ciscoCableQosMonitorMIB | 3 | 57 | This is the MIB module for subscriber QoS monitoring for DOCSIS-compliant Cable Modem Termination Systems (CMTS). Several subscrib… |
| 1.3.6.1.4.1.9.9.343 | ciscoAuthorizationStatsMibModule | 2 | 25 | The Cisco User Authorization Statistics MIB models counters and objects that are of management interest. |
| 1.3.6.1.4.1.9.9.344 | ciscoEntityDisplayMIB | 2 | 21 | This MIB module provides information about the status of display devices such as Light Emitting Diodes (LEDs) and alphanumeric di… |
| 1.3.6.1.4.1.9.9.350 | ciscoEntityDiagMIB | 3 | 139 | This MIB module defines the managed objects that describe the online diagnostics capabilities supported by the physical entities … |
| 1.3.6.1.4.1.9.9.351 | ciscoAtmTrunkMIB | 3 | 102 | The MIB for voice and Nx64 over ATM Trunking applications. The following lists the abbreviations used in this MIB: AAL ATM … |
| 1.3.6.1.4.1.9.9.356 | ciscoVoiceToneCadenceMIB | 3 | 30 | The MIB defines the attributes of the programmable tones specified in ITU-T E.180 Supplement 2. Each country has its own regulati… |
| 1.3.6.1.4.1.9.9.358 | ciscoBbsmMIB | 3 | 20 | This mib is designed to send BBSM specific notifications. There are variables that contain detail data that are bind to a notifi… |
| 1.3.6.1.4.1.9.9.359 | ciscoLicenseMIB | 3 | 52 | This MIB module provides objects to view the features and services that are licensed to run on a system (usually a network entity… |
| 1.3.6.1.4.1.9.9.360 | ciscoImageUpgradeMIB | 3 | 101 | This mib provides, objects to upgrade images on modules in the system, objects showing the status of the upgrade operation, and o… |
| 1.3.6.1.4.1.9.9.361 | ciscoCommonRolesMIB | 3 | 40 | MIB module for managing the common roles between access methods like Command Line Interface (CLI), SNMP and XML interfaces. Every … |
| 1.3.6.1.4.1.9.9.362 | ciscoPortStormControlMIB | 3 | 43 | The MIB module for managing Cisco Port Storm Control. |
| 1.3.6.1.4.1.9.9.363 | ciscoFcSpanMIB | 2 | 49 | MIB module for displaying and configuring Switched Port Analyzer(SPAN) related features in a Fibre Channel device. SPAN is a featu… |
| 1.3.6.1.4.1.9.9.364 | ciscoPsmMIB | 3 | 213 | The MIB module for the management of the Port Security Manager (PSM). The PSM consists of 2 aspects: Port binding and Fabric bindi… |
| 1.3.6.1.4.1.9.9.365 | ciscoFCCMIB | 3 | 42 | The MIB module for the management of Fibre Channel Congestion Control(FCC). FCC is a Cisco proprietary flow control mechanism tha… |
| 1.3.6.1.4.1.9.9.367 | ciscoAAAServerExtMIB | 2 | 77 | This MIB is an extension to the CISCO-AAA-SERVER-MIB. This MIB module enhances the 'casConfigTable' to include other types of Ser… |
| 1.3.6.1.4.1.9.9.368 | 368 | 0 | 0 | Cisco Content Services (CSS) switch product, also known as Arrowpoint, for version 7.40 and later |
| 1.3.6.1.4.1.9.9.369 | ciscoLicenseMgrMIB | 3 | 102 | The MIB module for a method of managing license files on the system. Licensing mechanism provides more flexibility in supporting v… |
| 1.3.6.1.4.1.9.9.371 | ciscoIvrMIB | 3 | 192 | The MIB module for the management of Inter-VSAN routing within the framework of Cisco's Inter-VSAN Routing (IVR) Architecture. IV… |
| 1.3.6.1.4.1.9.9.372 | ciscoIsnsClientMIB | 3 | 16 | MIB module for monitoring and configuring Internet Storage Name Service (iSNS) client. |
| 1.3.6.1.4.1.9.9.373 | ciscoFdmiMIB | 3 | 47 | Fabric Device Management Interface (FDMI) MIB. This MIB module defines objects for managing the devices such as HBA (Host Bus Ada… |
| 1.3.6.1.4.1.9.9.374 | ciscoDynamicArpInspectionMIB | 3 | 82 | The MIB module is for configuration of Dynamic ARP Inspection feature. Dynamic ARP Inspection is a security mechanism which valid… |
| 1.3.6.1.4.1.9.9.375 | ciscoFiconMIB | 3 | 176 | This is the FICON (FIber CONnection) MIB module. FICON is an IBM standard of transport mechanism for communication between the ma… |
| 1.3.6.1.4.1.9.9.376 | ciscoSVIAutostateMIB | 3 | 19 | The MIB module is for configuration of the switch virtual interface (SVI) autostate feature. Autostate feature is a mechanism to … |
| 1.3.6.1.4.1.9.9.377 | ciscoFeatureCtrlMIB | 3 | 53 | There are two types of features in the system: - Regular features - Optional features The Regular features may or may not need t… |
| 1.3.6.1.4.1.9.9.378 | ciscoSvcInterfaceMIB | 3 | 115 | MIB module for displaying and configuring SVC (SAN Volume Controller) related features in the Storage Area Network (SAN) switches… |
| 1.3.6.1.4.1.9.9.379 | ciscoItpmMIB | 3 | 47 | The MIB for providing information related to monitoring SS7 links. This information can be used to manage the state of software u… |
| 1.3.6.1.4.1.9.9.380 | ciscoDhcpSnoopingMIB | 3 | 127 | The MIB module is for configuration of DHCP Snooping feature. DHCP Snooping is a security mechanism which uses information gleane… |
| 1.3.6.1.4.1.9.9.381 | ciscoDiffServExtMIB | 2 | 49 | This MIB is a Cisco extension to the DIFFSERV-MIB, RFC 3289. This MIB defines a Fibre Channel (FC) Multi Field filter to be used i… |
| 1.3.6.1.4.1.9.9.383 | ciscoCidsMIB | 3 | 183 | Cisco Intrusion Detection System MIB. Provides trap definitions for the evAlert and evError elements of the IDIOM (Intrusion Det… |