5.2.1 RBAR Feature Activation

Feature Activation

Detailed steps for RBAR feature activation are provided in this procedure.

1. Log out from any active NOAM and/or SOAM GUI sessions.

   Figure 5-10 Logout

   
   

   

   
   

   .
2. Establish an SSH session to the NOAM VIP. Log in as admusr.
3. Navigate to the feature activation directory by executing the following command $ cd /usr/TKLC/dsr/prod/maint/loaders/
4. Execute the feature activation script, run the feature activation script by executing the following command:$ ./featureActivateDeactivate

   Select Activate.

   Figure 5-11 Activate

   
   

   

   
   

   Select RBAR.

   Figure 5-12 RBAR

   
   

   

   
   

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

   Note:

   Alternatively you can also activate on all SOAM sites.

   Figure 5-13 SOAM

   
   

   

   
   

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

5. Establish a GUI session on the Active SOAM Server by using IP address of the SOAM server. Open the web browser and enter the following URL http://<Active_SOAM_IP_Address>
6. Log in as the guiadmin user.

   Figure 5-14 Oracle System Login

   
   

   

   
   
7. Verify if the RBAR folder is visible. Locate and verify the RBAR folder from Main Menu, check if it is visible and verify if the configuration folder items are present.

   Figure 5-15 RBAR Configuration

   
   

   

   
   
8. Verify if the application maintenance screen is visible. Verify if the RBAR application is present in the Application Status screen. Expand the Diameter folder, click Maintenance and select Applications.

   Figure 5-16 RBAR Status

   
   

   

   
   

   Verify if the RBAR status is uninitialized. The following data should be displayed:

   • Admin State = Disabled
   • Operational Status = Unk
   • Operational Reason = Unk
   • Congestion Level = Unk
9. In the stand by SOAM GUI, repeat the verification step 5 up to step 8.

   Note:

   If the verifications for the standby SOAM differ from the active SOAM, stop and contact My Oracle Support.
10. 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>
11. Log in as the guiadmin user.

    Figure 5-17 Oracle System Login

    
    

    

    
    
12. Restart DA-MPs. Multiple iterations of this step can be executed during the feature activation procedure. 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 the Status & Manage and click Server.

    Figure 5-18 Server Folder

    
    

    

    
    

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

13. Click Restart.

    Figure 5-19 Restart

    
    

    

    
    

    Click OK to confirm.

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

    Repeat for the additional DA-MPs.

14. Verify the RBAR application is present in the Application Status screen. Expand the Diameter folder, click Maintenance and select Applications.

    Figure 5-20 Application Status

    
    

    

    
    

    Verify RBAR status is initialized. The following data should display:

    • Admin State = Disabled
    • Operational Status = Unavailable
    • Operational Reason = Shutdown
    • Congestion Level = Normal

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