Refer to the exhibit. A Cisco UCS Series Server fails to boot from SAN, but all other devices in the network that are connected to different switches can boot from SAN. Which set of actions resolves…

The correct answer is A. Create VSAN1011 and assign it with vfc1 and fc1/48 on the N9000 device. The Nexus 9K must be running in FCoE NPV mode and have the FCoE VLAN mapped to the same VSAN that your MDS is using. In the exhibit the VLAN->VSAN mapping was created for VSAN 1011, but the only VSAN membership shown is VSAN 11. The fix is to: 1. On the Nexus 9K: 2. Verify that…

Storage Network

Question

Refer to the exhibit. A Cisco UCS Series Server fails to boot from SAN, but all other devices in the network that are connected to different switches can boot from SAN. Which set of actions resolves the issue?

Exhibits

Options

ACreate VSAN1011 and assign it with vfc1 and fc1/48 on the N9000 device.
BCreate VSAN1011 and assign it with vfc1 and fc1/48 on the N9000 device.
CModify VLAN-to-VSAN mapping to VSAN11 on the N9000 device.
DModify VLAN-to-VSAN mapping to VSAN11 on the N9000 device.

How the community answered

(23 responses)

A
83% (19)
B
4% (1)
C
9% (2)
D
4% (1)

Explanation

The Nexus 9K must be running in FCoE NPV mode and have the FCoE VLAN mapped to the same VSAN that your MDS is using. In the exhibit the VLAN->VSAN mapping was created for VSAN 1011, but the only VSAN membership shown is VSAN 11. The fix is to: 1. On the Nexus 9K: 2. Verify that show fcoe database now lists your server WWN and that show vsan membership shows VLAN 1011->VSAN 11 bound to both vfc1 (the server-facing FCoE port) and fc1/48 (the Enabling fcoe-npv and aligning the VLAN-to-VSAN IDs restores FCoE connectivity so the UCS server can issue FLOGIs and boot from SAN.

Topics

#boot from SAN#VSAN#FCoE VLAN mapping#N9000

Community Discussion

No community discussion yet for this question.

Full 300-615 Practice