Attachment 0013i - D-IBCS-0473_Adv_NetMgr.pdf

UNCLASSIFIED

Copyright 2020 Northrop Grumman Systems Corporation.

UNCLASSIFIED

IBCS.DM.025.25 (Jan20)

Integrated Air and Missile Defense (IAMD)

Battle Command System (IBCS)

Operator/Maintainer Course

Advanced Network Manager

DOCUMENT NUMBER: RELEASE: DOCUMENT DATE:

D-IBCS-0473 001 06 May 2020

CDRL NUMBER: CONTRACT: CONTRACT NUMBER:

N/A IBCS W31P4Q-08-C-0418

EXPORT CONTROL WARNING DISTRIBUTION STATEMENT D

WARNING -This document contains technical data whose export is restricted by the Arms Export Control Act (Title 22, U.S.C., Sec 2751,

et. seq.) or the Export Administration Act of 1979, as amended, Title

50, U.S.C., App. 2401 et. seq. Violations of these export laws are subject to severe criminal penalties. Disseminate in accordance with provisions of DoD Directive 5230.25.

Distribution authorized to DoD and U.S. DoD contractors only;

Administrative and operational Use; 26 July 2017. Other requests for this document shall be referred to the IAMD Project Office, Bldg.

5250 Martin Road, Redstone Arsenal, AL 35898.

DISCLAIMER STATEMENT AND DISTRIBUTION

RESTRICTION

The views, opinions, and/or findings contained in this report are those of the author(s) and should not be construed as an official Department of Defense position, policy, or decision, unless so designated by other official documentation.

This document contains information EXEMPT FROM

MANDATORY DISCLOSURE under the FOIA. Exemption 3 (e) apply. (Reference: Army Regulation 25-55)

This material is based upon work supported by the U.S. Army Aviation and Missile Command under Contract No. W31P4Q-08-C-0418.

Prepared for: Prepared by:

Integrated Air and Missile Defense (IAMD)

Battle Command System (IBCS)

Northrop Grumman Defense Systems Sector

Combat Systems and Mission Readiness (CSMR)

Division

213 Wynn Drive

Huntsville, AL 35805-1928

CAGE Code 9F909

W31P4Q-20-R-0015 ATTACHMENT 0013i

D-IBCS-0473, Rel. 001

06 May 2020 ii

Integrated Air and Missile Defense (IAMD)

Battle Command System (IBCS)

Operator/Maintainer Course

Advanced Network Manager

Approval Sheet

SIGNATURES FOR RELEASE:

Author: // Signature on File // 5/6/2020

Pamela A. Gray, IBCS Logistics Training Material Developer Date

Approved by: // Signature on File // 5/6/2020

Rafael Miranda, IBCS Logistics Training Manager Date

Approved by: // Signature on File // 5/6/2020

James Bradley, IBCS Logistics Engineering Manager Date

Approved by: // Signature on File // 5/6/2020

Lori Tatom, IBCS Mission Assurance Manager Date

Approved by: // Signature on File // 5/6/2020

Tim Speece, IBCS Logistics Lead Date

Approved by: // Signature on File // 5/6/2020

Mark Rist, IBCS Program Director Date

Document Release: // Signature on File // 5/6/2020

Kristi Fugit, IBCS Configuration/Data Management Date

Document Type:

Logistics

Preparing Organization (if different from owning organization) Hardware and Software Used

N/A PC Microsoft® Office® Suite

Notes or Comment:

N/A iii

Northrop Grumman Defense Systems

Combat Systems and Mission Readiness (CSMR) Division

IAMD Battle Command System (IBCS)

213 Wynn Drive

Huntsville, Alabama 35805-1928

CHANGE RECORD

Release

Number Date Authority

Pages

Affected Remarks

001 06 May 2020 SOW 3.2.10.9.1 All Initial Release, DCR-6595, PCCB #587 iv

This page intentionally blank.

UNCLASSIFIED D-IBCS-0473, Rel. 001

Advanced Network Manager 06 May 2020

Integrated Air and Missile Defense (IAMD)

Battle Command System (IBCS)

Operator/Maintainer Course

Student Guide

Advanced Network Manager

UNCLASSIFIED

TABLE OF CONTENTS

Lesson 1: Advanced Network Manager Course Introduction

Lesson 2: Perform Advanced Network Manager Procedures

1. Describe the Network Management Window

2. Network Requirements

3. Analyze and Optimize a Plan

4. Describe Cross-Domain Solution (CDS)

5. Perform Network Pruning

6. Perform Manual Pruning

Advanced Network Manager Practical Exercises

Practical Exercise (PE) Overview

1. Directions to Students

2. Practical Exercise Execution

PE 01: Create a Neighbor Table

PE 02: Perform Neighbor Management and Network Pruning

Appendix A: Acronyms and Abbreviations ............................................................ A-1

LIST OF FIGURES

Figure 2-1. Linked EOCs

Figure 2-2. EOC Neighbor Table

Figure 2-3. Pruned and Unpruned Networks

Figure 2-4. Main Script Screen for Manual Pruning

Figure 2-5. Manual Pruning, Option 2

Figure 2-6. Manual Pruning, Option 3

Figure 2-7. Manual Pruning, Option 4

Figure 2-8. Manual Pruning, Option 5

Figure 2-9. Manual Pruning, Option 6

Figure 2-10. Manual Pruning, Option 7

Figure 2-11. Manual Pruning, Option 8

Figure 2-12. Manual Pruning, Option 9

Figure 3-1. PE 01 Mesh Network Diagram

Figure 3-2. PE 01 EOC and Relay Neighbor Table

UNCLASSIFIED

LIST OF TABLES

Table 1-1. Mouse Pointer Icons

Table 2-1. IBCS Message Types

Lesson 1: Advanced Network Manager Course Introduction 06 May 2020

UNCLASSIFIED

LESSON 1: ADVANCED NETWORK MANAGER COURSE

INTRODUCTION

Terminal Learning Objective

Action: Review the scope and framework of the Advanced Network Manager course.

Conditions: Given the IBCS, SUM, and IBCS Advanced Network Manager Student Guide.

Standards: Review advanced course learning objectives, document conventions, system keyboard standards, and supporting documentation locations in the CWMI software.

1. Purpose

a. The Advanced Network Manager course instructs personnel in the operation of advanced Network Management procedures in the IBCS Common Warfighter Machine Interface (CWMI) software.

b. Instruction focuses on specific, task-based standards and advanced learning objectives to successfully navigate and operate the CWMI.

2. Scope

a. The Advanced Network Manager course instructs students on a deeper understanding of the CWMI capabilities in the following areas:

(1) Advanced network requirements and capabilities.

(2) Advanced network analyzation.

(3) Advanced network optimization.

(4) Advance network pruning (CWMI and Manual procedures).

b. Practical exercises provide hands-on experience and reinforce learned tasks.

3. Document Conventions

a. Courier Font: Text an Operator types into a data entry field.

Example: At the prompt, type: adduser

b. Brackets [ ]: Text within brackets is an example or explanation of data required.

Example: At the prompt, type: adduser [username]

c. Angle brackets < >: Indicates keys pressed on a keyboard or buttons clicked on a software display.

Example: Press <Enter> (key). Select <Add> (button).

d. Right angle bracket >: Indicates submenu selections.

Example: At the XYZ window menu bar, select File > New > Folder.

e. <Enter> is pressed after entering text or issuing a command in terminal windows.

UNCLASSIFIED

4. Mouse and Keyboard

a. The CWMI pointing device is a standard two- or three-button mouse.

b. The CWMI uses a standard QWERTY keyboard and provides hot-key alternatives to the mouse.

(1) Reorient the map: press <R>

(2) Zoom in: press <Ctrl> + <Up Arrow>

(3) Zoom out: press <Ctrl> + <Down Arrow>

(4) Rotate clockwise: press <Shift> + <Right Arrow>

(5) Rotate counter-clockwise: press <Shift> + <Left Arrow>

(6) Tilt view up: press <Shift> + <Up Arrow>

(7) Tilt view down: press <Shift> + <Down Arrow>

(8) Pan the map: press Up, Down, Left, or Right Arrow keys

c. Mouse Pointer icons help operators interact with the CWMI user-interface.

Table 1-1. Mouse Pointer Icons

Icon Indicated Action

Single-click

Double-click

Right-click

Mouse Hover/ Mouseover

Drag

5. IBCS Reference Documents

a. Refer to the IBCS Software User Manual (SUM) for complete guidance on system functions and capabilities.

(1) The SUM is a portable document format (PDF) file accessed through the Help tab on the CWMI Ribbon bar.

(2) Request a copy of the SUM from the IAMD Project Office.

b. Refer to the Interactive Electronic Technical Manual (IETM): DRAFT TM-11-5895- 567-13&P.

(1) The IETM is accessible from a Windows-based IBCS Collaborative Environment (ICE) workstation with the IADS4 application and the IETM software installed.

UNCLASSIFIED

(2) Open only four Virtual Windows simultaneously in an ICE.

6. Safety Information

a. Students must be familiar with the safety briefing provided in Module A, IBCS Operator/Maintainer Course Overview (Lesson A02).

b. Ask the instructor about safety concerns.

c. Refer to DRAFT TM 11-5895-567-13&P (IETM) for complete safety information.

Lesson 2: Perform Advanced Network Manager Procedures 06 May 2020

UNCLASSIFIED

LESSON 2: PERFORM ADVANCED NETWORK MANAGER

PROCEDURES

Terminal Learning Objective

Action: Perform advanced Network Manager tasks.

Conditions: Given the IBCS, SUM, and IBCS Advanced Network Manager Student Guide.

Standards: Analyze a plan; optimize a plan; and perform network pruning.

1. Describe the Network Management Window

The Network Management window enables the operator to monitor the network status of Engagement Operation Centers (EOC), Integrated Fire Control Networks (IFCN), network components, and links. Users manage device status, network events, link status, and network analysis and optimization. The following are primary network management functions:

● Monitor Task Force network health status.

● Maintain network topology, and link and device status.

● Perform network pruning.

● Detect network events and outages.

● Maintenance and Diagnostics support – Provides ping status of devices on the Network (Refer to the IBCS Operator/Maintainer Student Guide, Module E: System Maintenance).

a. Open the Network Management window.

(1) Change role to Staff 6 – [S6], if necessary.

(2) Click the Equipment tab on the Ribbon bar.

(3) Click <Network Manager>. The Network Management window opens.

(4) Select an EOC or IFCN on the left side of the window to view the Network Management window tabs.

b. Review the window tabs.

(1) Network Devices tab – Provides status information where devices are the focus.

The tab displays data for the selected EOC or IFCN Relay.

(a) A Device Status box in the bottom-left of the window shows cross-reference color codes for the Network Devices tab.

1) Green – Operational

2) Amber – Degraded

3) Red – Non-Operational

4) Grey – Unknown

5) Green radar icon – Connectivity, can be pinged.

6) Red radar icon – No connectivity, cannot be pinged.

(b) Network Map tab – Displays a graphical representation of the connections and the status of each device.

UNCLASSIFIED

(c) FCN Devices tab – Displays the status of Fire Control Network (FCN) devices.

(d) Mission Critical Devices tab – Displays the status of mission-critical devices.

(e) Non Mission Critical Devices tab – Displays the status of non-mission-critical devices.

(f) External Links tab – Displays the status of tactical devices.

(2) Network Events tab – Displays network events.

(a) Network events list in the order received.

(b) Each event provides information: Severity, Event Type, Description, Physical Location, Device, Time Stamp, and Report Available.

(c) Click an event to view more information. When a report is available, a report screen opens displaying event details.

(d) Use the search option to filter event records.

(3) Links tab – Provides status information where links are the focus.

(a) EOCs and IFCN Relays list on the left side of the window.

(b) Click an EOC to expand the area and view each EOC linked to the one selected.

(c) Click one of the items to display a graphical representation of all links associated with the EOC, as shown in Figure 2-1.

Figure 2-1. Linked EOCs

(d) The line color represents link status (i.e., green, amber, red, and grey).

(e) Click a link to open a pop-up window displaying the link Burst Rate, Average Data Rate, and Packet Loss information.

1) Burst Rate – Amount of data sent or received in one intermittent operation.

UNCLASSIFIED

2) Average Data Rate – Average data rate sent or received.

3) Packet Loss – Percentage of packets lost with respect to packets sent.

(4) Network Control tab – Provides tools to analyze and optimize the network.

(a) Comms Control tab – Provides a list of all Comm Nodes, related Neighbor settings, and nodes manually pruned.

(b) Analyze/Optimize tab – Provides tools to analyze and optimize a plan and proposed plans.

2. Network Requirements

a. IBCS Message Types

(1) Table 2-1 displays IBCS message types and associated network requirements for delivery and latency.

(2) Mission Critical Messages and Engagement Support Track-Related Messages require a latency no greater than 400 milliseconds (ms) at 99.9% and 90% reliability. For example, 999/1000 Mission Critical Messages must arrive within 400 ms. The message types drive the network design.

Table 2-1. IBCS Message Types

Message Type Required

Delivery % Required Latency

Mission Critical Messages 99.90% 400 ms

Engagement Support Track-Related Messages 90% 400 ms

High Priority Situational Awareness Track-Related Messages 90% 1.3 sec

Time-Sensitive *C2 Messages 90% 3.0 sec

Force Operations Survival Information Messages 95% 5 sec

Low Priority Situational Awareness Track-Related Messages 90% 5.3 sec

Force Operations Time-Sensitive Messages 95% 8 sec

Force Operations Aggregate Routine Messages 95% 30 sec

Force Operations Non-Real-Time-Sensitive Messages 95% 900 sec

*C2: Command and Control.

b. IFCN Basic Concept

Several systems feed information into IBCS, and access into the IFCN is tightly control.

The systems convert external messages into IBCS messages, allowing traffic to be prioritized and routed correctly.

(1) Link 16 feeds into the IFCN through the Gateway EOC ADSI.

(2) Secret Internet Protocol Router (SIPR) feeds into the IFCN through the red firewall (i.e. voice, Air Tasking Order (ATO), Airspace Control Order (ACO), and 3011c).

(3) Sensors/Launchers feed into the IFCN through the B-Kit.

UNCLASSIFIED

c. IFCN Key Components

The following basic components are required for IFCN traffic:

(1) HRFU + BPU (HNR) = converts IP/Ethernet data to Radio Frequency (RF) to communicate with other EOCs/Relays.

(2) Black Router = Prioritizes traffic and decides the traffic route between HNR, ALT- Media.

(3) Black Firewall/ ISO Router = provides a cyber approved path to the Warfighter Information Network-Tactical (WIN-T) Non-Classified Internet Protocol (NIPR).

(4) KG-250 (Type-1 Encryption) = provides National Security Agency (NSA) approved encryption for Classified “Red” Traffic to be transported over RF.

(5) CDS = Cross-Domain Solution (CDS) allows very specific traffic to flow between High (Classified) and Low (Unclassified) Networks. For example, the CWMI on the Red Side can monitor devices on the Black Side (e.g. HNR, Black Router, etc.) and perform HNR pruning from the CWMI.

(6) Red Router = responsible for prioritizing Red network traffic and deciding the traffic routes.

(7) Red Firewall/ ISO Router = provides a Cyber approved path to WIN-T Secret Internet Protocol Router (SIPR).

(8) Red Switch = provides a network connection point for Red systems (Servers, Workstations, etc.).

d. Highband Networking Radio (HNR)

(1) Provides interoperable, long-range secure, self-forming, self-healing network backbone for stationary, and on-the-move platforms.

(2) Integrates directive-beam technology with mobile, ad hoc mesh networking, and achieves burst data rates of up to 54 Mbps.

(3) Latency per Hop, Range limitations, and Throughput Limitations.

(a) Latency per hop is ~50 ms, when a special queue for <400 ms messages that push the average latency per to hop to around 35 ms. This drives the maximum diameter of a IBCS Task Force to 10.

(b) Range is radio/antenna/line-of-sight (LOS) limited.

(c) Throughput is driven by range and network topology, which is why pruning is so important.

(d) IBCS plans for 18 Mbps or greater links, and up to 3 neighbors per node.

Maximum distance to achieve 18 Mbps or higher is ~27 km or less between linked MEIs.

e. Preferred Neighbors / Pruning

The pruning approach consists of three steps:

(1) Establishing the unpruned large meshed network.

(2) Searching for the depth and width of a small network.

UNCLASSIFIED

(3) Transferring the knowledge from the unpruned large network to the searched small network, consisting of no more than 3 links/paths per-node.

f. HNR Emplacement:

(1) Permissible emplacement of the HNR in relation to a Radar to avoid damage/interference to the radio.

(2) Placement of an HNR within 50 m to the rear of and radar and within 1500 m in front of a radar can cause damage to the equipment.

g. Data Distribution Manager (DDM):

(1) The IFCN consolidates of data from multiple sources so that it can be used strategically.

(2) DDM prioritizes and meters out various track messages based on high to low priority schema.

(3) DDM constantly monitors the overall load that sensors are putting on the network and will adjust what priority and at what rate messages are put on the network dynamically.

(4) Track data is prioritized based on the System Adjustable Parameter (SAP) found in the defense plan which is based on the overall throughput capacity of the network.

(a) When the throughput of the network cannot handle the track load, lower priority track updates are either limited in their published rate and or dropped completely to ensure higher priority and Critical messages are sent.

(b) A carefully managed data pipeline helps to provide reliable track data.

3. Analyze and Optimize a Plan

a. Analyze the current plan.

(1) Click the Analyze/Optimize Network tab. The Analyze/Optimize Network view displays.

(2) Observe the analysis of the current plan displayed in the window.

b. Optimize using a proposed plan.

(1) Click <Generate a Pruning Solution> to display an analysis of the proposed plan.

The results for the new plan display in the Proposed Plan column.

(a) Network Edge Connectivity – The number of edge disjoint paths between all node pairs in the network plan.

(b) Network Diameter – Length of the longest of the shortest path between any node pairs. Longer paths have more latency. An HNR network with a diameter greater than 10 hops may not achieve IFCN latency requirements.

(c) Second Network Diameter – Length of the longest of the remaining shortest path between any node pairs when their shortest path is deleted from the network. The value indicates the degree of Quality of Service (QoS) lost due to link outages. A robust network increases diameter by no more than one hop when a link is lost.

UNCLASSIFIED

(d) Link Rate <12 Mbps – The percent of links with a predicted or measured burst rate of less than 12 Mbps.

(e) Minimum Node Degree – The smallest number of links at any node.

(f) Maximum Node Degree – The largest number of links at any node.

(g) Average Node Degree – The average number of links at the nodes.

(h) Average Azimuth Deviation – The difference from the average azimuth spacing between links to equal azimuth spacing (i.e. 360°/node-degree) averaged over all nodes.

(i) Poor Rate Separation – The fraction of nodes with links separated by more than three data rate steps.

(j) Expected Throughput – The estimated load that the IFCN Plan network delivers without congestion.

(2) Click <Use Proposed Plan> button and automatically prune the system based on system recommendations.

4. Describe Cross-Domain Solution (CDS)

a. The Cross-Domain Solution (CDS) transfers data between the black side (unclassified) and the red side (classified), providing the following IBCS capabilities:

(1) Full network topology and pruning.

(2) Monitoring of remote IFCN Relay equipment.

(3) Detection of outages.

(4) Receiving Continuous Built-In Test (CBIT) and IFCN alerts for relays only equipped with black-side comms hardware.

(5) Use of IFCN Relays without classified equipment in a network. The capability places unclassified relays in remote locations, without guards, to keep the relay secure.

b. CDS and Integrated Defense Design (IDD)

(1) Network Manager (NM) uses Support Control because it affects the amount of Simple Network Management Protocol (SNMP) traffic going over the IFCN for black-side relay monitoring.

(a) A preference of 3 subordinates, and no more than 6, is a good ‘rule of thumb’ for planning purposes due to the amount of IFCN traffic generated by monitoring subordinate relays.

(b) If a limit of 3 subordinates is unrealistic, the Quality of Service (QoS) policy should prevent Network Manager (NM) from degrading IFCN performance for other Computer Software Configuration Items (CSCI).

(c) Too many subordinates may result in occasionally dropped SNMP messages for NM, but has no adverse impact on other IFCN consumers.

(d) Only the EOC having Support Control can send the IFCN Relay commands from Network Manager.

UNCLASSIFIED

(2) No automatic transition of Support Control to another EOC is possible if an EOC is lost to equipment failure—such as the loss of the CDS.

(a) Operators manually transition the functionality to an operational EOC with a working CDS “Support Control” of the relay for NM to continue black-side monitoring.

1) Select TF Configuration.

2) Select Support Control

3) Select the drop-down menu next to the EOC that formerly had Support Control.

4) Select the IFCN Relay of interest and <Remove>.

5) Select the new EOC from the drop-down menu and ADD the IFCN Relays needing assignment:

(b) The defense plan is updated and activated to give to the operational EOC.

(3) Three links per comm node (EOC or IFCN Relay) is the optimal number of links for an IBCS network.

(4) Before sending a defense plan, classified comm nodes display as green on the network map, and unclassified comm nodes display as grey.

c. CDS and Network Management

(1) An EOC must be off the network when performing node isolation.

(2) Always reassign control of IFCN relays controlled by the EOC to another EOC first.

(3) Never perform node isolation during mission critical times—this reboots the radios.

5. Perform Network Pruning

a. Pruning is the process of limiting and prioritizing network neighbors to optimize the network for increased network throughput.

(1) Throughput is a measure of the amount of data a network can transmit in a given time.

(2) When networks attempt to exceed their capacity, bandwidth saturation occurs.

(3) The available throughput for the network is reduced when nodes have too many active RF links.

UNCLASSIFIED

b. By default, the HNR radio defaults to the maximum numbers of 6 nodes, which quickly uses up radio resources just creating redundant and alternative paths.

(1) Pruning reduces the overhead by eliminating unneeded links based on the network topology, and prioritizing the links that are critical so that the network laydown consistently in the topology designed.

(2) This increases the amount of resources each HNR radio has available to carry IBCS traffic, which increases the overall effective throughput of the network.

c. Perform pruning to optimize your network when creating or modifying a defense plan, or when the network topology changes.

d. A Neighbor Table is used when planning an IFCN; and helps determine which links to prune in the network.

(1) Figure 2-2 is an example of a Network Table listing assets along the top and left side.

(2) Place an X in the cell correlating with the link to keep between assets.

(3) Identify no more than 3 links for each node.

Figure 2-2. EOC Neighbor Table

UNCLASSIFIED

e. Figure 2-3 shows a pruned and unpruned network, also called a Mesh Network.

Figure 2-3. Pruned and Unpruned Networks

NOTE: If the CDS is not operational, manual pruning may be required.

f. Prune an EOC through CWMI.

(1) Change role to Staff 6 – [S6].

(2) Click <Network Manager> on the Equipment tab. The Network Management window opens.

(3) Click the Network Control tab.

(4) Select the Comms Control tab.

(5) Select an EOC from the Comm Node list on the left side of the window. The Comm Node Control screen displays settings for the EOC.

(6) Select the Maximum Number of Neighbors for the currently selected node to establish communication.

(a) The maximum value is 6.

(b) The optimal value is 3.

(c) A value greater than three will degrade the network.

(d) Increasing the number of nodes increases the number of links formed with neighboring comm nodes.

(7) Select the Maximum Number of Nodes the selected node will track. Increasing the number of nodes allows the node to track more possible links, but does not increase the number of links formed.

(8) Select the minimum number of timeslots allocated to each link in the Minimum Timeslot per Neighbor field.

UNCLASSIFIED

(9) Select the Center Frequency (MHz) for the enhanced high power HNR C-band HRFU channels—tunable from 4.497 MHz to 5.097 MHz.

(10) Select the Advanced Settings drop-down arrow and update node parameters, if necessary.

(11) Prune links to neighboring comm nodes.

(a) Select a priority number for the link(s). Higher values (0–4) receive higher priority.

CAUTION: The value of -2 will permanently delete the link.

1) A value of -1: The link is not tracked as a possible link.

2) A value of -2: The link cannot be formed in the future.

(b) Click <Apply>.

(c) Click <Yes> to apply changes.

g. Prune an IFCN Relay through CWMI – Prune an IFCN Relay using the same procedure to prune an EOC.

6. Perform Manual Pruning

The following procedure is an alternate way to prune the network.

a. Verify pre-requisites for manual pruning.

(1) Laptop with Windows 10.

(2) Straight through Ethernet cable.

b. Setup for manual pruning.

(1) Connect the Ethernet cable from the BPU J2 to the laptop.

(2) Set the laptop IPV4 network settings:

(a) IP Address: 192.168.5.253

(b) Gateway: 255.255.255.0

c. Review the command line tool.

(1) Use when no CDS is available.

(2) The script is made to run on the black Network Manager laptop.

(3) The script includes a “run.sh” script that prints 9 input options for the user:

● 1) Clear Preferred Neighbor Table For a HNR

● 2) Set A Preferred Neighbor Table Entry For a HNR

● 3) Set MAX Neighbors For a HNR

● 4) Send Save To Flash Command to HNR

● 5) Reboot a HNR

● 6) Print Preferred Neighbor Table

● 7) Print Neighbor Table

UNCLASSIFIED

● 8) Print UMAC for a HNR

● 9) Print Max Neighbors for a HNR

● 10 or q) Quit

d. Use the command line tool.

(1) Run the command line in a terminal to access the script screen, type: ./run.sh

Figure 2-4. Main Script Screen for Manual Pruning

(2) At the Enter Command prompt, type: 1

(3) At the Enter Command prompt, type: 2

Figure 2-5. Manual Pruning, Option 2

(a) Enter the target HNR IP address.

(b) Enter the UMAC of the HNR to add.

(c) Enter the priority of the neighbor.

(d) Enter the Min Timeslots for the neighbor.

1) Setting this value to -1 will remove the corresponding neighbor preference table entry.

2) Setting this value to -2 will prevent the local node from forming a link to the neighbor.

UNCLASSIFIED

3) Values from 0 (no priority) to 4 (highest priority) indicate a relative preference allowing other UMAC nodes to progress past the link status of pending neighbors and exchange data.

(4) At the Enter Command prompt, type: 3

Figure 2-6. Manual Pruning, Option 3

(a) Enter the target HNR IP address.

(b) Enter MAX Neighbor Value

(5) At the Enter Command prompt, type: 4

Figure 2-7. Manual Pruning, Option 4

UNCLASSIFIED

(6) At the Enter Command prompt, type: 5

Figure 2-8. Manual Pruning, Option 5

(7) At the Enter Command prompt, type: 6

Figure 2-9. Manual Pruning, Option 6

(8) At the Enter Command prompt, type: 7

Figure 2-10. Manual Pruning, Option 7

UNCLASSIFIED

(9) At the Enter Command prompt, type: 8

Figure 2-11. Manual Pruning, Option 8

(10) At the Enter Command prompt, type: 9

Figure 2-12. Manual Pruning, Option 9

(11) Close the command line took, at the Enter Command prompt, type: 10.

Advanced Network Manager Practical Exercises 06 May 2020

UNCLASSIFIED

ADVANCED NETWORK MANAGER PRACTICAL EXERCISES

WARNING: Adhere to all safety Warnings and Cautions during the exercises.

PRACTICAL EXERCISE (PE) OVERVIEW

1. Directions to Students

a. Perform the following mission: Perform network management operations using the

IBCS CWMI.

b. Perform assigned tasks and procedures given by the instructor.

c. Use TMs, Student Guide materials, and notes when performing exercises.

d. Safety Precautions:

(1) Obey all applicable cautions and warnings.

(2) Use the proper tools for the task.

e. Student References

(1) The IBCS Advanced Network Manager Student Guide

(2) The Software User Manual (SUM)

2. Practical Exercise Execution

a. By performing the exercises, students learn the following tasks:

(1) Create an EOC and Relay Neighbor Table

(2) Network Management

(3) Network Pruning

b. Evaluations are conducted on individual and team participation when performing exercises.

UNCLASSIFIED

PE 01: CREATE A NEIGHBOR TABLE

Evaluation

The PE validates the ability of the student to create an EOC and Neighbor table, used to prune a communications network.

The instructor performs a progress check on each student to ensure that proper actions are taken during the practical exercise (PE). At the end of the exercise, the instructor marks the PE “GO” or “NO-GO.” A NO-GO assessment results in retraining and re-evaluation.

Directions

● Follow the instructions given in the Student Guide.

● Perform proper procedures indicated by the instructor.

● Follow procedures exactly, unless the instructor states otherwise.

a. Given the MESH network diagram in Figure 3-1, and the blank table in Figure 3-2, develop an EOC and Relay Neighbor table to prune the given MESH network.

Instructor Check: GO_____ NO-GO_____

Figure 3-1. PE 01 Mesh Network Diagram

Figure 3-2. PE 01 EOC and Relay Neighbor Table

UNCLASSIFIED

PE 02: PERFORM NEIGHBOR MANAGEMENT AND NETWORK PRUNING

Evaluation

The PE validates the ability of the student to perform Neighbor Management and Network Pruning tasks.

The instructor performs a progress check on each student to ensure that proper actions are taken during the practical exercise (PE). At the end of the exercise, the instructor marks the PE “GO” or “NO-GO.” A NO-GO assessment results in retraining and re-evaluation.

Directions

● Follow the instructions given in the Student Guide.

● Perform proper procedures indicated by the instructor.

● Follow procedures exactly, unless the instructor states otherwise.

a. With guidance from the instructor perform Network Pruning.

b. Select Roles as S6.

c. Click the Network manager.

d. Click the Network Control.

e. Select the Appropriate EOC.

(1) Using the battalion layout, modify the neighbor list so the two closest neighbors are the highest priority.

(2) Set all other neighbors to the lowest priority. Do not use -2.

Instructor Check: GO_____ NO-GO_____

Appendix A: Acronyms and Abbreviations 06 May 2020

UNCLASSIFIED

A-1

APPENDIX A: ACRONYMS AND ABBREVIATIONS

The following acronyms and abbreviations are used in this document.

Acronym Definition

ACO Airspace Control Order

ADSI Air Defense Systems Integrator

AIAMD Army Integrated Air and Missile Defense

ALT Alternate

AMD Air and Missile Defense

AO Area of Operations

AOI Area of Interest

ASoS AIAMD System of Systems

ATO Air Tasking Order

BPU Branch Processing Unit

C2 Command and Control

CAGE Commercial and Government Entities

CBIT Continuous Built-In Test

CDS Cross Domain Solution

CID Combat Identification

CSCI Computer Software Configuration Items

CWMI Common Warfighter Machine Interface

DCR Document Change Request

DDM Data Distribution Manager

DoD Department of Defense

EOC Engagement Operations Center

FCN Fire Control Network

GUI Graphical User Interface

GW Gateway

HNR Highband Network Radio

HRFU Highband Networking Waveform RF Unit

IADS Interactive Authoring and Display System

IAMD Integrated Air and Missile Defense

IBCS IAMD Battle Command System

ICE IBCS Collaborative Environment

IDD Integrated Defense Design

IETM Interactive Electronic Technical Manual

IFC Integrated Fire Control

IFCN Integrated Fire Control Network

UNCLASSIFIED

A-2

Acronym Definition

IFF Identification Friend or Foe

IGRM Initialization and GPS Receiver Module

IP Internet Protocol km kilometer

LAN Local Area Network

LOS Line of Sight

Mbps Megabits per second

MEI Major End Item

MHz Megahertz

MIL-STD Military Standard ms milliseconds

N/A Not Applicable

NIPR Non-Classified Internet Protocol

NSA National Security Agency

OS Operating System

PDF Portable Document Format

PE Practical Exercise

QoS Quality of Service

RF Radio Frequency, Roadside Front

S6 Staff 6

SAP Saturation Alleviation Plan, System Adjustable Parameter sec seconds

SIPR Secret Internet Protocol Router

SNMP Simple Network Management Protocol

SoS System of Systems

SUM Software User Manual

SWGK Surface Wire Grounding Kit

TOC Table of Contents

TTP Tactics, Techniques, and Procedures

U.S. United States

UI User Interface

UPS Uninterruptible Power Supply

UNCLASSIFIED

A-3

Electronic Signatures: