2,187
edits
Difference between revisions of "Installation (ESX)"
Jump to navigation
Jump to search
→HBA and SAN Operations: Added "VMFS / LUN Addition"
(→Build Notes: Added "Build Numbers") |
(→HBA and SAN Operations: Added "VMFS / LUN Addition") |
||
| Line 242: | Line 242: | ||
== HBA and SAN Operations == | == HBA and SAN Operations == | ||
=== VMFS / LUN Addition === | |||
The new LUN needs to be carved up and presented to all ESX's that should see it (normally all ESX's from a particular cluster). Once completed, follow the procedure below to add to the ESX's... | |||
# Pick ESX in cluster with lowest load | |||
# Go to '''Storage Adapters''', hit '''Rescan...''' and untick the ''Scan for New VMFS Volumes'' | |||
# Once scan has complete, go to '''Storage''', and hit '''Add Storage...''' | |||
# Click '''Next >''' to select ''Disk/LUN'' storage | |||
# Select the appropriate device and click '''Next >''' | |||
# Check the current disk layout (ie its blank if its meant to be) and click '''Next >''' | |||
# Give the datastore an appropriate name, and click '''Next >''' | |||
# Select an approriate block size (this limits maximum VMDK size), and click '''Next >''' | |||
# Review config and click '''Finish''' | |||
# On the remaining ESX's, go to '''Storage Adapters''', hit '''Rescan...''' (leave both boxes checked) | |||
=== SAN LUN ID === | === SAN LUN ID === | ||
The SAN LUN ID is used by SAN admin's to identify LUN's. It's not readily available from the GUI and has to be extracted from the vml file... | The SAN LUN ID is used by SAN admin's to identify LUN's. It's not readily available from the GUI and has to be extracted from the vml file... | ||