Changing The Default Ssh Key; Default Ssh Key Warnings; Standalone Vcs; Clustered Vcs - Cisco TelePresence Video Communication Server Administrator's Manual

This will give the command line that named (the BIND server) was invoked with. If there is a -t
option, then the path following that is the new root directory and your files will be located relative to that
root.
In /etc/named.conf look for a directory entry within the options section. This will give the directory in
which the zone files are stored, possibly relative to a new root directory. In the appropriate zone
section, a file entry will give the name of the file containing the zone details.
For more details of how to configure BIND servers and the DNS system in general see the publication
DNS and BIND [6].

Changing the default SSH key

Default SSH key warnings

A warning message "Security alert: the SSH service is using the default key" is displayed if your VCS
is still configured with its factory default SSH key.
Using the default key means that SSH sessions established to the VCS may be vulnerable to "man-in-
the-middle" attacks, so you are recommended to generate new SSH keys which are unique to your
VCS.

Standalone VCS

Use the following instructions to generate a new SSH key for the VCS, entering all commands from
the CLI while logged in as root:
1. Type regeneratesshkey.
2. Type exit to log out of the root account.

Clustered VCS

Use the following instructions to generate new SSH keys for each cluster peer.
Enter the following commands from the CLI while logged in as root:
1. On each VCS peer in turn:
a. Type cluster.
b. Select option (3) to temporarily disable replication on each VCS.
Follow the instructions but DO NOT remove the VCS from the list of peers.
c. Select (q) to quit.
2. On each VCS peer in turn:
a. Type regeneratesshkey.
3. After each VCS has had replication disabled and its SSH key regenerated, on each VCS peer in
turn:
a. Type cluster.
On the master VCS, select option (1) and follow the instructions to set it as the replication
o
master.
On each non-master VCS, select option (2) and follow the instructions to set it to replicate
o
with a peer.
b. Select (q) to quit.
4. On every VCS in turn:
a. Type cluster.
b. Select option (5) to check that VCS replication is working correctly.
c. Select (q) to quit.
5. Type exit to log out of the root account.
Finally, you must restart every VCS. You are recommended to do this from the web interface:
Cisco VCS Administrator Guide (X6.1)
Reference material
Page 262 of 401