Just finish the FlexPod training, there are 2 things that want to clarify.

The fist thing is about the FCoE connectivity between the Nexus 5K and the Netapp storage. The reference architecture (diagram below) shows that a vPC is formed between the 2 N5K, then the vPC connects to the ifgrp of the Netapp filer.

Here there is an important points to be aware. The vPC can be used to carry traffics for all data VLANs, but not the FCoE traffic. In fact, in the design guide, it mentions that in order to key the SAN A/B design (as from the UCS SAN traffic design, we always keep 2 different storage paths). the FCoE traffic of a particular VSAN (which actuatlly caried by VLAN) will not be send in both links of the vPC. E.g. if the left hand side N5K is carrying the traffic of VSAN 201 over VLAN 101, while the right hand side VSAN 202 over VLAN 102 Then the links from the left hand side N5K to the Netapp will only carry VSAN 201/VLAN 101, while right hand side is VSAN 202/VLAN 102.

While data VLAN will have no restriction, e.g. if VLAN 50 is for data, then the VLAN 50 traffic can be carried over all 4 links (as below).

The 2nd thing is, currrently the FCoE cannot support FCoE port channel, i.e. you can't use 2 parallel links connecting the Netapp filer to the same N5K. Thus for FCoE storage deployment, the reference design is the only valid physical connectivity design.