Comments on: FCoE and VLAN Trunking on Nexus 5000 http://blog.scottlowe.org/2009/11/03/fcoe-and-vlan-trunking-on-nexus-5000/ The weblog of an IT pro specializing in virtualization, storage, and servers Sat, 13 Mar 2010 21:28:20 +0000 http://wordpress.org/?v=abc hourly 1 By: jane http://blog.scottlowe.org/2009/11/03/fcoe-and-vlan-trunking-on-nexus-5000/comment-page-1/#comment-47511 jane Wed, 17 Feb 2010 07:33:11 +0000 http://blog.scottlowe.org/?p=1722#comment-47511 Hi, Thank you for good article. I wonder if it's possible to do port channel (4x4G FC) between nexus 5000 and mds 9124 ? Thank you Hi,

Thank you for good article.
I wonder if it’s possible to do port channel (4×4G FC) between nexus 5000 and mds 9124 ?

Thank you

]]> By: RTFM Education » Blog Archive » Scott Lowe - NPIV, Nexus, Design Exam.. http://blog.scottlowe.org/2009/11/03/fcoe-and-vlan-trunking-on-nexus-5000/comment-page-1/#comment-46967 RTFM Education » Blog Archive » Scott Lowe - NPIV, Nexus, Design Exam.. Wed, 09 Dec 2009 12:12:36 +0000 http://blog.scottlowe.org/?p=1722#comment-46967 [...] http://blog.scottlowe.org/2009/11/03/fcoe-and-vlan-trunking-on-nexus-5000 [...] [...] http://blog.scottlowe.org/2009/11/03/fcoe-and-vlan-trunking-on-nexus-5000 [...]

]]> By: Brad Hedlund http://blog.scottlowe.org/2009/11/03/fcoe-and-vlan-trunking-on-nexus-5000/comment-page-1/#comment-46528 Brad Hedlund Tue, 03 Nov 2009 17:31:55 +0000 http://blog.scottlowe.org/?p=1722#comment-46528 Scott, Hey, thanks for the plug! :-) Just a few quick notes to compliment your post: 1) Other than having fewer chips, less power, smaller form factor, another major difference between Gen1 & Gen2 CNA's is that Gen2 uses the finalized FC-BB-5 spec with FIP. 2) Cisco and other vendors on the FC-BB-5 effort decided it was best to have VLANs dedicated to just FCoE, rather than sharing the FCoE VLAN with the main data VLAN. This is why trunking at the switchport is required with Gen2. 3) The customer does not *need* to configure VLAN trunking on the CNA itself. Tags for the FCoE VLAN are applied by the CNA hardware regardless of how the Ethernet portion of the CNA is configured in the OS. Furthermore, the FCoE VLAN is automatically discovered by the CNA via FIP. 4) If no VLAN trunking is configured on the Ethernet portion of the CNA then normal data traffic will ride on the default VLAN configured on the switch port, defined by 'switchport access vlan' Cheers, Brad Scott,
Hey, thanks for the plug! :-) Just a few quick notes to compliment your post:

1) Other than having fewer chips, less power, smaller form factor, another major difference between Gen1 & Gen2 CNA’s is that Gen2 uses the finalized FC-BB-5 spec with FIP.

2) Cisco and other vendors on the FC-BB-5 effort decided it was best to have VLANs dedicated to just FCoE, rather than sharing the FCoE VLAN with the main data VLAN. This is why trunking at the switchport is required with Gen2.

3) The customer does not *need* to configure VLAN trunking on the CNA itself. Tags for the FCoE VLAN are applied by the CNA hardware regardless of how the Ethernet portion of the CNA is configured in the OS. Furthermore, the FCoE VLAN is automatically discovered by the CNA via FIP.

4) If no VLAN trunking is configured on the Ethernet portion of the CNA then normal data traffic will ride on the default VLAN configured on the switch port, defined by ’switchport access vlan’

Cheers,
Brad

]]>