Perhaps I am reading this wrong, but here are some hints that I have
learned over the years:
1) The bootp server must be at or above the oslevel of the restored
server:
AIX 5.3 can be used as a bootp server for AIX 5.2
AIX 5.2 cannot be used as a bootp server for AIX 5.3
This sounds like a show stopper till you are able to upgrade the NIM/bootp
server.
2) In order for sysback to restore on different hardware, the sysback
image must include all the device drivers for the restored machine. I was
sure they fixed that during the upgrade to AIX 5.3 by loading ALL device
drivers during installation. Just to be sure, you might try the following
steps:
a) install "devices.*" from the install media
b) recreate your sysback image
c) re-run your sysback restore
Question: What is the LED shown for your 505 server? The LED might also
indicate the problem.
goc <goran.k AT VIP DOT HR>
Sent by: "ADSM: Dist Stor Manager" <ADSM-L AT VM.MARIST DOT EDU>
04/03/2006 02:21 AM
Please respond to
"ADSM: Dist Stor Manager" <ADSM-L AT VM.MARIST DOT EDU>
To
ADSM-L AT VM.MARIST DOT EDU
cc
Subject
sysback help needed !
hi all,
i'm doing an test restore of rootvg from TSM via classic network boot
the communication is fine and everything seems okay except this ...
it simply hangs on following ...
-------------------------------------------------------------------------------
Type menu item number and press Enter or select Navigation key:1
IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM
IBM
IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM
IBM
IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM
IBM
IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM
IBM
IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM
IBM
IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM
IBM
IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM
IBM
IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM
IBM
IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM
IBM
IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM
IBM
IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM
IBM
IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM
IBM
IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM
IBM
IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM
IBM
IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM
IBM
IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM
IBM
IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM
IBM
IBM IBM IBM IBM IBM IBM STARTING SOFTWARE IBM IBM IBM IBM IBM
IBM
IBM IBM IBM IBM IBM IBM PLEASE WAIT... IBM IBM IBM IBM IBM
IBM
IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM
IBM
IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM
IBM
IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM
IBM
IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM
IBM
IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM
IBM
IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM
IBM
IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM
IBM
IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM
IBM
IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM
IBM
IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM
IBM
IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM
IBM
IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM
IBM
BOOTP: chosen-network-type = ethernet,auto,rj45,auto
BOOTP: server IP = 10.243.122.10
BOOTP: requested filename =
BOOTP: client IP = 10.243.166.9
BOOTP: client HW addr = 0 11 25 7e 4 4e
BOOTP: gateway IP = 10.243.166.1
BOOTP: device /pci@800000020000002/pci@2/ethernet@1
BOOTP: loc-code U789A.001.AAA1094-P1-T1
BOOTP: wait 60 seconds for Spanning Tree ...
BOOTP R = 1 BOOTP S = 2
FILE: /tftpboot/axtprov2
BOOTP: chosen-network-type = ethernet,auto,rj45,auto
BOOTP: server IP = 10.243.122.10
BOOTP: requested filename =
BOOTP: client IP = 10.243.166.9
BOOTP: client HW addr = 0 11 25 7e 4 4e
BOOTP: gateway IP = 10.243.166.1
BOOTP: device /pci@800000020000002/pci@2/ethernet@1
BOOTP: loc-code U789A.001.AAA1094-P1-T1
BOOTP: wait 60 seconds for Spanning Tree ...
BOOTP R = 1 BOOTP S = 2
FILE: /tftpboot/axtprov2
FINAL Packet Count = 16673
FINAL File Size = 8536286 bytes.
load-base=0x4000
real-base=0xc00000
Elapsed time since release of system processors: 16 mins 27 secs
-------------------------------------------------------------------------------
Welcome to AIX.
boot image timestamp: 07:39 03/30
The current time and date: 10:59:09 03/30/2006
number of processors: 2 size of memory: 3936Mb
boot device:
/pci@800000020000002/pci@2/ethernet@1:10.243.122.10,,10.243.166.9,10.243.166.1,00,00
closing stdin and stdout...
-------------------------------------------------------------------------------
in documentation it clearly says that restored server has to be the same
OS
version for starting network boot,
but i don't get it, the restored server just neeeds the boot image, no ?
the
bootp server is AIX 5.2 and the restored server is p505 with AIX 5.3
is/should be restored, the sysback backups went fine with no problems at
all, i tested the restore with one old B50 server with AIX 5.2 and
everything went fine, i'm suspicious about network connectivity but the
firewall was allowed for ping,bootps,bootpd,1500,1023,1022,1239,tftpd ...
i general i suspect that bootimage on AIX 5.2 server the BOOTP server is
not
okay for this kind of server with AIX 5.3 which is the one he needs, can
be
? the boot image is created like this ...
/usr/sbin/mksbnetboot -h'axtprov2' -d'ethernet' '-T chrp' '-k
mp' -S'10.243.122.10'
with no problems :-|
any help would be GREATELY appreciated !!!
any clue ?
TIA
goran
|
