Determining the system IDs of the replacement controller modules
After you have replaced all hardware at the disaster site, you must determine the system ID of the newly installed storage controller module or modules.
About this task
You must perform this procedure with the replacement controller modules in Maintenance mode.
This section provides examples for four-node configurations. For eight-node configurations, you must account for the additional nodes on the second DR group. The examples make the following assumptions:
Site A is the disaster site.
node_A_1 has been replaced.
node_A_2 has been replaced.
Present only in four-node MetroCluster configurations.
Site B is the surviving site.
node_B_1 is healthy.
node_B_2 is healthy.
Present only in four-node MetroCluster configurations.
The examples in this procedure use controllers with the following system IDs:
| Number of nodes in MetroCluster configuration | Node | Original system ID | New system ID | Will pair with this node as DR partner |
|---|---|---|---|---|
| Four | node_A_1 | 4068741258 | 1574774970 | node_B_1 |
| node_A_2 | 4068741260 | 1574774991 | node_B_2 | |
| node_B_1 | 4068741254 | unchanged | node_A_1 | |
| node_B_2 | 4068741256 | unchanged | node_A_2 |
Note
In a four-node MetroCluster configuration, the system determines DR partnerships by pairing the node with the lowest system ID at site_A and the node with the lowest system ID at site_B. Because the system IDs change, the DR pairs might be different after the controller replacements are completed than they were prior to the disaster.
In the preceding example:
node_A_1 (1574774970) will be paired with node_B_1 (4068741254)
node_A_2 (1574774991) will be paired with node_B_2 (4068741256)
Give documentation feedback