1. Diameter Signaling Router Policy and Charging Application Feature Activation Guide
  2. Feature Activation
  3. Pre-Activation Procedures
  4. Health Check for Pre-activation

5.1.1 Health Check for Pre-activation

This procedure is used to determine the health and status of the network and servers. This must be executed at the start of every maintenance window.

Note:

The Health Check procedure below is the same as the Health Check procedure described in Section Perform Health Check when preparing for feature activation, but it is repeated here to emphasize that it is being re-executed if Section Perform Health Check was performed outside the maintenance window.

Procedure 3 : Perform 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 5-1 Oracle System Login


    Oracle System Login

  3. Under Main Menu, verify the Policy and Charging folder is NOT present.

    Figure 5-2 Main Menu


    Main Menu

Verify the server status.

  1. Expand Status & Manage option and click Server.

    Figure 5-3 Server


    Server

  2. Verify if Server Status is Normal (Norm) for: Alarm (Alm), Database (DB), Replication Status, and Processes (Proc).

    Figure 5-4 Server Status


    Server Status

    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 prior to proceeding with the feature activation. The activation may be able to proceed in the presence of certain Major or Critical alarms. Contact My Oracle Support (MOS) for assistance as necessary.

Verify the server configuration.

  1. Expand Configuration option and click Server Groups.

    Figure 5-5 Server Groups


    Server Groups

    Verify the configuration data is correct for your network.

  2. Log current alarms, Expand Alarms & Events option and click View Active.

    Figure 5-6 Alarms and Events


    Alarms and Events

  3. Click Report.

    Figure 5-7 Report


    Report

  4. Save or Print this report to keep copies for future reference.

    Figure 5-8 Save or Print


    Save or Print

Check the software version on all servers.

  1. Navigate to Administration option, click Software Management and then click Upgrade.

    Verify the Upgrade ISO column shows the correct release number for all servers in the DSR network.

    Note:

    All servers in the network must be on the same DSR release when activating PCA.

    Figure 5-9 Upgrade ISO Column


    Upgrade ISO Column

Check the Upgrade Acceptance status on all servers.

  1. Navigate to Administration option, click Software Management and then click Upgrade.

    Verify the Upgrade State column does not show ACCEPT or REJECT

    Note:

    Upgrade must be accepted on all servers before activating PCA.

    Figure 5-10 Upgrade State Column


    Upgrade State Column

    Upgrade State should be Ready. If the Upgrade State is ACCEPTORREJECT, follow the Installation Guide [1] or Upgrade Guide [7] (whichever applies) to accept the upgrade on all servers before activating PCA.

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