Cisco Cisco TelePresence Video Communication Server Expressway 릴리즈 노트

다운로드
페이지 50
Introduction 
Cisco TelePresence Video Communication Server X7.2.4 Software Release Notes 
Page 6 of 50 
 
 
Introduction 
These release notes describe the features and capabilities included in the Cisco TelePresence Video 
Communication Server (Cisco VCS) software version X7.2.3. 
Upgrading to VCS X7.2.n 
Read the "Open caveats" section before upgrading. You can only upgrade directly to X7.n if you have 
version X6.0 or later. 
CAUTION: If you are upgrading a cluster, you must follow the directions in the X7.2 
“Cluster Creation 
and Maintenance
” VCS deployment guide (document D14367), otherwise the cluster will not 
synchronize. 
There is a software dependency between VCS X7.n and TMS 12.6 or later. If you are running Cisco 
TelePresence Management Suite (Cisco TMS) with Provisioning or FindMe, or your Cisco VCSs are 
clustered and you want to upgrade your Cisco VCS to X7.n or later, you must also upgrade Cisco 
TMS to TMS 12.6 or later, see the table below. 
 
Deployment using Provisioning, Clustering or FindMe 
Software version 
TMS 12.6-13.1 
TMS 13.2 
X5.2 
 
 
X6.n 
 
 
X7.0.n 
 
 
X7.1 / X7.2 (TMS Agent legacy mode) 
 
 
X7.1 / X7.2 (TMS Provisioning Extension mode) 
 
 
Note: You should backup your system before upgrading. If you later need to downgrade to an earlier 
release you will have to restore a backup made against that previous release. 
It is vital that you upgrade the Cisco VCS and Cisco TMS correctly 
– instructions for the upgrade are 
documented in the Upgrading to X7.2. section of this document. 
After upgrading to X7.2 
Note the following important configuration information, following an upgrade to X7.2: 
 
The default Traversal Subzone media port range is now 50000 - 54999 (previously 50000 - 
52399), in order to support the new media encryption policy feature. To reflect this change, 
system administrators may need to modify the rules configured in their firewall devices. 
 
Core dump mode is enabled (even if it was previously disabled). It can be configured on the 
Incident reporting configuration
 page. 
 
An “Insecure password in use” alarm will be raised against the root account. This is because the 
VCS now uses SHA512 to hash passwords. Passwords were previously hashed using MD5. The 
root account will still be accessible but you are recommended to use the root passwd command to 
reset the root account password. Administrator account passwords are rehashed automatically on 
upgrade. 
 
If the system was previously configured to use Remote authentication as its Administrator 
authentication source
 this will be changed to the new Both option which allows both locally and 
remotely maintained administrator accounts to log in to the VCS, and any pre-existing local 
administrator accounts will be set as Disabled