Fibre Channel (SAN)

Reply
Occasional Contributor
Posts: 6
Registered: ‎01-21-2005

When blades in IBM bladeserver with built in Brocade switches are rebooted they do not re-acquire RAID LUN's.

I had to re-boot a blade in an IBM Blade Center. the bladecenter allows access to the SAN through built in Brocade switches. When the blade came up it didn't see the SAN. I talked to some other System Admins here and they said that that type of thing had happened before and usually it could be remedied by moving the blade to another slot and booting it there. It could then be moved back to its original slot and should reboot normally. I was however not even that lucky.

In desperation I re-booted the Brocade. That caused me to loose all the devices on all the blades because the switch came up with all ports persistently disabled. I was able to figure out how to enable the ports but then had to re-boot all the blades to get them to re-acquire their devices. I might have been able to hot add but I didn't try.

So my two problems are; 1)Why do the blades loose connection to the RAID units in the firstplace when they are rebooted. This appearantly has happened several times during power outages etc. and I didn't know about it. 2)How to have the Built in Brocade switches re-boot without the ports becoming persistently disabled. There is no zoning configuration in this switch, poor practice, I know. Would that help?

External Moderator
Posts: 4,907
Registered: ‎02-23-2004

Re: When blades in IBM bladeserver with built in Brocade switches are rebooted they do not re-acquire RAID LUN's.

This is not normal behavior, and a reboot don't cause that all port will set to Persistent Disable something else is not ok here and cause this malfunction.

I assume any Firmware Bios Problem beetwen the Chassis and the Brocade Blade Switch FabricOS due a Incompatibility.

Which Brocade Blade switch Type / Modell is in the bladecenter ? And which FabOS release is installed ?

TechHelp24
N/A
Posts: 1
Registered: ‎01-11-2006

Re: When blades in IBM bladeserver with built in Brocade switches are rebooted they do not re-acquire RAID LUN's.

Hi, you must enable the external port via the blade management web ( remenber for all switch & save button !! ) :

san_blade.jpg

Hi Claudio.

External Moderator
Posts: 4,907
Registered: ‎02-23-2004

Re: When blades in IBM bladeserver with built in Brocade switches are rebooted they do not re-acquire RAID LUN's.

Claudiola,

--->>> That caused me to loose all the devices on all the blades because the switch came up with all ports persistently disabled.

....you must enable the external port via the blade management web

?????

TechHelp24
Occasional Contributor
Posts: 6
Registered: ‎01-21-2005

Re: When blades in IBM bladeserver with built in Brocade switches are rebooted they do not re-acquire RAID LUN's.

Thanks

I have gone into the Bladeserver Management GUI and changed from disabled to disabled and saved. I will not get to try a reboot until next week but I believe this should fix my problem.

sodapop

Frequent Contributor
Posts: 140
Registered: ‎02-27-2008

Re: When blades in IBM bladeserver with built in Brocade switches are rebooted they do not re-acquire RAID LUN's.

Hi claudiola

Techhelp is right you should not be seeing that kind of behaviour when you reboot a blade chassis switch.

What version of Fabric OS are you running on your switches ?

What is your topology that your Fabric is using ? You should be able to reboot a switch and any hosts shouldn't noticed the reboot. (Assuming multi-pathing software , dual fabrics)

Post up your topology and we'll take a look

David

Occasional Contributor
Posts: 6
Registered: ‎01-21-2005

Re: When blades in IBM bladeserver with built in Brocade switches are rebooted they do not re-acquire RAID LUN's.

What Claudiola is referring to I believe is the problem with the switch re-booting and coming up with all ports persistently disabled. I guess I should have made two seperate statements of problems because I actually have two problems. One is the one Claudiola addressed with the switch and the other is with the blades re-booting when the switch has not been re-booted. Anyway here is the output from the Topology screen, and below that a switchshow output.

View Fabric Topology from Switch brocade4Gb:
There are total of 3 domains in the fabric
Local Domain ID: 2  (Switch Name:  brocade4Gb)
Domain ID:  1  (Switch Name:  elpdb05)
Domain ID:  2  (Switch Name:  brocade4Gb)
Domain ID:  3  (Switch Name:  elpdb04)
Active Paths:
Destination Domain ID:1  (Switch Name: elpdb05)
Destination's World Wide Name: 10:00:00:05:1e:90:0e:a3
Number of Path(s) to Domain 2:  1
Metric to reach the domain: 500
Path Number 1:
Output PortInput PortsTotal BandwidthBandwidth DemandHop CountFlag
161 , 2 , 3 , 4 , 11 , 13 , 1547001D
Destination Domain ID:3  (Switch Name: elpdb04)
Destination's World Wide Name: 10:00:00:05:1e:90:1b:82
Number of Path(s) to Domain 2:  1
Metric to reach the domain: 500
Path Number 1:
Output PortInput PortsTotal BandwidthBandwidth DemandHop CountFlag
151 , 2 , 3 , 4 , 11 , 13 , 1647001D

brocade4Gb:root> switchshow
switchName:     brocade4Gb
switchType:     37.1
switchState:    Online   (Temporary)
switchMode:     Native
switchRole:     Subordinate
switchDomain:   2
switchId:       fffc02
switchWwn:      10:00:00:05:1e:05:a8:56
zoning:         OFF
switchBeacon:   OFF

Area Port Media Speed State
==============================
  0   0   --    N4   No_Module
  1   1   cu    N4   Online    F-Port  21:00:00:1b:32:04:62:a5
  2   2   cu    N4   Online    F-Port  21:00:00:1b:32:04:60:a5
  3   3   cu    N4   Online    F-Port  21:00:00:1b:32:04:a3:a5
  4   4   cu    N4   Online    F-Port  21:00:00:1b:32:04:e5:a2
  5   5   cu    AN   No_Sync  
  6   6   cu    AN   No_Sync  
  7   7   cu    AN   No_Sync  
  8   8   cu    AN   No_Sync  
  9   9   cu    AN   No_Sync  
10  10   cu    AN   No_Sync  
11  11   cu    N4   Online    F-Port  21:00:00:1b:32:04:6c:a5
12  12   cu    AN   No_Sync  
13  13   cu    N4   Online    F-Port  21:00:00:1b:32:04:86:a5
14  14   cu    AN   No_Sync  
15  15   id    N4   Online    E-Port  10:00:00:05:1e:90:1b:82 "elpdb04" (downstream)
16  16   id    N4   Online    E-Port  10:00:00:05:1e:90:0e:a3 "elpdb05" (upstream)
17  17   --    N4   No_Module
18  18   --    N4   No_Module
19  19   --    N4   No_Module

Occasional Contributor
Posts: 6
Registered: ‎01-21-2005

Re: When blades in IBM bladeserver with built in Brocade switches are rebooted they do not re-acquire RAID LUN's.

Here is the output of the switch information report.

List of Switches

Switch ID   Worldwide Name           Enet IP Addr    FC IP Addr      Name
-------------------------------------------------------------------------
  1: fffc01 10:00:00:05:1e:90:0e:a3  192.168.29.5    0.0.0.0        >"elpdb05"
  2: fffc02 10:00:00:05:1e:05:a8:56  152.61.7.10     0.0.0.0         "brocade4Gb"
  3: fffc03 10:00:00:05:1e:90:1b:82  192.168.29.4    0.0.0.0         "elpdb04"

The Fabric has 3 switches

Current Switch Information

Ethernet IP Address: 152.61.7.10
Ethernet Subnetmask: 255.255.255.0
Fibre Channel IP Address: 0.0.0.0
Fibre Channel Subnetmask: 0.0.0.0
Gateway Address: 152.61.7.254

Kernel:     2.4.19    
Fabric OS:  v5.0.5a
Made on:    Tue Jul 18 21:12:26 2006
Flash:     Sat Jul 21 10:51:34 2007
BootProm:   4.5.2

List of Inter-Switch Links

Local Domain ID: 2

Local Port     Domain     Remote Port     State
-------------------------------------------------------
    15   3        9 NB_ST_FULL
    16   1        9 NB_ST_FULL

List of Ports

switchName: brocade4Gb
switchType: 37.1
switchState: Online   (Temporary)
switchMode: Native
switchRole: Subordinate
switchDomain: 2
switchId: fffc02
switchWwn: 10:00:00:05:1e:05:a8:56
zoning:         OFF
switchBeacon: OFF

Area Port Media Speed State
==============================
  0   0   --    N4   No_Module
  1   1   cu    AN   No_Sync  
  2   2   cu    N4   Online    F-Port  21:00:00:1b:32:04:60:a5
  3   3   cu    N4   Online    F-Port  21:00:00:1b:32:04:a3:a5
  4   4   cu    N4   Online    F-Port  21:00:00:1b:32:04:e5:a2
  5   5   cu    AN   No_Sync  
  6   6   cu    AN   No_Sync  
  7   7   cu    AN   No_Sync  
  8   8   cu    AN   No_Sync  
  9   9   cu    AN   No_Sync  
10  10   cu    AN   No_Sync  
11  11   cu    N4   Online    F-Port  21:00:00:1b:32:04:6c:a5
12  12   cu    AN   No_Sync  
13  13   cu    N4   Online    F-Port  21:00:00:1b:32:04:86:a5
14  14   cu    AN   No_Sync  
15  15   id    N4   Online    E-Port  10:00:00:05:1e:90:1b:82 "elpdb04" (downstream)
16  16   id    N4   Online    E-Port  10:00:00:05:1e:90:0e:a3 "elpdb05" (upstream)
17  17   --    N4   No_Module
18  18   --    N4   No_Module
19  19   --    N4   No_Module

Name Server

{
  010000 010200 010300 010400 010701 010800 010a00 010b00
  010c00 010e00 020200 020300 020400 020b00 020d00 030000
  030200 030300 030400 030700 030800 030a00 030b00 030c00
  030e00
25 Nx_Ports in the Fabric }

{
Type Pid    COS     PortName                NodeName                 TTL(sec)
N    020200;      3;21:00:00:1b:32:04:60:a5;20:00:00:1b:32:04:60:a5; na
    FC4s: FCP
    NodeSymb: "QMI2472 FW:v4.04.09 DVR:v8.02.09.02.04.08-d"
    Fabric Port Name: 20:02:00:05:1e:05:a8:56
    Permanent Port Name: 21:00:00:1b:32:04:60:a5
N    020300;      3;21:00:00:1b:32:04:a3:a5;20:00:00:1b:32:04:a3:a5; na
    FC4s: FCP
    NodeSymb: "QMI2472 FW:v4.04.09 DVR:v8.02.09.02.04.08-d"
    Fabric Port Name: 20:03:00:05:1e:05:a8:56
    Permanent Port Name: 21:00:00:1b:32:04:a3:a5
N    020400;      3;21:00:00:1b:32:04:e5:a2;20:00:00:1b:32:04:e5:a2; na
    FC4s: FCP
    NodeSymb: "QMI2472 FW:v4.04.09 DVR:v8.02.09.02.04.08-d"
    Fabric Port Name: 20:04:00:05:1e:05:a8:56
    Permanent Port Name: 21:00:00:1b:32:04:e5:a2
N    020b00;      3;21:00:00:1b:32:04:6c:a5;20:00:00:1b:32:04:6c:a5; na
    FC4s: FCP
    NodeSymb: "QMI2472 FW:v4.04.09 DVR:v8.02.09.02.04.08-d"
    Fabric Port Name: 20:0b:00:05:1e:05:a8:56
    Permanent Port Name: 21:00:00:1b:32:04:6c:a5
N    020d00;      3;21:00:00:1b:32:04:86:a5;20:00:00:1b:32:04:86:a5; na
    FC4s: FCP
    NodeSymb: "QMI2472 FW:v4.04.09 DVR:v8.02.09.02.04.08-d"
    Fabric Port Name: 20:0d:00:05:1e:05:a8:56
    Permanent Port Name: 21:00:00:1b:32:04:86:a5
The Local Name Server has 5 entries }

Zoning Information

Defined configuration:
no configuration defined

Effective configuration:
no configuration in effect

SFP Serial ID Information

port  0: --
port  1: cu
port  2: cu
port  3: cu
port  4: cu
port  5: cu
port  6: cu
port  7: cu
port  8: cu
port  9: cu
port 10: cu
port 11: cu
port 12: cu
port 13: cu
port 14: cu
port 15: id (sw) Vendor: AVAGO            Serial No: A907324NSR      
port 16: id (sw) Vendor: AVAGO            Serial No: A907324NSV      
port 17: --
port 18: --
port 19: --

Join the Community

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