Cisco Support Community
cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
Community Member

How to break password for Content Engine 507

Version :

Cisco Content Delivery Network V3-0-2-rc10

Kernel 2.2.16-3 on an i686

BIOS Version: CE500 01.11

BIOS Build date: 07/27/00

Symbios, Inc. SDMS (TM) V4.0 PCI SCSI BIOS, PCI Rev. 2.0, 2.1

Copyright 1995, 1998 Symbios, Inc.

PCI-4.11.00

Press Ctrl-C to start Symbios Configuration Utility...

When I Key in Ctrl-C at the above prompt it does not work.

7 REPLIES
Anonymous
N/A

Re: How to break password for Content Engine 507

Note: Your configuration is lost after perfoming this password recovery. It is not possible to keep your configuration when recovering a lost administrative password.

Step-by-Step Procedure

Establish a console connection to the Cache Engine and reload the device or type reload or reboot at the command line. While the Cache Engine is rebooting, press any key to interrupt the low level configuration countdown.

At the prompt, type "p" to display the configuration menu.

At the prompt, type "c" to enter the configuration mode. Use:

a period (.) to clear a field

a dash (-) to go to the previous field

the Enter key to go to the next field

^D to quit

Press Enter nine times until the field flags are displayed.

Enter the value 0x4000 at the prompt and press Enter. This flag will allow the cache engine to bypass the nonvolatile RAM (NVRAM) configuration.

Type @ to reboot the Cache Engine. At this point, the Cache Engine is not password-protected.

To configure a new password, type configure terminal to enter the configuration mode.

Type user modify username admin password cisco to make "cisco" the new password.

Type write or copy running startup to commit the changes.

Reload the Cache Engine.

To set the flags back to their original value of 0x0, repeat steps 3 and 4 and enter 0x0 in the field flags.

Community Member

Re: How to break password for Content Engine 507

Thanks for you info. but upon booting, i tried pressing any key and it still won't work at all. seems like the keyboard works only after linux loader has taken place. Anything that i can do ? Thanks...

Community Member

Re: How to break password for Content Engine 507

Please following the booting process until a point to ask for bootflag. It will wait for a few seconds and just continue booting if nothing entered. There is one bootflag that allows you to disable password. After bootup, you should be able to login with id "admin" without password. You can perform this procedure through console line.

Community Member

Re: How to break password for Content Engine 507

I am having a simmilar problem, Currently, I have 2 Cisco Cache Engine model 590's. One of them runs some form of Linux and the other is running a very standard IOS. The problem I am having is that, the details for reseting the password on the Cisco CE that runs linux, are very different from what appears on the console, I have already sucessfully reset the username and password on the Cisco CE that is running IOS but the one that is obviously loading linux does not give a prompt to break out of the loader and specify the same info as the IOS one.

I just want to know how to reset the root password for this device, I get a login prompt for the linux os on this device however no one knows what the password is. Also everywhere I ask this question, I get dismissed as a heritic because people believe that I am trying to "install" linux on this device, when all I really want to do is "log in" to the current installation of linux.

The following is a complete Dump of the loading process that I am describing:

BIOS Version: CE500 01.11

BIOS Build date: 08/15/00

Symbios, Inc. SDMS (TM) V4.0 PCI SCSI BIOS, PCI Rev. 2.0, 2.1

Copyright 1995, 1998 Symbios, Inc.

PCI-4.11.00

Press Ctrl-C to start Symbios Configuration Utility...

Searching for device at HBA 0, ID 0, LUN 0 Synchronous negotiation...Searching for device at HBA 0, ID 0, LUN 1 Searching for device at HBA 0, ID 0, LUN 2 Searching for device at HBA 0, ID 0, LUN 3 Searching for device at HBA 0, ID 0, LUN 4 Searching for device at HBA 0, ID 0, LUN 5 Searching for device at HBA 0, ID 0, LUN 6 Searching for device at HBA 0, ID 0, LUN 7

Searching for device at HBA 0, ID 1, LUN 0

Synchronous negotiation...Searching for device at HBA 0, ID 1, LUN 1

Searching for device at HBA 0, ID 1, LUN 2

Searching for device at HBA 0, ID 1, LUN 3 Searching for device at HBA 0, ID 1, LUN 4 Searching for device at HBA 0, ID 1, LUN 5 Searching for device at HBA 0, ID 1, LUN 6 Searching for device at HBA 0, ID 1, LUN 7 Searching for device at HBA 0, ID 2, LU

N 0 Searching for device at HBA 0, ID 3, LUN 0 Searching for device at HBA 0, ID 4, LUN 0

Searching for device at HBA 0, ID 5, LUN 0

Searching for device at HBA 0, ID 6, LUN 0

Searching for device at HBA 0, ID 8, LUN 0

Searching for device at HBA 0, ID 9, LUN 0

Searching for device at HBA 0, ID 10, LUN 0

Searching for device at HBA 0, ID 11, LUN 0

Searching for device at HBA 0, ID 12, LUN 0

Searching for device at HBA 0, ID 13, LUN 0

Searching for device at HBA 0, ID 14, LUN 0 Searching for device at HBA 0, ID 15, LUN 0

HBA ID LUN VENDOR PRODUCT REV SYNC WIDE

INT13 CYL/ HD/SEC

--- -- --- -------- ---------------- ---- ---- ---- ----- ------------

0 0 0 IBM DMVS18D 0260 80.0 16 BOOT 1024/255/63

0 1 0 IBM DMVS18D 0260 80.0 16 81h 1024/255/63

0 7 0 Symbios SYM53C895 0002 80.0 16

Symbios, Inc. PCI boot ROM successfully installed!

Cisco CE Booting From Flash.

running robin2_start.S

This is cmain! You are now running C code!

build date: Fri Jul 21 18:48:00 PDT 2000

build number: 59

Directory verified ok!

phase2: examining phase3 boot-rom: 'default_bootrom'

cmain: going to jump to location PHASE3_MEM_LOCATION = 16777216

cmain: 10 code bytes: 85 -119 -27 -125 -20 32 87 86 83 -24

defphase3.c: Running third-phase bootrom code!

defphase3.c: directory is ok!

defphase3.c: db_dir_get_location("rescue") failed: -5

defphase3.c: your devimg does not seem to have a rescue image in it

defphase3.c: running default system image instead

defphase3.c: default system image is 'default_sysimg'

defphase3.c: default_sysimg: 76 sectors

defphase3.c: loaded 76 device sectors to 0x4000000!

defphase3.c: kernel checksum ok! running execute_kernel!

execute_kernel: system image header:

magic: 'g1d1x'

version: 1

bzimage_len: 902713

initrd_len: 8978308

execute_kernel: setup_len = 2560, text_len = 899648

execute_kernel: set kernel parameters:

execute_kernel: moving (setup + bootsect) = 3072 bytes to 0x90000

execute_kernel: command-line is 'root=/dev/ram ramdisk_size=100000 ramdisk_start=0

x6000000 console=ttyS0,9600n8'

execute_kernel: moving rest of kernel (899648 bytes) downwards 0x3f01000 bytes to

0x100000!

execute_kernel: adjusting initrd (8978308 bytes) upwards 32650240 bytes to 0x60000

00!

execute_kernel: calling params->run_kernel()!

run_kernel called

Linux version 2.3.36.csco (gid@vista) (gcc version egcs-2.91.66 19990314/Linux (eg

cs-1.1.2 release)) #64 SMP Fri Jul 21 18:41:27 PDT 2000

setup.c: E820 fixup: old map: 5 entries; new map: 7 entries

e820: 0009ec00 @ 00000000 (usable)

e820: 00001400 @ 0009ec00 (reserved)

e820: 0001f800 @ 000e0800 (reserved)

e820: 00e00000 @ 00100000 (usable)

e820: 00100000 @ 00f00000 (reserved)

e820: 3f000000 @ 01000000 (usable)

e820: 00100000 @ fff00000 (reserved)

Scan SMP from 78000000 for 1024 bytes.

Scan SMP from 7809fc00 for 1024 bytes.

Scan SMP from 780f0000 for 65536 bytes.

Scan SMP from 7809ec00 for 4096 bytes.

mapped APIC to ffffe000 (01000000)

On node 0 totalpages: 00040000

zone(0): 4096 pages.

zone(1): 258048 pages.

zone(2): 0 pages.

Detected 598987570 Hz processor.

Console: colour *CGA 15x25

Calibrating delay loop... 598.02 BogoMIPS

Memory: 1016920k/1048576k available (1563k kernel code, 30240k reserved, 180k data

, 404k init, 0k highmem)

Buffer-cache hash table entries: 65536 (order: 6, 262144 bytes)

Page-cache hash table entries: 262144 (order: 8, 1048576 bytes)

Pentium-III serial number disabled.

Checking 386/387 coupling... OK, FPU using exception 16 error reporting.

Checking 'hlt' instruction... OK.

POSIX conformance testing by UNIFIX

Pentium-III serial number disabled.

per-CPU timeslice cutoff: 50.08 usecs.

CPU0: Intel Pentium III (Coppermine) stepping 01

SMP motherboard not detected. Using dummy APIC emulation.

Initializing CPU#0

calibrating APIC timer ...

..... CPU clock speed is 598.9589 MHz.

..... host bus clock speed is 0.0000 MHz.

cpu: 0, clocks: 0, slice: 0, nr: 1.

CPU0<0>

Setting commenced=1, go go go

PCI: PCI BIOS revision 2.10 entry at 0xe9b9c

PCI: Using configuration type 1

PCI: Probing PCI hardware

PCI: Cannot allocate resource region 2 of device 00:0d.0

PCI: Cannot allocate resource region 2 of device 00:0e.0

PCI: Allocation of memory region 00:0d.0/2 (-1609564160 bytes) failed

PCI: Allocation of memory region 00:0e.0/2 (-1609564160 bytes) failed

Limiting direct PCI/PCI transfers.

Linux NET4.0 for Linux 2.3

Based upon Swansea University Computer Society NET3.039

skb_init: memory pools configured to steal max 444596224 bytes (424MB) for skbuff

memory

skb_init: pool locking done by local_irq_save/local_irq_restore, 4 CPUs

NET4: Unix domain sockets 1.0/SMP for Linux NET4.0.

NET4: Linux TCP/IP 1.0 for NET4.0

IP Protocols: ICMP, UDP, TCP

TCP: Hash tables configured (established 65536 bind 65536)

Starting kswapd v1.6

Serial driver version 4.91 (1999-11-17) with<4>Keyboard timeout[2]

Keyboard timeout[2]

MANY_PORTS SHARE_IRQ SERIAL_PCI PCI_IOMEM enabled

ttyS00 at 0x03f8 (irq = 4) is a 16550A

ttyS01 at 0x02f8 (irq = 3) is a 16550A

pty: 256 Unix98 ptys configured

Linux video capture interface: v1.00

RAMDISK driver initialized: 16 RAM disks of 100000K size 1024 blocksize

Uniform Multi-Platform E-IDE driver Revision: 6.21

PIIX4: IDE controller on PCI bus 00 dev 39

PIIX4: not 100% native mode: will probe irqs later

ide0: BM-DMA at 0xfc00-0xfc07, BIOS settings: hda:pio, hdb:pio

ide1: BM-DMA at 0xfc08-0xfc0f, BIOS settings: hdc:pio, hdd:pio

Floppy drive(s): fd0 is 1.44M, fd1 is 1.44M

FDC 0 is a post-1991 82077

sym53c8xx: at PCI bus 0, device 15, function 0

sym53c8xx: setting PCI_COMMAND_PARITY...(fix-up)

sym53c8xx: 53c895 detected with Symbios NVRAM

sym53c895-0: rev 0x2 on pci bus 0 device 15 function 0 irq 5

sym53c895-0: Symbios format NVRAM, ID 7, Fast-40, Parity Checking

sym53c895-0: initial SCNTL3/DMODE/DCNTL/CTEST3/4/5 = (hex) 07/4e/a0/01/00/24

sym53c895-0: final SCNTL3/DMODE/DCNTL/CTEST3/4/5 = (hex) 07/4e/80/00/08/24

sym53c895-0: on-chip RAM at 0xa0081000

sym53c895-0: resetting, command processing suspended for 2 seconds

sym53c895-0: restart (scsi reset).

sym53c895-0: enabling clock multiplier

sym53c895-0: Downloading SCSI SCRIPTS.

scsi0 : sym53c8xx - version 1.5g

scsi : 1 host.

sym53c895-0: command processing resumed

Vendor: IBM Model: DMVS18D Rev: 0260

Type: Direct-Access ANSI SCSI revision: 03

Detected scsi disk sda at scsi0, channel 0, id 0, lun 0

Vendor: IBM Model: DMVS18D Rev: 0260

Type: Direct-Access ANSI SCSI revision: 03

Detected scsi disk sdb at scsi0, channel 0, id 1, lun 0

sym53c895-0-<0,0>: tagged command queue depth set to 4

sym53c895-0-<1,0>: tagged command queue depth set to 4

scsi : detected 2 SCSI disks total.

sym53c895-0-<0,*>: WIDE SCSI (16 bit) enabled.

sym53c895-0-<0,*>: FAST-40 WIDE SCSI 80.0 MB/s (25 ns, offset 31)

SCSI device sda: hdwr sector= 512 bytes. Sectors= 35843670 [17501 MB] [17.5 GB]

sym53c895-0-<1,*>: WIDE SCSI (16 bit) enabled.

sym53c895-0-<1,*>: FAST-40 WIDE SCSI 80.0 MB/s (25 ns, offset 31)

SCSI device sdb: hdwr sector= 512 bytes. Sectors= 35843670 [17501 MB] [17.5 GB]

3c59x.c:v0.99H 11/17/98 Donald Becker http://cesdis.gsfc.nasa.gov/linux/drivers/vo

rtex.html

eepro100.c:v1.09j 7/27/99 Donald Becker http://cesdis.gsfc.nasa.gov/linux/drivers/

eepro100.html

eth0: Intel PCI EtherExpress Pro100 at 0xb8804000, 00:02:B9:45:9E:7C, IRQ 9.

Board assembly 668081-002, Physical connectors present: RJ45

Primary interface chip i82555 PHY #1.

General self-test: passed.

Serial sub-system self-test: passed.

Internal registers self-test: passed.

ROM checksum self-test: passed (0x04f4518b).

Receiver lock-up workaround activated.

eth1: Intel PCI EtherExpress Pro100 at 0xb8806000, 00:02:B9:45:9E:7D, IRQ 10.

Board assembly 668081-002, Physical connectors present: RJ45

Primary interface chip i82555 PHY #1.

General self-test: passed.

Serial sub-system self-test: passed.

Internal registers self-test: passed.

ROM checksum self-test: passed (0x04f4518b).

Receiver lock-up workaround activated.

eepro100.c:v1.09j 7/27/99 Donald Becker http://cesdis.gsfc.nasa.gov/linux/drivers/

eepro100.html

Partition check:

sda: sda1 sda2 sda3

sdb: sdb1

rd.c: rd_open... INITRD_MINOR

rd.c: rd_open... not INITRD_MINOR

RAMDISK: Compressed image found at block 100663296

Freeing initrd memory: 4194303k freed

Cisco CacheEngine Flash Driver Version 0.01

rd.c: rd_open... not INITRD_VFS: Mounted root (ext2 filesystem).

Freeing unused kernel memory: 404k freed

rd.c: FYI: sbh == rbh in ramdisk io

rd.c: FYI: sbh == rbh in ramdisk io

rd.c: FYI: sbh == rbh in ramdisk io

rd.c: FYI: sbh == rbh in ramdisk io

rd.c: FYI: sbh == rbh in ramdisk io

rd.c: FYI: sbh == rbh in ramdisk io

rd.c: FYI: sbh == rbh in ramdisk io

rd.c: FYI: sbh == rbh in ramdisk io

rd.c: FYI: sbh == rbh in ramdisk io

INIT: version 2.78 booting

Welcome to Diamond

*** THIS IS THE RESCUE/NETBOOT IMAGE!

Mounting non-disk filesystems

Set clock: Sun Sep 7 22:31:29 EDT 1980

setting $TERM to vt100

+ mke2fs /dev/ram1

mke2fs 1.18, 11-Nov-1999 for EXT2 FS 0.5b, 95/08/09

Filesystem label=

OS type: Linux

Block size=1024 (log=0)

Fragment size=1024 (log=0)

25064 inodes, 100000 blocks

5000 blocks (5.00%) reserved for the super user

First data block=1

13 block groups

8192 blocks per group, 8192 fragments per group

1928 inodes per group

Superblock backups stored on blocks:

8193, 24577, 40961, 57345, 73729

Writing inode tables: 0/13 1/13 2/13 3/13 4/13 5/13 6/13 7/13 8/13 9/13 10/13 11/

13 12/13 done

Writing superblocks and filesystem accounting information: done

+ mkdir /ram1

+ mount /dev/ram1 /ram1

+ insmod /diamond/bin/kmonte.o

+ [ ! -f /ram1/bzimage ]

+ /diamond/bin/rescue

[CE boot]: ^c

INIT: Entering runlevel: 3

/etc/rc.d/rc: /etc/rc.d/init.d/functions: No such file or directory

/etc/rc.d/rc: /sbin/runlevel: No such file or directory

BASH=/bin/bash

BASH_VERSION=1.14.7(1)

CONSOLE=/dev/console

EUID=0

HOME=/

HOSTTYPE=i386

IFS=

INIT_VERSION=sysvinit-2.78

OPTERR=1

MINOR

OPTIND=1

OSTYPE=Linux

PATH=/usr/local/sbin:/sbin:/bin:/usr/sbin:/usr/bin

PPID=1

PREVLEVEL=N

PS4=+

PWD=/

RUNLEVEL=3

SHELL=/bin/bash

SHLVL=1

TERM=linux

UID=0

_=

argv1=3

INIT: cannot execute "/sbin/update"

Cisco Cache Engine Console

(none) login:

Cisco Cache Engine Console

(none) login:

Cisco Cache Engine Console

(none) login:

Community Member

Re: How to break password for Content Engine 507

I encountered this problem as well. I performed the manula upgrade from ECDN v3.0.3rc7 to ACNS 4.2.1. After the upgrade I could log in as Admin with no problem.

TAC was no help on this, they referred me to links which contained the same "password recovery" techniques as described above. There seems to be a big gap in documentation, knowledge & support for ECDN v3.x software.

Community Member

Re: How to break password for Content Engine 507

I just ran into the exact same problem this morning, and we definitely have the LINUX-flavored CE590. The password recovery procedure does not work, so we end up with a prompt for a username and password and nothing works. Until we tried:

username: admin

password: default

And then it let us right in. Didn't see that on CCO, just happened to try it. It definitely was not in the config, so it should work on all LINUX-flavored CE590's with this problem. Good luck!

Community Member

Re: How to break password for Content Engine 507

Hello I've read your message and I'm having exactly the same problems, I dont get a username/password but a login/password instead.

I've tried admin/default but it keeps coming back with

Cisco Content Delivery Network V3-0-2-rc10

Kernel 2.2.16-3 on an i686

login: admin

Password:

___ _ ____ ___ ___

/ __| (_) / ___| / __| / _ \

| | | | \___ \ | | | | | |

| |__ | | ___) || |__ | |_| |

\___| |_| |____/ \___| \___/

Logins are disallowed.

Login incorrect

did you ever solve this problem?

Any help appreciated

Best Regards Tony Holmes CCNP

1279
Views
0
Helpful
7
Replies
CreatePlease to create content