Netbotz Fails to boot

[DCIM_Support]

Hi,

I have successfully applied firmware updates (4.5.0) to 18 netbotz (570s, 550s & 450s) and associated sensor pods via DCE. Sadly I now have a very poorly 19th Netbotz (570) 

It now boots with the following and goes no further

U-Boot 1.1.4 (Nov 17 2015 - 17:30:35)

MPC8248 Reset Status: External Soft, External Hard

MPC8248 Clock Configuration
- Bus-to-Core Mult 3x, VCO Div 4, 60x Bus Freq 16-50 , Core Freq 50-150
- dfbrg 0, corecnf 0x10, busdf 3, cpmdf 1, plldf 0, pllmf 3
- vco_out 400000000, scc_clk 100000000, brg_clk 100000000
- cpu_clk 300000000, cpm_clk 200000000, bus_clk 100000000
- pci_clk 33333333

CPU: MPC8248 (HiP7 Rev 14, Mask 1.0 1K50M) at 300 MHz
Watchdog enabled
I2C: ready
DRAM: 128 MB
FLASH: 64 MB
PCI Scan: Found Bus 0, Device 22, Function 0
PCI Scan: Found Bus 0, Device 22, Function 1
PCI Scan: Found Bus 0, Device 22, Function 2
In: serial
Out: serial
Err: serial
Net: FCC1 ETHERNET
Model: NBRK0570
Hit any key to stop autoboot: 0
### JFFS2 loading 'nbKernel' to 0x200000
Scanning JFFS2 FS: ...................... done.
### JFFS2 load complete: 1280330 bytes loaded to 0x200000
## Booting image at 00200000 ...
Image Name:
Created: 2013-12-13 19:04:06 UTC
Image Type: PowerPC Linux Kernel Image (gzip compressed)
Data Size: 1280266 Bytes = 1.2 MB
Load Address: 00000000
Entry Point: 00000000
Verifying Checksum ... Bad Data CRC
NetBotz>

I've rerun the firmware updates locally with versions 4.3.0 and 4.5.0 using tftp with both the rootupg and "rootupg keep"

Sadly still the same, has anybody come across this issue, is there something else I could try? 

Many thanks.

(CID:105462070)

[DCIM_Support]

Dear Dominic,

I will also let the other community experts to suggest on your issue.

Here is my suggestion. If you have tried all the methods, In case if the device is not booting correctly and if you are not able to connect to the device via Advance view or through Web interface, then I would suggest you to reset or reformat the netbotz appliance. I hope you would have taken the backup of the appliance before firmware upgrade. Note: Reformating the appliance will reset the appliance to the factory defaults.

K-base ID: FA158175

This document explains the two methods used to restore the factory default settings (including user ID and password) on a NetBotz V2/V3 300, 400, 500 series monitoring appliances. Keep in mind that ALL threshold and alert recipients will be reset using this process. 

You may also want to consider resetting an appliance that is not performing properly due to unknown configuration or other potential software issues.

Resolution:
 

Method 1
How to restore the appliance to factory defaults if you know the admin username & password:

WARNING: When restoring the appliance to its factory defaults, only the appliance IP address, subnet mask, and default gateway settings are preserved. All other settings are reset to factory defaults by this procedure.

1: Open a web browser

2: Use the following url to reset everything except tcp/ip settings to defaults
http:///unconfig

3: You will be prompted for an admin username password

4: After it is entered, you will see a message on the web page that says the following:

Configuration reset requested (keeping basic network settings)....

Reset Initiated

Close the browser
The reset procedure is now complete, you will be able to log into the advanced view or basic (web) view with netbotz/netbotz

Method 2

How to restore the appliance to factory defaults if you do not know the admin username & password:

WARNING: All settings, including TCP/IP settings, are reset to factory defaults by this procedure.

1: If you have a V2 appliance, use a null modem serial cable (included with the bot) to connect the appliance to your computer system. If you have a V3 appliance, use a USBA-USBB cable(included with the netbot) to connect the appliance to your computer system.

2: Start a serial communications application (such as Hyper terminal or putty) on your computer system.

3: Configure and establish a serial connection with the appliance. Use the following serial communication settings:

• Bits per second: 38400
• Data bits: 8
• Parity: none
• Stop Bits: 1
• Flow Control: Hardware

4: After you have successfully established a serial connection to the appliance, power-cycle the appliance. When the message:
"Hit any key to stop autoboot:"

appears on screen, press Enter to interrupt the boot process and activate the NetBotz> prompt.

5: Type at the NetBotz> prompt: configreset

and then press Enter

The appliance will erase its Flash memory, write a new default configuration, and then restart automatically.

If you need to reset the appliance with a static ip, after the Netbot reboots, let it boot fully so that you get a login prompt.
Login with either root/netbotz (V2) or root/apc (V3) and follow the prompts to reset the ip settings

You can now close the serial communications program, disconnect your console cable, and log into the appliance using the default User ID and Password of netbotz (V2) or apc (v3).

I hope this helps.

Regards,

Bala

(CID:105462105)

[DCIM_Support]

Hi Dominic,

I'm assuming this is only one of the devices, not all 18. If the TFTP flash without the keep fails it is possibly a hardware issue. The configreset Bala mentioned should set all to defaults but the TFTP flash without the keep option (and of course not re-importing a backup) should reset the device as well. You may also want to try these (TFTP no keep or configreset) with nothing connected (sensors, pods, etc) to be sure it's not due to a connected device.

It's possible too that there was something with the download so maybe also try a re-download or downloading 4.5.1 and running the TFTP flash without keep and without importing a backup. 

Steve

(CID:105462139)

[DCIM_Support]

Big thank you to Steve and Bala, you led me to a fix,

Steps used to fix the “Bad Data CRC” issue

Remove all pods, sensors and usb devices

Interrupt boot

Netbotz>configreset

Interrupt boot

Netbotz>setenv serverip “tftp server ip”

Netbotz>saveenv

Netbotz>reset

Interrupt boot

Netbotz>setenv ipaddr “botz ip”

Netbotz>setenv gatewayip “gateway ip”

Netbotz>setenv netmask “netmask”

Netbotz>saveenv

Netbotz>reset

Interrupt boot

At this point, I again attempted a “rootupg” with firmware versions 4.2.0, 4.3.0 and 4.5.0, same problem “Bad Data CRC” then I found this post on the APC forum "Netbotz 500 booting seems to be stuck", instead of using “rootupg” I repeated the above steps and then ran

Netbotz>postupg

Netbotz>kernupg

Netbotz>reset

It just so happened that the tftp program was pointing at the firmware version 4.2.0, these steps may work with all levels of firmware?

The Netbotz is again working and connected to DCE, this time the firmware upgrade via DCE worked.

Thank you both again for your help

(CID:105462504)

[DCIM_Support]

Hi Dominic, Any time you do the tftp flash, you should have only one firmware in the folder at a time. The process won't know which one to use so I'm guessing it'll use the first one. I never tested it. I'm not familiar with the Netbotz>reset. Is that resetting the setenv parameters? If so, I wouldn't do a saveenv and then a reset until it's done. If you do, then yes I would expect to need to repeat the setenv process again. Either way, I'm glad you got it straightened out. Steve

(CID:105462505)

[DCIM_Support]

This question is closed for comments. You're welcome to start a new topic if you have further comments on this issue.