Creating a configuration file automatically

When using Basic BOFM for the first time, you must create a configuration file in which you assign virtual addresses to each slot in each chassis.

The following example outlines the steps you might follow when creating a configuration file automatically. It does not apply to all BladeCenter environments. These example steps assume that you have a single domain (no addresses are duplicated).
  1. Log in to the AMM Web interface and select Open Fabric Manager in the left pane, under Blade Tasks. The Open Fabric Manager Configuration Management page opens in the right pane.
  2. Click Create an Initial Configuration. This opens the Specify Virtual Addresses page in the right pane.
  3. For the Ethernet Address Type, use the pull-down under Vendor and select IBM.
    Note: Another option for Vendor is User Defined.
  4. For the FC Address Type, use the pull-down under Vendor and select Emulex or QLogic.
  5. For the SAS Address Type, use the pull-down under Vendor and select LSI or IBM range.
  6. Click Advanced option and check the box next to Generate an FC target place holder or SAS target place holder.
  7. In the WWN field, enter the storage system WWPN.
    Note: Optionally, you can also specify a value in the LUN field.
  8. Click Next. This opens the Chassis to include page in the right pane.
  9. Click Next. You can optionally add to an existing BOFM configuration. You can specify an existing BOFM configuration file (CSV file) using the Browse button. This file is prepended to the newly generated BOFM configuration file that contains addresses that follow those in the existing specified file. This extends the existing BOFM domain. If you do not want the new BOFM configuration prepended to an existing configuration, do not specify any file name. Instead, click Next.
  10. On the Chassis to include page, there are two methods for providing the list of chassis to be included in the configuration file.

    You can either create a file with the list of AMM IP addresses or use the chassis that were discovered by the AMM via SLP. Before you click the Use AMM IP Addresses that were discovered on the AMM management network button, first use the Remote Chassis page with the SLP method to verify that all chassis on the page are those you want to configure BOFM. Otherwise, specify the chassis address list in a file as described below.

    If you elect to use an explicit list of AMM IP addresses instead, create a text file in which each line contains a single IP address or the hostname of a single chassis. If you use hostnames in this file, enable DNS and define at least one DNS server on the AMM Web interface Network Protocols page. When the text file is complete, you can then select the Use AMM IP Addresses in a file that I specify option on the Chassis to include page. Click Browse to locate the file that you created.
    Note: You can also use a valid existing BOFM configuration file to define the list of chassis.
  11. Click Next. The AMM generates the configuration file and displays The Configuration File Has Been Created page.
  12. The browser launches the File Save window allowing you to save the generated configuration file. If the File Save window does not appear, click Download the configuration file manually on The Configuration File Has Been Created page.
It is best practice to store the configuration file locally, and validate the new configuration. It is also important to store the configuration file in a safe location because this is your original copy of the BOFM configuration. If an AMM has a hardware failure and you don't have a standby AMM, this is your single source to reproduce the BOFM configuration.

To apply the configuration directly or to create a Requirements Report, you can do it directly from this page.

When you complete the Specify Virtual Addresses page, consider the following information: