Cisco Cisco TelePresence Video Communication Server Expressway 릴리즈 노트
Introduction
Cisco TelePresence Video Communication Server X7.2.2 Software Release Notes
Page 9 of 50
message will be identified as coming through that neighbor zone, the VCS will not perform any
credential checking (as the neighbour zone is set to Do not check credentials) and the message will
be accepted.
credential checking (as the neighbour zone is set to Do not check credentials) and the message will
be accepted.
Deployments with multiple regional / subnetwork directory VCSs
If your deployment is segmented into multiple regional subnetworks, each with their own directory
VCS, it is not feasible (or recommended) to set up neighbor zones between each and every VCS
across the entire network.
VCS, it is not feasible (or recommended) to set up neighbor zones between each and every VCS
across the entire network.
In this scenario you should configure each subnetwork as described above – i.e. set up neighbor
zones between each of the VCSs managed by the same directory VCS – and then configure the
neighbor zones between each directory VCS so that they do stay in the call signaling path on calls
crossing subnetworks between those directory VCSs. To do this:
zones between each of the VCSs managed by the same directory VCS – and then configure the
neighbor zones between each directory VCS so that they do stay in the call signaling path on calls
crossing subnetworks between those directory VCSs. To do this:
1. On the directory VCS, go to the
Zones
page (
VCS configuration > Zones
) and then click on the
relevant zone to the other directory VCS.
2. On the
Edit zones
page, scroll down to the Advanced section and set Zone profile to Custom.
3. Set Call signaling routed mode to Always.
4. Click Save.
5. Repeat this for the equivalent zone definition on the “other” directory VCS, and then repeat the
entire process for any other zone configurations between any other directory VCSs.
Note: do not modify the directory VCS’s primary Call signaling routed mode setting on the
Calls
page.
This means that the each directory VCS will stay in the call signaling path for calls that go between
subnetworks. Each directory VCS will still be able to optimize itself out of the call signaling path for
calls entirely within each subnetwork.
subnetworks. Each directory VCS will still be able to optimize itself out of the call signaling path for
calls entirely within each subnetwork.
You must also ensure that you have sufficient non-traversal and traversal licenses on each directory
VCS to handle those calls going between each subnetwork.
VCS to handle those calls going between each subnetwork.
Upgrading from X6.1 to X7.n
Important note for Cisco VCS units delivered with X6.1 pre-installed
As with upgrading from any Cisco VCS release, you should first backup your system before
upgrading. However, if your system was delivered with X6.1 pre-installed, you must make some
configuration changes before using the backup process.
upgrading. However, if your system was delivered with X6.1 pre-installed, you must make some
configuration changes before using the backup process.
You do not need to use the procedure below if you do not have X6.1 installed or your installation of
X6.1 is the result of an upgrade from a previous release.
X6.1 is the result of an upgrade from a previous release.
To ensure that all of your data is backed up:
1. Log in to the Cisco VCS as root user.
2. Enter the following commands:
a. mkdir /tandberg/persistent/oti
b. mkdir /tandberg/persistent/management
3. Exit the root account.
You can now log into the web user interface and backup your system as normal via
Maintenance >
Backup and restore
, and then upgrade the Cisco VCS using the X7.2 “Cluster Creation and
Maintenance” Cisco VCS deployment guide, or by following the “Upgrading to X7.2” instructions in this
document.
document.