×

Warning message

  • Cisco Support Forums is in Read Only mode while the site is being migrated.
  • Cisco Support Forums is in Read Only mode while the site is being migrated.

AIM-CUE module won't boot

Unanswered Question
Mar 31st, 2010
User Badges:

Hi all,


I've bought an AIM-CUE to play around with Unity Express but I'm having some significant issues getting it going. When the module is booted it seems to constantly power cycle itself like so:


Initializing memory.  Please wait. ... 256 MB SDRAM detected
BIOS Version: Cisco SE-AIM 01.02
BIOS Build date: 08/14/03
System Now Booting ...[BOOT-ASM]
7

Please enter '***' to change boot configuration:  Filesystem type is reiserfs,
partition type 0x83
kf: a1 : (hd0,0)/bzImage root=/dev/hda1 ro plat=aim
kf: a2 : (hd0,0)/bzImage root=/dev/hda1 ro plat=aim
in grub_open: (hd0,0)/bzImage root=/dev/hda1 ro plat=aim
in grub_open1: /bzImage root=/dev/hda1 ro plat=aim
in grub_open2: /bzImage root=/dev/hda1 ro plat=aim
in grub_open3: /bzImage root=/dev/hda1 ro plat=aim 1
in grub_open4: /bzImage root=/dev/hda1 ro plat=aim
kernel_func: kt: 0
in boot func: kt: 0ÿ

However it then keeps repeating this and never (seems) to go any further. At first I thought it was just a corrupt software image so I tried to load up 7.2.1 (latest for this module) using boot helper and I'm able to get into the bootloader and make my configuration options:


Please enter '***' to change boot configuration: ***Probing...[EEPRO100]Found I
ntel EtherExpressPro100 82559ER at 0x00000000 ROM address 0x003FC000
Ethernet addr: 00:04:9A:49:3C:70
equalizer val: 16


ServicesEngine Bootloader Version : 1.0.17


ServicesEngine boot-loader>


but after issuing the boot helper and the AIM-CUE sucessfully downloading the image I then get this:


ServicesEngine boot-loader> boot helper
Probing...[EEPRO100]Found Intel EtherExpressPro100 82559ER at 0x00000000 ROM ad
dress 0x003FC000
Ethernet addr: 00:04:9A:49:3C:70
equalizer val: 16
Me: 192.168.1.2, Server: 10.0.80.3, Gateway: 192.168.1.1
Loading cue-installer.aim.7.2.1
Dbg: Final image size: 11713916
Debug: bl_sz: 115296
reading key: 0
reading key: 1
reading key: 2
reading key: 3
reading key: 4
reading key: 5
in verifysignature_md5, MD5 hash generated now, str format:hexmd5:ba556d2ce37ea
f6f829259196cd40ea5
Verifying signature now...
calling RSA decrypt now

mem ptr: 0 704 832 968 1040 1172 1184 1196 1208 1220 1228 1244 1268 1284 1300 1
316 1332 1344 1360 1384 1400 1664 1804 2080 2224 2364 2880 3396 3660 3924 4188
RSA decrypt returned:-1
verifysignature_md5, Orig MD5 hash generated during encryption:¼zÌzi|T{¬Å¼²|
calling RSA decrypt now

mem ptr: 0 704 832 968 1040 1172 1184 1196 1208 1220 1228 1244 1268 1284 1300 1
316 1332 1344 1360 1384 1400 1664 1804 2080 2224 2364 2880 3396 3660 3924 4188
RSA decrypt returned:-1
verifysignature_md5, Orig MD5 hash generated during encryption:¼zÌzi|T{¬Å¼²|
calling RSA decrypt now

mem ptr: 0 704 832 968 1040 1172 1184 1196 1208 1220 1228 1244 1268 1284 1300 1
316 1332 1344 1360 1384 1400 1664 1804 2080 2224 2364 2880 3396 3660 3924 4188
RSA decrypt returned:-1
verifysignature_md5, Orig MD5 hash generated during encryption:¼zÌzi|T{¬Å¼²|
calling RSA decrypt now

mem ptr: 0 704 832 968 1040 1172 1184 1196 1208 1220 1228 1240 1260 1276 1288 1
304 1320 1332 1348 1368 1380 1644 1784 2060 2204 2344 2860 3376 3640 3904 4168
RSA decrypt returned:-1
verifysignature_md5, Orig MD5 hash generated during encryption:¼zÌzi|T{¬Å¼²|
calling RSA decrypt now

mem ptr: 0 704 832 968 1040 1172 1184 1196 1208 1220 1228 1244 1268 1284 1300 1
316 1332 1344 1360 1384 1400 1664 1804 2080 2224 2364 2880 3396 3660 3924 4188
RSA decrypt returned:-1
verifysignature_md5, Orig MD5 hash generated during encryption:¼zÌzi|T{¬Å¼²|
calling RSA decrypt now

mem ptr: 0 704 832 968 1040 1172 1184 1196 1208 1220 1228 1244 1268 1284 1300 1
316 1332 1344 1360 1384 1400 1664 1804 2080 2224 2364 2880 3396 3660 3924 4188
RSA decrypt returned:-1
verifysignature_md5, Orig MD5 hash generated during encryption:¼zÌzi|T{¬Å¼²|
signatures do not match...
Invalid signature !!ÿ

Initializing memory.  Please wait. ...


Unfortunately the module then goes back to restarting constantly. Just incase I was unlucky enough to get a faulty image I tried an older one and got the same results. I'm unfortunately at a bit of a loss on what to do next. Could it be a hardware issue?


Any ideas?

  • 1
  • 2
  • 3
  • 4
  • 5
Overall Rating: 0 (0 ratings)
Loading.
paolo bevilacqua Thu, 04/01/2010 - 12:19
User Badges:
  • Super Gold, 25000 points or more
  • Hall of Fame,

    Founding Member

Is that a 1-GB module ?

All requisites seems to be good. May be bad memory or faulty HW.

Actions

This Discussion

Related Content