Activating a VSAN on a Virtual Fibre Channel (VFC) Interface in FCoE

350-601 By islever Editorial Last updated

Implement Fibre Channel

Short answer

A Map an FCoE VLAN to VSAN 100.

Question

Refer to the exhibit. An engineer configures FCoE in a newly installed data center. Which configuration must be applied to activate VSAN 100 on VFC 100? - Exhibit: Activating a VSAN on a Virtual Fibre Channel (VFC) Interface in FCoE
  1. Map an FCoE VLAN to VSAN 100. Correct Answer
  2. Allow VSAN 100 on interface eth1/12.
  3. Issue the shutdown lan command on VFC 100.
  4. Configure a VLAN on VFC 100.

Key Takeaways

FCoE requires a dedicated VLAN that is mapped to a VSAN (the FCoE VLAN is the Ethernet transport for that VSAN). Without the fcoe vsan mapping, the VFC cannot carry the VSAN's Fibre Channel frames even if the VFC is bound and created.

To carry Fibre Channel traffic over Ethernet, you must bind a VFC interface to a physical Ethernet interface and map an FCoE VLAN to the VSAN. The missing step to 'activate VSAN 100 on VFC 100' is the VLAN-to-VSAN mapping (vlan <id> ; fcoe vsan 100).

Common mistake: Thinking you must allow VSAN 100 on interface eth1/12 (B) or configure a VLAN on VFC 100 (D). The exhibit shows the VFC already bound/created; what is missing is the FCoE VLAN to VSAN mapping that links the Ethernet segment to the Fibre Channel VSAN.

Expert Analysis

Why the Answer Is Correct

FCoE operation requires mapping an FCoE VLAN to the VSAN so the VFC interface can transport that VSAN's FC traffic: vlan 100 then fcoe vsan 100. This is the step that activates VSAN 100 on the VFC. (Typically you also bind the VFC to the Ethernet interface and add the VSAN to the VFC trunk, which the exhibit already shows.)

Why the Other Options Are Wrong

B. Allowing VSAN on eth1/12 is a trunk-allow step, not the activation mapping. C. shutdown lan on VFC disables it. D. Configuring a VLAN on VFC is not how FCoE VSAN activation works — the mapping is done under the VLAN, not on the VFC.

Community Comment Notes

Community: "I think A, missing command: Vlan 200 fcoe vsan 2" (illustrating the vlan to fcoe vsan mapping pattern). Votes A 100.

Official Reference

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_01110.pdf

This link opens the official vendor documentation in a new tab.

Community Votes

A
100%

100% of anonymous learners picked answer A. 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

  1. crooks_1988 👍 2
    I think A, missing command: Vlan 200 fcoe vsan 2
  2. udo2020 👍 1
    I also think it's A!
  3. Rollizo 👍 1 Answered A
    A for sure

Reader comments & corrections

No reader corrections yet — spotted an error or have a note? Share it below.

Log in to comment, report an error, or add a note about this question.

NX-OS Software Downgrade Impact Check

S-grade

Terraform ACI Provider Authentication and APIC DOS Threshold Counting

S-grade

MDS 9000 TE Port Channel for Multi-VSAN Trunking with Mismatch Suspension

S-grade

FCoE FC-Map Configuration to Prevent Cross-Fabric Talk

S-grade

← Back to 350-601 Study Guide