You may need to fail over the network management services
to the standby site even when the active site is fully operational.
You execute the jmp-dr manualFailover command at the standby
site to fail over the network management services to the standby site.
When the failover is complete, the standby site becomes the new active
site.
Note:
-
We recommend that you check the status of the disaster recovery configuration
before and after executing the jmp-dr manualFailover
command. To do so, execute the jmp-dr health command at
both sites.
-
If you do a manual failover after the automatic failover is disabled, then
you need to again disable the automatic failover using jmp-dr
toolkit watchdog status --disable-automatic-failover 0
command.
To manually fail over the network management services
to the standby site:
- Log in to the CLI of the Junos Space node at the standby
site on which the VIP or the eth0:0 interface is configured.
The Junos Space Settings Menu is displayed.
-
Enter
7while
using a virtual appliance at the Junos Space Settings Menu prompt to run shell
commands.
The following is a sample output from a virtual appliance:
admin@10.206.41.183's password:
Last login: Mon Aug 17 06:17:58 2015 from 10.206.41.42
Welcome to the Junos Space network settings utility.
Initializing, please wait
Junos Space Settings Menu
1> Change Password
2> Change Network Settings
3> Change Time Options
4> Retrieve Logs
5> Security
6> Expand VM Drive Size
7> (Debug) run shell
A> Apply changes
Q> Quit
R> Redraw Menu
Choice [1-7,AQR]: 7
You are prompted to enter the administrator password.
- Enter the administrator password.
- Type
jmp-dr manualFailover at the shell prompt
and press Enter.
- Enter Yes.
The following is a sample output:
[root@space-000c29088bfa ~]# jmp-dr manualFailover
? Do you really want to start manual failover Yes
Check DR state of this site: started
INFO: => switchover DR at current site: active
Stop dr-watchdog if it's running [ OK ]
Check status of DR remote site: up
Check current DR role: standby
Restore configuration files [ OK ]
Setup MySQL replication: master-master [ OK ]
Skip MySQL data backup [ OK ]
Setup PostgreSQL replication [ OK ]
Start file & RRD replication [ OK ]
Open firewall for device traffic [ OK ]
Start services(jboss,jboss-dc,etc.) [ OK ]
Start dr-watchdog [ OK ]
Copy files to DR slave site [ OK ]
Update DR role of current site: active [ OK ]
INFO: => switchover DR at DR remote site: standby
Check DR state of this site: started
Stop dr-watchdog if it's running [ OK ]
Check status of DR remote site: up
Check current DR role: active
Stop services(jboss,jboss-dc,etc.) [ OK ]
Block firewall for device traffic [ OK ]
Reset MySQL init script and stop replication [ OK ]
Skip MySQL data restore [ OK ]
Setup MySQL replication and start replication [ OK ]
Setup PostgreSQL replication [ OK ]
Start files & RRD replication [ OK ]
Start dr-watchdog [ OK ]
Clean up /var/cache/jmp-geo/incoming [ OK ]
Update DR role of current site: standby [ OK ]
Command completed.
Command completed.
The standby site becomes the new active site.
Note: If you have made any NAT-related updates in any of the
disaster recovery sites, after a manual failover, run the following
commands to ensure that NAT devices work seamlessly with the new active
site:
Move the backup file from /var/cache/jmp-geo/config/diff.properties_backup to /var/cache/jmp-geo/config/diff.properties.
Run the following command on the VIP node to update the
changed standby cluster device management, NAT, and IP configuration
on the current active site:
/var/cache/jmp-geo/script/toolkit-config-update.pl
