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

Best Practices for Storage Connectivity, General SAN Guidelines, Using LUN 0 with PowerStore

Page 9 highlights

2 Best Practices for Storage Connectivity This chapter contains the following topics: Topics: • General SAN Guidelines • Fibre Channel SAN Guidelines • NVMe/FC SAN Guidelines • iSCSI SAN Guidelines • NVMe over TCP (NVMe/TCP) SAN Guidelines • NVMe-oF General Guidelines • SAN Connectivity Best Practices General SAN Guidelines This section provides general guidelines for storage connectivity. NOTE: This document describes mainly the storage-specific recommendations for PowerStore. It is recommended to always consult with the OS documentation for the up-to-date guidelines specific for the used operating system. NOTE: In hosts running a hypervisor, such as VMware ESXi, Microsoft Hyper-V or any clustering software, it is important to ensure that the logical unit numbers of PowerStore volumes are consistent across all hosts in the hypervisor cluster. Inconsistent LUNs may affect operations such as VM online migration or VM power-up. Using LUN 0 with PowerStore The PowerStore system exposes a Storage Array Controller Device (SACD) by default. The device is exposed with a LUN ID 0. ● A user may choose to override the SACD with a real storage device (such as a volume or a clone), by setting the device LUN ID to 0. ● Doing so may require the user to manually force a host rescan to discover that device. For instructions on forcing a host rescan, see the operating system vendor documentation. Using LUNs 254 and 255 with PowerStore ● PowerStore appliances expose for vSphere Virtual Volumes LUN 254, 255. ● The LUNs are not 'real' LUNs, and cannot be used for any volume mapping. ● The LUNs represent the Virtual Volume Physical Endpoint (PE). Best Practices for Storage Connectivity 9

  • 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

Best Practices for Storage Connectivity
This chapter contains the following topics:
Topics:
General SAN Guidelines
Fibre Channel SAN Guidelines
NVMe/FC SAN Guidelines
iSCSI SAN Guidelines
NVMe over TCP (NVMe/TCP) SAN Guidelines
NVMe-oF General Guidelines
SAN Connectivity Best Practices
General SAN Guidelines
This section provides general guidelines for storage connectivity.
NOTE:
This document describes mainly the storage-specific recommendations for PowerStore. It is recommended to
always consult with the OS documentation for the up-to-date guidelines specific for the used operating system.
NOTE:
In hosts running a hypervisor, such as VMware ESXi, Microsoft Hyper-V or any clustering software, it is important
to ensure that the logical unit numbers of PowerStore volumes are consistent across all hosts in the hypervisor cluster.
Inconsistent LUNs may affect operations such as VM online migration or VM power-up.
Using LUN 0 with PowerStore
The PowerStore system exposes a Storage Array Controller Device (SACD) by default. The device is exposed with a LUN ID 0.
A user may choose to override the SACD with a real storage device (such as a volume or a clone), by setting the device LUN
ID to 0.
Doing so may require the user to manually force a host rescan to discover that device. For instructions on forcing a host
rescan, see the operating system vendor documentation.
Using LUNs 254 and 255 with PowerStore
PowerStore appliances expose for vSphere Virtual Volumes LUN 254, 255.
The LUNs are not 'real' LUNs, and cannot be used for any volume mapping.
The LUNs represent the Virtual Volume Physical Endpoint (PE).
2
Best Practices for Storage Connectivity
9