Sun Microsystems, Inc.  Oracle System Handbook - ISO 7.0 May 2018 Internal/Partner Edition
   Home | Current Systems | Former STK Products | EOL Systems | Components | General Info | Search | Feedback

Asset ID: 1-71-2325480.1
Update Date:2017-11-08
Keywords:

Solution Type  Technical Instruction Sure

Solution  2325480.1 :   How To Set a Diameter Signaling Router (DSR) Server Out Of Service (OOS) Pending Maintenance  


Related Items
  • BNS Platform Hardware
  •  
Related Categories
  • PLA-Support>Sun Systems>CommsGBU>Global Signaling Solutions>SN-SND: Tekelec DSR
  •  




In this Document
Goal
Solution


Created from <SR 3-15994038481>

Applies to:

BNS Platform Hardware - Version DSR 5.1 and later
Information in this document applies to any platform.

Goal

The Goal of this article is to direct users to the proper method to take a server out of service in a DSR when it needs maintenance and is awaiting the scheduled maintenance window.

Solution

While awaiting maintenance, if an operator wishes to set a Diameter Signaling Router server safely out of service the following procedure should be utilized:

  1. In a web browser, log into the active Network OAM (NOAM) GUI and log in.
  2. Using the left menu tree, navigate through Main Menu / Status & Manage screen
  3. Select [Edit] near the bottom of the screen.
  4. Find the row with the Hostname of the server you wish to take out of service.
  5. Using the pulldown in the 'Max Allowed HA Role' column in the server's row, select 'OOS' and then select the [Ok] button
  6. If prompted, confirm.  Note that if the server was the Active among the group [OAM Max HA Role], a switch-over will ensue.

This action will set the server safely out of service (OOS).  Note that taking a server out of service will cause several alarms to assert, depending on the role of the server.  These should be ignored until the server maintenance is completed and the Max Allowed HA Role can again be set to 'Active.'

Taking the server out of service by inhibiting the database (NOAM / Main Menu / Status & Mange / Database) is never recommended unless specifically indicated by a published Oracle procedure.  A server should not have its database inhibited for extended periods of time.

 


Attachments
This solution has no attachment
  Copyright © 2018 Oracle, Inc.  All rights reserved.
 Feedback