EMC CX500I Configuration Guide - Page 111

RAID 3, LUN ID, SP owner, SP back-end loops buses., RAID Group ID

Get EMC CX500I - Insignia CLARiiON NAS Server PDF manuals and user guides View all EMC CX500I manuals
Add to My Manuals
Save this manual to your list of manuals

Page 111 highlights

Planning File Systems and LUNs RAID 3. If you want to use the SP memory for RAID 3, check the box. RAID Group/LUN Entries Complete a RAID Group/LUN entry for each LUN and hot spare. LUN ID. The LUN ID is a hexadecimal number assigned when you bind the disks into a LUN. By default, the ID of the first LUN bound is 0, the second 1, and so on. Each LUN ID must be unique within the storage system, regardless of its Storage Group or RAID Group. The maximum number of LUNs supported on one host bus adapter depends on the operating system. SP owner. Specify the SP that will own the LUN: SP A or SP B. You can let the management program automatically select the SP to balance the workload between SPs; to do so, leave this entry blank. SP back-end loops (buses). Each CX300 SP supports one physical loop that is paired with its counterpart SP to create a redundant loop (loop 0).. Each CX500/CX500i SP supports two physical loops that are paired with its counterpart SP to create four redundant loops (loop 0 and 1). Each CX700 SP supports four physical loops that are paired with its counterpart SP to create eight redundant loops (loop 0, 1, 2, and 3). Ideally, you will place the same amount of load on each loop. This may mean placing two or three heavily used LUNs on one loop, and six or eight lightly used LUNs on the other loop. The loop designation appears in the disk ID (form b-e-d, where b is the back-end loop number, e is the enclosure number, and d is the disk position in the enclosure. For example, 0-1-3 indicates the fourth disk on loop 0, in enclosure 1 (numbering 0, 1, 2, 3...from the left) in the storage system. RAID Group ID. This ID is a hexadecimal number assigned when you create the RAID Group. By default, the number of the first RAID Group in a storage system is 0, the second 1, and so on, up to the maximum of 1F (31). Planning Applications, LUNs, and Storage Groups 5-17

  • 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
  • 94
  • 95
  • 96
  • 97
  • 98
  • 99
  • 100
  • 101
  • 102
  • 103
  • 104
  • 105
  • 106
  • 107
  • 108
  • 109
  • 110
  • 111
  • 112
  • 113
  • 114
  • 115
  • 116
  • 117
  • 118
  • 119
  • 120
  • 121
  • 122
  • 123
  • 124
  • 125
  • 126
  • 127
  • 128
  • 129
  • 130
  • 131
  • 132
  • 133
  • 134
  • 135
  • 136
  • 137
  • 138
  • 139
  • 140
  • 141
  • 142
Planning Applications, LUNs, and Storage Groups
5-17
Planning File Systems and LUNs
RAID 3
. If you want to use the SP memory for RAID 3, check the
box.
RAID Group/LUN Entries
Complete a RAID Group/LUN entry for each LUN and hot spare.
LUN ID
. The LUN ID
is a hexadecimal number assigned when
you bind the disks into a LUN. By default, the ID of the first LUN
bound is 0, the second 1, and so on. Each LUN ID must be unique
within the storage system, regardless of its Storage Group or
RAID Group.
The maximum number of LUNs supported on one host bus
adapter depends on the operating system.
SP owner
. Specify the SP that will own the LUN: SP A or SP B.
You can let the management program automatically select the SP
to balance the workload between SPs; to do so, leave this entry
blank.
SP back-end loops (buses).
Each CX300 SP supports one physical
loop that is paired with its counterpart SP to create a redundant
loop (loop 0)..
Each CX500/CX500i SP supports two physical loops that are
paired with its counterpart SP to create four redundant loops
(loop 0 and 1).
Each CX700 SP supports four physical loops that are paired with
its counterpart SP to create eight redundant loops (loop 0, 1, 2,
and 3).
Ideally, you will place the same amount of load on each loop. This
may mean placing two or three heavily used LUNs on one loop,
and six or eight lightly used LUNs on the other loop. The loop
designation appears in the disk ID (form
b-e-d
, where
b
is the
back-end loop number,
e i
s the enclosure number, and
d
is the
disk position in the enclosure. For example, 0-1-3 indicates the
fourth disk on loop 0, in enclosure 1 (numbering 0, 1, 2,
3
...from
the left) in the storage system.
RAID Group ID
. This ID is a hexadecimal number assigned
when you create the RAID Group. By default, the number of the
first RAID Group in a storage system is 0, the second 1, and so on,
up to the maximum of 1F (31).