Vlans on FCoE uplinks in UCS

Hi, we are running UCS ver 2.1.1e. We are doing multihop FCoE to the N5ks from the FIs. I noticed that if you bind the FCoE uplinks into a FCoE port-channel, you cannot tag ethernet vlans on it. BUT if you keep them as just FCoE uplinks you can tag vlans on them. Why is this behaviour?

Hi, so I have a scenario where the FIs are connected to N7ks for the LAN part and to the N5ks for FCoE. I want to steer certain vlans to the n5ks due to some requirement by using the vlan-groups. Ports 23 and 24 from the FI-A connect to n5k-A and the same for B side. config is -
ucs-A(nxos)# sh run interface eth1/23-24
version 5.0(3)N2(2.11e)
interface Ethernet1/23
description C: FcoeUplink
pinning border
switchport mode trunk
switchport trunk native vlan 4049
switchport trunk allowed vlan 2009,3009,4048-4049,4080-4081
no shutdown
interface Ethernet1/24
description C: FcoeUplink
pinning border
switchport mode trunk
switchport trunk native vlan 4049
switchport trunk allowed vlan 2009,3009,4048-4049,4080-4081
no shutdown
The VFCs config is -
wdb-labucs-A(nxos)# sh run int vfc 703-704
version 5.0(3)N2(2.11e)
interface vfc703
bind interface Ethernet1/23
switchport mode NP
no shutdown
interface vfc704
bind interface Ethernet1/24
switchport mode NP
no shutdown
Now, even though I see that the ethernet vlans are allowed on the physical ports, why don`t I see the physical interfaces under the vlan groups? Why do I need to change them to a Unified port?

Similar Messages

Vlan overlapping when upgrading to ucs 2.0x

HI All,
we are going to upgrade to ucs 2.0x from 1.4.3(L).
As we are using vlan 1 as native vlan for ethernet and VSAN 1 FCoe vlan (which is default for 1.4.3L).
Althuogh we are not using VSAN1 at all, our current configuration is using over-lapping vlan for VSAN and Ethernet accordingt to UCS firmware upgrade guide and will create critical alert.
SO I am trying to change VSAN 1 FCoE vlan to vlan 4048 before firmware upgrade The reason picking up vlan 4048 is that we want to keep consistence for UCS new build and upgrade (4048 is default FCoE vlan for new installation of UCS 2.0.)
When i log in the UCS, i found vlan 4048 looks like has been used by UCS internally (cisco doc suggest the same)
4048 VLAN4048 active Po1 (Po1 is uplink port channel)
For the VSAN 1 FCoe VLan change, i have 2 questions:
1st question is: Can I change VSAN 1 FCoE vlan to 4048 on 1.4.3(L)? Does anybody has experience for this?
2nd question is:
If answer for Q1 is YES, What's the impact on UCS system (ESX hosts, bare-metal server and virtual machine) when I am changeing VSAN 1 FCoE to vlan 4048?

Hello,
Before upgrade, 4048 is already allocated as fcoe-native-vlan.
scope fc-storage
show detail
set fcoe-storage-native-vlan ?
4048-4093 FCoE Storage native VLAN - valid values: 1-3967,4048-4093
To achieve your configuration requirement of having FCoE VLAN ID to 4048 for VSAN 1, first we need to change fcoe storage native vlan to 4049.
Then, you can assign 4048 to VSAN 1.
Regarding the status of VLAN ID 4048, it is user configurable.
http://www.cisco.com/en/US/docs/unified_computing/ucs/sw/gui/config/guide/2.0/b_UCSM_GUI_Configuration_Guide_2_0_chapter_010000.html
Guidelines for VLAN IDs
VLAN 4048 is user-configurable. However, Cisco UCS Manager uses VLAN 4048 for the following default values. If you want to assign 4048 to a VLAN, you must reconfigure these values
Can you please share the information on the screen shot i.e which section of UCSM GUI 2.0 configuration doc where it is listed 4048 as reserved VLAN ?
I will follow it up to get it updated.
Thanks
HTH
Padma

Management vlan with the 1000V and UCS

If I want to use VLAN 10 for management, I would have to configure the following:
1000V -VM vEthernet port profile access port with VLAN 10, Ethernet uplink profile includes VLAN 10
UCS - vNIC in Service Profile, include VLAN 10, and include VLAN 10 in uplink trunk from UCS
Upstream switch: Include VLAN 10 in trunk port.
OK?
Now, this management VLAN, can I Iuse this for everything? I mean for 1000V management VLAN, vSPhere management, FI management and switch management? Or should for instance the 1000V management be different from the others?

Hi Atle,
Yes, what you have mentioned is the correct in terms of activities you need to carry out. However i would like to add a few:
1) define the vlan on the UCS - unless you do this you will not be able to add it to the vnic. Plus once you have the vlan defined it will automatiaclly get added to the trunk list on the uplinks ports (unless you l2-disjoint configured)
You can have the same vlan for all the management, unless you have certain traffic you would not like certain device to see / reach.
./Abhinav

Prevent vlan 1 on an uplink in UCS

Folks,
I have 2 disjoing domains and I am using the new feature in UCS 2.1 to allow only certain vlans over a port channel. But, What I am noticing is that there is no way to prevent vlan 1 to flow on that port channel on the UCS side even though i do not see it in the vlan manager.
Any thoughts would be highly appreciated.

VLAN 1 will always be allowed on your uplinks regardless of disjoint L2 configuration. This is one of the limiations of the system. This is called out in the config guide:
http://www.cisco.com/en/US/docs/unified_computing/ucs/sw/cli/config/guide/2.0/b_UCSM_CLI_Configuration_Guide_2_0_chapter_010100.html#concept_4E7BF4F5FA754183B5FE3298755800A1
Regards,
Robert

FCoE uplink is down on vsan

Hello, I have a problem connecting nexus switches to fabric interconnects.
I have created vsan's, unified uplinks, vfc interfaces on nexus, vlan to vsan mappings but still I see this fault in the event log.
HBA templates and HBA's are also created.
I have 2 nexus 5548up switches connected to UCS 6324 FI's.

Walter, I believe this is correct article in my case: http://www.cisco.com/c/en/us/support/docs/switches/nexus-5000-series-switches/116248-configure-fcoe-00.html
So I've done everything as described, including port-channel, but still have the same issue, do I miss something?
I've performed a migration from IBM Servers and FC-switches to UCS and now myb storage is connected via iSCSI, my goal is to make it FcOE connected so I'd have all the benefits of FC in unified fabric. This is my first experience with UCS and FcOE.
Here is what I have on Nexus side for now:
vfc50 is trunking
    Bound interface is port-channel4
    Hardware is Ethernet
    Port WWN is 20:31:8c:60:4f:1f:bd:ff
    Admin port mode is F, trunk mode is on
    snmp link state traps are enabled
    Port mode is TF
    Port vsan is 500
    Trunk vsans (admin allowed and active) (500)
    Trunk vsans (up)                       ()
    Trunk vsans (isolated)                 ()
    Trunk vsans (initializing)             (500)
    1 minute input rate 0 bits/sec, 0 bytes/sec, 0 frames/sec
    1 minute output rate 0 bits/sec, 0 bytes/sec, 0 frames/sec
      0 frames input, 0 bytes
        0 discards, 0 errors
      0 frames output, 0 bytes
        0 discards, 0 errors
And UCS:
Interface Vsan Admin Admin Status Bind Oper Oper
Mode Trunk Info Mode Speed
Mode (Gbps)
vfc765 500 F on trunking Veth8957 TF auto
vfc767 500 F on trunking Veth8959 TF auto
vfc776 1 E on trunking Po4 TE 20
FI-A-A(nxos)# sh flogi data
INTERFACE VSAN FCID PORT NAME NODE NAME
vfc765 500 0x5f0000 20:00:00:25:b5:00:0a:1f 20:00:00:25:b5:00:00:0f
vfc767 500 0x5f0020 20:00:00:25:b5:00:0a:0f 20:00:00:25:b5:00:00:1f
I don't understand why vfc's 765,767 are not binded to Po4.

VLAN Tagging from Windows on UCS B200m Server

We have two B200m blades that we have installed with Windows 2008 R2 and need to determine if the current driver set available for the MK81R/MK82R for Windows 2008 R2 supports VLAN tagging from inside of Windows. If anyone could point me in the right direction I would surely appreciate it!

Windows has never been a great OS for trunking multiple VLANs. The best way to set an individual adapter to a certain VLAN is to set it as the Native VLAN on the UCSM side. The order of the vNICs seen in the UCSM and the order that windows sees them is not always the same so match them up by MAC address, then set the Native VLAN to the correct one on the vNIC within the UCSM and you should be all set within Windows.
Drivers can be found on the Cisco.com Support page, under
Downloads Home
Products
Unified Computing and Servers
Cisco UCS B-Series Blade Server Software
Unified Computing System (UCS) Drivers

Multiple vlans but shared uplink

I have 8 apartments that have a single internet connection coming into the building, I then have a PoE Access Point in each of the 8x apartments.
What I would like to be able to do is to have each apartment within its own vlan, but to be able to use the internet via one of the non-PoE ports (port 9 say) but do not want residents in different flats to be able to see each others devices on the same network.
I have a Cisco SG 300-10MP which has 8x PoE ports and 2x Ethernet ports, one of which my Internet connection is plugged into (using WiMax).
Apologies if it is the wrong place to locate the question, or if it is a fundamental solution which would do the trick, but I certainly welcome any advice.
Thanks in advance!

Dave,
Thank you for pointing me in the right direction - I was sure it must be a basic/common request, im just out of touch with the correct terminology.
Appreciate such a quick response though and a very informative one too!
Thanks,
Alex

Various questions on uplink profiles, CoS, native VLAN, downlink trunking

I will be using vPC End Host Mode with MAC-pinning. I see I can further configure MAC-Pinning. Is this required or will it automatically forward packets by just turning it on? Is it also best not to enable failover for the vnics in this configuration? See this text from the Cisco 1000V deployment Guide:
Fabric Fail-Over Mode
Within the Cisco UCS M71KR-E, M71KR-Q and M81KR adapter types, the Cisco Unified Computing System can
enable a fabric failover capability in which loss of connectivity on a path in use will cause remapping of traffic
through a redundant path within the Cisco Unified Computing System. It is recommended to allow the Cisco Nexus
1000V redundancy mechanism to provide the redundancy and not to enable fabric fail-over when creating the
network interfaces within the UCS Service Profiles. Figure 3 shows the dialog box. Make sure the Enable Failover
checkbox is not checked."
What is the 1000V redundancy?? I didn't know it has redundancy. Is it the MAC-Pinning set up in the 1000V? Is it Network State Tracking?
The 1000V has redundancy and we can even pin VLANs to whatever vNIC we want. See Cisco's Best Practices for Nexus 1000V and UCS.
Nexus1000V management VLAN. Can I use the same VLAN for this and for ESX-management and for Switch management? E.g VLan 3 for everything.
According to the below text (1000V Deployment Guide), I can have them all in the same vlan:
There are no best practices that specify whether the VSM
and the VMware ESX management interface should be on the same VLAN. If the management VLAN for
network devices is a different VLAN than that used for server management, the VSM management
interface should be on the management VLAN used for the network devices. Otherwise, the VSM and the
VMware ESX management interfaces should share the same VLAN.
I will also be using CoS and Qos to prioritize the traffic. The CoS can either be set in the 1000V (Host control Full) or per virtual adapter (Host control none) in UCS. Since I don't know how to configure CoS on the 1000V, I wonder if I can just set it in UCS (per adapter) as before when using the 1000V, ie. we have 2 choices.
Yes, you can still manage CoS using QoS on the vnics when using 1000V:
The recommended action in the Cisco Nexus 1000V Series is to assign a class of service (CoS) of 6 to the VMware service console and VMkernel flows and to honor these QoS markings on the data center switch to which the Cisco UCS 6100 Series Fabric Interconnect connects. Marking of QoS values can be performed on the Cisco Nexus 1000V Series Switch in all cases, or it can be performed on a per-VIF basis on the Cisco UCS M81KR or P81E within the Cisco Unified Computing System with or without the Cisco Nexus 1000V Series Switch.
Something else: Native VLANs
Is it important to have the same native VLAN on the UCS and the Cisco switch? And not to use the default native VLAN 1? I read somewhere that the native VLAN is used for communication between the switches and CDP amongst others. I know the native VLAN is for all untagged traffic. I see many people set the ESXi management VLAN as native also, and in the above article the native VLAN (default 1) is setup. Why? I have been advised to leave out the native VLAN.
Example:Will I be able to access a VM set with VLAN 0 (native) if the native VLAN is the same in UCS and the Cisco switch (Eg. VLAN 2)? Can I just configure a access port with the same VLAN ID as the native VLAN, i.e 2 and connect to it with a PC using the same IP network address?
And is it important to trunk this native VLAN? I see in a Netapp Flexpod config they state this: "This configuration also leverages the native VLAN on the trunk ports to discard untagged packets, by setting the native VLAN on the port channel, but not including this VLAN in the allowed VLANs on the port channel". But I don't understand it...
What about the downlinks from the FI to the chassis. Do you configure this as a port channel also in UCS? Or is this not possible with the setup described here with 1000V and MAC-pinning.
No, port channel should not be configured when MAC-pinning is configured.
[Robert] The VSM doesn't participate in STP so it will never send BPDU's. However, since VMs can act like bridges & routers these days, we advise to add two commands to your upstream VEM uplinks - PortFast and BPDUFilter. PortFast so the interface is FWD faster (since there's no STP on the VSM anyway) and BPDUFilter to ignore any received BPDU's from VMs. I prefer to ignore them then using BPDU Gaurd - which will shutdown the interface if BPDU's are received.
-Are you thinking of the upstream switch here (Nexus, Catalyst) or the N1kV uplink profile config?
Edit: 26 July 14:23. Found answers to many of my many questions...

Answers inline.
Atle Dale wrote:
Something else: Native VLANsIs it important to have the same native VLAN on the UCS and the Cisco switch? And not to use the default native VLAN 1? I read somewhere that the native VLAN is used for communication between the switches and CDP amongst others. I know the native VLAN is for all untagged traffic. I see many people set the ESXi management VLAN as native also, and in the above article the native VLAN (default 1) is setup. Why? I have been advised to leave out the native VLAN.[Robert] The native VLAN is assigned per hop. This means between the 1000v Uplinks port profile and your UCS vNIC definition, the native VLAN should be the same. If you're not using a native VLAN, the "default" VLAN will be used for control traffic communication. The native VLAN and default VLAN are not necessarily the same. Native refers to VLAN traffic without an 802.1q header and can be assigned or not. A default VLAN is mandatory. This happens to start as VLAN 1 in UCS but can be changed. The default VLAN will be used for control traffic communication. If you look at any switch (including the 1000v or Fabric Interconnects) and do a "show int trunk" from the NXOS CLI, you'll see there's always one VLAN allowed on every interface (by default VLAN 1) - This is your default VLAN.Example:Will I be able to access a VM set with VLAN 0 (native) if the native VLAN is the same in UCS and the Cisco switch (Eg. VLAN 2)? Can I just configure a access port with the same VLAN ID as the native VLAN, i.e 2 and connect to it with a PC using the same IP network address?[Robert] There's no VLAN 0. An access port doesn't use a native VLAN - as its assigned to only to a single VLAN. A trunk on the other hand carries multiple VLANs and can have a native vlan assigned. Remember your native vlan usage must be matched between each hop. Most network admins setup the native vlan to be the same throughout their network for simplicity. In your example, you wouldn't set your VM's port profile to be in VLAN 0 (doens't exist), but rather VLAN 2 as an access port. If VLAN 2 also happens to be your Native VLAN northbound of UCS, then you would configured VLAN 2 as the Native VLAN on your UCS ethernet uplinks. On switch northbound of the UCS Interconnects you'll want to ensure on the receiving trunk interface VLAN 2 is set as the native vlan also. Summary:1000v - VM vEthernet port profile set as access port VLAN 21000v - Ethernet Uplink Port profile set as trunk with Native VLAN 2UCS - vNIC in Service Profile allowing all required VLANs, and VLAN 2 set as NativeUCS - Uplink Interface(s) or Port Channel set as trunk with VLAN 2 as Native VLANUpstream Switch from UCS - Set as trunk interface with Native VLAN 2From this example, your VM will be reachable on VLAN 2 from any device - assuming you have L3/routing configured correctly also.And is it important to trunk this native VLAN? I see in a Netapp Flexpod config they state this: "This configuration also leverages the native VLAN on the trunk ports to discard untagged packets, by setting the native VLAN on the port channel, but not including this VLAN in the allowed VLANs on the port channel". But I don't understand it...[Robert] This statement recommends "not" to use a native VLAN. This is a practice by some people. Rather than using a native VLAN throughout their network, they tag everything. This doesn't change the operation or reachability of any VLAN or device - it's simply a design descision. The reason some people opt not to use a native VLAN is that almost all switches use VLAN 1 as the native by default. So if you're using the native VLAN 1 for management access to all your devices, and someone connects in (without your knowing) another switch and simply plug into it - they'd land on the same VLAN as your management devices and potentially do harm.What about the downlinks from the FI to the chassis. Do you configure this as a port channel also in UCS? Or is this not possible with the setup descrived here with 1000V and MAC-pinning.[Robert] On the first generation hardware (6100 FI and 2104 IOM) port channeling is not possible. With the latest HW (6200 and 2200) you can create port channels with all the IOM - FI server links. This is not configurable. You either tell the system to use Port Channel or Individual Links. The major bonus of using a Port Channel is losing a link doesn't impact any pinned interfaces - as it would with individual server interfaces. To fix a failed link when configured as "Individual" you must re-ack the Chassis to re-pinn the virtual interfaces to the remaining server uplinks. In regards to 1000v uplinks - the only supported port channeling method is "Mac Pinning". This is because you can't port channel physical interfaces going to separate Fabrics (one to A and one to B). Mac Pinning gets around this by using pinning so all uplinks can be utilized at the same time.--[Robert] The VSM doesn't participate in STP so it will never send BPDU's. However, since VMs can act like bridges & routers these days, we advise to add two commands to your upstream VEM uplinks - PortFast and BPDUFilter. PortFast so the interface is FWD faster (since there's no STP on the VSM anyway) and BPDUFilter to ignore any received BPDU's from VMs. I prefer to ignore them then using BPDU Gaurd - which will shutdown the interface if BPDU's are received.-Are you thinking of the upstream switch here (Nexus, Catalyst) or the N1kV uplink profile config?[Robert] The two STP commands would be used only when the VEM (ESX host) is directly connected to an upstream switch. For UCS these two commands to NOT apply.

Nexus 5548UP FCoE to C series UCS

Ok here is the scenario
nexus 5548 switch ---- fex 2232 --- UCS C series (C220)
snippets of the configuration:
vlan 1100
fcoe vsan 1100
vlan database
vsan 1100
fex 100
description 2232-A
fcoe
int ethernet100/1/1
switchport
switchport mode trunk
switchport trunk allowed vlan 10,1100
interface vfc100
bind interface ethernet100/1/1
switchport trunk allowed vsan 1100
no shut
so it is configured above, the vfc interface won't trunk unless I do the following:
vsan database
vsan 1100 interface vfc100
I found this document that describes mapping VSANs to VLANs example configuration (page 8)

Each fc and/or vfc interface must be member of a VSAN; by default, they belong all initially to VSAN 1.

Uplink port VLAN

Hi there:
I'm lost
I know when you have for example two uplink ports that belong at the same vlan, and two or more vNICs asociated at this vlans, pinning happen dinamically
I know how configure a VLAN and assign it to an vNIC
But I can't found how to associate the uplink port to this VLAN in UCS manager
Can anybody help me please
Thank you in advance
Al

Al,
In the end-host mode for the ethernet, once you define the vlan in the UCSM the vlan is automatically assgined / configured on all the uplink and the server ports.
Here is a chapter from the config guide:
http://www.cisco.com/en/US/docs/unified_computing/ucs/sw/gui/config/guide/2.0/UCSM_GUI_Configuration_Guide_2_0_chapter15.html
However starting with version 2.0 there is a feature under which you can control or confiure different vlans on different uplink ports. This feature is L2-disjoint feature and here is a URL to configure it:
http://www.cisco.com/en/US/docs/unified_computing/ucs/sw/gui/config/guide/2.0/UCSM_GUI_Configuration_Guide_2_0_chapter21.html
Hope this helps!
./Abhinav

UCS FCoE VSAN 1 down

Any way to clear these faults?
F1081 2013-02-21T15:04:24.658 157614 san Member 1/31 of Port-Channel 8 on fabric interconnect A is down, membership: down
F1081 2013-02-21T15:04:24.658 157613 san Member 1/32 of Port-Channel 8 on fabric interconnect A is down, membership: down
Have FCoE setup between 6248s and Nexus 5548s. Using VSAN 20 on Fabric A and VSAN 40 on Fabric B.
Why is VSAN 1 trying to initialize when I have the FCoE port-channel mapped to VSAN 20 in UCSM? Any way to set the allowed trunk vsan list?
Everything is working just would like the anoying faults to go away

Hi,
This sounds like:
FCoE Uplink vsan membership fault for any vsan not configured upstream
Symptom:
Fabric Vsan Membership Down fault message on FCoE uplink portsSeverity: Major
Code: F1083
Name: Fabric Vsan Membership Down
Conditions:
Observed with UCSM 2.1 and when FCoE uplink port is configured on the Fabric Interconnect
Workaround:
None.Error message is cosmetic.
http://tools.cisco.com/Support/BugToolKit/search/getBugDetails.do?method=fetchBugDetails&bugId=CSCud81857
I'd open a case on it and have them link it to the bug if it is indeed the case

FCOE over VPC

Hi All,
Acc. to attached scenario.
Can i make VFC between two Nexus switches. As i don't want another seperate dedicated link for storage traffic. I want to send storage traffic only on eth 1/4 from down nexus 1 to northbound nexus 2. i.e. Nexus 1 ---> Nexus 2
And LAN traffic will follow both links in VPC as usual. Nexus 1 ---> Nexus 2 and Nexus 1 ---> Nexus 3
If i make interface VFC 23 on two nexus only i.e. on nexus 1 and nexus 2
Nexus 1 conf
interface vfc 23
bind interface eth 1/4 ( Not binding port channel 23)
vsan 1011 interface vfc 23
Interface port-channel 23
Switchport mode trunk
spanning-tree port type network
vlan 1011
fcoe vsan1011
vsan database
vsan 1011
interface eth 1/4
channel-group 23 mode active
interface eth 1/5
channel-group 23 mode active
Nexus 2 Conf:
interface vfc 23
bind interface eth 1/4
vsan 1011 interface vfc 23
Interface port-channel 23
Switchport mode trunk
spanning-tree port type network
vpc 23
vlan 1011
fcoe vsan1011
vsan database
vsan 1011
interface eth 1/4
channel-group 23 mode active
Nexus 3 conf:
Interface port-channel 23
Switchport mode trunk
spanning-tree port type network
vpc 23
interface eth 1/4
channel-group 23 mode active

Hello Stephen,
One of the reason on why FCoE over vPC ( between UCS and N5K ) is not supported is that UCS currently allows all VSANs on all uplinks and cannot be pruned.
HTH
Padma

Ucs 2.2(1d) leads to vmware network outtages

Since the update to 2.2(1d) we have network timeouts / outtages between vsphere vm's hosted on ucs b-series servers and the rest of the world outside vmware / ucs. first occured with sles10 guests, but windows 2008 and more are also involved. any idas or similar experiences?

Hello,
I don't want this to be taken as a recommendation, but more as an informative post in response to your concerns about the the Cisco tech may have said in regards to it being expected behavior. But just for reference, this would be in line with your option #3 you have listed above.
Layer 2 Disjoint Upstream Packet Forwarding in End-Host Mode
Server links (vNICs on the blades) are associated with a single uplink port (which may also be a PortChannel). This process is called pinning, and the selected external interface is called a pinned uplink port. The process of pinning can be statically configured (when the vNIC is defined), or dynamically configured by the system.
In Cisco UCS Manager Release 2.0, VLAN membership on uplinks is taken into account during the dynamic pinning process. VLANs assigned to a vNIC are used to find a matching uplink. If all associated VLANs of a vNIC are not found on an uplink, pinning failure will occur.
The traffic forwarding behavior differs from that in Cisco UCS Manager Release 1.4 and earlier in the way that the incoming broadcast and multicast traffic is handled. A designated receiver is chosen for each VLAN, rather than globally as in Cisco UCS Manager Release 1.4 and earlier.
This is from the following link:
http://www.cisco.com/c/en/us/solutions/collateral/data-center-virtualization/unified-computing/white_paper_c11-692008.html
So as you can see, that behavior has been present since 1.4 release and onwards. There will only be one designated receiver per vlan. This may be why the tech mentioned that as a viable workaround. in your case, it would be to ensure that the ports we need to multicast are set to do so on a specific vlan, and that that vlan is only allowed on one interface (or port-channel). If we have it enabled on multiple uplinks and they are not listening on the one they are pinned to, we may see that traffic be dropped.
Regards,
-Gabriel

N5K running 5.0(2)N2(1) support for FCOE VSAN-trunking

Hi, from 5.0(2)N2(1) on , on the N5K on a FCoE Port VSAN-trunking should be supported on VE-Port and VF-Port.
But I could not find a doc how to configure
classical configuration where I assign one VSAN to every FCoE-Port
vlan 111
name ETH_111
vlan 112
name ETH_112
vlan 113
name ETH_113
vlan 1011
name VSAN_1
fcoe vsan 1
vlan 1012
name VSAN_2
fcoe vsan 2
vlan 1013
name VSAN_3
fcoe vsan 3
vsan database
vsan 1 interface vfc 1
vsan 2 interface vfc 2
vsan 3 interface vfc 3
int vfc 1
bind interface eth 1/1
int vfc 2
bind interface eth 1/2
int vfc 3
bind interface eth 1/3
interface eth 1/1
switchport mode trunk
switchport trunk allowed vlan 111,1011
spanning-tree port type edge trunk
spanning-tree bpduguard enable
interface eth 1/2
switchport mode trunk
switchport trunk allowed vlan 112,1012
spanning-tree port type edge trunk
spanning-tree bpduguard enable
interface eth 1/3
switchport mode trunk
switchport trunk allowed vlan 113,1013
spanning-tree port type edge trunk
spanning-tree bpduguard enable
no I want to configure FCoE trunk transporting all 3 VSANs on Eth 1/4
interface vfc 4
description FCoE Uplink
bind interface eth 1/4
switchport trunk allowed vsan 1-3
interface eth 1/4
description FCoE Uplink
switchport mode trunk
switchport trunk allowed vlan 1011,1012,1013
spanning-tree port type edge trunk
spanning-tree bpduguard enable
so I assume I do not have to configure anything additional in the VSAN-database, I saw it s only possible to assign a VFC-Interface to only one VSAN.
Does anybody have more infos about configuring VSAN-trunking on FCoE Ports ?
Thx in Advance
Hubert

Unless you need to keep the data separate, there is not a requirement to place each VFC interface in a different VSAN. They can all exist in the same VSAN, and you can isolate them from each other using zoning with in the VSAN.
What are you looking to trunk the FCoE connections to? At this point the only option is another N5K. Eventually, there will be FCoE trunk support between the N5K, the Cisco N7K, and the MDS.
You are correct that for the trunk port, you do not need to ad any VSAN database entry. It will reside in the default VSAN which is normally VSAN 1.
It this not working for you, or is this a planned configuration that you want to verify.
You do need to make the VFC 4 interface in your post an E port. 'switchport mode e' is the command.
Here is a snip from a working FCoE trunk port on a 5K. It happens to use an Ethernet port channel bound to the VFC.
pod2-N5010-82# sh run interface port-channel 402
version 5.0(2)N1(1)
interface port-channel402
switchport mode trunk
switchport trunk allowed vlan 122,222
speed 10000
pod2-N5010-82# sh run interface vfc 402
version 5.0(2)N1(1)
interface vfc402
bind interface port-channel402
switchport mode E
switchport trunk allowed vsan 122
switchport trunk allowed vsan add 222
no shutdown
pod2-N5010-82# sh int vfc 402
vfc402 is trunking
    Bound interface is port-channel402
    Hardware is Virtual Fibre Channel
    Port WWN is 21:91:00:05:9b:20:a9:7f
    Peer port WWN is 00:00:00:00:00:00:00:00
    Admin port mode is E, trunk mode is on
    snmp link state traps are enabled
    Port mode is TE
    Port vsan is 1 <====
    Trunk vsans (admin allowed and active) (122,222)
    Trunk vsans (up)                       (122,222)
    Trunk vsans (isolated)                 ()
    Trunk vsans (initializing)             ()
HTH,
Mike

FCoE Nexus 5000

Hi,
I have a Nexus 5000 conected with a UCS C-200 with qlogic CNA in FCoE. The ethernet traffic is ok, but FC dont work fine, i thinks that i have configured all ok, by the show int vfc show the trunk vsan in initializating mode and i dont find what is the problem
switch(config-if)# sh int vfc 1
vfc1 is trunking
    Bound interface is Ethernet1/9
    Port description is Conexion FC con UCS1
    Hardware is Virtual Fibre Channel
    Port WWN is 20:00:00:0d:ec:e8:2c:7f
    Admin port mode is F, trunk mode is on
    snmp link state traps are enabled
    Port mode is TF
    Port vsan is 1
    Trunk vsans (admin allowed and active) (1)
    Trunk vsans (up)                       ()
    Trunk vsans (isolated)                 ()
    Trunk vsans (initializing)             (1)
    1 minute input rate 0 bits/sec, 0 bytes/sec, 0 frames/sec
    1 minute output rate 0 bits/sec, 0 bytes/sec, 0 frames/sec
      0 frames input, 0 bytes
        0 discards, 0 errors
      0 frames output, 0 bytes
        0 discards, 0 errors
    last clearing of "show interface" counters never
    Interface last changed at Mon Dec 20 19:59:31 2010
switch(config-if)# show port internal info interface vfc 1
vfc1 - if_index: 0x1E000000, phy_port_index: 0x1000
     local_index: 0xffff
Admin Config - state(up), mode(F), speed(auto), trunk(on)
    beacon(off), snmp trap(on), tem(false)
    description(Conexion FC con UCS1)
    port owner()
Operational Info - state(trunking), mode(TF), speed(auto), trunk(on)
    state reason(None)
    phy port enable (1), phy layer (FC), port_osm_mode(OSM)
    participating(1), fcid(0x000000), bb_scn(0)
    config port vsan (1), oper port vsan (1)
    rx bb_credit(0), rx bb_credit multiplier(0)
    rx bb_credit performance buffers(0), tx bb_credit(0)
    not first time port bringup is 0
    Port WWN is 20:00:00:0d:ec:e8:2c:7f
    current state [PI_FSM_ST_TXPORT_INIT_TRUNKING_ENABLED]
    port_init_eval_flag(0x00000401), cfg wait for none
        FC_PORT_INIT_DATA_VALID (0)
        FC_PORT_INIT_ADMIN_ST_DOWN_TO_UP (10)
        FC_PORT_INIT_PHY_PORT_UP (49)
    Mts node id 0x0
    Lock Info: resource [vfc1]
      type[0] p_gwrap[(nil)]
          FREE @ 259535 usecs after Mon Dec 20 19:59:31 2010
      type[1] p_gwrap[(nil)]
          FREE @ 260559 usecs after Mon Dec 20 19:59:31 2010
      type[2] p_gwrap[(nil)]
          FREE @ 266012 usecs after Mon Dec 20 19:59:31 2010
    0x10000001e000000
    eport_init_flag(0x00000000), elp_chk_flag(0x00000000)
    elp_rcvd_fc2_handle(0x00000000), elp_sent_fc2_handle(0x00000000)
    esc_chk_flag(0x00000000), esc_fc2_handle(0x00000000)
    elp_flags(0x0000), classes_supported(F), tx bb_credit(0)
    Peer ELP Revision: 0
    Timer active for PI_FSM_EV_TE_2_E_TIMER_EXPIRED
    cnt_link_failure(0), cnt_link_success(0), cnt_port_up(0)
    cnt_cfg_wait_timeout(2), cnt_port_cfg_failure(2), cnt_init_retry(0)
    nos link failures (0), debounce window (300 ms), elp wait tout (750 ms)
    link fail reason (0x0)    num_elps_before_up (0)
    internal_reinit_counter (0) external_reinit_counter (0)
Trunk Info -
    trunk vsans (allowed active) (1)
    trunk vsans (operational allowed) (1)
    trunk vsans (up) ()
    trunk vsans (isolated) ()
TE port per vsan information
vfc1, Vsan 1 - state(down), state reason(waiting for flogi), fcid(0x000000)
    port init flag(0x0),
    Lock Info: resource [vfc1, vsan 1]
      type[0] p_gwrap[(nil)]
          FREE @ 270103 usecs after Mon Dec 20 19:59:31 2010
      type[1] p_gwrap[(nil)]
          FREE @ 270104 usecs after Mon Dec 20 19:59:31 2010
      type[2] p_gwrap[(nil)]
          FREE @ 270105 usecs after Mon Dec 20 19:59:31 2010
    0x40000011e000000
current state [TE_FSM_ST_WAIT_FOR_FLOGI]
    RNID info not found.
    first time elp: 1
    Peer ELP Revision: 0
Pacer Info -
    Pacer state: released credits due to timer expiry
PQP: not in progress
My configuration
vlan 701
fcoe vsan 1
name FCoE-Vsan1
interface vfc1
bind interface Ethernet1/9
switchport description Conexion FC con UCS1
no shutdown
interface Ethernet1/9
description Conexion FCoE con UCS1
switchport mode trunk
spanning-tree port type edge trunk
I need configure anything in UCS?.
Regards.

Under your ethernet 1/9 try adding:
switchport trunk allowed vlan 1, 701
Assuming vlan 1 as your native default vlan and 701 is FCoE vlan, this should bring up vlan 701 to your CNA.

Vlans on FCoE uplinks in UCS

Similar Messages

Maybe you are looking for