Implementation Guide › Installing CA Enterprise Log Manager › Installation Considerations for a System with SAN Drives › Install with Enabled SAN Drives

Install with Enabled SAN Drives

The topic, Example: Set Up SAN Storage for CA Enterprise Log Manager, includes the recommendation to disable the SAN drives (LUNs) before installing the operating system on the CA Enterprise Log Manager appliance.

An alternative is to leave the SAN drives enabled but to modify the kick-start file, ca-elm-ks.cfg, with an ISO editing tool, after starting the operating system installation. The modification helps ensure that the install and boot are done from the local hard disk, not from the SAN.

To boot from the local disk (not SAN)

1. Boot the server with the OS installation DVD
2. Respond to the first prompt for keyboard type.
3. Press Alt-F2 to display the Anaconda/Kickstart prompt.
4. Type the following:

   list-hardrives
   

   The list of available drives displays, where the list resembles the following:

   cciss/c0d0 - 68GB RAID 1 (cciss is HP Smart Array)
   Sda - 500GB SAN  (sda - h is the SAN Multipathed) 
   Sdb - 500GB SAN
   Sdc - 500GB SAN
   Sdd - 500GB SAN
   Sde - 500GB SAN
   Sdf - 500GB SAN
   Sdg - 500GB SAN
   Sdh - 500GB SAN
   

5. Identify the local hard drive. In this case, it is cciss/c0d0.
6. Take the following steps:
   1. Open the CA Enterprise Log Manager operating system kickstart file, ca-elm-ks.cfg for edit. Use an ISO editor.
   2. Locate the following line to edit:

      bootloader --location=mbr --driveorder=sda,sdb
      

      Change it to the following:

      bootloader --location=mbr --driveorder=cciss/c0d0
      

      This change specifies to boot from the local disk only.

   3. Locate the following lines to edit:

      clearpart --all --initlabel
      part /boot --fstype "ext3" --size=100 
      part pv.4 --size=0 -grow
      

      Change these lines to the following:

      part /boot --fstype "ext3" --size=100 --ondisk cciss/c0d0
      part pv.4 --size=0 --grow --ondisk cciss/c0d0
      

      This change to the partition definition lines helps ensure that the partitions are created on the cciss/c0d0 disk by name. Using --ondisk, replaces the existing $disk1 and $disk2 variables.

   4. If appropriate for your case, remove the IF/When clause for the number of disk drives, retaining only the first set of disk commands (lines 57 - 65).
   5. Save the new ISO image.
7. Exit the Anaconda prompt to return to the operating system installation prompts.
8. Continue with the installation, using the documented procedures.