A.11 Additional Backout Steps

This procedure provides the details about additional backout steps for NOAM, SOAM, and SBR server(s) to support backout for incremental upgrade release paths.

A.11 Server CLI: Log in to the Server

1. Use the SSH command (on UNIX systems – or putty if running on Windows) to log in to the server under backout:

   ssh admusr@<server address>

   password: <enter password>

   Answer yes if you are asked to confirm the identity of the server.

   If the server is NOAM or SOAM server, execute tasks 2 to 5 in this procedure and if server is SBR server, execute tasks 6. to 7. Please note down the host name of the server on which these steps are executed. Once all the servers in a server group will be backed out then the additional post-backout steps will be executed to revert back the changes done in this procedure.

A.11 Server CLI: Set the Resource as Optional for OAM Servers Only

1. Check for the resource:

   iqt -E HaResourceCfg where "name='<resource_name>'"

2. Execute this command:

   iset -W -foptional='Yes' HaResourceCfg where "name='DSROAM_Proc'"

   These commands change/update the results of some records.

   Note:

   Make sure the resource being set is in system. Some of the resources shown are introduced in different releases. If the resource is not in the system, presence check will not result any output records. In this case, skip updating these fields for the resource not in the system.

A.11 Server CLI: Restart the HTTPD Service (For OAM Servers Only)

1. Execute this command:

   sudo systemctl restart httpd.service

A.11 Active NOAM/SOAM Server CLI: Log in to the Server

1. Use the SSH command (on UNIX systems – or putty if running on Windows) to log in to the Active NOAM/SOAM server in the same server group, in which server is under backout:

   ssh admusr@<server address>

   password: <enter password>

   Answer yes if you are asked to confirm the identity of the server.

A.11 Server CLI: Verify that the Replication is Working Appropriately (For OAM Servers Only)

1. Execute this command on an active NOAM/SOAM server in the same server group being backed out:

   irepstat

2. Verify the irepstat command displays a replication row for the server which is being backed out.

   Note the replication status is Active before proceeding. If it is Audit, then wait until replication becomes Active.

   If this step is missed, data is lost and is unrecoverable.

   Example:

   Here Ford-B-NO is Active NOAM Server and Ford-A-NO is backed out.

   Ford-B-NO A3301.157 Ford-B-NO 09:32:17 [Rw]

   Policy 0 ActStb [DbReplication] ----------------------------------------

   AA To P0 Ford-A-NO Active 0 0.00 1%R 0.12%cpu 1.88k/s

   AA To P1 Chevy-DRNO-B Active 0 0.00 1%R 0.08%cpu 1.89k/s

   AB To D0 Camaro-SO-B Active 0 0.00 1%R 0.09%cpu 1.89k/s

   AB To D0 Nova-SO-B Active 0 0.00 1%R 0.08%cpu 1.90k/s

   AB To D0 Pinto-SO-B Active 0 0.00 1%R 0.10%cpu 1.89k/s

   AB To D0 Mustang-SO-B Active 0 0.00 1%R 0.10%cpu 2.14k/s

3. Press q if you want to exit the irepstat command output.
4. Execute irepstat again, if required.

A.11 Server CLI: Set the Resource as Optional (For SBR Servers Only)

1. If a resource is not in the system, presence check does not result in any output records. In this case, do not update the fields for the resource.

   Resource presence can be checked using:

   iqt -E HaResourceCfg where "name='<resource_name>'"

   For example:

   iqt -E HaClusterResourceCfg where "resource='uSbrRes'"

   Execute this command for Session SBR only:

   iset -W -foptional='Yes' HaResourceCfg where "name='pSbrSBaseRepl'"

   iset -W -foptional='Yes' HaClusterResourceCfg where "resource='uSbrRes'"

   iset -W -foptional='Yes' HaClusterResourceCfg where "resource='pSbrSessionRes'"

   Execute this command for Binding SBR only:

   iset -W -foptional='Yes' HaResourceCfg where "name='pSbrBBaseRepl'"

   iset -W -foptional='Yes' HaClusterResourceCfg where "resource='uSbrRes'"

   iset -W -foptional='Yes' HaResourceCfg where "name='pSbrBindingRes'"

   These commands change/update the results of some records.

   Note:

   Make sure the resource being set is in the system. Some of the resources listed below are introduced in different releases.

A.11 Server CLI: Verify that the Replication is Working Appropriately (For SBR Servers Only)

1. Execute this command on an active SBR server in the same server group as the server being backed out:

   irepstat

2. Verify the irepstat command displays a replication row for the server which is being backed out.

   Note the replication status is Active before proceeding, if it is Audit, then wait until replication becomes Active.

   If this step is missed, data is lost and is unrecoverable.

   Example:

   Here Pinto-SBR-2 is Active SBR Server and Pinto-SBR-1 is backed out.

   Also, on Binding SBR, resource will be pSbrBindingPolicy.

   And on Session SBR, resource will be pSbrSessionPolicy.

   Pinto-SBR-2 C3783.034 Pinto-SBR-2 13:39:38 [Rw]

   Policy 0 ActStb [DbReplication] ----------------------------------------

   BC From D0 Pinto-SO-B Active 0 0.10 ^0.10%cpu 67.0/s

   CC To P0 Pinto-SBR-1 Active 0 0.10 1%S 0.31%cpu 30.9/s

   CC To P1 Mustang-SBR-3 Active 0 0.10 1%S 0.28%cpu 39.6/s

   Policy 21 pSbrBindingPolicy [pSbrBBaseRepl] ----------------------------

   CC To P0 Pinto-SBR-1 Active 0 0.10 1%S 0.63%cpu 186k/s

   CC To P1 Mustang-SBR-3 Active 2 0.13 1%S 0.55%cpu 189k/s

3. Press q if you want to exit the irepstat command output.
4. Execute irepstat again, if required.