4.2.2 Promoting the DR NOAM from Secondary to Primary (Outage)

Perform the following steps in DR NOAM to promote the DR NOAM from Secondary to Primary:

1. Establish an SSH session to the SDS/DSR DR NOAM XMI IP address, access the command prompt (CLI) and log in to the server as admusr user.

   msvnc-sds-NO-b login: admusr
   Password: <admusr_password>

2. To check NOAM Status of the server, run the following command on the Active NOAM.

   $ ha.mystate
   [admusr@msvnc-sds-NO-b ~]$ ha.mystate

   
   

   

   
   
3. Verify that the current value for myClusterRole is Secondary.

   [admusr@mrsvnc-sds-NO-b ~]$ top.myrole
   myNodeId=A1103.165
   myParentClusters=( A0907 )
   myClusterRole=Secondary
   myRecognizedPrimary=A0907
   myRecognizedSecondary=A1103
   [admusr@mrsvnc-sds-NO-b ~]$

4. Using the clusterId of the myRecognizedPrimary from the previous step, set the clusterId to Secondary.

   [admusr@mrsvnc-sds-NO-b ~]$ top.setSecondary A0907
   - New Secondary Timestamp: 03/03/17 18:28:48.318
   - Updating To A0907.060: rlghnc-sds-NO-asetSecondaryTo(A0907) returned proxy error=28
   SOAP 1.2 fault SOAP-ENV:Receiver [no subcode]
   "Connection timed out"Detail: connect failed in tcp_connect()
   
   - Updating To A0907.113: rlghnc-sds-QSsetSecondaryTo(A0907) returned proxy error=28
   SOAP 1.2 fault SOAP-ENV:Receiver [no subcode]
   "Connection timed out"Detail: connect failed in tcp_connect()
   
   - Updating To A0907.121: rlghnc-sds-NO-bsetSecondaryTo(A0907) returned proxy error=28
   SOAP 1.2 fault SOAP-ENV:Receiver [no subcode]
   "Connection timed out"Detail: connect failed in tcp_connect() 
   
   - Updating To A1103.165: mrsvnc-sds-NO-b- Updating To A1103.223: mrsvnc-sds-NO-a
   [admusr@mrsvnc-sds-NO-b ~]$

   Note:

   The connection timeouts to the Primary NOAM NE are expected when that NE is network isolated.

   Under these circumstances, the user should allow several minutes (≈ 7) for this command to complete.

5. Set the value for myClusterRole to Primary.

   [admusr@mrsvnc-sds-NO-b ~]$ top.setPrimary
   - Using my cluster: A1103
   - New Primary Timestamp: 03/03/17 18:35:26.279
   - Updating To A0907.060: rlghnc-sds-NO-asetPrimaryTo(A1103) returned proxy error=28
   SOAP 1.2 fault SOAP-ENV:Receiver [no subcode]
   "Connection timed out"
   Detail: connect failed in tcp_connect()
   
   - Updating To A0907.113: rlghnc-sds-QSsetPrimaryTo(A1103) returned proxy error=28
   SOAP 1.2 fault SOAP-ENV:Receiver [no subcode]
   "Connection timed out"
   Detail: connect failed in tcp_connect()
   
   - Updating To A0907.121: rlghnc-sds-NO-bsetPrimaryTo(A1103) returned proxy error=28
   SOAP 1.2 fault SOAP-ENV:Receiver [no subcode]
   "Connection timed out"
   Detail: connect failed in tcp_connect() 
   
   - Updating To A1103.165: mrsvnc-sds-NO-b
   - Updating To A1103.223: mrsvnc-sds-NO-a
   [admusr@mrsvnc-sds-NO-b ~]$

   Note:

   The connection timeouts to the Primary NOAM NE (shown in the output to the right) are expected when that NE is network isolated.

   Under these circumstances, the user should allow several minutes (≈ 7) for this command to complete.

6. Verify that the value for myClusterRole is now set to Primary.

   [admusr@mrsvnc-sds-NO-b ~]$ top.myrole
   myNodeId=A1103.165
   myParentClusters=(  )
   myClusterRole=Primary
   myRecognizedPrimary=A1103
   myRecognizedSecondary=A0907
   [admusr@mrsvnc-sds-NO-b ~]$

   Note:

   Perform the next steps on the New Primary NOAM VIP (former DR).
7. Launch an HTML5 compliant browser and connect to the XMI Virtual IP address (VIP) assigned to Primary Active NOAM site.
   If a Certificate Error is received, click on Continue to this website (not recommended) link.

   Figure 4-8 Certificate Error

   
   

   

   
   

   The login screen appears.

8. Log in to the GUI using a user account with administrator privileges.
   
   

   

   
   

   The Product Main Menu appears.

9. Verify that the message shown across the bottom of the panel indicates that the browser is using the VIP to connect to the ACTIVE NETWORK OAM&P.
   
   

   

   
   
10. Go to Main Menu, and then Administration, and then General Options.
    
    

    

    
    
11. Verify the value for Durability Administrative State.
    If performing this procedure in response to a network isolated Primary NOAM (outage), modify the Durability Administrative State value to 1 (if necessary).
    

    

    
    Click OK.
    

    

    
    
12. Go to Main Menu, and then Status & Manage, and then Server and identify the hostname of the Primary Active NOAM server from the banner message at the bottom of the browser window.
    
    

    

    
    

    Note:

    Based on the information recorded in this step, perform the next steps on the newly promoted Primary NOAM Active Server (Site_2).
13. Select the Server Hostname (highlighted once selected) and click Restart.
    
    

    

    
    Click Ok, in the pop-up confirmation box.
    

    

    
    

    Note:

    • For SDS systems, this procedure is completed. Return to NOAM Failover Process Flowchart for next steps.
    • For DSR systems only, perform the next steps in this procedure on the New Primary NOAM VIP (former DR).
14. Identify the clusterId values for the myRecognizedPrimary and the myRecognizedSecondary. For example, Axxxx.

    [admusr@dominica-dr-noam-b ~]$ top.myrole
    myNodeId=A0568.058
    myParentClusters=(  )
    myClusterRole=Primary
    myRecognizedPrimary=A0568
    myRecognizedSecondary=A1667
    [admusr@dominica-dr-noam-b ~]$

15. Record the clusterId values for the myRecognizedPrimary and the myRecognizedSecondary in the space provided.

    myRecognizedPrimary (clusterId) = ________________________
    myRecognizedSecondary (clusterId) = ________________________

16. Identify which A-Level clusterId (example, Axxxx) is located in the HaClusterResourceCfg table.

    [admusr@dominica-dr-noam-b ~]$ iqt -p HaClusterResourceCfg
    cluster resource optional
    A0568 DSROAM_Proc Yes
    C0804 DSROAM_Proc Yes
    C1223 DSROAM_Proc Yes
    C2346 DSROAM_Proc Yes
    C3147 DSROAM_Proc Yes
    C3316 DSROAM_Proc Yes
    [admusr@dominica-dr-noam-b ~]$

17. If the A-Level clusterId located in the HaClusterResourceCfg table is the myRecognizedPrimary value recorded in next step of this procedure, delete the entry.
    For example:

    $ irem HaClusterResourceCfg where "cluster='<myRecognizedPrimary_clusterId>'"
    [admusr@dominica-dr-noam-b ~]$ irem HaClusterResourceCfg where "cluster='A0568'"
    === deleted 1 records ===
    [admusr@dominica-dr-noam-b ~]$

    If the A-Level clusterId is not located in the table, continue to the next step.

18. Add an entry to the HaClusterResourceCfg table for the myRecognizedSecondary value recorded in Step 18 of this procedure.
    For example:

    $ echo "<myRecognizedSecondary_clusterId>|DSROAM_Proc|Yes" | iload -ha -xun -fcluster -fresource -foptional HaClusterResourceCfg
    [admusr@dominica-dr-noam-b ~]$ echo "A1667|DSROAM_Proc|Yes" | iload -ha -xun -fcluster -fresource -foptional HaClusterResourceCfg
    [admusr@dominica-dr-noam-b ~]$

19. Verify if the HaClusterResourceCfg table now displays an entry for the myRecognizedSecondary value recorded in Step 18 of this procedure.

    [admusr@dominica-dr-noam-b ~]$ iqt -p HaClusterResourceCfg
    cluster resource optional
    A1667 DSROAM_Proc Yes
    C0804 DSROAM_Proc Yes
    C1223 DSROAM_Proc Yes
    C2346 DSROAM_Proc Yes
    C3147 DSROAM_Proc Yes
    C3316 DSROAM_Proc Yes
    [admusr@dominica-dr-noam-b ~]$

    Note:

    Once this Procedure is completed, return to Figure 2-1.