Prerequisites for a UCS provisioning environment
In addition to the standard BMC Server Automation provisioning setup requirements, you must ensure that the DHCP, IIS, and data store system are set up properly for UCS provisioning.
DHCP settings
You must set the entire set of scope options as shown in the following table.
Scope option name | Sample Value |
|---|---|
003 Router | 10.20.238.2 |
006 DNS Servers | 10.20.21.3, 10.20.21.13 |
060 PXEClient | PXEClient |
211 bl-server | 10.20.238.101 |
212 bl-port | 0x2667 |
IIS settings
To access the Kickstart file for Linux provisioning from an IIS web server, set the IIS web service extensions as shown in the following table.
Web service extension | Status |
|---|---|
All Unknown CGI Extensions | Allowed |
All Unknown ISAPI Extensions | Prohibited |
Active Server Pages | Prohibited |
ASP .NET v2.0 50727 | Prohibited |
Indexing Service | Prohibited |
Internet Data Connector | Allowed |
Server Side Includes | Prohibited |
WebDAV | Prohibited |
Data store machine configuration
Check the host computer that contains the data store to ensure that the following requirements are met:
- NSH is installed.
- RSCD agent is installed.
- The exports file (/usr/lib/rsc/exports) contains an entry with the application server IP address or host name and a read/write mapping. This restricts access to accept connections only from the listed application server. For example:
192.168.0.1 rw - If the data store is on a Linux machine, the data store root must have the appropriate Samba share with valid credentials.
Supported operating systems
For a list of the operating systems that you can provision with BMC Server Automation, use the BMC Solution and Product Availability and Compatibility (SPAC) Utility. Search for the BMC BladeLogic Server Automation Suite product name and the BMC BladeLogic Server Automation Provisioning component.