Solution Guide

Active System Manager Solution GuideActive System 800 (AS800)
103
The ESXi 5.1 customized image is embedded inside the appliance at
/var/lib/tftpboot/esxi51._dell. The image is configured to create a kickstart file dynamically
based on the IP address provided in the Active System Manager inventory.
If the ESXi host is configured to learn the IP address through DHCP (configured through orchestration),
and then there is no need to update the Server IP Address information in the Active System Manager
inventory. The IP Address configured on the hosts by the DHCP server will be updated automatically
during the server installation.
If a new image is required to be added to the appliance, follow the steps available in Appendix C
Firmware and Software Base Lineup.
To start the DHCP services, execute the /etc/init.d/dhcpd restart command.
G.5 Configuring the PXE Setup with the Existing DHCP Server
If the DHCP server already exists on the Hypervisor Management Network, perform the following steps:
1. Update the appliance’s DHCP settings to support the Bootstrap Protocol (BOOTP).
2. Edit the /etc/dhcpd/dhcpd.conf file.
3. Update the next-server to point to the Active System Manager appliance IP address; the images
are hosted on the appliance.
allow booting;
allow bootp;
filename "pxelinux.0";
next-server 192.168.122.101;
H Appendix HFAQs
Q1 Volumes on EqualLogic Array are not removed for cancelled sessions. This wastes storage
space and consumes iSCSI connections.
A1 User should manually cleanup the unused volumes on the EqualLogic storage array and iSCSI
connections after session is canceled.
Q2 The orchestrations assume that Port Channel 2 is configured on the switches. If not, you get a
failure indicated by red links on the session.
A2 The list of port-channels are configurable, based on the environment this list could be
controlled by updating the “portChannelList” in the “ssi.properties” file under “$HOME/asm-
galeforce/gf/common/integrations/Dell/Force10-S4810
Q3 Where is the VM created? Is there way to specify which Datastore gets created?
A3 User can specify on which datastore the VM will be created by providing the value of
“TargetDatastore” provisioning parameter of the VM in the template as shown in the
screenshot below. If there is no value provided for “TargetDatastore” , the RA chooses the best
available datastore for VM creation.