Ethernet Fabric (VDX, CNA)

Reply
New Member
Posts: 1
Registered: ‎04-15-2014

How to recovery VDX 6740-24F Firmware while NOS not ready occurred %3F%21

Hi ! All,

 

I have a VDX 6740-24F Switch but cannot boot to normal state, the following are the booting log captured from console

port, the major problem is I cannot login to NOS which it say "Error: Network OS is not ready. Please login later."

 

How do I recovery the image from this situation ?!  Many Thanks !!!

 

BootROM version: 1.0.30
Copyright (C) 2011 Brocade Communication.

CPU0:  P3041, Version: 2.0, (0x82110320)
Core:  E500MC, Version: 3.2, (0x80230032)
Clock Configuration:
       CPU0:1500 MHz, CPU1:1500 MHz, CPU2:1500 MHz, CPU3:1500 MHz,
       CCB:750  MHz,
       DDR:500  MHz (1000 MT/s data rate) (Asynchronous), LBC:46.875 MHz
       FMAN1: 375 MHz
       PME:   375 MHz
L1:    D-cache 32 kB enabled
       I-cache 32 kB enabled
Model ID: 131
Board: P3041 CASTOR, 36-bit Addressing
reset reason was 0x00000001: Power Up
I2C:   ready
DRAM:  Initializing....
Enabled DHC_EN
DIMM 0 [0xfe008174=0x8675a607] [0xfe008f38=0x10100d0b] [0xfe008f3c=0x0a0c0d0e] [
0xfe008f40=0x0c004004]
6 GiB left unmapped
    DDR: 8 GiB (DDR3, 64-bit, CL=7, ECC on)
testdram value not set, dram test not run
Now running in RAM - U-Boot at: 7ff30000
FLASH: 4 MiB
L2:    128 KB enabled
Corenet Platform Cache: 1024 KB enabled
SERDES: bank 2 disabled
PCI: gd->brcd_flags = 0, PCI init
    PCIE1 connected to Slot 1 as Root Complex (base addr fe200000)
               Scanning PCI bus 01
    PCIE0 on bus 00 - 01
In:    serial
Out:   serial
Err:   serial
    SRIO1: disabled
    SRIO2: disabled
NVRAM/RTC oscillator already turned on in a previous boot
Net:   Fman: Uploading microcode version 101.6.0.
FM1@DTSEC4, FM1@DTSEC5
usb reset 0
(Re)start USB 0...
USB:   Register 10011 NbrPorts 1
USB EHCI 1.00
scanning bus for devices... 2 USB Device(s) found
       scanning bus for storage devices... 1 Storage Device(s) found
Hit ESC to stop autoboot:  0
Loading Environment 0 from NVRAM...
(Re)start USB 0...
USB:   Register 10011 NbrPorts 1
USB EHCI 1.00
scanning bus for devices... 2 USB Device(s) found
       scanning bus for storage devices... 1 Storage Device(s) found
setting prt to 1
Loading file "/boot/fastloading.mdt" from usb device 0:1 (usbda1)
155 bytes read
Image: [uImage]
 Image: [hv.uImage]
 Image: [silkworm.dtb]
 Image: [silkworm_hct.dtb]
 WARNING: adjusting available memory to 30000000
## Booting kernel from Legacy Image at 02000000 ...
   Image Name:
   Image Type:   PowerPC Linux Kernel Image (uncompressed)
   Data Size:    420064 Bytes = 410.2 KiB
   Load Address: 00000000
   Entry Point:  00000000
   Verifying Checksum ... OK
## Flattened Device Tree blob at 04000000
   Booting using the fdt blob at 0x4000000
   Loading Kernel Image ... OK
OK
   Loading Device Tree to 00ff7000, end 00fff1e3 ... OK
=======================================
Freescale Hypervisor 0.8-004
Hypervisor command line: config-addr=0x3000000 p1-linux="root=/dev/sda1  rootfst
ype=ext4 quiet"
[0] malloc_init: using 31 MiB at 0x7e0b7930 - 0x7fffffff
Device tree compatible: brocade,SILKWORM_PB
[0] dt_read_aliases: Alias pci1 points to non-existent /pcie@ffe201000
[0] dt_read_aliases: Alias sec_jr0 points to non-existent /soc@ffe000000/crypto@
300000/jr@1000
[0] dt_read_aliases: Alias sec_jr1 points to non-existent /soc@ffe000000/crypto@
300000/jr@2000
[0] dt_read_aliases: Alias sec_jr2 points to non-existent /soc@ffe000000/crypto@
300000/jr@3000
[0] dt_read_aliases: Alias sec_jr3 points to non-existent /soc@ffe000000/crypto@
300000/jr@4000
[0] dt_read_aliases: Alias rtic_a points to non-existent /soc@ffe000000/crypto@3
00000/rtic@6000/rtic-a@0
[0] dt_read_aliases: Alias rtic_b points to non-existent /soc@ffe000000/crypto@3
00000/rtic@6000/rtic-b@20
[0] dt_read_aliases: Alias rtic_c points to non-existent /soc@ffe000000/crypto@3
00000/rtic@6000/rtic-c@40
[0] dt_read_aliases: Alias rtic_d points to non-existent /soc@ffe000000/crypto@3
00000/rtic@6000/rtic-d@60
[0] assign_callback: device serial0 in serial0 not found
[0] assign_callback: device /hvcpld in fpga not found
[0] remap_restart_init: undefine restart-maps-to. Setting to remap_restart_unc.
[0] watchdog enabled with period 38
[1] watchdog enabled with period 38
[2] watchdog enabled with period 38
[3] watchdog enabled with period 38
[0] assign_callback: device /soc/memory-controller@9000 in memory-controller@900
0 not found
[0] assign_callback: device mdio0 in mdio0 not found
[0] assign_callback: device phy5 in phy5 not found
Bootargs set for cpu = 0 guest p1-linux bootagrs = root=/dev/sda1  rootfstype=ex
t4 quiet
HV>
 part1 ACTIVE
[0] loading binary image from 0x79fff000 to 0x3000000
[0] Loading uImage from 0x78000000 to 0
[0] branching to guest p1-linux, 2 cpus
HV> this is quiet!

 end of DRAM 4294967296 memstart_addr0 total_lowmem 4294967296
SLUB: dfree enabled
PRIMING SLUB: main caches
SLUB: export __kmalloc at 0x40106afc changed to 0x40105050
SLUB: export vmalloc at 0x400f54b8 changed to 0x400f526c
SLUB: export vfree at 0x400f4658 changed to 0x400f4588
network namespace NR (VRF) started
mmod_sysctl_inited: 1

 Fman microcode       51       45       46

 FMAN microcode UC size 0x1b64
default MII is 0xc10a4000 for tsec0
default MII is 0xc10ac000 for tsec0
Uboot wdt counter value: 0
INIT: version 2.78 booting
e2fsck 1.41.12 (17-May-2010)
/dev/sda1: clean, 14256/119280 files, 185977/476806 blocks
e2fsck 1.41.12 (17-May-2010)
/dev/sda2: recovering journal
/dev/sda2: clean, 6377/119280 files, 119046/476928 blocks
Firmware Integrity Check is default off
Bypassing firmware validation.
mount: sysfs already mounted or /sys busy
mount: according to mtab, none is already mounted on /sys
mknod: /dev/fsl-hv: File exists
/etc/rc.d/rc.sysinit: /sbin/fwcheck: No such file or directory
Hostname is sw0
INIT: Entering runlevel: 3
        FIPS-mode test application

1. Non-Approved cryptographic operation test...
        a. Excluded algorithm (MD5)...successful
        b. Included algorithm (D-H)...successful
2. Automatic power-up self test...successful
3. AES-128,192,256 CBC  encryption/decryption...successful
4. RSA key generation and encryption/decryption...successful
4.1. RSA 2048 with 'SHA256' testing...successful
5. TDES-CBC encryption/decryption...successful
6a. SHA-1 hash...successful
6b. SHA-256 hash...successful
6c. SHA-512 hash...successful
6d. HMAC-SHA-1 hash...successful
6e. HMAC-SHA-224 hash...successful
6f. HMAC-SHA-256 hash...successful
6g. HMAC-SHA-384 hash...successful
6h. HMAC-SHA-512 hash...successful
7. Non-Approved cryptographic operation test...
        a. Excluded algorithm (MD5)...Not executed
        b. Included algorithm (D-H)...successful as expected
8. Zero-ization...Successful
9. TLS KDF...successful
10. SSH KDF...successful

All tests completed with 0 errors
(none)
Waiting to starting configuration management service
Starting configuration management service
[wmd_init]: chunk_size = 0xa00000
[wmd_init]: Checksum does not match. current_cksum = 0x16c0388f stored_cksum = 0
x8fd5a6c1
[wmd_init]: FPGA version = 0x002223a3
[wmd_init]: reset_reason = 0x1
[wmd_init]: updated reset_reason = 0x0

Reset reason = 0x1
wmem: b0004000:247463936
tbuf: 8ff00000:536870912
Found 3(threshold 5) abnormal reboots within 3000 seconds window(threshold)
Starting Dcmd ... Wed Apr 16 02:57:11 GMT 2014
server starting
server starting
Connecting to Dcmd & Ccmd database.......done
waiting for server to shut down.... done
server stopped
waiting for server to shut down.... done
server stopped

pcie_event_isr: virq 170 core 1 MCSR 0x0 MSR 0x10021002
CPLD INIT DONE
PCIe Event [UNKNOWN]  slot 0 Source Bus 0 Dev 0 MM Parent Bus 0 Dev 0 Events: 1
Cobra rev B found
Creating L3-L2 fifo Wed Apr 16 02:58:27 GMT 2014 ...
Starting HASM ... Wed Apr 16 02:58:27 GMT 2014
Exisitng reboot reason fsize = 5 rb=
Global Fan Direction: Port Side INTAKE
tp_register, got none fss tp handle=10000001h
2014/04/16-02:58:32, [HASM-1004], 6278,, INFO, VDX6740, Processor reloaded - Res
et.
********************************************************************************
************************
** Crashed in OM/Worker (WaveNs:Smiley Very HappyatabaseObjectManagerExecuteCopySchemaWorker::e
xecuteCopySchemaMessageHandler(WaveNs:Smiley Very HappyatabaseObjectManagerExecuteCopySchemaMes
sage*))
********************************************************************************
************************

WaveNs:Smiley Very HappyatabaseObjectManagerExecuteCopySchemaWorker::executeCopySchemaMessageHa
ndler(WaveNs:Smiley Very HappyatabaseObjectManagerExecuteCopySchemaMessage*)
WaveNs::WaveObjectManager:Smiley TonguerismOperationMapContext::executeMessageHandler(WaveN
s:Smiley TonguerismMessage*&)
WaveNs::WaveObjectManager::handlePrismMessage(WaveNs:Smiley TonguerismMessage*)
WaveNs:Smiley TonguerismThread::start()
WaveNs:Smiley TonguerismPosixThread:Smiley TonguethreadStartMethod(WaveNs:Smiley TonguerismPosixThread*)
/lib/libpthread.so.0 [0xe5a8e58]
clone

 

Network OS (sw0)


sw0 console login: admin


Password:
Error: Network OS is not ready. Please login later.


Network OS (sw0)


sw0 console login:
*** CORE FILES WARNING (04/16/14 - 03:00:01 ) ***
1 KBytes in  file(s)
use "copy support" command to upload


*** FFDC FILES WARNING (04/16/14 - 03:00:01 ) ***
1 KBytes in  file(s)
use "copy support" command to upload

 


Network OS (sw0)


sw0 console login: admin


Password:
Error: Network OS is not ready. Please login later.


Network OS (sw0)


sw0 console login: Wed Apr 16 03:04:11 GMT 2014 :: Confd: Waiting for Dcmd to be
come ready...

 

Network OS (sw0)


sw0 console login:


Network OS (sw0)


sw0 console login:


Network OS (sw0)


sw0 console login:


Network OS (sw0)


sw0 console login: admin


Password:
Error: Network OS is not ready. Please login later.


Network OS (sw0)


sw0 console login:


Network OS (sw0)


sw0 console login: admin


Password:
Error: Network OS is not ready. Please login later.


Network OS (sw0)


sw0 console login:

New Member
Posts: 1
Registered: ‎06-30-2014

Re: How to recovery VDX 6740-24F Firmware while NOS not ready occurred %3F%21

Bump. Different crash, same issue.

Brocadian
Posts: 1
Registered: ‎12-22-2009

Re: How to recovery VDX 6740-24F Firmware while NOS not ready occurred %3F%21

It seems to be that the Local NOS booting database is corrupted. So please try the below steps to resolve the issue,

 

Follow the below steps to resolve the issue:

1) Login as "root".

2) Run the following commands: 

 a) SW01:root> rm /etc/fabos/Dcmd/Dcmd.Linux.powerpc.cfg
 b) SW01:root> rm /etc/fabos/Ccmd/Ccmd.Linux.powerpc.cfg

3) Reboot the switch

4) Upon reboot, the database will be rebuilt and login to NOS CLI should be possible.
Occasional Contributor
Posts: 5
Registered: ‎01-23-2015

Re: How to recovery VDX 6740-24F Firmware while NOS not ready occurred %3F%21

which is the root password?



 

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

Re: How to recovery VDX 6740-24F Firmware while NOS not ready occurred %3F%21

default root password on VDX is "fibranne"

TechHelp24

Join the Community

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