Jumpstart Client Issue

UNIX Solaris
1

I have a jumpstart client that is not requesting the tftp boot file. The rarp function is working, hostname and ip are set ok, but it hangs after that.

tcpdump output:

jumpstart-server:/var/lib/tftpboot# tcpdump -i eth1
tcpdump: verbose output suppressed, use -v or -vv for full protocol decode
listening on eth1, link-type EN10MB (Ethernet), capture size 96 bytes
12:53:11.456281 IP v445-27.552 > 255.255.255.255.sunrpc: UDP, length 76
12:53:12.993052 IP v445-27.552 > 255.255.255.255.sunrpc: UDP, length 76
12:53:14.544813 IP v445-27.552 > 255.255.255.255.sunrpc: UDP, length 76
12:53:16.147544 IP v445-27.552 > 255.255.255.255.sunrpc: UDP, length 76
12:53:17.769511 IP v445-27.552 > 255.255.255.255.sunrpc: UDP, length 76
12:53:19.290295 IP v445-27.552 > 255.255.255.255.sunrpc: UDP, length 76
12:53:20.791088 IP v445-27.552 > 255.255.255.255.sunrpc: UDP, length 76
12:53:21.566594 IP6 fe80::211:43ff:fee8:8d06.mdns > ff02::fb.mdns: 0[|domain]
12:53:21.566657 IP jumpstart-server.mdns > 224.0.0.251.mdns: 0 PTR (QM)? 255.255.255.255.in-addr.arpa. (46)
12:53:22.307872 IP v445-27.552 > 255.255.255.255.sunrpc: UDP, length 76
12:53:22.574564 IP6 fe80::211:43ff:fee8:8d06.mdns > ff02::fb.mdns: 0[|domain]
12:53:22.574611 IP jumpstart-server.mdns > 224.0.0.251.mdns: 0 PTR (QM)? 255.255.255.255.in-addr.arpa. (46)
12:53:23.835900 IP v445-27.552 > 255.255.255.255.sunrpc: UDP, length 76
12:53:24.578566 IP6 fe80::211:43ff:fee8:8d06.mdns > ff02::fb.mdns: 0[|domain]
12:53:24.578612 IP jumpstart-server.mdns > 224.0.0.251.mdns: 0 PTR (QM)? 255.255.255.255.in-addr.arpa. (46)
12:53:25.379668 IP v445-27.552 > 255.255.255.255.sunrpc: UDP, length 76
12:53:26.907446 IP v445-27.553 > 255.255.255.255.sunrpc: UDP, length 76
12:53:56.598567 IP6 fe80::211:43ff:fee8:8d06.mdns > ff02::fb.mdns: 0[|domain]
12:53:56.598617 IP jumpstart-server.mdns > 224.0.0.251.mdns: 0 PTR (QM)? 251.0.0.224.in-addr.arpa. (42)
12:53:57.362810 IP v445-27.rtsp > 255.255.255.255.sunrpc: UDP, length 76
12:53:57.606567 IP6 fe80::211:43ff:fee8:8d06.mdns > ff02::fb.mdns: 0[|domain]
12:53:57.606615 IP jumpstart-server.mdns > 224.0.0.251.mdns: 0 PTR (QM)? 251.0.0.224.in-addr.arpa. (42)
12:53:58.964789 IP v445-27.rtsp > 255.255.255.255.sunrpc: UDP, length 76
12:53:59.610564 IP6 fe80::211:43ff:fee8:8d06.mdns > ff02::fb.mdns: 0[|domain]
12:53:59.610612 IP jumpstart-server.mdns > 224.0.0.251.mdns: 0 PTR (QM)? 251.0.0.224.in-addr.arpa. (42)
12:54:00.436603 IP v445-27.rtsp > 255.255.255.255.sunrpc: UDP, length 76
12:54:01.963380 IP v445-27.rtsp > 255.255.255.255.sunrpc: UDP, length 76
12:54:03.480166 IP v445-27.rtsp > 255.255.255.255.sunrpc: UDP, length 76
12:54:05.085894 IP v445-27.rtsp > 255.255.255.255.sunrpc: UDP, length 76
12:54:06.611922 IP v445-27.rtsp > 255.255.255.255.sunrpc: UDP, length 76
12:54:08.121710 IP v445-27.rtsp > 255.255.255.255.sunrpc: UDP, length 76
12:54:09.739431 IP v445-27.555 > 255.255.255.255.sunrpc: UDP, length 76

syslog output:

jumpstart-server:/var/lib/tftpboot# tail -100 /var/log/syslog
Dec 18 12:50:06 jumpstart-server rpc.bootparamd: Returning v445-27   (none)    192.168.10.112
Dec 18 12:50:06 jumpstart-server rpc.bootparamd: whoami got question for 192.168.200.27
Dec 18 12:50:06 jumpstart-server rpc.bootparamd: This is host v445-27
Dec 18 12:50:16 jumpstart-server rpc.bootparamd: Returning v445-27   (none)    192.168.10.112
Dec 18 12:50:16 jumpstart-server rpc.bootparamd: whoami got question for 192.168.200.27
Dec 18 12:50:16 jumpstart-server rpc.bootparamd: This is host v445-27
Dec 18 12:50:26 jumpstart-server rpc.bootparamd: Returning v445-27   (none)    192.168.10.112
Dec 18 12:50:26 jumpstart-server rpc.bootparamd: whoami got question for 192.168.200.27
Dec 18 12:50:26 jumpstart-server rpc.bootparamd: This is host v445-27
Dec 18 12:50:36 jumpstart-server rpc.bootparamd: Returning v445-27   (none)    192.168.10.112
Dec 18 12:50:36 jumpstart-server rpc.bootparamd: whoami got question for 192.168.200.27
Dec 18 12:50:36 jumpstart-server rpc.bootparamd: This is host v445-27
Dec 18 12:50:46 jumpstart-server rpc.bootparamd: Returning v445-27   (none)    192.168.10.112
Dec 18 12:50:46 jumpstart-server rpc.bootparamd: whoami got question for 192.168.200.27
Dec 18 12:50:46 jumpstart-server rpc.bootparamd: This is host v445-27
Dec 18 12:50:56 jumpstart-server rpc.bootparamd: Returning v445-27   (none)    192.168.10.112
Dec 18 12:50:56 jumpstart-server rpc.bootparamd: whoami got question for 192.168.200.27
Dec 18 12:50:56 jumpstart-server rpc.bootparamd: This is host v445-27
Dec 18 12:51:06 jumpstart-server rpc.bootparamd: Returning v445-27   (none)    192.168.10.112
Dec 18 12:51:06 jumpstart-server rpc.bootparamd: whoami got question for 192.168.200.27
Dec 18 12:51:06 jumpstart-server rpc.bootparamd: This is host v445-27
Dec 18 12:51:16 jumpstart-server rpc.bootparamd: Returning v445-27   (none)    192.168.10.112
Dec 18 12:51:16 jumpstart-server rpc.bootparamd: whoami got question for 192.168.200.27
Dec 18 12:51:16 jumpstart-server rpc.bootparamd: This is host v445-27
Dec 18 12:51:26 jumpstart-server rpc.bootparamd: Returning v445-27   (none)    192.168.10.112
Dec 18 12:51:26 jumpstart-server rpc.bootparamd: whoami got question for 192.168.200.27
Dec 18 12:51:26 jumpstart-server rpc.bootparamd: This is host v445-27
Dec 18 12:51:37 jumpstart-server rpc.bootparamd: Returning v445-27   (none)    192.168.10.112
Dec 18 12:51:37 jumpstart-server rpc.bootparamd: whoami got question for 192.168.200.27
Dec 18 12:51:37 jumpstart-server rpc.bootparamd: This is host v445-27

This jumpstart server has worked on 150+ clients in the last 6 months...just seems to be this one client (v445).

I have reset OBP values to defaults, power cycled the client a few times, and did a reboot of the jumpstart server.

What are the next options? TIA

2

how are the config files looking?

  • /etc/hosts
  • /etc/ethers
  • /etc/bootparams

what are the IP parameters for host and server...?

3

/etc/hosts

/etc/ethers

/etc/bootparams

The server has an IP of 192.168.200.1.

The client hangs with the following text:

---------- Post updated at 01:42 PM ---------- Previous update was at 01:27 PM ----------

The may or may not be helpful

returns

4

and what is 192.168.10.112 ?

also, please don't use "quote" tags for code. use "code" tags!

5

eth0 on the jumpstart server is 192.168.10.112 and is used to connect from internal pc's to admin the js server.

6

don't know, but it seems like the 192.168.10.112 is the problem here... can you set this interface to "down" state and test again?

1 Like
7

That worked. I'll have to look into the network setup.

Thanks for the help!