[Back]
[Index]
[Next]
|
[Back] |
[Index] |
[Next] |
Warfighter Guide to Intelligence 2000 |
TROJAN
Chapter 6 *
TROJAN *
(U) TROJAN System Overview *
(U) TDN AND TNCC OVERVIEW *
TROJAN Classic and TROJAN Classic XXI (TCXXI) *
(U) TROJAN SPIRIT II (TS II) *
ICDs *
Black End-to-End Test. *
Red End-to-End Test. *
DVCT Troubleshooting *
Connectivity between CCS and TROJAN SPIRIT Il. *
PHYSICAL CONNECTIVITY. *
MITT/TROJAN SPIRIT II INTERFACE *
INTERNET PROTOCOL (IP) ADDRESSES. *
RED SECRET (COLLATERAL) ETHERNET LAN INTERFACE. *
- The United States Army’s PROJECT TROJAN features two distinct, yet technically linked systems. The first of these is the TROJAN Classic, which historically preceded the second, the TROJAN SPIRIT. The two distinct systems are both supported by the TROJAN Data Network communications architecture.
(U//FOUO) The TROJAN system architecture is a digital communications system, which was primarily established for maintaining linguistic and analytical skills of U.S. Army Intelligence personnel globally. The TROJAN mission has been expanded to include a point-of-access for deployed U.S. Army and Joint Task Force (JTF) assets for globally accessing theater and/or national-level databases or systems during sustained or multi-tiered operations. The TROJAN Classic System architecture consists of the following elements: Central Operating Facilities (COFs), Remote Collection Facilities (RCFs), TROJAN Switch Extensions (TSEs), and the TROJAN Network Control Center (TNCC). Also include in the TROJAN architecture to support the tactical commanders in the field are TROJAN Special Purpose Integrated Remote Intelligence Terminals version II (SPIRIT II), and as well as TROJAN Lightweight Integrated Telecommunications Equipment (LITE) terminals.
(U//FOUO) The Army originally designed the TROJAN Data Network (TDN) to support intelligence training and operational readiness. The Army envisioned that the TROJAN Program, supported by the TDN communications architecture, would provide a worldwide capability. This capability would then enable Military Intelligence (MI) soldiers located in garrison to remotely target and exploit global enemy operations in near-real-time, thereby enhancing their language skills and operational readiness. TROJAN’s original mission expanded greatly since its inception, to include developing a seamless communications system that enables interconnectivity from the tactical level among lateral echelons through and including echelons above corps and national intelligence producers to provide army intelligence support to combat commanders. This consequential advancement occurred with the creation of the TROJAN Network Control Center (TNCC) at Fort Belvoir, Virginia.
(U//FOUO) The TDN is a TCP/IP based Wide Area Network (WAN) that has been implemented on existing TROJAN communications architecture. The TDN provides the warfighting commander with a secure and reliable means of communicating U.S. intelligence information. The TDN facilitates the vertical and horizontal exchange of intelligence between echelons below Corps (EBC), and echelons above Corps (EAC) to include Department of Defense (DoD) and national level organizations and strategic locations. The TDN integrates intelligence communications and analysis support capabilities between the battlefield.
(U//FOUO) The addition of the TNCC to TROJAN provided for a central point of communications connectivity for the TDN. The TNCC uses both commercial and government communications, as available, to provide connectivity to TROJAN sites worldwide. The TNCC uses multiplexing technology to provide collateral and/or SCI communications to TROJAN locations. This feature allows TROJAN elements connectivity to connect to JWICS, SIPRNET or both. Additionally, select elements of the TROJAN architecture are anticipated to have Global Connectivity Service (GCS) in the near future. Such connectivity supports commanders both in garrison and in the field. At many sites, the TROJAN System provides the only available communications architecture for the unit’s classified LANs.
(U) Although sharing a common project name and a common network architecture, the TROJAN Program can be divided into two distinct categories: the TROJAN Classic and the TROJAN SPIRIT.
- TROJAN Classic and TROJAN Classic XXI (TCXXI)
(U) TROJAN Classic is the name of a system, which provides a combined operational readiness, and training system. TROJAN Classic uses advanced networking technology to provide cryptologic support, such as rapid radio relay and secure communications, to U.S. forces throughout the world. TROJAN operations may be easily tailored to fit military intelligence unit training schedules, and surged during specific events to provide direct support intelligence to the tactical commander.
(U//FOUO) Originally designed to allow MI soldiers to train in their languages by accessing live language environments, some elements of TROJAN Classic naturally evolved into a SIGINT collection system. These components consist of the Remote Receiver Group (RRG) and the Monitor Control Group (MCG). RRGs, located in Remote Collection Facilities (RCFs), are positioned strategically around the world for access to favorable target signal environments. Communications from RRGs are routed through the TNCC to MCGs, housed in Remote Operations Facilities (ROFs) at various garrison locations. The TNCC switching element, controlled by the Army TCAE at Fort Meade, Maryland determines which RRG communications will be routed to which MCGs. All TROJAN elements, both fixed and mobile must connect through the single switching node at the TNCC, creating a star configuration network.
********INSERT DRAWING AS EDITED*****
(U//FOUO) The other component of the TROJAN Classic is the TROJAN Switch Extension (TSE). Installed at numerous Army locations worldwide, TSEs provide the capability of telephony and data exchanges between all other facets of TROJAN, to include RRGs, MCGs, TSEs, and TROJAN SPIRIT. The Army TCAE uses a TSE for connectivity to the TNCC to complete its switching activities for the TROJAN Classic System. Additionally, TSEs provide vital secure communications and cryptologic support capabilities for units engaged in split based unit operations. TROJAN Switch Extensions do not conduct SIGINT collection operations, although they may be used to provide cryptologic support to such.
(U//FOUO) TROJAN Classic XXI (TCXXI) is the recapitalization and modernization of the TROJAN Classic System which brings TROJAN into compliance with the evolving national Common Remoted Systems (CRS) architecture. TCXXI uses common hardware, software and protocols in compliance with CRS standards. This commonality affords TCXXI with interoperability with other national and sister service systems, allowing resource sharing and seamless interconnectivity.
(U//FOUO) Common, shared software interfaces allows MI soldiers to transition between TROJAN operations and other CRS operations facilities with no additional training needed. Intuitive, easy to learn operating software, complete with locally available computer based training, ensures that new operator training can be conducted locally with minimal impact on ongoing operations. All TCXXI ROFs receive on-line dictionaries, transcription tools and other working aids to assist them in their operations and training. Ethernet connectivity between TCXXI sites and the TNCC facilitates the remote upgrade or addition of software, as well as provides enhanced remote troubleshooting and diagnostic capabilities. This same Ethernet connectivity continues to allow TCXXI sites with data sharing capability through file transfers.
(U//FOUO) TCXXI will continue the initiative of providing mobile or transportable components, to include the future modernization of systems such as the TROJAN Classic’s TROJAN Air Transportable Electronic Reconnaissance System (TATERS).
TATERS utilizes equipment common to other TROJAN Classic Systems. TATERS is a transportable ground terminal for the TROJAN System and is less mobile once placed in its intended configuration. Featuring eight and 20 foot satellite dishes, TATERS is a modular system housed in International Standards Organizations (ISO) shelters. TATERS places the full range of TROJAN collection capabilities in this transportable configuration. It supports the Army’s contingency missions by providing worldwide, forward deployed, quick reaction capabilities. TATERS is reconfigured and staged at depot prior to each operational deployment in order to mount only those assemblies required for the specific contingency mission. Once prepared for deployment, TATERS can be transported by C-130 or larger aircraft or sling-loaded from a CH-47. TATERS is fully self-supporting, including integrated power generations and the following four subsystems: Common Hardware Intelligence Processing Subsystem (CHIPS); Satellite Communications INTELSAT/DSCS Nodal Subsystem (SCINS); Primary Electrical Equipment Life Support (PEELS); Temporary Occupancy Troop Shelter (TOTS).
(U//FOUO) Additional prototype systems currently in development for TCXXI include the CRS compliant TROJAN Mobile Remote Receiver System (TMRRS) and the TROJAN Soldier Portable Remote Intelligence Group (T-SPRING). TMRRS is a modularly configured, intelligence receiving and dissemination system that exploits the RF spectrum. Like TATERS, TMRRS utilizes common TROJAN Classic and TROJAN SPIRIT hardware. The satellite communication system can operate in both the C- and Ku-commercial bands. TMRRS operates within the TROJAN architecture and can be remotely controlled by MCGs.
(U//FOUO) The TROJAN Soldier Portable Remote Intelligence Group, currently in the prototype development stage, consists of TCXXI receiver and SPIRIT communications hardware integrated into a fly-away capability. This transportable element provides the deployment flexibility critical to meet the rapid, short notice deployments inherent in the evolving National Military Strategy and may be deployed under the INSCOM QRC SIGINT program.
- (U) TROJAN SPIRIT II (TS II)
(U//FOUO) The TROJAN SPIRIT II program was established during Operation Desert Shield/Storm to satisfy an immediate need for additional intelligence capability in order to support imagery and other intelligence dissemination, as well as split based intelligence exchange between forward deployed and sanctuary warfighter elements.
The current TS II, AN/TSQ-1909 (V) consists of secure voice collateral SECRET and TS/SCI, data, fax, video, and secondary imagery dissemination capabilities. It is mounted on a Heavy Variant HMMWV and has a tunnel mounted 10 kW power generation system and can also connect to commercial power generation equipment. The system will receive, display and transmit imagery, weather and terrain products, templates, graphics, and text between forces in a split-based operation. These capabilities are provided on the SECRET collateral and TS/SCI LAN/WAN with router operational data rates up to 512 kbps for the two classified networks. There are a total of 14 data channels (8 TS/SCI and 6 SECRET collateral) available for use on the accredited dual level multiplexer, for a total aggregate output rate of up to T1 (1.544 Mbps) data rate.
(U//FOUO) The TS II provides a mobile tri-band, C-, X-, and Ku-band, Super High Frequency (SHF) satellite terminal that is deployable within either a low, medium, or high intensity environment to support the dissemination of critical Intelligence and Electronic Warfare (IEW) data. The C- and Ku-band version of the TS II is deployed at division and maneuver brigades, while the X-band version is found at corps and theater-levels. The TS II can come with two antennas, a 2.4-meter antenna for C- and Ku-bands, and a 6.1-meter antenna for X-band, C- and Ku-bands. The TS II provides a critical communications capability to intelligence systems and organizations, such as the U.S. Army’s All-Source Analysis System (ASAS), the U.S. Marine Air Ground Task Force (MAGTF) Intelligence Analysis System (IAS), and the Joint Chiefs of Staff’s (JCS) National Military Intelligence Support Team (NMIST). In supporting deployed intelligence elements, the TS II provides long-haul satellite and remote communications services necessary for establishing and sustaining split-based operations.
(U//FOUO) The TS II additionally features the TS II Video Intelligence Enhanced Workstation and Server (VIEWS) which provides Video Teleconferencing/Video Forwarding capability. This is accomplished via specialized cards for video compression; "tiled" screen displays, and external VTC equipment (camera, speaker, and microphone). There is one VIEWS in the Primary HMMWV Shelter (PHS) of the TROJAN SPIRIT 11 system, and another in the Spare Equipment and Maintenance (SEM) shelter. The VIEWS equipment performs all of the standard functions of database access, file transfer, e-mail, templating, report generation, etc., using JDISS or ASAS-WARLORD software, in addition to its VTC and reconnaissance video forwarding functions.
(U//FOUO) The TROJAN Lightweight Integrated Telecommunications Equipment (LITE) II is a variant of the TS II that provides a fly-away intelligence dissemination capability and provides voice and data connectivity from a Maneuver Battalion or Brigade to the Division or Corps Analysis and Control Element (ACE). TROJAN LITE system deployment takes utilizes available C and Ku-band satellite communications. Units can operate the TROJAN LITE II at both the SECRET Collateral and TS/SCI security level. The TROJAN LITE design allows for interoperability and communications connectivity with unit-organic processors, such as ASAS, Remote WorkStation (RWS) and Joint Deployable Intelligence Support System (JDISS). Rapidly deployable, TROJAN LITE set-up and activation time, from time of arrival at the deployment site, is under 30 minutes.
- Internal Control Documents (IDCs)
The best resource for interfacing one system to another is the system Interface Control documents (ICDs). In order to best utilize these documents, it is necessary to understand how to retrieve them and to know how they apply to your unit’s architecture. Unless your unit has an extensive library of these ICDs, it may be necessary to contact the Program Manager for each system to gain access to the documents. At a minimum units should have the ICDs necessary to support their primary and at least one alternate systems interface plan. The following are extracts from a variety of ICDs in order to illustrate the level of detail included in an ICD.
- Black End-to-End Test.
The following paragraph provides the steps required performing a Black end-to-end test.
a. Configure FIREBERD 6000 test set as follows:
(1) Power ON.
(2) Press DATA button until LED corresponding to 2047 is illuminated.
(3) Press GEN CLK button until LED corresponding to INTF is illuminated.
(4) Press MENU button until LED corresponding to INTF SETUP is illuminated.
(5) Press interface select button corresponding to 188BAL. Display reads
"INTERFACE: 188BAL"
(6) Press ANALYSIS RESULTS <CATEGORY> rocker switches until
LEDs corresponding to ERROR are illuminated.
(7) Press ANALYSIS RESULTS <RESULT> rocker switches until BER is
displayed.
(8) Press ANALYSIS MODE button until LED corresponding to
CONTINUOUS
is illuminated.b. At the FIREBERD test panel, connect cable W179 P1 to FIREB ERD front
panel connector labeled "To DCE" and P2 to BLACK TEST J1.
c. At Black Digital Patch Panel (BDPP), insert an EPC-1-3 patch cord in test
module, and insert the other end in A1 MODEM connector.
d. Contact DDSG, and tell them you have configured for Black end-to-end test.
DDSG will configure their end to return test signals.
e. When tests are in sync, Bit Error Rate (BER) should be less than 10 –5
- Red End-to-End Test.
The following paragraph provides the steps required performing a Red end-to-end test.
a. Configure FIREBERD 6000 test as follows:
(1) Power ON.
(2) Press DATA button until LED corresponding to 2047 is illuminated.
(3) Press GEN CLK button until LED corresponding to INTF is illuminated.
(4) Press MENU button until LED corresponding to INTF SETUP is illuminated.
(5) Press interface select button corresponding to 188BAL. Display reads
"INTERFACE: 188BAL"
(6) Press ANALYSIS RESULTS <CATEGORY> rocker switches until
LEDs corresponding to ERROR are illuminated.
(7) Press ANALYSIS RESULTS <RESULT> rocker switches until BER is
displayed.
(8) Press ANALYSIS MODE button until LED corresponding to
CONTINUOUS
is illuminated.b. At the FIREBERD test panel, connect cable W179 P1 to FIREBIRD front
panel connector labeled "To DCE" and P2 to RED TEST J3.
c. At Red Digital Patch Panel (RDPP) No.1, insert an PMPC-3 patch cord in
test connection module, and insert the other end in A1 MODEM connector.
NOTE
KIV-7 No.1 must be properly keyed and on-line prior to initiating this test.
d. Contact DDSG, and tell them you have configured for Red end-to-end test.
DDSG will configure their end to return test signals.
e. When tests are in sync, BER should be less than 10 –5
- DVCT Troubleshooting
a. If the display on the DVCT you intend to use is displaying OUT OF SYNC, you
cannot make a call on that phone until you perform the following:
(1) Go to another DVCT and see if its display is displaying VOICE MODE.
(2) If the other DVCT's display is displaying VOICE MODE, this means your
circuit is operational.
(3) Put the MUX port for this DVCT on a port loop. If the DVCT displays VOICE
MODE, you need a reset performed by the Digital Data Switching Group
(DDSG) on the DVCT you want to use.
(4)
Call the DDSG (Order wire #0131/0133) and state "This circuit number XXXXXNN at site XXXXXXXXX. (Circuit number is provided during equipment
setup. The site name is your geographic location.) My DVCT phone number
XXXX (number of phone out OF SYNC; for example: 6592) is not working.
Please give me a reset on 6592."
(5) The DDSG will then perform a reset procedure, which will normally take about
one to two minutes to complete.
(6) When the reset is completed, the DVCT will display VOICE MODE, and the
phone will now be operational.
b. If all three DVCT displays are displaying OUT of SYNC, observe the display of the MUX. This display should read OPERATION NORMAL. If the display reads
OPERATION ALARM
, call your on-site maintenance technician.- Connectivity between CCS and TROJAN SPIRIT Il.
This figure shows a cable between the two multiplexer at the TROJAN Switch Center. This cable is called a bypass cable, which provides a point-to-point connection at the multiplexer port level between two TROJAN systems. To have this cable put in place, initiate coordination with the lSC-Fort Belvoir representative several days prior to making this interface (DSN 235-2257, Commercial (703) 706-2257).
- PHYSICAL CONNECTIVITY.
- CCS - Internal.
The CCS has four major components that are involved with the connection to the TROJAN SPIRIT II: the Communications Support Processor (CSP), Communications Protocol Processor (CPP), KG-84A and CODEX 2510. In 8-3 TB 32-5895-400-12&P-1 8-4 the Version 3 CCS, these components are located within the CCS shelter and connected through patch panels. This document does not dictate which CPP port, KG-84A or CODEX 2510 the CCS operator must use.
CCS - External.
The CCS Version 3 uses an external junction box for analog or "four wire" connectivity to external users, i.e. Mobile Subscriber Equipment (MSE), MITT, TROJAN SPIRIT II, etc. This junction box provides a connection to the analog side of two CODEX 2510 modems within the shelter. The quad or set of transmit and receive punch blocks chosen at the junction box determines the CODEX 2510 modem to be used. The Version 2 CCS external communications package has the transmit and receive punch blocks located on the rear of the CODEX and KG-84A rack.
- TROJAN SPIRIT II - Internal.
The CODEX 2510, KIV-7 #3 and the DNE 2048AT-16 Multiplexer port 1 are the internal components of the TROJAN SPIRIT II used for the CCS interface. The signal path for this interface goes from the Black Entry Panel, through the Black Patch Panel (analog), to the CODEX 2510, back through the Black Patch Panel (digital), to the Black side of KIV-7 #3, to the Red side of KIV-7 #3, then to the Red Tip Ring Patch Panel, and terminating at Multiplexer port 1. This signal flow is directly connected and does not require patching at either the Black or Red patch panels. Programming and settings for the components identified are included in these instructions.
- TROJAN SPIRIT II - External.
The transmit and receive "four-wire" coming from the CCS is attached on the Black Entry Panel punch blocks labeled "CODEX 2510" connector J2. The transmit connection on the TROJAN SPIRIT II must correlate to the receive connection at the CCS, leaving the receive connection on the TROJAN SPIRIT II to correlate with the transmit connection from the CCS.
- CCS SETUP.
- CSP Programming.
The CSP should be programmed with the following settings:
Option Setting
Mode 1
Data Rate 2400
CRC Not Used
Crypto Resync Yes
Audit In No
Satellite Yes
Delay 9 sec
TB 32-5895-400-12&P-1
NOTE: When setting the port to be used, choose TXDIN and RXDIN. This sets the DIN flag and routes all messages in and out of the DIN queue.
KG-84A Settings.The front panel settings:
FUNCTION
SETTING
CLOCK
1
DATA MODE
2
DATA RATE RX
8
DATA RATE TX
8
TOGLE SWITCH
B
TOGLE SWITCH
B
STEP PULSE INTVL
1
STEP PULSE INTVL TOGLE SWITCH
+0
TTY MODE
1
INTFC
3
DATA LENGTH
SYNC
SYNC MODE
1
COMM MODE
1
NOTE: The keymat loaded into the KG-84A must also be loaded into the TROJAN SPIRIT II KIV-7 #3, with the same day count displayed.
CODEX 2510 Settings. Table 8-1 lists the settings, which must be programmed into the CODEX 2510.
Internal strapping:
CCS CODEX 2510 SETTINGS
BD
PLUG
FUNCTION
STRAPPING
STRAPPING
A1
P2 P3
ETCT
UNBAL J5-J6 J9-J10
P4 P5
SMT CTRL/CTTR
UNBAL J11-J12 J14-J15
P6
INTERFACE
KG84 J17B
A2
P2 P3
TCTC
UNBAL J5-J7 J8-J10
P4
CLK LOCK
DSBL J20-J22
P5 P7
CTCD/CTRS
UNBAL J14-J16 J11-J13
P6
CTCD/CTRS
KG84 J17-J18
A5
P2
TIME OUT
DSBL J8-J9
P3
VUX
ENBL J5-J6
P4
FILL SELECT
KG84 J12-J13
A6
P2
U UPDATE
ENBL J7-J8
A9
P2 P3
RED I/O
UNBAL J6 J7
P4
STEP PULSE
DBL J9-J10
P5
TX CLOCK
CONT J11-J12
- TROJAN SPIRIT II SETUP.
CODEX 2510 Settings.
KIV-7 SETTINGS:
NOTE: The keymat loaded into KIV-7 #3 must be the same as that loaded into the CCS KG-84A, with the same day count displayed.
Multiplexer settings:
The following settings are to be used for multiplexer port 1:
PORT 1
SYNCHRONOUS
EQUIRATE
2400
CL-HIGH
RX-INT
TX-INT
CENTERED
NEG-MARK
- CONNECTIVITY TESTING.
The following loopbacks can be helpful in determining if the equipment settings and physical connections are correct.
- CCS Testing.
C CODEX 2510 Loop. The CODEX 2510 has a loop test called MODEM CHECK. Initiate this loop and turn the TXDIN and RXDIN ports on. When the loop is initiated the KG-84A should show a Synch indication and the TXDIN and RXDIN ports will indicate that the line is up. A message transmitted will then be received into the DIN queue.
C Remote CODEX 2510 Loop. After the MODEM CHECK is turned off the CCS CODEX 2510 should synchronize with the TROJAN SPIRIT II CODEX 2510. If this is achieved the TX data, RX data, TX clock and RX clock lights will be lit. Also, under the STATUS menu a display of AQ=9 indicates a quality connection between the two modems. Activate the MODEM CHECK loop on the TROJAN SPIRIT II CODEX 2510. As in the previous loop test the KG-84A should show a Synch indication. Turning the TXDIN and RXDIN ports on, the CSP should indicate the lines are up. A message transmitted will then be received into the DIN queue.
C Multiplexer Local Loop. Taking the TROJAN SPIRIT II CODEX 2510 out of the
MODEM CHECK loop, KIV-7 #3 should show an FDX TR indication. The CCS KG-84A should also show a Synch indication. Placing multiplexer port 1 into a LOCAL loopback, the CCS TXDIN and RXDIN line indications should be up. A message transmitted will then be received into the DIN queue.
C Multiplexer Remote Loop. Removing the port 1 local loopback, place port 1 now into a
REMOTE loopback.
- TROJAN SPIRIT II Testing.
C CODEX 2510 Loop. The CODEX 2510 has loop test called MODEM CHECK. When the loop is initiated, KIV-7 #3 should display FDX TR.
C RED Bit Error Rate Test. Both TROJAN SPIRIT II systems will connect their FIREBERD 6000M test sets to port 1 of their multiplexers via the test patch and tip ring patch panels. The synthesized rate of operations is at 2400, with a MIL-188-114 interface. With both FIREBERD test sets set appropriately, they should indicate data, clock and sync. This test shows a good connection through the bypass cable at the TROJAN Switch Center between both TROJAN SPIRIT II"s. TB 32-5895-400-12&P-1
MITT/TROJAN SPIRIT II INTERFACE INTRODUCTION.
Within the T-SCIF area, connection between the MITT and TROJAN SPIRIT II is achieved through the MITT Night Hawk 4400 Gateway Guard and the TROJAN SPIRIT II Red Entry Panel. For the purpose of non-TENCAP assets, external connectivity to the MITT is limited to Ethernet Thinnet (TNC) connector or 4-wire cable (binding post). The 4-wire X.25 Black entry will be encrypted data with modems used to extend the circuit between shelters. The TROJAN SPIRIT II Red Entry Panel provides access to both Secret and SI/TK communications services.
- INTERNET PROTOCOL (IP) ADDRESSES.
The MITT will continue to use IP addresses that are organic to their system. The TROJAN SPIRIT II Computer Security Officer (CSO) will assign TDN1 IP addressees to the MITT for the purpose of bridging the two networks at the Night Hawk Gateway Guard.
- RED SECRET (COLLATERAL) ETHERNET LAN INTERFACE.
LAN Access.
The Red Secret (collateral) Ethernet LAN Interface provides the TENCAP system direct LAN access to the TROJAN WAN. Connectivity between the two systems will be from the TENCAP Guard Ethernet Thinnet cable to the TROJAN that provides Thinnet interface. The TENCAP system will provide the necessary transceiver for the interface.
From Equipment
Connection
To Equipment
Connection
(TENCAP)
TENCAP Guard
Ethernet Card
(TENCAP)
Attachment Unit
Interface (AUI) 15-
Pin Male
Connector
(TENCAP)
Ethernet
Transceiver
(TENCAP)
BNC to
Transceiver, TNC
to TROJAN
SPIRIT II/ Thinnet
Cable
(TROJAN)
TROJAN SPIRIT
II, J7-Red Entry
Panel
(TROJAN)
TNC Connector/
Thinnet Cable
(TROJAN)
Cisco 4000 Router
Ethernet LAN
(TROJAN)
Internal Cabling
TROJAN SPIRIT II operators will normally provide the first 100 feet of Thinnet
cable from J7, terminating the cable with a 50-Ohm impedance terminator. If the
J7 connector is occupied, the connection to the LAN will be made between an
existing cable connection or at the end of the Ethernet cable. In either case, a
TNC "T" connector will be used to connect to the LAN. If connection is at the
end of the cable, a 50-Ohm impedance terminator will be placed on one side of
the T connector.
RED SECRET (COLLATERAL) X.25 WAN INTERFACE.
TENCAP Guard to Serial Port Interface. This Red interface is X.25 from the TENCAP Guard to the serial port of the TROJAN SPIRIT II router. The router serial port can be programmed for the LAN or remain serial, back to the TSC and TROJAN WAN access. From the TROJAN SPIRIT II Red Entry Panel, a 25-pair will be extended, up to 200 feet and terminated with a 25-pin, "D" shell female connector. The subscriber (TENCAP) will interface the TROJAN SPIRIT II cable with a 25-pin, "D" shell male connector. For pin assignments of signals see Figure 1-5 in ICD TB 32-5895-400-12&P-1. In situations where pin assignments are not compatible, a wiring adapter (also shown in Figure 1-5) provided by TROJAN SPIRIT II personnel will be added to the cable to allow for signal strapping. The subscriber (TENCAP) will interface the wiring adapter with a 25-pin, "D" shell male connector.
FROM
EQUIPMENT
CONNECTION
TO
EQUIPMENT
CONNECTION
(TENCAP)
TENCAP Guard
X.25 Serial Card
(TENCAP)
RS-232
(TENCAP)
Interface Cable
(TENCAP)
25-Pin Mail "D"
Shell Connector to
TROJAN SPIRIT II Interface Cable
(for Wiring
Adapter)
(TROJAN)
Interface Cable
(TROJAN)
25-Pin Female to
TENCAP Interface
Cable/ Red Entry
Panel Connection
(TROJAN)
J1-J4 of Red Entry
Panel
(TROJAN)
Cannon Plug
(SPIRIT II)
Tip/Ring Patch
Panel No. 2
(SPIRIT II)
Internal
(SPIRIT II)
Tip/Ring Patch
Panel No. 1
(SPIRIT II)
Patch Cord
(SPIRIT II)
Cisco 4000 Router
Serial Port 1
- 2510 MODEM SETUP:
CODEX MODEM 3251 CONFIGURATION
:- KIV-7 SETTINGS:
|
[Back] |
[Index] |
[Next] |