Cisco Cisco TelePresence Video Communication Server Expressway
Appendix 2 – Adding a VCS to TMS
Cisco VCS Deployment Guide: Cluster creation and maintenance (Cisco VCS X7.1)
Page 48 of 69
Appendix 2 – Adding a VCS to TMS
On the VCS:
1. Go to the SNMP page (System > SNMP) and ensure that:
a. SNMP mode is set to v3 plus TMS support or v2c.
b. Community name is set to public.
(If SNMP was previously disabled, an alarm may appear indicating the need for a restart. If a
restart is required, go to Maintenance > Restart and click Restart System.)
restart is required, go to Maintenance > Restart and click Restart System.)
If multiple peers need restarting: restart each peer in turn, waiting for the peer to be accessible
through the web interface before restarting the next peer.
through the web interface before restarting the next peer.
2. Go to the External Manager page (System > External Manager) and ensure that:
a. Address is set to the IP Address or FQDN of TMS.
b. Path is set to tms/public/external/management/SystemManagementService.asmx.
c.
If the Protocol is HTTPS and Certificate verification mode is On then you must load the
relevant certificates before the connection can become ‘
relevant certificates before the connection can become ‘
Active
’. See document “D50520
Implementing Secure Management” for details.
d. If the Protocol is HTTP or Certificate verification mode is Off, no certificates need to be
loaded.
3. Click Save.
The Status section of the External Manager page should show a State ‘
Active
’ or ‘Initialising’.
On TMS:
1. Select Systems > Navigator.
2. Select (or create) an appropriate folder in which to put the VCS (in the example below the folder
has been called “Cluster”):
3. Click Add Systems.
4. In section “1. Specify Systems by IP addresses or DNS names”, enter the IP address or DNS
name of the VCS.
5. Click Next.
6. Look for
System added.
If an error occurs, e.g. “
Wrong Password”, click on the Edit System link and correct the
problem (enter the root password of the VCS).
1
TMS may force protocol to be HTTPS. The configuration for this is found in TMS Administrative Tools > Configuration >
Network settings. The protocol will be forced to HTTPS if, in the TMS Services section Enforce Management Settings on
Systems is set to On and in the Secure-Only Device Communication section Secure-Only Device Communication is set to
On.
Systems is set to On and in the Secure-Only Device Communication section Secure-Only Device Communication is set to
On.