hi,We have a StorageWorks SAN Switch 2 / 16V that was currently working fine on a SAN. We needed to reuse it, in other site, so we restarted the switch to factory with the following commands:
switchdisablecfgdisable (hit "and" at prompt)cfgclear (hit "and" at prompt)cfgSave (hit "and" at prompt)configdefaultswitchenablereboot
once the switch restarts, it doesn´t allow us to enable the ports and the command switchShow shows the following:
Port Media Speed State
0 id 2G No_Light Disabled
1 id 2G No_Light Disabled
2 -- 2G Port_Flt Disabled
3 id 2G No_Light Disabled
4 id 2G No_Light Disabled
5 id 2G No_Light Disabled
6 id 2G No_Light Disabled
7 id 2G No_Light Disabled
8 id 2G No_Light Disabled
9 id 2G No_Light Disabled
10 id 2G No_Light Disabled
11 id 2G No_Light Disabled
12 id 2G No_Light Disabled
13 id 2G No_Light Disabled
14 id 2G No_Light Disabled
15 id 2G No_Light Disabled
when we try to issue the command portenable on a port, it shows:
portEnable failed check if switch is disabled or slot is off
Also, the sfpshow command does not display information about any of the sfp and lights in the ports are one in green (not blinking) and the other in orange blinking.
The switch has a licence and it is correct.
san_hornos:admin> licenseshowxxxxxxxxxxxxxxxxxxx: Web license Zoning license 2 Domain Fabric licensesan_hornos:admin>
I am enable to connect to the switch through telnet and serial, and with admin and root accounts.
Any idea about how to fix it?
Hi alexey and thanks for the reply.
The switch has the following Firmware version:
san_hornos:admin> firmwareshowPrimary partition: v4.2.0bSecondary Partition: v4.2.0bsan_hornos:admin>
and yes, i try to issue the commands switchdisable and switchenable, also reboot the switch several times, issue the command portcfgpersistentenable but none of it really works.
thanks for any idea.
can you post the output of errdump?
Hi Felipon, here you go.
Error 13--------0x264 (fabos): Dec 11 12:07:06Switch: 0, Info FABRIC-DOMAIN_INFO, 4, Domain 1
Error 12--------0x264 (fabos): Dec 11 12:07:06Switch: 0, Info FABRIC-SWITCH_ROLE, 4, Principal switch
Error 11--------0x24e (fabos): Dec 11 12 0x264 (fabos): Switch: 0, Info :06:56Switch:FABRIC-DOMAIN_INFO, 4, 0, Error EM-SWIDomain 1TCH_FAULTY, 2, Switch set to faulty, rc=0x30000
Error 10--------0x24e (fabos): Dec 11 12:06:56Switch: 0, Error EM-SWITCH_FAULTY, 2, Switch set to faulty, rc=0x30000
Error 09--------0x3c5 (fabos): Dec 11 12:05:55Switch: 0, Critical DIAG-INIT, 1, txdpath:ExtLB, pass 1,Pt0/2(2) Ch0/2 2Gbps Failed to go active after initialization,Err# 139023A 0002
Error 08--------0x24f (fabos): Dec 11 12:04:26Switch: 0, Info HAM-REBOOT_REASON, 4, Switch reboot, reason: Unknown
Error 07--------0x265 (fabos): Dec 11 12:04:23 (2)Switch: 0, Info ZONE-DB_RESTORE_TIME, 4, Zone-DB size (8) bytes. Wallclock Restore time (3) milli-sec [normal].
Error 06--------0x24e (fabos): Dec 09 11:43:23Switch: 0, Error EM-SWITCH_FAULTY, 2, Switch set to faulty, rc=0x30000
Error 05--------0x24e (fabos): Dec 09 11:43:23Switch: 0, Error EM-SWITCH_FAULTY, 2, Switch set to faulty, rc=0x30000
Error 04--------0x3bf (fabos): Dec 09 11:42:22Switch: 0, Critical DIAG-INIT, 1, txdpath:ExtLB, pass 1,Pt0/2(2) Ch0/2 2Gbps Failed to go active after initialization,Err# 139023A 0002
Error 03--------0x24e (fabos): Dec 09 11:40:54Switch: 0, Error EM-FRU_FAULTY, 2, Power supply 1 set to faulty, rc=0x2000e
Error 02--------0x24f (fabos): Dec 09 11:40:53Switch: 0, Info HAM-REBOOT_REASON, 4, Switch reboot, reason: Unknown
Error 01--------0x2ffe (fabos): Dec 05 17:20:03Switch: 0, Info ERRLOG-NV_LOG_CLRD, 4, Persistent error log cleared
really, don't sond good with this Switch, and is not a discussion if this is a "museum rarity" or is not.
please try follow:
from command line, execute the command "savecore -l" Note ( caracter l = L )
if any dump file is available, please remove with the operand -R
Additional, a BUG was present in old FOS 4.x Release, this bug full the compact Flash.
here is a command syntax available which I at the moment don't remeber, but you must access with "root" credential.
I'll try to find this and coming back.
let me know what happened.
I found more....
FOS 4..2.0b have a BUG which was closed in FOS 4.4.0b
this BUG caused exactely the problem you get out after power down or reboot.
is also most probable that the switch is not defective, and you need you to Upgrade the FOS.
This FOS release is not longer for Download available, ( BTW: WARNING! don't use or Upgrade to FOS 4.4.0 or FOS 4.4.0a ) in such case you made the switch corrupt.
I've the release in my Lab, but unfortunately at the moment I don't have access to.
Thanks for the reply Antonio, the switch come to life again like a walking dead after i issue the command diagDisablePost
But whenever you can send me the FOS Upgrade, it will be aprecciated, and i will apply the update.
fine that work :-)
I'm at the moment out of Country, whe I have acces to the FOS Package coming back.
In the meantime try with google for the FOS package, I would suggest to upgrade first to 4.4.0b and the to 5.0.x ->5.1 ->5.2.x
The Switch is Supported until FOS 5.3.2c
Thanks for the advice, i´m almost new in SAN stuff and didn´t realize about having the diag post disable.
At the moment there is no a SFP module on port #2, but it was, and i try booting the switch with and without the SFP, same results
And I am not offended about museum rarity in any way, just grateful.
And if you think it´s a museum rarity, i better don´t tell the whole history, this museum rarity is to replace a old old old HP 8 ports SAN HUB i think, it can´t be called switch.
so did i get you right - WITH SFP #2 it was also showing "Port_Flt"? or maybe something else, but clearly different from all other ports?omg!!! are you talking about A3724A???http://www.zdtronic.com/images/A3724A.JPG... i used to work with them before 2000 ... firmware upgrade took around 10-12 hrs via rs-232 using xmodem!!! and i had four of them to upgrade!!!
Yes, the port #2 was in Port_Flt when the SFP was in the switch
And yes, you´re right, some dude thought that putting a A3724A was a great idea, and now we have to deal with it. It has no management, no zonning, no nothing!!
So if you look that way, the old fashioned Brocade 16 Ports is like a Ferrari :smileyvery-happy:
Thanks guys for the answers
I issued the command diagDisablePost, then boot the switch and it come to life again, all ports enabled and system warning go off.
I am agreed with you guys, it´s just a museum rarity, but it is what we have for now and if i think it better, i´m going to cry :smileysad:
Thanks for the help Alexey.
san_hornos:admin> switchshowswitchName: san_hornosswitchType: 26.2switchState: OnlineswitchMode: NativeswitchRole: PrincipalswitchDomain: 1switchId: fffc01switchWwn: 10:00:00:05:1e:34:3e:31zoning: OFFswitchBeacon: OFF
Port Media Speed State=========================0 id N2 No_Light1 id N2 No_Light2 -- N2 No_Module3 id N2 No_Light4 id N2 No_Light5 id N2 No_Light6 id N2 No_Light7 id N2 No_Light8 id N2 No_Light9 id N2 No_Light10 id N2 No_Light11 id N2 No_Light12 id N2 No_Light13 id N2 No_Light14 id N2 No_Light15 id N2 No_Lightsan_hornos:admin>
follow this URL
at the page end there are TWO FOS package, 4.4.0c and 4.4.1a
here is another package, 5.0.2 but show to me ( from a small MB Size ) this is a special package for Blade Switch, you should not use this 5 Upgrade
I have just finished installing the FOS updates to the switch, first 4.4.0c and them 4.4.1a, but still, when i issue the command diagEnablePost the switch goes to faulty and all the ports to Disable.
So i think the switch has, and always had a hardware problem, but previous administrators didn´t care about it, so i´ll try to find other FOS updates and try, but if it didn´t work, it´s the only switch we have, so it will have a nice diagDisablePost on it.
Thanks for the help!