Version 11 (modified by 9 years ago) (diff) | ,
---|
Enterprise
Short CPDLC Regression Run (Groups 1-3)
Scenario Locations
- sdrr4:/usr/local/scenarios/Enterprise-ead400
- sdrrdc:/usr/local/scenarios/Enterprise-ead400
SDRR Bring Up
- For SLC/TB4
- Login to sdrr4 as task23
- cd Enterprise
- Launch sdrr: ./runsdrr
Run Scenario Injector
- For SLC/TB4
- Login to sdrr4 as task23
- cd Enterprise
- Execute injector script:
- Using port 9601: ./enterprise-msg-inj-ead400+ -g "group #"
- Using port 9602: ./enterprise-msg-inj-9602-ead400+ -g "group #"
- Example: ./enterprise-msg-inj-ead400+ -g 1 (will inject messages from group 1)
- *Note need to hit enter twice to start injecting messages
Altys Bring Up
- Open rdesktop as peer3
- Start PEERMaster
- Select MasterConf file for Radios 3 and 4
- EACP File: /PEER3/work/ScenarioMng/ScenarioFiles/Enterprise/Enterprise-short-cpdlc-r3-r4.eacp
- Groups File:
- Standard Run: /PEER3/work/ScenarioMng/Groups/Groups-Enterprise.xml
- Push DCL: /PEER3/work/ScenarioMng/Groups/Groups-Enterprise-push-DCL.xml
- Start PEERMaster
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 sdrr scenario then the logins will be entered before flight plans which will cause them to be rejected.
Extended CPDLC Regression Run (Groups 4a-b, 5)
Scenario Locations
- sdrr4:/usr/local/scenarios/Enterprise-ead400
- sdrrdc:/usr/local/scenarios/Enterprise-ead400
SDRR Bring Up
- For SLC/TB4
- Login to sdrr4 as task23
- cd Enterprise
- Launch sdrr: ./runsdrr
Run Scenario Injector
- For SLC/TB4
- Login to sdrr4 as task23
- cd Enterprise
- Execute injector script:
- Using port 9601: ./enterprise-msg-inj-ead400+ -g "group #"
- Using port 9602: ./enterprise-msg-inj-9602-ead400+ -g "group #"
- Example: ./enterprise-msg-inj-ead400 -g 4a (this will inject messages from group 4a)
- *Note need to hit enter twice to start injecting messages
Altys Bring Up
- Open rdesktop as peer3
- Start PEERMaster
- Select MasterConf file for Radios 3 and 4
- EACP File: /PEER3/work/ScenarioMng/ScenarioFiles/Enterprise/Enterprise-Extended-r3-r4.eacp
- Groups File:
- Standard Run: /PEER3/work/ScenarioMng/Groups/Groups-Enterprise.xml
- Push DCL: /PEER3/work/ScenarioMng/Groups/Groups-Enterprise-push-DCL.xml
- Start PEERMaster
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 sdrr scenario then the logins will be entered before flight plans which will cause them to be rejected.
Fallback to PDC Run (Groups 12a-e )
Scenario Locations
- sdrr4:/usr/local/scenarios/Enterprise-ead400
- sdrrdc:/usr/local/scenarios/Enterprise-ead400
SDRR Bring Up
- For SLC/TB4
- Login to sdrr4 as task23
- cd Enterprise
- Launch sdrr: ./runsdrr
Run Scenario Injector
- For SLC/TB4
- Login to sdrr4 as task23
- cd Enterprise
- Execute injector script:
- Using port 9601: ./enterprise-msg-inj-ead400+ -g "group #"
- Using port 9602: ./enterprise-msg-inj-9602-ead400+ -g "group #"
- Example: ./enterprise-msg-inj-ead400 -g 12a (this will inject messages from group 12a)
- *Note need to hit enter twice to start injecting messages
Altys Bring Up
- Open rdesktop as peer3
- Start PEERMaster
- Select MasterConf file for Radios 3 and 4
- EACP File: /PEER3/work/ScenarioMng/ScenarioFiles/Enterprise/FallbackToPDC-r3-r4.eacp
- Groups File:
- Standard Run: /PEER3/work/ScenarioMng/Groups/Groups-Enterprise.xml
- Push DCL: /PEER3/work/ScenarioMng/Groups/Groups-Enterprise-push-DCL.xml
- Start PEERMaster
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 sdrr scenario then the logins will be entered before flight plans which will cause them to be rejected.
KBOI Manual CPDLC/PDC Run (Groups 21 & 22)
Scenario Locations
- sdrr4:/usr/local/scenarios/Enterprise-ead400
- sdrrdc:/usr/local/scenarios/Enterprise-ead400
SDRR Bring Up
- For SLC/TB4
- Login to sdrr4 as task23
- cd Enterprise
- Launch sdrr: ./runsdrr
Run Scenario Injector
- For SLC/TB4
- Login to sdrr4 as task23
- cd Enterprise
- Execute injector script:
- Using port 9601: ./enterprise-msg-inj-ead400+ -g "group #"
- Using port 9602: ./enterprise-msg-inj-9602-ead400+ -g "group #"
- Example: ./enterprise-msg-inj-ead400+ -g 1 (this will inject messages from group 1)
- *Note need to hit enter twice to start injecting messages
Altys Bring Up
- Open rdesktop as peer3
- Start PEERMaster
- Select MasterConf file for Radios 3 and 4
- EACP File: /PEER3/work/ScenarioMng/ScenarioFiles/Enterprise/Enterprise-kboi-manual-cpdlc-r3-r4.eacp
- Groups File:
- Standard Run: /PEER3/work/ScenarioMng/Groups/Groups-Enterprise.xml
- Push DCL: /PEER3/work/ScenarioMng/Groups/Groups-Enterprise-push-DCL.xml
- S1P2/KBOI: /PEER3/work/ScenarioMng/Groups/Groups-Enterprise-s1p2-kusa.xml
- Start PEERMaster
KBOI Logons Run (Groups 25 & 26)
Scenario Locations
- sdrr4:/usr/local/scenarios/Enterprise-ead400
- sdrrdc:/usr/local/scenarios/Enterprise-ead400
SDRR Bring Up
- For SLC/TB4
- Login to sdrr4 as task23
- cd Enterprise
- Launch sdrr: ./runsdrr
Run Scenario Injector
- For SLC/TB4
- Login to sdrr4 as task23
- cd Enterprise
- Execute injector script:
- Using port 9601: ./enterprise-msg-inj-ead400+ -g "group #"
- Using port 9602: ./enterprise-msg-inj-9602-ead400+ -g "group #"
- Example: ./enterprise-msg-inj-ead400 -g 1 (this will inject messages from group 1)
- *Note need to hit enter twice to start injecting messages
Altys Bring Up
- Open rdesktop as peer3
- Start PEERMaster
- Select MasterConf file for Radios 3 and 4
- EACP File: /PEER3/work/ScenarioMng/ScenarioFiles/Enterprise/Enterprise-kboi-logons-r3-r4.eacp
- Groups File:
- Standard Run: /PEER3/work/ScenarioMng/Groups/Groups-Enterprise.xml
- Push DCL: /PEER3/work/ScenarioMng/Groups/Groups-Enterprise-push-DCL.xml
- S1P2/KBOI: /PEER3/work/ScenarioMng/Groups/Groups-Enterprise-s1p2-kusa.xml
- Start PEERMaster
back to: DatacommProcedures