Cisco Headend System Release 2.7 Installation Guide

Page of 154
 
Chapter 5    SR 5.0 Post Upgrade Procedures 
 
 
 
78 
4042225 Rev A 
Run fixSiteConfigs on the RNCS 
Only perform this procedure if the site you are upgrading has an RNCS system. If 
the site you are upgrading does not have an RNCS, skip this procedure and go to the 
next procedure in this chapter. 
This procedure fixes the /tftpboot config files for headend components. It also sets 
the AlarmServerIpAddr entries to the correct IP address for the RNCS. 
1  In a root xterm window on the RNCS, type the following command and press 
Enter
fixSiteConfigs
 
Sample output: 
# fixSiteConfigs
 
     fixSiteConfigs: Fixing config files in lionn1:/tftpboot...
 
     fixSiteConfigs: modified: goqam.config
 
     fixSiteConfigs: modified: gqam.config
 
     fixSiteConfigs: Ignoring platform file 'inet-config'
 
    fixSiteConfigs: modified: mqam.config
 
     fixSiteConfigs: WARNING: unknown tftpboot config file: 'nc.config'
 
    fixSiteConfigs: no mods needed: nc.config
 
     fixSiteConfigs: modified: qam.config
 
     fixSiteConfigs: modified: qpsk.config
 
     fixSiteConfigs: modified: scsmqam.config
 
     fixSiteConfigs: 6 of 9 tftpboot config files were modified
 
2  Type the following command and press Enter
cd /tftpboot
 
3  Verify that each of the .config files contains the correct IP addresses. 
Notes: 
 
The QAM config files contain two IpAddr variables, RpcServerIpAddr and 
AlarmServerIpAddr. These entries should have the following IP addresses 
assigned: 
RpcServerIpAddr = [dncsatm IP Address]
 
AlarmServerIpAddr = [RNCS IP Address]
 
 
If these variables do NOT have the correct IP address assigned, contact Cisco 
Services for assitance. 
 
Ignore any inet-config and nc.config warnings.