6.2.1 RBAR Feature Deactivation

Feature Deactivation

This section provides the detailed steps of the RBAR deactivation procedures.

1. Log in to the SOAM VIP GUI. Establish a GUI session on the SOAM server by using the VIP address of the SOAM server. Open the web browser and enter the URL http://<Active_SOAM_IP_Address>
2. Log in as the guiadmin user.

   Figure 6-9 Oracle System Login

   
   

   

   
   
3. Disable RBAR application, browse to Maintenance folder under Diameter and select Applications.

   Figure 6-10 RBAR Applications

   
   

   

   
   
4. Select the RBAR applications to disable and click Disable.

   Figure 6-11 Disable

   
   

   

   
   
5. Click OK to confirm.

   Figure 6-12 Shut Down

   
   

   

   
   
6. Log out of any active NOAM and/or SOAM GUI sessions.

   Figure 6-13 Logout

   
   

   

   
   
7. Establish a SSH session to the NOAM VIP. Log in as admusr.
8. Navigate to the feature activation directory by running the command $ cd /usr/TKLC/dsr/prod/maint/loaders/
9. In the NOAM VIP GUI, run the feature activation script by running the following command:$ ./featureActivateDeactivate

   Select Deactivate.

   Figure 6-14 Deactivate

   
   

   

   
   

   Select RBAR.

   Figure 6-15 RBAR Feature

   
   

   

   
   

   Select the SOAM site for which the application will be deactivated:

   Note:

   As an alternative, you can also deactivate on all SOAM sites:

   Figure 6-16 Feature Deactivation

   
   

   

   
   

   Refer to Sample Output of De-Activation (Active NOAM) for output example.

10. Log in to the active SOAM GUI, establish a GUI session on the active SOAM server by using IP address of the SOAM server. Open the web browser and enter the URL http://<Active_SOAM_IP_Address>
11. Log in as the guiadmin user.

    Figure 6-17 Oracle System Login

    
    

    

    
    
12. In the active SOAM GUI, verify if the RBAR folder is not visible under Main Menu.
13. Repeat Step 10-12 for the standby SOAM.

    Note:

    If the verifications for the standby SOAM differ from the active SOAM, stop and contact My Oracle Support.
14. Repeat steps 10-12 for any spare SOAMs present.

    Note:

    If the verifications for the standby SOAM differ from the active SOAM, stop and contact My Oracle Support.
15. Log in to the SOAM VIP GUI. Establish a GUI session on the SOAM server by using the VIP address of the SOAM server. Open the web browser and enter the URL http://<Primary_SOAM_VIP_IP_Address>.
16. Log in as the guiadmin user.

    Figure 6-18 Oracle System Login

    
    

    

    
    
17. In the SOAM VIP GUI, restart the DA-MPs. During the feature deactivation procedure, you can execute this step in multiple iterations. This is dependent on the number of DA-MP servers within your system. Make a written record of the number of times the step was performed. It is recommended that no more than 50% of the DA-MPs be restarted at once. Expand Status & Manage folder and click Server.

    Figure 6-19 Server Folder

    
    

    

    
    
18. Select the desired DA-MPs, press Ctrl to select multiple DA-MPs at once. Click Restart.

    Figure 6-20 Restart

    
    

    

    
    

    Click OK to confirm.

    Verify if the server changes to the Err state and wait until it returns to the Enabled/Norm state.

    Repeat for the additional DA-MPs.

19. In the SOAM VIP GUI, verify the maintenance screen. Browse to Maintenance folder under Diameter and select Applications.

    Figure 6-21 Applications Folder

    
    

    

    
    

    Verify if the RBAR application is not present.

    If this procedure fails, contact My Oracle Support for assistance.