IP130 Password Recovery 1

You need to boot system into single user mode. To do this reboot the machine and when you see the line " boot: " you must enter "-s" . (you have about 10 seconds)

After it boots, it will ask you "Enter pathname of shell or RETURN for sh:", press Enter key.

Enter "/etc/overpw" in the # prompt. It will ask if you want continue, type "y".

In IPSO 3.4 and above, /etc/overpw will ask you to set a password. The admin password defaults to no password in earlier versions of IPSO.

Reboot.

Login as admin. If a password is required, you will be asked for one.


Use the dbpasswd command to set a new password:

nokia[admin]# dbpasswd admin newpassword ""

(Note that the "" is necessary to specify (NULL) as the old password.)

Then, save this new password to the configuration file so that you can log into Network Voyager:

nokia[admin]# dbset :save


Akiwondo (MCSE, CCSE)

Hi All,

this is what I get,

1 Bootmgr
2 IPSO

Default: 1

Starting bootmgr
Loading boot manager..
Boot manager loaded.
Entering autoboot mode.
Type any character to enter command mode.
BOOTMGR[3]> help
boot Boot/Load and Run kernel or executable
install Proceed to install new IPSO image
halt Halt the system
setenv Set Environment Variable
unsetenv Clear Environment Variable
printenv Print Environment Variables
passwd Set password for system
ls List Directory
sysinfo Display System Information
unsetalias Clear System alias
setalias Set System alias
showalias Show System aliases
set-defaults Set bootmgr defaults
netconfig Configure network boot parameters
BOOTMGR[4]> ls
IPSO-3.7-BUILD026-08.19.2003-184000-1214
current
BOOTMGR[5]> set-defaults
BOOTMGR[6]> boot
Booting /dev/wd0f:/image/IPSO-3.7-BUILD026-08.19.2003-184000-1214/kernel
[kernel] symtab a06a6000, sym_start a06a6004, sym_end a06e7278
[kernel] sym_size 56df, str_size 5f5e4
[ preserving 0xa085c bytes of kernel symbol table ]
Copyright (c) 1982, 1986, 1989, 1991, 1993
The Regents of the University of California. All rights reserved.

Resizing packet buffers: mbufs 15360 clusters 14000
releng 1214 08.19.2003-184000
CPU: 300-MHz Pentium (586-class CPU)
real memory = 268435456 (256M bytes)
avail memory = 251539456 (239M bytes)
mediagx0 <Cyrix GXLV CPU with PCI/Memory Controller> rev 0 on pci0:0:0
mediagx1 <Cyrix CS5530 PCI to ISA bridge> rev 48 on pci0:18:0
mediagx2 <Cyrix CS5530 SMI> rev 0 on pci0:18:1
mediagx3 <Cyrix CS5530 IDE> rev 0 on pci0:18:2
cyrix 5530
Probing for devices on the ISA bus:
sio0 at 0x3f8-0x3ff irq 4 on isa
<5>sio0: type 16550A
sio1 at 0x2f8-0x2ff irq 3 on isa
<5>sio1: type 16550A
wdc0 at 0x1f0-0x1f7 irq 14 on isa
Setting using 0x1000
wd0: mw=0x2, pio=0x4, pcirev=0x0, udma=0x2
wdc0: unit 0 (wd0): <TOSHIBA MK2018GAS>, LBA, DMA
wd0: 20003MB (39070080 sectors), LBA geometry: 2432 cyls, 255 heads, 63 S/T
wd0: Physical geometry: 16383 cyls, 16 heads, 63 S/T
npx0 on motherboard
npx0: INT 16 interface
superio0 at 0x0 on isa
mediagx4 <Cyrix CS5530 audio> rev 0 on pci0:18:3
fxp0 <Intel EtherExpress Pro 10/100B Ethernet> rev 16 int a irq 6 slot 1
netlog:eth-s1p1 .. Ethernet address 0:a0:8e:21:dd:22
fxp1 <Intel EtherExpress Pro 10/100B Ethernet> rev 16 int a irq 10 slot 2
netlog:eth-s2p1 .. Ethernet address 0:a0:8e:21:dd:23
fxp2 <Intel EtherExpress Pro 10/100B Ethernet> rev 16 int a irq 11 slot 3
netlog:eth-s3p1 .. Ethernet address 0:a0:8e:21:dd:24
ubsec0 <Broadcom 5802 Encryption Accelerator> rev 1 int a irq 12 on pci0:13:0
sizeof hwa_dev_t = 12
changing root device to wd0f
swapon: adding /dev/wd0b as swap device
Automatic reboot in progress...
/dev/rwd0f: clean, 461247 free (831 frags, 57552 blocks, 0.1% fragmentation)
/dev/rwd0a: CLEAN FLAG NOT SET IN SUPERBLOCK (FIXED)
/dev/rwd0a: 4 files, 28 used, 37528 free (16 frags, 4689 blocks, 0.0% fragmentation)
/dev/rwd0d: CLEAN FLAG NOT SET IN SUPERBLOCK (FIXED)
/dev/rwd0d: 822 files, 884943 used, 13847992 free (816 frags, 1730897 blocks, 0.0% f)/dev/rwd0e: CLEAN FLAG NOT SET IN SUPERBLOCK (FIXED)
/dev/rwd0e: 4755 files, 625100 used, 1936096 free (2272 frags, 241728 blocks, 0.1% f)Apr 22 13:21:39 xpand[28]: xpand will perform upgrade if necessary

clearing /tmp
checking for core dump...savecore: no core dump
recording kernel -c changes
starting system daemons: syslogd done.
Apr 22 13:21:42 IZC1S100 [LOG_NOTICE] kernel: sio0: type 16550A
Apr 22 13:21:42 IZC1S100 [LOG_NOTICE] kernel: sio1: type 16550A
ifmnetlog:eth-s3p1 .. enabling 10baseT/UTP port in half duplex mode
netlog:eth-s2p1 .. enabling 100baseTX/UTP port in full duplex mode
netlog:eth-s1p1 .. enabling 100baseTX/UTP port in full duplex mode
done.
Apr 22 13:21:45 IZC1S100 [LOG_INFO] kernel: netlog:eth-s3p1 .. enabling 10baseT/UTP eApr 22 13:21:45 IZC1S100 [LOG_INFO] kernel: netlog:eth-s2p1 .. enabling 100baseTX/UTeApr 22 13:21:45 IZC1S100 [LOG_INFO] kernel: netlog:eth-s1p1 .. enabling 100baseTX/UTefw driver loadable interface called.
FW-1: 2 interfaces installed
Generating config files for IZC1S100: ipsrd hosts password group resolver snmp inetd.Fri Apr 22 13:22:01 JST 2005
Apr 22 13:22:02 IZC1S100 [LOG_ERR] xntpd[222]: sendto(211.19.45.231): Can't assign rs
IPSO (IZC1S100) (ttyd0)

login: Informatory: the current VPN-1 & FireWall-1 license allows only 100 internal .If this is different from the license you intended to purchase, ensure that you have.See for troubleshooting.
Informatory: the current VPN-1 & FireWall-1 license allows only 100 internal hosts.
If this is different from the license you intended to purchase, ensure that you have.See for troubleshooting.
vpn1 driver loadable interface called.
VPN-1: Cryptographic algorithm tests passed successfully
VPN-1: connected to FW-1


IPSO (IZC1S100) (ttyd0)

login: admin
Password:
Apr 22 13:23:32 IZC1S100 [LOG_NOTICE] login: authentication failure; root(uid=0) -> e

So, may I ask, what is the default login/password.? Cheers.

Mark Sargent.

Hi All,

hold the forte..I figured it out..needed to try IPSO where I would then get the boot: prompt. Cheers.

Mark Sargent.

Hi All,

ok, spoke too soon. I get this far,

Terminal type? dbpasswd admin admin "status"
tset: terminal type dbpasswd admin admin "status" is unknown
Terminal type?

I logged in as admin/status, so, status is the old password. What am I not getting here..? Cheers.

Mark Sargent.

Hi All,

ok, I had to type vt100 to keep moving.

Set the new passwd, and saved, but, after rebooting, it still requires the previous passwd even after I had changed it.

Terminal type? vt100
IZC1S100[admin]# dbpasswd admin admin status
err: (null) return: USM keys for SNMP not created for user 'admin'. Password must bed

IZC1S100[admin]# dbset :save
IZC1S100[admin]# reboot

P.S. Does this forum have an edit function? Would save me having to re-post every time.

OK, quick HOWTO for Bootmanager based systems:

1. Power the machine on and wait for the system to start to boot. If you get a menu choice, then hit "1" to start BootManager.

2. When BootManager starts to boot, be ready. Once you see the line:
Type any character to enter command mode.
Hit a key - I prefer RETURN, but it doesn't matter. You only get about 3-4 secs to do this before the system continues to boot, so be sharp. If You see the system star to continue booting, turn it off and start again.

3. At the resulting BOOTMGRx> prompt you need to kick the boot off into single user mode using the "boot -s" command:
BOOTMGR1> boot -s

4. Once the system gets to single user mode, you'll get the prompt:
"Enter pathname of shell or RETURN for sh:"
Just hit the RETURN key again to get a prompt.

5. At the unix shell prompt, just run the overpw tool to fix the password to a known state by typing:
# /etc/overpw

6. Once you have reset the password, you need to complete the boot into normal operation before you can save the changed passwords properly. To complete the boot, type CTRL-D to exit the single user shell.

7. Once the system finishes booting fully, you can log in to the admin account with your new password. Once in, use Voyager to SAVE the database which will include the changed password. Alternatively you can use the command line and issue a "dbset :save"

I think that covers it - mostly as akiwondo posted earlier.








========================================
Find out about what I do for a living at
========================================

Hi All,

yep, that's great. I did all those steps. I was saying that it ain't saving, because, when booting up normally, after all the changes etc, the new pasword is not saved. Not too sure how else to explain it. Cheers.

Mark Sargent.