Waiting for flogi

[jfcai2004]

I have one C220 connects to Nexus 5548UP via FCoE, but the vfc is in trunking, and the vsan is waiting for flogi.

Below is the conf,

vlan 1000

  fcoe vsan 1000

vsan database

  vsan 1000

interface vfc1

  bind interface Ethernet1/1

  switchport trunk allowed vsan 1000

  no shutdown

vsan database

  vsan 1000 interface vfc1

interface Ethernet1/1

  switchport mode trunk

  switchport trunk allowed vlan 1,1000

  spanning-tree port type edge trunk

N5548# show int vfc 1 trunk vsan

vfc1 is trunking

    Vsan 1000 is down (waiting for flogi)

Any reason?

Thanks,

Jeff

[Marcel Zehnder]

Hi Jeff

Looks to me like an issue on the C220 - Could you please post some screenshots from the interface/vHBA-Config on your C220?

Regards

Marcel

[jfcai2004]

Thanks, Marcel.

ucs-c220-m3 /chassis/adapter/host-fc-if # show detail

Name fc0:

    World Wide Node Name: 10:00:54:78:1A:87:35:2C

    World Wide Port Name: 20:00:54:78:1A:87:35:2C

    FC SAN Boot: disabled

    Persistent LUN Binding: disabled

    Uplink Port: 0

    MAC Address: 54:78:1A:87:35:2C

    CoS: 3

    VLAN: 1000

    Rate Limiting: OFF

    PCIe Device Order: ANY

    EDTOV: 2000

    RATOV: 10000

    Maximum Data Field Size: 2112

    Channel Number: N/A

    Port Profile: N/A

Is this enough?

[Marcel Zehnder]

Okay, looks good - I know about an similar issue if you don't configure the FCoE-awere QoS policy-maps on your N5k.

What is the output if you do a  "sh run ipqos all" on your N5K?

[jfcai2004]

# sh run ipqos all

!Command: show running-config ipqos all

!Time: Wed Mar 13 16:05:36 2013

version 5.1(3)N2(1c)

class-map type qos class-fcoe

class-map type qos match-any class-default

class-map type qos match-any class-all-flood

class-map type qos match-any class-ip-multicast

class-map type queuing class-fcoe

  match qos-group 1

class-map type queuing class-default

  match qos-group 0

class-map type queuing class-all-flood

  match qos-group 2

class-map type queuing class-ip-multicast

  match qos-group 2

policy-map type qos default-in-policy

  class class-default

policy-map type qos fcoe-default-in-policy

  class class-fcoe

    set qos-group 1

  class class-default

policy-map type queuing default-in-policy

  class type queuing class-default

    bandwidth percent 100

policy-map type queuing default-out-policy

  class type queuing class-default

    bandwidth percent 100

policy-map type queuing fcoe-default-in-policy

  class type queuing class-fcoe

    bandwidth percent 50

  class type queuing class-default

    bandwidth percent 50

policy-map type queuing fcoe-default-out-policy

  class type queuing class-fcoe

    bandwidth percent 50

  class type queuing class-default

    bandwidth percent 50

class-map type network-qos class-fcoe

  match qos-group 1

class-map type network-qos class-default

  match qos-group 0

class-map type network-qos class-all-flood

  match qos-group 2

class-map type network-qos class-ip-multicast

  match qos-group 2

policy-map type network-qos default-nq-policy

  class type network-qos class-default

    multicast-optimize

policy-map type network-qos fcoe-default-nq-policy

  class type network-qos class-fcoe

    pause no-drop

    mtu 2158

  class type network-qos class-default

    multicast-optimize

system qos

  service-policy type qos input fcoe-default-in-policy

  service-policy type queuing input fcoe-default-in-policy

  service-policy type queuing output fcoe-default-out-policy

  service-policy type network-qos fcoe-default-nq-policy

  fex queue-limit

interface Ethernet1/1

  priority-flow-control mode auto

interface Ethernet1/2

  priority-flow-control mode auto

interface Ethernet1/3

  priority-flow-control mode auto

interface Ethernet1/4

  priority-flow-control mode auto

interface Ethernet1/5

  priority-flow-control mode auto

interface Ethernet1/6

  priority-flow-control mode auto

interface Ethernet1/7

  priority-flow-control mode auto

interface Ethernet1/8

  priority-flow-control mode auto

interface Ethernet1/9

  priority-flow-control mode auto

interface Ethernet1/10

  priority-flow-control mode auto

interface Ethernet1/11

  priority-flow-control mode auto

interface Ethernet1/12

  priority-flow-control mode auto

interface Ethernet1/13

  priority-flow-control mode auto

interface Ethernet1/14

  priority-flow-control mode auto

interface Ethernet1/15

  priority-flow-control mode auto

interface Ethernet1/16

  priority-flow-control mode auto

interface Ethernet1/17

  priority-flow-control mode auto

interface Ethernet1/18

  priority-flow-control mode auto

interface Ethernet1/19

  priority-flow-control mode auto

interface Ethernet1/20

  priority-flow-control mode auto

interface Ethernet1/21

  priority-flow-control mode auto

interface Ethernet1/22

  priority-flow-control mode auto

interface Ethernet1/23

  priority-flow-control mode auto

interface Ethernet1/24

  priority-flow-control mode auto

[Marcel Zehnder]

Looks good as well...I'm out of ideas - sorry.

One last shot:

Try:

int vfc1

shut

switchport mode f

no shut

Regards

[jfcai2004]

BTW, can I connect C220 direct to 5548?

[jfcai2004]

same.

show int vfc 1

vfc1 is trunking

    Bound interface is Ethernet1/1

    Hardware is Ethernet

    Port WWN is 20:00:00:2a:6a:0a:66:ff

    Admin port mode is F, trunk mode is on

    snmp link state traps are enabled

    Port mode is TF

    Port vsan is 1000

    Trunk vsans (admin allowed and active) (1000)

    Trunk vsans (up)                       ()

    Trunk vsans (isolated)                 ()

    Trunk vsans (initializing)             (1000)

[jfcai2004]

we do not install OS yet, and want to use SAN boot.

[upule]

If you have local HDD, just give a try with installing a simple o/s lke ESXi & then check flogi.

This eliminates lots of unnecessary troubleshooting & narrow down the issue whether it is SAN boot issue or HBA issue.

We have done SAN boot with UCS blades with boot policy set to SAN specifying the pwwn of the storage port & respective LUN ID as target.

[CiscoDebug]

Hello Jeff,

I had the same problem with the same configuration as yours.

First of all we ugraded the version of our Nexus from 5.1(3) to 5.2(1) N1 (3)

The problem is that the CIMC didn't sync the BIOS with the boot from SAN flag.

I just reboot the server with the kvm chose F2 to enter the bios settings then F9 to reset the default parameters and reboot...

And that doesn't reset the BIOS, that update it ! The server boot from SAN and i could install VMware on the lun.

[jfcai2004]

Hello Herve,

We found the RAID controller is failed. When we pressed  F2 or F6, it just displayed Entering setup or Entering boot menu...,  until we removed RAID controller.

Then we update the firmwares on C220, we can configure LUN and we can install the ESXi on the LUN.

But when reboot, we could not find the LUN for boot in the boot menu. Any suggestion?

Thanks,

Jeff

[Michael Dougherty]

Hello

You should verify that the HBA has initialized. I have experienced this similar issue with Qlogic cards, basically right out of the box you have to enter into the card during boot and actually turn on FCoE. The Qlogic gives the ability to connect and test the SAN connection over FC in its BIOS. Please note that sometimes a cold reboot of the server is needed before flogi appears. You can issue the sho int vfc , also show flogi data. You will hopefully see the cards PWWN and the vfc interface number.

This is based on my experience with dell and hp using Qlogic CNAs.

Sent from Cisco Technical Support iPad App

[jfcai2004]

We find the issue is the battery of the RAID controller.

Sometime we will get following messages on screen:

USB cache device is not responding.

From the link

http://www.cisco.com/en/US/docs/unified_computing/ucs/release/notes/OL-28995-01.html

We find following solution:

Workaround  

Power  down the system for 2 minutes to attempt recovery and avoid cache data  loss, and then power-on. If it fails, replace SuperCap with newer Rev-K  SuperCap (49571-03). (CSCud38069)

After replace the SuperCap, the issue solved. Now we can use the SAN boot.

Really bad experience.