HP Dl180 Booting HP ProLiant servers from a storage area network

HP Dl180 - G6 E5504 2X2gb 4Lff Svr Manual

HP Dl180 manual content summary:

  • HP Dl180 | Booting HP ProLiant servers from a storage area network - Page 1
    Booting HP ProLiant servers from a storage area network HOWTO, 2nd edition Abstract...2 Required hardware ...2 Supported firmware versions ...2 Supported Fibre Channel switches ...2 Setting up LUN on HP StorageWorks arrays and zoning on Fibre Channel switches 3 Deploying the OS by CD overview ...3
  • HP Dl180 | Booting HP ProLiant servers from a storage area network - Page 2
    /products/servers/support/Boot_from_SAN_Fibre_Channel_Switch_Supp ort_Matrix.pdf lists which ProLiant servers are supported for Fibre Channel switch and HP StorageWorks array combination that supports booting from SAN. Verifying compatibility and support among system products can help avoid problems
  • HP Dl180 | Booting HP ProLiant servers from a storage area network - Page 3
    Windows Server x64 edition systems: http://h20000.www2.hp.com/bc/docs/support/SupportManual/c00099862/c00099862.pdf Deploying the OS by CD overview The following steps provide an overview a CD installation: 1. Download, but do not install, the latest HBA drivers, SmartStart, and the ProLiant Support
  • HP Dl180 | Booting HP ProLiant servers from a storage area network - Page 4
    which ProLiant servers and OSs are supported for Boot From SAN deployment with RDP. Refer to the three support manuals listed in the "Setting up LUN on HP StorageWorks arrays and zoning on Fibre Channel switches" section for important details about SAN configurations and minimum firmware versions
  • HP Dl180 | Booting HP ProLiant servers from a storage area network - Page 5
    write the line feeds correctly. 8. Execute the Write ProLiant ML/DL/BL QLogic HBA Configuration [server specific] job from the Server Deployment Toolbox\1 - Hardware Configuration\HBA job folder on the target server. 9. Execute the Deploy ProLiant BL System Configuration (Boot From SAN) job from the
  • HP Dl180 | Booting HP ProLiant servers from a storage area network - Page 6
    file. Setting up two paths to the LUN (for example, through both HBAs on a blade) will cause an OS failure due to a drive that is "unformatted, damaged, or After deploying the first server using scripting, you can deploy additional servers using imaging. To deploy a server with an embedded array
  • HP Dl180 | Booting HP ProLiant servers from a storage area network - Page 7
    refer to the resources listed below. Source Hyperlink HP StorageWorks SAN Design Reference Guide Regular Firmware Updates Essential for Optimal Performance and Functionality of HP ProLiant Servers http://h20000.www2.hp.com/bc/docs/support/SupportM anual/c00403562/c00403562.pdf http://h20000.www2
  • 1
  • 2
  • 3
  • 4
  • 5
  • 6
  • 7

Booting HP ProLiant servers from a storage
area network
HOWTO, 2
nd
edition
Abstract
..............................................................................................................................................
2
Required hardware
..............................................................................................................................
2
Supported firmware versions
.............................................................................................................
2
Supported Fibre Channel switches
.....................................................................................................
2
Setting up LUN on HP StorageWorks arrays and zoning on Fibre Channel switches
....................................
3
Deploying the OS by CD overview
........................................................................................................
3
Deploying the OS by Rapid Deployment Pack overview
...........................................................................
4
Before you start
................................................................................................................................
4
Instructions
......................................................................................................................................
4
Scripted installs
................................................................................................................................
6
Image deployment
...........................................................................................................................
6
For more information
............................................................................................................................
7
Call to action
......................................................................................................................................
7