From my understanding, an FCoE switch is an FCF if it de-encapsulates the FC frame from the FCoE frame and makes a forwarding decision based on the destination FC_ID in the FC header. FSPF will decide what the next hop is. Subsequently, the FCoE frame will either be forwarded out an FC port or re-encapsulated into an FCoE frame.
Does an FCoE switch in NPV mode make forwarding decsions based on destination FC-ID using FSPF?
Collolary: is an FCoE switch in NPV mode an FCF based on the definiton above?
Rich, not sure I totally agree with you. The definition of an FCF, as I understand it and as defined by a leading FC expert, Robert Kembel, is a device that will de-encapsulate an FCoE frame and make a forwarding decision based on the D_ID in the FC frame header. So the question is what mechanism does the FCoE switch in NPV mode use to forward frames?
Keep in mind that a npv switch does is mapping one port to another, It's no take decisions based on header frame or does encapsulation/desencapsulation. The host depends completly of NPIV upstream switch to FIP works and bring up the vfc interface.
The mechanism is simple, just mapping TF ports to VNP ports in the same vsan to forward all frames. If more than one VNP in the same vsan is avaliable the rebalancing will occur by default or can be done manually if you wish.
The documentation is not so clear about definitions or concepts, but about the "data plane decisions" is clear enough.