DOCS-IF31-MIB :: docsIf31CmtsCmRegStatusDsProfileIdList

MIB Reference — IPNetwork Monitor · Updated October 05, 2026

All MIBs › DOCS-IF31-MIB › docsIf31CmtsCmRegStatusDsProfileIdList

docsIf31CmtsCmRegStatusDsProfileIdList

Module: DOCS-IF31-MIB

OID (symbolic): DOCS-IF31-MIB::docsIf31CmtsCmRegStatusDsProfileIdList

OID (numeric): 1.3.6.1.4.1.4491.2.1.28.1.3.1.2

Node type: OBJECT-TYPE

Type: OCTET STRING

Access: read-only

Description: This attribute is a variable length series of hexadecimal octets where each series entry consists of the following fields (encoded in the following order):

- The ifIndex (4 octets) of the OFDM channel where the downstream Profile IDs are assigned.

- The number or count of Profile IDs (1 octet with valid values of 1-4) assigned to the CM on that channel.

- The list of Profile IDs (1 octet each with valid values of 0-15) assigned to this CM on that channel. Profile ID 0 is commonly referred to as Profile A. Likewise, Profile IDs 1, 2 and 3 are commonly referred to as Profiles B, C and D.

The CCAP encodes each OFDM channel in a CM's RCS as a separate n-octet entry in the ProfileIdList.

Examples: a CM with a single OFDM channel (ifIndex 34) and four assigned profiles (Profile IDs 0, 8, 9 and 10) would have a ProfileIdList value of 0x00000022040008090A. A CM with a 2 OFDM channel bonding group each with two assigned profiles (Profile IDs 0 and 15 on channel with ifIndex 34 and Profile IDs 0 and 14 on channel with ifIndex 35) would have a ProfileIdList value of 0x0000002202000F0000002302000E).

Note: the CCAP must not include the transitional profile or test profile in the ProfileIdList.

Note that octet string lengths greater than 18 are optional.

This object is applicable to DOCSIS 3.1 modems but not to prior versions of DOCSIS modems. If the CM is a pre-DOCSIS 3.1 modem, the CMTS returns a zero length octet string.

What is docsIf31CmtsCmRegStatusDsProfileIdList?

A packed binary list, one entry per OFDM downstream channel, showing which downstream Profile IDs (0-15, commonly called Profiles A-D and beyond) the CMTS has assigned to this modem, each entry encoding the channel's ifIndex followed by the count and list of Profile IDs. An admin troubleshooting downstream modulation issues can decode this to see exactly which profiles a specific modem is using on each bonded OFDM channel; it is only populated for DOCSIS 3.1 modems and returns a zero-length string for older modems.

Examples

Walk all instances (SNMPv2c):

snmpwalk -v2c -c public <target> 1.3.6.1.4.1.4491.2.1.28.1.3.1.2
snmpwalk -v2c -c public <target> DOCS-IF31-MIB::docsIf31CmtsCmRegStatusDsProfileIdList

Get a specific instance (index 1):

snmpget -v2c -c public <target> 1.3.6.1.4.1.4491.2.1.28.1.3.1.2.1
snmpget -v2c -c public <target> DOCS-IF31-MIB::docsIf31CmtsCmRegStatusDsProfileIdList.1

Start monitoring DOCSIS 3.1 cable modem/CMTS-CCAP (OFDM/OFDMA channels, vendor-neutral CableLabs standard) with a free 30-day trial of IPNetwork Monitor. Create custom SNMP monitor using the DOCS-IF31-MIB::docsIf31CmtsCmRegStatusDsProfileIdList OID value, configure state conditions and alerts, and monitor any DOCSIS 3.1 cable modem/CMTS-CCAP (OFDM/OFDMA channels, vendor-neutral CableLabs standard) from a single console.

OID Breakdown

Upper-level ancestors (9 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.4491cableLabsCLAB-DEF-MIB
1.3.6.1.4.1.4491.2clabProjectCLAB-DEF-MIB
1.3.6.1.4.1.4491.2.1clabProjDocsisCLAB-DEF-MIB
Numeric OIDNameModule
1.3.6.1.4.1.4491.2.1.28docsIf31MibDOCS-IF31-MIB
1.3.6.1.4.1.4491.2.1.28.1docsIf31MibObjectsDOCS-IF31-MIB
1.3.6.1.4.1.4491.2.1.28.1.3docsIf31CmtsCmRegStatusTableDOCS-IF31-MIB
1.3.6.1.4.1.4491.2.1.28.1.3.1docsIf31CmtsCmRegStatusEntryDOCS-IF31-MIB
1.3.6.1.4.1.4491.2.1.28.1.3.1.2docsIf31CmtsCmRegStatusDsProfileIdListDOCS-IF31-MIB