12 Perform Health Check - Pre-Feature Activation

This section describes the procedure to perform a health check pre-feature activation.

Log in to the NOAM VIP GUI, establish a GUI session on the NOAM server by using the VIP address of the NOAM server.

1. Open the web browser and enter the URL, http://<Primary_NOAM_VIP_IP_Address>
2. Log in as the guiadmin user.

   Figure 12-1 Oracle System Log in

   
   

   

   
   
3. In the NOAM (2-Tiered) VIP GUI, verify if the DCA Framework folder is not present. Expand the Main Menu option, click Diameter.
4. In the SOAM (2-Tiered) VIP GUI, verify if the DCA Framework folder is not present. Expand the Main Menu option click Diameter.
5. Verify the Server Status. Expand Status & Manage click on Server

   Figure 12-2 Status and Manage

   
   

   

   
   
6. Verify all Server Status is Normal (Norm) for, Alarm (Alm), Database (DB), Reporting Status, and Processes (Proc).

   Figure 12-3 Alarms

   
   

   

   
   

   Do not proceed to feature activation if any of the above states are not Norm. If any of these are not Norm, corrective action should be taken to restore the non-Norm status to Norm before proceeding with the feature activation.

   If the Alarm (Alm) status is not Norm but only Minor alarms are present, it is acceptable to proceed with the feature activation. If there are Major or Critical alarms present, these alarms should be analyzed before proceeding with the feature activation. The activation may be able to proceed in the presence of certain Major or Critical alarms.

7. In the NOAM VIP GUI, verify server configuration. Expand the Configuration option, click Server Groups. Verify if the configuration data is correct in the network.

   Figure 12-4 Server Group

   
   

   

   
   
8. In the NOAM VIP GUI, log the current alarms. Expand the Alarms & Events option and click View Active

   Figure 12-5 View Active Alarms

   
   

   

   
   
9. Click Report

   Figure 12-6 Report

   
   

   

   
   
10. Verify if the configuration data is correct for your network. Save or Print this report to keep copies for future reference.

    Figure 12-7 Save or Print

    
    

    

    
    
11. In the NOAM VIP GUI, log the alarm history. Expand Alarms & Events option and click View History.
12. Click Report

    Figure 12-8 Report

    
    

    

    
    
13. Verify if the configuration data is correct for your network. Save or Print this report to keep copies for future reference.

    Figure 12-9 Save or Print

    
    

    

    
    
14. In the NOAM VIP GUI, check the Upgrade Acceptance status on all servers. Expand the Administration option, navigate to Software Management and click Upgrade. Verify if the Upgrade State column does not show ACCEPT or REJECT.

    Note:

    Upgrade must be accepted on all servers before activating DCA.

    Figure 12-10 Upgrade

    
    

    

    
    

    Upgrade State should be Ready. If the Upgrade State is ACCEPT or REJECT, follow the procedure documented in DSR C-Class Software Installation and Configuration guide or DSR Software Upgrade Guide (as applicable) to accept the upgrade on all servers before activating DCA.

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