Showing results for 
Search instead for 
Did you mean: 
Field Notice 70545


There are two different configuration options that may or may not complement one another – NPIV enabled VMs within ESXi, and End Host Mode for the FIs. What types of storage ports are they when not using NPIV for VMs?


Please correct the attached diagram. This is for FIs using the default End Host Mode.

Wes Austin
Cisco Employee

This sounds like an exam question.......?



The NPV switch above is the UCS FI, the blades vhba are N-Ports, connecting to a F-Port of the UCS FI. The MDS has to be in NPIV mode !


Thanks for the response.


How are the ports configured with Top of Rack switches in between the FI and the Core - NP Ports? Are the ToR switches still considered NPV edge switches, or are they just logically inseparable from the core?


Also how does VMwares implementation of NPIV for VMs play into this? Do the port types change for the ToR/Core switches?

On the attachment I included in the original post, I had a question mark next to the interface from the NPIV switch to the ToR (or FI). Is this a TNP port?

This design doesn't make sense at all; your NetApp is connected to 2 different MDS ! perfect, it's a physical dual fabric; then you merge everything to a single ToR, which is a single point of failure.

Anyway, your ToR must be NPIV, and the ports between MDS and ToR are E-Port's.

TF-TNP link between an F port in the NPIV core switch (ToR in your case) , and an NP port in the NPV switch (UCS FI in your case):
Enable the F port trunking and channeling protocol on the MDS core switch:
switch(config)# feature fport-channel-trunk

Thanks for continuing forward with the discussion Walter. I still don't fully understand the basics of the port types. Could you label the attached diagram?


I mentioned several times, that your FC design is simply not correct and state of the art.

Take the time and go through this document, and you hopefully understand what I mean;


That is one design. For a large datacenter not everything will run directly from the FI to the core. The original diagram was logical, not physical - I added another ToR to the latest diagram regardless.


Other than FlexPod architectures, do you have any other designs to share? The last place I worked had hundreds of terabytes of consolidated storage with multiple SAN switches. They had a FlexPod as well, but that wasn't the primary design.

The NPIV/NPV in UCS blade is not properly configured, the UCS blades are B200 M5 series
The SAN storage is provided through MDS9706 fabric and the NPIV protocol is able on MDS fabrics and working for Oracle virtual machine and AIX/vios environments

The storage is provided through MDS9706 fabric, connected through UCS FI, and the UCS blades are booted on SAN and installed on Red Hat virtualization version 7.7 and it's properly working.

However, the 4 provided HBA are not virtualization capable, so how these 4 HBA ports can be enabled for supporting virtulization capable.

Thanks, Claude

virsh nodedev-list --cap scsi_host

virsh nodedev-list --cap vports
< empty>


Discovery of HBA(s) capable of NPIV is provided through the virsh command "virsh nodedev-list --cap vports"
which will return a list of scsi_host's capable of generating a vHBA.
These scsi_host's will be described as the parent. If no HBA is returned, then the host configuration should be checked.


It does work on RedHat powerPC linux, it looks like there is a setting missing on UCS bios.



No it's not. It's my relentless pursuit of knowledge.

Recognize Your Peers
Content for Community-Ad