DRSN OM Guide 28May08.doc

Defense REd Switch NetWork

(DRSN)

Operations and Maintenance (O&M) Guide

May 2008

TABLE OF CONTENTS

SECTION

PAGE

1-1Section 1.

Introduction

1-11.1 Purpose

1-11.2 Goals and objectives

1-11.3 Organization

1-21.4 development

2-1Section 2.

DRSN DOCUMENTATION

2-12.1

OPERATIONS AND MAINTENANCE SITE REQUIRED AND RECOMMENDED DOCUMENTS

2-32.2 DISA Publication Ordering

3PART I. DRSN OVERVIEW

3-1Section 3.

DRSN Subsystems

3-13.1 General

3-13.1.1 Switching Subsystem

3-53.1.2 Transmission Subsystem

3-53.1.3 Timing and Synchronization Subsystem

3-53.1.4 Network Management Subsystem

4-1Section 4.

DRSN Network Management

4-14.1 General

4-14.1.1 Network Management Subsystem

4-14.1.2 Fault Management

4-24.1.3 Performance Management

4-24.1.4 Configuration Management

4-24.1.5 Accounting Management

4-34.1.6 Security Management

4-44.2 Network Management Responsibilities

4-44.2.1 DISA Line of Business Office

4-44.2.2 National Military Command Center Communications Watch Division

4-44.2.3 Joint Task Force – Global Network Operations

4-44.2.4 DISA Theater Network Control Centers and DRSN Operations Center

4-54.2.5 Operations and Maintenance Commands

4-54.3 Network Management Point of Contact Numbers

PART II. SITE ADMINISTRATION PROCEDURES

5-1Section 5.

DRSN Site Network Management Data Collection

5-15.1

5-15.2 DRSN Data Collection and Reporting Procedures

5-15.2.1 Fault Management Data Log

5-25.2.2 Configuration Management and Performance Management Data Collection

5-75.2.3 Security Data Management Requirements

5-85.2.4 Accounting Data Management Requirements

5-85.2.5 RED Switch Level Device Reporting Requirement

6-1Section 6.

DRSN Site Security Management

6-16.1

6-16.2 SECTION Contents

6-16.3 Definitions

6-16.3.1 Security Management

6-16.3.2 Threat

6-26.3.3 Certification

6-26.3.4 Accreditation

6-26.4 SECURITY MANAGEMENT Responsibilities AND PROCEDURES

7-1Section 7.

Ordering Telecommunications Service

7-17.1

7-17.2

7-17.2.1 Telecommunications Service Request

7-17.2.2 Telecommunications Certification Office

7-17.2.3 Telecommunications Service Order

7-17.2.4 Request for Service (RFS)

7-17.3 Service Ordering Procedures

8-1Section 8.

DRSN Site Record keeping Configuration Management Inventory AND Maintenance

8-18.1

8-18.2 SECTION Content

8-18.3 DRSN OPERATIONS AND MAINTENANCE Record keeping Procedures

9-1Section 9.

DRSN WEB SITE INSTRUCTIONS

10PART III. SITE O&M PROCEDURES

10-1Section 10.

DRSN Site Fault Management

10-110.1

10-110.2

10-110.3

10-110.3.1 Fault Identification

10-110.3.2 Fault Troubleshooting

10-210.3.3 Status Reporting

10-210.3.4 Fault Correction

10-210.4 DRSN Fault Management Procedures

11-1Section 11.

DRSN Site Preventive Maintenance

11-111.1

11-111.2 DRSN OPERATIONS AND MAINTENANCE PREVENTIVE MAINTENANCE PROCEDURES FOR THE DSS SWITCH

11-111.2.1 Review System Messages

11-311.2.2 Check Enclosure Cooling Fans

11-311.2.3 Clean Dust Filter

11-311.2.4 Inspect/Replace Door EMI Finger Stock

11-411.2.5 Clean PWAs

11-511.2.6 Check/Adjust Power Supply Output Voltages

11-1011.2.7 Site Database Back Up and Restore

11-1211.3

DRSN OPERATIONS AND MAINTENANCE PREVENTATIVE

11-1311.3.1 Periods of Performance

11-1711.3.2 Other Tape Back-ups

11-1811.3.3 Crypto Change-out and Rekey Procedures

11-2011.3.4 Key Management Procedures (KIV-7/HS)

12-1Section 12.

Logistics and Repair Parts Support

12-112.1

12-112.2

12-112.3 Promina MULTIPLXER Logistics

12-112.4 DRSN Red switch Logistics

13-1Section 13.

DRSN Management database system

Figures

3-2Figure 3‑1 DRSN CONUS Topology

3-3Figure 3‑2 DRSN OCONUS Topology

3-4Figure 3‑3 DRSN Notional System Overview

4-6Figure 4‑1 DRSN Network Management Communication, Guidance, and Data Flow

8-4Figure 8‑1 Sample Site Equipment Diagram

8-5Figure 8‑2 Sample Circuit Diagram

8-5Figure 8‑3 Sample T&S Diagram

Tables

2-1Table 2‑1 O&M Site Required and Recommended Documents

4-5Table 4‑1 Network Management POC Numbers

5-1Table 5‑1 Fault Management Data Log

5-3Table 5‑2 Configuration Management CDH Data Collection

5-4Table 5‑3 CDH Data Collection Procedures

5-5Table 5‑4 Performance Data Collection (UIC)

5-6Table 5‑5 UIC Data Collection Procedures

5-7Table 5‑6 Security Data Management Requirements

5-8Table 5‑7 RED Switch Level Device Reporting Requirement

5-9Table 5‑8 RED Switch Level Reportable Device Format

6-3Table 6‑1 Site Security Management Responsibilities

6-3Table 6‑2 Certification and Accreditation

6-4Table 6‑3 Access Control Measures

6-5Table 6‑4 Communication Security Measures (SAL Classmarks)

6-6Table 6‑5 Information Security Measures Classification

6-6Table 6‑6 Physical Security Measures

7-2Table 7‑1 Ordering New Service

8-2Table 8‑1 Record Keeping

10-3Table 10‑1 Unscheduled Service Interruptions and Outages

10-6Table 10‑2 Responding to Senior User Call Failures

10-6Table 10‑3 Switching Subsystem Alarm Events

10-7Table 10‑4 Transmission Subsystem Alarm Events

10-7Table 10‑5 Timing and Synchronization Subsystem Alarm Events

10-8Table 10‑6 Authorized Outages

10-9Table 10‑7 Authorized outage Request Format

10-10Table 10‑8 Site Level Reporting Requirements

11-2Table 11‑1 Example System Messages

11-3Table 11‑2 Check Cooling Fans

11-3Table 11‑3 Clean Dust Filters

11-4Table 11‑4 Inspect/Replace Door EMI Finger Stock

11-5Table 11‑5 Clean PWAs

11-6Table 11‑6 Power Distribution Voltage Adjustment

11-10Table 11‑7 Backup Switch Database

11-11Table 11‑8 Restore Backed-Up Switch Database

11-11Table 11‑9 SPARC station Reboot

11-12Table 11‑10 SPARC station Shutdown

11-12Table 11‑11 SPARC station Start From Power Off

11-14Table 11‑12 Daily Maintenance Inspections

11-15Table 11‑13 Weekly Maintenance Inspections

11-16Table 11‑14 Monthly Maintenance Inspections for SDS/RSU Type Switches Only

11-17Table 11‑15 Quarterly Maintenance Inspection

11-17Table 11‑16 Annual Maintenance Inspection

11-18Table 11‑17 Crypto Change-out and Rekey Procedures

11-19Table 11‑18 Updating the KG-94/94A TEK Thru Change Key Operations

11-21Table 11‑19 Procedures to Load KEYMAT into the KIV-7/HS

11-21Table 11‑20 Procedures to Update Keys in the KIV-7/HS

11-22Table 11‑21 Procedures to TX a Key Stored in the KIV-7/HS to Distant-End

11-22Table 11‑22 Procedures to Zeroize Keys in the KIV-7/HS

11-22Table 11‑23 Procedures to Select a Key for Operation in the KIV-7/HS

11-23Table 11‑24 Procedures to Select Crypto Configuration-settings/strapping KIV-19A

12-2Table 12‑1 Promina Logistics

Section 1. Introduction

1.1 Purpose

The purpose of the Defense RED Switched Network (DRSN) Operations and Maintenance (O&M) Guide is to provide a comprehensive and concise overview of policies and procedures related to the operations, maintenance, and network management (NM) of the DRSN. This guide is intended to facilitate operations, maintenance, and management of the network and to foster network quality and cohesiveness through network wide standardized practices. The guide is not intended to replace referenced directives, but rather to provide a quick reference source for O&M personnel involved in the day-to-day DRSN O&M activities. To obtain a software copy of this guide, log on to the DRSN Website (SIPRNET). To access the Website, follow the instructions as described in Section 9 of this guide.

1.2 Goals and objectives

The goal of this guide is to provide the O&M personnel with a user-friendly, reference document for the day-to-day O&M procedures.

The main objective of this guide is to provide the DRSN site technician with a living document, a useful and practical tool for continually improving the quality of the DRSN to effectively provide uninterrupted service to all users of the network.

1.3 Organization

This guide contains three (3) parts: DRSN Overview, Site Administration Procedures, and Site O&M Procedures.

a.

Part I: DRSN Overview. Part I, (begins with Section 3) provides a brief overview of the DRSN and DRSN subsystems that includes: switching, transmission, timing and synchronization (T&S), and NM.

b.

Part II: Site Administration Procedures. Part II (begins with Section 5) addresses the DRSN administrative processes of site NM (data collection), security management, ordering telecommunications service, and record keeping (site configuration, maintenance, and inventory).

c.

Part III: Site O&M Procedures. Part III (begins with Section 10) covers the day-to-day DRSN O&M procedures for fault management (FM), status reporting, preventive maintenance, and logistics (repair parts) support.

1.4 development

The Defense RED Switched Network (DRSN) Operations and Maintenance (O&M) Guide should be viewed as a living document that will continually change and improve. The users of the guide are invited to provide ideas and suggestions to enhance the guide, as it is field tested over time. DRSN O&M personnel may send comments and input for the guide to the following address:

DISA, CODE: GS24

ATTN: Jim Gundy (Pri) – Michael Lewis (Alt)

P. O. Box 4502

Arlington, VA 22204-4502

E-Mail Address: Jim.Gundy@disa.mil;

Michael.Lewis@disa.mil

DSN:

381-0351, 381-0352

Commercial:

(703) 882-0351, (703) 882-0352

FAX:

(703) 882-2880

Section 2. DRSN DOCUMENTATION

2.1 OPERATIONS AND MAINTENANCE SITE REQUIRED AND RECOMMENDED DOCUMENTS

Table 2-1 is a list of required and recommended documents for all DRSN O&M sites. Documents marked with one asterisk “*” are recommended. Two asterisks “**” indicate required documents.

Table 2‑1 O&M Site Required and Recommended Documents

DISAC 300-115-7**

Defense RED Switch Network (DRSN) Security Classification Guide, (last revision) 12 July 2006

(last revision) 26 July 2006

(last revision) 25 May 2006

8 May 2002

1 August 2004

Note 1: Site is only required to have TM for equipment actually installed at that location.

Note 2: Version may vary depending on Software Release installed.

2.2 DISA Publication Ordering

To order Defense Information Systems Agency (DISA) publications that are classified or not available on the DISA Web site, use the following steps:

1. Locate required publication in DISA Notice 210-0-1, Index: DISA Circulars and Notices

2. Complete DISA Form 117 (E)

Mail request order to:

DISA

Attn: SPI21

P.O. Box 4502

Arlington, VA 22204-4502

DSN: 761-2099

Coml: 703-681-2099

4.

Fax request order to: DISA Publications Management Office

Coml: (703) 681-2878 DSN: 761

PART I. DRSN OVERVIEW

DRSN SUBSYSTEMS

· General

· Switching Subsystem

· Transmission Subsystem

· Timing and Synchronization Subsystem

· Network Management Subsystem

DRSN NETWORK MANAGEMENT

· General

· Network Management Subsystem

· Fault Management

· Performance Management

· Configuration Management

· Accounting management

· Security Management

· Network Management Responsibilities

· Network Management Point of Contact Intentionally Left Blank Section 3. DRSN Subsystems

3.1 General

The DRSN, an element of the Defense Information Systems Network (DISN), is a network of secure command and control switches that provide high-quality secure voice and conferencing capabilities to the senior decision makers and staff of the Military Departments (MILDEPs), the Combatant Commanders, Major Commands (MAJCOMs), other Government departments and agencies, and Allies.

The mission of the DRSN is to provide the ability to transfer voice and data between the MILDEP, the National Military Command Center (NMCC), combatant commands, the Services, subordinate organizations (military and civilian), and Allies (North Atlantic Treaty Organization (NATO), Canada, etc.), both locally and worldwide. The DRSN also provides secure voice conferencing and gateway access to secure strategic, tactical, airborne, and sea borne equipment and platforms.

The DRSN consists of four major subsystems: one (1) Switching Subsystem, two (2) Transmission Subsystem, three (3) Timing and Synchronization (T&S) Subsystem, and four (4) Network Management Subsystem (NMS). The subsystem descriptions are intended to provide the reader with a general understanding of the DRSN. Figures 3-1 and 3-2 illustrate the current DRSN topology. See the DRSN Interface Criteria for more detailed descriptions of each subsystem and its respective component equipment.

3.1.1 Switching Subsystem

The DRSN Switching Subsystem provides the DRSN users secure and nonsecure call origination and call termination capabilities, secure conferencing, and direct interoperability with other secure networks. The primary switching platforms of the DRSN Switching Subsystem are the Raytheon family of Secure Digital Switches (SDS) and the Digital Small Switch (DSS). In many DRSN switch locations, both a RED switch and a BLACK switch are installed to provide integrated RED/BLACK service (i.e., users are provided a single telephone instrument with which they can access both secure networks and nonsecure networks). A notional overview of a DRSN node is shown in Figure 3-3.

Figure 3‑1 DRSN CONUS Topology

FIGURE 3‑2

DRSN OCONUS Topology

Figure 3‑3 DRSN Notional System Overview

3.1.2 Transmission Subsystem

The DRSN Transmission Subsystem provides connectivity between DRSN RED switches, connectivity between a DRSN RED switch and users located remotely from the switch, and interconnection with other secure networks and systems. The Transmission Subsystem includes Network Equipment Technologies, Inc. (N.E.T.) Promina multiplexing equipment, encryption devices, channel service units (CSUs), and tail segment cabling. The Transmission Subsystem connects the DRSN RED switches to Government-owned and leased backbone transmission systems (e.g., full T1 or E1 transmission systems, fractional T1 (FT1) transmission links, and 56 or 64 kilobits per second (kb/s) transmission links). DRSN BLACK switch connectivity is provided to the Defense Switched Network (DSN), Public Switched Network (PSN), or Federal Telecommunications System, as appropriate, and is not considered a part of the DRSN Transmission Subsystem. Appendix C Table lists Promina RED and Promina BLACK nodes that provide DRSN connectivity.

3.1.3 Timing and Synchronization Subsystem

The T&S Subsystem is comprised of reference clocks, clock distribution systems, and RED/BLACK isolation filters and buffers. The T&S Subsystem provides a primary, secondary, and tertiary method of obtaining a timing source for site contingency and the network.

3.1.4 Network Management Subsystem

The NMS provides DISA with the capabilities to provide day-to-day direction and operational oversight of the DRSN. It includes the facilities, equipment, organizational structure, and people to monitor and interface with the DRSN site O&M activity to affect problem resolution.

Section 4. DRSN Network Management

4.1 General

DISA, as the Joint Staff designated System Manager (SM) for the DRSN, is responsible for providing operational direction and management of worldwide DRSN assets.

4.1.1 Network Management Subsystem

Network management requirements for the DRSN are specified in the Joint Staff Memorandum J-6A 016650-92, Secure Voice Requirements Concept, and CJCSI 6215.01B, Policy for the DOD Voice Networks. NM ensures user-to-user service is maintained under changing traffic conditions, changing user requirements, natural and manufactured stresses and disturbances, and equipment failures or degradations. NM consists of the following five (5) functions:

· Fault Management (FM)

· Performance Management (PM)

· Configuration Management (CM)

· Security Management (SM)

· Accounting Management (AM)

O&M personnel play a major part in enhancing the day-to-day and long-term network performance through the collection of network performance and configuration data and assisting in the detection, diagnosis, and correction of performance problems at the site level.

4.1.2 Fault Management

Fault management is defined as the detection, isolation, and correction of network problems. It encompasses activities such as performing system diagnostics, tracing faults through a network, managing error logs, identifying causative events, and correcting faults.

Fault management provides centralized near-real-time management of the network during times of abnormal traffic conditions and/or equipment failures to ensure the network can be optimized to support critical command and control traffic under stress conditions.

The Theater NetOps Centers (TNCs), Service/Agency Theater Network Operations and Security Centers (STNOSC/ATNOSCs) and O&M sites support FM by continuously monitoring DRSN alarm ports, processing received data, maintaining event logs, and notifying the site operator when significant alarms occur in DRSN subsystems.

4.1.3 Performance Management

Performance management is defined as the collection and analysis of statistical data to measure the performance of a network. Performance management permits the use of models to determine whether a network element is:

· Meeting required throughput rates

· Providing adequate response times

· Approaching overload conditions

· Operating efficiently

The TNC’s and O&M sites support PM by gathering performance data and developing statistics to diagnose day-to-day network problems or abnormalities. The PM data is also used to support long-term network sizing and topology design studies.

4.1.4 Configuration Management

Configuration Management procedures are currently in a state of migration to Integration Configuration and Administrative Tracking System (ICATS). The conversion from CM to ICATS has been placed on the ICATS implementation schedule. The procedures for the conversion are to be determined later.

Network CM ensures changes to the DRSN baseline are methodically approved and controlled. CM begins with the implementation of the approved network functional baseline. CM reviews, approves, or disapproves change proposals, deviations, and waivers to the baseline. CM also oversees implementation of the baseline and approved changes and audits the network functionality to ensure compliance with the baseline and approved changes. DISA/GS24 is responsible for CM of the DRSN.

The TNCs and O&M sites support CM through the establishment and maintenance of a network CM database. Centralized management and configuration control of network features, such as network routing, numbering, precedence levels, security access levels (SALs), calling area authorizations, and alarm classifications, ensure standardization that simplifies user operational procedures and enhances network performance.

4.1.5 Accounting Management

Accounting Management (AM) defines how network usage, charges, and costs are identified.

The Defense Working Capital Fund (DWCF) Telecommunications Services/Enterprise Acquisition Services (TS/EAS) serves as a revolving fund supporting telecommunications services for the DoD and other authorized users. Funds paid from the DWCF TS/EAS for DRSN network costs, such as common inter-switch trunks and the other costs of operating the network, must be reimbursed by charging rates distributed to all customers. Rates developed by DISA are computed so revenue collected from customers will equal the costs of operating the network. The ultimate objective is that DWCF TS/EAS will break even, i.e. the DWCF will not make a profit or incur a loss. The DRSN billing is accomplished by allocating costs to the Military Departments based upon the number of Red switches that they own and operate. Some Military Departments internally pass those costs to the owning command; others pay the DWCF bill centrally. DISA does not include the Black Raytheon switches in the billing calculation, but does include Red switches that are “behind” another Red Switch.

DISA and OSD are implementing an alternate funding and billing process for DISN services that will be put in place in early FY2006.

The TNCs and O&M sites support AM by providing network user data for billing purposes through the CM database.

4.1.6 Security Management

Security management is concerned with protecting managed objects. It provides cryptographic key management, authentication rules, access control routines, authorization facility maintenance, and security logs.

4.2 Network Management Responsibilities

The following is a description of the DRSN NM hierarchy and overall responsibilities.

4.2.1 DISA Line of Business Office

The DRSN Line of Business Office (LOB) is responsible for non-real-time operational management of the DRSN, including development of operational policy and procedures, operational CM, long-term performance analysis, and circuit provisioning. The Line of Business Office also operates DRSN Website (SIPRNET) to provide on-line access to DRSN information, such as the DRSN Telephone Directory, points of contact (POCs), Engineering Change Proposal (ECP) status, and other information related to DRSN O&M.

The Line of Business Office also receives a feed from the Scott AFB, IL, TNC Advanced RED Defense Integrated Management Support System (ARDIMSS) database. This information covers all DRSN switch fault alarms for a 24-hour period. It is used to look for trends coming from the DRSN and specific outages on VIP telephones. The Line of Business Office works closely with the TNCs and, occasionally, with switch site personnel to identify problems and trends and correct deficiencies attempting to prevent major outages or disruptions to VIP customers.

4.2.2 National Military Command Center Communications Watch Division

The NMCC Communications Watch Division (CWD) maintains a worldwide view of the DRSN and reports to the Secretary of Defense any conditions that could impair the ability to support worldwide contingency operations. The CWD notifies the JTF-GNO and the Scott GNSC of failures, NMCC VIP call failures, outages, degradations, or any problems identified by the NMCC with the potential for affecting service to a senior DRSN customer of Joint Staff interest.

4.2.3 Joint Task Force – Global Network Operations

The Joint Task Force – Global Network Operations (JTF-GNO) maintains a worldwide view of the entire DRSN as well as all other DISA managed (i.e., DISN) networks. The Global NetOps Center (GNC) assesses and coordinates resolution of inter-theater network problems and advises key personnel of network status.

4.2.4 DISA Theater Network Control Centers and DRSN Operations Center

Scott AFB, GNSC, and the TNCs in Vaihingen (Patch Barracks), Germany, Europe (EUR) and the Wheeler Army Air Field (AAF), HI, Pacific (PAC) provide day-to-day oversight and management of DRSN assets in their areas of responsibility. The Scott, EUR and PAC TNC maintain continuous surveillance of DRSN assets in their assigned region to detect abnormalities, to implement or direct near-real-time corrective actions in response to adverse network conditions, and to coordinate repair and restoration actions with the military department (MILDEP) O&M Commands. They also coordinate authorized outages with the O&Ms and report network conditions to the JTF-GND. In addition, the GNSC coordinates the implementation of approved network configuration changes worldwide such as changes in network routing or numbering in the switches and changes in the Promina configuration.

4.2.5 Operations and Maintenance Commands

The O&M Commands play a key role in the management of the DRSN. The O&Ms are directly responsible for the day-to-day operation of network switches, transmission facilities, and related equipment at individual DRSN switching sites. The O&Ms administer DRSN hardware and software, troubleshoot and repair equipment failures, reconfigure network assets in response to valid tasking, maintain configuration control over assets, and report local conditions that could affect network operations. The O&Ms also engineers, implements, and controls features and functions at the end-user level (e.g., assignment and control of user instruments, features, and telephone numbers) and special site-specific sub networks that may share DRSN facilities such as SCAMPI, interfaces with tactical networks, and others. In addition to the functional requirements at the end-user level, it is suggested that O&Ms establish a proactive relationship with their customers, who fosters a smooth and effective troubleshooting process when responding to end-user problem calls. The O&Ms are also responsible for the overall security of their DRSN sites.

Figure 4-1 illustrates the network management data flow between the three levels of the DRSN hierarchy. Each link in the data flow is critical to the overall coordination, troubleshooting, and O&M activities needed to provide the end-user with high-quality service.

4.3 Network Management Point of Contact Numbers

Table 4-1 provides POC numbers for the GNSC and TNCs.

Table 4‑1 Network Management POC Numbers

JTF-GNO-DOD DISA HQ

Arlington, VA.

(312) 607-4009

(312) 779-9010

DRSN Secure:

80-631-6486 or

80-631-6487

(618) 229-9000

(618) 229-9010

DSN:

(312) 779-9044

TNC-EUR

(DISA-EUR)

Vaihingen (Patch Barracks), GE.

(314) 430-7373

(314) 430-5955

(314) 430-6372

(314) 430-4071

TNC-PAC

(DISA-PAC)

Wheeler Army Air Field, HI.

(315) 456-2777

(315) 456-2159

(808) 656-2777

(808) 656-2159

DSN:

(315) 456-1277/9311

Secure:

(315) 456-4500

Figure 4‑1 DRSN Network Management Communication, Guidance, and Data Flow

PART II. SITE ADMINISTRATION PROCEDURES

· Site Network Management Data Collection

· Site Security Management

· Ordering Telecommunications Service

· Site Record Keeping

· Site Configuration

· Maintenance

· Inventory

· DRSN Website Instructions

Intentionally Left Blank

Section 5. DRSN Site Network Management Data Collection

5.1 Purpose

This section identifies procedures for collecting and reporting DRSN data to support NM functions to include Performance Management, Configuration Management, Fault Management, Security Management, and Account Management.

5.2 DRSN Data Collection and Reporting Procedures

The following series of tables provide suggested procedures for the O&Ms to use in supporting the DRSN NM data collection.

5.2.1 Fault Management Data Log

Each DRSN site must maintain a DRSN FM data log (see Table 5-1) in accordance with (IAW) the DISA Circular (DISAC 310-70-1), DII Technical Control. The log can be maintained in a local database to support local O&M, Scott GNSC troubleshooting, and FM efforts.

Table 5‑1 Fault Management Data Log

Affected caller’s SDN

Time problem occurred

Specific problem location

Nature of problem

Fix actions taken

NOTE: The document link below contains O&M information provided for replaceable items, preventive maintenance schedules and procedures, troubleshooting procedures, and repair information and procedures.

5.2.2 Configuration Management and Performance Management Data Collection

Tables 5-2 through 5-5 provide step-by-step procedures for local data collection supporting network PM and CM. This data supports DISA’s long‑term network PM and CM processes of engineering, enhancing, and upgrading network topology. On a bimonthly basis, each site is required to send DISA Operational Management Section (GS24) their Call Detail History (CDH) and site User Identification Code (UIC) data. Note: The CDH procedures in Tables 5-2 and 5-3 have been updated with the Alpha processor. In addition, Tables 5-4 and 5-5 have been updated with Alpha processor procedures for collecting site UIC data.

To work within the DRSN security policies, DISA requires that each site collect the CDH data 30 days in advance of the UIC data. Each site will be responsible to hold the CDH data for 30 days. After 30 days, IAW DISAC 300-115-7, the CDH data and media will be declassified to For Official Use Only (FOUO) and mailed simultaneously (same tape or separate tapes) with the site UIC data. However, if an active UIC issue still exists on the same tape of the CDH and has not been resolved, the tape should be considered SECRET due to the unresolved UIC issue. You may send CDH tapes separate marked (FOUO) or if packaged in the same container as the UIC tapes, the package must be classified SECRET. The entire package (both the CDH data and the UIC data) must be marked SECRET and only mailed via U.S. REGISTERED MAIL and marked POSTMASTER DO NOT FORWARD to DISA/GS24 per the schedules in the following tables.

5.2.2.1 Configuration Management Call Detail History Data Collection

Each DRSN site will provide switch CDH data IAW Table 5-2. The CDH data supports DISA’s network CM process of controlling, auditing, and status accounting for all changes to the DRSN configuration baseline. Table 5-3 shows the procedures for the CDH data collection.

5.2.2.2 Performance Data Collection (User Identification Code)

Each DRSN site will provide switch UIC data IAW Table 5-4. This data supports DISA’s network PM process. Table 5-5 shows the procedures for UIC data collection.

Table 5‑2 Configuration Management CDH Data Collection

Switching CDH data collection will take place bimonthly to coincide with the site UIC data collection.

CDH DATA DATES

1-14 January

1-14 March

1-14 May

1-14 July

1-14 September

1-14 November

TAPE PREPARATION DATES

14 January

14 March

14 May

14 July

14 September

14 November

CDH DAT MAILING DATES (To be mailed with site UIC data)

15 February

15 April

15 June

15 August

15 October

15 December See CDH Data Collection Procedures, Table 5‑3.

The CDH data must be collected 30 days in advance of the site UIC data and held locally for 30 days as SECRET. After 30 days the CDH data will be downgraded to FOUO and mailed simultaneously with the site UIC data. Because the site UIC data is SECRET, package with both sets of data must be classified as SECRET when mailed to DISA/GS24.

Table 5‑3 CDH Data Collection Procedures

Table 5‑4 Performance Data Collection (UIC)

Prepare the package cartridge (site UIC data) on the following dates:

15 February

15 April

15 June

15 August

15 October

15 December

Mailing Address:

DISA

ATTN: GS24

P.O. BOX 4502

ARLINGTON, VA 22204-4502

Tapes should be marked, packaged and mailed per security instructions.

The packaged cartridges will be promptly returned to each site immediately after processing.

See UIC Data Collection Procedures, Table 5‑5.

The site UIC data is not required to be held for 30 days. Site UIC data should be mailed at the same time as the CDH data (after the CDH data has been held locally for 30 days). The packaged cartridge with both sets of data must be classified SECRET and mailed to DISA/GS24.

Table 5‑5 UIC Data Collection Procedures

UIC DATA COLLECTION PROCEDURES

This table contains the procedure to back up all files located in the site UIC of the processor. All entries are made at the associated console terminal (CRT) or X-Windows terminal. This procedure can also be used to perform weekly back-ups of the site UIC. Do not use this procedure to back up the entire hard disk. Total time for site UIC back up is approximately 2 to 3 minutes.

CAUTION

Database back-up procedures should be performed on the off-line processor ONLY. STOPSDS should be performed before doing back-up tapes, especially if deleting a directory.

NOTE

Step 2 in the following procedure may be omitted if the terminal is already logged on. If this is the case, ensure the terminal is at the root directory [XXXXXXXX] before proceeding.

1.

Insert the DAT cartridge into the off-line Alpha processor. Wait until the green light on the tape drive stops flashing. A red light indicator on the front of the tape drive, with the tab inserted, indicates write protection is enabled. If indicator is lit, remove DAT and disable write protection. Reinsert DAT.

2.

At the processor interface terminal (or CRT) or X-Windows terminal for the off-line processor, press the space bar to bring up the display. At the indicated prompts, enter the following commands:

(a) Username: XXXXXXXX [CR] where XXXXXXXX is site-specific

(b) Password: YYYYYYYY [CR] where YYYYYYYY is site-specific

3.

If DAT cartridge is not initialized, initialize by entering:

INIT MKA500: save_set [CR] where save_set is a maximum of six characters and is user defined. The save_set is used to identify a specific version to the tape (for example: save_set=JAN016).

4.

At the prompt, type ME [CR] or SITE [CR] to get to the site UIC.

5.

To begin back-up, at the prompt enter:

BACKUP/LOG/VER DKA300:[ALPHASDS.SITE_UIC]*.* MKA500:save_set/SAVE[CR]

(a) Where “SITE_UIC” is the name of the site UIC of the SDS-1.

(b) “save_set” is the name used to identify the specific version of the tape provided in step c above.

Defined switches are:

/LOG Displays information about each file copied on the terminal.

/VER Verifies each file is backed up correctly.

6.

Remove DAT cartridge from the tape drive by pressing the eject button on the tape drive or entering: DISMOUNT MKA500: [CR].

7. When the data has been successfully captured, the operator will label the tape with the date, security classification of “SECRET,” UIC directory, site location, POC, and POC DSN telephone number, and forward to DISA/GS24.

5.2.3 Security Data Management Requirements

Table 5-6 provides step-by-step procedures for local data collection-supporting network SM.

Table 5‑6 Security Data Management Requirements

Disable/Enable Codes

Train users on how to program telephones and the Group Enable/ Disable function. Ensure telephones are disabled when unattended.

Switch Database Accounts. Change passwords periodically and anytime a user departs. Change passwords anytime they are included in data on DAT tapes.

Set up accounts for individuals needing access to the database and ensure the default login account (REDS) is deleted from the database.

Maintenance Logs

Each switch will have a maintenance log to record all switch activity. The log will include date, time, name, and what activity.

STU-III/R Keys

Call KMC at 1‑800-635-6301 to rekey the STU‑III/R keys annually.

Facility Maintenance

All facility maintenance activities in the area of the switch will be done only in the presence of cleared switch maintenance personnel.

5.2.4 Accounting Data Management Requirements

Because of the current methodology for billing for DRSN, there are no Data requirements that affect the O&M Command

5.2.5 RED Switch Level Device Reporting Requirement

Table 5-7 provides procedures for the “RED Switch Level Device” Reporting Requirement.

Table 5‑7 RED Switch Level Device Reporting Requirement

(Site Appointment)

All RED switch locations will maintain a master site list of all senior-level users, trunks, circuits, or any other locally important devices. This master list will be updated when changes occur and transmitted to the Scott AFB, GNSC, DISA-PAC or DISA-EUR TNCs. All locations will check and update this information a minimum of quarterly to ensure accuracy. Table 5-8 provides an example of the master list format for reporting RCSSII updates.

Table 5‑8 RED Switch Level Reportable Device Format

END *

* Note: “DISTANT END” is applicable to trunks only.

Intentionally Left Blank

Section 6. DRSN Site Security Management

6.1 Purpose

This section addresses the DRSN day-to-day Security Management requirements. It identifies existing DRSN security directives and provides guidance for implementation of required security-related activities.

6.2 SECTION Contents

Topics covered in this section are as follows:

· Responsibilities

· Accreditation and certification

· Access Measures

· Security Measures

· Information Classification

· Physical Measures

6.3 Definitions

Security management, threats, certification, and accreditation are explained in the following paragraphs.

6.3.1 Security Management

Each DRSN switch site must have a published system security plan (usually the Defense Intelligence Agency (DIA)-approved accreditation test report will suffice for the Sensitive Compartmented Information (SCI)-accredited nodes) that prescribes component configuration and procedures for:

· Safeguarding the switch complex

· Enforcing access controls to switch complex components

· Assigning subscriber terminal identifications and class markings

· Modifying the switch firmware and software

6.3.2 Threat

The DRSN is subject to many threats from a variety of sources. To maintain DRSN integrity, DRSN facilities (switches and associated equipment) must be protected from unauthorized modifications that could jeopardize network operations. Unauthorized manipulation of databases or other software could result in a significant threat to command, control, communications, and the national security.

6.3.3 Certification

Certification is a technical determination that a system satisfies established standards for security and integrity. Qualified technical personnel must verify that the system satisfies established standards for:

· Physical security

· Personnel security

· Operational security

· Computer security

· Communications security

6.3.4 Accreditation

Accreditation is a Designated Approving Authority (DAA) declaration that the system provides acceptable security and integrity. A DAA bases this management decision on the certification documentation and other factors, such as requests for waivers. The DIA is the DAA for SCI nodes. The DISA DAA accredits all other nodes.

6.4 SECURITY MANAGEMENT Responsibilities AND PROCEDURES

Tables 6-1 through 6-6 provide responsibilities and procedures for the O&Ms to use in conducting SM of the DRSN. The tables do not address all possible events that could occur, however, they do identify some key security measures required for the DRSN. Refer to MILDEP procedures or contact your responsible TNC for assistance on procedures not addressed within these tables.

Table 6‑1 Site Security Management Responsibilities

Assign a security compartment level and a terminal identifier to each DRSN terminal access line and switch cryptographic interface. The ISSO position will not be occupied by the SSO.

2.

Implement the switch-node security plan. In that capacity, the ISSO controls the modification or replacement of system hardware, software, firmware, or database contents that affect systems security features and any other changes involving granting or removing SCI access to a subscriber terminal. Additionally, the ISSO will control installation or relocation of subscriber terminals.

Ensure report (magnetic, electronic, and printed reports) classification is IAW DISAC 300-115-7, Chapter 5.

Table 6‑2 Certification and Accreditation

IAW DISAC 300-115-7, Chapter 6

IAW DISAC 300-115-7, Chapter 6

IAW DISAC 300-115-7, Chapter 6

Table 6‑3 Access Control Measures

Note: Single password entry will allow unrestricted access into the system.

IAW DISAC 300-115-7, Chapter 2

Request for access to physical area (switch consoles and subscriber terminals)

Requests for access to RED switch operating information, control functions, and software

Request for console access

Request for terminal access

Level 1 Access. Restrict access using the password system established by the Scott GNSC or theater TNC.

2.

Level 2 Access. Coordinate with the Scott GNSC or theater TNC to request temporary level 2 or higher access when local assistance is needed to bring the Promina node back on-line.

IAW DISAC 300-115-7, Chapter 4, and DRSN Promina Access Policy and Procedures developed by the Scott GNSC

Table 6‑4 Communication Security Measures (SAL Classmarks)

Table 6-4 Communication Security Measures (SAL Classmarks) (continued)

Table 6‑5 Information Security Measures Classification

Table 6‑6 Physical Security Measures

Section 7. Ordering Telecommunications Service

7.1 Purpose

This section provides a reference of existing policies and procedures for ordering telecommunications service and requesting logistics support for DRSN equipment and parts.

7.2 Definitions

The Telecommunications Service Request (TSR), the DRSN Telecommunications Certification Office (TCO), and the Telecommunications Service Order (TSO) are explained in the following paragraphs.

7.2.1 Telecommunications Service Request

A valid, approved, and funded telecommunications requirement prepared in accordance with the format in chapter 3 of the DISA Circular 310-130-1 and submitted to a DISA or DISA activities for fulfillment. TSR's may not be issued except by a specifically authorized TCO.

7.2.2 Telecommunications Certification Office

The activity designated by a Federal department or agency to certify to DISA (as a operating agency of the National Communications System) that a specified telecommunications service or facility is a validated, coordinated, and approved requirement of the department or agency, and that the department or agency is prepared to pay mutually acceptable costs involved in the fulfillment of the requirement.

The DRSN Program Management Office is the Designated TCO for all actions (i.e.. start, change or discontinue) involving the backbone transmission part of the DRSN inter-switch trunks.

7.2.3 Telecommunications Service Order

The authorization from Headquarters DISA, a DISA area, or DISA TMSO to start, change, or discontinue circuits or trunks and to effect administrative changes.

7.2.4 Request for Service (RFS)

The document used to initially request telecommunications service, which is submitted by the requestor of the service to his designated TCO.

7.3 Service Ordering Procedures

Table 7-1 provides procedures for the O&Ms to use in ordering service for DRSN users. The table does not address all possible events that could occur, however, it does identify the most common events in the DRSN. Refer to MILDEP procedures or contact your responsible GNSC for assistance on procedures not covered by this table.

Table 7-1 also identifies…