All MIBs › SL-ENTITY-MIB › slEntPhysicalSerialNum
slEntPhysicalSerialNum
Module: SL-ENTITY-MIB
OID (symbolic): SL-ENTITY-MIB::slEntPhysicalSerialNum
OID (numeric): 1.3.6.1.4.1.4515.1.3.6.1.1.1.7
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 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 slEntPhysicalSerialNum?
This object stores the vendor-assigned serial number of a physical component (chassis, module, port, etc.), either as read from hardware at boot or as set by network management. An operator relies on this for asset tracking, warranty administration, and hardware replacement coordination. The serial number must be retained across reboots and is essential for tracking individual physical entities across the network infrastructure lifecycle.
Examples
Walk all instances (SNMPv2c):
snmpwalk -v2c -c public <target> 1.3.6.1.4.1.4515.1.3.6.1.1.1.7 snmpwalk -v2c -c public <target> SL-ENTITY-MIB::slEntPhysicalSerialNum
Get a specific instance (index 1):
snmpget -v2c -c public <target> 1.3.6.1.4.1.4515.1.3.6.1.1.1.7.1 snmpget -v2c -c public <target> SL-ENTITY-MIB::slEntPhysicalSerialNum.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::slEntPhysicalSerialNum 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 OID | Name | Module |
|---|---|---|
| 1 | iso | LANART-AGENT |
| 1.3 | org | AirPair-MIB |
| 1.3.6 | dod | AirPair-MIB |
| 1.3.6.1 | internet | AirPair-MIB |
| 1.3.6.1.4 | private | AirPair-MIB |
| 1.3.6.1.4.1 | enterprises | AirPair-MIB |
| 1.3.6.1.4.1.4515 | smartoptics | SL-NE-MIB |
| 1.3.6.1.4.1.4515.1 | sitelight | SL-NE-MIB |
| 1.3.6.1.4.1.4515.1.3 | slMain | SL-MAIN-MIB |
| Numeric OID | Name | Module |
|---|---|---|
| 1.3.6.1.4.1.4515.1.3.6 | slmEntity | SL-ENTITY-MIB |
| 1.3.6.1.4.1.4515.1.3.6.1 | slEntityPhysical | SL-ENTITY-MIB |
| 1.3.6.1.4.1.4515.1.3.6.1.1 | slEntPhysicalTable | SL-ENTITY-MIB |
| 1.3.6.1.4.1.4515.1.3.6.1.1.1 | slEntPhysicalEntry | SL-ENTITY-MIB |
| 1.3.6.1.4.1.4515.1.3.6.1.1.1.7 | slEntPhysicalSerialNum | SL-ENTITY-MIB |