Determining I/O Module Type on a Nexus 5548 Switch

Carole Warner Reece

This is just a short post inspired by one of my colleagues. He wanted to know how to tell whether a Nexus 5548 contained a Layer 3 I/O module or a Layer 2 I/O module.

It’s pretty easy, I told him – use the show module command.

L3-5K2# sh module
Mod Ports Module-Type                       Model                  Status
--- ----- --------------------------------- ---------------------- ----------
1   32    O2 32X10GE/Modular Universal Plat N5K-C5548UP-SUP        active *
3   0     O2 Daughter Card with L3 ASIC     N55-D160L3-V2          ok

Mod  Sw              Hw      World-Wide-Name(s) (WWN)
---  --------------  ------  ------------------------------------------------
1    5.2(1)N1(1)     1.0     --
3    5.2(1)N1(1)     1.0     --

Mod  MAC-Address(es)                         Serial-Num
---  --------------------------------------  ----------
. . .

He could then look for a N55-D160L3-V2 or a N55-D160L3 in module 3.

No, that would not work for him. He had two of both types of 5548s, and wanted to determine the module type before mounting it and turning it on. He wanted to mount the correct N5Ks to match his rack elevation diagram.

Hmm. I had answered that very question before, but I forgot what to look for. So I looked around in the Cisco documentation.

After you find the right link, it is easy to tell. Layer 3 modules have an N55-D160L3 or N55-D160L3-V2 product ID located at the spot pointed to by the 1 in the figure below. Layer 2 modules do not indicate any Product ID here.

2013 10 29 N5K I-O module type

Here’s another picture of the Layer 3 I/O module, also known as the Layer 3 Daughter card.

2013 10 29 5548 L3 Daughter card

Note: This is a pull and replace field upgrade. To upgrade from a L2 5548 to a L3 5548, you remove the fan tray modules from the existing L2 I/O module, remove the L2 I/O module, install the L3 module in the 5548, and then reinstall the fan tray modules. More details here:


— cwr

Twitter: @cwreece

One response to “Determining I/O Module Type on a Nexus 5548 Switch

  1. Carole – Thanks for the information.

    Maybe you know the answer to the following question.

    I could not find the meaning used for the naming convention with the I/O modules, specifically for the fields after the “number of ports field”. I believe it has to do with the speed of the module. For example: N7K-F132XP-15

    N7K – Family Name/Series ID

    F1 – Module Type/Generation
    32 – Number of Ports
    XP – ??????????

    1 – Fabric Series
    5 – Number of Fabric Modules for full bandwidth

    Any insight is greatly appreciated.


Leave a Reply


Nick Kelly

Cybersecurity Engineer, Cisco

Nick has over 20 years of experience in Security Operations and Security Sales. He is an avid student of cybersecurity and regularly engages with the Infosec community at events like BSides, RVASec, Derbycon and more. The son of an FBI forensics director, Nick holds a B.S. in Criminal Justice and is one of Cisco’s Fire Jumper Elite members. When he’s not working, he writes cyberpunk and punches aliens on his Playstation.


Virgilio “BONG” dela Cruz Jr.

CCDP, CCNA V, CCNP, Cisco IPS Express Security for AM/EE
Field Solutions Architect, Tech Data

Virgilio “Bong” has sixteen years of professional experience in IT industry from academe, technical and customer support, pre-sales, post sales, project management, training and enablement. He has worked in Cisco Technical Assistance Center (TAC) as a member of the WAN and LAN Switching team. Bong now works for Tech Data as the Field Solutions Architect with a focus on Cisco Security and holds a few Cisco certifications including Fire Jumper Elite.


John Cavanaugh

CCIE #1066, CCDE #20070002, CCAr
Chief Technology Officer, Practice Lead Security Services, NetCraftsmen

John is our CTO and the practice lead for a talented team of consultants focused on designing and delivering scalable and secure infrastructure solutions to customers across multiple industry verticals and technologies. Previously he has held several positions including Executive Director/Chief Architect for Global Network Services at JPMorgan Chase. In that capacity, he led a team managing network architecture and services.  Prior to his role at JPMorgan Chase, John was a Distinguished Engineer at Cisco working across a number of verticals including Higher Education, Finance, Retail, Government, and Health Care.

He is an expert in working with groups to identify business needs, and align technology strategies to enable business strategies, building in agility and scalability to allow for future changes. John is experienced in the architecture and design of highly available, secure, network infrastructure and data centers, and has worked on projects worldwide. He has worked in both the business and regulatory environments for the design and deployment of complex IT infrastructures.