Cisco Model D9500 Switched Digital Video Server (NTSC and PAL) 릴리즈 노트
4
4035984 Rev A
Installation and Upgrade Guidelines
Installation and Upgrade Guidelines
General Notes
An FTP or SSH server is required to download new software to the USRM.
Installation Requirements
Before performing the upgrade procedure, make sure the following requirements are
met:
met:
The desired USRM software release has already been uploaded to the FTP server.
If the DNCS is being used as the FTP or SSH server, make sure that the desired
USRM release is located in the /export/home/dncs directory.
USRM release is located in the /export/home/dncs directory.
If the DNCS is being used as an SSH server, make sure that the Provisionkeys
application has been run on each of the servers.
application has been run on each of the servers.
A backup of the existing USRM database has been completed prior to upgrading
to be prepared in case a rollback to the previous version is desired. A backup can
be created from any directory in the USRM by typing usrmbackup at the
command line prompt. The backup file will be stored in the /root directory. We
recommend that this backup file be copied to and saved in a secure location in
case it is needed in the future.
to be prepared in case a rollback to the previous version is desired. A backup can
be created from any directory in the USRM by typing usrmbackup at the
command line prompt. The backup file will be stored in the /root directory. We
recommend that this backup file be copied to and saved in a secure location in
case it is needed in the future.
Note: A downgrade from USRM 2.1.4 to USRM 1.x requires the installation of a 1.x
database as part of the procedure. If a 1.x database does not exist, all persistdata will
be lost during the downgrade.
database as part of the procedure. If a 1.x database does not exist, all persistdata will
be lost during the downgrade.
New Requirement
With the introduction of VOD Session Management capabilities to the USRM, it is
now required to keep track of all traffic on all GigE ports on all QAMs. With this in
mind, we now require that the Edge Input IP address(es) be included for all QAMs.
If you have configuration files, the Edge Input address(es) should be added to these
files.
Note: Failure to populate Edge Input Address(es) will result in session setup
failures.
now required to keep track of all traffic on all GigE ports on all QAMs. With this in
mind, we now require that the Edge Input IP address(es) be included for all QAMs.
If you have configuration files, the Edge Input address(es) should be added to these
files.
Note: Failure to populate Edge Input Address(es) will result in session setup
failures.