OID reference

serviceDataDumpCapabilityMask

1.3.6.1.4.1.2.3.51.2.23.3.1.1.9

Description

Full description and source information

Identification

Identifier and names

Parent: 1.3.6.1.4.1.2.3.51.2.23.3.1.1 (bladeServiceDataEntry)
Node code: 9
Node name: serviceDataDumpCapabilityMask
Category: SNMP management object
Numeric OID: 1.3.6.1.4.1.2.3.51.2.23.3.1.1.9
URN notation: urn:oid:1.3.6.1.4.1.2.3.51.2.23.3.1.1.9

ASN.1, OID-IRI and named path variants

ASN.1 notation

{1 3 6 1 4 1 2 3 51 2 23 3 1 1 9}

{iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprise(1) ibm(2) ibmAgents(3) netfinitySupportProcessorAgent(51) bladeCenterSnmpMIB(2) service(23) bladeServiceData(3) bladeServiceDataTable(1) bladeServiceDataEntry(1) serviceDataDumpCapabilityMask(9)}
{iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprise(1) atmMIBCompliance2(2) ibmAgents(3) netfinitySupportProcessorAgent(51) bladeCenterSnmpMIB(2) service(23) bladeServiceData(3) bladeServiceDataTable(1) bladeServiceDataEntry(1) serviceDataDumpCapabilityMask(9)}
{iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprises(1) ibm(2) ibmAgents(3) netfinitySupportProcessorAgent(51) bladeCenterSnmpMIB(2) service(23) bladeServiceData(3) bladeServiceDataTable(1) bladeServiceDataEntry(1) serviceDataDumpCapabilityMask(9)}
{iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprises(1) atmMIBCompliance2(2) ibmAgents(3) netfinitySupportProcessorAgent(51) bladeCenterSnmpMIB(2) service(23) bladeServiceData(3) bladeServiceDataTable(1) bladeServiceDataEntry(1) serviceDataDumpCapabilityMask(9)}
{iso(1) identified-organization(3) dod(6) internet(1) private(4) ldap-enterprise(1) ibm(2) ibmAgents(3) netfinitySupportProcessorAgent(51) bladeCenterSnmpMIB(2) service(23) bladeServiceData(3) bladeServiceDataTable(1) bladeServiceDataEntry(1) serviceDataDumpCapabilityMask(9)}
{iso(1) identified-organization(3) dod(6) internet(1) private(4) ldap-enterprise(1) atmMIBCompliance2(2) ibmAgents(3) netfinitySupportProcessorAgent(51) bladeCenterSnmpMIB(2) service(23) bladeServiceData(3) bladeServiceDataTable(1) bladeServiceDataEntry(1) serviceDataDumpCapabilityMask(9)}
{iso(1) identified-organization(3) dod(6) internet(1) private(4) vendor-objects(1) ibm(2) ibmAgents(3) netfinitySupportProcessorAgent(51) bladeCenterSnmpMIB(2) service(23) bladeServiceData(3) bladeServiceDataTable(1) bladeServiceDataEntry(1) serviceDataDumpCapabilityMask(9)}
{iso(1) identified-organization(3) dod(6) internet(1) private(4) vendor-objects(1) atmMIBCompliance2(2) ibmAgents(3) netfinitySupportProcessorAgent(51) bladeCenterSnmpMIB(2) service(23) bladeServiceData(3) bladeServiceDataTable(1) bladeServiceDataEntry(1) serviceDataDumpCapabilityMask(9)}
{iso(1) org(3) dod(6) internet(1) private(4) enterprise(1) ibm(2) ibmAgents(3) netfinitySupportProcessorAgent(51) bladeCenterSnmpMIB(2) service(23) bladeServiceData(3) bladeServiceDataTable(1) bladeServiceDataEntry(1) serviceDataDumpCapabilityMask(9)}
{iso(1) org(3) dod(6) internet(1) private(4) enterprise(1) atmMIBCompliance2(2) ibmAgents(3) netfinitySupportProcessorAgent(51) bladeCenterSnmpMIB(2) service(23) bladeServiceData(3) bladeServiceDataTable(1) bladeServiceDataEntry(1) serviceDataDumpCapabilityMask(9)}
{iso(1) org(3) dod(6) internet(1) private(4) enterprises(1) ibm(2) ibmAgents(3) netfinitySupportProcessorAgent(51) bladeCenterSnmpMIB(2) service(23) bladeServiceData(3) bladeServiceDataTable(1) bladeServiceDataEntry(1) serviceDataDumpCapabilityMask(9)}
{iso(1) org(3) dod(6) internet(1) private(4) enterprises(1) atmMIBCompliance2(2) ibmAgents(3) netfinitySupportProcessorAgent(51) bladeCenterSnmpMIB(2) service(23) bladeServiceData(3) bladeServiceDataTable(1) bladeServiceDataEntry(1) serviceDataDumpCapabilityMask(9)}
{iso(1) org(3) dod(6) internet(1) private(4) ldap-enterprise(1) ibm(2) ibmAgents(3) netfinitySupportProcessorAgent(51) bladeCenterSnmpMIB(2) service(23) bladeServiceData(3) bladeServiceDataTable(1) bladeServiceDataEntry(1) serviceDataDumpCapabilityMask(9)}
{iso(1) org(3) dod(6) internet(1) private(4) ldap-enterprise(1) atmMIBCompliance2(2) ibmAgents(3) netfinitySupportProcessorAgent(51) bladeCenterSnmpMIB(2) service(23) bladeServiceData(3) bladeServiceDataTable(1) bladeServiceDataEntry(1) serviceDataDumpCapabilityMask(9)}
{iso(1) org(3) dod(6) internet(1) private(4) vendor-objects(1) ibm(2) ibmAgents(3) netfinitySupportProcessorAgent(51) bladeCenterSnmpMIB(2) service(23) bladeServiceData(3) bladeServiceDataTable(1) bladeServiceDataEntry(1) serviceDataDumpCapabilityMask(9)}
{iso(1) org(3) dod(6) internet(1) private(4) vendor-objects(1) atmMIBCompliance2(2) ibmAgents(3) netfinitySupportProcessorAgent(51) bladeCenterSnmpMIB(2) service(23) bladeServiceData(3) bladeServiceDataTable(1) bladeServiceDataEntry(1) serviceDataDumpCapabilityMask(9)}
Additional combinations skipped.

OID-IRI notation

/1/3/6/1/4/1/2/3/51/2/23/3/1/1/9
/ISO/Identified-Organization/6/1/4/1/2/3/51/2/23/3/1/1/9
/ISO/3/6/1/4/1/2/3/51/2/23/3/1/1/9

Named path variants

/iso/identified-organization/dod/internet/private/enterprise/ibm/ibmAgents/netfinitySupportProcessorAgent/bladeCenterSnmpMIB/service/bladeServiceData/bladeServiceDataTable/bladeServiceDataEntry/serviceDataDumpCapabilityMask
/iso/identified-organization/dod/internet/private/enterprise/IBM/ibmAgents/netfinitySupportProcessorAgent/bladeCenterSnmpMIB/service/bladeServiceData/bladeServiceDataTable/bladeServiceDataEntry/serviceDataDumpCapabilityMask
/iso/identified-organization/dod/internet/private/enterprise/atmMIBCompliance2/ibmAgents/netfinitySupportProcessorAgent/bladeCenterSnmpMIB/service/bladeServiceData/bladeServiceDataTable/bladeServiceDataEntry/serviceDataDumpCapabilityMask
/iso/identified-organization/dod/internet/private/enterprises/ibm/ibmAgents/netfinitySupportProcessorAgent/bladeCenterSnmpMIB/service/bladeServiceData/bladeServiceDataTable/bladeServiceDataEntry/serviceDataDumpCapabilityMask
/iso/identified-organization/dod/internet/private/enterprises/IBM/ibmAgents/netfinitySupportProcessorAgent/bladeCenterSnmpMIB/service/bladeServiceData/bladeServiceDataTable/bladeServiceDataEntry/serviceDataDumpCapabilityMask
/iso/identified-organization/dod/internet/private/enterprises/atmMIBCompliance2/ibmAgents/netfinitySupportProcessorAgent/bladeCenterSnmpMIB/service/bladeServiceData/bladeServiceDataTable/bladeServiceDataEntry/serviceDataDumpCapabilityMask
/iso/identified-organization/dod/internet/private/ldap-enterprise/ibm/ibmAgents/netfinitySupportProcessorAgent/bladeCenterSnmpMIB/service/bladeServiceData/bladeServiceDataTable/bladeServiceDataEntry/serviceDataDumpCapabilityMask
/iso/identified-organization/dod/internet/private/ldap-enterprise/IBM/ibmAgents/netfinitySupportProcessorAgent/bladeCenterSnmpMIB/service/bladeServiceData/bladeServiceDataTable/bladeServiceDataEntry/serviceDataDumpCapabilityMask
/iso/identified-organization/dod/internet/private/ldap-enterprise/atmMIBCompliance2/ibmAgents/netfinitySupportProcessorAgent/bladeCenterSnmpMIB/service/bladeServiceData/bladeServiceDataTable/bladeServiceDataEntry/serviceDataDumpCapabilityMask
/iso/identified-organization/dod/internet/private/vendor-objects/ibm/ibmAgents/netfinitySupportProcessorAgent/bladeCenterSnmpMIB/service/bladeServiceData/bladeServiceDataTable/bladeServiceDataEntry/serviceDataDumpCapabilityMask
/iso/identified-organization/dod/internet/private/vendor-objects/IBM/ibmAgents/netfinitySupportProcessorAgent/bladeCenterSnmpMIB/service/bladeServiceData/bladeServiceDataTable/bladeServiceDataEntry/serviceDataDumpCapabilityMask
/iso/identified-organization/dod/internet/private/vendor-objects/atmMIBCompliance2/ibmAgents/netfinitySupportProcessorAgent/bladeCenterSnmpMIB/service/bladeServiceData/bladeServiceDataTable/bladeServiceDataEntry/serviceDataDumpCapabilityMask
/iso/org/dod/internet/private/enterprise/ibm/ibmAgents/netfinitySupportProcessorAgent/bladeCenterSnmpMIB/service/bladeServiceData/bladeServiceDataTable/bladeServiceDataEntry/serviceDataDumpCapabilityMask
/iso/org/dod/internet/private/enterprise/IBM/ibmAgents/netfinitySupportProcessorAgent/bladeCenterSnmpMIB/service/bladeServiceData/bladeServiceDataTable/bladeServiceDataEntry/serviceDataDumpCapabilityMask
/iso/org/dod/internet/private/enterprise/atmMIBCompliance2/ibmAgents/netfinitySupportProcessorAgent/bladeCenterSnmpMIB/service/bladeServiceData/bladeServiceDataTable/bladeServiceDataEntry/serviceDataDumpCapabilityMask
/iso/org/dod/internet/private/enterprises/ibm/ibmAgents/netfinitySupportProcessorAgent/bladeCenterSnmpMIB/service/bladeServiceData/bladeServiceDataTable/bladeServiceDataEntry/serviceDataDumpCapabilityMask
Additional combinations skipped.

SNMP properties

Value type: OCTET STRING
Maximum access defined by MIB: read-only
Status in MIB: mandatory

Using this OID with SNMP

At least one MIB declaration places this object in a table row. A value belongs to a row instance; its suffix depends on the row's INDEX or AUGMENTS definition.

In BLADE-MIB, the row index serviceDataIndex is declared as INTEGER. A non-negative index value is encoded as one numeric subidentifier. An instance has the form .1.3.6.1.4.1.2.3.51.2.23.3.1.1.9.<serviceDataIndex>. Use an index value actually present on the device and permitted by its MIB. Other definitions can differ.

snmpwalk [connection options] DEVICE .1.3.6.1.4.1.2.3.51.2.23.3.1.1.9

Replace the placeholders with your connection and authentication options. Available permissions and device support can differ from the MIB.

Properties come from available MIB definitions. Actual device support and access can differ. See source records below for original files and qualifications.

Published definitions

Available source records contain 2 distinct definitions; some records may not include a definition.

Show 2 published definitions

serviceDataDumpCapabilityMask · mandatory

serviceDataDumpCapabilityMask OBJECT-TYPE
                   SYNTAX  OCTET STRING
                   ACCESS  read-only
                   STATUS  mandatory
                   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 AMM
                   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 AMM.
                   0001 0000 means this blade supports 'platform' type and the file can be transferred to the AMM.
                   0010 0000 means this blade supports 'partition' type and the file can be transferred to the AMM
                   0100 0000 means this blade supports 'serviceData' type and the file can be transferred to the AMM

                   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 AMM"
                   ::= { bladeServiceDataEntry 9 }

serviceDataDumpCapabilityMask · mandatory

serviceDataDumpCapabilityMask OBJECT-TYPE
                   SYNTAX  OCTET STRING
                   ACCESS  read-only
                   STATUS  mandatory
                   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"
                   ::= { bladeServiceDataEntry 9 }

Meaning

Descriptions

2 unique

Identical descriptions are grouped. Different wording and device-specific notes are retained.

Description 1

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 AMM 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 AMM. 0001 0000 means this blade supports 'platform' type and the file can be transferred to the AMM. 0010 0000 means this blade supports 'partition' type and the file can be transferred to the AMM 0100 0000 means this blade supports 'serviceData' type and the file can be transferred to the AMM 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 AMM

Sources for this description

IBM MIB copies (LibreNMS/Observium Community)

See 1 matching source record

Description 2

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

Sources for this description

IBM MIB copies (LibreNMS/Observium Community)IBM MIB copies (MibBrowser.online)

See 1 matching source record

Evidence

Source records

2 records

Matching descriptions are grouped; open a group to compare definitions and supporting files.

Records for description 1IBM MIB copies (LibreNMS/Observium Community)1 record · 1 source

Description 1

serviceDataDumpCapabilityMask · mandatoryIBM MIB copies (LibreNMS/Observium Community)1 source

Status in source: mandatory.

Names: serviceDataDumpCapabilityMask

Technical details

{
  "smi_kind": "OBJECT-TYPE",
  "definition": [
    "serviceDataDumpCapabilityMask",
    "OBJECT-TYPE",
    "SYNTAX",
    "OCTET",
    "STRING",
    "ACCESS",
    "read-only",
    "STATUS",
    "mandatory",
    "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 AMM 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 AMM. 0001 0000 means this blade supports 'platform' type and the file can be transferred to the AMM. 0010 0000 means this blade supports 'partition' type and the file can be transferred to the AMM 0100 0000 means this blade supports 'serviceData' type and the file can be transferred to the AMM 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 AMM\"",
    "::=",
    "{",
    "bladeServiceDataEntry",
    "9",
    "}"
  ],
  "syntax_tree": [
    [
      "SimpleSyntax",
      "OCTET STRING"
    ],
    null,
    [
      "MaxAccessPart",
      "read-only"
    ],
    [
      "Status",
      "mandatory"
    ],
    [
      "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 AMM 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 AMM. 0001 0000 means this blade supports 'platform' type and the file can be transferred to the AMM. 0010 0000 means this blade supports 'partition' type and the file can be transferred to the AMM 0100 0000 means this blade supports 'serviceData' type and the file can be transferred to the AMM 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 AMM"
    ],
    null,
    null,
    null,
    null
  ]
}

IBM MIB copies (LibreNMS/Observium Community) · Publisher's source file: BLADE-MIB
Vendor MIB copy from the LibreNMS archive. IBM support.

Module: BLADE-MIB

See published definition above
Module imports
```
{'RFC-1212': ['OBJECT-TYPE'], 'RFC-1215': ['TRAP-TYPE'], 'RFC1155-SMI': ['enterprises', 'IpAddress']}
```
· Download BLADE-MIB
Related source files and packages:
Same file in Observium Community.

Records for description 2IBM MIB copies (LibreNMS/Observium Community), IBM MIB copies (MibBrowser.online)1 record · 2 sources

Description 2

serviceDataDumpCapabilityMask · mandatoryIBM MIB copies (LibreNMS/Observium Community), IBM MIB copies (MibBrowser.online)2 sources

Status in source: mandatory.

Names: serviceDataDumpCapabilityMask

Technical details

{
  "smi_kind": "OBJECT-TYPE",
  "definition": [
    "serviceDataDumpCapabilityMask",
    "OBJECT-TYPE",
    "SYNTAX",
    "OCTET",
    "STRING",
    "ACCESS",
    "read-only",
    "STATUS",
    "mandatory",
    "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\"",
    "::=",
    "{",
    "bladeServiceDataEntry",
    "9",
    "}"
  ],
  "syntax_tree": [
    [
      "SimpleSyntax",
      "OCTET STRING"
    ],
    null,
    [
      "MaxAccessPart",
      "read-only"
    ],
    [
      "Status",
      "mandatory"
    ],
    [
      "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"
    ],
    null,
    null,
    null,
    null
  ]
}

IBM MIB copies (LibreNMS/Observium Community) · Publisher's source file: CME-MIB
Vendor MIB copy from the LibreNMS archive. IBM support.

Module: CME-MIB

See published definition above
Module imports
```
{'RFC-1212': ['OBJECT-TYPE'], 'RFC-1215': ['TRAP-TYPE'], 'RFC1155-SMI': ['enterprises', 'IpAddress']}
```
· Download CME-MIB
Same file in Observium Community.
IBM MIB copies (MibBrowser.online) · Publisher's source file: CME-MIB — archive MIB indexed for IBM (https://w3.ibm.com/standards )
Vendor MIB copy from the MibBrowser.online archive. IBM (https://w3.ibm.com/standards ) support.

Module: CME-MIB

Same published definition
Module imports
```
{'RFC-1212': ['OBJECT-TYPE'], 'RFC-1215': ['TRAP-TYPE'], 'RFC1155-SMI': ['enterprises', 'IpAddress']}
```
· Download CME-MIB — archive MIB indexed for IBM (https://w3.ibm.com/standards )
Related source files and packages:

Registration

Registration authorities

First Registration Authority (inferred from ancestor 1.3.6.1.4.1.2)

Bob Moore

Siblings (9)

OID	Name	Direct children	Descendants	Description
1.3.6.1.4.1.2.3.51.2.23.3.1.1.1	serviceDataIndex	0	0
1.3.6.1.4.1.2.3.51.2.23.3.1.1.2	serviceDataBladeId	0	0
1.3.6.1.4.1.2.3.51.2.23.3.1.1.3	serviceDataBladeExists	0	0
1.3.6.1.4.1.2.3.51.2.23.3.1.1.4	serviceDataBladePowerState	0	0
1.3.6.1.4.1.2.3.51.2.23.3.1.1.5	serviceDataBladeName	0	0
1.3.6.1.4.1.2.3.51.2.23.3.1.1.6	serviceDataBladeCapability	0	0
1.3.6.1.4.1.2.3.51.2.23.3.1.1.7	serviceDataDumpInitiate	0	0
1.3.6.1.4.1.2.3.51.2.23.3.1.1.8	serviceDataDumpRetrieve	0	0
1.3.6.1.4.1.2.3.51.2.23.3.1.1.10	serviceDataDumpInProgress	0	0