Nov
05
2009

Bootp error during remote install with NIM (59661,004)

I get the following error when trying to do a remote NIM install with a new spot and lpp_source that I just created from 5.3 TL 11

oslevel -s: 5300-08-07-0920

(Allocated NIM resources)
5300-11-lpp lpp_source
5300-11-spot spot
nim_script nim_script directory containing customization scripts cre
boot boot represents the network boot resource

BOOTP: chosen-network-type = ethernet,auto,none,auto
BOOTP: server   IP =        10.32.18.39
BOOTP: requested filename =
BOOTP: client   IP =        10.32.16.130
BOOTP: client   HW addr =   fe f8 30 0 40 2
BOOTP: gateway  IP =        10.32.18.39
BOOTP: device    /vdevice/l-lan@30000002
BOOTP: loc-code  U9133.55A.103878H-V4-C2-T1

icmp 3 : port unreachable
ERROR: icmp 3
BOOTP: BOOTP request fail: 0

icmp 3 : port unreachable
ERROR: icmp 3
BOOTP: BOOTP request fail: 1

icmp 3 : port unreachable
ERROR: icmp 3
BOOTP: BOOTP request fail: 2
BOOTP ERROR: BOOTP request failed, QUIT
        !BA010004 !

We tried this, but it didn’t work:

nim -Fo reset 
nim -Fo deallocate -a subclass=all  

stopsrc -g nfs
stopsrc -s portmap
cd /etc
rm -rf rmtab xtab
cd /var/statmon
rm -rf state sm sm.bak
cd /etc
mv exports exports.old
touch exports
startsrc -s portmap
startsrc -g nfs 

Next we decided to put bootp in debug mode:

NIM Documentation

#

1. Comment out the bootps entry from the /etc/inetd.conf file on the server.
2. Stop all running bootpd processes.
3. Restart inetd using the refresh -s inetd command.
4. Start bootpd from the command line, using the /usr/sbin/bootpd -s -d -d -d command.

bash-3.00# /usr/sbin/bootpd -s -d -d -d
BOOTPD: bootptab mtime is Thu Nov  5 13:09:42 2009
BOOTPD: reading "/etc/bootptab"
BOOTPD: bad hardware address for host "10.32.17.150"
BOOTPD: read 2 entries from "/etc/bootptab"
BOOTPD: dumped 2 entries to "/etc/bootpd.dump".
BOOTPD: bootptab mtime is Thu Nov  5 13:09:42 2009
BOOTPD: Received boot request.
BOOTPD: request from IP addr 10.32.16.100
BOOTPD: IP address not found: 10.32.16.100
BOOTPD: Finished processing boot request.
BOOTPD: bootptab mtime is Thu Nov  5 13:09:42 2009
BOOTPD: Received boot request.
BOOTPD: request from IP addr 10.32.16.130
BOOTPD: found 10.32.16.130 nad0019aixd22
BOOTPD: bootfile = /tftpboot/nad0019aixd22
BOOTPD: vendor magic field is 99.130.83.99
BOOTPD: RFC1048 vendor data ( bp_vend[64] )
99.130.83.99.1.4.255.255.252.0.255.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.BOOTPD: sending RFC1048-style reply
BOOTPD: The following addresses are included in the bootp reply
BOOTPD: Client IP address (bp->bp_ciaddr) = 10.32.16.130
BOOTPD: Server IP address (bp->bp_siaddr) = 10.32.18.39
BOOTPD: Gateway IP address (bp->bp_giaddr) = 10.32.18.39
BOOTPD: Finished processing boot request.
BOOTPD: bootptab mtime is Thu Nov  5 13:09:42 2009
BOOTPD: Received boot request.
BOOTPD: request from IP addr 10.32.16.130
BOOTPD: found 10.32.16.130 nad0019aixd22
BOOTPD: bootfile = /tftpboot/nad0019aixd22
BOOTPD: vendor magic field is 99.130.83.99
BOOTPD: RFC1048 vendor data ( bp_vend[64] )
99.130.83.99.1.4.255.255.252.0.255.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.BOOTPD: sending RFC1048-style reply
BOOTPD: The following addresses are included in the bootp reply
BOOTPD: Client IP address (bp->bp_ciaddr) = 10.32.16.130
BOOTPD: Server IP address (bp->bp_siaddr) = 10.32.18.39
BOOTPD: Gateway IP address (bp->bp_giaddr) = 10.32.18.39
BOOTPD: Finished processing boot request.
BOOTPD: bootptab mtime is Thu Nov  5 13:09:42 2009
BOOTPD: Received boot request.
BOOTPD: request from IP addr 10.32.16.104
BOOTPD: IP address not found: 10.32.16.104
BOOTPD: Finished processing boot request.
BOOTPD: bootptab mtime is Thu Nov  5 13:09:42 2009
BOOTPD: Received boot request.
BOOTPD: request from IP addr 10.32.16.104
BOOTPD: IP address not found: 10.32.16.104
BOOTPD: Finished processing boot request.

Ironically, just putting it in debug mode made it work, we took it back out of debug mode and it still worked.

Written by admin in: NIM |

2 Comments »

  • GAUDIN

    We encountered the same problem and we resolved it starting the deamon bootps ! So enervous !!

    Comment | January 27, 2010
  • admin

    This is one of those cases where you just have to ‘jiggle the handle’ a little bit and then it will work.

    Comment | January 28, 2010

RSS feed for comments on this post. TrackBack URL

Leave a comment

Powered by WordPress | Aeros Theme | TheBuckmaker.com WordPress Themes