Fabric Interconnects Modes End Host (NPV) (default and recommended) FCoE is performed from Server/Chassis up to FI's FCoE is decapsulated, and FLOGI's turned into FDISC's and transmitted to upstream FC switch F-Port running in NPIV mode FCoE Northbound of FI's is supported in 2.1 (Del Mar) FC Switching Mode Limited use No zoning configuration in 2.0 - get's zoning form upstream switch (Zoning is support in UCS Mgr. 2.1) For UCS 2.0 upstream switch must be a MDS or Nexus 5K to get zoning FC Switching is necessary for storage array direct connect Designed for very small scale or demo environments HBA's and pWWN's Presented as 2 normal HBA's to OS using standard PCIe virtualization Standard OS level Multipathing software PowerPath /DMP/MPIO No hardware failover (standard for Fibre Channel Network) WWN/pWWN Emulex and Qlogic and Burn In Addresses (BIA) M81KR/PALO/VIC don't have a BIA There are three for pWWN usages Derived form the BIA (Only for Emulex or Qlogic) Manually assign From a Pool VSAN's Trunking and Port Channels Can have an ISL with multiple VSAN's heading northbound out of the FI to FC Fabric Cannot limit which VSAN's head northbound our of FI (they all do) in 2.0 Can limit which VSAN's are allowed to transverse onto the NB switch from MDS/N5K trunk Limit of 32 VSAN's per UCS system Port Channel can and should be used with trunking Can use up to 16FC interfaces in a Port Channel Hasing algorithm uses Src, Dst, and Exch ID (OxID (originator exchange identifier) - same as N5K Non Configurable Both Port Channeling and Trunking work in both NPV and FC Switching modes (remember FC Switching mode you need MDS or N5K F-PortChannel mode) If you don't use Port-Channeling, vHBA would need to re-FLOGI need to enable "feature fort-channel-trunk" on MDS Direct Connect FC or FCoE Storage Must be in FC Switching mode Remember FC and Ethernet modes are independent Still must have upstream FC/FCoE switch to configure zoning (in 2.0) Reasoning behind the need for a MDS or N5K for zoning Would only use if you have to transition between FC and FCoE Switching will be local on FI's and they do get a FC domain ID Configuration Topology  Click on the SAN TAB in UCS manger You'll see the following  Click on SAN Cloud and then SAN Uplinks Manager  On MDS's make sure the configuration for the Ports are current show run int fc1/7-8  Check the Port-Channel settings sho run int po2  show run | in feature (to make sure the correct features are enabled)  Back in UCS Manger click on SAN Tab, click on SAN Cloud, and right click on Fabric A and click Create Port-Channel  Name the Port-Channel  Give it a name Po1 with an ID of 11   Next enable Port Channel  VSAN Creations  You also have some pre-defined policies that get assigned to the vHBA's and you can also create your own if needed.  You can do a show flogi database to make sure the FI's have logged into the fabric correctly and you can see the WWPN form the Equipment Tab, click on FI A, Click on Physical Ports, and finally click on Uplink FC ports  |
Blog >