SL-ENTITY-MIB :: slEntPhysicalOemSerialNum

MIB Reference — IPNetwork Monitor · Updated September 21, 2026

All MIBs › SL-ENTITY-MIB › slEntPhysicalOemSerialNum

slEntPhysicalOemSerialNum

Module: SL-ENTITY-MIB

OID (symbolic): SL-ENTITY-MIB::slEntPhysicalOemSerialNum

OID (numeric): 1.3.6.1.4.1.4515.1.3.6.1.1.1.23

Node type: OBJECT-TYPE

Type: SnmpAdminString

Access: read-only

Description: The oem-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 an physical entity, the value of slEntPhysicalSerialNum 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 slEntPhysicalSerialNum will be set to a zero-length string instead.

Note that implementations which can correctly identify the serial numbers of all installed physical entities do not need to provide write access to the slEntPhysicalSerialNum object. Agents which cannot provide non-volatile storage for the slEntPhysicalSerialNum 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 slEntPhysicalIsFRU object is equal to 'false(2)' (e.g., the repeater ports within a repeater module), do not need their own unique serial number. An agent does not have to provide write access for such entities, and may return a zero-length string.

If write access is implemented for an instance of slEntPhysicalSerialNum, and a value is written into the instance, the agent must retain the supplied value in the slEntPhysicalSerialNum instance associated with the same physical entity for as long as that entity remains instantiated. This includes instantiations across all re- initializations/reboots of the network management system, including those which result in a change of the physical entity's slEntPhysicalIndex value.

What is slEntPhysicalOemSerialNum?

This value reports the OEM-specific serial number string for this physical entity, distinct from the vendor's own serial number object. An admin uses it when dealing with an OEM reseller's support process, since that support desk will typically ask for the OEM serial rather than the primary vendor's serial number. For example, an OEM serial like "OEM-00234A" would be the identifier quoted when opening a support ticket with the reseller.

Examples

Walk all instances (SNMPv2c):

snmpwalk -v2c -c public <target> 1.3.6.1.4.1.4515.1.3.6.1.1.1.23
snmpwalk -v2c -c public <target> SL-ENTITY-MIB::slEntPhysicalOemSerialNum

Get a specific instance (index 1):

snmpget -v2c -c public <target> 1.3.6.1.4.1.4515.1.3.6.1.1.1.23.1
snmpget -v2c -c public <target> SL-ENTITY-MIB::slEntPhysicalOemSerialNum.1

Start monitoring Smartoptics SiteLight optical network elements (physical entity/firmware/protection-state inventory) with a free 30-day trial of IPNetwork Monitor. Create custom SNMP monitor using the SL-ENTITY-MIB::slEntPhysicalOemSerialNum OID value, configure state conditions and alerts, and monitor any Smartoptics SiteLight optical network elements (physical entity/firmware/protection-state inventory) 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.4515smartopticsSL-NE-MIB
1.3.6.1.4.1.4515.1sitelightSL-NE-MIB
1.3.6.1.4.1.4515.1.3slMainSL-MAIN-MIB
Numeric OIDNameModule
1.3.6.1.4.1.4515.1.3.6slmEntitySL-ENTITY-MIB
1.3.6.1.4.1.4515.1.3.6.1slEntityPhysicalSL-ENTITY-MIB
1.3.6.1.4.1.4515.1.3.6.1.1slEntPhysicalTableSL-ENTITY-MIB
1.3.6.1.4.1.4515.1.3.6.1.1.1slEntPhysicalEntrySL-ENTITY-MIB
1.3.6.1.4.1.4515.1.3.6.1.1.1.23slEntPhysicalOemSerialNumSL-ENTITY-MIB