For more details, please see ourCookie Policy.

Ethernet Fabric (VDX, CNA)

New Contributor
Posts: 4
Registered: ‎06-22-2010

How do you recover a VDX-6740 from BootProm prompt?



Here is where the switch is stuck not sure how it got to this condition it's a Lab use switch, I just need to recover it if possible.


Guys I have a VDX-6740 in the Dell / EMC Denver Data Center that I need to rebuild from the prom level commands.

BootROM version: 1.0.30


It looks like the EXT2 file system is corrupted.


It seems like this would be a no brainer to an internal Brocade guru with the command syntax for the boot prom to rebuild this.


I would think that the internal compact flash which is housing the NOS 4.1.2x version should be able to be rebuilt via the boot prom commands provided the compact flash card is not defective.


I have the NOS revision 5.0.2b and 6.0.1a on a Brocade compatible USB stick.


Can any of the Brocade guys internal engineers for VDX-6740 share the boot prom commands to rebuild the NOS on the internal compact flash.


Looks like the commands are available at the boot prom level however boot prom the command help options are limited at this particular boot prom revision.



This is what happens during the boot sequence,


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=0x0e0e0b0a] [0xfe008f3c=0x080a0b0d] [0xfe008f40=0x0a004004]

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


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.


usb reset 0

(Re)start USB 0...

USB:   Register 10011 NbrPorts 1


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


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/zImage.tree.initrd" from usb device 0:1 (usbda1)

Failed to mount ext2 filesystem...

** Bad ext2 partition or disk - usb 0:1 **

Loading file "boot/silkworm.dtb" from usb device 0:1 (usbda1)

Failed to mount ext2 filesystem...

** Bad ext2 partition or disk - usb 0:1 **

Loading file "boot/hv.uImage" from usb device 0:1 (usbda1)

Failed to mount ext2 filesystem...

** Bad ext2 partition or disk - usb 0:1 **

Loading file "boot/silkworm_hct.dtb" from usb device 0:1 (usbda1)

Failed to mount ext2 filesystem...

** Bad ext2 partition or disk - usb 0:1 **

WARNING: adjusting available memory to 30000000

Wrong Image Format for bootm command

ERROR: can't get kernel image!




I have all these Brocade boot prom commands available  however, I do not have any detailed information how to use them and command completion does not seem to be an option.


I just need to understand what the process is to load the NOS boot image from the prom level. Typically with other vendors it would be some sort of Binary and kickstart files that I would load however, not sure what that process is for Brocade 


I can do this on the competitors (Cisco) switch load the  NX-OS code from the loader / boot prom prompt.

“bad word I know!”


Hopefully a crippled NOS or a corupted compact flash does not mean a switch replacement.

Any help is appreciated



Dell EMC



=> help

?       - alias for 'help'

base    - print or set address offset

bcmspi  - bcmspi    - SWITCH SPI utility commands;

bdinfo  - print Board Info structure

boot    - boot default, i.e., run 'bootcmd'

bootd   - boot default, i.e., run 'bootcmd'

bootelf - Boot from an ELF image in memory

bootm   - boot application image from memory

bootp   - boot image via network using BOOTP/TFTP protocol

bootvx  - Boot vxWorks from an ELF image

calc_prt- calc_prt - calculate primary partition based on value of OSRootPartition

checkenv- check environment variables against persistent storage

cmp     - memory compare

coninfo - print console devices and information

cp      - memory copy

cpu     - Multiprocessor CPU boot manipulation and release

crc32   - checksum calculation

defaultenv- load environment variables from compiled in default values

dhcp    - boot image via network using DHCP/TFTP protocol

echo    - echo args to console

editenv - edit environment variable

erase   - erase FLASH memory

errata  - Report errata workarounds

execute_internal_bootcmd- execute_internal_bootcmd - execute internal multiGOS boot cmd with internal multiGOS boot args

exit    - exit script

ext2load- load binary file from a Ext2 filesystem

ext2ls  - list files in a directory (default /)

false   - do nothing, unsuccessfully

fatinfo - print information about filesystem

fatload - load binary file from a dos filesystem

fatls   - list files in a directory (default /)

fdt     - flattened device tree utility commands

flinfo  - print FLASH memory information

form_internal_bootvars- form_internal_bootvars - form internal multiGOS boot variables

fsdevinit- fsdevinit - initialize the filesystem device to load files from for current GOS

go      - start application at address 'addr'

help    - print command description/usage

hinv    - hinv  - print Hardware System Inventory

i2c     - I2C sub-system

iminfo  - print header information for application image

imls    - list all images found in flash

imxtract- extract a part of a multi-image

interrupts- enable or disable interrupts

irqinfo - print information about IRQs

itest   - return true/false on integer compare

loadb   - load binary file over serial line (kermit mode)

loadenv - load environment variables from persistent storage

loads   - load S-Record file over serial line

loady   - load binary file over serial line (ymodem mode)

loop    - infinite loop on address range

loopbacktest- loopback test in management port

makesinrec- makesinrec  - make a SIN record

md      - memory display

mdio45  - MDIO Clause 45 utility commands

mii     - MII utility commands

mii_scan- MII scan commands

mm      - memory modify (auto-incrementing address)

mtest   - simple RAM read/write test

mw      - memory write (fill)

nfs     - boot image via network using NFS protocol

nm      - memory modify (constant address)

passwd  - passwd  - Set the boot modification password

pci     - list and access PCI Configuration Space

physaddrtest- memory test over a 64-bit physical address range using a special test TLB

ping    - send ICMP ECHO_REQUEST to network host

printenv- print environment variables

protect - enable or disable FLASH write protection

rarpboot- boot image via network using RARP/TFTP protocol

readlinkspeed- read management port speed

reset   - Perform RESET of the CPU

resetpw - resetpw  - Remove the boot modification password

run     - run commands in an environment variable

sata    - SATA sub system

saveenv - save environment variables to persistent storage

set_internal_bootvar- set_internal_bootvar - set an internal multiGOS boot variable

setenv  - set environment variables

setexpr - set environment variable as the result of eval expression

show_internal_bootvars- show_internal_bootvars - show internal multiGOS boot variables

showvar - print local hushshell variables

sleep   - delay execution for some time

source  - run script from memory

sspi    - SPI utility commands

test    - minimal test like /bin/sh

tftpboot- boot image via network using TFTP protocol

true    - do nothing, successfully

ulpi    - Perform operations on the ULPI tranciever (must first do usb reset)

usb     - USB sub-system

usbboot - boot from USB device

version - print monitor version

w0w1    - Walking 0's and walking 1's test with optional save/restore

warmboot- b 0xfffffffc


let me know.









Former Brocadian
Posts: 102
Registered: ‎02-04-2015

Re: How do you recover a VDX-6740 from BootProm prompt?

Hi Mike,


As you mentioned, and from the output shared, the flash is corrupted and it can't be recovered remotely, unfortunately.


The only option is to contact Brocade Support and have the switch replaced, giving that it has a valid contract.





Any and all information provided by me is not reviewed, approved or endorsed by Brocade and is provided solely as a convenience for Brocade customers.

All systems and all networks are different and unique. If you have a service affecting network problem, please open a TAC service request for service through Brocade, or through your OEM equipment provider. If this provided you with a solution to this issue, please mark it with the button at the bottom "Accept as solution" .

Join the Community

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