Asset ID: |
1-71-2125246.1 |
Update Date: | 2017-10-12 |
Keywords: | |
Solution Type
Technical Instruction Sure
Solution
2125246.1
:
Diameter Signaling Router (DSR) - How to Edit the NTP Configuration on a Given Server Running DSR 7.x Release?
Related Items |
- Oracle Communications Diameter Signaling Router (DSR)
|
Related Categories |
- PLA-Support>Sun Systems>CommsGBU>Global Signaling Solutions>SN-SND: Tekelec DSR
|
In this Document
Created from <SR 3-12466880761>
Applies to:
Oracle Communications Diameter Signaling Router (DSR) - Version DSR 7.0.1 and later
Information in this document applies to any platform.
Goal
How to edit the NTP configuration on a given server running DSR 7.x release?
Solution
Operations, Administration, and Maintenance (OAM) user's Guide does not give the operator instructions on how to 'Edit' servers and more specifically how to edit the NTP configuration. Bug 22811507 has been created in order to add the procedure to the OAM user guide.
In order to edit the NTP configuration of a given server, the below steps need to be followed:
- Go to 'Main Menu: Configuration -> Servers' of the NOAM (Network Operations, Administration, and Maintenance) GUI.
- Select/highlight the server to be edited and click on "Edit" at the bottom.
- Modify NTP servers and save.
- Go to 'Status and Manage > HA' of NOAM GUI.
- Click on "Edit".
- Identify the target server(s) on which you want to perform the NTP Sync action (from step 2 above). Confirm that the target server(s) reflect a "Max Allowed HA Role" of either Standby, Spare or Observer. If it doesn't reflect one of these states, make needed changes.
- Click "Ok" if the "Max Allowed HA Role" was changed, in order for it to take effect.
- Go to 'Main Menu: Status & Manage -> Server' of NOAM GUI.
- Select/highlight the server that was modified in step 2 above.
- Click on "NTP Sync" at the bottom.
- A warning message may appear: "Are you sure you wish to force an NTP Sync on the following server(s)?"
- Click OK to continue.
- Release the force-standby by reversing the "Max Allowed HA Role" to it's original state (steps 4 thru 7 above).
This procedure runs a restart of the application on the concerned server. Some alarms are then expected to raise.
References
<BUG:22811507> - OAM DOCUMENT DOES NOT CONTAIN INSTRUCTIONS TO EDIT SERVERS
Attachments
This solution has no attachment