Dell PowerStore 5200T EMC PowerStore Host Configuration Guide - Page 90

Considerations for Boot from SAN with PowerStore

Get Dell PowerStore 5200T PDF manuals and user guides View all Dell PowerStore 5200T manuals
Add to My Manuals
Save this manual to your list of manuals

Page 90 highlights

A Considerations for Boot from SAN with PowerStore This appendix provides considerations for configuring boot from SAN with PowerStore. Topics: • Consideration for Boot from SAN with PowerStore Consideration for Boot from SAN with PowerStore NOTE: See your operating system documentation for general boot from SAN configuration guidelines. NOTE: The current PowerStore OS release does not support mapping individual LUNs to host under a host group. Follow these guidelines when configuring boot from SAN: ● Manually register your HBAs with PowerStore and create a host. ● Create the boot volume. ● Map the created boot volume to the host. ● Use the path that owns the volume (Node A or Node B). ○ The lowest-numbered path to the boot LUN must be the active path. ● It is recommended to assign the boot LUN with Host LUN ID 0. During the installation procedure, it is recommended that only one LUN be mapped to a host for ease of use. ○ Once the installation is complete, additional LUNs may be mapped to the host. Follow these guidelines for clustered boot from SAN mapping: ● For every physical host, there should be one host in the PowerStore manager. Do not create a host group. ● Boot LUNs are mapped only for the specific host. ● Shared LUNs are mapped to all hosts in the cluster. The user must keep the same LUN ID across the cluster for shared LUNs. When migrating a boot volume, using the PowerStore native migration tool, follow these guidelines: ● Power off the connected host before the migration; after the boot LUN ID is successfully changed, power it back on . ● It is recommended to assign the boot LUN with HOST LUN ID 0. ● When a volume is migrated from one PowerStore appliance to another appliance in the same cluster using the native migration tool, the LUN ID number changes automatically. ● After migrating a boot from SAN volume, the LUN ID number can be changed back to 0. ● Perform the following steps to change the boot LUN ID: 1. On the PowerStore Manager of the destination appliance, select Storage > Volumes. 2. Click the name of the boot volume and select the Host Mapping tab. 3. Click the checkbox next to the boot volume name and select MORE ACTIONS > Edit Logical Unit Number. NOTE: Changing the LUN ID number is a disruptive operation. The following message is displayed before changing the number: Changing the Logical Unit Number of the host will disrupt its access to the volume until a host-side rescan is performed. 90 Considerations for Boot from SAN with PowerStore

  • 1
  • 2
  • 3
  • 4
  • 5
  • 6
  • 7
  • 8
  • 9
  • 10
  • 11
  • 12
  • 13
  • 14
  • 15
  • 16
  • 17
  • 18
  • 19
  • 20
  • 21
  • 22
  • 23
  • 24
  • 25
  • 26
  • 27
  • 28
  • 29
  • 30
  • 31
  • 32
  • 33
  • 34
  • 35
  • 36
  • 37
  • 38
  • 39
  • 40
  • 41
  • 42
  • 43
  • 44
  • 45
  • 46
  • 47
  • 48
  • 49
  • 50
  • 51
  • 52
  • 53
  • 54
  • 55
  • 56
  • 57
  • 58
  • 59
  • 60
  • 61
  • 62
  • 63
  • 64
  • 65
  • 66
  • 67
  • 68
  • 69
  • 70
  • 71
  • 72
  • 73
  • 74
  • 75
  • 76
  • 77
  • 78
  • 79
  • 80
  • 81
  • 82
  • 83
  • 84
  • 85
  • 86
  • 87
  • 88
  • 89
  • 90
  • 91
  • 92
  • 93
Considerations for Boot from SAN with
PowerStore
This appendix provides considerations for configuring boot from SAN with PowerStore.
Topics:
•
Consideration for Boot from SAN with PowerStore
Consideration for Boot from SAN with PowerStore
NOTE:
See your operating system documentation for general boot from SAN configuration guidelines.
NOTE:
The current PowerStore OS release does not support mapping individual LUNs to host under a host group.
Follow these guidelines when configuring boot from SAN:
●
Manually register your HBAs with PowerStore and create a host.
●
Create the boot volume.
●
Map the created boot volume to the host.
●
Use the path that owns the volume (Node A or Node B).
○
The lowest-numbered path to the boot LUN must be the active path.
●
It is recommended to assign the boot LUN with Host LUN ID 0. During the installation procedure, it is recommended that
only one LUN be mapped to a host for ease of use.
○
Once the installation is complete, additional LUNs may be mapped to the host.
Follow these guidelines for clustered boot from SAN mapping:
●
For every physical host, there should be one host in the PowerStore manager. Do not create a host group.
●
Boot LUNs are mapped only for the specific host.
●
Shared LUNs are mapped to all hosts in the cluster. The user must keep the same LUN ID across the cluster for shared
LUNs.
When migrating a boot volume, using the PowerStore native migration tool, follow these guidelines:
●
Power off the connected host before the migration; after the boot LUN ID is successfully changed, power it back on .
●
It is recommended to assign the boot LUN with HOST LUN ID 0.
●
When a volume is migrated from one PowerStore appliance to another appliance in the same cluster using the native
migration tool, the LUN ID number changes automatically.
●
After migrating a boot from SAN volume, the LUN ID number can be changed back to 0.
●
Perform the following steps to change the boot LUN ID:
1.
On the PowerStore Manager of the destination appliance, select
Storage
>
Volumes
.
2.
Click the name of the boot volume and select the
Host Mapping
tab.
3.
Click the checkbox next to the boot volume name and select
MORE ACTIONS
>
Edit Logical Unit Number
.
NOTE:
Changing the LUN ID number is a disruptive operation. The following message is displayed before changing the
number: Changing the Logical Unit Number of the host will disrupt its access to the volume until a host-side rescan is
performed.
A
90
Considerations for Boot from SAN with PowerStore