Cisco Headend System Release 3.2 Installation Guide

Page of 112
 
 
 
Process Overview 
 
4042389 Rev A 
93 
 
9  Take all of the Disaster Recovery jobs off of hold. See Take Disaster Recovery 
Jobs Off Hold (on page 102). 
Note: Verify that Disaster Recovery Near Real Time Syncs and Periodic Syncs are 
successful. These two syncs will keep the data between the Primary DNCS and 
Standby DNCS synchronized until the maintenance window opens and the 
Disaster Recovery Switch-Over is performed. It is strongly recommended that 
the customer not modify any of the DBDS elements (QAMs, QPSKs, Netcrypts, 
etc.) as well as no modification of the logical DBDS entities (channel maps, 
sources, services etc.). The Disaster Recovery Near Real Time Sync and Periodic 
Sync processes will only keep DHCT-related data/configs and Impulse Pay-Per-
View events and purchase data synchronized between the Primary DNCS and 
Standby DNCS. 
10  Customer needs to make Go/No-Go decision regarding whether to proceed with 
the Switch-Over to the Standby DNCS during the next maintenance window. 
11  Perform a Disaster Recovery Switch-Over. This process makes the Standby 
DNCS the Active DNCS and the Primary DNCS the Inactive DNCS. 
12  Verify that the Switch-Over was successful by: 
a  Verifying that the correct network switch ports on the Primary DBDS 
isolation network switch are down and that the correct network switch ports 
on the Standby DBDS isolation network switch are up. 
b  Verifying that the Disaster Recovery "bit-bucket" and "QAM emulation 
gateway" are no longer present in the Standby DNCS routing table. The bit-
bucket IP address is 192.168.1.4 and the "QAM emulation gateway" address is 
the Standby MC IP address. 
- netstat -rvn |grep 192.168.1.4 
Note: You should not see any occurrence of 192.168.1.4 in the routing table. If 
you do, you will want to flush the routing table and then setup the correct 
routes by executing the /etc/rc2.d/S82atminit file. 
- route -f  
- netstat -rvn |grep <Standby MC IP Address> 
Note: You should not see any occurrence of the Standby MC IP address in 
the routing table. If you do, you will want to flush the routing table and then 
setup the correct routes by executing the /etc/rc2.d/S82atminit file. 
13  On the Standby DBDS System, verify that a DHCT can boot and can receive 
advanced services (VOD, IPG, xOD, SDV, etc.). You will want to boot and verify 
SARA, Aptive/Pioneer, and MDN/ODN DHCTs if you have them. You will also 
want to verify billing server connectivity. Troubleshoot any issues before 
proceeding. 
14  Customer needs to make Go/No-Go decision regarding whether to proceed or 
Switch-Back to the Primary DNCS.