Need a Cisco serial number for an inventory record, a support case, or a replacement part? On supported Cisco IOS and IOS XE platforms, start with:

show inventory

That answer has aged well. show inventory returns a device's hardware inventory as Cisco unique device identifiers (UDIs): product ID (PID), version ID (VID), and serial number (SN). The part that gets people into trouble is assuming the first serial number on screen is always the chassis serial number. A modular router or switch can report serial numbers for its chassis, power supplies, fans, line cards, and stack members.

Run show inventory First

From the device CLI, run the command and save the complete output with the ticket or asset record:

router# show inventory

A typical IOS XE-style result looks like this:

NAME: "Chassis", DESCR: "Cisco ISR4331 Chassis"
PID: ISR4331/K9       , VID: V05, SN: FOC1234A1BC

NAME: "Power Supply Module 0", DESCR: "250W AC Power Supply"
PID: PWR-4330-AC      , VID: V03, SN: DCA5678D2EF

For the router itself, record the SN on the line associated with NAME: "Chassis". The second number belongs to the power supply. If you are opening an RMA for that supply, it is exactly the number you want; if you are renewing the router's support contract, it is not.

On a stack, look for the inventory entry that identifies each switch member. On a modular chassis, match the serial number to the slot or module description before copying it into an asset system. Capture the PID and VID beside the serial number as well. They make it much easier to establish that a serial number belongs to the correct component when the support portal or warehouse record disagrees.

Why This Is Better Than Hunting Through show version

show version often includes a processor-board ID or another serial-looking value, and it is still useful for collecting the software release and platform model. It is not the cleanest inventory view, though. show inventory presents the identifiers in a consistent PID/VID/SN format and can enumerate installed hardware that show version does not make obvious.

When you are collecting information remotely, use both commands:

show version
show inventory

The first establishes the model and software family; the second gives you the inventory records. This small bit of discipline saves time when a device has been upgraded, stacked, or partly replaced since the last asset audit.

IOS, IOS XE, and Older Releases

Cisco documents show inventory for IOS and IOS XE hardware, but the exact command availability and output depend on the platform and software train. The original IOS command reference lists 12.3(4)T as the introduction point and also records integrations into several 12.0 and 12.2 service-provider releases. In other words, a blanket “12.3 or later” rule is too simple, and a successful command on an older 12.2 device is not surprising.

On a device that rejects the command, do not guess your way through a change window. Start by confirming the platform and release with show version, then use CLI help and the model-specific command reference:

show ?
show inventory ?

Some older, specialized, and non-IOS Cisco families expose the chassis serial number through a different command or a platform-specific hardware view. NX-OS, Cisco IOS XR, firewalls, and wireless controllers should be treated as separate command families, not as variants guaranteed to behave like a Catalyst switch or IOS router.

Collecting Inventory Without Losing the Context

For one device, copying the full output is usually faster and safer than clever filtering. The NAME and PID/SN fields are commonly printed on separate lines, so a narrow filter can leave you with a serial number and no reliable indication of the component it belongs to. Keep the original transcript, then extract the asset data from that record.

For a fleet, have your automation collect the hostname, capture time, show version, and unmodified show inventory output together. Parse the UDI records only after preserving the source. Device stacks, field-replaceable modules, and platform-specific output make “the first serial number returned” a fragile automation rule. A useful inventory schema treats the chassis and every installed component as separate records linked to the same device.

This also keeps the operational boundary clear: show inventory is a read-only discovery command, but inventory data is still sensitive. Limit access to serial-number exports and ticket attachments in the same way you would other infrastructure records.

A Small Checklist for Support and Asset Work

Before you close the ticket or update an inventory system, verify these details:

1. Record the serial number for the right entity: chassis, stack member, module, or power supply.
2. Record the nearby PID and VID, especially for replaceable hardware.
3. Save show version and the full show inventory output as evidence rather than just pasting one serial number into a spreadsheet.
4. Do not use a module or power-supply serial number for a chassis support contract unless Cisco specifically asks for that component.
5. If the output is ambiguous, compare the model and serial field against the physical label during an approved maintenance visit.

The same approach pays off when troubleshooting hardware health: establish exactly what is installed before interpreting its status. For a practical next step, see How to Check Power Supply Status on Cisco Switches and Routers.

For the current syntax and UDI field definitions, Cisco's IOS XE unique device identifier documentation is the authoritative reference. Return to Slaptijack for more practical networking and systems articles.