Deploying OneSAF in Your Environment - OneSAF Public Site

OneSAF I2S 

Deploying OneSAF in Your Environment 

September 2012 

Distribution A – Approved for Public Release – Distribution is Unlimited

Deploying OneSAF in Your Environment 

‭ 

Topics 

Simulation Control (Workstations) 

Simcores 

Interop 

Dynamic Terrain (DT) Server 

MC Adapter 

System Configuration and Asset Manager Tool (SCAMT) 

AAR 

RDT 

OneSAF Properties 

Version 6.0 Enhancements 

Example Configurations 


2

Simulation Control 

‭ 

‭ 

MCT 

Standard workstation for Operators and Battlemaster 

Can control all aspects of the simulation 

Privilege set determines what operator can use 

Usage tips 

• In large simulation Battlemaster should have 8 GB of RAM 

• Typically have two Battlemasters in large system 

• Operator workstations should be configured for PubSub 

Ares 

3D Operator Workstation 

Modern video card required 

High memory needs, dependent on entity count and terrain 

• 12k entities on SWA terrain – 16 GB 

• 100 entities on JRTC terrain – 4 GB 


3

Simulation Control 

‭ 

‭ 

MCT Lite (v6.0) 

MCT Optimized for Operator Workstation 

No battlemaster controls 

Simplified interface 

WebSAF (v6.0) 

Javascript/HTML 5 based web client 

Requires User Data Gateway (UDG) composition on the server side 

Limited functionality compared to MCT 

Primarily intended as an Operator Workstation but has some simulation 

state control capability 

• Load/Run/Stop scenario 


4

Simcores 

‭ 

‭ 

Determining power and number of simcores 

Fewer, more powerful, simcores is better (3 – 6) 

Should have a little more than you need 

Memory needs 

• 4 GB RAM for most scenarios 

• 6-8 GB RAM for very large scenarios 

Number of operator workstations can effect simcore performance 

OneSAF effectively can use 4-6 processor cores 

Simcore for our larger scale exercises: 

• 12k mr entities, 15 operator workstations (14 MCT, 1 Ares) 

• 3 Simcores (Dell Z800, 24 core, 48 GB) – this is overkill 

Usage Tips 

Late join (post initialization) an extra simcore to deal with mid-run load increases. 

• Adding new entities 

• Simcore lost 


5

Interoperability 

‭ 

OneSAF Interop 

Typically this is on its own simulation node but can be added to others 

Each Interop node has a single configuration (DIS, VDIS, HLA) 

System will handle multiple interop nodes 

• Example: Can connect to an HLA federation from one node and DIS 

from another (maybe for a stealth) 

Inbound interop in most expensive. 

• If part of a federation with a lot of external entities, the interop node 

needs to be more powerful. 


6


‭ 

DT Server 

There are two modes for the DT Server 

• Network Singleton (default) 

– No configuration needed 

– System determines where the process should run 

– Automatically moves to a new node if the node it is on goes 

down. 

• Specifically configured DT Server Node 

– Use‭application:‭“dtserver” 

– If that node goes down, there is no DT until it is brought back in 

Mode controlled by the property: 

• net.onesaf.core.services.erc.useNetworkSingletonForDT 

The entire system should be set for the same thing or there could be 

significant problems 

• Recommend setting as a global property in the SCAMT 


7

MC Adapter 

‭ 

MC Adapter Options 

CS 11/12(VMF and DDS) vs SW Block 2 (VMF and PASS) 

One MC Adapter per OneSAF Cluster 

All MC Devices need to be on the same tactical network (even across 

sites) 

MC Adapter by default will send out situational awareness for all comms 

enabled entities in OneSAF 

• Includes location reports, observations reports, and overlays 

• Can change this option with property: 

net.onesaf.services.sys.props.C2AdapterModeling 

MC Adapter can send out situational awareness for other HLA federates 

using a JLVCID to URN mapping file 


8

MC Adapter 

‭ 

MC Adapter Usage Tips 

Identify your address book (LDIF) ASAP. All devices must know about 

each other to talk to each other 

Make sure your IP routing tables are correct on your MC Adapter 

machine 

If you are using VMF, make sure your multicast routing is enabled on 

your routers 

Export URNs from the Task Org to have a spreadsheet of who has what 

URN in your scenario 


9


‭ 

DT Server 

Recommend using specifically configured DT Server for any large or 

medium scale system. 

• Provides better control and prevents it from interfering with simcores 

If not expecting significant DT, can use Network Singlton for DT and dial 

down the amount of a simcore it will take up 

• net.onesaf.core.services.erc.DTServerProcessingReserve 

– Default = 99 (as a percent of the node) 

• Note: most DT comes from craters which can be turned off if not 

needed 

– net.onesaf.core.services.erc.generateCraters (default: true) 


10

System Configuration and Asset Manager Tool 

(SCAMT) 

‭ 

SCAMT 

Helps configure, control, and monitor a OneSAF Distribution. 

Recommended for medium and large scale exercises 

To maintain consistent onesaf properties across system, use the 

SCAMT properties settings 

• Can set any number of onesaf properties and it makes sure all 

nodes have that property set 

Not absolutely required 

• OneSAF nodes will connect to each other over a local network if 

given the same exercise id 


11

After Action Review (AAR) 

‭ 

AAR 

As of version 5.5 two AAR systems are supported 

• Power stripes AAR (traditional OneSAF AAR) 

– Use‭application:‭“aar” 

– Windows only 

• AARS 

– Use‭application:‭“aars_remaarc” 

– In addition requires AARS LAARC running and the AARS client 

– LAARC and Client are Windows 7 only 

Both are delivered with OneSAF 5.5 


12

Rapid Deployment Toolkit (RDT) 

‭ 

RDT 

Set of scripts to deploy, configure and manage a distribution 

Deploy OneSAF to a whole lab from one computer 

Can‭install‭from‭“bare‭metal”‭to‭a‭list‭of‭computers 

• Loads‭Red‭Hat‭5.5‭AGM‭when‭installing‭“bare‭metal” 

Can be used to deploy patches to all computers in the distribution 

Helps‭configuration‭management‭of‭the‭distribution‭by‭setting‭the‭“Build”‭ 

tag with each patch that shows up in the OneSAF splash screen 

• Helps make sure all OneSAFs are using the same patch version 

• Stored in: PAIR/properties/version/sequence.txt 

Start/Stop RCS and SCAMT on all computers in the distribution from 

one computer 

Synce scenarios, properties, and preferences among all computers 

Utility scripts to check disk space, logs, turn off screen saver, and more 


13


‭ 

Useful Properties to consider 

Suppression: net.onesaf.coreservices.sys.props.suppressionEffects 

• Turning it off also removes degraded components capability 

Echelon Display: 

net.onesaf.core.services.sys.props.highestEchelonDisplayDefault 

• Sets the default display level in the MCT 

• Improves performance of the Battlemaster at really large scale 

exercises (40k+ entities) 

Deviate from AAMSA: 

net.onesaf.core.services.sys.props.allowDeviationsFromAMSAA 

• Enables additional data sets in AAMSA based models when 

AMSAA data is not necessary 


14


‭ 

Useful Properties to consider 

Entity Avoidance: 

net.onesaf.core.services.sys.props.entityAvoidanceEnabled 

• Makes it look better for visual systems and provides some more 

realistic effect 

• Degrades performance of system 

Sensor range clipping: 

net.onesaf.services.sys.props.operationalSensorRangesEnabled 

• Improves‭performance‭by‭clipping‭sensors‭at‭their‭“official”‭ranges 

• This is not officially endorsed by AMSAA 


15

Version 6.0 Additional Considerations 

‭ 

New capabilities that effect configuration 

OSS (ODB Sync Service) 

• Allows a cluster of operators across a WAN 

• Only operator workstations (MCT, MCT-Lite, Ares) and a C2 

Adapter can be on the client side 

• Requires an OSS Server node on the server side and an OSS 

Client node on the client side 

User Data Gateway 

• Provides a web services interface to OneSAF 

WebSAF 

• Requires a UDG node on OneSAF 

• Requires a map server and an icon server (can be configured on a 

OneSAF node) 

NOTE: All of these have network and firewall setup to function over a 

WAN 


16

Version 6.0 Additional Considerations 

‭ 

New capabilities that effect configuration 

Reduced System Footprint 

• Work is being done to configure multiple OneSAF nodes on a 

single, more powerful machine 

• Goal is 2-3 computers for all back end applications 

– Simcores 

– DT Server 

– C2 Adapter 

– Interop 

– UDG 

– OSS 

• Target Hardware: 

– Dell Z800, 24 processor cores, 48 GB RAM 

• SCAMT is being updated to support 


17

Example Configurations 


18

Small Event 


19

Large Event 


20

Multi-Cluster Distributed 


21

Virtual SAF 


22

Distributed Operations (v6.0) 


23

Back Up Slides 

Note: this slide used to indicate conclusion of briefing segment (no text) 

or Back Up Slides 

September 2012 24

Deploying OneSAF in Your Environment - OneSAF Public Site

Create successful ePaper yourself

Delete template?

Save as template?