Cisco Headend System Release 2.7 Release Notes
Chapter 2 What Are the Site Requirements?
20
4019364 Rev B
Upgrade Logistics
Introduction
This section contains information that can help system operators plan the upgrade to
SR 2.8.
SR 2.8.
Supported Upgrade Path
Note these important upgrade requirements:
Systems that upgrade to SR 2.8 must currently be operating with system
software from SR 2.2 or SR 3.2, or later, as well as DHCT client operating system
(OS) 3.1 or later. The upgrade software is contained in a UniPack due to
significant changes contained in SR 2.8 and other time saving factors. Rollback
procedures and software are included in the UniPack installation instructions in
the event that the upgrade is unsuccessful.
software from SR 2.2 or SR 3.2, or later, as well as DHCT client operating system
(OS) 3.1 or later. The upgrade software is contained in a UniPack due to
significant changes contained in SR 2.8 and other time saving factors. Rollback
procedures and software are included in the UniPack installation instructions in
the event that the upgrade is unsuccessful.
You must already have the DNCS Utilities software installed onto the DNCS and
should have already run the pre-upgrade checks to ensure system compatibility
with SR 2.8 UniPack upgrade requirements. Refer to DNCS Utilities Installation
and Operation Guide for instructions on installing and executing the DNCS
Utilities.
should have already run the pre-upgrade checks to ensure system compatibility
with SR 2.8 UniPack upgrade requirements. Refer to DNCS Utilities Installation
and Operation Guide for instructions on installing and executing the DNCS
Utilities.
Important: You can now use Live Upgrade with the UniPack. Through the use of
Live Upgrade, engineers can upgrade without shutting down the system processes
until you activate the new system software.
Live Upgrade, engineers can upgrade without shutting down the system processes
until you activate the new system software.
Time to Complete
The actual upgrade to SR 2.8 must be completed within a single maintenance
window that usually starts around midnight. A few pre-upgrade procedures,
consisting mainly of system checks, backups, and various operations upon the
metadevices of the DNCS, can be completed before the maintenance window begins.
window that usually starts around midnight. A few pre-upgrade procedures,
consisting mainly of system checks, backups, and various operations upon the
metadevices of the DNCS, can be completed before the maintenance window begins.
Our engineers have determined that a typical site can be upgraded within one
maintenance window. See Scheduling Requirements (on page 24) for additional
details.
maintenance window. See Scheduling Requirements (on page 24) for additional
details.
System Performance Impact
Interactive services will not be available during the maintenance window.