ITEM: T6626L
Sysback Ver 3.2 failed on the network install
ENV:
AIX 3.2.5
Sysback version 3.2.0.11
model 990 Server
model 220 client
Desc:
Customer wants to know if he can boot a system over the
network if it does not have a diskette drive on it.
Action:
If the 220 is bootp enable then the answer is you can boot
and install a system over the network at 3.2.5. At 4.1
you don't need to have a bootp enable system. You can make
IPLROM diskettes to do that.
Here is how to Create and Boot a System from the Network
---------------------------------------------------------
On the server do this
----------------------
1. smitty sysback
Remote Backup Services
Configure Remote Backup Services
2. smitty sysback
Network Install Services
Configure this Host as a Network Install Server
3. smitty sysback
Network Install Services
Define a Tape Drive or Virtual Device for Network Installation
"Add your tape drive to this list"
4. smitty sysback
Network Install Services
Configure/Update a Network Boot Image
"Choose the ethernet or token ring"
5. smitty sysback
Network Install Services
Add or Change a Network Boot Client
Network Adapter [/dev/tok0]
Client HOSTNAME []
Client Network ADAPTER ADDRESS []
You have to know the HARDWARE ADDRESS OF THE NETWORK ADAPTER (12 digit
number) not
the Network IP Address
Client system
-------------
If the system is bootp enable do this:
1. boot in secure mode
2. When it hungs on led 200; turn key to service mode and hit the
reset button only once
3. You should get a network boot menu, fill it in with the correct
ip address for both the client and the server systems
4. and start the boot
Response:
Booted client this way:
1. rebooted in secure mode
2. When it hits 200 turn to service mode and hit the reset
button once
3. hung on led 262
262 Attempting Network IPL, menus, no console keyboard detected
4. Press Enter on the tty
5. choose the correct lang "1"
6. choose the correct boot device
7. and start the boot again
The bootp worked correctly, but the tftp part is failing. It is
only sending over 6 packets then failing.
Response:
Action: Customer seemed to be having problems with TFTP. I had
the customer go to his /etc/inetd.conf file and checked
to make sure that the tftp line was uncommented and
it was. I then had the customer save the file and do
an inetimp and then a refresh -s inetd.
I then had the customer go into SMIT and check the nobody
account. It had expired so I had the customer change
the experation date to be 0 and saved the change. I then
had the customer tftp the motd and it worked just fine.
Lee then had the customer try to tftp the image they
had been working on and it timed out. I could not understand
why, the client sends out a request the server then
receives it the client then sent out 3 more requests, but
the server only responded to the first one.
We then had the customer try to tftp from the client to
the server (while the client was in normal mode, before
the client was in service mode) and we were successful
in tftping the image from one machine to the other, only
when we try to boot the machine over the network via twisted
pair do we have a problem. I am not sure why.
Next Action:
Informed customer that we would do some research and get
back to him on this.
Response:
Action: Called customer and asked him to fax in a copy of his
/etc/bootptab file. He did this while we were on the phone.
I then had the customer check the permissions of
the /tftpboot and they were 775 which is correct. I then
made sure the linked file permissions were correct and
they were. All permissions on the files were
correct.
I then got the fax and looked at the /etc/bootptab file
and it all seemed correct.
I then asked the customer what the ip address of the
the server and client are:
client (220) 151.145.8.130
server (990) 151.145.9.70
I noticed that they are on two different subnets so
I asked the customer if we are going through any type of
gateway. He said they are and the gateway ip is
151.145.8.200.
So I had the customer add to his /etc/bootptab file the
following: gw=151.145.8.200:
We did this, and I then had the customer go ahead and
put bootp in debug mode.
I had the customer do the following in order to start
bootp in debug mode:
ps -eaf | grep bootpd
kill any process of bootpd that is running using the
-9.
vi /etc/inetd.conf
comment out the bootps line
save the file and then do
inetimp
refresh -s inetd
bootpd -d -d -d -d -s & (starts bootp in debug)
Started the 220 to try and boot and got back the following
information about the bootp debug.
ciaddr 151.145.8.130
siaddr 151.145.9.73
giaddr 151.145.8.200
I then asked the customer how many interfaces he has in the
990. He has two ethernet adapters. One has the ip
address of 151.145.9.73 and the other is 151.145.9.70.
Customer would like to have the bootp received on the
151.145.9.70. So in the /etc/bootptab file I had the customer
add the following flag of sa=151.145.9.70:
When he added this flag we started up the bootp in debug
mode again and then tried to boot the 220 and it worked just
fine. Customer was very happy. I then had the
customer do a ps -eaf | grep bootpd and kill the bootpd
process. Then I had the customer vi the /etc/inetd.conf
and uncomment the bootps line. Save the file and then
do an inetimp and refresh -s inetd.
Customer is going to let the machine boot and then try
it again to make sure that this works.
He will call in if he has any more questions or problems.
Support Line: Sysback Ver 3.2 failed on the network install ITEM: T6626L
Dated: April 1995 Category: N/A
This HTML file was generated 99/06/24~13:30:35
Comments or suggestions?
Contact us