Fibre Channel (SAN)

Reply
N/A
Posts: 1
Registered: ‎12-22-2011

Brocade 425 and remote node_name 0xffffffffffffffff

We are working on a proof of concept SAN here and keep running into this issue on our initiators with Brocade 425 Fibre adapters and the 2.3.0.5 driver.  Our setup has 2 target hosts with 2 dual port fibre cards in them.  Each has two ports plugged into two silkworm 5000 switches.  The initiator has one port each in the two switches meaning that each lun exported will be seen on 4 paths:

    disk    foo 1-0_h283_b1       300  /dev/sdh

    disk    foo 1-0_h283_b1       300  /dev/sdl

    disk    foo 1-0_h283_b1       300  /dev/sdp
    disk    foo 1-0_h283_b1       300  /dev/sdt

    disk    foo 1-1_h283_b1       300  /dev/sdaf
    disk    foo 1-1_h283_b1       300  /dev/sdan
    disk    foo 1-1_h283_b1       300  /dev/sdab
    disk    foo 1-1_h283_b1       300  /dev/sdaj

Periodically we encounter a scenario where the luns from one of the target hosts is no longer visible through one of the switches:

    disk    foo 1-0_h283_b1       300  /dev/sdh
    disk    foo 1-0_h283_b1       300  /dev/sdl

    disk    foo 1-0_h283_b1       300  /dev/sdp
    disk    foo 1-0_h283_b1       300  /dev/sdt

    disk    foo 1-1_h283_b1       300  /dev/sdaf
    disk    foo 1-1_h283_b1       300  /dev/sdan

Since we can still access one of the target hosts through the chain we can't really pinpoint the problem to any one link in that chain.  Whenever we have this failure we see the following in the sysfs for the remote port corresponding to the "invisible" target:

# cat /sys/class/fc_host/host2/device/rport-2:0-2/fc_remote_ports:rport-2:0-2/port_name

0x21000024ff25a1ca   <---- correct

# cat /sys/class/fc_host/host2/device/rport-2:0-2/fc_remote_ports:rport-2:0-2/node_name

0xffffffffffffffff  <--- obviously incorrect

The only solution that we've come up with so far is to reboot the initiator and then everything comes up correctly for a time.  Everything else that we've tried (rescan-scsi-bus.sh -i -r, issuing lip, disabling and re-enabling ports on the switch, replacing fibre cable, unplugging and replugging SFP on the adapter, disabling and representing the lun on the target) doesn't help.  Obviously having to reboot hosts periodically to keep redundancy through the switch is a deal breaker here.  Is there anything else that we can do to cause the brocade adapter to "reinitialize" this port and rediscover what is out there?

Contributor
Posts: 36
Registered: ‎11-06-2008

Re: Brocade 425 and remote node_name 0xffffffffffffffff

What FOS code version on the Brocade 5000 switch? I would recommend updating to latest available FOS code. Also, there’s a v3.0.3.0 drivers for the Brocade BR-425 available to download today. If the issue still occurs, please collect the adapter’s supportsave log file and open a support request (SR#) with the vendor that you purchased the Brocade adapter via Brocade support. (US and Canada Toll-Free: 800-752-8061 International Numbers — view details. For areas unable to access 800 numbers: 408-333-6061 E-mail: support@brocade.com)

Here’s the link for drivers download:

http://www.brocade.com/services-support/drivers-downloads/adapters/index.page

Join the Community

Get quick and easy access to valuable resource designed to help you manage your Brocade Network.