CISCO-PSD-CLIENT-MIB :: cPsdClientDSWriteReq

MIB Reference — IPNetwork Monitor · Updated October 05, 2026

All MIBs › CISCO-PSD-CLIENT-MIB › cPsdClientDSWriteReq

cPsdClientDSWriteReq

Module: CISCO-PSD-CLIENT-MIB

OID (symbolic): CISCO-PSD-CLIENT-MIB::cPsdClientDSWriteReq

OID (numeric): 1.3.6.1.4.1.9.9.495.1.1.1

Node type: OBJECT-TYPE

Type: Counter32

Access: read-only

Description: The 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.

What is cPsdClientDSWriteReq?

Counts the Data Record Transfer write requests the client has sent to the PSD (Persistent Storage Device) server, indicating how many FIFO write operations have been initiated.

Examples

Walk all instances (SNMPv2c):

snmpwalk -v2c -c public <target> 1.3.6.1.4.1.9.9.495.1.1.1
snmpwalk -v2c -c public <target> CISCO-PSD-CLIENT-MIB::cPsdClientDSWriteReq

Get a specific instance (index 1):

snmpget -v2c -c public <target> 1.3.6.1.4.1.9.9.495.1.1.1.1
snmpget -v2c -c public <target> CISCO-PSD-CLIENT-MIB::cPsdClientDSWriteReq.1

Start monitoring Cisco GGSN / Content Services Gateway (CSG) with a free 30-day trial of IPNetwork Monitor. Create custom SNMP monitor using the CISCO-PSD-CLIENT-MIB::cPsdClientDSWriteReq OID value, configure state conditions and alerts, and monitor any Cisco GGSN / Content Services Gateway (CSG) from a single console.

How to Use in IPNetwork Monitor

Select a Cisco GGSN / Content Services Gateway (CSG) as the target host to create a monitor — the SNMP service should be up and running on it. Click New Monitor, then check SNMP Custom on the Favorites tab, click Next, and confirm the host. On the next page, click Select... to open the built-in SNMP MIB Browser and type cPsdClientDSWriteReq into the Find box to locate it in the OID tree, then select it and click OK. The number of Data Record Transfer request (for write) messages sent to the PSD server. On the monitor's Main parameters page you can set the target's SNMP port (default 161), credentials, polling interval, and other settings — see the SNMP Monitor help for details. On the State conditions and Alerting tabs, configure when the monitor should change state and trigger an alert; since this is a Counter32-type OID, Value bounds is the most useful condition here — trigger an alert if the counter increases sharply between polls relative to its normal baseline, since an unexpected spike often reflects a real change in traffic or activity. Click Finish to create the monitor; you can adjust any parameter later.

OID Breakdown

Upper-level ancestors (8 from the standard OID tree / other modules)
Numeric OIDNameModule
1isoLANART-AGENT
1.3orgAirPair-MIB
1.3.6dodAirPair-MIB
1.3.6.1internetAirPair-MIB
1.3.6.1.4privateAirPair-MIB
1.3.6.1.4.1enterprisesAirPair-MIB
1.3.6.1.4.1.9ciscoCAT2600-MIB
1.3.6.1.4.1.9.9ciscoMgmtCISCO-SMI
Numeric OIDNameModule
1.3.6.1.4.1.9.9.495ciscoPsdClientMIBCISCO-PSD-CLIENT-MIB
1.3.6.1.4.1.9.9.495.1ciscoPsdClientMIBObjectsCISCO-PSD-CLIENT-MIB
1.3.6.1.4.1.9.9.495.1.1ciscoPsdClientStatisticsCISCO-PSD-CLIENT-MIB
1.3.6.1.4.1.9.9.495.1.1.1cPsdClientDSWriteReqCISCO-PSD-CLIENT-MIB