CISCO-PSD-CLIENT-MIB

        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.
    
Source file
CISCO-PSD-CLIENT-MIB
Last revised
Identity
ciscoPsdClientMIB
Base OID
1.3.6.1.4.1.9.9.495
Imported Objects
CISCO-SMI ciscoMgmt
INET-ADDRESS-MIB InetAddress InetAddressType
SNMP-FRAMEWORK-MIB SnmpAdminString
SNMPv2-CONF MODULE-COMPLIANCE (no object page) NOTIFICATION-GROUP (no object page) OBJECT-GROUP (no object page)
SNMPv2-SMI Counter32 Integer32 MODULE-IDENTITY (no object page) NOTIFICATION-TYPE (no object page) OBJECT-TYPE (no object page)
SNMPv2-TC RowStatus TruthValue
Net-SNMP examples using the cisco MIB directory Show commands

These commands use the standard Observium installation path and load the selected MIB variant before the RFC and Net-SNMP directories.

Translate the module identity
/usr/bin/snmptranslate -Pud -Ir -On -m 'CISCO-PSD-CLIENT-MIB' -M '/opt/observium/mibs/cisco:/opt/observium/mibs/rfc:/opt/observium/mibs/net-snmp' 'CISCO-PSD-CLIENT-MIB::ciscoPsdClientMIB'
Walk the MIB subtree
/usr/bin/snmpbulkwalk -v2c -c '<community>' -Pud -Ir -OQUs -m 'CISCO-PSD-CLIENT-MIB' -M '/opt/observium/mibs/cisco:/opt/observium/mibs/rfc:/opt/observium/mibs/net-snmp' 'udp:<hostname>:161' 'CISCO-PSD-CLIENT-MIB::ciscoPsdClientMIB'
How SNMP, Net-SNMP, MIB paths, and variants work
Objects (29)
.1.3.6.1.4.1.9.9.495
.1.3.6.1.4.1.9.9.495.0
.1.3.6.1.4.1.9.9.495.1
.1.3.6.1.4.1.9.9.495.1.1
.1.3.6.1.4.1.9.9.495.1.1.1
.1.3.6.1.4.1.9.9.495.1.1.2
.1.3.6.1.4.1.9.9.495.1.1.3
.1.3.6.1.4.1.9.9.495.1.1.4
.1.3.6.1.4.1.9.9.495.1.2
.1.3.6.1.4.1.9.9.495.1.2.1
.1.3.6.1.4.1.9.9.495.1.3
.1.3.6.1.4.1.9.9.495.1.3.1
.1.3.6.1.4.1.9.9.495.1.3.1.1
OctetString
.1.3.6.1.4.1.9.9.495.1.3.1.1.1
.1.3.6.1.4.1.9.9.495.1.3.1.1.2
messages/minuteInteger32
.1.3.6.1.4.1.9.9.495.1.3.1.1.3
.1.3.6.1.4.1.9.9.495.1.3.1.1.4
.1.3.6.1.4.1.9.9.495.1.3.2
.1.3.6.1.4.1.9.9.495.1.3.2.1
.1.3.6.1.4.1.9.9.495.1.3.2.1.1
OctetString
.1.3.6.1.4.1.9.9.495.1.3.2.1.2
.1.3.6.1.4.1.9.9.495.1.3.2.1.3
.1.3.6.1.4.1.9.9.495.1.3.2.1.4
.1.3.6.1.4.1.9.9.495.1.4
.1.3.6.1.4.1.9.9.495.1.4.1
.1.3.6.1.4.1.9.9.495.1.4.2
.1.3.6.1.4.1.9.9.495.2
.1.3.6.1.4.1.9.9.495.2.1
.1.3.6.1.4.1.9.9.495.2.2
Dependencies (6) 6 direct Show tree and compile order Hide dependency details

Each imported module is resolved in the importing module's source directory first, then through the normal default-variant rules.

Dependency tree
Dependency-first compile order
  1. SNMPv2-SMIrfc
  2. CISCO-SMIcisco
  3. SNMPv2-TCrfc
  4. INET-ADDRESS-MIBrfc
  5. SNMPv2-CONFrfc
  6. SNMP-FRAMEWORK-MIBrfc
  7. CISCO-PSD-CLIENT-MIBciscoselected
Conformance Groups (5)
A collection of objects providing Data Store
related statistics.
.1.3.6.1.4.1.9.9.495.2.2.1
A collection of objects providing Data Store related
configurations.
.1.3.6.1.4.1.9.9.495.2.2.2
A collection of Notifications.
.1.3.6.1.4.1.9.9.495.2.2.3
A collection of notification info objects on PSD.
.1.3.6.1.4.1.9.9.495.2.2.4
A collection of objects related with notification
management on PSD.
.1.3.6.1.4.1.9.9.495.2.2.5
Compliance Statements (1)

OID .1.3.6.1.4.1.9.9.495.2.1.1
The compliance statement for entities which implement
the CISCO PSD CLIENT MIB.
Required groups
Object refinements
ObjectAccessSyntaxDescription
cPsdClientDSRowStatus
active(1), createAndGo(4), destroy(6)
The states notInService(2), notReady(3) and
createAndWait(5) need not be supported.
cPsdClientDSServerRowStatus
active(1), createAndGo(4), destroy(6)
The states notInService(2), notReady(3) and
createAndWait(5) need not be supported.
Notifications / Traps (3)
NameOIDDescription
.1.3.6.1.4.1.9.9.495.0.1
A 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.
.1.3.6.1.4.1.9.9.495.0.2
A 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.
.1.3.6.1.4.1.9.9.495.0.3
A 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.