UPGRADE AOS v6.4.4.645.R01 + Miniboot v6.4.3.565.R01

Post Reply
cedric64
Member
Posts: 13
Joined: 23 Apr 2014 09:38

UPGRADE AOS v6.4.4.645.R01 + Miniboot v6.4.3.565.R01

Post by cedric64 »

Hello,

I'm looking for the UBOOT/MINIBOOT files Version 6.4.3.565.R01 for OS6400

Have you got a link for me to downoad it please ?

Thanks.
Last edited by cedric64 on 23 Apr 2014 21:14, edited 1 time in total.
devnull
Alcatel Unleashed Certified Guru
Alcatel Unleashed Certified Guru
Posts: 976
Joined: 07 Sep 2010 10:16
Location: Germany

Re: OS6400 Miniboot upgrade v6.4.3.565.R01

Post by devnull »

Should be in 6.4.3 GA files which you can get via business Portal or your distri.

You can also use google and land at http://support.alcadis.nl/downloads/Alc ... ch/OS6400/
(not sure whether they are supposed to have that public available)
cedric64
Member
Posts: 13
Joined: 23 Apr 2014 09:38

Re: OS6400 Miniboot upgrade v6.4.3.565.R01

Post by cedric64 »

Thank you, I just found the files

I just tried with this command : "update miniboot all"

And the OS6400 asks for the file : "Gfpga.upgrade_kit"

Do you know why ?
silvio
Alcatel Unleashed Certified Guru
Alcatel Unleashed Certified Guru
Posts: 1890
Joined: 01 Jul 2008 10:51
Location: Germany

Re: OS6400 Miniboot upgrade v6.4.3.565.R01

Post by silvio »

you have to copy the miniboot, uboot, fpga etc. always to /flash. You will find the nessesary infos in the RN https://service.esd.alcatel-lucent.com/ ... /caWy/2w1g.
regards
Silvio
cedric64
Member
Posts: 13
Joined: 23 Apr 2014 09:38

Re: OS6400 Miniboot upgrade v6.4.3.565.R01

Post by cedric64 »

Thank you Silvio

90 % of my OS6400-U24 upgrade = SUCCESS
10 % of failure (with the stack-2)

Like this issue for example :

After the upload of the AOS files (v6.4.4.645.R01) in the folder /flash/working

I launch this :

OS6400> reload working no rollback-timeout in 00:01
Confirm Activate (Y/N) : Y

And I wait...
...but I can see the log in my logserveur
...And here is the logfile

Apr 23 23:02:09 - CSM-CHASSIS(103) Data: == CSM == CERTIFYing software process started
Apr 23 23:02:09 - CSM-CHASSIS(103) Data: == CSM == Setting CERTIFY Timeout for 800 seconds#012
Apr 23 23:02:50 - CCM-CHASSIS(100) Data: ******* CS Debug: STR NON FATAL ********
Apr 23 23:02:50 - CCM-CHASSIS(100) Data: Source file name : cs_ccm_main.c
Apr 23 23:02:50 - CCM-CHASSIS(100) Data: Line number in the file: 627
Apr 23 23:02:50 - CCM-CHASSIS(100) Data: Error number : 00000000
Apr 23 23:02:50 - CCM-CHASSIS(100) Data: Comments : Call to mip_write_error failed
Apr 23 23:02:50 - CCM-CHASSIS(100) Data: ******* CS Debug: STR NON FATAL ********
Apr 23 23:02:50 - CCM-CHASSIS(100) Data: Source file name : cs_ccm_main.c
Apr 23 23:02:50 - CCM-CHASSIS(100) Data: Line number in the file: 633
Apr 23 23:02:50 - CCM-CHASSIS(100) Data: Error number : 00000000
Apr 23 23:02:50 - CCM-CHASSIS(100) Data: Comments : Call to mip_deferred_answer failed
Apr 23 23:08:45 - CSM-CHASSIS(103) Data: == CSM == Manual-FlashSynchro in progress, try again later
Apr 23 23:08:45 - CSM-CHASSIS(103) Data: == CSM == Primary.CMM is to Flash Synchro with slot 2 .
Apr 23 23:08:45 - CSM-CHASSIS(103) Data: == CSM == ftp in progress, please wait ...
Apr 23 23:09:00 - CVM-CHASSIS(104) Data: == CVM == Synchro Timer set for 900 seconds
Apr 23 23:09:00 - FTP(82) Data: Session 0 New Connection, Client Address 127.2.66.1
Apr 23 23:09:00 - FTP(82) Data: Get /flash/working/software.lsm!
Apr 23 23:09:00 - FTP(82) Data: Session 0 Ending
Apr 23 23:09:00 - FTP(82) Data: Session 0 New Connection, Client Address 127.2.66.1
Apr 23 23:09:00 - FTP(82) Data: Get /flash/working/Gbase.img!
Apr 23 23:13:26 - FTP(82) Data: Get /flash/working/Geni.img!

...After 60 minutes of waiting, no more get file... no more certify process... no reboot....

So, when I attempt to launch a new reboot, here is the new issue :

OS6400> reload working no rollback-timeout in 00:01
ERROR: System resource unavailable, try again later

Do you know a way to kill the process please ?
Last edited by cedric64 on 25 Apr 2014 12:41, edited 1 time in total.
devnull
Alcatel Unleashed Certified Guru
Alcatel Unleashed Certified Guru
Posts: 976
Joined: 07 Sep 2010 10:16
Location: Germany

Re: UPGRADE AOS v6.4.4.645.R01 + Miniboot v6.4.3.565.R01

Post by devnull »

Reboot, (e.g. Powerdown) i had that once before, and i think i solved it this way.
cedric64
Member
Posts: 13
Joined: 23 Apr 2014 09:38

Re: UPGRADE AOS v6.4.4.645.R01 + Miniboot v6.4.3.565.R01

Post by cedric64 »

Thanks but I need to find a solution without any reboot.

Is there a way to kill a process in dShell mode ?
User avatar
cavagnaro
Alcatel Unleashed Certified Guru
Alcatel Unleashed Certified Guru
Posts: 7014
Joined: 14 Sep 2005 19:45
Location: Brasil, Porto Alegre
Contact:

Re: UPGRADE AOS v6.4.4.645.R01 + Miniboot v6.4.3.565.R01

Post by cavagnaro »

If you already waited 60 min what is the difference on doing it again?
Ignorance is not the problem, the problem is the one who doesn't want to learn

OTUC/ICS ACFE/ACSE R3.0/4.0/5.0/6.0
Certified Genesys CIV 8.5
Certified Genesys Troubleshooting 8.5
Certified Genesys BEP 8.x
Genesys Developer
cedric64
Member
Posts: 13
Joined: 23 Apr 2014 09:38

Re: UPGRADE AOS v6.4.4.645.R01 + Miniboot v6.4.3.565.R01

Post by cedric64 »

I've checked again my OS6400 failures during upgrade AOS and I've found 2 differents issues.

[ FIRST CASE ]

After 60 minutes of waiting, I can't do it again because the certify process is still trying (loop messages like "certify failed" in logfiles) without any transfer of any file.

OS6400-ISSUE-N1> show log swlog timestamp 04/25/2014 20:00 appid chassis
- FRI APR 25 20:13:00 2014 CSM-CHASSIS info == CSM == Images from Working dir were updated, Certified Prohibited
- FRI APR 25 20:13:00 2014 CCM-CHASSIS warning CCM_CSM_FLASH_SYNCHRO_RS-appError 26
- FRI APR 25 20:13:10 2014 CSM-CHASSIS info == CSM == Images from Working dir were updated, Certified Prohibited
- FRI APR 25 20:13:10 2014 CCM-CHASSIS warning CCM_CSM_FLASH_SYNCHRO_RS-appError 26
- FRI APR 25 20:23:07 2014 CSM-CHASSIS info == CSM == Images from Working dir were updated, Certified Prohibited
- FRI APR 25 20:23:07 2014 CCM-CHASSIS warning CCM_CSM_FLASH_SYNCHRO_RS-appError 26
- FRI APR 25 20:23:17 2014 CSM-CHASSIS info == CSM == Images from Working dir were updated, Certified Prohibited
- FRI APR 25 20:23:17 2014 CCM-CHASSIS warning CCM_CSM_FLASH_SYNCHRO_RS-appError 26
- FRI APR 25 20:33:00 2014 CSM-CHASSIS info == CSM == Images from Working dir were updated, Certified Prohibited
- FRI APR 25 20:33:00 2014 CCM-CHASSIS warning CCM_CSM_FLASH_SYNCHRO_RS-appError 26
- FRI APR 25 20:33:10 2014 CSM-CHASSIS info == CSM == Images from Working dir were updated, Certified Prohibited
- FRI APR 25 20:33:10 2014 CCM-CHASSIS warning CCM_CSM_FLASH_SYNCHRO_RS-appError 26
- FRI APR 25 20:43:07 2014 CSM-CHASSIS info == CSM == Images from Working dir were updated, Certified Prohibited
- FRI APR 25 20:43:07 2014 CCM-CHASSIS warning CCM_CSM_FLASH_SYNCHRO_RS-appError 26
- FRI APR 25 20:43:17 2014 CSM-CHASSIS info == CSM == Images from Working dir were updated, Certified Prohibited
- FRI APR 25 20:43:17 2014 CCM-CHASSIS warning CCM_CSM_FLASH_SYNCHRO_RS-appError 26
- FRI APR 25 20:53:00 2014 CSM-CHASSIS info == CSM == Images from Working dir were updated, Certified Prohibited
- FRI APR 25 20:53:00 2014 CCM-CHASSIS warning CCM_CSM_FLASH_SYNCHRO_RS-appError 26
- FRI APR 25 20:53:11 2014 CSM-CHASSIS info == CSM == Images from Working dir were updated, Certified Prohibited
- FRI APR 25 20:53:11 2014 CCM-CHASSIS warning CCM_CSM_FLASH_SYNCHRO_RS-appError 26
- FRI APR 25 21:03:16 2014 CSM-CHASSIS info == CSM == Images from Working dir were updated, Certified Prohibited
- FRI APR 25 21:03:16 2014 CCM-CHASSIS warning CCM_CSM_FLASH_SYNCHRO_RS-appError 26
- FRI APR 25 21:03:26 2014 CSM-CHASSIS info == CSM == Images from Working dir were updated, Certified Prohibited
- FRI APR 25 21:03:26 2014 CCM-CHASSIS warning CCM_CSM_FLASH_SYNCHRO_RS-appError 26

OS6400-ISSUE-N1> show running-directory
CONFIGURATION STATUS
- Running CMM : PRIMARY,
- CMM Mode : DUAL CMMs,
- Current CMM Slot : 1,
- Running configuration : WORKING,
- Certify/Restore Status : CERTIFY NEEDED
SYNCHRONIZATION STATUS
- Flash Between CMMs : NOT SYNCHRONIZED,
- Running Configuration : NOT SYNCHRONIZED,
- Stacks Reload On Takeover: ALL NIs (CMM Only Config OUT-OF-SYNC)

OS6400-ISSUE-N1> debug flash-synchro recover

OS6400-ISSUE-N1> copy working certified
- CERTIFY process failed
- ERROR: Attempt to copy working to cert w/flash synchr failed
- CVM response to CSM CERTIFY process failed


OS6400-ISSUE-N1> copy certified working

Logfile :
- Apr 25 21:23:22 edg-pia64-0103 CSM-CHASSIS(103) Data: == CSM == File transfer is completed successfully
- Apr 25 21:23:22 edg-pia64-0103 CSM-CHASSIS(103) Data: == CSM == Please wait while module 2 performs Certify process ...
- Apr 25 21:23:44 edg-pia64-0103 CSM-CHASSIS(103) Data: == CSM == Flash Synchronization process completed successfully

OS6400-ISSUE-N1> show running-directory
CONFIGURATION STATUS
- Running CMM : PRIMARY,
- CMM Mode : DUAL CMMs,
- Current CMM Slot : 1,
- Running configuration : WORKING,
- Certify/Restore Status : CERTIFIED
SYNCHRONIZATION STATUS
- Flash Between CMMs : SYNCHRONIZED,
- Running Configuration : SYNCHRONIZED,
- Stacks Reload on Takeover: PRIMARY ONLY

>> problem solved >> will retry upgrade AOS


[ SECOND CASE ]

- Error "******* CS Debug: STR NON FATAL ********" + no-reboot after upload AOS.

OS6400-ISSUE-N2> reload working no rollback-timeout in 00:01
- ERROR: System resource unavailable, try again later

OS6400-ISSUE-N2> show running-directory
CONFIGURATION STATUS
- Running CMM : PRIMARY,
- CMM Mode : DUAL CMMs,
- Current CMM Slot : 1,
- Running configuration : WORKING,
- Certify/Restore Status : CERTIFY NEEDED
SYNCHRONIZATION STATUS
- Flash Between CMMs : NOT SYNCHRONIZED,
- Running Configuration : SYNCHRONIZED,
- Stacks Reload on Takeover: PRIMARY ONLY

OS6400-ISSUE-N2> copy working certified flash-synchro
- ERROR: System resource unavailable, try again later

OS6400-ISSUE-N2> copy certified working
- ERROR: System resource unavailable, try again later

OS6400-ISSUE-N2> show health all memory
- Memory Limit Curr Avg Avg Max
-----------------+-------+------+------+-----+----
- 01 80 00 00 00 00
- 02 80 66 66 66 66

>> problem unsolved

I'm now looking for a command (in dShell mode ?) to reinitialize a memory module (without any powerdown)
cedric64
Member
Posts: 13
Joined: 23 Apr 2014 09:38

Re: UPGRADE AOS v6.4.4.645.R01 + Miniboot v6.4.3.565.R01

Post by cedric64 »

I'm still looking to resolve my memory issue.

OS6400-ISSUE-N2> show health all memory
- Memory Limit Curr Avg Avg Max
-----------------+-------+------+------+-----+----
- 01 80 00 00 00 00
- 02 80 66 66 66 66

OS6400-ISSUE-N2> debug memory monitor enable
OS6400-ISSUE-N2> debug memory monitor show log
Task Memory Memory Addr of OS func Calling Previous
Name Comments Addr Size OS call Called Function Caller
---------+--------+--------+----------+--------+----------+----------+----------
tssApp_6* 05aed268 320 00390e3c selWakeupT taskInit taskCreat
tssApp_6* TCB Stac 05b870a0 20544 003e4b94 taskCreat taskSpawn ssAppChild
tssApp_6* Vx B Sem 05af0eb8 40 003e07a4 semBCreate pipe ssAppChild
tssApp_6* Vx B Sem 05aef670 40 003e07a4 semBCreate pipe ssAppChild
tssApp_6* 05b8c0f0 5121 003b9600 rngCreate pipe ssAppChild
tssApp_6* 05aeae08 16 003b95e8 rngCreate pipe ssAppChild
tssApp_6* 05ae5870 10 003872fc iosDevAdd pipe ssAppChild
(...)
OS6400-ISSUE-N2> debug memory monitor disable

I think the RAM of slot-1 is still OK but I can't find any dShell command to go further.
- My uplink-port (management link) is located on this slot-1..

I don't know if the "takeover" command will cause a management lost or if I can try :-s
Post Reply

Return to “OmniSwitch 6400”