DOCS-RPHY-MIB :: docsRphyRpdIfPhysEntitySerialNum

MIB Reference — IPNetwork Monitor · Updated September 14, 2026

All MIBsDOCS-RPHY-MIBdocsRphyRpdIfPhysEntitySerialNum

docsRphyRpdIfPhysEntitySerialNum

Module: DOCS-RPHY-MIB

OID (symbolic): DOCS-RPHY-MIB::docsRphyRpdIfPhysEntitySerialNum

OID (numeric): 1.3.6.1.4.1.4491.2.1.30.1.2.1.1.11

Node type: OBJECT-TYPE

Type: SnmpAdminString

Access: read-only

Description: The vendor-specific serial number string for the physical entity. The preferred value is the serial number string actually printed on the component itself (if present).

On the first instantiation of a physical entity, the value of docsRphyRpdIfPhysEntitySerialNum associated with that entity is set to the correct vendor-assigned serial number, if this information is available to the agent. If a serial number is unknown or non-existent, the docsRphyRpdIfPhysEntitySerialNum will be set to a zero-length string instead.

Note that implementations that can correctly identify the serial numbers of all installed physical entities do not need to provide write access to the docsRphyRpdIfPhysEntitySerialNum object. Agents that cannot provide non-volatile storage for the docsRphyRpdIfPhysEntitySerialNum strings are not required to implement write access for this object.

Not every physical component will have a serial number, or even need one. Physical entities for which the associated value of the docsRphyRpdIfPhysEntityIsFRU object is equal to 'false(2)' (e.g., the repeater ports within a repeater module) do not need their own unique serial numbers. An agent does not have to provide write access for such entities and may return a zero-length string.

Examples

Walk all instances (SNMPv2c):

snmpwalk -v2c -c public <target> 1.3.6.1.4.1.4491.2.1.30.1.2.1.1.11
snmpwalk -v2c -c public <target> DOCS-RPHY-MIB::docsRphyRpdIfPhysEntitySerialNum

Get a specific instance (index 1):

snmpget -v2c -c public <target> 1.3.6.1.4.1.4491.2.1.30.1.2.1.1.11.1
snmpget -v2c -c public <target> DOCS-RPHY-MIB::docsRphyRpdIfPhysEntitySerialNum.1

Start monitoring DOCSIS Remote PHY Device (RPD), cable HFC access node (vendor-neutral CableLabs standard) with a free 30-day trial of IPNetwork Monitor. Create custom SNMP monitor using the DOCS-RPHY-MIB::docsRphyRpdIfPhysEntitySerialNum OID value, configure state conditions and alerts, and monitor any DOCSIS Remote PHY Device (RPD), cable HFC access node (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.30docsRphyMibDOCS-RPHY-MIB
1.3.6.1.4.1.4491.2.1.30.1docsRphyObjectsDOCS-RPHY-MIB
1.3.6.1.4.1.4491.2.1.30.1.2docsRphyRpdIfMibObjectsDOCS-RPHY-MIB
1.3.6.1.4.1.4491.2.1.30.1.2.1docsRphyRpdIfPhysEntityTableDOCS-RPHY-MIB
1.3.6.1.4.1.4491.2.1.30.1.2.1.1docsRphyRpdIfPhysEntityEntryDOCS-RPHY-MIB
1.3.6.1.4.1.4491.2.1.30.1.2.1.1.11docsRphyRpdIfPhysEntitySerialNumDOCS-RPHY-MIB