Configure AdminServer VIP for failover
As part of the Enterprise Deployment Guide (EDG) Oracle recommend using a virtual IP (VIP) for the admin server. This article explains the steps to setup a VIP and failover the admin server (collocated).
There is no need to create a new compute node for the admin server. Compute nodes in MyST are represented as physical servers.
Assumptions
Two physical servers
Physical1 - Managed Server1 + Admin Server (collocated)
Physical2 - Managed Server2
Failover between existing nodes in the domain
Shared storage for aserver domain home
6.5.0-rc8 or Newer
Setup Admin Server with a VIP
Start by setting the machine listen address which MyST references for the AdminServer listen address.
Override the AdminServer Machine name to be a generic name. Eg. 'admin'.
Failing Over the Admin Server
In order to failover the Adminserver you will need to move the Admin Server product within the Compute Nodes.
Update the AdminServer Product in Compute Nodes
Go to Platform Model > Compute Nodes
Update the Admin Server product to it's respective node. In this example we move the Admin Server from soa - 01 to soa - 02.
Click Actions > Update
Stop the Admin Server (Custom action:
stop-as-via-nm
)Stop the Node Managers (Custom action:
stop-nm
)Update the DNS for adminserver-vip.internal to point to the new IP address
Start the Node Managers (Custom action:
start-nm
)Start the Admin Server (Custom action:
start-as-via-nm
)The Admin Server will now be successfully running on soa - 01.
6.5.0-rc7 or Older
Moving the Admin Server product in older versions of MyST caused invalid auto computed properties to be generated. Upgrade to 6.5.0-rc8+ for an improved experience.
Setup Admin Server with a VIP
MyST uses the admin server machine's listen address to also set the admin server listen address. Here we set the machine listen address.
Use a VIP for the admin server machine's listen address
Failing Over the Admin Server
Configuration change sin MyST are required to fail over the admin server to another node in the domain.
Updating Compute Nodes
Go to Compute Nodes
Update the Admin Server product to it's respective node. For example:
Go to Machines
Remove the auto-computed machine
Restore the Name and Listen Address. This was re-computed by MyST when updating the Admin Server product.
Updating the Platform Instance Revision
Force MyST to update the platform model [pmNN] revision (which contains the above compute node changes) you can use the reprovision option while selecting 'Environment already pre-provisioned' checkbox.
Go to Actions > Reprovision
Select Environment already pre-provisioned?
MyST Actions
The MyST actions are expected to work as normal. No changes are required.
Patch
MyST runs patch action against each compute node
Install
Product binaries are installed to each compute node
Update
The update action connects to the admin server's listen address (VIP) using WLST
Last updated