Ping test failed during mksysb installation from master nim to client nim


Ping test failed during mksysb installation from master nim to client nim. I got this message " Response to the First BOOTP request was not received ". Please some one provide me what is the main reason and how solve this problem.  Thanks
sams20Asked:
Who is Participating?

[Webinar] Streamline your web hosting managementRegister Today

x
 
woolmilkporcConnect With a Mentor Commented:
I think the most probable reason for your issue is VLAN.

Please examine the settings:

Switch: tagged/untagged, VLAN ID

VIO: VLAN ID, SEA/l-lan

LPAR: VLAN ID, l-lan
0
 
woolmilkporcCommented:
I think you mean "from client to master", and this is mostly due to an incorrect gateway or target (server) address setting.

Or is there a firewall inbetween?

The master cannot ping the client  between the tftp transfer and the final reboot.

Please double check!

wmp

0
 
sams20Author Commented:

 Wmp

Thanks, I mean " from master to client" , I have mksysb file and a spot for this mksysb on master nim. I was trying to install on a client through nim installation process. Both master and client same subnet , mentioned client ip and master server ip in IP parameter. Then when I was trying to ping test , it was failed. Got this message, "Response to the First BOOTP request was not received ."

                         
0
Upgrade your Question Security!

Your question, your audience. Choose who sees your identity—and your question—with question security.

 
woolmilkporcCommented:
What you're saying is not really consistent.

If a PING test fails from the client to the master the client says "Ping test failed" and nothing else.

If a ping fails from master to client it simply says "PING ..."  until you cancel it, then it displays the packet statistics.

There is no "NIM PING" from master to client.

Your message could appear on the client when booting the client over the net fails.

Sometimes "bootpd" is not running on the NIM master in such a case. Check with

lssrc -ls inetd

whether it's there.

It can also appear on the master when the client is not up but you chose "Initiate reboot and installation now: Yes" nonetheless.

The net boot on the client will work in the latter case!

0
 
sams20Author Commented:

wmp

Thanks, actually I have mentioned about booting the client during nim installation process. I got from master,

# lssrc -ls inetd                                                              
Subsystem         Group            PID          Status                          
 inetd            tcpip            4522122      active                          
Debug         Not active                                                        
Signal        Purpose                                                          
 SIGALRM      Establishes socket connections for failed services.              
 SIGHUP       Rereads the configuration database and reconfigures services.    
 SIGCHLD      Restarts the service in case the service ends abnormally.        
Service       Command                  Description              Status          
 bootps       /usr/sbin/bootpd         bootpd /etc/bootptab     active          
 tftp         /usr/sbin/tftpd          tftpd -n                 active          
 xmquery      /usr/bin/xmtopas         xmtopas -p3              active          
 wsmserver    /usr/websm/bin/wsmserver wsmserver -start         active          
 time         internal                                          active          
 daytime      internal                                          active          
 time         internal                                          active          
 daytime      internal                                          active          
 ntalk        /usr/sbin/talkd          talkd                    active          
 exec         /usr/sbin/rexecd         rexecd                   active          
 login        /usr/sbin/rlogind        rlogind                  active          
 shell        /usr/sbin/rshd           rshd                     active          
 telnet       /usr/sbin/telnetd        telnetd -a               active          
 ftp          /usr/sbin/ftpd           ftpd                     active          
#                                                                              

and when I will check option before start mksysb installation on master, for "Initiate reboot and installation now:   ", will choice "yes" instead of "no".

0
 
woolmilkporcCommented:
Choose "No" for that option!
0
 
woolmilkporcCommented:
.,, and reset the client before reattempting to prepare it for installation!

smitty nim_mac_op -> reset -> deallocate/force: yes
0
 
sams20Author Commented:


I did reset the client. But still when I choose execute ping test option and press enter. After a minutes message shows failed
0
 
woolmilkporcCommented:
Did you really set the correct IP of the NIM master (and the correct mask) on the client?

You could also try turning off "Spanning Tree". It's in the Interface Setup area of SMS on the client.
0
 
woolmilkporcCommented:
... and did you configure the right NIC on the client, if there's more than one?
0
 
sams20Author Commented:

yes, I did setup correct ip parameter on client. choose turn off spinning tree.I have one NIC on client.

Thanks.
0
 
woolmilkporcCommented:
If server and client are on the same subnet - which gateway address did you specify?
I found a hint saying that you should specify the NIM server's IP as the gateway address - well, I must say that I never had to do that, but you could try it nonetheless.

Please take care not to specify the IP with any leading zeroes, i.e. don't use something like 172.016.020.005 !

Another (perhaps silly) question - your client's IP is not accidentially in use by another machine?

0
 
sams20Author Commented:

I did use nim server ip as a gateway address and without gateway address non of those working. I did nslookup client ip is the same ip. Is there any issue about bootp services?
0
 
woolmilkporcCommented:
Even if there were a bootp issue ping must work!

We definitely do have an IP problem here!

Are you able to ping the NIM server's IP from other machines?
0
 
woolmilkporcCommented:
You could try to ping the client's ip to rule out a dupllicate address.

Is the client perhaps an LPAR controlled by a VIOS?
If so, is everything set up correctly in that aspect, particularly regarding VLAN?
0
 
sams20Author Commented:

Yes, ping from both side is working fine.
But the client is an LPAR controlled by VIOS.
Yes, there is VLAN, but I used same VLAN id on both server.
0
 
woolmilkporcCommented:
ping from both sides??

You should not be able to ping a machine which is on SMS, and I always thoght that the fact that the client can _not_ ping the server is the issue we're working on here!
0
 
sams20Author Commented:

But during mksysb installation process, after setup IP parameter there is one option 3 ping test and option 1: execute ping test, That ping test was failed on SMS. This is the issue.
0
 
woolmilkporcCommented:
Yes, I assumed that. But why did you write in your previous comment that ping works?
0
 
sams20Author Commented:


This ping works mean. if I do just ping on terminal it works like.

from server A,
#ping serverB  
or
from serverB,
#ping serverA

But, during mksysb installation on client SMS ping test is failed.
0
All Courses

From novice to tech pro — start learning today.