Configuring system packages in BMC Server Automation

To use IBM LPAR system packages in BMC Cloud Lifecycle Management, first you must configure the following settings in BMC Server Automation.

To configure the NIM machine name and LPAR hostname

1. Add the NIM machine static IP address to the AIX system package:
   1. Open the AIX system package that you created in BMC Server Automation.
   2. Navigate to the Local Properties tab.
   3. Navigate to the Basic Config tab of the system package, and use the ??HOST_NAME?? property in the Nim machine name field.
      
      BMC Cloud Lifecycle Management passes the property value to the BMC Server Automation provider.
2. Add the CLIENT_IP_ADDRESSto the AIX system package:
   1. Navigate to the Local Properties tab.
   2. Add CLIENT_IP_ADDRESS as a new local property.

   3. Click the Pre-Machine Definition Scripts tab, and then enter the following script:
      echo ??CLIENT_IP_ADDRESS?? ??HOST_NAME??
      
      This command adds the LPAR hostname and its IP address entry to the NIM server's /etc/hostfile so that the NIM server can resolve LPAR with the hostname.

      Note

      If the NIM server fails to contact LPAR with the hostname, you must make this entry.

You now have two options, depending whether the customer NIC is set to DHCP or Static.

To configure the first boot script if the NIC is set to DHCP

If the customer NIC is set to DHCP, perform the following steps:

1. Click the Agent Install/First boot script tab.

2. In First boot script, add a script that enables the customer NIC that is set for DHCP.
   For example:

   echo interface en1 >> /etc/dhcpcd.ini
   echo { >> /etc/dhcpcd.ini
   echo option 19 0 >> /etc/dhcpcd.ini
   echo  option 20 0 >> /etc/dhcpcd.ini
   echo  option 27 0 >> /etc/dhcpcd.ini
   echo option 29 0 >> /etc/dhcpcd.ini
   echo option 30 0 >> /etc/dhcpcd.ini
   echo option 31 0 >> /etc/dhcpcd.ini
   echo option 34 0 >> /etc/dhcpcd.ini
   echo option 36 0 >> /etc/dhcpcd.ini
   echo option 39 0 >> /etc/dhcpcd.ini
   echo } >> /etc/dhcpcd.ini
   
   cat /etc/rc.d/rc | grep -v exit > /etc/rc.d/sk
   echo startsrc -s dhcpcd >> /etc/rc.d/sk
   echo exit 0 >> /etc/rc.d/sk
   mv /etc/rc.d/sk /etc/rc.d/rc
   chmod 544 /etc/rc.d/rc
   

To configure the first boot script if the NIC is set to Static

If the customer NIC is set to Static, perform the following steps:

1. Click the Local Properties tab.
2. Create the following local properties:
   • ETH1_IPADDR (for the IP address)
   • ETH1_NETMASK (for the subnet mask)
   • ETH1_GATEWAY (for gateway)
     You use these local properties with the boot script.
3. Click the Agent Install/First boot script tab.

4. In First boot script, add a script that enables the customer NIC that is Static.
   For example:

   mktcpip -h ??HOST_NAME?? -a ??ETH1_IPADDR?? -m ??ETH1_NETMASK?? -i en1 -n DNS Server -d Domain Name -g ??ETH1_GATEWAY?? -s -C 0 -A no
   

   All these local properties are replaced by values assigned by BMC Network Automation.
   For example:

   mktcpip -h LPARSKSK-1 -a 10.128.243.58 -m 255.255.255.192 -i en1 -n 137.72.16.1 -d bmc.com -g 10.128.243.62 -s -C 0 -A no
   

Where to go from here

After you configure the packages, you need to publish them to the Product Catalog for use by BMC Cloud Lifecycle Management. See Publishing the Product Catalog.