CME-MIB :: serviceDataDumpCapabilityMask

MIB Reference — IPNetwork Monitor · Updated September 14, 2026

All MIBsCME-MIBserviceDataDumpCapabilityMask

serviceDataDumpCapabilityMask

Module: CME-MIB

OID (symbolic): CME-MIB::serviceDataDumpCapabilityMask

OID (numeric): 1.3.6.1.4.1.2.3.51.2.23.3.1.1.9

Node type: OBJECT-TYPE

Type: OCTET STRING

Access: read-only

Description: Indicates whether the blade has the capability to trigger service data and if so, which operations are supported and whether the file can be transferred to the MM from the blade. The values and meanings are as follows: 0000 0000 means this blade does not support any at all.

0000 0001 means this blade supports 'processor' type and the file remains on the blade. 0000 0010 means this blade supports 'platform' type and the file remains on the blade 0000 0100 means this blade supports 'partition' type and the file remians on the blade

0000 1000 means this blade supports 'processor' type and the file can be transferred to the MM. 0001 0000 means this blade supports 'platform' type and the file can be transferred to the MM. 0010 0000 means this blade supports 'partition' type and the file can be transferred to the MM 0100 0000 means this blade supports 'serviceData' type and the file can be transferred to the MM For example, the returned value of 01111000 means this blade supports 'processor','platform', 'partition' and 'serviceData' types, and the file can be transferred to the MM

What is serviceDataDumpCapabilityMask?

This object reports, as a bitmask, which dump types a blade supports and whether the resulting files can be transferred to the management module or remain on the blade itself. An admin planning a diagnostic data collection checks this mask first to know which of serviceDataDumpInitiate's dump types will actually work for a given blade. For example, a mask of 0000 0000 tells the admin that blade supports no dump collection at all, so the admin would look for another diagnostic approach.

Examples

Walk all instances (SNMPv2c):

snmpwalk -v2c -c public <target> 1.3.6.1.4.1.2.3.51.2.23.3.1.1.9
snmpwalk -v2c -c public <target> CME-MIB::serviceDataDumpCapabilityMask

Get a specific instance (index 1):

snmpget -v2c -c public <target> 1.3.6.1.4.1.2.3.51.2.23.3.1.1.9.1
snmpget -v2c -c public <target> CME-MIB::serviceDataDumpCapabilityMask.1

Start monitoring Cisco Communications Manager Express (CME) router/gateway with a free 30-day trial of IPNetwork Monitor. Create custom SNMP monitor using the CME-MIB::serviceDataDumpCapabilityMask OID value, configure state conditions and alerts, and monitor any Cisco Communications Manager Express (CME) router/gateway from a single console.

OID Breakdown

Upper-level ancestors (10 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.2ibmBLADE-MIB
1.3.6.1.4.1.2.3ibmAgentsBLADE-MIB
1.3.6.1.4.1.2.3.51netfinitySupportProcessorAgentBLADE-MIB
1.3.6.1.4.1.2.3.51.2bladeCenterSnmpMIBBLADE-MIB
Numeric OIDNameModule
1.3.6.1.4.1.2.3.51.2.23serviceCME-MIB
1.3.6.1.4.1.2.3.51.2.23.3bladeServiceDataCME-MIB
1.3.6.1.4.1.2.3.51.2.23.3.1bladeServiceDataTableCME-MIB
1.3.6.1.4.1.2.3.51.2.23.3.1.1bladeServiceDataEntryCME-MIB
1.3.6.1.4.1.2.3.51.2.23.3.1.1.9serviceDataDumpCapabilityMaskCME-MIB