James; I'm aware of the

Mohammad Mahdi Salim · ‎06-22-2015

I'm building a brand new UCS system which is running 2.2(3g). The plan is to use FCoE uplinks and it's going to be in a multi-hop FCoE configuration.

To my surprise , there is no place to assign the FCoE port channel to a specific vSan , instead I do have a new option for LACP policy.

we do have the option in older firmware but for some reason it either does not exist or I cannot find it.

FC works fine and after creating an FC Port-Channel I can assign the vsan with no issues.

-------------------------------------------------------------------------------
Interface Vsan Admin Admin Status Bind Oper Oper
Mode Trunk Info Mode Speed
Mode (Gbps)
-------------------------------------------------------------------------------
vfc915 1 NP on trunking port-channel141 TNP auto

vsan 1 interfaces:
vfc915

vsan 3042 interfaces:

vsan 4079(evfp_isolated_vsan) interfaces:

vsan 4094(isolated_vsan) interfaces:

Any thoughts ?

Jing Ren · ‎06-23-2015

Hi Mohammad,

I guess probably you mis-understood port-channel and san-port-channel from your config. Your output seemed to be a proper bind of your vfc915 to an etherchannel 141. You should either assign a vsan or trunk vsans to your vfc interfaces.

This link might explains steps in detail:

http://www.cisco.com/c/en/us/support/docs/switches/nexus-5000-series-switches/116248-configure-fcoe-00.html

HTH,

James

Mohammad Mahdi Salim · ‎06-23-2015

James;

I'm aware of the adapter level vsan assignment for the vhbas, this is about vsan assignment on the FCoE uplink ports.

Attached, is the screenshot from my other UCS running an older code.

isaac anish · ‎06-24-2015

Hi,

Did you tried from cli mode....?

Mohammad Mahdi Salim · ‎06-25-2015

You cannot configure NXOS from CLI on UCS

Mohammad Mahdi Salim · ‎06-23-2015

James;

Even in the document which you sent me you can clearly see in step 8 that we can select the vsan and assign in to the FCoE port channel uplinks.

For some reason which is unknown to me , we do not have this option in 2.2(3g)

Regards

Jing Ren · ‎06-25-2015

Hi Mohammad,

The VSAN dropdown list page is using the same gui page as FC port-channel, that's why you see a VSAN in both locations. In FCoE Po the vsan actually refers to the fcoe vlan mapped to vsan.

If you want to limit vsans trunked in the uplinks, right click Fabric A/B, and disable FC uplink trunking.

Please note by default vsan 1 is trunked, you can't disable that.

J

Mohammad Mahdi Salim · ‎06-25-2015

Hi James;

FC Uplink Trunking is disabled by default. Enabling or disabling that does NOT make any difference on FCoE uplink ports.

As you can see here I do have 2 port-channels connected to 2 different fabrics and UCS created vfc 734 and 740.

I want admin allowed vsans to be 3042 for vfc 734 and 40 for vfc 740.

vfc734 is trunking (Not all VSANs UP on the trunk)
Bound interface is port-channel141
Hardware is Ethernet
Port WWN is 22:dd:00:2a:6a:43:d9:3f
Admin port mode is NP, trunk mode is on
snmp link state traps are enabled
Port mode is TNP
Port vsan is 1
Trunk vsans (admin allowed and active) (1,40,3042)
Trunk vsans (up) (3042)
Trunk vsans (isolated) ()
Trunk vsans (initializing) (1,40)
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
9 frames input, 1056 bytes
0 discards, 0 errors
300 frames output, 42692 bytes
0 discards, 0 errors
last clearing of "show interface" counters never
Interface last changed at Tue Jun 23 14:00:17 2015

vfc740 is trunking (Not all VSANs UP on the trunk)
Bound interface is port-channel139
Hardware is Ethernet
Port WWN is 22:e3:00:2a:6a:43:d9:3f
Admin port mode is NP, trunk mode is on
snmp link state traps are enabled
Port mode is TNP
Port vsan is 1
Trunk vsans (admin allowed and active) (1,40,3042)
Trunk vsans (up) (40)
Trunk vsans (isolated) ()
Trunk vsans (initializing) (1,3042)
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
24 frames input, 3948 bytes
0 discards, 0 errors
20 frames output, 2576 bytes
0 discards, 0 errors
last clearing of "show interface" counters never
Interface last changed at Thu Jun 25 14:11:18 2015

so right now , I'm just doing this by limiting the allowed vsan list on my NEXUS and MDS switches. But I believe it makes sense to have the ability to change the admin allowed vsans on UCS too.

.

clayguthery · ‎06-23-2015

I just started a new deployment on 2.2(5a) and ran into this exact same question! Still hunting..

Mohammad Mahdi Salim · ‎06-24-2015

This is a bit frustrating and confusing.

I'm looking at my old UCS's show vfc command and I can see both vsan1 and vsan3375

vfc876 is trunking (Not all VSANs UP on the trunk)
Bound interface is port-channel107
Hardware is Virtual Fibre Channel
Port WWN is 23:6b:00:2a:xx:xx:xx:xx
Admin port mode is NP, trunk mode is on
snmp link state traps are enabled
Port mode is TNP
Port vsan is 3375
Trunk vsans (admin allowed and active) (1,3375)
Trunk vsans (up) (3375)
Trunk vsans (isolated) ()
Trunk vsans (initializing) (1)

Same situation on the new one with the new firmware :

vfc733 is trunking (Not all VSANs UP on the trunk)
Bound interface is port-channel141
Hardware is Ethernet
Port WWN is 22:dc:00:2a:xx:xx:xx:xx
Admin port mode is NP, trunk mode is on
snmp link state traps are enabled
Port mode is TNP
Port vsan is 1
Trunk vsans (admin allowed and active) (1,20,3022)
Trunk vsans (up) (3022)
Trunk vsans (isolated) ()
Trunk vsans (initializing) (1,20)

I just don't like seeing the other vsans remain in initializing mode for ever.

Limiting the allowed vsans on nexus VFC or FC ports is really easy and can be done by adding switchport trunk allowed vsan xyz , but not sure how to do it on UCS. it seems to me that although we have the configuration option in the old firmware , but it still suffers from the same issue.

Can someone let us know how to limit the allowed vsans on FCoE ports on UCS ????

Mohammad Mahdi Salim · ‎06-26-2015

Clay;

Did you find anything about this issue ? I've built the service profiles and it shows that the HBA is member of vsan 1 which I do not have presented to UCS from my nexus . As the result the server won't boot.

This is frustrating

Mohammad Mahdi Salim · ‎06-26-2015

Clay;

I opened a case with Cisco today and had a Webex session with them. It was a surprise to Cisco as well that this feature was not there any more.

We are just trying to do a normal vlan pruning on the FCoE vlans. this can be easily done for Ethernet traffic under the LAN tab for DJL2 but the functionality in no longer there for FCoE.

Cisco Engineer told me that he has to go back to the developers to see why this feature was removed and request for enhancement.

Let me know about your findings.

clayguthery · ‎06-26-2015

We have been fighting others issues and haven't come back to this one as it's not really a deal breaker for our configuration. Please let me know if they come back with any further information, thanks!

Pom Ham · ‎10-14-2019

Hi,

After 2.2 code, they have removed the vsan drop down menu in UCSM. As long as the port-channel is created, it will have the vsan assigned to the fcoe uplinks. You can verify by running the show command in nxos.

In the example below, we can verify the vlan 111 associated to the vsan 111 under the allowed vlans.

nterface Ethernet1/9

description C: FcoeUplink

pinning border

switchport mode trunk

switchport trunk allowed vlan 111,300,400,501,510,1010,4048

udld disable

channel-group 111 mode active

no shutdown

#show running-config port-channel 111

there is no place to bind vSan to FCoE Port-Channels