The following examples illustrate problems with the current backup sequence and how to correct them.
Example 1 - Changing the backup sequence when primary node is ok
Table 1 shows a four-node environment where the current backup sequence does not reflect the desired behavior in the event of a switch. Also, the relative order of the configured backup sequence does not match the relative order of either the current sequence or the desired sequence.
|
Desired Order |
Initial Values, Example 1 Work with Node Entries |
|---|---|
|
Status View
-----------Current--------------- Opt Node Role Sequence Data Provider __ ________ __ NODEA *PRIMARY *PRIMARY __ NODEB *BACKUP 1 *PRIMARY __ NODED *BACKUP 2 *PRIMARY __ NODEC *BACKUP 3 *PRIMARY
|
|
Configured View
-----------Configured------------ Opt Node Role Sequence Data Provider __ ________ __ NODEA *PRIMARY *PRIMARY __ NODEC *BACKUP 1 *PRIMARY __ NODEB *BACKUP 2 *PRIMARY __ NODED *BACKUP 3 *PRIMARY |
Each row in Table 2 shows a change to be made to the nodes on the configured view of the Work with Node Entries display. The rows are in the order that the changes need to occur to correct this example configuration to the desired order.
|
Node to Change |
Change To |
Effect on Configured Order, Example 1 |
Notes |
|---|---|---|---|
|
NODEB |
Role = *BACKUP Position = *FIRST |
Configured View
-----------Configured------------ Opt Node Role Sequence Data Provider __ ________ __ NODEA *PRIMARY *PRIMARY __ NODEB *BACKUP 1 *PRIMARY __ NODEC *BACKUP 2 *PRIMARY __ NODED *BACKUP 3 *PRIMARY
|
Intermediate step |
|
NODED |
Role = *BACKUP Position = *FIRST |
Configured View -----------Configured------------ Opt Node Role Sequence Data Provider _ ________ _ NODEA *PRIMARY *PRIMARY _ NODED *BACKUP 1 *PRIMARY _ NODEB *BACKUP 2 *PRIMARY _ NODEC *BACKUP 3 *PRIMARY |
Desired configuration but it is not effective until STRAG ROLE (*CONFIG) is performed. |
Example 2 - Correcting the configured primary node and changing the backup sequence
Table 3 shows a four-node environment where the current backup sequence does not reflect the desired behavior in the event of a switch. Also, the current and configured primary node do not match. The configured primary node must be corrected first, before attempting to correct any backup node sequence problems.
|
Desired Order |
Initial Values, Example 2 Work with Node Entries |
|---|---|
|
Status View
-----------Current--------------- Opt Node Role Sequence Data Provider __ ________ __ NODEA *PRIMARY *PRIMARY __ NODEB *BACKUP 1 *PRIMARY __ NODED *BACKUP 2 *PRIMARY __ NODEC *BACKUP 3 *PRIMARY
|
|
Configured
View -----------Configured------------ Opt Node Role Sequence Data Provider __ ________ __ NODEB *PRIMARY *PRIMARY __ NODEC *BACKUP 1 *PRIMARY __ NODEA *BACKUP 2 *PRIMARY __ NODED *BACKUP 3 *PRIMARY |
Each row in Table 4 shows a change to be made to the nodes on the configured view of the Work with Node Entries display. The rows are in the order that the changes need to occur to correct this example configuration to the desired order.
|
Node to Change |
Change To |
Effect on Configured Order, Example 2 |
Notes |
|---|---|---|---|
|
NODEB |
Role = *BACKUP Position = *FIRST |
Configured View -----------Configured------------ Opt Node Role Sequence Data Provider _ ________ _ NODEB *BACKUP 1 *PRIMARY _ NODEC *BACKUP 2 *PRIMARY _ NODEA *BACKUP 3 *PRIMARY _ NODED *BACKUP 4 *PRIMARY
|
Intermediate step |
|
NODEA |
Role = *PRIMARY |
Configured View
-----------Configured------------ Opt Node Role Sequence Data Provider __ ________ _ NODEA *PRIMARY *PRIMARY _ NODEB *BACKUP 1 *PRIMARY _ NODEC *BACKUP 2 *PRIMARY _ NODED *BACKUP 3 *PRIMARY
|
Intermediate step, corrects configured *PRIMARY. The sequence number for Backup 3 may appear as 4. The relative order is equivalent. |
|
NODED |
Role = *BACKUP Position = *FIRST |
Configured View
-----------Configured------------ Opt Node Role Sequence Data Provider __ ________ __ NODEA *PRIMARY *PRIMARY _ NODED *BACKUP 1 *PRIMARY _ NODEB *BACKUP 2 *PRIMARY _ NODEC *BACKUP 3 *PRIMARY
|
Desired configuration but it is not effective until STRAG ROLE (*CONFIG) is performed. |