When moving traffic between switches configured with NPV and NPIV features, it's crucial to ensure that the NPV traffic management settings are correctly configured to handle the new interface allocation. This typically involves updating the NPV traffic-map and ensuring that the upstream NPIV core switch recognizes the new paths for the traffic. Additionally, the engineer may need to verify the zoning and VSAN configurations to ensure that the new interface is part of the correct VSAN and that the zoning allows for the FLOGI to be processed correctly on the new interface123.
References:
* Cisco MDS 9000 Series Interfaces Configuration Guide, Release 8.x1.
* Cisco documentation on Configuring N Port Virtualization2.
* Cisco guide on N-Port Identifier Virtualization (NPIV) and N-Port Virtualization (NPV)

To implement traffic monitoring for a server vNIC with fabric failover enabled, ensuring that traffic is sent to an analyzer even during a fabric interconnect failure, the correct configuration is to create two traffic monitoring sessions with different names, one per fabric, and connect an analyzer on each FI as the destination for the monitoring session local to the FI. This setup allows continuous monitoring because if one fabric interconnect fails, the other can still send traffic to its connected analyzer2.
References := Cisco Community Discussion on Understanding Fabric Failure and Failover in UCS

Explanation
https://www.cisco.com/c/en/us/td/docs/switches/datacenter/sw/4_0/dcnm/security/configuration/guide/sec_dcnm Text Description automatically generated