NME-WAE-502-K9 doesn´t want to boot

[jmfranco]

Hi.

I have added a new NME-WAE-502-K9 in one of our remote Cisco 2811 routers. This module doesn´t boot, and it seems to be in a loop trying to boot. I´m trying to find documentation about how to proceed with this kind of situations and this kind of network modules, but don´t find anything helpful. Please, could you give me a help?

router #service-module integrated-Service-Engine 1/0 status

Service Module is Cisco Integrated-Service-Engine1/0

Service Module supports session via TTY line 66

Service Module is failed

Service Module heartbeat-reset is enabled

Service Module is in fail open

Service Module status is not available

[Resuming connection 1 to 1.1.1.1 ... ]

ServicesEngine boot-loader>

ServicesEngine boot-loader> reboot
Rebooting !ÿNmi Npx0 Dly P92 Sha0 Kbd0 Cmos Pci Dma0 PrtB Tim Exp Rfsh Geom

Initializing memory.  Please wait. Mem0 Mem1 Ebda Sha1 CacheE Admgr1 Memmgr1 Adm
grEbda Media LowBios Brd2 Cache0 Driver PostDrv Dma1 Irq1 Vec Brd4 Time0 Kbd1 Sp
eed Com Vid0 Par PciEnum Vid1 Redir Brd6 Com KbdBuf SMM
General Software Firmbase[r] SMM Kernel 1.3.2 Feb 11 2005 11:51:07
Intel(R) E7320 Performance Development Platform

EIST: Enhanced Intel Speedstep Driver, V3.0.
EIST: Copyright (C) 2003-2006 General Software, Inc.
EIST: Built Mar  3 2006, 14:49:27
UsbHid Pwd Msg0 Msg1 Cache1 Mem2 Prot Cache2 Flg Siz0 Msg2 Ata Dsk Npx1 Apm Err
Dbg Enb App MemReduce MemSync1 Ext MemSync2 PciRom MemSync3 Setup Time1 Mfg Brd8
Com Admgr2 Cfg Brd10
DDR2 Memory 1023 MB with ECC detected
Intel(R) Celeron(R) M processor         1.00GHz
BIOS ISE 5.00, Build date: 05/05/06
System Now Booting ...

Force to boot from Primary Boot Loader ...

704 832 968 1040 1172 1184 1196 1208 1220 1228 1240 1260 1276 1288 1304 1320 133
2 1348 1368 1380 1644 1784 2060 2204 2344 2860 3376 3640 3904 4168 RSA decrypt r
eturned:33
a2f9b14f5b559e31560726525c22077b

Booting from Secure primary boot loader..., please wait.

[BOOT-ASM]

Please enter '***' to change boot configuration:
got meta list size: 2, 23, 70, 244
file opened: (hd0,1)+1, -1, -1
file closed: (hd0,1)+1
file opened: (hd0)1+255, -1, -1
file closed: (hd0)1+255
Unable to boot imageÿNmi Npx0 Dly P92 Sha0 Kbd0 Cmos Pci Dma0 PrtB Tim Exp Rfsh
Geom

Initializing memory.  Please wait. Mem0 Mem1 Ebda Sha1 CacheE Admgr1 Memmgr1 Adm
grEbda Media LowBios Brd2 Cache0 Driver PostDrv Dma1 Irq1 Vec Brd4 Time0 Kbd1 Sp
eed Com Vid0 Par PciEnum Vid1 Redir Brd6 Com KbdBuf SMM
General Software Firmbase[r] SMM Kernel 1.3.2 Feb 11 2005 11:51:07
Intel(R) E7320 Performance Development Platform

EIST: Enhanced Intel Speedstep Driver, V3.0.
EIST: Copyright (C) 2003-2006 General Software, Inc.
EIST: Built Mar  3 2006, 14:49:27
UsbHid Pwd Msg0 Msg1 Cache1 Mem2 Prot Cache2 Flg Siz0 Msg2 Ata Dsk Npx1 Apm Err
Dbg Enb App MemReduce MemSync1 Ext MemSync2 PciRom MemSync3 Setup Time1 Mfg Brd8
Com Admgr2 Cfg Brd10
DDR2 Memory 1023 MB with ECC detected
Intel(R) Celeron(R) M processor         1.00GHz
BIOS ISE 5.00, Build date: 05/05/06
System Now Booting ...

Force to boot from Primary Boot Loader ...

704 832 968 1040 1172 1184 1196 1208 1220 1228 1240 1260 1276 1288 1304 1320 133
2 1348 1368 1380 1644 1784 2060 2204 2344 2860 3376 3640 3904 4168 RSA decrypt r
eturned:33
a2f9b14f5b559e31560726525c22077b

Booting from Secure primary boot loader..., please wait.

[BOOT-ASM]

Please enter '***' to change boot configuration:
got meta list size: 2, 23, 70, 244
file opened: (hd0,1)+1, -1, -1
file closed: (hd0,1)+1
file opened: (hd0)1+255, -1, -1
file closed: (hd0)1+255
Unable to boot imageÿNmi Npx0 Dly P92 Sha0 Kbd0 Cmos Pci Dma0 PrtB Tim Exp Rfsh
Geom

Initializing memory.  Please wait. Mem0 Mem1 Ebda Sha1 CacheE Admgr1 Memmgr1 Adm
grEbda Media LowBios Brd2 Cache0 Driver PostDrv Dma1 Irq1 Vec Brd4 Time0 Kbd1 Sp
eed Com Vid0 Par PciEnum Vid1 Redir Brd6 Com KbdBuf SMM
General Software Firmbase[r] SMM Kernel 1.3.2 Feb 11 2005 11:51:07
Intel(R) E7320 Performance Development Platform

[Nicolas Fournier]

Hi,

Can you try install the sysimg on it through this procedure:

http://www.cisco.com/en/US/docs/app_ntwk_services/waas/waas/v441/configuration/guide/maint.html#wp1105252 then from there try to install the WAAS/ACNS image on the module.

Regards,

Nicolas

[jmfranco]

Thanks Nicolas, but this procedure is only for WAE appliances. Now I´m trying to load sysimg from usb pendrive connected to one of router 2800 usb ports, and I´m configuring IOS router as TFTP server for sysimg file, but It doesn´t seems to work fine. Anybody could tell me software recovery procedure on this kind of NME platforms?

router(config)#tftp-server usbflash1:waas-4.4.7.4-k9.sysimg
router(config)#end

router#sh run interface integrated-Service-Engine 1/0

!

interface Integrated-Service-Engine1/0
ip address 1.1.1.1 255.255.255.0
service-module ip address 1.1.1.9 255.255.255.0
service-module ip default-gateway 1.1.1.1
no keepalive
end

router#service-module integrated-Service-Engine 1/0 session
Trying 1.1.1.1, 2066 ... Open

ServicesEngine boot-loader>

ServicesEngine boot-loader> show config
IP addr:                10.1.1.9
Netmask:                255.255.255.0
TFTP server :           10.1.1.1
GW IP addr:             10.1.1.1
eth int:                internal
Default boot:           chainloader
Bootloader Version:     2.1.15.22
Bootloader Name:        WAAS_BOOTLOADER
Default Helper-file:    /waas-4.4.7.4-k9.sysimg
Default bootloader:     secondary
External i/f media:     copper

B.R.

[Nicolas Fournier]

Hi,

The procedure should be the same for the module, it is just that we stopped mentioning them in the latest WAAS doc.

Have a look at the documentatoon for 4.0:

http://www.cisco.com/en/US/docs/app_ntwk_services/waas/waas/v407/configuration/guide/maint.html#wp1105207

Search fro NME-WAE in this page and you'll find the detailed step for the module.

Regards,

Nicolas

[jmfranco]

Hi Nicolas, thanks for your response. Your suggested procedure is fine for NME-WAE. However I think our NME-WAE is crashing before to reach BOOT-PHASE3 as described in procedure, so I don´t know if i have to go ahead with sysimg images. Anyway, I have been testing with diferent sysimg versions, and I always obtain the same result: I obtain "corrupted netboot image" error

ServicesEngine boot-loader> show config|

IP addr:                1.1.1.9

Netmask:                255.255.255.0

TFTP server :           1.1.1.1

GW IP addr:             1.1.1.1

eth int:                external

Default boot:           chainloader

Bootloader Version:     2.1.15.22

Bootloader Name:        WAAS_BOOTLOADER

Default Helper-file:    waas-4.4.5d.5-k9.sysimg

Default bootloader:     secondary

External i/f media:     copper

ServicesEngine boot-loader> boot helper/

Invalid signature hdr

imgaddr[0]: 0x67, g

imgaddr[1]: 0x31, 1

imgaddr[2]: 0x64, d

imgaddr[3]: 0x31, 1

imgaddr[4]: 0x78, x

imgaddr[5]: 0x0,

imgaddr[6]: 0x0,

imgaddr[7]: 0x0,

imgaddr[8]: 0x0,

imgaddr[9]: 0x0,

imgaddr[10]: 0x0,

imgaddr[11]: 0x0,

imgaddr[12]: 0x0,

imgaddr[13]: 0x0,

imgaddr[14]: 0x0,

imgaddr[15]: 0x0,

imgaddr[16]: 0x2, 

imgaddr[17]: 0x0,

imgaddr[18]: 0x0,

imgaddr[19]: 0x0,

imgaddr[20]: 0x64, d

imgaddr[21]: 0x2>, .

imgaddr[22]: 0x6>, n

imgaddr[23]: 0x0,

imgaddr[24]: 0x??????98, ˜

Corrupted netboot image  detected ServicesEngine boot-loader> boot helper/
Invalid signature hdr
imgaddr[0]: 0x67, g
imgaddr[1]: 0x31, 1
imgaddr[2]: 0x64, d
imgaddr[3]: 0x31, 1
imgaddr[4]: 0x78, x
imgaddr[5]: 0x0,
imgaddr[6]: 0x0,
imgaddr[7]: 0x0,
imgaddr[8]: 0x0,
imgaddr[9]: 0x0,
imgaddr[10]: 0x0,
imgaddr[11]: 0x0,
imgaddr[12]: 0x0,
imgaddr[13]: 0x0,
imgaddr[14]: 0x0,
imgaddr[15]: 0x0,
imgaddr[16]: 0x2, 
imgaddr[17]: 0x0,
imgaddr[18]: 0x0,
imgaddr[19]: 0x0,
imgaddr[20]: 0x64, d
imgaddr[21]: 0x2>, .
imgaddr[22]: 0x6>, n
imgaddr[23]: 0x0,
imgaddr[24]: 0x??????98, ˜
Corrupted netboot image  detected

any idea?

[Nicolas Fournier · Accepted solution]

Hi,

I checked in our database for this "Corrupted netboot image detected" message and each of the ten to twenty cases I've found were solved by a hardware replacement.

The last things I could think of would be to use an external tftp server to make sure the issue has nothing to do with the router serving the file and to make sure that the file on the server has the same md5 as the one on CCO,

If it still doesn't work, RMA would be the last available option.

Regards,

NIcolas

[jmfranco]

Hi Nicolas. Thanks a lot for your help. As you can see, I was trying from external tftp server, but I have tested from router where NME is inserted too, configured as tftp server, and I obtain the same result.

I think I´ll go ahead with hardware replacement.

B.R.