Courseiva
SystemPrivileged EXEC

show inventory

Retrieve serial numbers and hardware model information for asset management, RMA processes, and license validation.

Definition: show inventory is a Cisco IOS privileged exec command. Displays hardware inventory including chassis, modules, power supplies, and fan trays with their product IDs (PIDs), version IDs (VIDs), and serial numbers.

Overview

The `show inventory` command is a vital diagnostic and asset management tool in Cisco IOS that provides a detailed hardware inventory of the device. It displays the product IDs (PID), version IDs (VID), and serial numbers (SN) for all major hardware components, including the chassis, power supplies, fans, modules, and line cards. This command is essential for verifying hardware components during initial deployment, troubleshooting hardware failures, and maintaining accurate asset records for compliance and lifecycle management.

Unlike `show version`, which focuses on software and uptime, `show inventory` drills into the physical hardware layer, making it the go-to command when you need to confirm the exact model, revision, or serial number of a specific component. It is particularly useful when ordering replacement parts, validating warranty coverage, or ensuring that field-replaceable units (FRUs) match the bill of materials. The command operates in privileged EXEC mode (enable) and does not affect the running configuration.

Its output is buffered, meaning it may not reflect real-time changes if hardware is hot-swapped; a reload or re-insertion may be required to update the inventory. The command is supported across Cisco IOS, IOS-XE, and NX-OS platforms, though output formatting may vary slightly. In a broader network workflow, `show inventory` is often used alongside `show environment` (for power and temperature) and `show module` (for module status) to perform a comprehensive hardware health check.

For network engineers, this command is indispensable during site audits, RMA processes, and when integrating new devices into a management system like Cisco DNA Center or Prime Infrastructure. Understanding the inventory output helps in identifying counterfeit parts, tracking end-of-life (EOL) components, and ensuring that hardware meets the minimum requirements for a specific IOS version. The command also supports optional parameters to filter by specific component types, making it efficient for large chassis-based systems like the Catalyst 6500 or ASR 9000 series.

Overall, `show inventory` is a foundational command that bridges the gap between physical hardware and logical configuration, enabling engineers to maintain accurate, reliable, and secure network infrastructure.

Syntax·Privileged EXEC
show inventory [raw]

When to Use This Command

  • Obtain chassis serial number for Cisco Smart License registration
  • Verify which modules are installed in a modular switch or router
  • Confirm hardware model before applying a software upgrade
  • Collect inventory data for asset management systems

Parameters

ParameterSyntaxDescription
rawrawDisplays the inventory information in raw format without any formatting. This is useful for scripting or parsing the output programmatically. When used, the output is not human-readable but contains all data fields in a structured manner.

Command Examples

Catalyst switch inventory

Switch# show inventory
NAME: "1", DESCR: "WS-C2960X-48FPD-L"
PID: WS-C2960X-48FPD-L  , VID: V03 , SN: FOC2147X0AB

NAME: "Switch 1 - Power Supply A", DESCR: "FRU Power Supply"
PID: PWR-C2-640WAC      , VID: V03 , SN: ART214700B1

Understanding the Output

NAME = internal component name, DESCR = human-readable description, PID = Cisco product ID (use this for ordering replacements or registering smart licenses), VID = version ID (hardware revision), SN = serial number.

Configuration Scenarios

Verify Hardware Inventory on a New Cisco ISR 4321 Router

A network engineer has just received a new Cisco ISR 4321 router and needs to verify that all ordered components (chassis, power supply, and modules) are present and correctly seated before deployment.

Topology

ISR4321 (Chassis)---(Power Supply PSU-4321-AC)---(NIM-2T module)

Steps

  1. 1.Step 1: Connect to the router via console or SSH and enter privileged EXEC mode: Router> enable
  2. 2.Step 2: Run the show inventory command to display all hardware components: Router# show inventory
  3. 3.Step 3: Review the output to confirm the chassis PID (e.g., ISR4321/K9), power supply PID (e.g., PSU-4321-AC), and any NIM modules (e.g., NIM-2T). Verify serial numbers against the packing slip.
  4. 4.Step 4: If a component is missing, use the show inventory raw command to capture the output for documentation and RMA purposes.
Configuration
! No configuration is required; this is a verification command.
Router# show inventory
NAME: "Chassis", DESCR: "Cisco ISR4321/K9 Chassis"
PID: ISR4321/K9       , VID: V02  , SN: FGL12345678

NAME: "Power Supply Module 0", DESCR: "AC Power Supply"
PID: PSU-4321-AC     , VID: V01  , SN: DCH12345678

NAME: "Module 1", DESCR: "2-Port Serial NIM"
PID: NIM-2T          , VID: V01  , SN: FOC12345678

Verify: Run show inventory and ensure that all expected components appear with correct PIDs and serial numbers. For example, the chassis should show PID ISR4321/K9, and the power supply should show PID PSU-4321-AC.

Watch out: If a component is not listed, it may not be properly seated or recognized. Try reseating the module or power cycling the router. Also, note that the output is static until a reload; hot-swapped modules may not appear immediately.

Identify a Faulty Power Supply in a Catalyst 9300 Stack

A Catalyst 9300 stack is experiencing intermittent power failures. The engineer needs to identify which power supply in the stack is faulty by checking its serial number and part number for replacement.

Topology

Stack: Switch1 (PWR1: PSU-9300-AC, PWR2: PSU-9300-AC) --- Switch2 (PWR1: PSU-9300-AC, PWR2: PSU-9300-AC)

Steps

  1. 1.Step 1: Access the stack master via console or SSH and enter privileged EXEC mode: Switch> enable
  2. 2.Step 2: Run show inventory to list all power supplies: Switch# show inventory | include Power
  3. 3.Step 3: Identify the faulty power supply by cross-referencing the serial number with the device's LED status or environmental logs. For example, if PWR2 on Switch1 is faulty, note its PID and SN.
  4. 4.Step 4: Use the serial number to order a replacement from Cisco or your vendor. Document the output for RMA submission.
Configuration
! No configuration required.
Switch# show inventory | include Power
NAME: "Power Supply Module 1", DESCR: "AC Power Supply"
PID: PSU-9300-AC     , VID: V01  , SN: ART12345678
NAME: "Power Supply Module 2", DESCR: "AC Power Supply"
PID: PSU-9300-AC     , VID: V01  , SN: ART87654321

Verify: After replacement, run show inventory again to confirm the new power supply is recognized with the correct PID and a new serial number.

Watch out: In a stack, power supplies are listed per switch. Ensure you note which switch the faulty supply belongs to. Also, the output may not update until the stack is reloaded or the power supply is re-seated.

Troubleshooting with This Command

When troubleshooting hardware issues, the `show inventory` command is your first step to confirm the physical components present in the device. A healthy output will list all expected hardware with valid PIDs, VIDs, and serial numbers. Problem indicators include missing components (e.g., a power supply not listed), 'Unknown' or 'N/A' in the PID field, or serial numbers that are all zeros or repeated across components, which may indicate counterfeit or faulty hardware.

Focus on the PID and SN fields: a valid PID should match the expected model number (e.g., PSU-9300-AC), and the SN should be unique per component. If a component is missing, check physical seating, power, and compatibility. For example, if a line card is not listed, it may be faulty or not fully inserted.

Use `show inventory raw` to capture the full data for analysis or to compare with a known-good device. Correlate the output with `show environment` to check power supply status (e.g., 'Power Supply 1: OK' vs 'Power Supply 1: Faulty') and with `show module` to see module operational status. A step-by-step diagnostic flow: 1) Run `show inventory` and note any missing or abnormal entries. 2) If a power supply is missing, check `show environment power` for voltage readings. 3) If a module is missing, check `show module` for status (e.g., 'ok' vs 'faulty'). 4) Use `show logging` to see if there are hardware-related error messages (e.g., %PM-4-BAD_MODULE). 5) For suspected counterfeit parts, compare the serial number format against Cisco's official database. 6) If the issue persists, reseat the component, then reload the device to force a re-inventory.

Remember that `show inventory` output is static until a reload or re-insertion; it does not reflect real-time hot-swap events. Therefore, after replacing a component, you may need to reload the device or use `hw-module slot <slot> reload` to refresh the inventory. In summary, `show inventory` is a powerful tool for hardware troubleshooting, but it must be used in conjunction with other show commands and physical inspection to accurately diagnose and resolve hardware problems.

CCNA Exam Tips

1.

CCNA exam may reference show inventory for identifying hardware

2.

Know that PID is the product identifier used for ordering and licensing

3.

Serial numbers (SN) are used for smart licensing and TAC support cases

Common Mistakes

Confusing show inventory (hardware serial numbers) with show version (software version, uptime, license info)

Using show inventory raw adds all FRU-capable sub-components including transceiver modules

show inventory vs show boot

Both 'show inventory' and 'show boot' are privileged EXEC commands used for system troubleshooting, but they address different aspects: hardware identification versus boot parameter configuration. They are often considered together during device replacement or upgrade planning because inventory data ensures correct spare parts, while boot settings confirm the software image to be loaded.

Aspectshow inventoryshow boot
ScopeHardware components (chassis, modules, PSUs, fans) with PID/VID/SN.Boot system settings: image filename, configuration register, BOOT variable.
Configuration modeRead-only; no configuration impact.Read-only; displays current boot parameters, not runtime state.
PersistenceOutput is ephemeral; does not affect device state.Output reflects persistent boot configuration (startup-config or BOOT env var).
PrecedenceNot applicable; inventory is static hardware data.Shows precedence order of boot images (first match wins).
Typical useVerify hardware model/SN for RMA, licensing, or inventory tracking.Confirm next boot image and configuration register before reload.

Use show inventory when you need to document or verify the physical hardware components and their identifying information for asset management or warranty claims.

Use show boot when troubleshooting boot issues, planning an IOS upgrade, or verifying that the correct image will load on the next reload.

Platform Notes

In IOS-XE (e.g., Catalyst 9000 series, ISR 4000 series), the `show inventory` command syntax and output are very similar to classic IOS, but the output may include additional fields like 'Stack' for stackable switches. The command is fully supported. In NX-OS (e.g., Nexus 9000, 7000), the equivalent command is `show inventory` as well, but the output format differs: it lists components in a table with columns for Name, Descr, PID, VID, and SN.

NX-OS also supports `show inventory raw` for scripting. For ASA firewalls, the command `show inventory` is available in ASA 9.x and later, but the output is more limited, typically showing only the chassis and power supplies. In IOS-XR (e.g., ASR 9000, CRS), the command is `show inventory` and it provides detailed hardware inventory, including all FRUs.

However, IOS-XR may require additional privileges (e.g., root-lr) to execute. Between IOS versions (12.x vs 15.x vs 16.x), the output has remained consistent, though newer versions may include additional components like USB modules. Always check the specific platform documentation for any nuances.

Related Commands

Practice for the CCNA 200-301

Test your knowledge with practice questions covering all CCNA 200-301 exam domains.

Practice CCNA 200-301 Questions