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
  • Open the bat-files folder
  • Select one of the following:
    • Failure-Recovery-Group1.bat - Shortcut
    • Failure-Recovery-Group2.bat - Shortcut
    • Failure-Recovery-Group3.bat - Shortcut

SDRR Bring Up

• For SLC/TB4
  • Log in to sdrr4 as task23
  • Change directory to Failure-Recovery/zlc
    cd Failure-Recovery/zlc
  • Execute the runsdrr script
    ./runsdrr-zlc
• for HOU/TB3:
  • Log in to sdrr3 as task23
  • Change directory to Failure-Recovery/zhu
    cd Failure-Recovery/zhu
  • Execute the runsdrr script
    ./runsdrr-zhu

Run Scenario Injector

• For SLC/TB4:
  • Log in to sdrr4 as task23
  • Change directory to Failure-Recovery/zlc
    cd Failure-Recovery/zlc
  • Execute the message injector script
    ./zlc-failure-recovery-msg-ing -g <group number>
• For HOU/TB3:
  • Log in to sdrr3 as task23
  • Change directory to Failure-Recovery/zhu
    cd Failure-Recovery/zhu
  • Execute the message injector script
    ./zhu-failure-recovery-msg-ing -g <group number>
• Groups 10 and 11 are only on SLC
  For example, if you are requested to run groups 1 and 10 you would have 3 instances of the message injector running (2 for SLC and 1 for HOU) 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

Additional Notes

Ensure that Altys and the scenario injector are started as close to the same time as possible. If Altys is started too far ahead of the SDRR scenario then the logons will be entered before flight plans which will cause the logons to be rejected.

back to: DatacommProcedures