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-2230550.1
Update Date:2018-03-30
Keywords:

Solution Type  Technical Instruction Sure

Solution  2230550.1 :   Oracle Communications User Data Repository (OCUDR): FAILOVER IN OCUDR  


Related Items
  • Oracle Communications User Data Repository
  •  
Related Categories
  • PLA-Support>Sun Systems>CommsGBU>Broadband Network Solutions>SN-SND: Tekelec UDR
  •  




In this Document
Goal
Solution
References


Created from <SR 3-14048503091>

Applies to:

Oracle Communications User Data Repository - Version UDR 10.0 to UDR 12.2 [Release UDR 10.0 to UDR 12.0]
Information in this document applies to any platform.

Goal

 Performing SWITCHOVER (SWO) in OCUDR

Solution

This document should be referred to perform switch-over in OCUDR Geo Redundant system.

Network Architecture:

Geo Redundant OCUDR system with 4 NOAM's.

{Site1: 1(ACT) + 1(STB); Site2: 1 (SPR) + 1 (SPR)}

 

Recommended Configuration


1> At Active OCUDR site (SITE1): We have Active and Standby server, these server should be configured as shown in pic below, which will enable them to work as ACTIVE or STANDBY.
Verifying via GUI: Check for NOAM Group and their status in “HA role Pref”
Main Menu: Configuration -> Server Groups
Here, box below “Preferred HA Role” should not be checked as shown below in screen shot ( Figure 1)

SWO UDR                                                                                                                                                                                                                      

 

 

 

 

2> At DR OCUDR Site (Site2): These servers status should be “SPARE”. These server should be configured to work as SPARE if, SITE-1 OCUDR servers are working fine.
Verifying via GUI:
Main Menu: Configuration -> Server Groups
Here, box below “Preferred HA Role” should be checked as shown below in screen shot. (Figure 2)

SWO UDR

                                                                                                                                                                                                                                                                         

 

Mechanism:
If, configured as mentioned above, whenever both servers at Site1 has problem, then only Site-2 (DR Site) servers will gain ACT/STB status. As soon as problem at Site1 is restored, again any one the 2 servers at Site-1 will become Active UDR. This will happen automatically without any intervention.

To elaborate more checked “Preferred Spare” at Site-2 means, even 1 server from Site-1 is in good health it will become ACTIVE.

How to Perform SWO
Assumption*** : Customer has permitted Oracle TAC to perform switchover and make Site-2 as Active OCUDR and Site-1 as DR Site.

WARNING*** : NOAM switch over will have momentarily impact both on Provisioning and SH traffic. Maintenance window is recommended.

STEP:1:
1.a ) Login to Active OCUDR VIP (Site1): Navigate to Main Menu: Configuration -> Server Groups
1.b ) Select DR site (Site-2) NO Grp, click “Edit” button below and uncheck “Preferred HA Role” box and “Apply

SWO UDR

                                                                                                                                                                                                                                                                  

 

STEP: 2:
2.a ) Now, change the status of Site-1: Active & Standby NOAM’s to SPARE.
2.b ) Navigate to Main Menu: Status & Manage -> HA, click “Edit” and change the status of NO-A & NO-B for Site-1 NOAM’s to "SPARE" & click “OK”.

SWO UDR

                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                

 

Note:  After performing this step; SITE-2 will become ACTIVE and we need to Open new GUI session using Site-2 VIP.

 

STEP:3:
3.a ) Verify NOAM at Site-2 becomes Active and Standby. (via CLI and GUI)
3.b ) Login to Site-2 VIP: CLI.

[admusr@NO-A ~]$ ha.mystate
resourceId role node subResources lastUpdate
DbReplication Active A3398.068 0 0202:132452.904
VIP Active A3398.068 0 0202:132452.906
CacdProcessRes Active A3398.068 0 0202:132452.906
UDRBE_Process Active A3398.068 0 0202:132452.953
UDRPROV_Process Active A3398.068 0 0203:070105.545
IMPORT_Process Active A3398.068 0 0202:132452.906
EXPORT_Process Active A3398.068 0 0202:132452.906
DBAUDITOR_Process OOS A3398.068 0 0130:160342.290
UDROAM_Process OOS A3398.068 0 0130:160342.291

3.c ) Via GUI : Main Menu: Status & Manage -> HA

3.d ) Active NOAM at site2 will reflect DB replication alarm due to SWO, which should auto clear in ~ 10-15mins. Verification should be done via GUI : Main Menu: Alarms & Events -> View Active

 

STEP:4:
4.a ) Login to Site-2 VIP this time.
4.b ) Navigate to Main Menu: Configuration -> Server Groups. Select NO group for Site-1 and check the box for “Preferred HA Role” as shown below.

SWO UDR

                                                                                                                                                                                                                                                                                      

Note: After performing above Step-4 we made sure that Site1 is nowDR site and Site2 as Active UDR.

 

STEP:5:
5.a ) Login to Active UDR VIP via GUI i.e. Site-2.
5.b ) Navigate to Main Menu: Status & Manage -> HA, click “Edit” and change the status of NO-A & NO-B for Site-1 NOAM’s to “ACTIVE” click Ok as shown below.

SWO UDR

                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                     

Procedure is completed.

References

<NOTE:2212215.1> - SRDC - Data Collection for OCUDR Database Replication Issues
<NOTE:2045296.1> - Oracle Communications UDR Health Check Document

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