Which three statements are correct regarding Fibre Channel over Ethernet (FCOE)? (Choose three.)
A.
The network switch must have Priority-based Flow Control (PFC) set to AUTO.
B.
The network switch must have Priority-based Flow Control (PFC) set to ON.
C.
Each port on the FCoE card must reside on the same vSwitch.
D.
Each port on the FCoE card must reside on a separate vSwitch.
E.
The ESXi host will require a reboot after moving an FCoE card to a different vSwitch.
Explanation:
Explanation/Reference:
A, D, and E are correct:
https://pubs.vmware.com/vsphere-60/index.jsp#com.vmware.vsphere.storage.doc/GUID-6B49866F-7005-4099-84AC-4FB2A1A91F64.html?resultof=%2522%2550%2572%2569%256f%2572%2569%2574%2579%252d%2562%2561%2573%2565%2564%2520%2546%256c%256f%2577%2520%2543%256f%256e%2574%2572%256f%256c%2522%2520
0
0
https://docs.vmware.com/en/VMware-vSphere/5.5/vsphere-esxi-vcenter-server-552-storage-guide.pdf
Section: Configuring Fibre Channel over Ethernet
0
0
Network Switch Guidelines:
On the ports that communicate with your ESXi host, disable the Spanning Tree Protocol (STP). Having the STP enabled might delay the FCoE Initialization Protocol (FIP) response at the switch and cause an all paths down (APD) condition.
The FIP is a protocol that FCoE uses to discover and initialize FCoE entities on the Ethernet.
Turn on Priority-based Flow Control (PFC) and set it to AUTO.
Make sure that you have a compatible firmware version on the FCoE switch.
Network Adapter Best Practices
If you plan to enable software FCoE adapters to work with network adapters, specific considerations apply.
Make sure that the latest microcode is installed on the FCoE network adapter.
If the network adapter has multiple ports, when configuring networking, add each port to a separate vSwitch. This practice helps you to avoid an APD condition when a disruptive event, such as an MTU change, occurs.
Do not move a network adapter port from one vSwitch to another when FCoE traffic is active. If you need to make this change, reboot your host afterwards.
If you changed the vSwitch for a network adapter port and caused a failure, moving the port back to the original vSwitch resolves the problem.
0
0