Multiple subnets

The challenge with an Ignite server connected to multiple subnets is ensuring the server is correctly configured to handle client network interfaces for boot and installation on the different subnets. If subnets are isolated or performance is a concern, you will need to ensure that installation traffic is correctly routed to the Ignite server.

The following diagram shows the example systems used when outlining solutions for a complex network with multiple subnets.

Remote systems

Network boot is based on broadcast protocols. These broadcasts are normally constrained to one subnet. When client systems are on a subnet that is not directly connected to an Ignite server broadcast network, packets used for boot will not be able to reach the Ignite server. If there are remote systems on other subnets (hpuxsysa and hpuxsysb), you must determine how network boot will be supported on each subnet for these systems. You will also need to ensure that installation traffic is correctly routed.

The following diagram shows the systems that will be referenced when solutions for remote systems are discussed.

Complex network challenges 49