Dell PowerVault NX3500 Administrator's Guide - Page 143

Detaching the PowerVault NX3500 Controller, System, Management, Network, Subnets, Primary, Console VIP

Page 143 highlights

Detaching the PowerVault NX3500 Controller In order to bring the cluster into the single-controller mode you need to detach a controller while any hardware is being replaced. This ensures that the system can be brought back to service with minimal downtime. You may have to detach the controller under the following circumstances: • A controller needs to be replaced with a new standby controller. • A controller needs to be repaired, possibly after replacing some components. • The administrator wants to attach a working controller to another (more critical) cluster. • The administrator wants to discard the cluster (for example, in order to use the standby controllers to create a new cluster elsewhere). To detach a controller: 1 Log in to the CLI using the management access VIP address. To obtain this address, in the NAS Manager, go to the System Management tab and click NetworkSubnetsPrimaryManagement Console VIP. 2 Execute the following command: system maintenance controllers detach start -nosaveConf NOTE: Depending on the configuration and the controller being detached, you may have to disconnect and reboot the system. This will only occur if the controller being detached is the primary controller being accessed by the CLI. If a controller was alive and working prior to initiating the detach procedure, it will be shut down and upon reboot it will appear as a standby controller. In the case of a failed controller, the system adjusts in a manner that allows the connection of a new controller. Maintaining the PowerVault NX3500 143

  • 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

Maintaining the PowerVault NX3500
143
Detaching the PowerVault NX3500 Controller
In order to bring the cluster into the single-controller mode you need to
detach a controller while any hardware is being replaced. This ensures that
the system can be brought back to service with minimal downtime.
You may have to detach the controller under the following circumstances:
A controller needs to be replaced with a new standby controller.
A controller needs to be repaired, possibly after replacing some
components.
The administrator wants to attach a working controller to another (more
critical) cluster.
The administrator wants to discard the cluster (for example, in order to
use the standby controllers to create a new cluster elsewhere).
To detach a controller:
1
Log in to the CLI using the management access VIP address.
To obtain this address, in the NAS Manager, go to the
System
Management
tab and click
Network
Subnets
Primary
Management
Console VIP
.
2
Execute the following command:
system maintenance controllers detach start
<
controllerID
> -nosaveConf
NOTE:
Depending on the configuration and the controller being detached,
you may have to disconnect and reboot the system. This will only occur if the
controller being detached is the primary controller being accessed by the CLI.
If a controller was alive and working prior to initiating the detach
procedure, it will be shut down and upon reboot it will appear as a standby
controller. In the case of a failed controller, the system adjusts in a manner
that allows the connection of a new controller.