Ignite-UX
Showing results for 
Search instead for 
Do you mean 

tftp acting strange during ignite restore

Frequent Visitor

tftp acting strange during ignite restore

Hello Experts,

I am facing a strange issue while installing HP-UX on ia64 servers.

I have a ignite server which has two IPs, both are in same subnet.

when I try to boot a client(bl860c i2) from this ignite server, it fails for one IP but works with the other.

 

-On the client this is the settings of my dbprofiles

 

Profile Name: profileA
Network Type: IPv4
Server IP address: 10.32.4.15
Client IP address: 10.32.4.16
Gateway IP address: 10.32.4.1
Subnet Mask: 255.255.255.0
Boot File: /opt/ignite/boot/nbp.efi
Optional Data:

 

Profile Name: profileB
Network Type: IPv4
Server IP address: 10.32.4.172
Client IP address: 10.32.4.16
Gateway IP address: 10.32.4.1
Subnet Mask: 255.255.255.0
Boot File: /opt/ignite/boot/nbp.efi
Optional Data:

 

- IP configured on Ignite-UX server

 

Name Mtu  Network    Address
lan1 1500 10.32.4.0  10.32.4.172
lan0 1500 10.32.4.0  10.32.4.15
lo0 32808 127.0.0.0  127.0.0.1

 

when I use "profileB" to boot the client, the client boots properly and I get the OS selection option almost immediately.

However, when I try to use "profileA" the client fails with "PXE-E18: Server response timeout." and on the ignite server I get the following errors in syslog file:

 

Feb 26 11:34:12 cubau001 tftpd[26302]: Transfer timed out
Feb 26 11:37:39 cubau001 tftpd[26487]: Transfer timed out
Feb 26 11:37:43 cubau001 tftpd[26488]: Transfer timed out
Feb 26 11:37:47 cubau001 tftpd[26490]: Transfer timed out

 

And here is the rub, when I use "profileA" where Ignite-UX server IP is 10.32.4.15 and client IP is 10.32.4.16, netstat revels this:

 

cubau001 /root $ netstat -an |grep -i 67
udp 0 0 10.32.4.172.65042 10.32.4.16.1767
udp 0 0 10.32.4.172.65035 10.32.4.16.1767
udp 0 0 *.67 *.*
udp 0 0 10.32.4.172.65045 10.32.4.16.1767
udp 0 0 10.32.4.172.65044 10.32.4.16.1767
udp 0 0 10.32.4.172.65043 10.32.4.16.1767

 

I am not able to understand why the client is binding to 10.32.4.172 though I have specified 10.32.4.15.

Also, if I unplumb 10.32.4.172 NIC then the client boots from the Ignite server flawlessly.

Ignite-UX version:

IGNITE C.7.15.254 HP-UX Installation Utilities (Ignite-UX)
Ignite-UX-11-11 C.7.15.254 HP-UX Installation Utilities for Installing 11.11 Systems
Ignite-UX-11-23 C.7.15.254 HP-UX Installation Utilities for Installing 11.23 Systems
Ignite-UX-11-31 C.7.15.254 HP-UX Installation Utilities for Installing 11.31 Systems

 

OS Version:

 HPUX11i-DC-OE            B.11.31.1209   HP-UX Data Center Operating Environment

 

Any help would be very much appreciated. 

Unix is user-friendly. It's just very selective about who its friends are
2 REPLIES
HPE Pro

Re: tftp acting strange during ignite restore

Check the output of the below command to find the IP address configured as Ignite-UX Server IP. This IP address would be used during Ignite-UX Client network recovery. 

 

# instl_adm -d

 

In your case, 10.32.4.172 might be configured as Ignite-UX server IP. 

 

Sample output:

# instl_adm -d

# instl_adm defaults:
# NOTE: Manual additions between the lines containing "instl_adm defaults"
# and "end instl_adm defaults" will not be preserved.
server="15.130.230.22" --> Ignite-UX Server IP address
netmask[]="255.255.255.224"
route_gateway[0]="15.145.112.129"
route_destination[0]="default"
# end instl_adm defaults.

 

Regards,
Pradeep

I am an HP Employee
A quick resolution to technical issues for your HP Enterprise products is just a click away HP Support Center Knowledge-base
See Self Help Post for more details


Highlighted
Frequent Visitor

Re: tftp acting strange during ignite restore

Hi Pradeep,

Thanks for the respnse, I have checked that, its set to 10.32.4.15

 

cubau001 /root $ instl_adm -d
# instl_adm defaults:
# NOTE: Manual additions between the lines containing "instl_adm defaults"
# and "end instl_adm defaults" will not be preserved.
server="10.32.4.15"
netmask[]="255.255.255.0"
route_gateway[0]="10.32.4.1"
route_destination[0]="default"
# end instl_adm defaults.

Unix is user-friendly. It's just very selective about who its friends are