Filter
Top Products
396 APPENDIX C: REPLACING A FAILED DISK ON A VCX SERVER
4 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 mm_dd_yy.
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
“man in the middle” attack. This message indicates that the security key
that was associated with the down server has changed, and the running
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
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.
b On the down server, restore the IPMSG database. For instructions, see
the IPMSG Operations and System Administration Guide.
5 Ensure that the codec that is installed on the running server is installed on
the down server.
a On the running server, log in as root.
b Enter these commands.
cd /opt/3com/VCX/UMS/app/app.dir
grep Codec config.app
The output from this command indicates which codec is being used
on the running server.
Example: Codec_Supported=g711u