CME-MIB :: componentServiceDataDumpCapabilityMask

MIB Reference — IPNetwork Monitor · Updated September 14, 2026

All MIBsCME-MIBcomponentServiceDataDumpCapabilityMask

componentServiceDataDumpCapabilityMask

Module: CME-MIB

OID (symbolic): CME-MIB::componentServiceDataDumpCapabilityMask

OID (numeric): 1.3.6.1.4.1.2.3.51.2.23.15.1.1.5

Node type: OBJECT-TYPE

Type: OCTET STRING

Access: read-only

Description: Indicates whether the component 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 component. The values and meanings are as follows: 0000 0000 means this component does not support any at all.

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

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

What is componentServiceDataDumpCapabilityMask?

This object reports, as a bitmask, which dump types a chassis component supports and whether those files can be transferred to the MM. An admin planning to collect diagnostics from a component checks this mask first to know which componentServiceDataDumpInitiate options will actually be accepted. For example, a mask showing only the processor-type bit set would tell the admin not to bother trying to initiate a platform or partition dump on that component.

Examples

Walk all instances (SNMPv2c):

snmpwalk -v2c -c public <target> 1.3.6.1.4.1.2.3.51.2.23.15.1.1.5
snmpwalk -v2c -c public <target> CME-MIB::componentServiceDataDumpCapabilityMask

Get a specific instance (index 1):

snmpget -v2c -c public <target> 1.3.6.1.4.1.2.3.51.2.23.15.1.1.5.1
snmpget -v2c -c public <target> CME-MIB::componentServiceDataDumpCapabilityMask.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::componentServiceDataDumpCapabilityMask 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.15componentServiceDataCME-MIB
1.3.6.1.4.1.2.3.51.2.23.15.1componentServiceDataTableCME-MIB
1.3.6.1.4.1.2.3.51.2.23.15.1.1componentServiceDataEntryCME-MIB
1.3.6.1.4.1.2.3.51.2.23.15.1.1.5componentServiceDataDumpCapabilityMaskCME-MIB