Alcatel Unleashed

All,

I have received a new Alcatel-Lucent OS6602-24. The switch is only a few days old. At boot the switch will only boot to the "Certified" directory due to an issue with one of the files in the working directory and the "Certified" Directory is empty. I have two other OS6602-24's in a STACKED configuration and they are working fine so if need be I can access those files and transfer them to this switch. Any help would be GREAT!

I have included a sample of my boot messages below as well as what files are in the "Working" directory.

Benny.. If you are seeing this I would really appreciate your help as you seem to be one of those that might be able to help.

Thanks,
Tony Santos

Boot Messages:

[Miniboot]->setNextRunningVersion 2
value = 1 = 0x1
[Miniboot]->reboot
WARNING: "sysResetHardwareFlag" flag is SET, forcing CMM board reset.
usrRoot(): COLD Boot.
Starting at 0x500000...boot from flash boot sectors...

startType=0x82 (COLD) (w/ POWER ON RESET)

The current date and time is:
Coordinated Universal Time (UTC): SAT JAN 10 20:58:43 2009
Local time: SAT JAN 10 14:58:43 2009 CST

/flash/ - disk check in progress ...
/flash/ - Volume is OK

total # of clusters: 60,404
# of free clusters: 58,060
# of bad clusters: 0
total free space: 12,338 max contiguous free space: 40,022,016 bytes
# of files: 40
# of folders: 3
total bytes in files: 12,338 # of lost chains: 0
total bytes in lost chains: 12,338Boot parameters are:

'flash(0,0)lanswitchCmm: e=192.168.1.1:ffffff00 h=192.168.10.1 g=192.168.1.254 u=lanswitchUser pw=lanswitchPassword tn=MDF-0S6602-24-01 o=lnPci cb=9600 cp=none cs=1 cw=8 cm=modemControlOff'


Adding 4793 symbols for standalone.
Spare jumper not grounded: enabling WDB

Socket failed
wdbConfig: error configuring WDB communication interface

AOS miniboot version: 5.1.5.115.R02
Attempting to load from the WORKING directory...
Loading kernel from '/flash/working/Hos.img'...
Cannot find component(alcatelNetworking_kernel.lnk) in package(/flash/working/Hos.img)!
Cannot find component(kernel.lnk) in package(/flash/working/Hos.img)!
Unable to load kernel image from file '/flash/working/Hos.img'.
Unable to boot from the WORKING software release.
Attempting to boot from the CERTIFIED software release.
Attempting to load from the CERTIFIED directory...
Loading kernel from '/flash/certified/Hos.img'...
Cannot find component(alcatelNetworking_kernel.lnk) in package(/flash/certified/Hos.img)!
Cannot find component(kernel.lnk) in package(/flash/certified/Hos.img)!
Unable to load kernel image from file '/flash/certified/Hos.img'.
Unable to boot from the CERTIFIED software release.
[Miniboot]->

Summary of Files in "Working":
[Miniboot]->ll
drw 1024 Jan 9 22:13 ./
drw 1024 Jan 10 14:58 ../
-rw 0 Jan 9 22:13 Hos.img
-rw 3541 Jan 9 22:13 Hqos.img
-rw 105613 Oct 18 2005 certs.pem
-rw 7865 Jan 9 22:05 Hrelease.img
-rw 1548 Jan 9 22:02 boot.cfg
-rw 225 Jan 9 22:00 bootrom.bin
-rw 3794 Jan 9 22:00 Hrout.img
-rw 3655 Jan 9 22:00 Hadvrout.img
-rw 5197 Jan 9 22:00 Hbase.img
-rw 3522 Jan 9 22:00 Hdiag.img
-rw 4496 Jan 9 22:13 Heni.img
-rw 4605 Jan 9 22:12 Hl2eth.img
-rw 3692 Jan 9 22:00 Hsecu.img
-rw 3764 Jan 9 22:00 Hweb.img
-rw 3622 Jan 9 22:00 Hwebadvrout.img
-rw 3616 Jan 9 22:00 Hwebl2eth.img
-rw 3562 Jan 9 22:00 Hwebqos.img
-rw 3616 Jan 9 22:00 Hwebrout.img
-rw 4154 Jan 9 22:00 Hwebsecu.img
-rw 228 Jan 9 22:00 miniboot.backup
-rw 228 Jan 9 22:00 miniboot.default
-rw 1097 Jan 9 22:00 software.lsm

59453440 bytes free
value = 0 = 0x0
[Miniboot]->

Your Hos.img is 0 byte of size. I don't believe that it was shipped like that, as every device has to go through testing before it is shipped. I could think of a hardware defect due to shipping like "not booting up at all", but a Hos.img of 0 byte size?

Get hold of the same AOS version as the one on the switch and upload the Hos.img to the working directory via zModem.

I don't have a switch next to me so I have write off my mind. (Obviously you have to be connected via console - use a terminal application which can do a zModem data transfer like SecureCRT.)

Change to the working directory from Miniboot:
Miniboot-> cd "working"

Delete the 0 byte Hos.img:
Miniboot-> xdelete "Hos.img"

Start the upload of the Hos.img (enter the command case-sensitive):
Miniboot-> sysStartZmodem

Your terminal application should offer you to select a file - select only ONE file to upload. You should select the Hos.img here.

Note:
It will be successful to load the file, but your switch won't boot - all the other image files appear to be too small in size. I don't know what you did with that switch, but it probably failed so sync in a stack?! You might have to upload all AOS image files through zModem which will be slow based on 9600 baud rate.

Hope that helps...

-benny

Benny,

As unbelievable as this may seem this is the state that we received this switch. Actually, this also had happened once before with one of the other switched we received. Sadly, because of this error there was not much I could do to make it any worse as I haven't even sync'd it with the stack yet since the switch would not boot. I know it's hard to believe but this is joe I received this switch.

Thank you for the zModem command that was actually what they had me do on the other one. I just could not remember the command. This time I have got it saved for the next time. Since I have 2 other 6602's I will FTP into them and download the known good files. Then I can connect to this one copy them into the CERTIFIED directory I know it will take a few hours. After that I will try to REBOOT the switch it should go to CERTIFIED. From there if I boot successfully I can do a "copy CERTIFIED WORKING" to clear up the issues with that directory and from there we should be good. I am starting my download now. I will post my results in a few hours.

As I said before Benny I know this is hard to believe but including this event this is ACTUALLY the SECOND time this has happened to me on a brand new switch. So no I did not do this or anything to make this happen.

Regards,
Tony S.

Well...

Thanks to Benny and the ZModem command and good files on the other 6602's I have at this site the 6602-24 OUT OF BOX FAILURE is now up and working. Here are the steps I followed:

1) Transferred the files from my working 6602 via FTP to a directory on my laptop (I copied them from the WORKING directory.
2) Using ZModem from VxWorks (MiniBoot-->) and the "sysStartZmodem" command from Benny and after like three hours of painfully slow file transfers (I DO NOT miss the modem days at all) the files were successfully transferred to the "CERTIFIED" directory.
3) Restarted the switch and was able to complete the boot process and get to the CLI. Of course since I could only boot to CERTIFIED this is where I was at when the boot procees completed
4) Updated the files in the WORKING directory by executing the "copy certified working" command which was successful
5) Executed a "reload working no roll-back timeout" to assure I could get into WORKING and was successful as well
6) I then checked the microcode using "show microcode loaded" and all versions were the same as the other 6602-24's I have.

Switch is working and all is well. Benny, do you know where I can get a command reference for VxWorks as it relates to what is running in the Alcatel switches? This way I can become more self sufficient especially when it comes to Alcatel crash recovery. This site I am working at is an complete Alcatel for Data environment I have configured 3 6602-24's and 5 6248's. The 6602's are in a stacked configuration and the 6248's are used as closet switches. Site is only segmented with 3 vlans and we use OSPF for the routing protocol. The configurations are products of my madness and so far all is well.

Thanks for your help Benny. Also, I am glad I found this site as with what I have dealt with from Alcatel support its much more easier to come here.

Thanks Again!!!
Tony S.

Hi,

I am glad to read that your OS6600 is working again. There is unfortunately no such thing as a command reference for the Miniboot.
You can find several "crash recovery" tech tips in the TT section of the AlcaLu BPWS.

Btw. when it comes to stacking I recommend that you upgrade your switches to the latest AOS 5.1.6.R02. Don't run the GA code in a new customer setup.

Maybe I should write a book?

-benny