5 Verifying Alarm Status (After Failover)
Perform the following steps in New Primary NOAM VIP (former DR) to verify
alarms status at the Primary Active NOAM.
- 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 5-1 Certificate Error
The login screen appears.
- Log in to the GUI using a user account with administrator
privileges.
The Product Main Menu appears.
- 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.
Figure 5-2 Product Main Menu
- Go to . Then, select View Active.
Figure 5-3 View Active
The current list of Active Alarms appears.
Figure 5-4 Active Alarms
Note:
Alarms visible at this time may include but are not limited to Event ID(s): 31106, 31107, 31114, 31233 & 31283. - Monitor the current list of Active alarms until all alarms
associated with the Failover have cleared.
Note:
The user should allow at least 15 minutes for resulting alarms to clear before attempting any troubleshooting activities.
Note:
- Contact My Oracle Support (MOS) for assistance with any reoccurring alarms or alarms which fail to clear within a 15 minute timeframe.
- Refer to My Oracle Support (MOS), for more information on contacting Oracle Customer Service.
- If alarms fail to clear that are related to features that use SSH key
exchange based file transfer and the user wishes to
re-enable them prior to performing a Failover back to the original
Primary or Secondary states, then the feature may be reconfigured using
the product feature’s initial configuration procedures.
Partial list of features that use SSH key exchange based file transfer:
- SDS: provimport, provexport, APDE
- HLRR: PDE, APDE
- DSR: APDE
- This procedure has been completed. Return to Figure 2-1.