FCoE Native VLAN Restriction and VSAN Configuration
Short answer
C Configure the FCoE VLAN in the VSAN database before including it in the trunk port.
Question
Key Takeaways
The core trap is assuming any VLAN can carry FCoE; the key insight is that FCoE is explicitly prohibited on native VLANs, requiring both VLAN separation and VSAN mapping.
This question examines the critical restriction that FCoE traffic cannot traverse a native VLAN on Cisco Nexus switches. It establishes that resolving datastore reachability requires moving FCoE to a non-native VLAN and ensuring proper VSAN database configuration.
Common mistake: Many learners select option A solely because it moves FCoE off the native VLAN, overlooking the mandatory requirement to configure the FCoE VLAN in the switch's VSAN database for FCoE initialization.
Expert Analysis
Why the Answer Is Correct
Correct answer: C — Configure the FCoE VLAN in the VSAN database before including it in the trunk port.FCoE (Fibre Channel over Ethernet) relies on a specific mapping between Ethernet VLANs and Fibre Channel VSANs. For the Nexus switch to process FCoE frames correctly, the VLAN must be mapped to a VSAN in the switch's VSAN database. Without this mapping, the switch treats the traffic as standard Ethernet or drops it, preventing access to the storage array. While option A addresses the native VLAN issue, option C is the definitive technical step required to enable FCoE functionality on the switch platform, as the VSAN mapping is prerequisite for FCoE convergence.
Why the Other Options Are Wrong
Option A suggests implementing FCoE on VLAN 10, which avoids the native VLAN restriction, but it does not address the fundamental need for VSAN database configuration. Without the VSAN map, even a non-native VLAN will not function for FCoE. Option B involves Spanning Tree PortFast, which is relevant for edge ports but does not solve the protocol-level FCoE/VSAN mapping issue. Option D suggests separate interfaces, which is unnecessary if the switch supports multiple VSANs/VLANs on trunks, and again fails to mention the critical VSAN configuration step.Community Comment Notes
Commenter Wasamela highlights that the FCoE VLAN needs to be configured in the VSAN database for the switch to recognize the traffic, aligning with the correct technical requirement. OLENDE points out that FCoE is not supported on native VLANs, referencing Cisco documentation, which validates why VLAN 99 (native) fails. Another user agrees with C, confirming the consensus on the necessity of VSAN configuration.Official Reference
This link opens the official vendor documentation in a new tab.
Exam Strategy
Always check for VSAN-to-VLAN mapping when troubleshooting FCoE issues. Remember that FCoE cannot run on native VLANs, so you may need to move traffic, but the VSAN configuration is the enabler.
Frequently Asked Questions
Why can't FCoE run on a native VLAN?
Is moving to VLAN 10 enough to fix FCoE?
Community Votes
67% of anonymous learners picked answer C. Votes are pick records left by other test-takers — they are not the verified answer.
Discussion 3 contributions
Compiled from public community threads and reader submissions, lightly edited for clarity. Handles and vote tallies are shown as recorded, and comments reflect the views of individual contributors.
From public community threads 3
-
Wasamela 👍 2 Answered CI think that FCoE VLAN 99 needs to be configured in the VSAN database for the switch to recognize the traffic as FCoE
-
OLENDE 👍 1 Answered AI think that FCoE is not supported on native vlan. So, the answere may be A https://www.cisco.com/c/en/us/td/docs/switches/datacenter/nexus9000/sw/93x/san_switching/configuration/guide/b-cisco-nexus-9000-nx-os-san-switching-configuration-guide-933/b-cisco-nexus-9000-nx-os-san-switching-configuration-guide-933_chapter_01111.pdf
-
lurker8000 👍 1Agree with C on this
Reader comments & corrections
No reader corrections yet — spotted an error or have a note? Share it below.