Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations strongm on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

Nokia IP330 Console Boot problem

Status
Not open for further replies.

jamesworthy88

IS-IT--Management
May 4, 2004
24
US
I was recently given a IP330 to configure as a backup firewall. From the console during the boot process, I can choose 1 or 2 to get to go to BootMgr or IPSO. However, once I get to boot prompt in the bootmgr or the login prompt in IPSO, the device is locked up. Upon multiple reboots, I was able to determine I can quickly type a short command BEFORE I get to the bootmgr prompt and it will accept it but once the prompt displays in the terminal window the device is locked. I have no access via Voyager so I'm at a loss as to what to try and do to resolve. I was using SecureCRT with 9600,8,N,1, and no flow control with the factory cable so it isn't a cable/terminal software problem. (I did try waiting for a minute before conecting the serial cable upon restart) Can I put the drive in my linux box, mount the drive, and copy over a new bootmgr or ipso image? There is nothing on the device I need to keep so a complete reinstall is fine.

Here is what I captured from a boot to IPSO and the settings when I was able to enter the printenv command befor getting to the bootmgr prompt.


>> IPSO boot
Usage: [[wd(0,f)]/kernel][-abcCdhrsv]
Boot:wd0f /kernel
Booting wd(0,f)/image/IPSO-3.4.1-FCS10-12.12.2001-210900-910/kernel @ 0x100000
text=0x237000 data=0x51000 bss=0x83c7c symbols=[+0x384+0x4+0x36e58+0x4+0x4d6e5]
total=0x490545 entry point=0x100000
[kernel] symtab c040c000, sym_start c040c004, sym_end c0442e5c
[kernel] sym_size 4932, str_size 4d6ec
[ preserving 0x84548 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 7680
releng 910 12.12.2001-210900
CPU: 401-MHz K6-2 (586-class CPU)
real memory = 268435456 (256M bytes)
avail memory = 254283776 (242M bytes)
chip0 <Intel 82439TX (MTXC) System Controller> rev 1 on pci0:0:0
piix0 <Intel 82371AB (PIIX4) PCI to ISA bridge> rev 2 on pci0:7:0
piix1 <Intel 82371AB (PIIX4) PCI to ISA bridge Function> rev 1 on pci0:7:1
Probing for devices on the ISA bus:
sio0: interrupt test 0 failed
sio0 at 0x3f8-0x3ff irq 4 on isa
<5>sio0: type 16550A
wdc0 at 0x1f0-0x1f7 irq 14 on isa
wdc0: unit 0 (wd0): <IC35L020AVER07-0>, LBA, DMA
wd0: 20576MB (40188960 sectors), LBA geometry: 2501 cyls, 255 heads, 63 S/T
wd0: Physical geometry: 16383 cyls, 16 heads, 63 S/T
npx0 on motherboard
npx0: INT 16 interface
ultraio0 at 0x0 on isa
piix2 <Intel 82371AB (PIIX4) PCI to ISA bridge Function> rev 1 on pci0:7:2
piix3 <Intel 82371AB (PIIX4) PCI to ISA bridge Function> rev 2 on pci0:7:3
fxp0 <Intel EtherExpress Pro 10/100B Ethernet> rev 5 int a irq 10 slot 3
netlog:eth-s3p1 .. Ethernet address 0:a0:8e:1f:42:18
fxp1 <Intel EtherExpress Pro 10/100B Ethernet> rev 5 int a irq 11 slot 4
netlog:eth-s4p1 .. Ethernet address 0:a0:8e:1f:42:1c
fxp2 <Intel EtherExpress Pro 10/100B Ethernet> rev 5 int a irq 12 slot 5
netlog:eth-s5p1 .. Ethernet address 0:a0:8e:1f:42:20
changing root device to wd0f
Bootmgr version is older than running kernel
Current:
Latest : Bootmgr Revision: 3.3,base kernel=3.4.1-FCS10 12.12.2001-210900
You may want to upgrade your bootmgr using /etc/upgrade_bootmgr.
swapon: adding /dev/wd0b as swap device
Automatic reboot in progress...
/dev/rwd0f: clean, 136997 free (1381 frags, 16952 blocks, 0.3% fragmentation)
/dev/rwd0a: CLEAN FLAG NOT SET IN SUPERBLOCK (FIXED)
/dev/rwd0a: 4 files, 17 used, 33354 free (18 frags, 4167 blocks, 0.1% fragmentation)
/dev/rwd0d: UNREF FILE I=84484 OWNER=0 MODE=100644
/dev/rwd0d: SIZE=0 MTIME=Sep 16 23:22 2005 (CLEARED)
/dev/rwd0d: FREE BLK COUNT(S) WRONG IN SUPERBLK (SALVAGED)
/dev/rwd0d: BLK(S) MISSING INnetlog:eth-s5p1 .. enabling 100baseTX/UTP port in half duplex mode
BIT MAPS (SALVAnetlog:eth-s5p1 .. enabling 100baseTX/UTP port in full duplex mode
GED)
/dev/rwd0d: SUMMARY INFORMATION BAD (SALVAGED)
/dev/rwd0d: CLEAN FLAG NOT SET IN SUPERBLOCK (FIXED)
/dev/rwd0d: 720 files, 75590 used, 3492069 free (1101 frags, 436371 blocks, 0.0% fragmentation)
/dev/rwd0e: CLEAN FLAG NOT SET IN SUPERBLOCK (FIXED)
/dev/rwd0e: 2080 files, 424242 used, 238485 free (693 frags, 29724 blocks, 0.1% fragmentation)
Sep 18 10:59:25 xpand[28]: xpand will perform upgrade if necessary

clearluna0 <PCI LunaVPN Token> rev 1 int a irq 12 slot 1
luna: Chrysalis-ITS LunaVPN PCI driver version 4.27
luna: _get_property: (user) 'max_logs=2000'
luna: _temp_create: allocated 524288 bytes at 0xc50ec000
luna0: _get_property: (user) 'max_device_errors=0'
luna0: _map_regs_and_sram: this board uses I/O space regs: NOT HOT-SWAPPABLE!
luna: _rq_grow_freelist: allocating 62KB
ing /tmp
checking for core dump...savecore: no core dump
recording kernel -c changes
starting system daemons: syslogd done.
Sep 18 10:59:27 gimnptbeach-nk [LOG_NOTICE] kernel: sio0: type 16550A
Sep 18 1FW1 driver loadable interface called.
0:59:27 gimnptbeach-nk [LOG_WARNING] kernel: BooFW-1: 2 interfaces installed
tmgr version is older than running kernel
Sep 18 10:59:27 gimnptbeach-nk [LOG_WARNING] kernel: Current:
Sep 18 10:59:27 gimnptbeach-nk [LOG_WARNING] kernel: Latest : Bootmgr Revision: 3.3,base kernel=3.4.1-FCS10 12.12.2001-210900
Sep 18 10:59:27 gimnptbeach-nk [LOG_WARNING] kernel: You may want to upgrade your bootmgr using /etc/upgrade_bootmgr.
ifmSep 18 10:59:27 gimnptbeach-nk [LOG_INFO] kernel: netlog:eth-s5p1 .. enabling 100baseTX/UTP port in half duplex mode
done.
Sep 18 10:59:27 gimnptbeach-nk [LOG_INFO] kernel: netlog:eth-s5p1 .. enabling 100baseTX/UTP port in full duplex mode
Generating config files for gimnptbeach-nk: ipsrd hosts password group resolver snmp inetd ttys tz ntp ssmtp skey arp ndp aggrclass acl ddr ef syslog autosupport httpd lynx modem Sep 18 10:59:31 gimnptbeach-nk [LOG_INFO] kernel: luna: Chrysalis-ITS LunaVPN PCI driver version 4.27
Sep 18 10:59:31 gimnptbeach-nk [LOG_INFO] kernel: luna: _get_property: (user) 'max_logs=2000'
Sep 18 10:59:31 gimnptbeach-nk [LOG_INFO] kernel: luna: _temp_create: allocated 524288 bytes at 0xc50ec000
Sep 1luna0: _do_reset: elapsed = 1000 msec
8 10:59:31 gimnptbeach-nk [LOG_IFW-1: Start using VPN-1 Accelerator Card
NFO] kernel: luna0: _get_property: (user) 'max_device_errors=0'
Sep 18 10:59:31 gimnptbeach-nk [LOG_WARNING] kernel: luna0: _map_regs_and_sram: this board uses I/O space regs: NOT HOT-SWAPPABLE!
cron Sep 18 10:59:31 gimnptbeach-nk [LOG_INFO] kernel: luna: _rq_grow_freelist: allocating 62KB
ipsec fmd AAA ssh done.
Sun Sep 18 10:59:32 PDT 2005
Sep 18 11:00:48 gimnptbeach-nk [LOG_INFO] kernel: luna0: _do_reset: elapsed =jJAM=??¥µ¹ÿptbeach-nk) (ttyd0)

login:

==========================================
==========================================

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[1]> printenv

Bootmgr Revision: 3.3,base kernel=3.4.1-FCS5 08.18.2001-053000
autoboot: YES
testboot: NO
bootwait: 3
boot-file: /image/current/kernel
boot-flags:
boot-device: wd0
vendor: Nokia
model: IP
BOOTMGR[2]> BOOTMGR[3]>

========================================
========================================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[1]> ls /image

IPSO-3.4-FCS4A-06.26.2001-235900-767 IPSO-3.4.1-FCS5-08.18.2001-053000-826
IPSO-3.4.1-FCS10-12.12.2001-210900-910 current
BOOTMGR[2]> BOOTMGR[3]>



 
James

You're running the box with a lower rev of the bootmgr than the default image. This invariably causes problems on IPSO because you end up loading different driver versions for the hardware and the box panics. You have a few options:

1: RMA the sucker if you've got Nokia support.
2: As you say, get a known-good disk image and dd it on to yours.
3: Accept that it's had it and buy a refurb unit - seem to sell 'em cheap.
3: Ditch it and put SPLAT on to any old Intel box to replace it.
4: Buy a new IP260.

HTH
 
Yep, you confirmed exactly what I thought after researching nokia support. Appreciate you mentioning the other options, some I hadn't considered. If I try to salvage the existing drive anyone have details on how to dd the image over?

JW88
 
I personally use Acronis to image the disk, and copy to a new disk, but you can use
dd if=/dev/wd0 of=/dev/wd1 bs=1024k
which works just as well.

Stu
 
I used dd on a linux box to copy a second ip330 hd's image onto the existing hd but had the same issue. Looks to boot properly but I can't type anything at the command prompt. I also swapped the hard drive out and placed it into a second IP330 and the hd looked to be fine. Anyone have other ideas on what to try? I've swapped cables and used different terminal software. Nothing helps.
 
you may be able to boot into single user mode and manually upgrade the boot manager?
 
On a Nokai IP330 the bootmgr is on the harddrive so using the dd command fixed that. I now also have access via voyager (didn't realize that worked right away) but I still can't type when connecting via the console. I haven't tried telnet yet but if it works, are there any commands I can run to diagnose the console problem?
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top