HP Insight Control for Linux 7.0 Installation Guide

Figure 15 Multiple network architecture
In this configuration, static routes must be added to the (and to the external DHCP, if used) to set
the gateway to the remote subnets. If the same router that provides connectivity to the remote
subnets also provides connectivity to the larger public network, a simple default gateway may
suffice. It is just required that the CMS have the ability to reach the remote network.
To accommodate multiple networks, you must modify the DHCP configuration to provide additional
address ranges and options to the clients on those networks. The following sections provide examples
of these modified configurations.
A.5.1 Configuring ISC DHCP with multiple subnets
The information in this section applies to configuring ISC DHCP on the CMS or on an external
server.
Example 13 provides an example of the /etc/dhcpd.conf file configuration modifications that
are required to support multiple subnets integrated into the operation of HP Insight Control for
Linux. Two additional subnets, 172.1.2.0/24 and 172.1.3.0/24, are configured. Each subnet
must be provided with its own routers and IP address ranges that are specific to it.
Example 13 ISC DHCP configuration file modifications to support multiple subnets
#
# DHCP Configuration modified for Insight Control for Linux
#
ddns-update-style interim;
ignore client-updates;
deny duplicates;
# Insight Control for Linux Settings
option option-140 code 140 = text; # set option 140 to "text"
option option-140 "172.1.1.1"; # IP address of the Insight Control for Linux CMS
next-server 172.1.1.1; # IP address of the Insight Control for Linux CMS
filename "pxelinux.bin"; # name of the PXE boot image file
A.5 Configuring a multiple subnetwork topology 79