FCoE VFC VSAN stuck at waiting for flogi / initializing – %PORT-5-IF_TRUNK_DOWN: %$VSAN 102%$ Interface vfc102, vsan 102 is down (waiting for flogi)

The most common issue that I see when trying to register vsan to flogi is the issue with association under vsan database. Its very easy to miss the extra step compared to classical ethernet when assigning vsan to the interface.

N5K10(config-if)# 2003 Aug 5 10:53:59 N5K10 %PORT-5-IF_TRUNK_DOWN: %$VSAN 200%$ Interface vfc102, vsan 200 is down (waiting for flogi)
2003 Aug 5 10:53:59 N5K10 %PORT-5-IF_TRUNK_DOWN: %$VSAN 102%$ Interface vfc102, vsan 102 is down (waiting for flogi)

So we have our interface which allows appropriate vsan on that interface but flogi database still not showing registration i.e. for vsan 102:

N5K10(config-if)# sh run int vfc102

!Command: show running-config interface vfc102
!Time: Tue Aug 5 10:56:54 2003

version 7.3(2)N1(1)

interface vfc102
bind interface Ethernet102/1/1
switchport trunk allowed vsan 102
no shutdown

N5K10(config-if)# sh flogi database
——————————————————————————–
INTERFACE VSAN FCID PORT NAME NODE NAME
——————————————————————————–
fc1/48 1 0x080000 21:01:00:1b:32:24:5e:dc 20:01:00:1b:32:24:5e:dc
San-po200 200 0x570040 24:c8:54:7f:ee:c5:6a:80 20:c8:54:7f:ee:c5:6a:81
San-po200 200 0x570042 20:00:00:25:b5:1b:44:09 20:00:00:25:b5:1a:44:09

What makes it harder is that with vfc the flogi registration won’t show unless its properly configured. That’s the difference between classical fiber channel which still going to register but will be assigned to the default vsan like i.e: fc1/48 on vsan 1.¬†

If you are only running FCoE, flogi database will be empty and no correlation can be made.

Check the followings to make sure you have all the settings:

  • vlan to fcoe mapping
  • vfc interface configuration
  • vsan database
  • vsan membership

N5K10(config-if)# sh run | section vlan
feature interface-vlan
vlan 1, 10, 20
vlan 102
fcoe vsan 102

N5K10(config-if)# sh run int vfc102

interface vfc102
bind interface Ethernet102/1/1
switchport trunk allowed vsan 102
no shutdown

N5K10(config-if)# sh run | sec “vsan database”
vsan database
vsan 102
vsan 200
vsan database
vsan 200 interface san-port-channel 200

N5K10(config-if)# sh vsan membership
vsan 1 interfaces:
fc1/44 fc1/45 fc1/48 vfc102

vsan 102 interfaces:

vsan 200 interfaces:
fc1/46 fc1/47 san-port-channel 200

vsan 4079(evfp_isolated_vsan) interfaces:

As you can see from above output my vsan database is missing proper vsan to interface mapping to vfc102 which can be confirmed under vsan membership. My vfc101 belongs to incorrect vsan.

To simply fix that assign the proper vsan number to the vfc interface:

N5K10(config-if)# vsan database
N5K10(config-vsan-db)# vsan 102 interface vfc102
N5K10(config-vsan-db)# 2003 Aug 5 11:24:51 N5K10 %PORT-5-IF_TRUNK_DOWN: %$VSAN 102%$ Interface vfc102, vsan 102 is down (waiting for flogi)
2003 Aug 5 11:24:52 N5K10 %PORT-5-IF_TRUNK_DOWN: %$VSAN 102%$ Interface vfc102, vsan 102 is down (Initializing)
2003 Aug 5 11:24:52 N5K10 %PORT-5-IF_TRUNK_UP: %$VSAN 102%$ Interface vfc102, vsan 102 is up

N5K10(config-vsan-db)# sh flogi database
——————————————————————————–
INTERFACE VSAN FCID PORT NAME NODE NAME
——————————————————————————–
fc1/48 1 0x080000 21:01:00:1b:32:24:5e:dc 20:01:00:1b:32:24:5e:dc
San-po200 200 0x570040 24:c8:54:7f:ee:c5:6a:80 20:c8:54:7f:ee:c5:6a:81
San-po200 200 0x570042 20:00:00:25:b5:1b:44:09 20:00:00:25:b5:1a:44:09
vfc102 102 0x340000 20:bb:00:25:b5:c2:00:30 10:00:00:00:c8:aa:00:03

Total number of flogi = 4.

Additionally, if everything checks out on the switch and you are still getting “waiting for flogi” and vfc is stuck at initializing double check the other end (i.e. UCS) vHBA’s. It could be that their end is tagging incorrect VSAN. In the example my vfc200 is expecting vsan 200 as this is the only vsan allowed on the trunk where look what its showing on the vHBA fc0 (fig. 1)

N5K10(config-if)# sh run int vfc200

bind interface Ethernet102/1/1
switchport trunk allowed vsan 200
no shutdown

ucs-c-vhba-interface
Fig. 1 – vHBA Properties showing VSAN tag of 101 instead of 200 which is configured on vfc interface. Similar concept to trunking between switches – needs to match on both ends!

 

Thanks,
Bart

 

Tags:, , , ,
One Comment

Add a Comment

Your email address will not be published. Required fields are marked *