CE 565 will not boot

matthoulden · ‎12-02-2004

Hi,

When I start up my content Engine the system does all its usual checks and starts the boot process. I then get to the ACNS startup and just hangs. See output below:

Application and Content Networking System Software (ACNS)

Application and Content Networking System Software Release 5.1.5 (build b2 Mar 3

0 2004)

INIT: Entering runlevel: 3

Nodemgr started!

Dec 2 16:50:15 (none) %CE-SYS-3-900000: ..MP-BIOS bug: 8254 timer not connected

to IO-APIC

Dec 2 16:50:15 (none) %CE-SYS-3-900000: wccp: v1.00 (20000327), debug=0

check-parameter-packet-v2: short read on /tmp/127.sect: Success

BOOT-100: no v2 pp, continuing normal booting

/ruby/bin/apply-parameter-packet-v4: short read on /tmp/127.sect: Success.

BOOT-100: no v4 pp, continuing normal booting

From this point it just hangs

Thanks in advance

Matt.

mchin345 · ‎12-08-2004

I think you need to connect to the Content Engine via the serial port using a DB9 connector and a rollover cable, then connect to a PC via console port. On the HyperTerminal settings use the default values (bits per second 9600, data bits 8, parity none, stop bits 1, flow control none).

gid · ‎12-19-2004

I'm not sure what the problem might be, exactly, but my guess is it's a ddts that's been fixed. If you're still having this problem, I would suggest getting a newer 5.1.x or 5.2.x flash image file (ACNS-.sysimg from the sw center) and installing that. You can install it from the rescue image by interrupting the bootloader before it loads the regular image (type "***" at the console when prompted). Do a search in the ACNS documentation for "rescue image" for the exact procedure. The procedure will ask you to enter CE IP, netmask, interface to use, default gateway, an address for an FTP server to get the *.sysimg file from, and FTP server username/password.

matthoulden · ‎12-20-2004

Thanks for the advice but with futher investigation I have found that the content engine has a faulty flash disk.

I have spoken to cisco and they have agreed to replace the content engine with a new one.