3Com VCX V7000 Installation Manual page 425

server does not recognize the down server's new security key. The change
to the security key is a normal consequence of the disk replacement
process.
To resolve this issue, locate the
(
/opt/home/cworks/.ssh/known_hosts
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
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.
11 Restore the database on the down server. For instructions, see the VCX
Administration Guide.
12 Set up Oracle database replication on either of the servers.
a On the running server or the down 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 of the eth0 network interface 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.
13 Restore Intelligent Mirroring for IP Messaging.
a Transfer the IPMSG database backup files (that you saved in a previous
step) to the down server and place them in this directory (you must
first create the directory):
/opt/3comdata/umsdata/backup/DATE/
DATE is the date on which the IP Messaging backup script was run.
The format is
CAUTION: When you use the scp command to copy the database
backup files to the down server, you may see a warning message about a
known_hosts
file. If you use this method, the next time you
.
mm_dd_yy
Replacing a Disk (VCX Connect)
file on the running server
) and perform one of these
425