Failure Recovery

Scenario Locations

• sdrr4:/usr/local/scenarios/Failure-Recovery
• sdrr3:/usr/local/scenarios/Failure-Recovery
• sdrrdc:/usr/local/scenarios/Failure-Recovery

Altys Bring Up

Failure Recovery groups 1, 2, and 3 each have their own Altys scenario to load. The table below lists the files to select for each group when running Altys. If running with Push DCL, use the Push DCL Groups file when prompted for the groups file by PEERMaster.

Group	MasterConf	EACP File	Groups File	Push DCL Groups File
1	MasterConf-R3.xml	Failure-Recovery-Group1-r3.eacp	Groups-Failure_Recovery.xml	Groups-Failure-Recovery-Push-DCL.xml
2	MasterConf-R4.xml	Failure-Recovery-Group2-r4.eacp	Groups-Failure_Recovery.xml	Groups-Failure-Recovery-Push-DCL.xml
3	MasterConf-R7.xml	Failure-Recovery-Group3-r7.eacp	Groups-Failure_Recovery.xml	Groups-Failure-Recovery-Push-DCL.xml

• Open rdesktop as peer3
• Start PEERMaster and load files listed above for the group you are running.

SDRR Bring Up

• For SLC/TB4
  • task23@sdrr4:~/Failure-Recovery/zlc/runsdrr-zlc
• for HOU/TB3:
  • task23@sdrr3:~/Failure-Recovery/zhu/runsdrr-zhu

Run MSG Injector

• For SLC/TB4:
  • task23@sdrr4:~/Failure-Recovery/zlc/zlc-failure-recovery-msg-inj
• For HOU/TB3:
  • task23@sdrr3:~/Failure-Recovery/zhu/zhu-failure-recovery-msg-inj
• Groups 10 and 11 are only on SLC. So, for example, if they requested that you run groups 1 for SLC and HOU and group 10 you would have 3 instances of the msg injector running in 3 different xterm windows as follows:
  • task23@sdrr4:~/Failure-Recovery/zlc/zlc-failure-recovery-msg-inj -g 1
  • task23@sdrr4:~/Failure-Recovery/zlc/zlc-failure-recovery-msg-inj -g 10
  • task23@sdrr3:~/Failure-Recovery/zhu/zhu-failure-recovery-msg-inj -g 1

back to: DatacommProcedures