CentOS DHCP setup
The setup on a Linux CentOS or RedHat distribution requires modification of the DHCP configuration file to support VC auto-deployment capabilities.
Install the DHCP service if it is not already installed: >yum install dhcp
If the DHCP server installation was installed at the time the OS was installed, then you must edit the /etc/dhcp/dhcpd.conf file. An example DHCP configuration file is provided below.
In the configuration file, the two key elements enabling auto-deployment to work are the tftp-server-name and bootfile-name fields. Definition of these two fields allows the DHCP server to reply to DHCP clients with the proper TFTP server and file settings. The DHCP configuration file can be customized based on your specific configuration needs. The example below assumes that each enclosure has its own VC configuration script for deployment, but if enclosures share the same script, you can modify your DHCP configuration file to accommodate that.
Example
/etc/dhcp/dhcpd.conf using one configuration file for all target VC configurations: default-lease-time 600;
max-lease-time 720; authoritative;
option subnet-mask 255.255.255.0; option broadcast-address 192.168.1.255; option routers 192.168.1.254;
option domain-name-servers 192.168.1.1, 192.168.1.2; option domain-name "hpvcdeploy.com";
subnet 192.168.1.0 netmask 255.255.255.0 { range 192.168.1.100 192.168.1.200; option tftp-server-name "192.168.1.3"; option bootfile-name "myconfig-1.script";
Another optional configuration for DHCP involves separate VC configuration files for the target enclosures. In this case, you would need to explicitly define the mapping between the configuration files and the MAC addresses of the primary VC-Enet modules in the enclosures.
Similarly, you could also have multiple VC-Enet modules using a specific configuration file that requires a grouping of configuration definitions supported by DHCP.
Example
/etc/dhcp/dhcpd.conf using one-to-one configuration file mapping to VC configurations: default-lease-time 600;
max-lease-time 7200; authoritative;
option subnet-mask 255.255.255.0; option broadcast-address 192.168.1.255; option routers 192.168.1.254;
option domain-name-servers 192.168.1.1, 192.168.1.2; option domain-name "hpvcdeploy.com";
subnet 192.168.1.0 netmask 255.255.255.0 { range 192.168.1.100 192.168.1.200;
host enclosure1 {
option tftp-server-name “192.168.1.3”;
Appendix B: Auto-deployment process 293