ISC DHCP and VCS setup

Frank Bulk frnkblk at
Wed May 9 18:59:35 UTC 2007

When we put our third-party DHCP HA appliance into production our Calix 
IRC card also choked on DHCP responses.  

Guenther, Calix wizard, was able to see in debug mode that the device 
responding to the DHCP request didn't match the Calix-configured relay 
address.  So our third-party DHCP appliance vendor implemented iptables 
into their product so that the response packets were munged to the match
the virtual IP.

I hope this helps.


-----Original Message-----
From: dhcp-users-bounce at [mailto:dhcp-users-bounce at] On Behalf
Of Steve Forman
Sent: Wednesday, May 09, 2007 11:11 AM
To: dhcp-users at
Subject: ISC DHCP and VCS setup


	We are currently in the process of setting up DHCP with Veritas
Cluster Server in preparation for service migration and I've setup a
process resource which creates a virtual IP on the servers.  I've tested
failover capabilities and it all works well, however, in the past, we've
noticed that our Calix customers seem to ignore the "server-identifier"
property which (if I understand correctly is supposed to force the
daemon to process requests on the virtual IP as opposed to the physical). 
Therefore, with our impending cutover, it would require that all of our
Calix customers, on several individual Calixes, replace the old physical
server IP addresses with all three of our new server  IPs. 
	 The question is:  is it possible to make this cutover without
the need for them to change their Calix setups, i.e., is there an
alternate configuration that would work or another way to force the
daemon to listen on the virtual IP? Does anybody have any advice on how
to proceed moving forward with VCS or is this the best/only way to do it?
Thanks greatly in advance.

More information about the dhcp-users mailing list