Asset ID: |
1-71-2159119.1 |
Update Date: | 2016-07-15 |
Keywords: | |
Solution Type
Technical Instruction Sure
Solution
2159119.1
:
Changing VIP On Server (CMP/MPE/MRA)
Related Items |
- Oracle Communications Policy Management
|
Related Categories |
- PLA-Support>Sun Systems>CommsGBU>Broadband Network Solutions>SN-SND: Tekelec Policy
|
In this Document
Created from <SR 3-12948745261>
Applies to:
Oracle Communications Policy Management - Version POLICY 11.5.2 and later
Information in this document applies to any platform.
Goal
On : POLICY 11.5.2 version, Cable (Production)
Changing VIP on Server
We want to change the VIP on one of our servers. We want to remove the current VIP and then reassign the new VIP to the server and we would like to know any risks associated with this change as well as the required steps we need to take in order to change the VIP as well as the steps to get the server back into the topology with the new VIP configured.
We want to do this without having to re-install the entire policy application on the server.
Solution
Please find the steps below to modify OAM VIP and plan to execute this is LAB environment before implementing on the Production servers.
I've tried the below steps in my lab environment and works fine.
1. Go to CMP GUI-> Platform settings->Topology Settings -> Choose the MPE where the VIP IP needs to be changed
2. Click Modify the site -> change the VIP IP and save the page
3. At this point a pop window appears "Active Server will restart", click OK.
Also make sure that there is no failover happens while the VIP is being modified.
Note: OAM VIP is usually used for all the Network elements to initiate Diameter connections and hence any NE using this VIP should be informed prior to this activity and modify the IP at the remote end.
There are a few considerations:
- Assume they are talking about a SIG-A/B/C VIP? Logic for OAM is the same, but the following discussion assumes a SIG-A VIP.
- Is the sub-network changing? (e.g. is 10.0.0.0/8 changing to 10.0.0.0/16?)
If the sub-network is changing, then check if all routes on SIG-A will remain valid once the VIP changes?
- All PGWs/NEs/Data-Sources that connect to the VIP will need to be updated...even if they do not initiate connections, they may have access-control-lists (ACL) that must be updated.
- Inter-site firewalls may need to be updated with new ACL rules if they reference the old VIP.
References
<BUG:23726849> - OAM VIP IP CHANGE IN MA
Attachments
This solution has no attachment