Monday, May 26, 2014

in.dhcpd[1099]: [ID 603263 daemon.notice] No more IP addresses

I came across this one at $work on a Solaris 9 server, and I must admit I was a little stumped. The full error is something like:

in.dhcpd[1099]: [ID 603263 daemon.notice] No more IP addresses on 192.168.254.0 network ()

When a additional SunRay terminal was plugged into the network. These are SunRay servers so I checked out how utadm was configured:


# utadm -l
LAN connections: 0ff
Subnetwork: 192.168.254.0
        Interface=      dmfe1 (192.168.254.1)
        Netmask=        255.255.255.0
        Broadcast=      192.168.254.255
        Router=         192.168.254.1
        AuthSrvr=       192.168.254.1
        FirmwareSrvr=   192.168.254.1
        NewTver=        3.1_120879-06_2007.03.13.15.14
        IP assignment=  10/239 (192.168.254.100)


Notice the last line, it specified the network - 192.168.254.100

So I checked DHCP leases:

#  pntadm -P 192.168.254.100

I found a bunch of leases displaying a lease expiration of 10+ years ago. They looked like:


0100144F6F70EE  00      192.168.254.194 10.16.16.40     04/02/2004       SunRay-dmfe1


So the fix, was to remove the leases that are now no longer in use and re-add the address back to the DHCP table for a new lease:

(Note: Where 192.168.254.100 is the network, and SunRay-dmfe1 is the DHCP macro code)

Ping the list to make sure they're not active:

# for x in $(pntadm -P 192.168.254.100 | grep 2004 | cut -f 3); do echo ${x}:; ping ${x} 2; done

If no replies, delete and re-add the IP address:

# for x in $(pntadm -P 192.168.254.100 | grep 2004 | cut -f 3); do echo Removing ${x}:; pntadm -D ${x} 192.168.254.100; echo Adding ${x}:; pntadm -A ${x} -m SunRay-dmfe1 192.168.254.100; done

Had the site plug the new terminal back in to the network and it now works!

Happy days...