CISCO-PSD-CLIENT-MIB
The CISCO-PSD-CLIENT-MIB manages the Persistent Storage Device (PSD) client functionality on Cisco GGSN and CSG platforms to monitor the operational state (up/down/full) of PSD servers and configure data-store parameters for GTP' charging protocol sessions. This module ensures the reliable buffering and automatic retrieval of Call Detail Records (CDRs) when Charging Gateways (CG) are unavailable, preventing data loss during GGSN memory exhaustion or CG failures.
Imported Objects
Objects
32 total| Object Name |
|---|
ciscoPsdClientMIBThis 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. MODULE-IDENTITY .1.3.6.1.4.1.9.9.495 |
ciscoPsdClientMIBNotifs OBJECT IDENTIFIER .1.3.6.1.4.1.9.9.495.0 |
cPsdClientDownNotifA notification of this type is generated when the
PSD server goes DOWN.
If the PSD client was in write/retrieving state, then
that operation shall be be stopped. NOTIFICATION-TYPE .1.3.6.1.4.1.9.9.495.0.1 |
cPsdClientUpNotifA notification of this type is generated when the
PSD server comes UP.
A GTP' path will be created fulfilling all the specific
requirements of the PSD interface. NOTIFICATION-TYPE .1.3.6.1.4.1.9.9.495.0.2 |
cPsdClientDiskFullNotifA notification of this type is generated when the
PSD server's disk become full.
If the disk of writable PSD server becomes full, the
client shall not be able to write any CDR into the
server. It shall then behave as a retrieve only PSD
server. NOTIFICATION-TYPE .1.3.6.1.4.1.9.9.495.0.3 |
ciscoPsdClientMIBObjects OBJECT IDENTIFIER .1.3.6.1.4.1.9.9.495.1 |
ciscoPsdClientStatistics OBJECT IDENTIFIER .1.3.6.1.4.1.9.9.495.1.1 |
cPsdClientDSWriteReqThe number of Data Record Transfer request (for write)
messages sent to the PSD server.
This counter is incremented when the FIFO write request
is sent to the PSD server from the client.ro Counter32 .1.3.6.1.4.1.9.9.495.1.1.1 |
cPsdClientDSReadReqThe number of Data Record Transfer request (for read)
messages sent to PSD server.
This counter is incremented when the FIFO read request
message is sent to PSD server.ro Counter32 .1.3.6.1.4.1.9.9.495.1.1.2 |
cPsdClientDSRdWrRetransThe number of Data Record Transfer Request
(retransmission) messages sent to the PSD server.
The PSD does not differentiate between a retransmission
and original request. So, this counter together with
the above two counters cPsdClientDSReadReq/
cPsdClientDSWriteReq can be used to tally the number of
messages received by the PSD client.
This counter is incremented when the FIFO read/write
retransmission messages are sent to PSD server.ro Counter32 .1.3.6.1.4.1.9.9.495.1.1.3 |
cPsdClientDSDiskFullTransThe number of state transitions made by the PSD from
state 'disk available' to 'disk full'.
This counter is incremented when client receives the
disk full indication from PSD server.ro Counter32 .1.3.6.1.4.1.9.9.495.1.1.4 |
ciscoPsdClientNotifMgmt OBJECT IDENTIFIER .1.3.6.1.4.1.9.9.495.1.2 |
cPsdClientNotifEnableThis object specifies whether the agent should
generate the notifications defined in this MIB module.
If the value of this object is 'true' it enables the
device to generate the notifications.
If the value of this object is 'false' it disables the
device from generating the notifications.rw TruthValue (SNMPv2-TC) .1.3.6.1.4.1.9.9.495.1.2.1 |
ciscoPsdClientConfigurations OBJECT IDENTIFIER .1.3.6.1.4.1.9.9.495.1.3 |
cPsdClientDSTableA table consisting of entries for data-store(DS) and
auto-retrieval configurations.
In order to minimize the performance/memory impact on
the PSD client, as well as not to overwhelm the CG
with both live CDRs and retrieved CDRs, the maximum
retrieval rate from PSD server to GGSN is limited and
can be configured by the user. SEQUENCE OF CPsdClientDSEntry .1.3.6.1.4.1.9.9.495.1.3.1 |
cPsdClientDSEntryEach entry contains the configuration for
auto-retrieval and also maximum retrieval value if
auto-retrieval is enabled. CPsdClientDSEntry .1.3.6.1.4.1.9.9.495.1.3.1.1 |
cPsdClientDSNameThis object contains the name of the configured
data-store SnmpAdminString .1.3.6.1.4.1.9.9.495.1.3.1.1.1 |
cPsdClientDSAutoRetrieveThis object is used to enable/disable the CDR
auto-retrieval functionality.
If value of this object is set to 'true',
auto-retrieval is enabled.
If value of this object is set to 'false',
auto-retrieval is disabled.rw TruthValue (SNMPv2-TC) .1.3.6.1.4.1.9.9.495.1.3.1.1.2 |
cPsdClientDSMaxRetrieveThis object used to specify the maximum retrieval
value, when auto retrieve is enabled, i.e when the
value of the corresponding instance of
cPsdClientDSAutoRetrieve is set to 'true'.rw Integer32 .1.3.6.1.4.1.9.9.495.1.3.1.1.3 |
cPsdClientDSRowStatusThe status of this conceptual row. This object is
used to create a row or delete a existing row in a
table.rw RowStatus (SNMPv2-TC) .1.3.6.1.4.1.9.9.495.1.3.1.1.4 |
cPsdClientDSServerTableThe table contains the list of the PSD servers used to
write/retrieve the CDRs. SEQUENCE OF CPsdClientDSServerEntry .1.3.6.1.4.1.9.9.495.1.3.2 |
cPsdClientDSServerEntryThis entry contains a description of the PSD server. CPsdClientDSServerEntry .1.3.6.1.4.1.9.9.495.1.3.2.1 |
cPsdClientDSServerAddressTypeThis object indicates the type of Internet address of
the PSD server. InetAddressType (INET-ADDRESS-MIB) .1.3.6.1.4.1.9.9.495.1.3.2.1.1 |
cPsdClientDSServerAddressThe object specifies the Internet address of the PSD
server. The type of address of an instance of this object
is determined by the value of the corresponding instance
of cPsdClientDSServerAddressType. InetAddress .1.3.6.1.4.1.9.9.495.1.3.2.1.2 |
cPsdClientDSRetrieveOnlyThe object represents that, the PSD server can be
configured either as write/retrievable or as
retrievable only.
If the value of this object is set to 'true', the PSD
server (the value of the corresponding instance of
cPsdClientDSServerAddress) shall not be used for
writing the CDRs.
If the value of this object is set to 'false', the PSD
server (the value of the corresponding instance of
cPsdClientDSServerAddress) shall be used for writing
the CDRs as well as retrieving the CDRs.rw TruthValue (SNMPv2-TC) .1.3.6.1.4.1.9.9.495.1.3.2.1.3 |
cPsdClientDSServerRowStatusThe status of this conceptual row. This object will
create a row or delete a existing row in a table.rw RowStatus (SNMPv2-TC) .1.3.6.1.4.1.9.9.495.1.3.2.1.4 |
ciscoPsdClientNotifInfo OBJECT IDENTIFIER .1.3.6.1.4.1.9.9.495.1.4 |
cPsdClientNotifDSServerAddrTypeThis object indicates the type of Internet address of
the Data-Store server.ro InetAddressType (INET-ADDRESS-MIB) .1.3.6.1.4.1.9.9.495.1.4.1 |
cPsdClientNotifDSServerAddressThis object specifies the Internet address of the
Data-Store server . The type of address of an instance
of this object is determined by the value of
cPsdClientNotifDSServerAddrType.ro InetAddress (INET-ADDRESS-MIB) .1.3.6.1.4.1.9.9.495.1.4.2 |
ciscoPsdClientMIBConform OBJECT IDENTIFIER .1.3.6.1.4.1.9.9.495.2 |
cPsdClientMIBCompliances OBJECT IDENTIFIER .1.3.6.1.4.1.9.9.495.2.1 |
cPsdClientMIBGroups OBJECT IDENTIFIER .1.3.6.1.4.1.9.9.495.2.2 |
More MIBs from Cisco
Browse all CiscoMIBs →The CISCO-ENTITY-VENDORTYPE-OID-MIB maps Cisco-specific hardware component identifiers to the ENTITY-MIB's entPhysicalTable, enabling precise differentiation of physical device types such as line cards, power supplies, and fans within Cisco infrastructure. This mapping ensures that SNMP management systems can accurately correlate physical inventory entries with vendor-specific component definitions for accurate device discovery and monitoring.
The CISCO-UNIFIED-COMPUTING-EQUIPMENT-MIB provides SNMP-based monitoring and management of Cisco Unified Computing System (UCS) hardware components, including chassis, blades, fabric interconnects, and power supplies. It exposes critical operational metrics such as device status, port states, temperature readings, fan speeds, and power consumption data for infrastructure health assessment.
The CISCO-UNIFIED-COMPUTING-ADAPTOR-MIB enables SNMP-based monitoring and management of physical and virtual network adapter interfaces, including link status, traffic counters, error statistics, and port configuration parameters, within the Cisco Unified Computing System (UCS) fabric interconnects and blade servers.
The CISCO-UNIFIED-COMPUTING-TC-MIB module defines standard textual conventions and data type definitions required for monitoring Cisco Unified Computing System (UCS) hardware components, including server blades, fabric interconnects, and chassis resources. These definitions enable consistent interpretation of specific UCS metrics such as power supply status, fan speeds, thermal readings, and port utilization across SNMP management applications.
The CISCO-UNIFIED-COMPUTING-FABRIC-MIB enables SNMP-based monitoring and management of the Cisco UCS Fabric Interconnects and associated fabric switching infrastructure, exposing metrics for port states, link utilization, error counters, and fabric topology status. It facilitates granular visibility into the physical and logical fabric layers, including uplink/downlink interfaces, VLAN configurations, and fabric failover conditions within the unified computing environment.
The STARENT-MIB module provides SNMP management and monitoring capabilities for Cisco ASR 5000 and ASR 5500 multimedia core platforms, specifically exposing metrics related to 2G/3G/4G and WiFi subscriber sessions, inline service states, and carrier-class high-availability status.