nerdexam
Cisco

300-170 · Question #81

You have a server that has a Cisco UCS CNA. A service profile that has a vNIC and a vHBA is mapped to fabric A. The vNIC is configured to use VLAN 10. VLAN 10 is the native VLAN for the vNIC. The…

The correct answer is A. VSAN 3 can be configured by using VLAN 10 as the FCoE VLAN ID. In FCoE, an FCoE VLAN ID is used to carry Fibre Channel traffic over Ethernet, and this ID is independent of a vNIC's native VLAN, meaning the same VLAN ID can be used for different purposes.

Cisco UCS

Question

You have a server that has a Cisco UCS CNA. A service profile that has a vNIC and a vHBA is mapped to fabric A. The vNIC is configured to use VLAN 10. VLAN 10 is the native VLAN for the vNIC. The vHBA is configured to use VSAN 2. Which description of the configuration is true?

Options

  • AVSAN 3 can be configured by using VLAN 10 as the FCoE VLAN ID
  • BVSAN 2 can read traffic on VLAN 5.
  • CVLAN 10 and VSAN 2 must use the same ID
  • DVSAN 2 can be mapped to other VLANs in fabric A.

How the community answered

(32 responses)
  • A
    75% (24)
  • B
    16% (5)
  • C
    6% (2)
  • D
    3% (1)

Why each option

In FCoE, an FCoE VLAN ID is used to carry Fibre Channel traffic over Ethernet, and this ID is independent of a vNIC's native VLAN, meaning the same VLAN ID can be used for different purposes.

AVSAN 3 can be configured by using VLAN 10 as the FCoE VLAN IDCorrect

An FCoE VLAN ID is an Ethernet VLAN tag designated to carry Fibre Channel over Ethernet traffic for a specific VSAN. While VLAN 10 is currently used as the native VLAN for a vNIC's data traffic, it can also be designated as the FCoE VLAN ID for a different VSAN (like VSAN 3) because these are distinct logical uses of the same VLAN identifier.

BVSAN 2 can read traffic on VLAN 5.

VSANs are logical domains for Fibre Channel traffic, while VLANs are for Ethernet traffic; they operate independently, and a VSAN cannot directly 'read traffic' on an arbitrary data VLAN.

CVLAN 10 and VSAN 2 must use the same ID

There is no requirement for a Fibre Channel VSAN ID and an Ethernet VLAN ID to be numerically identical, as FCoE provides the encapsulation and mapping between them.

DVSAN 2 can be mapped to other VLANs in fabric A.

Each VSAN is typically mapped to a single FCoE VLAN ID on a given Fabric Interconnect for its transport and does not get mapped to multiple different VLANs for its own traffic.

Concept tested: FCoE VLAN and VSAN relationship

Source: https://www.cisco.com/c/en/us/td/docs/unified_computing/ucs/sw/gui/config/guide/3-1/b_ucs_gui_config_guide_3_1/b_ucs_gui_config_guide_3_1_chapter_010000.html

Topics

#Cisco UCS networking#FCoE#VLANs#VSANs

Community Discussion

No community discussion yet for this question.

Full 300-170 Practice