HP 3PAR StoreServ 7200 2-node HP 3PAR Command Line Interface Administrator& - Page 75

QLogic CNA in FCoE mode, HP 3PAR 4-port 4G FC

Page 75 highlights

stay online and host multipath software is not affected. The online software upgrade completes without any dependency on host multipath software. Persistent ports can also be used to ensure nondisruptive host I/O activity for planned and unplanned node down time, such as HBA firmware upgrades, adding or replacing HBAs, adding or replacing DIMMs, node failures, and cable or switch failures. NOTE: FC connections can support more than one partner port. iSCSI connections are limited to one partner port due to the limitations of IP failover. The following configuration requirements and limitations apply when using persistent ports for port-level failover: • The host port must be connected and zoned through fabric topology to a HP 3PAR storage system physical port. • The automatically-designated partner port must be connected to the same fabric as its partner port on the same switch. • The partner port does not have to be zoned to the host port. • Under normal conditions, a host port has a single I/O path to the storage array available. • If a partner port is zoned to the same host port as the primary port, the host port has two I/O paths to the storage array available. • The FC fabric used in the configuration must support NPIV. • Host-facing adapters on HP 3PAR storage systems used in the configuration must support NPIV. • FC adapters on hosts used in this configuration do not require NPIV support. • Port failover is only supported on target mode point to point port configurations. Persistent port failover is only supported on the following NPIV-compliant HBAs: • HP 3PAR 4-port 4G FC • Emulex 2-port 4G • Emulex 4-port 8G FC • QLogic CNA in FCoE mode • QLogic 1G iSCSI • QLogic CNA in 10G iSCSI mode Use the showport and showportdev commands to monitor the status of port failover and failback operations. The operating system assigns failover ports using a fixed mapping of N¹:S:P. N¹ uses the XOR operator; therefore N¹ = N XOR 1. For example, port 0:1:1 partners with port 1:1:1. This means that port 0:1:1 provides failover for 1:1:1 and port 1:1:1 provides failover for port 0:1:1. The showport command output includes Partner and FailoverState columns that display the partner port :: information and failover state information. FailoverState values represent the failover state of the two ports listed in the N:S:P and Partner columns. The FailoverState value can be one of the following: • none-No failover in operation. • failover_pending-In the process of failing over to partner. • failed_over-Failed over to partner. • active-The partner port is failed over to this port. • active_down-The partner port is failed over to this port, but this port is down. • failback_pending-In the process of failing back from partner. Using Persistent Ports for Nondisruptive Online Software Upgrades 75

  • 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
  • 143
  • 144
  • 145
  • 146
  • 147
  • 148
  • 149
  • 150
  • 151
  • 152
  • 153
  • 154
  • 155
  • 156
  • 157
  • 158
  • 159
  • 160
  • 161
  • 162
  • 163
  • 164
  • 165
  • 166
  • 167
  • 168
  • 169
  • 170
  • 171
  • 172
  • 173
  • 174
  • 175
  • 176
  • 177
  • 178
  • 179
  • 180
  • 181
  • 182
  • 183
  • 184
  • 185
  • 186
  • 187
  • 188
  • 189
  • 190
  • 191
  • 192
  • 193
  • 194
  • 195
  • 196
  • 197
  • 198
  • 199
  • 200
  • 201
  • 202
  • 203
  • 204

stay online and host multipath software is not affected. The online software upgrade completes
without any dependency on host multipath software.
Persistent ports can also be used to ensure nondisruptive host I/O activity for planned and unplanned
node down time, such as HBA firmware upgrades, adding or replacing HBAs, adding or replacing
DIMMs, node failures, and cable or switch failures.
NOTE:
FC connections can support more than one partner port. iSCSI connections are limited
to one partner port due to the limitations of IP failover.
The following configuration requirements and limitations apply when using persistent ports for
port-level failover:
The host port must be connected and zoned through fabric topology to a HP 3PAR storage
system physical port.
The automatically-designated partner port must be connected to the same fabric as its partner
port on the same switch.
The partner port does not have to be zoned to the host port.
Under normal conditions, a host port has a single I/O path to the storage array available.
If a partner port is zoned to the same host port as the primary port, the host port has two I/O
paths to the storage array available.
The FC fabric used in the configuration must support NPIV.
Host-facing adapters on HP 3PAR storage systems used in the configuration must support NPIV.
FC adapters on hosts used in this configuration do not require NPIV support.
Port failover is only supported on target mode point to point port configurations.
Persistent port failover is only supported on the following NPIV-compliant HBAs:
HP 3PAR 4-port 4G FC
Emulex 2-port 4G
Emulex 4-port 8G FC
QLogic CNA in FCoE mode
QLogic 1G iSCSI
QLogic CNA in 10G iSCSI mode
Use the
showport
and
showportdev
commands to monitor the status of port failover and failback
operations.
The operating system assigns failover ports using a fixed mapping of N¹:S:P. N¹ uses the XOR
operator; therefore N¹ = N XOR 1. For example, port 0:1:1 partners with port 1:1:1. This means
that port 0:1:1 provides failover for 1:1:1 and port 1:1:1 provides failover for port 0:1:1.
The
showport
command output includes
Partner
and
FailoverState
columns that display
the partner port <node>:<slot>:<port> information and failover state information.
FailoverState
values represent the failover state of the two ports listed in the
N:S:P
and
Partner
columns. The
FailoverState
value can be one of the following:
none—No failover in operation.
failover_pending—In the process of failing over to partner.
failed_over—Failed over to partner.
active—The partner port is failed over to this port.
active_down—The partner port is failed over to this port, but this port is down.
failback_pending—In the process of failing back from partner.
Using Persistent Ports for Nondisruptive Online Software Upgrades
75