Reference record for OID 1.3.6.1.4.1.9.9.495
- Parent
- 1.3.6.1.4.1.9.9 (ciscoMgmt)
- Node code
- 495
- Node name
- ciscoPsdClientMIB
- Numeric OID
- 1.3.6.1.4.1.9.9.495
- URN notation
- urn:oid:1.3.6.1.4.1.9.9.495
- Type
- OBJECT IDENTIFIER
- ASN.1 notation
-
{1 3 6 1 4 1 9 9 495}
- {iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprise(1) cisco(9) ciscoMgmt(9) ciscoPsdClientMIB(495)}
- {iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprise(1) me1200(9) ciscoMgmt(9) ciscoPsdClientMIB(495)}
- {iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprises(1) cisco(9) ciscoMgmt(9) ciscoPsdClientMIB(495)}
- {iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprises(1) me1200(9) ciscoMgmt(9) ciscoPsdClientMIB(495)}
- {iso(1) identified-organization(3) dod(6) internet(1) private(4) ldap-enterprise(1) cisco(9) ciscoMgmt(9) ciscoPsdClientMIB(495)}
- {iso(1) identified-organization(3) dod(6) internet(1) private(4) ldap-enterprise(1) me1200(9) ciscoMgmt(9) ciscoPsdClientMIB(495)}
- {iso(1) identified-organization(3) dod(6) internet(1) private(4) vendor-objects(1) cisco(9) ciscoMgmt(9) ciscoPsdClientMIB(495)}
- {iso(1) identified-organization(3) dod(6) internet(1) private(4) vendor-objects(1) me1200(9) ciscoMgmt(9) ciscoPsdClientMIB(495)}
- {iso(1) org(3) dod(6) internet(1) private(4) enterprise(1) cisco(9) ciscoMgmt(9) ciscoPsdClientMIB(495)}
- {iso(1) org(3) dod(6) internet(1) private(4) enterprise(1) me1200(9) ciscoMgmt(9) ciscoPsdClientMIB(495)}
- {iso(1) org(3) dod(6) internet(1) private(4) enterprises(1) cisco(9) ciscoMgmt(9) ciscoPsdClientMIB(495)}
- {iso(1) org(3) dod(6) internet(1) private(4) enterprises(1) me1200(9) ciscoMgmt(9) ciscoPsdClientMIB(495)}
- {iso(1) org(3) dod(6) internet(1) private(4) ldap-enterprise(1) cisco(9) ciscoMgmt(9) ciscoPsdClientMIB(495)}
- {iso(1) org(3) dod(6) internet(1) private(4) ldap-enterprise(1) me1200(9) ciscoMgmt(9) ciscoPsdClientMIB(495)}
- {iso(1) org(3) dod(6) internet(1) private(4) vendor-objects(1) cisco(9) ciscoMgmt(9) ciscoPsdClientMIB(495)}
- {iso(1) org(3) dod(6) internet(1) private(4) vendor-objects(1) me1200(9) ciscoMgmt(9) ciscoPsdClientMIB(495)}
- Additional combinations skipped.
- OID-IRI notation
- /1/3/6/1/4/1/9/9/495
- /ISO/Identified-Organization/6/1/4/1/9/9/495
- /ISO/3/6/1/4/1/9/9/495
- Named path variants
- /iso/identified-organization/dod/internet/private/enterprise/cisco/ciscoMgmt/ciscoPsdClientMIB
- /iso/identified-organization/dod/internet/private/enterprise/me1200/ciscoMgmt/ciscoPsdClientMIB
- /iso/identified-organization/dod/internet/private/enterprise/Cisco/ciscoMgmt/ciscoPsdClientMIB
- /iso/identified-organization/dod/internet/private/enterprises/cisco/ciscoMgmt/ciscoPsdClientMIB
- /iso/identified-organization/dod/internet/private/enterprises/me1200/ciscoMgmt/ciscoPsdClientMIB
- /iso/identified-organization/dod/internet/private/enterprises/Cisco/ciscoMgmt/ciscoPsdClientMIB
- /iso/identified-organization/dod/internet/private/ldap-enterprise/cisco/ciscoMgmt/ciscoPsdClientMIB
- /iso/identified-organization/dod/internet/private/ldap-enterprise/me1200/ciscoMgmt/ciscoPsdClientMIB
- /iso/identified-organization/dod/internet/private/ldap-enterprise/Cisco/ciscoMgmt/ciscoPsdClientMIB
- /iso/identified-organization/dod/internet/private/vendor-objects/cisco/ciscoMgmt/ciscoPsdClientMIB
- /iso/identified-organization/dod/internet/private/vendor-objects/me1200/ciscoMgmt/ciscoPsdClientMIB
- /iso/identified-organization/dod/internet/private/vendor-objects/Cisco/ciscoMgmt/ciscoPsdClientMIB
- /iso/org/dod/internet/private/enterprise/cisco/ciscoMgmt/ciscoPsdClientMIB
- /iso/org/dod/internet/private/enterprise/me1200/ciscoMgmt/ciscoPsdClientMIB
- /iso/org/dod/internet/private/enterprise/Cisco/ciscoMgmt/ciscoPsdClientMIB
- /iso/org/dod/internet/private/enterprises/cisco/ciscoMgmt/ciscoPsdClientMIB
- Additional combinations skipped.
Descriptions
Descriptions may differ between sources. The primary description is shown first.
Primary description: Circitor
functionality of the Persistent Storage Device(PSD).
This MIB instrumentation is for configuring
data-store(PSD client) feature on GGSN and monitoring
the state of the PSD server(up/down/full).
The Cisco Persistent Storage Device(PSD) is an
extension to existing storage on the Cisco Content
Services Gateway(CSG).
The GGSN currently allows sending of the CDRs to an
active CG, while allowing up to two standby CG's to
be configured. When all the configured CG's become
unavailable, the CDRs get stored at the GGSN and
start using up GGSN resources such as memory. As the
amount of memory is limited on GGSN and failure of
GGSN shall lead to losing these stored CDRs.
Using PSD as temporary storage, shall avoid losses
due to these problems. When all the configured CG's
are unavailable, GGSN needs to backup the live closed
CDR's to a PSD. When any of the CG's shall become
available, GGSN shall retrieve the stored CDR's
automatically from the PSD and forwards them to the
active CG.
PSD supports the charging protocol(GTP'), version 0
with a few private extensions, which is used to
facilitate the required functionality via UDP.
Acronyms and terms:
CDR Call Detail Record
CID Charging Identification
CG Charging Gateway
CGF Charging Gateway Functionality
DS Data-Store
ETSI European Telecommunications Standards
Institute
Ga Name of the interface between SGSN/GGSN and
CG
Gi Name of the interface between GGSN and PDN
Gn Name of the interface between GGSN and SGSN
G-CDR Gateway GPRS Support Node-Call Detail Record
GGSN Gateway GPRS Support Node
GPRS General Packet Radio Service
GSM Global System for Mobile communication
GTP GPRS Tunneling Protocol
GTP' GTP enhanced for charging
IE Information Element
MS Mobile Station
PDN Packet Data Network
PDP Packet Data Protocol
SGSN Serving GPRS support Node
TOS Type of Service.
PSD Persistence Storage Device.
Parsed from file CISCO-PSD-CLIENT-MIB.mib
Module: CISCO-PSD-CLIENT-MIB
Source file: Download CISCO-PSD-CLIENT-MIB.mib
Publisher path: Mibs; 21,151 bytes
Alternative description: Cisco
functionality of the Persistent Storage Device(PSD).
This MIB instrumentation is for configuring
data-store(PSD client) feature on GGSN and monitoring
the state of the PSD server(up/down/full).
The Cisco Persistent Storage Device(PSD) is an
extension to existing storage on the Cisco Content
Services Gateway(CSG).
The GGSN currently allows sending of the CDRs to an
active CG, while allowing up to two standby CG's to
be configured. When all the configured CG's become
unavailable, the CDRs get stored at the GGSN and
start using up GGSN resources such as memory. As the
amount of memory is limited on GGSN and failure of
GGSN shall lead to losing these stored CDRs.
Using PSD as temporary storage, shall avoid losses
due to these problems. When all the configured CG's
are unavailable, GGSN needs to backup the live closed
CDR's to a PSD. When any of the CG's shall become
available, GGSN shall retrieve the stored CDR's
automatically from the PSD and forwards them to the
active CG.
PSD supports the charging protocol(GTP'), version 0
with a few private extensions, which is used to
facilitate the required functionality via UDP.
Acronyms and terms:
CDR Call Detail Record
CID Charging Identification
CG Charging Gateway
CGF Charging Gateway Functionality
DS Data-Store
ETSI European Telecommunications Standards
Institute
Ga Name of the interface between SGSN/GGSN and
CG
Gi Name of the interface between GGSN and PDN
Gn Name of the interface between GGSN and SGSN
G-CDR Gateway GPRS Support Node-Call Detail Record
GGSN Gateway GPRS Support Node
GPRS General Packet Radio Service
GSM Global System for Mobile communication
GTP GPRS Tunneling Protocol
GTP' GTP enhanced for charging
IE Information Element
MS Mobile Station
PDN Packet Data Network
PDP Packet Data Protocol
SGSN Serving GPRS support Node
TOS Type of Service.
PSD Persistence Storage Device.
Source file: Download CISCO-PSD-CLIENT-MIB.my · Publisher's file
Copy from Netdisco; File: cisco/CISCO-PSD-CLIENT-MIB.my; 20,588 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-PSD-CLIENT-MIB · Publisher's file
Copy from Observium Community; File: cisco/CISCO-PSD-CLIENT-MIB; 20,588 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-PSD-CLIENT-MIB.my · Publisher's file
Publisher path: cisco/cisco-mibs/main/v2/CISCO-PSD-CLIENT-MIB.my; 20,588 bytes
Alternative description: MIBdepot
functionality of the Persistent Storage Device(PSD).
This MIB instrumentation is for configuring
data-store(PSD client) feature on GGSN and monitoring
the state of the PSD server(up/down/full).
The Cisco Persistent Storage Device(PSD) is an
extension to existing storage on the Cisco Content
Services Gateway(CSG).
The GGSN currently allows sending of the CDRs to an
active CG, while allowing up to two standby CG's to
be configured. When all the configured CG's become
unavailable, the CDRs get stored at the GGSN and
start using up GGSN resources such as memory. As the
amount of memory is limited on GGSN and failure of
GGSN shall lead to losing these stored CDRs.
Using PSD as temporary storage, shall avoid losses
due to these problems. When all the configured CG's
are unavailable, GGSN needs to backup the live closed
CDR's to a PSD. When any of the CG's shall become
available, GGSN shall retrieve the stored CDR's
automatically from the PSD and forwards them to the
active CG.
PSD supports the charging protocol(GTP'), version 0
with a few private extensions, which is used to
facilitate the required functionality via UDP.
Acronyms and terms:
CDR Call Detail Record
CID Charging Identification
CG Charging Gateway
CGF Charging Gateway Functionality
DS Data-Store
ETSI European Telecommunications Standards
Institute
Ga Name of the interface between SGSN/GGSN and
CG
Gi Name of the interface between GGSN and PDN
Gn Name of the interface between GGSN and SGSN
G-CDR Gateway GPRS Support Node-Call Detail Record
GGSN Gateway GPRS Support Node
GPRS General Packet Radio Service
GSM Global System for Mobile communication
GTP GPRS Tunneling Protocol
GTP' GTP enhanced for charging
IE Information Element
MS Mobile Station
PDN Packet Data Network
PDP Packet Data Protocol
SGSN Serving GPRS support Node
TOS Type of Service.
PSD Persistence Storage Device.
Source file: Download CISCO-PSD-CLIENT-MIB.my.txt
File: cisco/CISCO-PSD-CLIENT-MIB.my.txt; 21,151 bytes
Information from Circitor
ciscoPsdClientMIB MODULE-IDENTITY
LAST-UPDATED "200508241800Z"
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-gprs@cisco.com"
DESCRIPTION
"This MIB module manages the client side
functionality of the Persistent Storage Device(PSD).
This MIB instrumentation is for configuring
data-store(PSD client) feature on GGSN and monitoring
the state of the PSD server(up/down/full).
The Cisco Persistent Storage Device(PSD) is an
extension to existing storage on the Cisco Content
Services Gateway(CSG).
The GGSN currently allows sending of the CDRs to an
active CG, while allowing up to two standby CG's to
be configured. When all the configured CG's become
unavailable, the CDRs get stored at the GGSN and
start using up GGSN resources such as memory. As the
amount of memory is limited on GGSN and failure of
GGSN shall lead to losing these stored CDRs.
Using PSD as temporary storage, shall avoid losses
due to these problems. When all the configured CG's
are unavailable, GGSN needs to backup the live closed
CDR's to a PSD. When any of the CG's shall become
available, GGSN shall retrieve the stored CDR's
automatically from the PSD and forwards them to the
active CG.
PSD supports the charging protocol(GTP'), version 0
with a few private extensions, which is used to
facilitate the required functionality via UDP.
Acronyms and terms:
CDR Call Detail Record
CID Charging Identification
CG Charging Gateway
CGF Charging Gateway Functionality
DS Data-Store
ETSI European Telecommunications Standards
Institute
Ga Name of the interface between SGSN/GGSN and
CG
Gi Name of the interface between GGSN and PDN
Gn Name of the interface between GGSN and SGSN
G-CDR Gateway GPRS Support Node-Call Detail Record
GGSN Gateway GPRS Support Node
GPRS General Packet Radio Service
GSM Global System for Mobile communication
GTP GPRS Tunneling Protocol
GTP' GTP enhanced for charging
IE Information Element
MS Mobile Station
PDN Packet Data Network
PDP Packet Data Protocol
SGSN Serving GPRS support Node
TOS Type of Service.
PSD Persistence Storage Device."
REVISION "200508241800Z"
DESCRIPTION
"Initial version of this MIB module."
::= {ciscoMgmt 495 }
Information from Cisco SMIv1
Source file: Download CISCO-PSD-CLIENT-MIB-V1SMI.my · Publisher's file
Publisher path: cisco/cisco-mibs/main/v1/CISCO-PSD-CLIENT-MIB-V1SMI.my; 16,848 bytes
Source file: Download CISCO-PSD-CLIENT-MIB-V1SMI.my.txt
File: cisco/CISCO-PSD-CLIENT-MIB-V1SMI.my.txt; 17,385 bytes
ciscoPsdClientMIB OBJECT IDENTIFIER ::= { ciscoMgmt 495 }
Information from OID Repository
Information from MIBdepot
ciscoPsdClientMIB MODULE-IDENTITY
LAST-UPDATED "200508241800Z"
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-gprs@cisco.com"
DESCRIPTION
"This MIB module manages the client side
functionality of the Persistent Storage Device(PSD).
This MIB instrumentation is for configuring
data-store(PSD client) feature on GGSN and monitoring
the state of the PSD server(up/down/full).
The Cisco Persistent Storage Device(PSD) is an
extension to existing storage on the Cisco Content
Services Gateway(CSG).
The GGSN currently allows sending of the CDRs to an
active CG, while allowing up to two standby CG's to
be configured. When all the configured CG's become
unavailable, the CDRs get stored at the GGSN and
start using up GGSN resources such as memory. As the
amount of memory is limited on GGSN and failure of
GGSN shall lead to losing these stored CDRs.
Using PSD as temporary storage, shall avoid losses
due to these problems. When all the configured CG's
are unavailable, GGSN needs to backup the live closed
CDR's to a PSD. When any of the CG's shall become
available, GGSN shall retrieve the stored CDR's
automatically from the PSD and forwards them to the
active CG.
PSD supports the charging protocol(GTP'), version 0
with a few private extensions, which is used to
facilitate the required functionality via UDP.
Acronyms and terms:
CDR Call Detail Record
CID Charging Identification
CG Charging Gateway
CGF Charging Gateway Functionality
DS Data-Store
ETSI European Telecommunications Standards
Institute
Ga Name of the interface between SGSN/GGSN and
CG
Gi Name of the interface between GGSN and PDN
Gn Name of the interface between GGSN and SGSN
G-CDR Gateway GPRS Support Node-Call Detail Record
GGSN Gateway GPRS Support Node
GPRS General Packet Radio Service
GSM Global System for Mobile communication
GTP GPRS Tunneling Protocol
GTP' GTP enhanced for charging
IE Information Element
MS Mobile Station
PDN Packet Data Network
PDP Packet Data Protocol
SGSN Serving GPRS support Node
TOS Type of Service.
PSD Persistence Storage Device."
REVISION "200508241800Z"
DESCRIPTION
"Initial version of this MIB module."
::= {ciscoMgmt 495 }
Information from Cisco
ciscoPsdClientMIB MODULE-IDENTITY
LAST-UPDATED "200508241800Z"
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-gprs@cisco.com"
DESCRIPTION
"This MIB module manages the client side
functionality of the Persistent Storage Device(PSD).
This MIB instrumentation is for configuring
data-store(PSD client) feature on GGSN and monitoring
the state of the PSD server(up/down/full).
The Cisco Persistent Storage Device(PSD) is an
extension to existing storage on the Cisco Content
Services Gateway(CSG).
The GGSN currently allows sending of the CDRs to an
active CG, while allowing up to two standby CG's to
be configured. When all the configured CG's become
unavailable, the CDRs get stored at the GGSN and
start using up GGSN resources such as memory. As the
amount of memory is limited on GGSN and failure of
GGSN shall lead to losing these stored CDRs.
Using PSD as temporary storage, shall avoid losses
due to these problems. When all the configured CG's
are unavailable, GGSN needs to backup the live closed
CDR's to a PSD. When any of the CG's shall become
available, GGSN shall retrieve the stored CDR's
automatically from the PSD and forwards them to the
active CG.
PSD supports the charging protocol(GTP'), version 0
with a few private extensions, which is used to
facilitate the required functionality via UDP.
Acronyms and terms:
CDR Call Detail Record
CID Charging Identification
CG Charging Gateway
CGF Charging Gateway Functionality
DS Data-Store
ETSI European Telecommunications Standards
Institute
Ga Name of the interface between SGSN/GGSN and
CG
Gi Name of the interface between GGSN and PDN
Gn Name of the interface between GGSN and SGSN
G-CDR Gateway GPRS Support Node-Call Detail Record
GGSN Gateway GPRS Support Node
GPRS General Packet Radio Service
GSM Global System for Mobile communication
GTP GPRS Tunneling Protocol
GTP' GTP enhanced for charging
IE Information Element
MS Mobile Station
PDN Packet Data Network
PDP Packet Data Protocol
SGSN Serving GPRS support Node
TOS Type of Service.
PSD Persistence Storage Device."
REVISION "200508241800Z"
DESCRIPTION
"Initial version of this MIB module."
::= {ciscoMgmt 495 }
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.495.0 | ciscoPsdClientMIBNotifs | 3 | 3 | |
| 1.3.6.1.4.1.9.9.495.1 | ciscoPsdClientMIBObjects | 4 | 30 | |
| 1.3.6.1.4.1.9.9.495.2 | ciscoPsdClientMIBConform | 2 | 8 |
Siblings (706)
| OID | Name | Direct children | Descendants | Description |
|---|---|---|---|---|
| 1.3.6.1.4.1.9.9.514 | ciscoLwappTextualConventions | 0 | 0 | This module defines textual conventions used throughout the Cisco enterprise MIBs designed for implementation on Central Controlle… |
| 1.3.6.1.4.1.9.9.515 | ciscoLwappWebAuthMIB | 4 | 133 | 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.516 | ciscoLwappLinkTestMIB | 3 | 57 | 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.517 | ciscoLwappReapMIB | 3 | 342 | 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.518 | ciscoLwappMfpMIB | 4 | 68 | 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.519 | ciscoLwappIdsMIB | 3 | 28 | 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.520 | ciscoLwappCcxRmMIB | 3 | 45 | 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.521 | ciscoLwappWlanSecurityMIB | 3 | 77 | 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.522 | ciscoLwappDot11ClientCalibMIB | 3 | 55 | 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.523 | ciscoLwappClRoamMIB | 3 | 63 | 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.524 | ciscoLwappQosMIB | 3 | 491 | 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.525 | ciscoLwappTsmMIB | 3 | 57 | 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.529 | ciscoItpMsuRatesMIB | 3 | 61 | This MIB provides information used to manage the number of MTP3 MSUs transmitted and received per processor. Many of the higher … |
| 1.3.6.1.4.1.9.9.530 | ciscoNacTcMIB | 0 | 0 | This module defines the textual conventions for Cisco Network Admission Control(NAC) system. The Cisco Network Admission Control … |
| 1.3.6.1.4.1.9.9.532 | ciscoNATExtMIB | 3 | 13 | This MIB is an extension to the NAT-MIB. This MIB module includes objects for providing the NAT related statistics. Acronyms: NAT… |
| 1.3.6.1.4.1.9.9.533 | ciscoCbpTargetMIB | 3 | 25 | This MIB module defines the managed objects for representing targets which have class-based policy mappings. A target can be any… |
| 1.3.6.1.4.1.9.9.543 | ciscoLicenseMgmtMIB | 3 | 131 | The MIB module for managing licenses on the system. The licensing mechanism provides flexibility to enforce licensing for various… |
| 1.3.6.1.4.1.9.9.548 | ciscoErrDisableMIB | 3 | 45 | This MIB module provides the ability for a Network Management Station (NMS) to configure and monitor the error-disable feature vi… |
| 1.3.6.1.4.1.9.9.572 | ciscoRttMonIPExtMIB | 2 | 57 | This MIB contains extensions to tables in CISCO-RTTMON-MIB to support IP-layer extensions, specifically IPv6 addresses and other … |
| 1.3.6.1.4.1.9.9.573 | ciscoQosTcMIB | 0 | 0 | This module defines the textual conventions used within Cisco Qos MIBs. |
| 1.3.6.1.4.1.9.9.576 | ciscoLwappMobilityMIB | 3 | 106 | 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.577 | ciscoLwappAclMIB | 3 | 47 | 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.578 | ciscoRoutePoliciesMIB | 3 | 5 | This module provides a subtree to define OIDs so that various routing 'policies' used by Cisco routers can be expressed. This mod… |
| 1.3.6.1.4.1.9.9.580 | ciscoSwitchQosMIB | 3 | 295 | This MIB module extends the CISCO-CLASS-BASED-QOS-MIB by defining configuration and statistics information specific to the qualit… |
| 1.3.6.1.4.1.9.9.583 | ciscoGslbTcMIB | 0 | 0 | This MIB module defines Textual Conventions and OBJECT-IDENTITIES for use in documents defining management information base (MIBs… |
| 1.3.6.1.4.1.9.9.584 | ciscoEntityDiagTcMIB | 0 | 0 | This module defines the textual conventions used within Cisco Entity Diag MIB. |
| 1.3.6.1.4.1.9.9.585 | ciscoIpSlaEthernetMIB | 3 | 245 | This MIB module consists of two parts. 1) Auto-Ethernet-CFM Control: | | 2) ethernetJitter Stats: | | The first part defines a mechani… |
| 1.3.6.1.4.1.9.9.586 | ciscoNotificationControlMIB | 2 | 28 | This MIB provides network management support to regulate the transmission of notifications generated by a system providing networ… |
| 1.3.6.1.4.1.9.9.589 | ciscoGslbSystemMIB | 3 | 103 | This MIB module defines objects for network and system information of Global Server Load Balancer(GSLB) as a network device. A G… |
| 1.3.6.1.4.1.9.9.590 | ciscoCvpMIB | 3 | 255 | The Cisco Unified Customer Voice Portal (CVP) application integrates with both traditional time-division multiplexing (TDM) and I… |
| 1.3.6.1.4.1.9.9.592 | ciscoPrefPathMIB | 3 | 56 | The MIB module for the management of preferred path. This MIB enables managers to configure and monitor Preferred Path parameters. … |
| 1.3.6.1.4.1.9.9.593 | ciscoFcSdvMIB | 3 | 28 | This MIB instrumentation is for managing Fibre Channel (FC) SAN Device Virtualization (SDV) solution on Cisco Fibre Channel devic… |
| 1.3.6.1.4.1.9.9.594 | ciscoApplicationAccelerationMIB | 3 | 37 | This is a MIB for managing Application Acceleration System(s). This MIB includes instrumentation for providing the performance st… |
| 1.3.6.1.4.1.9.9.595 | ciscoGslbDnsMIB | 3 | 165 | The MIB defines objects for status and statistics information of DNS related operations of Global Server Load Balancer(GSLB). Th… |
| 1.3.6.1.4.1.9.9.597 | ciscoContentServicesMIB | 3 | 349 | Content Service is a capability to examine IP/TCP/UDP headers, payload and enable billing based on the content being provided. Ab… |
| 1.3.6.1.4.1.9.9.598 | ciscoLwappAAAMIB | 3 | 150 | This MIB is intended to be implemented on all those devices operating as Central Controllers (CC), that terminate the Light Weigh… |
| 1.3.6.1.4.1.9.9.599 | ciscoLwappDot11ClientMIB | 4 | 523 | 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.600 | ciscoGslbHealthMonMIB | 3 | 90 | The MIB defines objects related to global keepalive properties in GSLB devices. It contains the tables for keep alive configurat… |
| 1.3.6.1.4.1.9.9.601 | ciscoResilientEthernetProtocolMIB | 3 | 77 | This MIB module defines objects required for managing Resilient Ethernet Protocol (REP). Resilient Ethernet Protocol (REP) is a C… |
| 1.3.6.1.4.1.9.9.602 | ciscoPacketCaptureMIB | 3 | 103 | The MIB module for the management of packet capture feature. |
| 1.3.6.1.4.1.9.9.603 | ciscoThreatMitigationServiceMIB | 3 | 68 | This MIB provides management information about the Threat Mitigation Service(TMS) entity named 'Consumer'. TMS is part of Cisco's… |
| 1.3.6.1.4.1.9.9.604 | cdot1CfmMIB | 3 | 166 | Connectivity Fault Management module for managing IEEE 802.1ag |
| 1.3.6.1.4.1.9.9.606 | ciscoLwappMeshLinkTestMIB | 3 | 46 | ciscoLwappMeshLinkTestMIB MODULE-IDENTITY LAST-UPDATED "200702050000Z" ORGANIZATION "Cisco Systems Inc." CONTACT-INFO "Cisco Sy… |
| 1.3.6.1.4.1.9.9.607 | ciscoDot11HtPhyMIB | 3 | 71 | 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.610 | ciscoLwappRogueMIB | 4 | 134 | 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.611 | ciscoLwappDot11ClientCCXTextualConventions | 0 | 0 | This module defines the textual conventions used throughout the Cisco enterprise MIBs designed for implementation on Central Cont… |
| 1.3.6.1.4.1.9.9.612 | ciscoLwappDot11MIB | 3 | 158 | 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.613 | ciscoEvcMIB | 3 | 156 | Metro Ethernet services can support a wide range of applications and subscriber needs easily, efficiently and cost-effectively. … |
| 1.3.6.1.4.1.9.9.614 | ciscoLwappDot11LdapMIB | 3 | 33 | 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.615 | ciscoLwappRrmMIB | 3 | 175 | This MIB is intended to be implemented on all those devices operating as Central controllers, that terminate the Light Weight Acc… |