Dell PowerVault NX3610 User Manual - Page 20

Migrating Clients To Another Controller, Setting The Migration Policy, Assigned Controller

Get Dell PowerVault NX3610 PDF manuals and user guides View all Dell PowerVault NX3610 manuals
Add to My Manuals
Save this manual to your list of manuals

Page 20 highlights

The Client Connections page is displayed. By default, the Clients tab displays a list of all the client connections. 2. Select the appropriate filters in the Protocols and Controller lists. The client connections table displays the events depending on the parameters selected. 3. To sort the client connections, click the column headings of the client connections table. Migrating Clients To Another Controller If there is an imbalance in the network load, the system can rebalance the load by migrating clients between controllers, either automatically or manually. Choose whether the clients or routers in the list may be migrated to other controllers. 1. Select Monitor→ Load Balancing→ Client Connections. The Client Connections page is displayed. By default, the Clients tab displays a list of all the client connections. 2. In the client connections table, select one or more client connections that you want to migrate and click Assign Interface. The Assign Interface page is displayed. 3. In Move to, choose a specific controller as the target or choose Assigned Controller. - To migrate all the selected clients to a specific controller, choose a specific controller from the list. - To migrate all the selected clients back to their original controllers after a failed controller is revived, choose the Assigned Controller. Each client can have a different assigned controller. 4. In Interface, choose the appropriate target interface or allow the system to assign the target interface on the controller automatically. CAUTION: This operation disconnects CIFS connections if they are migrated to a different controller. 5. To enable Automatic Rebalance, select Allow these clients to migrate to other controllers when rebalancing the network load. 6. Click Assign. Setting The Migration Policy In case of a controller failure, the system automatically migrates each connection from the failed controller to another controller. This causes disconnections to CIFS clients, unless the Migrate Manually policy has been selected for CIFS. However, selection of this option requires you to manually migrate clients. Migration of CIFS clients in any circumstance, will interrupt I/O. Click the Windows Cancel button, and retry the transfer. When the failed controller restarts, the system rebalances the load by migrating clients back to the revived controller automatically. This operation is called fail-back. Clients that use NFS are stateless and are not affected during fail-back. To optimize the fail-back operation, the system provides you with the following policies for migration on recovery: • Migrate Immediately - Always keeps the system well balanced, at the cost of possibly disconnecting CIFS clients during work time. • Migrate Automatically - Always keeps the system well balanced if the controller failure is very short, at the cost of disconnecting CIFS clients. This option causes the system to remain unbalanced for a period of several days, if the failure remains for a long time. This mode overcomes short controller failures because clients have not created new material during the short time failure. Therefore, the best practice is to rebalance them as soon as possible. If the failure is longer than 10 minutes, the system remains unbalanced until you rebalance it manually. • Migrate Manually - Never migrates clients automatically. This requires manual intervention to rebalance the system. If the system requires manual intervention to rebalance it after fail-over, the system sends an appropriate email message to the administrator. To set the migration policies: 20

  • 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
The
Client Connections
page is displayed. By default, the
Clients
tab displays a list of all the client connections.
2.
Select the appropriate filters in the
Protocols
and
Controller
lists.
The client connections table displays the events depending on the parameters selected.
3.
To sort the client connections, click the column headings of the client connections table.
Migrating Clients To Another Controller
If there is an imbalance in the network load, the system can rebalance the load by migrating clients between controllers,
either automatically or manually. Choose whether the clients or routers in the list may be migrated to other controllers.
1.
Select
Monitor
→
Load Balancing
→
Client Connections
.
The
Client Connections
page is displayed. By default, the
Clients
tab displays a list of all the client connections.
2.
In the client connections table, select one or more client connections that you want to migrate and click
Assign
Interface
.
The
Assign Interface
page is displayed.
3.
In
Move to
, choose a specific controller as the target or choose
Assigned Controller
.
–
To migrate all the selected clients to a specific controller, choose a specific controller from the list.
–
To migrate all the selected clients back to their original controllers after a failed controller is revived,
choose the Assigned Controller. Each client can have a different assigned controller.
4.
In
Interface
, choose the appropriate target interface or allow the system to assign the target interface on the
controller automatically.
CAUTION: This operation disconnects CIFS connections if they are migrated to a different controller.
5.
To enable
Automatic Rebalance
, select
Allow these clients to migrate to other controllers when rebalancing the
network load
.
6.
Click
Assign
.
Setting The Migration Policy
In case of a controller failure, the system automatically migrates each connection from the failed controller to another
controller. This causes disconnections to CIFS clients, unless the
Migrate Manually
policy has been selected for CIFS.
However, selection of this option requires you to manually migrate clients. Migration of CIFS clients in any
circumstance, will interrupt I/O. Click the Windows
Cancel
button, and retry the transfer. When the failed controller
restarts, the system rebalances the load by migrating clients back to the revived controller automatically. This operation
is called fail-back.
Clients that use NFS are stateless and are not affected during fail-back. To optimize the fail-back operation, the system
provides you with the following policies for migration on recovery:
•
Migrate Immediately
— Always keeps the system well balanced, at the cost of possibly disconnecting CIFS
clients during work time.
•
Migrate Automatically
— Always keeps the system well balanced if the controller failure is very short, at the
cost of disconnecting CIFS clients. This option causes the system to remain unbalanced for a period of several
days, if the failure remains for a long time.
This mode overcomes short controller failures because clients have not created new material during the short
time failure. Therefore, the best practice is to rebalance them as soon as possible. If the failure is longer than 10
minutes, the system remains unbalanced until you rebalance it manually.
•
Migrate Manually
— Never migrates clients automatically. This requires manual intervention to rebalance the
system. If the system requires manual intervention to rebalance it after fail-over, the system sends an
appropriate email message to the administrator.
To set the migration policies:
20