Filter
Top Products
Replacing a Disk (Single Site) 385
to the security key is a normal consequence of the disk replacement
process.
To resolve this issue, locate the
known_hosts file on the running server
(
/opt/home/cworks/.ssh/known_hosts) and perform one of these
actions:
■ Edit the file, locate the line that contains the IP address of the down
server, and replace the old key with the new key.
■ Edit the file, locate the line that contains the IP address of the down
server and remove that line.
■ Delete the known_hosts file. If you use this method, the next time you
try to access any of the other VCX servers using commands such as
scp or ssh, you will be prompted to confirm that you want to trust the
target server.
f Restore the database on the down server. See the VCX Administration
Guide for instructions.
4 Set up Oracle database replication on either of the servers.
a On the running server, log in as cworks.
b Enter these commands:
cd /opt/3com/VCX/vcxdata/bin
./setupReplication
You must know which server is the Master Definition Site and provide the
IP address when the script prompts for this information.
The script asks for the IP addresses of the two servers and then checks the
replication state of the authentication databases on them. After the
check, database replication begins.
5 Verify that Oracle database replication has been completed
a Log in as cworks.
b Enter these commands:
cd /opt/3com/VCX/vcxdata/bin
./checkReplication
The script asks for the site ID and the IP addresses of the two servers
and then checks the replication state of the authentication databases
and reports the status.
If replication has been completed, you see this message: