Cisco Model D-PCG1000 PowerKEY CAS Gateway Installation Guide
Chapter 1 Upgrading the QPSK Software
4
4022031 Rev B
Verify the Current Software Version on the DNCS
Introduction
Before attempting to upgrade to QPSK G08, verify the number of configuration files
in use and what QPSK software version is associated with each configuration file.
in use and what QPSK software version is associated with each configuration file.
On occasion, for testing purposes, the configuration file for a test device or a set of
test devices is changed to a non-standard value (for example qpsk111.config instead
of qpsk.config). If your site has been involved in this type of testing (and you are
now ready to use the released code again), you should update the configuration file
setting for your test units to reflect the default values.
test devices is changed to a non-standard value (for example qpsk111.config instead
of qpsk.config). If your site has been involved in this type of testing (and you are
now ready to use the released code again), you should update the configuration file
setting for your test units to reflect the default values.
Note: The default configuration file for the QPSK is /tftpboot/qpsk.config.
Failure to correct a unit from using a unique configuration will result in the unit
remaining in the uniquely-specified configuration. Specifically, it will not load the
new code and it will continue to load the code specified in the unique configuration
file.
remaining in the uniquely-specified configuration. Specifically, it will not load the
new code and it will continue to load the code specified in the unique configuration
file.
In extremely rare cases, the configuration file may have been specified in or may
need to be specified in the /etc/bootptab file. In the event that a headend device fails
to load the code you intended it to receive, you should check to see if a unique file
was specified either through the DNCS GUI or in the /etc/bootptab file before
contacting Cisco Services for assistance.
need to be specified in the /etc/bootptab file. In the event that a headend device fails
to load the code you intended it to receive, you should check to see if a unique file
was specified either through the DNCS GUI or in the /etc/bootptab file before
contacting Cisco Services for assistance.
Checking for Multiple Config Files
1 From the DNCS Administrative Console, click Utilities and click xterm. The
xterm window opens.
2 Type dbaccess dncsdb <<% and press Enter.
3 Type unload to qpskdata select qmod_name, configfile from davic_qpsk; and
3 Type unload to qpskdata select qmod_name, configfile from davic_qpsk; and
press Enter.
4 Type % and press Enter. A result, similar to the following output, appears.