Step 1 |
Ensure that the network connectivity between the primary and secondary is functioning and that all the necessary ports are open. |
Step 2 |
Install the correct version of MSE on the primary MSE. |
Step 3 |
Make sure that the same MSE release version that is loaded on the other primary MSE and secondary MSE is also loaded on the new primary MSE. |
Step 4 |
On the intended primary MSE, enter the following command:
/opt/mse/setup/setup.sh
--------------------------------------------------------------
Welcome to the appliance setup.
Please enter the requested information. At any prompt,
enter ^ to go back to the previous prompt. You may exit at
any time by typing <Ctrl+C>.
You will be prompted to choose whether you wish to configure a
parameter, skip it, or reset it to its initial default value.
Skipping a parameter will leave it unchanged from its current
value.
Changes made will only be applied to the system once all the
information is entered and verified.
--------------------------------------------------------------
|
Step 5 |
Configure the hostname:
Current hostname=[mse]
Configure hostname? (Y)es/(S)kip/(U)se default [Skip]:
The hostname should be a unique name that can identify the device on the network. The hostname should start with a letter, end with a letter or number, and contain only letters, numbers, and dashes. |
Step 6 |
Configure the domain name:
Enter a domain name for the network domain to which the device belongs. The domain name should start with a letter, and it should end with a valid domain name suffix such as .
com. It must contain only letters, numbers, dashes, and dots.
Current domain=[]
Configure domain name? (Y)es/(S)kip/(U)se default [Skip]:
|
Step 7 |
Configure the HA role:
Current role=[Primary]
Configure High Availability? (Y)es/(S)kip/(U)se default [Skip]:
High availability role for this MSE (Primary/Secondary):
Select role [1 for Primary, 2 for Secondary] [1]: 1
Health monitor interface holds physical IP address of this MSE server.
This IP address is used by Secondary, Primary MSE servers and Prime Infrastructure to communicate
among themselves
Select Health Monitor Interface [eth0/eth1] [eth0]:eth0
-------------------------------------------------------------------
Direct connect configuration facilitates use of a direct cable connection between the primary and secondary MSE servers.
This can help reduce latencies in heartbeat response times, data replication and failure detection times.
Please choose a network interface that you wish to use for direct connect. You should appropriately configure the respective interfaces.
\"none\" implies you do not wish to use direct connect configuration.
-------------------------------------------------------------------
|
Step 8 |
Configure Ethernet interface parameters:
Select direct connect interface [eth0/eth1/none] [none]: eth0
Enter a Virtual IP address for first this primary MSE server:
Enter Virtual IP address [172.31.255.255]:
Enter the network mask for IP address 172.31.255.255.
Enter network mask [255.255.255.0]:
Current IP address=[172.31.255.255]
Current eth0 netmask=[255.255.255.0]
Current gateway address=[172.31.255.256
Configure eth0 interface parameters? (Y)es/(S)kip/(U)se default [Skip]:
|
Step 9 |
When prompted for “eth1” interface parameters, enter Skip to proceed to the next step. A second NIC is not required for operation:
Configure eth1 interface parameters? (Y)es/(S)kip/(U)se default [Skip]:
|
Step 10 |
Configure the hostname for secondary MSE:
Current hostname=[]
Configure hostname? (Y)es/(S)kip/(U)se default [Skip]:
|
Step 11 |
Configure domain name:
Current domain=
Configure domain name? (Y)es/(S)kip/(U)se default [Skip]:
|
Step 12 |
Configure the HA role:
Current role=[Primary]
Configure High Availability? (Y)es/(S)kip/(U)se default [Skip]:
High availability role for this MSE (Primary/Secondary)
Select role [1 for Primary, 2 for Secondary] [1]: 2
Health monitor interface holds physical IP address of this MSE server.
This IP address is used by Secondary, Primary MSE servers and Prime Infrastructure to
communicate among themselves
Select Health Monitor Interface [eth0/eth1] [eth0]: [eth0/eth1]
-------------------------------------------------------------------
Direct connect configuration facilitates use of a direct cable connection between the primary and secondary MSE servers.
This can help reduce latencies in heartbeat response times, data replication and failure detection times.
Please choose a network interface that you wish to use for direct connect. You should appropriately configure the respective interfaces.
\"none\" implies you do not wish to use direct connect configuration.
-------------------------------------------------------------------
|
Step 13 |
Configure Ethernet interface parameters:
Select direct connect interface [eth0/eth1/none] [none]: eth1
Enter a Virtual IP address for first this primary MSE server
Enter Virtual IP address [172.19.35.61]:
Enter the network mask for IP address 172.19.35.61:
Enter network mask [255.255.254.0]:
Current IP address=[172.19.35.127]
Current eth0 netmask=[255.255.254.0]
Current gateway address=[172.19.34.1]
Configure eth0 interface parameters? (Y)es/(S)kip/(U)se default [Skip]:
|
Step 14 |
Once you have configured both the primary MSE and secondary MSE, the Prime Infrastructure UI should be used to set up a pairing between the primary and secondary MSE. |
Step 15 |
Once the primary MSE is added successfully, click the Services > High Availability or click the primary MSE device in the Services > Mobility Services Engine page and choose HA Configuration > Service High Availability from the left sidebar menu.
The HA Configuration page appears. |
Step 16 |
Enter the secondary device name with which you want to pair the primary MSE. |
Step 17 |
Enter the secondary IP address which is the health monitor IP address of the secondary MSE. |
Step 18 |
Enter the secondary password. This is the Prime Infrastructure communication password configured on the MSE. |
Step 19 |
Specify the failover type. You can choose either Manual or Automatic from the Failover Type drop-down list. After 10 seconds, the system fails over. The secondary server waits for a maximum of 10 seconds for the next heartbeat from the primary server. If it does not get the heartbeat in 10 seconds, it declares a failure. |
Step 20 |
Specify the failback type by choosing either Manual or Automatic from the Failback Type drop-down list. |
Step 21 |
Specify the Long Failover Wait in seconds.
After 10 seconds, the system fails over. The maximum failover wait is 2 seconds. |
Step 22 |
Click Save.
The pairing and the synchronization happens automatically. |
Step 23 |
To check whether the heartbeat is received from the primary MSE or not, choose Services > Mobility Services Engine, and click Device Name to view the configured parameters. |
Step 24 |
Choose HA Configuration > Service High Availability from the left sidebar menu. Check whether the heartbeat is received from the primary MSE. |