How the OS Build Agent locates the Build Manager

How the OS Build Agent locates the Build Manager depends on the boot method.

WinPE

• SA retrieves DHCP options containing the agent gateway IP address and Build Manager port, or
• The Build Manager is located by loading the configuration file:

  /opt/opsware/boot/tftpboot/DHCPOptions.ini

  which contains the OS Provisioning settings specified during SA installation.

• If the processes above fail, SA defaults to the hostname buildmgr on port 8017.

• Linux

• Linux x86 locates the Build Manager using kernel arguments supplied at PXE boot time. These are configured during the SA installation and stored in the file

• /opt/opsware/boot/tftpboot/pxelinux.cfg/default

  Linux IA64

  Linux IA64 locates the Build Manager using kernel arguments supplied at PXE boot time. These are configured during the SA installer and stored in the file

  /opt/opsware/boot/tftpboot/elilo.conf

  Oracle Solaris/Sun SPARC 10 and 11

  For Oracle Solaris/Sun SPARC 10 and 11 OS Provisioning, the JumpStart build script (Solaris/SPARC 10) or Automated Installer (Solaris/SPARC 11) runs the OS Build Agent, which contacts the Build Manager (via the Agent Gateway in the core). The Solaris begin script attempts to locate the Build Manager in the following ways:

  • By using information that the SA DHCP server provided
  • By looking for the host name buildmgr in DNS as configured by the DHCP server

  You can override the way that the OS Build Agent contacts the Build Manager by specifying a boot argument at the prompt when you boot a new Solaris server, for example:

  ok boot net:dhcp - install buildmgr=buildmgr.example.com:8017

  ok boot net:dhcp - install buildmgr=192.168.1.15:8017

  Non-DHCP environments

  In both Windows and Red Hat non-DHCP environments, SA locates the Build Manager using the network configuration specifications you provide. See Booting a Red Hat Enterprise Linux server in a non-DHCP environment and Booting a Windows Server in a non-DHCP environment.