Table of Contents - Noodlez.org Courses PDF Student Guides... · 1-Centrix Cases 2811 Cisco Router CITRIX WAN Accelerator KG-175D-TACLANE 1-Spares Case 3 – Spare LNBs 1 – Spare

Table of Contents

Chapter 1 SIPR NIPR Access Point Chapter 2 Antenna Installation Chapter 3 ODU Equipment Chapter 4 RF Assembly and Components Chapter 5 Initial System Deployment CONUS Chapter 6 Initial System Deployment OCONUS Chapter 7 Baseband Theory Chapter 8 Baseband Components Chapter 9 Call manager Express Chapter 10 Access Lists Chapter 11 Backup/Restore Router Configuration Chapter 12 TACLANE (KG-175D) Chapter 13 Troubleshooting Chapter 14 Command Device Commands Chapter 15 Preventive Maintenance Chapter 16 Satcom Definitions

SIPR NIPR Access Point SNAP

2

3

System Overview

The SIPR/NIPR Access Point (SNAP) is a complete communications terminal consisting of a radio frequency (RF) side and a baseband side; providing access to the local IP network while communicating with distant terminal stations. Users have full access to input any form of IP equipment such as IP telephones and computers; fully separated via secure (SIPR) and non-secure (NIPR) communications. SNAP terminals can be customized to communicate within several tactical networks or communicate within its own SNAP meshed network. The SNAP contains full SIPR & NIPR capability and is pre-wired to be compatible with several Ethernet enabled modems. The SNAP falls under the everything-over-IP (EoIP) architecture and is built with satellite auto-tracking features. The SNAP system is a move towards the automated telecommunications systems; requiring less work from the user.

4

3

2.0M Antenna Assembly

UPS Case

SIPR Baseband Case:2811 Cisco RouterCitrix WAN AcceleratorKG-175D-TACLANE

RF Case:Antenna ControlLinkway S2 Modem

NIPR Baseband Case:2811 Cisco RouterCitrix WAN Accelerator

CITRIX Case:2811 Cisco RouterCitrix WAN AcceleratorKG-175D-TACLANE

System Overview

The SNAP package contains 11 cases upon shipment. Below is the breakdown of all cases: 1 – Case containing antenna base 1 – Case containing 1 center reflector and 4 pedals 1 – Case containing 4 legs, 2 strut bars for boom, 4 strut bars for leg assembly, & 1 boom 1 – Antenna assembly case 1 – Block UpConverter (BUC) 3 – Low Noise Blockers (LNB) 1 – TX/RX cable 1 – Power Cable 1 – HMMV Power Cable 1-RF Case Antenna Control Linkway S2 Modem TrackStar Handheld 1 – IP Phone 1 – CF-30 Laptop

5

Accessory Cables 1-UPS Case UPS 1-NIPR Case 2811 Cisco Router CITRIX WAN Accelerator 1-SIPR Case 2811 Cisco Router CITRIX WAN Accelerator KG-175D-TACLANE 1-Centrix Cases 2811 Cisco Router CITRIX WAN Accelerator KG-175D-TACLANE 1-Spares Case 3 – Spare LNBs 1 – Spare BUC 1-User Accessory Case 4 – IP Phones 3 – CF-30 Laptops Accessory Cables Rack Mounted Router Configuration 1-NIPR Case 2811 Cisco Router CITRIX WANScaler IP Accelerator 1-SIPR Case 2811 Cisco Router CITRIX WANScaler IP Accelerator KG-175D-TACLANE (GFE) 1-Centrix Case 2811 Cisco Router CITRIX WANScaler IP Accelerator Embedded Router Configuration 1- Embedded Case 1- NIPR 2811 Cisco Router CITRIX WANScaler IP Accelerator External Power supply with Input power measurement

6

1-SIPR 2811 Cisco Router CITRIX WANScaler IP Accelerator KG-175D TACLANE Mount kit. 1-Accessories bag including all RJ-45 cables needed for cabling

7

SIPR Encrypted via TACLANE and Tunneled through NIPR

SIPR Encrypted via TACLANE and Tunneled through NIPR

System Overview

Above is a simple block diagram of a Point to Point SNAP network. The diagram breaks out all vital equipment indicating the transmit (TX) and receive (RX) signal flow. It is important to understand the signal flow of the system. Understanding the signal flow provides a clear understanding of how a data flows through the system. For instance, the diagram shows how SIPR data has to flow through the NIPR router on TX and RX via a secure tunnel created by the TACLANE. This leads to the understanding that SIPR relies on NIPR to transfer packets; a very important piece to understand during troubleshooting. Note: The VLANS depicted in the diagram are only examples and may not be the actual VLANS used for the deployed SNAP.

8

5 BN CPN

STEP

Ku TDMA

Ku FDMA

(BCT)

JNN

Hub Node(Div/Corps)

DISN/GIG

DISN/GIG(cable)

SNAP

TDMA Mesh & Satellite Backbone

The tactical TDMA Mesh network utilizes a Ku Band commercial satellite network for the backbone interconnectivity of its systems. Both Time Division Multiple Access (TDMA) and Frequency Division Multiple Access (FDMA)are utilized. The TDMA network architecture is composed of four primary systems: 1. Unit Hub Node (UHN) 2. Joint Network Node (JNN) 3. Battalion Command Post Node (Bn CP N) 4. SIPR/NIPR Access Point (SNAP) These systems provide communications support to the various elements within an Army Division. The UHN is located at the Division and/or the Corps element. It provides connectivity to the Defense Information Systems Network (DISN) and the Global Information Grid (GIG). The UHN utilizes both FDMA and TDMA satellite connectivity. The JNN is located at the Brigade Combat Team (BCT) element. It serves as both a distribution point for the various systems within the BCT and provides direct network services for the Brigade headquarter elements. The JNN can utilize both TDMA and FDMA satellite connectivity. It has a single FDMA link which is usually reserved connectivity to the UHN.

9

The Bn CPN provides direct network access to users within a Battalion element. It utilizes only TDMA satellite connectivity. It has permanent links to the UHN and/or JNN and can establish on demand connections to other CPN’s within the BCT. The SNAP system is located at the Company level and, like the CPN, only utilizes TDMA. Also, like the CPN, the SNAP system is able to establish permanent links to JNNs, CPNs, UHNs, and C band and X band terminals (feed assembly must be changed to communicate with X band and C band terminals.

10

6

What is a Satellite?

Repeater in the sky

SATCOM and RF Theory

A satellite is simply a repeater in the sky. A satellite is any object that orbits or revolves around another object. For example, the Moon is a satellite of Earth, and Earth is a satellite of the Sun. The earth has many man-made satellites orbiting around it. Communications Earth Remote Sensing Weather Global Positioning These satellites are in varying orbits around the earth: Geostationary – 22,300 miles Low Earth Orbit – 200 – 500 miles

11

7

Why Satellite?• Allows for beyond line of sight (BLOS) extension

• Accessible from virtually anywhere on the battlefield

• No need for extensive “link”planning for installation of ground systems at a new

location

• Scales well for maneuver units

• Current ground equipment readily transportable

Transponder

SATCOM and RF Theory

The use of satellite communications by the JNN network allows for the installation and operation of a very flexible intra-network backbone for its users. Tactical line of sight radio systems (LOS) are normally limited to a maximum range of approximately 40 miles. This limits the area on a battle field that maneuver units can cover. With satellite, two systems can establish a radio link as long as they are within the earth “footprint” of the satellite coverage. This coverage can be rather large allowing systems to be hundreds of miles apart. LOS radio link installation requires extensive planning and engineering utilizing complex computer programs to provide a “profile”. It is not always possible to establish an LOS radio link between two locations. Whenever LOS radio systems are moved to a new location, this link planning must be conducted again prior to the installation of the new radio link. Satellite on the other hand requires initial link planning for the installation of radio links. Once this is done, systems can move almost anywhere within the footprint and reestablish the radio link. Also, there are virtually no limits to establishing a satellite link as long as there is a clear line of sight path between the earth system and the satellite. With the flexibility noted above, satellite based systems serve well in meeting the needs of Army combat units. As changes occur on the battlefield and units are required to move, satellite based systems provide them the ability to rapidly terminate and reestablish communications in a minimal amount of time.

12

Polarization

8

Vertical PolarizationHorizontal Polarization

Angle of the transmission/reception wave Way to reuse same frequencies Typically commercial satellite cross polarization One polarization up and the opposite down (e.g. V/H) Co-Polarization is the same polarization up and down

13

9 Provided by BCBL(G)

Transponder

• Antenna determines coverage area onearth's surface

Footprint

Ground, Space, Control Segment

There are three major segments within satellite communications: Ground Segment – contains the satellite earth terminal i.e. SNAP. Space Segment – contains the communications satellite Control Segment – satellite administrators which grant control and access to the satellite. SNAP operators will exclusively be a part of the Ground Segment. Under the ground segment the satellite has a coverage area known as the satellite footprint. In order for a SNAP terminal to communicate to any satellite it must be within the satellite’s footprint or coverage area.

14

10

Ku-band (Europe):Downlink: FSS: 10.700-11.700 GHz Uplink: FSS and Telecom: 14.000-14.800 GHz;

Ku-band (America): Downlink: FSS: 11.700-12.200 GHz Uplink: FSS: 14.000-14.800 GHz

Ku-band (Asia): Downlink: FSS: 10.950-11.700 GHz Uplink: FSS: 14.000-14.800 GHz

Space Segment

Frequency bands of communication and reference satellites are a part of the space segment. There are different receive frequencies per strategic location. In the SNAP spares case there will be three redundant LNBs. Each LNB is dedicated to a specific strategic location as depicted above. It is important for the operator to use the correct LNB for the specific location. Using the incorrect LNB will cause the VSAT antenna to scan a frequency band not associated with the area. Note, that with TDMA there is one transmit frequency which is shared throughout all systems.

15

Frequency Ranges

11

Uplink Downlink

C-Band 5.9-6.4GHz 3.7-4.2GHz

X-Band 7.9-8.4GHz 7.25-7.75GHz

Ku-Band 13.75-14.5GHz 10.7-12.75GHz

Ka-Band 27.5-31GHz 18.3-20.2GHz

Military 30-31GHz 20.2-21.2GHz

Commercial 27.5-30GHz 20.2-21.2GHz

16

12

SNAP SNAP

No Users Users

Signal

Noise

Shared BW

TDMA

TDMA is a digital transmission technology that allows a number of users to access a single radio-frequency (RF) carrier without interference by allocating unique time slots to each user within each carrier. The type utilized within JNTC-S is referred to as Multi-Frequency TDMA Demand Assigned Multiple Access. This allows for dynamic allocation of time slots based on user requirements and allows multiple carriers on the satellite within the TDMA network. This forms a “bandwidth pool” for the users. Major characteristics of TDMA are: Users share carrier(s) for both xmit and receive. Additional carriers can be defined to support network growth. Scales well – efficient use of valuable space resource. Supports ad hoc networking well. Bandwidth is a shared resource, not dedicated Slight delay in establishing link connection TDMA Characteristics Unique to the Linkway S2 Modem: Unique in the industry, the LinkWayS2 is a mesh MF-TDMA modem with completely independent fast-hopping transmit and receive sections. The transmit modulator and receive demodulator can each tune on a burst-to-burst basis, independently and automatically, to any of 64 carriers across an

17

800MHz frequency range spanning multiple transponders, multiple carrier rates, multiple carrier coding rates, and multiple carrier modulations. This allows the most efficient allocation of bandwidth on the network carriers, on any available timeslot on any available carrier frequency, for the most flexible and frequency agile system available

18

Defining the quality of Communications

13

Eb/N0 – Eb/N0 is defined as the ratio of Energy per Bit (Eb) to the Spectral Noise Density (No). This measurement is an important parameter in data transmission. Eb/N0 is the measure of signal to noise ratio for a digital communication system. It is measured at the input to the receiver and is used as the basic measure of how strong the signal is. It is especially useful when comparing the bit error rate (BER) performance of different digital modulation schemes without taking bandwidth into account.

19

Bit Error Rate

14

010100011?010001011000101?01010101111?0001001010111

ERROR ERROR ERROR

Bit Error Ratio – The number of bit errors that occur within a space of one second. This measurement is one of the prime considerations in determining signal quality. The higher the data transmission rate the greater the standard. In telecommunication transmissions, the bit error rate (BER) is the percentage of bits that have errors relative to the number of bits received in the transmission, usually expressed as 10 to a negative power. The Bit Error ratio calculation is the number of erroneous bits received divided by the total number of bits transmitted (e.g. 4.6x10-7 = 4.6 errors for every measured 10,000,000 bits)

20

15

RF Signal Flow

The Radio Frequency (RF) signal flow for the SNAP terminal is the same as most other RF systems. The picture above indicates transmit with the dashed line, receive is designated by a solid line. On receive, the initial signal flows from the satellite to the reflectors, then to the Low Noise Block (LNB). The LNB acts as a down-converter for the signal which is then transferred to the Outdoor Equipment Enclosure (OEE) which is located directly under the dish on the antenna system. The OEE contains both the Antenna Control Unit (ACU) and Spectrum Analyzer circuit bords and passes the signal to the pedestal where the system’s 100’ transmit/receive cable carries the signal in to the RF Equipment Case. Within this case the signal travels into the Linkway S2 Modem for demodulation and transfer into the Baseband segment of the terminal. On the transmit side, the signal begins in the Baseband segment of the terminal and is sent to the Modem via a Cat 5 cable connecting the NIPR case to the RF Equipment Case. This data is then modulated in the Linkway S2 modem into an Intermediate Frequency (IF) for transmission out through the 100’ transmit/receive cable where it connects to the antenna pedestal. The pedestal connection passes the signal up the boom to the Bulk Up Converter (BUC) which up-converts the signal to the appropriate satellite transmit frequency and amplifies the signal to the appropriate power level. From there the signal is sent

21

to the feed assembly where it is transmitted into the reflectors and sent back up to the satellite.

22

Antenna Installation

23

RF Hazards•10 Ft safety zone

Wind Loading Hazard•35 MPH wind speed limitation

•Compensations•Sand Bag placed in antenna base•Anchors

17

10 ft

Installation of 2.0 M Antenna

During the site survey, establish a safety zone a minimum 10 feet beyond the front of the feed horn and extend in an arc to 90 degrees of a center line on either side of the feed horn around any SNAP VSAT Satellite System Satellite Communications (SATCOM) device. The safety zone should be marked off to prevent others from entering the area. The operator must also keep a minimum of a 15 foot radius behind the antenna in order to avoid any electromagnetic interference. The compass and GPS antenna on the feed boom are very susceptible to magnetic interference. The operator must also ensure the direction of the positioner is faced towards the equator as marked on the positioned. This will mean the positioner will be facing due south in most situations. It is recommended that antenna assembly be performed at wind speeds under 35 MPH. At wind speeds of 45MPH or greater, the antenna should be placed in the stowed position (See Stowing Antenna procedures).

24

• 50 foot (minimum) separation between dish and fueling stations

• Unit Local policies• Approved power sources• Tripping hazards & unsafe conditions• Two-Man-Lift • Adhere to warnings and cautions

18


The satellite dish should be at a minimum 50 ft from any fueling station or high explosives. Access to all electrical power should be regulated by the respective unit’s local policies. Check the Technical guide for all approved power sources. Observe all equipment warnings and cautions indicated in technical manuals and on equipment. Identify all tripping hazards and unsafe conditions with proper identification and documentation. Any equipment over 50 pounds require a two-man-lift.

25

19

1

4

2

3

5

6


Feed Assembly – contains components for signal conditioning of TX & Rx signals Feed Boom – Supports the Feed Assembly Reflector Positioner – Positions the antenna Antenna Pedestal – Antenna support base Pedestal Legs –Supports and sustains the antenna assembly

26

20


Place the base of antenna approximately two feet from the center point of your antenna base location. The antenna base should be placed on ground that is close or equal to level. Unlock all latches and slowly lift the antenna case body upward; exposing the antenna base. Place the case body (open end up) on the flat surface; at the center point of antenna location. Lift the antenna base and position it directly on top of the case body.

27

21


Connect the legs of the antenna to each corner of the case body. The hook of the leg inserts first onto the pin located at the bottom of the case body. Once the hook is securely in place, screw the knob into the upper hole of the case body. Repeat for remaining legs. Connect struts from leg to leg, matching the colors until completion. Level the base of the antenna by twisting the knobs on the foot pedals of the legs. Watch the center setting on the base of the antenna for accurate leveling.

28

22


Place the center reflector on top of the designated channel mounts on the antenna base. Ensure that the portion of the center reflector associated with the number 1 pedal is facing directly to the rear. Screw and tighten all the knobs located on the antenna base into the reflector center section. Install all antenna pedals by matching the number of the pedal with to the corresponding number on the center reflector. The best way to install the pedals is to match from 1 to 4, individually clamping the pedals in place. Then attach pedals 7 & 8; individually clamping the pedals in place. Piece together pedals 5 & 6 with one person holding each pedal. With pedals 5 & 6 pieced together insert the assembled pedals into their respective slots on the reflector center section. Secure all pedals with secure latching clamps. Ensure all clamps are secured before proceeding.

29

23


Note: Make sure that the LNB is the correct one

Connect the antenna assembly to the boom by sliding the assembly onto the boom securely clamping the assembly. Match cable labeling with input on assembly and attach. Ensure the LNB mounted on the feed assembly is correct for the region.

30

24


Mount the feed boom to the reflector by aligning the bottom hole in the mounting bracket with the corresponding hole in the reflector mounting bracket. NOTE: Ensure the color coding of the struts match the color of the feed boom collar.

31

25


With a person on the end of each feed strut, rotate the feed boom upward while walking the struts around the edge of the reflector towards the lower connection point. Insert the 2nd captive ball detent pin into the upper reflector pivot bracket hole to secure the feed boom to the reflector. Connect the lower end of the feed strut to its ball joint by sliding back the locking collar

32

ODU Equipment

33

Wavestream Block Upconveter

27

The Block UpConverter (BUC) up-converts an L-Band frequency to a Ku Band or extended Ku Band frequency to transmit to the satellite. The Solid State Power Amplifier (SSPA) amplifies your upconverted signal to give it the power it needs to reach the satellite. The Ku-Band BUC’s Local Oscillator (LO) frequency is 12.8GHz. Ku Output range is 13.75GHz - 14.5GHz An external 10MHz is needed to provide signal stability. This is received from the 10 MHz signal generator on the front side of the RF Case

34

IFL Cable Diagram

28

Run the transmit (TX) and receive (RX) RF cables; and the antenna power and M&C cable between the indoor equipment location and the antenna assembly location. 2. Connect the antenna control cable to J1 on the positioner base. 3. Connect the red TX cable to the TX connector on the positioner base. 4. Connect the blue RX cable to the RX connector on the positioner base. 5. Connect the antenna power and M&C cable to J1 on the rear of the RF Equipment Case. 6. Connect the red TX cable to TX on the rear of the RF Equipment Case. 7.Connect the blue RX cable to RX on the rear of the RF Equipment Case. 8. Remove the 10 MHz reference GPS antenna from its pouch in the lid of the RF Equipment Case. 9.Connect the GPS antenna to J4 on the rear of the RF Equipment Case.

35

Low Noise Block Downconverter

29

Low Noise Block Down Converter (LNB) down-converts a signal returning from the satellite to an L-Band frequency for use with baseband equipment The LNB also amplifies the weak signal Easily changeable for maintenance or geographic reasons Three LNB options are available for the SNAP system to support worldwide Ku-Band 10.95 to 11.70GHz, w/ External 10MHz Ku-Band 11.70 to 12.20GHz, w/External 10MHz Ku-Band 12.20 to 12.75GHz, w/External 10MHz Signal passes through the waveguide portion of the LNB and is sent toward the baseband portion via an F-Type coaxial Connector An external 10MHz is needed to provide signal stability. This is received from the 10 MHz signal generator on the front side of the RF Case

36

RF Assembly & Components

37

31

Front Rear

1

2

3

45

6

Identify ComponentsRF Case

Satellite Modem (Linkway S2) – TDMA satellite modem RF Control Panel – Houses the antenna ODU circuit breaker, the Moxa NPort Serial to IP Converter the 10Mhz reference generator and contains input for TracStar & Phone/Laptop Storage Shelf – Houses the CF-30 laptop and IP phone Rear RF Patch Panel – Signal entry for 100 ft TX/RX cable,10Mhz Reference GPS, Antenna Control/Power Cable, and an RF-45 input for “NIPR in” Power Strip – Extra power source used for laptop and embedded kit Ground Bar – Ground all RF devices within the case

38

32

1

TX RXAntennaPower

Equipment Descriptions2.0M Antenna

Above is the interconnection from the Very Small Aperture Terminal (VSAT) dish to the Antenna Control Unit (ACU). Proper connection allows RF signals to and from the satellite and data packets to be transmitted and received. Ground – Ground wire connection point Antenna Power & Control – Provides power and control functioning from the ACU to the antenna TX – Transmit connection from RF case to antenna RX – Receive connection from RF case to antenna

39

33

modem lock indicator

Equipment DescriptionsLinkway S2 Modem

Multi-carrier, multi-rate, Multiple-Frequency Time Division Multiple Access (MF-TDMA) Satellite Modem Provides high-speed connection between SNAP remote terminals and the hub Data Rate – Up to 5Ms/s Dynamically allocates bandwidth on demand Backward Compatible with the Linkway 2100 Supports multiple network topologies (Mesh, Star or Multi-Star) Up to 256 Traffic Terminals (TTs) can be on a single carrier frequency on only a TDMA Network, under the control of the Network Master Reference Terminal (MRT) Output of Modem is “L” Band (0.950 – 1.450 GHz). All TTs and MRT use Linkway S2 and 2100 modems The MRT modem passes control bursts Controls timing and operation of all TTs in the network. Unlike TTs, does not pass traffic Without a MRT there is no Network

40

Linkway S2 Modem

34

The S2 is the connection point between your RF and Baseband side. Without Modem lock there is no end to end communication. Once the SNAP terminal attains all reference satellites and is deployed, the MODEM should have full lock. To verify MODEM lock look at the ‘SAT’ LED on the front of the modem. If there is a green flashing LED the modem has RX lock. After the Transmit Acquisition bursts have been acknowledged by the MRT and your terminal has been activated, the ‘SAT’ LED should be solid, indicating full TX & RX lock. The MODEM also serves the purpose of modulating and demodulating the data transmitted from the local baseband equipment and received from the distant baseband equipment. Through modulation the MODEM adds a carrier to the digital data suitable for transmission to follow on equipment (BUC). Through demodulation the carrier is stripped to recover the raw digital data for follow on equipment (baseband). For configuration, load parameters from a “Boot File” via a RJ45 port from a laptop or by Visual VSAT GUI. Bootfiles are to be obtained through the MRT (hub) supporting the specific mission. After a SAR (satellite access request) is approved an SAA (satellite access approval) will be granted and the POC listed on the SAA will receive the modem boot files

41

35

Front Rear

12

Identify ComponentsUninterruptible Power Supply (UPS) Case

The Uninterruptible Power Supply (UPS) system provides AC power for all baseband and RF stacks to draw power. Upon loss of external power, the internal battery of the UPS provide power to all stacks maintaining communications. On average, with all stacks drawing battery power from the UPS, communications will be maintained for about 15 to 20 minutes. Battery Compartment – Houses the external battery Power Strip – Located on the rear of the UPS rack. Provides power to all other cases within the SNAP system. Can also provide power for other devices (laptops, IP Phones, ect).

42

AVCOM Spectrum Analyzer

36

The SNAP system is equipped with a laptop based Spectrum Analyzer GUI. The AVCOM SpecAn is capable of most everything a physical SpecAn is capable of. The signal is received directly into the OEE where the Spectrum Analyzer board is located. This signal is routed through the MOXA NPORT Serial to IP converter Setting up the AVCOM Click the Configure Tab Set Connection Type to Serial 232 Set COM number to COM 9 Click the ADD button Click the Close Button

43

Tracstar Antenna Controller

37

Four Main Menus – Ready page, User Setup, Tech Page and Diagnostic page. Move through the menus by using the MAIN button for vertical movement (select one of the four Main menus) and the � key for horizontal (submenu) movement. Main-1-Ready Page: Main page displayed after powering up. From this page the user can access satellite and orbital position in degrees west longitude. Main-2-User Setup: From this page users can jog the antenna, input satellite parameters, and input the reference satellites. Main-3-Tech Setup: From this page users can run several pre-set tests. From here a user can also set the LNB parameters. Main-4-Diagnostics: From this page users can look at the antenna information such as look angles, level sensor readings, GPS data, and correction factors for the three axis.

44

Initial System Deployment

CONUS

45

Configuration of the ACU

39

From the Ready Page, Press the Main Button two times til you reach Tech Setup

Press the ENTER button til the CODE setting is flashing

Press the + button to Code 13 and press ENTER to input the Code

The configuration of the TracStar Antenna Control Unit is specific to the location in which the operator will be positioning the antenna system. When setting up in CONUS locations satellite acquisition is easier, simply because TracStar has already pre-programmed a library of reference satellites. When setting up in Europe and Asia the ScanSky function must be performed to build the reference satellite library. The ScanSky process takes a minimum of twenty minutes. During this time the antenna system is scanning the arc of the sky at different angles, peaking and frequency locking on all satellites 80 degrees from the front side of the dish. The following pages will walk the operator through the TracStar ACU procedure. The first portion will cover CONUS Setup. See the Appendix for CONUS and OCONUS quick reference guides. Firstly, the operator must set up the library of satellites known as “reference data”. When setting up CONUS there is no need to clear the reference data since the “USA REF SETUP” command automatically does this procedure. Before any configuration changes can be made the operator must set the Tech Setup Code to Code 13.

46

USA REF SETUP

40

From the Ready Page press the Main button twice to TECH SETUP (Code 13 should already be input)

From TECH SETUP Press the Arrow Button twice to SET TEST

From SET TEST Press the + button til USA REF SETUP

Press ENTER; CANCEL will now appear in the top right corner

Press + to RUN NOW and Press ENTER

Upon performing these steps the operator will be redirected to the Ready Page and a pre-programmed Reference Satellite will be input. NOTE: This data satellite may need to be changed according to your SAA.. At this time the Operator has the ability to select from a library of Reference Satellites.

47

Programming the Reference Satellites

41

From the Ready Page press the Arrow over once to SET REF SAT

Press the ENTER button until RefX is highlighted. Press the + or -buttons to select a Reference Satellite. Press Enter to select. NOTE: it cannot be the same as the Data Satellite

Press the ENTER button until RefY is selected. Press the + or –buttons to select a Reference Satellite. Press Enter to Select. NOTE: it cannot be the same as the Data Satellite

Now the operator has programmed the reference satellite. It is optimal to program reference satellites fairly close to the data satellite to ensure the line of site to the satellite. For example, if the Data Satellite annotated on the SAA is in the orbital longitude of 121W, the operator should program his two reference satellites at orbital locations such as 110W, 119W, 127W, etc. NOTE: When in CONUS locations it is perfectly fine to leave both RefX and RefY on Auto. This will simply use the compass and GPS on the antenna to pick the first reference satellite in the stored in the NVRAM.

48

Programming the Data Satellites

42

From the Ready Page, press the over Arrow two times to SET DATA SATELLITE.

Press The ENTER button to highlight SatA and use the + or – to toggle to SatA.

Press the ENTER Button til SatA is highlighted in the lower left hand corner. Using the + or – buttons input the longitudinal orbit of the data satellite. NOTE: All western satellites (CONUS) will be a positive number (121W = 121). All eastern satellites (OCONUS) will be negative (54E = ‐54).

Press the ENTER Button til SatB is highlighted in the lower right hand corner. Using the + or – buttons input the longitudinal orbit of the same data satellite.

Verify you have pressed ENTER to input all values and all settings are correct.

Now that the reference satellites have been programmed the operator must program the data satellite. NOTE: The operator must reference the SAA for this information. The operator is given the option to program two data satellites, one primary and one secondary. In most cases the mission will not call for two satellites as bandwidth must be purchased on two satellites and this is unusual. The operator must then program SatA and SatB to the same orbital longitude. Now the Data Satellite has been input. When at the Ready Screen it should read “Ready @ XXX (XXX = longitudinal orbit of the satellite).

49

Programming the Polarity

43

From the Ready Screen press the Arrow over three times to reach the Polarity Page.

Press the ENTER button to highlight the POL value

Using the + or – buttons toggle between HorzDN and VertDN

Press ENTER to input the correct POL value

Following the programming of Data/Ref satellites the operator must now program the polarity as determined by the SAA. In most cases the Polarity will be Horizontal Down (HorzDN). At this point the correct parameters for Polarity have should have been inputted by the operator.

50

Programming the Geographical Area

44

From the Ready Page press the MAIN button twice to TECH SETUP

From TECH SETUP press the Arrow button seven times to GEOGRAPHICAL LOCATION

Press the + or – button to ensure USAdvbis selected, press the ENTER button

When the LO is flashing toggle the + or –button to ensure the correct local oscillator for the us is input (10.75GHz)

Press the enter button until Fb l (frequency band Low) is flashing and toggle the + or – button to ensure the value is 11.7 GHz and press ENTER

After pressing ENTER, The Fb H (Frequency band High) should be flashing. This value should read 12.2 GHz

It is necessary for the operator to verify the ACU is set to the proper LNB Local Oscillator. If these parameters aren’t correct you will not achieve satellite lock on the ACU. By inputting these settings the ACU the dvb receiver is now programmed to correlate with the US region LNB and lock onto CONUS satellites.

51

Programming Frequency Scan Parameters

45

From the Ready Page, press the MAIN button to USER SETUP Menu.

Press the Arrow button over twice to SATELLITE PARAMETERS PAGE

Using the + or – buttons ensure SatA is selected, Press ENTER. At this point the first frequency should be flashing, using the – button ensure the frequency reads 10799, press the ENTER button and ensure the second frequency is also 10799 and press ENTER.

Press the Arrow key once to the reference satellite page and repeat the procedure above ensuring the frequency span being scanned is10799 to 10799.

When the dish begins scanning the sky in search for a strong reference satellite carrier and secondly a strong data satellite carrier to ensure maximum signal and frequency strength, it is important that before entering auto-acquisition mode, the reference and data satellites aren’t associated with a specific frequency range. This is why the system must be allowed to scan the entire frequency range of Ku-Band which is 10.799GHz to 10.799GHz.

52

Acquiring the Satellite, Deploying the Positioner

46

From the Ready Page, press Either the RUN button or hold + for 3 seconds. If outside near the ODU the operator can also press the green deploy button.

After reviewing all the steps listed above and ensuring the correct parameters are input into the TracStar handheld ACU, The operator is now ready to acquire the satellite. From the Ready Page, press Either the RUN button or hold + for 3 seconds. If outside near the ODU the operator can also press the green deploy button. After pressing the button the operator will see “STARTUP @ XXX”. This means the acquisition has begun. Throughout the entire process the operator will notice the numbers on the top left change (e.g. B21, B22, B23, etc). These are the mechanical steps of the system and are not to be taken into consideration. The next part of the sequence will read COMPASS and an associated number count (e.g. Compass -98, -99 -100, etc). If the operator were to monitor the dish at this point he or she would see the dish move in accordance with the calibration of the compass. After the compass has finished calibrating, the operator should see the GPS calibrating. The GPS will pull as many GPS satellite readings and begin passing NMEA data streams to the modem. TDMA requires constant GPS updates to synch its TX bursts. Upon completion of the GPS Calibration the operator will see the ACU begin to Scan for its first reference satellite. The AGC (Automatic Gain Control) reading in

53

the lower left hand corner will rise and fall growing with signal strength. If the ACU fails to lock onto its first reference satellite it will use the second satellite programmed by the operator. Pending successful acquisition of the reference satellite the antenna will cut directly to the data satellite programmed by the operator. The operator will notice the values in the lower right corner of the screen changing between AGC value and frequency strength value (e.g. F010799 100). Once the system has peaked in both signal and frequency strength the TracStar Handheld should read LOCK @ XXX (XXX = orbital longitude of the data satellite programmed by the operator). The System is now ready for modem bootfile configuration.

54

Initial System Deployment

OCONUS

55

OCONUS ACU Setup

48

This portion of the manual is designed for TracStar ACU configuration in OCONUS locations only. Upon setting up the SNAP system in an OCONUS (Europe/Asia) location, there are several things that must occur before the operator should begin TracStar ACU configuration. Firstly, it must be ensured that the correct LNB for the region is in use. This LNB should be NJR2637E with a local oscillator of 10.00GHz. Also upon setup the operator must ensure the front of his or her positioned is facing the equator. In Europe and Asia, as well as CONUS this is facing due South.

56

Configuration of the ACU

49

From the Ready Page, Press the Main Button two times til you reach Tech Setup

Press the ENTER button til the CODE setting is flashing

Press the + button to Code 13 and press ENTER to input the Code

The configuration of the TracStar Antenna Control Unit is specific to the location in which the operator will be positioning the antenna system. When setting up in CONUS locations satellite acquisition is easier, simply because TracStar has already pre-programmed a library of reference satellites. When setting up in Europe and Asia the ScanSky function must be performed to build the reference satellite library. The ScanSky process takes a minimum of twenty minutes. During this time the antenna system is scanning the arc of the sky at different angles, peaking and frequency locking on all satellites 80 degrees from the front side of the dish. The following pages will walk the operator through the TracStar ACU procedure. The first portion will cover CONUS Setup. See the Appendix for CONUS and OCONUS quick reference guides. Firstly, the operator must set up the library of satellites known as “reference data”. When setting up CONUS there is no need to clear the reference data since the “USA REF SETUP” command automatically does this procedure. Before any configuration changes can be made the operator must set the Tech Setup Code to Code 13.

57

Clearing the Reference Data

50

From the Ready Page, press the MAIN button twice to TECH SETUP. Ensure code 13 is selected.

Press the Arrow over twice to Set Test

Using the + or – button toggle to CLEAR REF DATA, Press ENTER

Press the + button to RUN NOW, Press ENTER

Before making any configurations or changes using the TracStar, all reference data must be cleared from the Antenna Control Unit (ACU) using the TracStar. This procedure should only be done for strategic location changes; i.e. country location. NOTE: If redeploying within the same local location, the same user data previously input into the system by the previous ScanSky should be used At this point all reference information will be cleared from the ACU. The ready page should ready “READY @ 0.0”

58

Programming the Geographical Area

51

From the Ready Page press the MAIN button twice to TECH SETUP

From TECH SETUP press the Arrow button seven times to GEOGRAPHICAL LOCATION

Press the + or – button to ensure MIDEAST is selected, press the ENTER button

When the LO is flashing toggle the + or –button to ensure the correct local oscillator for the us is input (10.00GHz)

Press the enter button until Fb l (frequency band Low) is flashing and toggle the + or – button to ensure the value is 10.95 GHz and press ENTER

After pressing ENTER, The Fb H (Frequency band High) should be flashing. This value should read 11.70 GHz

It is necessary for the operator to verify the ACU is set to the proper LNB Local Oscillator. If these parameters aren’t correct the ScanSky function which is to be performed next may not populate a correct list of Reference Satellites. By inputting these settings the ACU the dvb receiver is now programmed to correlate with the MIDEAST region LNB and lock onto OCONUS satellites.

59

Programming the Polarity

52

From the Ready Screen press the Arrow over three times to reach the Polarity Page.

Press the ENTER button to highlight the POL value

Using the + or – buttons toggle between HorzDN and VertDN

Press ENTER to input the correct POL value

Following the programming of Data/Ref satellites the operator must now program the polarity as determined by the SAA. In most cases the Polarity will be Horizontal Down (HorzDN). At this point the correct parameters for Polarity have should have been inputted by the operator.

60

Populating Reference Satellites

53

From the Ready Page, press the MAIN button twice to TECH SETUP

From TECH SETUP, press the Arrow button over to SET TEST.

Using the + or – button toggle to SCAN SKY, press Enter

Press the + button to RUN NOW, Press ENTER.

The next step in the OCONUS setup requires the operator to run the ScanSky function to build a library of reference satellites so, along with the compass, the SNAP will auto acquire and auto peak on the selected data satellite. Scanning the sky for satellites allows the SNAP ACU to acquire several references for communications. The SNAP ACU can store up to 12 reference satellites. The scan is done using the frequency bands programmed into the ACU (see Set Frequency Band procedures). When a scan is started it is best to set the TracStar control down until completion. Accidently pressing the ‘+’ or ‘-’ key can terminate the function. The scan can alternately be viewed using the built in spectrum analyzer NOTE: The operator should ensure the that the postioner is level and is facing due south before running this procedure. The ScanSky function takes approximately twenty to thirty minutes for the positioner to scan arc of the sky for the longitudinal orbits of visible satellites. When the ScanSky has finished the screen will read “OPER DONE” and revert back to the Ready Screen.

61

Programming the Reference Satellites

54

From the Ready Page press the Arrow over once to SET REF SAT

Press the ENTER button until RefX is highlighted. Press the + or -buttons to select a Reference Satellite. Press Enter to select. NOTE: it cannot be the same as the Data Satellite

Press the ENTER button until RefY is selected. Press the + or –buttons to select a Reference Satellite. Press Enter to Select. NOTE: it cannot be the same as the Data Satellite

Upon Completion of the ScanSky function a set of new reference satellites will be programmed into the reference library. At this time the operator must select two reference satellites. NOTE: When in the Eastern Region of the world note that all Eastern orbit satellites will be associated with a negative value. Once a scan has been performed to acquire reference satellites all acquired satellites can be viewed by performing the above procedures. Remember that the SNAP terminal can save up to 12 reference satellites.

62

Programming the Data Satellites

55

From the Ready Page, press the over Arrow two times to SET DATA SATELLITE.

Press The ENTER button to highlight SatA and use the + or – to toggle to SatA.

Press the ENTER Button til SatA is highlighted in the lower left hand corner. Using the + or – buttons input the longitudinal orbit of the data satellite. NOTE: All western satellites (CONUS) will be a positive number (121W = 121). All eastern satellites (OCONUS) will be negative (54E = ‐54).

Press the ENTER Button til SatB is highlighted in the lower right hand corner. Using the + or – buttons input the longitudinal orbit of the same data satellite.

Verify you have pressed ENTER to input all values and all settings are correct.

Now that the reference satellites have been programmed the operator must program the data satellite. NOTE: The operator must reference the SAA for this information. Most military satellites used in OCONUS locations are eastern orbit satellites requiring a negative value in the TracStar ACU (i.e. 4E = -4, 54E = -54, etc.) The operator is given the option to program two data satellites, one primary and one secondary. In most cases the mission will not call for two satellites as bandwidth must be purchased on two satellites and this is unusual. The operator must then program SatA and SatB to the same orbital longitude. Now the Data Satellite has been input. When at the Ready Screen it should read “Ready @ XXX (XXX = longitudinal orbit of the satellite).

63

Programming Frequency Scan Parameters

56

From the Ready Page, press the MAIN button to USER SETUP Menu.

Press the Arrow button over twice to SATELLITE PARAMETERS PAGE

Using the + or – buttons ensure SatA is selected, Press ENTER. At this point the first frequency should be flashing, using the – button ensure the frequency reads 10799, press the ENTER button and ensure the second frequency is also 10799 and press ENTER.

Press the Arrow key once to the reference satellite page and repeat the procedure above ensuring the frequency span being scanned is10799 to 10799.

When the dish begins scanning the sky in search for a strong reference satellite carrier and secondly a strong data satellite carrier to ensure maximum signal and frequency strength, it is important that before entering auto-acquisition mode, the reference and data satellites aren’t associated with a specific frequency range. This is why the system must be allowed to scan the entire frequency range of Ku-Band which is 10.799GHz to 10.799GHz.

64

Acquiring the Satellite, Deploying the Positioner

57

From the Ready Page, press Either the RUN button or hold + for 3 seconds. If outside near the ODU the operator can also press the green deploy button.

After reviewing all the steps listed above and ensuring the correct parameters are input into the TracStar handheld ACU, The operator is now ready to acquire the satellite. After pressing the button the operator will see “STARTUP @ XXX”. This means the acquisition has begun. Throughout the entire process the operator will notice the numbers on the top left change (e.g. B21, B22, B23, etc). These are the mechanical steps of the system and are not to be taken into consideration. The next part of the sequence will read COMPASS and an associated number count (e.g. Compass -98, -99 -100, etc). If the operator were to monitor the dish at this point he or she would see the dish move in accordance with the calibration of the compass. After the compass has finished calibrating, the operator should see the GPS calibrating. The GPS will pull as many GPS satellite readings and begin passing NMEA data streams to the modem. TDMA requires constant GPS updates to synch its TX bursts. Upon completion of the GPS Calibration the operator will see the ACU begin to Scan for its first reference satellite. The AGC (Automatic Gain Control) reading in the lower left hand corner will rise and fall growing with signal strength. If the

65

ACU fails to lock onto its first reference satellite it will use the second satellite programmed by the operator. Pending successful acquisition of the reference satellite the antenna will cut directly to the data satellite programmed by the operator. The operator will notice the values in the lower right corner of the screen changing between AGC value and frequency strength value (e.g. F010799 100). Once the system has peaked in both signal and frequency strength the TracStar Handheld should read LOCK @ XXX (XXX = orbital longitude of the data satellite programmed by the operator). The System is now ready for modem bootfile configuration.

66

Saving configuration to NVRAM

58

From the READY PAGE, press the MAIN button twice to TECH SETUP

From the TECH SETUP page, Press the Arrow over twice to SET TEST

Toggle the – button to SAVE EEP, Press Enter, + to RUN NOW, Press Enter.

After all reference data has been input into the ACU via the TracStar it must be saved; otherwise entered data may be erased upon any power outage or shut down.

67

ACU Peak-Up Procedure

59

In the case of low BER, low SNR, or any other symptoms of poor receive levels it may be necessary to re-peak and POL on the data satellite. The procedure for this is simple. When the system is in Run mode, simply double tap the RUN button and if done properly the operator should see “PEAK @ XXX”

68

ACU Cross Polarization Procedure

60

From the Ready Page press MAIN once to User Setup

From User Setup, Press the Over Arrow once to Jog Page, Press the Enter button and then + or – button to select JogSlow

Press the RUN button to enable Jog Mode, you will know you are in Jog mode when “JogSlow” becomes “JOgSlow”.

While in Jog Mode, press Enter to top right corner for E (elevation) and + or – to adjust. Press Enter for A (Azimuth) on bottom left and + or – to adjust. Press Enter again for P (POL) at bottom right and + or – to adjust.

:

The process of performing an antenna peaking and cross polarization, or Peak & Pol for short, is required by DISA when accessing a satellite with bandwidth leased or owned by the US Military. The Peak & Pol procedure serves two purposes. Firstly, the operator at the control segment will be able to inform the operator of the Traffic Terminal (SNAP) when he or she has reached optimal signal strength by viewing the SNAP’s unmodulated carrier on specialized spectrum analyzers. An unmodulated carrier, or carrier wave (CW), is a pure carrier without any data or modulation. Secondly, the other purpose of the Peak & Pol procedure is to ensure the Traffic Terminal is not operating on the incorrect polarity. For example, if the SNAP coming into the TDMA network is supposed to be operating on the Horizontal Polarity the feed must be rotated to match the horizontal polarity set by the Satellite. If a TT is operating on the wrong polarity, even the slightest bit, it could easily knock other customers paying for bandwidth on the other polarity out of the network and become an expensive problem. Even though the SNAP system is capable of performing a perfect Peak and Pol 99 times out of 100, it is mandatory that upon accessing a satellite using US military bandwidth, the peak and pol procedure must be performed The procedure is as follows: Open up a HyperTerminal session and login as “root”.

69

When at the # prompt, call the bandwidth provider and request to do a cross-pol check. Ask the operator for a Ku-Band frequency in Hz to bring your CW up on. NOTE: You must inform the earth station operator that your BUC Local Oscillator is 12800GHz and not the standard 13050GHz. After you have been given the frequency, and been told to bring up the carrier type this command into the HyperTerminal session: cw –power -25 –frequency xxxxxxxxxx –time 60 This can be shortened to: cw –p -25 –f (freq in Hz) –t (0 to 300 seconds). Be sure to include all spaces and dashes. If done correctly the CLI (command line interface) will echo back: “Switching LED 7 to 0” and your CW will be up for the allotted time programmed. The earth station controller will take an isolation reading, nominal isolation is 30db. From the Ready Page press MAIN once to User Setup If the operator asks you to manually jog the AZ, El, or POL, this is the procedure

70

Stowing the Antenna

61

From the Main menu Press and hold the - button for three seconds-The TracStar should read “Stowing”-

The antenna should only be stowed in cases of tear-down or excessively high wind speeds where anchoring or sand bagging does not secure the dish. Note: After deploying the Antenna, set the TracStar box down. Pressing any button afterwards will cancel the antenna deployment.

71

Loading the bootfile to Linkway S2 Modem

62

The operator must now configure the modem by loading the boot file. This is done through the Admin laptop by connecting a straight through RJ-45 cable to the Laptop/Phone on the front side of the RF Case. The bootfile should come in .txt format and should look like this: NOTE: Depending on the MRT which created the bootfile its formula may change. The operator may also receive a bootfile without “echo back” commands or command lines with the associated directory. As long as the operator is able to load the bootfile then the format isn’t an issue, however some formats may not load through the Visual VSAT GUI. If this is the case the operator will receive a “bad bootfile” notice.

72

Loading the bootfile on Linkway S2 Modem using CLI

63

1

2

3

4

COM7

115200

Open HyperTerminal on your laptop as follows: Start - Programs - Accessories - Communications - HyperTerminal The main HyperTerminal window will appear but will be inactive. The “Connection Description” dialog box will be active and will appear within the HyperTerminal window. Enter an easy to remember name in the “Name” field within the Connection Description dialog box. Ex: bootfile.txt, then Click the OK button. When the Connect To window appears, pull down the line menu in the Connect using: field. Choose the correct Com port that your console cable is connected to . Click OK. The Com port is assigned by using the NPORT Administrator and is usually set to Com 7. When the Com “X” Properties window displays, choose 115200 Bits per second and leave the remaining fields at their default setting (8, none, 1, hardware). Click OK. Once the HyperTerminal is displayed again, hit Enter a few times to trigger the communication between the Com port and the console port of the router. When prompted to login as “root” Directed to the # prompt. From the # prompt click the Transfer tab Select “Send Text File” The bootfile should appear on the screen The operator should then type “init 6” to load and reset the modem

73

Loading the bootfile on Linkway S2 Modem using Visual VSAT GUI

64

System Login window

Set the Network card on the laptop as such: IP: 10.255.255.3 SUB: 255.255.0.0 DG: 0.0.0.0 Open the Visual VSAT Application Login as Admin using “Password” as the password Ensure the display reads: COMMS: Connected ACU: Ready (green) NOTE: If there is no connectivity you cannot use the Visual VSAT to load bootfiles. Click the Network/Configuration tab

74

Loading the bootfile on Linkway S2 Modem using Visual VSAT GUI

65

Click on the Modem tab Click Load Config File Locate the saved bootfile and open the file If successful you will see the following messages from the GUI.

75

Baseband Connections

66

To Connect the Linkway S2 Modem to the Cisco 2811, the operator must simply connect a NIPR (green) straight-through RJ-45 cable from the rear of the RF case to the Gigabit 0/0 Port. The Citrix WanScaler should stay permanently connected to ports 15 (LAN) and 16 (WAN). Connect the Gigabit 1/0 port to rear of the SIPR case labeled KG CT When connecting the KG-175D ensure the red SIPR cable is connecting to the Plain Text (PT) side and the green NIPR cable is connected to the Cipher Text (CT) side.

76

Baseband Theory

77

The Concept of Networking

68

At its most elementary level, a network consists of two computers connected to each other by a cable so that they can share data. All networking, no matter how sophisticated, stems from that simple principle.

Everything we cover throughout the class is to provide connectivity from one computer to another. It may be email, web page or some other service. In each case, we are connecting one computer to another.

78

Understanding the Data

69

Data tends to exist as rather large files. However, networks cannot operate if computers put large amounts of data on the cable at one time.

- Large amounts of data sent as one large unit tie up the network

- Networks reformat large chunks of data into smaller packages in case there is an error in transmission.

Data tends to exist as rather large files. However, networks cannot operate if computers put large amounts of data on the cable at one time. There are two reasons why this slows down the network: First, large amounts of data sent as one large unit ties up the network and makes timely interaction and communications impossible, because one computer is flooding the cable with data. The second reason networks reformat large chunks of data into smaller packages is in case there is an error in transmission. Only a small section of data is affected, so only a small amount of data must be resent, making it relatively easy to recover from the error. In order for many users at once to transmit data quickly and easily across the network, the data must be broken into small, manageable chunks. These chunks are called packets, or frames.

79

The IP Address

Each Device must have a unique number to identify itself

Each number contains both the network and host information

Both the host and the network portions of an address are used to identify a computer’s location

70214.27.92.52

214.27.89.215 214.27.89.212

214.27.92.48 Network

214.27.92.53

214.27.89.208 Network

214.27.89.213

IP addresses are actually assigned to device interfaces. If a device has multiple interfaces, then there must be an IP address allocated for each interface.

80

IP Addressing Terms

NetworkIs a group of devices which share a range of IP addresses. Those addresses include a unique network address, a unique broadcast address and other addresses assignable to host devices.

HostIs any device on the network that is capable of receiving and transmitting IP packets, such as a workstation or a router. Each host must be supplied with a unique IP address.

MaskA mask is applied to the address to define which portion of the address is network specific and which is host specific. The mask is 32 bits long, and is a series of 1s followed by a series of 0s.

71

IP addressing is based on the concept of hosts and networks. A host is essentially anything on the network that is capable of receiving and transmitting IP packets, such as a workstation or a router. The hosts are connected together by one or more networks (segments). The IP address of any host consists of its network address plus its own host address on the network. Routers deliver packets to networks, not hosts. A mask is used to determine the network and host portion of an IP address. When applied to an IP address, it quite simply defines a range of addresses. The mask determines which IP addresses reside on a given network or segment. The mask is written in the same format as the IP address.

81

Network Address

• The network address is used by routers to identify and route packets to the correct destination.

• The network address cannot be assigned to a computer or host.

72

214.27.92.0 255.255.255.0214.27.92.128 255.255.255.128

214.27.92.64 255.255.255.192214.27.92.96 255.255.255.224

Network Address Examples

82

Broadcast Address

• The broadcast address is used by routers and hosts to send packets to all computers on a network at one time.

• The broadcast address cannot be assigned to a computer or host.

73

214.27.92.255 255.255.255.0214.27.92.127 255.255.255.128

214.27.92.63 255.255.255.192214.27.92.95 255.255.255.224

Broadcast Address Examples

83

IP Addressing

7474

214.27.92.48 Network Address

214.27.92.49

214.27.92.63

214.27.92.64 Broadcast Address

Hosts

214.27.92.48 255.255.255.240

Defining Network, Host and Broadcast Addresses According to Internet practices, the host-number field of an IP address cannot contain all 0-bits or all 1-bits. The all-0s host-number identifies the base network (or sub-network) number, while the all-1s host-number represents the broadcast address for the network (or sub-network). In the above example, there are 4 bits in the host-number field of each subnet address. This means that each subnet represents a block of 16 host addresses (24 -2 = 14, note that the 2 is subtracted because the all-0s and the all-1s host addresses cannot be used). The hosts on this subnet are numbered 1 through 14.

84

Baseband Components

85

76

Baseband ComponentsBlock Diagram

The Baseband equipment segment for the SNAP terminal consists of several pieces of networking equipment. The NIPR case consists of a Cisco 2811 router with a 16 port switch module and also a Citrix WANScaler. SIPR is exactly the same, except that it also contains the TacLane 175D encryption device to allow SIPR traffic to be encrypted and tunneled through the NIPR router. These terminals also come with a 3rd Baseband equipment case called the Centrix system, which is exactly the same in equipment layout as the SIPR case, but is used for Coalition forces communications at remote Forward Operating Bases (FOB).

86

77

1 – KG-175D TACLANE “Micro” Type-1 data encryptor

2 – 2811 Cisco Router Provides SIPR connectivity

3 – WANScaler Accelerator Maximizes data speeds on satellite networks

4 – SEP Signal Entry Panel to interface with the NIPR Baseband Case

5 – Ground Bar Grounds all equipment in the SIPR Baseband Case

6 – Power Strip Provides power distribution for internal and external components

Front Rear

4

5

1

23 6

Baseband ComponentsSIPR

The SIPR case is a 4 unit transit case consisting of a KG-175D TACLANE Micro, Cisco 2811 router, 16 port switch module, Citrix WANScaler, Signal Entry Panel (SEP) grounding bar and Power Strip. This system’s baseband connection passes from the KG-175D’s through to the SEP labled KG-CT where it connects out to the Fa 0/1 connection on the NIPR SEP.

87

78

1 – KG-175D TACLANE “Micro” Type-1 data encryptor

2 – 2811 Cisco Router Provides SIPR connectivity


4 – SEP Signal Entry Panel to interface with the NIPR Baseband Case

5 – Ground Bar Grounds all equipment in the SIPR Baseband Case


Front Rear

4

5

1

23 6

Baseband ComponentsCENTRIX

The CENTRIX case is identical to the SIPR case in equipment layout. The only difference between the two is where they connect to the NIPR case. Where SIPR connects to the NIPR SEP port Fa 0/1, the CENTRIX case connects from its KG-CT connection on the CEP into the GE1 connection on the front of the NIPR routers 16 port switch module.

88

79

1 – 2811 Cisco Router Provides NIPR connectivity


3 – SEP Signal Entry Panel to interface with the RF and SIPR Case

4 – Ground Bar Grounds all equipment in NIPR Baseband Case


Front Rear

12

345

Baseband ComponentsNIPR

89

Call Manager Express

90

CME Call Path

81

HUB Node

SNAP Terminal 2SNAP Terminal 1

SNAP Terminals and the Call Manager Express these are generally designated to be employed at the company level. A common misconception for the use of CME at these sites has been that it is simply there to enable intrasite phone calls during a network outage. There are actually several important reasons to have it – no need to register with a particular Hub, an independent dial plan, minimized downtime during network outages, and localization of the phone’s image file. The only path that a SNAP Terminal typically has in the network will be over a highly-latent satellite connection. By having all device registration and management functions, as well as several dial plans with routes to intra-brigade peers the SNAP Terminal has little to no reliance on an external call management device.

91

How It Works

82

Registration SCCP Registration SCCP

Call Manager Express is an IOS-based call control agent.

Several things happen during the registration of each IP phone or device. Once the phones begin power up and have an IP address, they begin to communicate with the call manager. This address is typically given via DHCP as option 150, or if manually assigned, it is entered in the field for the TFTP server. As the device is recognized by the call manager, it verifies that the phone has the correct version of firmware and then checks for an existing configuration file. If it requires firmware, it is downloaded to the phone via TFTP and the device is rebooted automatically. If it does not have a current configuration file, it is downloaded from the call manager. An additional point to remember is that Call Manager Express does not support devices on anything other than its local LAN. It is possible to get a device to register over a WAN connection, but it is not recommended to do so.

92

Configuration Steps

1. Set IP Address on Telephony Device.2. DHCP – Automatically set address.3. Turn on and Configure telephony-service.4. Create directory numbers.5. Apply directory numbers to devices.

83

93

DHCP Server Settings

84

ip dhcp pool NIPRnetwork 214.27.92.48 255.255.255.240default-router 214.27.92.49 dns-server 214.13.46.11 214.13.46.12 option 150 ip 214.27.92.49 netbios-node-type h-node

When any Cisco phone device boots, one of the first things it looks for is a DHCP server with which to get its IP settings and the Cisco Call Manager address. This is especially important to remember when a device has either been booted for the first time or has recently had a factory reset performed on it. In those cases, it is required to have both a DHCP server and a TFTP server available for the devices. The settings above are the minimum settings needed by any Cisco device in order to get it to function. “IP dhcp pool VOICE” creates a DHCP pool called “VOICE”, which is case-sensitive. The network command describes the range of addresses that will be provided to a client. The default-router points to the gateway, which in this case is also the CME router, but doesn’t always have to be the case. Option 150 is a setting utilized by Cisco to identify the address of the TFTP server to the client device. It also will be the address of the Call Manager, but again doesn’t always have to be the case. The device configuration file received via TFTP will actually have the Call Manager address which the device will use to register. The show command: sh ip dhcp binding will list any devices that have received an address from this DHCP server.

94

Telephony-Service Commands

telephony-servicesdspfarm units 1sdspfarm transcode sessions 16sdspfarm tag 1 SN-4185-NT2Rload 7960-7940 P00308000700load 7941 term41.default.loadsload 7961 term61.default.loadsmax-ephones 10max-dn 10ip source-address 214.27.92.49 port 2000auto assign 1 to 10timeouts interdigit 5system message NIPR

url authentication http://214.27.92.49/CCMCIP/authenticate.asp

time-zone 31time-format 24date-format yy-mm-ddmax-conferences 4 gain -6call-forward pattern .Tmoh music-on-hold.audn-webedittransfer-system full-consulttransfer-pattern .Tcreate cnf-files version-stamp Jan 01 2002

00:00:00

85

The above contains the settings used within telephony-service to configure the call management properties of the router. LOAD command – Specifies the devices expected and their associated firmware files. MAX-EPHONES – Sets the maximum number of physical devices allowed to be registered off the CME router. MAX-DN – Sets the maximum number of directory numbers allowed on the CME router. IP SOURCE-ADDRESS – Specifies which IP address the router should be listening for SCCP traffic off of. This is normally the IP address of VLAN 58 in the JNN system. TIMEOUTS INTERDIGIT – The amount of time, in seconds, that the system waits between dialed digits. MAX-CONFERENCES – Sets the maximum number of simultaneous conferences on the system.

95

CALL-FORWARD PATTERN – In the case of the JNN CMEs all calls are forwarded. MOH – Specifies the name of the music on hold file, stored in the root of the flash: drive. In this case it is music-on-hold.au. TRANSFER-SYSTEM – Sets the type of transfers allowed on the system-blind or full-consult. TRANSFER-PATTERN – Specifies which directory numbers are allowed to transfer active calls. A dial pattern of “.T” allows all extensions to make transfers. CREATE CNF-FILES – This command is used to automatically create the default device configuration files.

96

Ephone-dn Command

ephone-dn 1 dual-linenumber 4813850

!!ephone-dn 2 dual-linenumber 4813851

!!ephone-dn 3 dual-linenumber 4813852

!

86

This is the most basic setting available for the ephone-dn command. This command is used to create the actual directory numbers used on the system. At this point they are virtual and are not tied to any specific device. The number directly after “ephone-dn” is the tag number, which is normally sequential. The “dual-line” option is necessary for call waiting, conferencing and transfers to be enabled as this allows two virtual voice ports to be dedicated to the phone device. The number command sets the 7 digit number. Additional commands: NAME <WORD> - Used to create a free-text name that is used on both the phone and is also passed during call setup as the Caller ID Name. DESCRIPTION <display-text> - Unlike most applications of the description command, this is actually used as a header bar display along the top of the phone. LABEL <string> - Used to mark the line button on the phone device, rather than the line number.

97

Ephone Command Example

87

ephone 1no multicast-mohdevice-security-mode nonemac-address <MAC address>button 1:1!!ephone 2no multicast-mohdevice-security-mode nonemac-address <MAC address>button 1:2!!!ephone 3no multicast-mohdevice-security-mode nonemac-address <MAC address>button 1:3

The ephone command is used to associate a physical device (an Ethernet phone) to directory numbers. NOTE: If a phone has already been plugged in and is active on the system, it will automatically bind to the first available ephone number. This can be seen when a phone displays the date and time, but no directory number. The “show ephone summary” command may be run on the CLI to determine which ephone it has bound to, by MAC address. The administrator still needs to perform the above commands and type in the MAC address in order to fully register and bind a directory number to the device.

98

7961 IP Phone Reset

88

CISCO 7960/7961IP Phone

line buttons

CISCO 7940/7941IP Phone

line buttons

There will be times when your IP phone will not register with the Call Manager Express (CME). Some indications are the phone continuing to cycle, indicating that the phone is registering but never acquires an IP address (NOTE: the phone will recycle power about 2-3 times as part of the normal registration process, any more than that and there may be registration issues). Another indicator of invalid registration will be the phone locked on a boot status screen or the Cisco splash screen. In instances like these it is good to know how to reset your IP phone. Below are procedures for resetting the Cisco 7961/7941 IP phone and the Cisco 7960/7940 IP phones (NOTE: the 7961 model comes standard with the SNAP system, but others may be issued by NETOPS). There are different versions of IP Phones that may interface with the SNAP system. All reset procedures can be found at www.cisco.com. Cisco 7961/7941 IP Phone Reset Procedures: Recycle power on the phone. As soon as the phone boots press and hold the # key. Wait until the line buttons start to illuminate. Once the line buttons start to illuminate, enter the key sequence: ‘123456789*0#’. The phone will reboot and start to upgrade. Note: Do not be alarmed that the phone states ‘error’, this is a part of the process.

99

Cisco 7960/7940 IP Phone Reset Procedures: Boot phone completely Press the Menu button (oval button in lower right with square and check mark in it) From the main menu press **# to unlock the phone Press the “3” key to enter the Network Settings (may be the “2” key on some models) Press “33” to reach the “Reset Network Settings” prompt Select the “Yes” soft key Select the “Save” soft key Note: The phone will erase network settings and then reboot and reregister with the CallManager Express

100

Call Processing - Internal

89

Call Setup - SCCP

Voice Traffic-RTP

Phone A calls Phone B

PHONE BPHONE A

Call Setup - SCCP

A call sequence within one CME router is quite simple. The phone dials the requested number and the most specific match will be the directory number of the destination device. The same CME router handles the call control for both devices and then hands the call off to the devices. There are two protocols involved: SCCP – Skinny Call Control Protocol – Used primarily as the signaling method between a device and its registered call manager or between to call managers. Only used during device registration, call setup and call teardown. RTP – Real-Time Transport Protocol – Used as the end-to-end transport mechanism for applications passing real-time data, such as audio or video. Allows for time-stamping and packet sequencing to enable the devices to reassemble the packets in the correct order.

101

Call Processing CME to CME

90

Call Setup –H.323

Voice Traffic-RTP

Phone A calls Phone B

PHONE B

4315301

214.13.46.40

PHONE A

4311850

214.27.92.55

dial-peer voice 9991 voipdescription JOC Subscriberpreference 1destination-pattern .Tvoice-class codec 1session target ipv4:214.13.46.35dtmf-relay h245-signalip qos dscp cs3 signalingno vad

SNAP 3 CME

214.13.46.35

SNAP 1 CME

214.27.92.49

Call Setup - SCCPCall Setup - SCCP

When phone A goes offhook and begins dialing, the SNAP 1 CME is continually attempting to match the dialed digits with its most specific dial peer or directory number. Once the caller dials the sequence of 67273, the CME has now narrowed the possibilities down to the above dial peer. After the final digits are dialed and the requisite pause set by the “interdigit timeout”, the directory number request is immediately sent to the session target, in this case SNAP 3 CME for directory resolution. As the call is in progress between the WAN connections, the CMEs act as a sort of proxy for their respective voice devices. The RTP voice data is converted to H.323 signaling to be passed between the CME devices. Once received at the distant CME, the packet IP and UDP headers are rewritten for transmission for the device endpoint. The purpose of this conversion of RTP to H.323 is to take advantage of the QoS features inherent within H.323 such as RSVP and priority queuing.

102

Dial Peers

91

dial-peer voice 9991 voipdescription JOC Subscriberpreference 1destination-pattern .Tvoice-class codec 1session target ipv4:214.13.46.35dtmf-relay h245-signalip qos dscp cs3 signalingno vad

!dial-peer voice 9992 voipdescription SN Subscriberpreference 3destination-pattern .Tvoice-class codec 1session target ipv4:214.13.26.206dtmf-relay h245-signalip qos dscp cs3 signalingno vad

These are the two dial peers in the SNAP NIPR systems that are generic to all CMEs. Every SNAP node directs any non-matched directory numbers to the Cisco Call Manager at the JOC Hub Node. Note that both these dial peers have a “.T” destination pattern and thus any number dialed will match this peer. These dial peers and any others, for that matter, merely direct the call to the call management system that most likely contains the directory number dialed. Call completion will still follow the IP route to the actual IP-enabled device for call setup. An additional function that the default dial-peer performs does not involve outbound calls, but inbound. It ensures that the proper codec is used for call setup, which in this case is g.711. If this was not the case, there would be the possibility that an inbound number would not match one of the dial peers and would use the default “dial-peer 0” settings, which includes compression. Dial-peer 0 does not actually appear on the router configuration and cannot be modified, which is why it is always important to include a default dial-peer in your telephony configurations.

103

Dial PeersClass of Restriction

dial-peer cor customname PT-Class-Aname PT-Class-Bname PT-Class-Cname PT-Class-D

!!dial-peer cor list Css-Class-Amember PT-Class-Amember PT-Class-Bmember PT-Class-Cmember PT-Class-D

!dial-peer cor list Css-Class-Bmember PT-Class-Bmember PT-Class-Cmember PT-Class-D

!dial-peer cor list Css-Class-Cmember PT-Class-Cmember PT-Class-D

!dial-peer cor list Css-Class-Dmember PT-Class-D

92

CME offers Class of Restriction settings to restrict call capabilities. This configuration snippet configures Class A, B, C and D lines for access to different numbers. The above snippet indicates that the Class A service can dial any numbers and the Class D can only dial other lines indicated with Class D access.

104

Dial PeersClass of Restriction (2)

dial-peer voice 9991 voipcorlist outgoing Css-Class-Cdescription JOC Subscriberpreference 1destination-pattern .Tvoice-class codec 1session target ipv4:22.38.254.138dtmf-relay h245-signalip qos dscp cs3 signalingno vad

!dial-peer voice 9992 voipcorlist outgoing Css-Class-Cdescription JOC Publisherpreference 2destination-pattern .Tvoice-class codec 1session target ipv4:22.38.254.130dtmf-relay h245-signalip qos dscp cs3 signalingno vad

!

dial-peer voice 9993 voipcorlist outgoing Css-Class-Adescription Class_A to JOC (pref 1) ///DRSN///preference 1destination-pattern 312.......voice-class codec 1session target ipv4:22.38.254.138ip qos dscp cs3 signalingno vad

!dial-peer voice 9994 voipcorlist outgoing Css-Class-Adescription Class_A to JOC (pref 2) ///DRSN///preference 2destination-pattern 312.......voice-class codec 1session target ipv4:22.38.254.130ip qos dscp cs3 signalingno vad

!

93

These are the Dial Peers configured to use the Class of Restriction setting configured previously. These are very similar to standard Dial Peers, but they have a new configuration line: corlist outgoing that can is followed by the desired Class of Restriction. This line is interpreted by the Call Manager at the JOC Hub to determine what numbers the line is allowed to call, or if the phone making the call is authorized to dial that particular number.

105

Ephone-DNClass of Restriction

ephone-dn 1 dual-linenumber 4311850corlist incoming Css-Class-C

!!ephone-dn 2 dual-linenumber 4311851corlist incoming Css-Class-C


!

ephone-dn 4 dual-linenumber 4311853corlist incoming Css-Class-C



!

94

The final step in configuring Class of Restriction is to apply the CoR to the appropriate phone number by adding the corlist incoming command to the ephone-dn X config section.

106

Access Lists

107

Access List Applications

96

- Permit or deny packets moving through the router- Permit or deny vty access to or from the router- Permit or deny routing information

Packet filtering helps control packet movement through the network. Such control can help limit network traffic and restrict network use by certain users or devices. To permit or deny packets from crossing specified router interfaces, Cisco provides access lists. An IP access list is a sequential list of permit and deny conditions that apply to IP addresses or upper-layer IP protocols. Access lists filter traffic going through the router but they do not filter traffic originated from the router. Access lists can also be applied to the vty ports of the router to permit or deny Telnet traffic into or out of the router’s vty ports. You can use IP access lists to establish a finer granularity of control when differentiating traffic into priority and custom queues. An access list can also be used to identify interesting traffic that serves to trigger dialing in dial-on-demand routing (DDR). Access lists are also a fundamental component of route maps, which filter, and in some cases, alter the attributes within a routing protocol update.

108

Access List Tests

97

MatchFirstTest

Packet to interface

Deny

Deny

Permit

Permit

MatchSecond

Test

Destination Interface

No

Packet Discard Bucket

No MatchAny TestDENY ALL

No

Top Down Processing

Access list statements operate in sequential, logical order. They evaluate packets from the top down, one statement at a time. If a packet header and an access list statement match, the rest of the statements in the list are skipped and the packet is permitted or denied as specified in the matched statement. If a packet header does not match an access list statement, the packet will then be tested against the next statement in the list. This matching process continues until the end of the list is reached. A final implied statement covers all packets for which conditions did not test true. This final test condition matches all other packets and results in a deny. Instead of proceeding in or out an interface, all these remaining packets are dropped. This final statement is often referred to as the “implicit deny any” at the end of every access list. Because of the implicit deny any, an access list should have at least one permit statement in it; otherwise, the access list will block all traffic. An access list can be applied to multiple interfaces. However, there can be only one access list per protocol, per direction, per interface.

109

Standard Access Lists

98

access-list access-list-number { permit | deny } source { mask }

Router(config)#

- Sets parameters for this list entry. May be one of several statements.- IP standard access lists use 1-99- Default wild card mask = 0.0.0.0- No access-list access-list-number removes entire access list

ip access-group access-list-number { in | out }Router(config-if)#

- Activates a list on an interface- Sets inbound or out bound testing- Default = Outbound- No ip access-group access-list-number removes access

list from the interface

The access-list command creates an entry in a standard IP traffic filter list. access-list number - Identifies the list to which the entry belongs; a number from 1 to 99. permit \ deny - Indicates whether this entry allows or blocks traffic from the specified address. source – Identifies the source IP address. source-mask - Identifies which bits in the address field are matched. The default mask is 0.0.0.0 (match all bits). The ip access-group command links an existing access list to an interface. Only one access list per protocol, per direction, per interface is allowed. access-list-number – Indicates the number of the access-list to be linked to this interface. in | out – Selects whether the access list is applied as an incoming or outgoing filter. If in or out is not specified, out is the default. Note: To remove an IP access list from an interface, first enter the no ip access-group access-list-number command on the interface then enter the global no access-list access-list-number command to remove the access list.

110

Other Common ACL Applications

99

Blocking telnet access in / out vty lines

Standard ACLs can be applied to the vty lines, to permit or deny certain IPs from telnetting into, or once in, out of the router.

-- Uses the “access-class” command to apply-- Does not affect local users consoled into the router

Example:Access-list 12 permit 192.89.55.0 0.0.0.255!Line vty 0 15

access-class 12 in

Filtering routing information

ACLs can be used to limit the propagation of routing information-- Applied to the routing protocol with the “distribute-list” command-- Applied as route maps to route redistribution process

(exchanging route info from one protocol or source to another)

The basic principles of access list configuration are given in the figure. The order of access list statements is crucial to proper filtering. It is recommended to create and download your access list on a TFTP server using a text editor or to use a PC to cut and paste the access list into the router. Access lists are processed from the top down. If you place more specific tests, and tests that will test true frequently, in the beginning of the access list you can reduce processing overhead. Only named access lists allow removal, but not reordering, of individual statements from a list. If you wish to reorder or remove access list statements, you must remove the whole list and recreate it in the desired order or with the desired statements. All access lists end with an implicit deny all statements.

111

ACL Configuration Principles

Top-down processing Order of access list statements is crucialPlace more specific test statements first

No reordering / removal of statements for numbered lists

Use no access-list number command to remove entire list Exception: Named access lists permit addition and removal of individual statements.

Implicit deny all Unless access list ends with explicit permit any.

Create access lists before applying them to an interface

Access list must exist on the router before it can be applied to the interface or the user will receive an error

Access list filter traffic going through the router; they do not apply to traffic originated from the router 100

Follow these general principles to ensure the access lists you create have the intended results: Use numbers from the assigned range for the protocol and type of list you are creating. Only one access list per protocol, per direction, per interface is allowed. Multiple access lists are permitted per interface, but each must be for a different protocol. Top-down processing Organize your access list so that more specific references in a network or subnet appear before more general ones. Place more frequently occurring conditions before less frequent conditions. Subsequent additions are always added to the end of the access list. You cannot selectively add or remove lines when using numbered access lists, but you can when using named IP access lists (a Cisco IOS Release 11.2 feature). With named IP access lists, additions are still added to the end of the access list. Implicit deny all

112

Unless you end your access list with an explicit permit any, it will deny by default all traffic that fails to match any of the access list lines. Every access list should have at least one permit statement. Otherwise, all traffic will be denied. Create the access list before applying it to an interface. An interface with an empty access list applied to it allows (permits) all traffic. Access lists only filter traffic going through the router. They do not filter traffic originated from the router.

113

Verifying Access Lists

101

Commands to Verify Access Lists- show ip interface

Will show the access list applied to that interface.- show access-lists

Will show all access lists on the router.- show access-lists {access-list number}

Displays on the access list number you specify.- show {protocol} access-list {access-list number}

Will show all access lists applied in that protocol. (Normally you would use IP for protocol).

Applying access lists to the router provides a means of restricting access to particular IP addresses, protocols, etc. While working with access lists, particularly when adding or removing them, it is often necessary to perform some basic commands to verify creation, validity, etc. These are some of the commands which are useful in viewing the access lists on a router.

114

Backup/Restore Router Configuration through

Console

115

Connect to Router

103

1

2

3 4

5

Open HyperTerminal on your laptop as follows: Start - Programs - Accessories - Communications - HyperTerminal The main HyperTerminal window will appear but will be inactive. The “Connection Description” dialog box will be active and will appear within the HyperTerminal window. Enter an easy to remember name in the “Name” field within the Connection Description dialog box. Ex: Router Config, then Click the OK button. When the Connect To window appears, pull down the line menu in the Connect using: field. Choose the correct Com port that your console cable is connected to . Click OK. When the Com “X” Properties window displays, choose 9600 Bits per second and leave the remaining fields at their default setting (8, none, 1, hardware). Click OK. Once the HyperTerminal is displayed again, hit Enter a few times to trigger the communication between the Com port and the console port of the router.

116

Backup ConfigurationCapture configuration in HyperTerminal

104

1

2

3

4

Configuration backup should be a regular procedure for properly maintaining a system. To do so, Login to the router using credentials obtained from the JOC and type “show running-config” and press Enter. Press the space bar when the "-More -" prompt appears. NOTE: This command displays the active “running” configuration of the router that is stored in the RAM memory of the router. Capture the router configuration file. In the HyperTerminal window pulldown menu, click on the “Transfer” menu option, then click on “Capture Text.” When prompted, provide a path for the destination of the new file to be saved, and the new filename. Use a descriptive name of the router for the filename and use the .txt for the extension. REMEMBER the location of this file for later use. Enter the command “show running-config” at the router prompt. Press the space bar when the "-More -" prompt appears. Note: All the text that you will see appearing/scrolling on the HyperTerminal screen is also being “captured” to the text file that you created. After the “#” prompt re-appears, stop capturing the configuration file by going to the HyperTerminal pull-down menu, and clicking on the "Transfer" menu option, then click on "Capture Text." A new menu appears. Click on "Stop.“ The captured text has also been saved to the file created earlier.

117

Backup ConfigClean up Captured Configuration

105

5

7

6

Clean up the captured configuration file. Open Windows Notepad by clicking Start - Run - and type "Notepad" in the window. Press the Enter key. Once in Notepad, click on File/Open. Find the file you created from the capture in step 4` and click "Open.“ The displayed captured text will have some text that is not required for the router to read(e.g. "- More -" prompts.). The exclamation mark "!" is used in the file for user comments. Do not delete any text comments that are preceded with “!”. These comments are helpful in describing information in the text file to the user. The router will ignore any lines of text that are preceded by a “!”. Delete the lines with: “Sh run”, “Building configuration. . .”, “Current configuration. . .” Also delete each line that has the "- More -" prompt. Delete any lines that appear after the word "End“. Save the “cleaned up” version of the configuration by clicking on File/Save. Your captured file is now ready for the router to read. Close Notepad by clicking on File – Exit Make sure to save the configuration file so all the changes are updated. You now have a backup copy (.txt) file of your router’s running configuration that can be used to restore the routers running configuration or you can edit the file “offline” and then copy it to your router.

118

Change Line Delay for Config Restore

106

1 2

Loading a configuration file into a Router using HyperTerminal. NOTE: This procedure is usually done when a user needs to restore a router’s running configuration or update the router’s configuration file “offline” and then load it back into a router. Follow the directions previously for connecting to a router (Steps 1-5). Once the HyperTerminal is displayed again, hit Enter a few times to trigger the communication between the Com port and the console port of the router. In the HyperTerminal window, click File – Properties. In the Properties window that will display, click the Settings tab. Within the Settings tab, click the ASCII Setup… button at the bottom of the window. In the Line Delay field, enter 50 milliseconds . This allows for a smoother transfer of the configuration file into the router.

119

Restore Configuration

107

1 3

2 4

Login to the router and if a “>” prompt appears, then enter the Privileged EXEC mode by typing “enable” and pressing Enter and entering the password obtained from the JOC. Otherwise, you will get a prompt with a “#” contained within it and you are ready to move to step 2. Enter the command configure terminal. You will get a prompt with “(Config)” contained within it. Click on Transfer – Send - Text File in the HyperTerminal pull-down menu Browse for the backup file you are going to use. Once you choose the router’s backup file, click “Open”. Each line in the text file will be entered automatically into the router for you. Once the lines of text have been entered automatically into the router, press and hold Control-Z on your keyboard to exit global configuration mode. Then save the router’s new configuration that is currently running in the router’s RAM to the router’s NVRAM by typing the command copy running-config startup-config. Verify that the router’s configuration was saved into the NVRAM by typing show startup-config. If lines of text are displayed , then the router’s running configuration was correctly saved to NVRAM. The next time the router reboots it will use the new startup configuration file for its active configuration.

120

TACLANE (KG-175D)

121

109

Console Port

Power

CIK

OperationTACLANE Configuration

Install the CIK in the front panel of the TACLANE (Note: to load keys or make significant device settings changes you MUST use the Master CIK). Connect GFE computer to CONSOLE port on front panel of TACLANE. Ensure the TACLANE is powered on. If necessary, power-on by pressing green button on front panel of TACLANE. NOTE: There are often issues using a NIPR or SIPR imaged computer to connect to and setup the TACLANE because of device security settings, etc. Because of this it is recommended to use the laptop supplied with the SNAP terminal to access and configure the TACLANE.

122

110

123456789

OperationTACLANE Configuration – Setting PIN

Open a browser on CF-29 computer and enter the TACLANE default IP address of 172.16.0.1 to open the TACLANE GUI. Navigate to Maintenance/Security Administration/Enable SSO Privileges. The Enable Site Security Officer Privileges page will be displayed. Enter appropriate PIN (this pin should be located on the Master CIK tag, or in the upper left of the display after “Device Name”) and click YES. The menu should show SSO Enabled and icon in green. Note: 123456789 is the default PIN number for all KG-175Ds. This PIN should only be set if the device has not been previously setup.

123

111

Same IP

OperationTACLANE Configuration – Entering Local IPs

All local IP addresses will come from the user data spreadsheet. Verify all local TACLANE IP addresses before entering them into the TACLANE. Click Network ->IP Comm ->IPv4 Addresses. Enter the Plain Text (PT) and Cipher Text (CT) assigned IP addresses and subnet mask from the user data spreadsheets. PT and CT should be the same IP address. Click YES.

124

112

OperationTACLANE Configuration – Static Routes

Static Routes must be entered for HUB/MRT and all distant SNAP terminals within the TDMA network. Click Security->Static Routes->Route management. On the Static Routes screen, click CREATE

125

113

OperationTACLANE Configuration – Static Routes Cont’d

Enter values for NET ID/Prefix Length, Remote CT Address, and Remote PT Address. Click YES to save.

126

114

OperationTACLANE Configuration – Security Level

Click Operation->Security Level to enable security level. The Set Security Level screen is displayed. Select appropriate security level according to your key fill. SIPRnet will be Secret. Click YES to save

127

115

OperationTACLANE Configuration – Secure Comm

Click Operation->Secure Comm. You will receive a warning message. The TACLANE Secure Communication screen is displayed. Click Yes to enable secure communication. You will receive conformation of the communication change.

128

116

OperationTACLANE Configuration – Firefly

Click Key Management->FIREFLY Vector Set. The Manage FIREFLY Vector Set screen is displayed. Click the FILL button.

129

117

OperationTACLANE Configuration – Firefly Cont’d

Connect the Data Transfer Device (DTD). Select the desired key and send the key from the DTD. After the fill is complete, details are displayed.

130

118

OperationTACLANE Configuration – Static Routes

To verify configuration, navigate to Operation/Security Association Info/SA Table. Verify the static route is present. To verify connectivity, ping the distant end SIPR router. (This will only work if the distant end configuration is accurate and complete.)

131

Troubleshooting

132

Troubleshooting Process

• If there are issues with the SNAP Terminal, verify the followingfirst:– The SNAP system is installed on ground that slopes no more than

can be compensated for by the antenna pedestal. (NOTE: The system is validated on up to an 8 degree incline, so ensure the slope is no more than this.)

– Power is connected to the system.– All cables are properly connected and connectors are firmly seated.– Cables are not frayed or cut and do not have broken connectors or

pins.– System configurations have not changed.– The TDMA network you are trying to enter is operating correctly.

(NOTE: This information will be obtained from the Hub or NetOps.)– The proper user signals are connected.

120

To effectively troubleshoot the SNAP Terminal the operator must first have an understanding of system operations and signal flow. The procedures in this section assume the operator has been trained and understands SNAP operations. Be sure to follow proper safety procedures at all times and, if possible, do not work on this terminal alone. Ensure all operators understand how to contact medical or firefighting personnel in the event of an accident. In the event that all the above items are functioning properly then continue troubleshooting. Most issues can be narrowed down to a single unit or item, and to effectively isolate the problem the operator must understand the basic data transmit and receive signal flow of the terminal through NIPR, SIPR and CENTRIX. If necessary review section 1 for RF signal flow and section 6 for the SIPR, NIPR and CENTRIX signal flow. Identify symptoms and decide which of the components could cause those symptoms. When you suspect a component is faulty, check if it has an output. If it has an output, check it has all required inputs. If a required input is missing, follow the signal path backward and repeat the process with the previous component. If you find a component that has correct inputs but no output or an incorrect output, replace that component. Before calling Technical Support, have the following specific information ready: SNAP VSAT Satellite System number

133

Component, model nd serial number Type of software or version number/software baseline Brief description of the problem and indications Brief explanation of the steps taken to diagnose the problem

134

Troubleshooting Process Cont’d

• General Steps for troubleshooting– Identify any problems– Annotate problems– Decide what to do next– Verify equipment setup– Locate suspect components– Replace suspect components– Conduct testing– Annotate problem resolution– Prevent failures in the future

121

Identify any problems Step one is to identify the problems. Be aware of your current operating conditions. It is possible to find a potential problem and fix it before it causes a failure. Regularly check for problem indications on the front panel indicators of equipment. Perform at least daily checks of network statistics such as TDMA burst statistics and bit error rates. Regularly ask your users if their communications are operating normally. You can help minimize equipment failure and communication downtime by monitoring the system and following the preventive maintenance checks and services schedule. Annotate problems Collect any information available about the occurring problems. This step is very important and will help reduce the likelihood of repairing the wrong problem. Failures will vary, but you can ask specific questions to help with fault isolation. Keep an equipment log and record problems and how you fixed them. Recommended data to collect are: operator’s name and contact information; current date; and the make, model, and configuration of the equipment. Also record the symptoms of the problem. Describe any error messages, indicator lights, or other system information. Are the problems constant or intermittent? When did the problems start? Were maintenance procedures performed near the time the symptoms appeared? Were there any changes to operating configurations or parameters?

135

Decide what to do next Decide how to attack the problem only after collecting all the data you can about it. Safety of personnel is the primary concern during all procedures, so be sure to read and understand the safety information in this manual. Verify equipment setup Be sure the hardware and software are installed correctly and have had the proper initial settings applied. Refer to the system’s maintenance records to determine if regularly scheduled maintenance has been performed. Locate suspect components The procedures in this manual are useful in helping determine the source of faults, but in the event that they do not help then the best method to use is something called the “half-split” method of troubleshooting. This method involves assessing current system issues and using those symptoms and an understanding of the system’s signal flow and basic operations to divide the system in half. An example of this method would look like the following; after assessing the SNAP terminal and determining that there are problems with achieving a transmit lock on the modem you are able to immediately disregard the baseband side of the system because the issues will not pertain to that portion of the system. You are then able to further split the system and focus on the transmit side of the system without wasting time evaluating the LNB or receive side of the modem. With this method you have significantly reduced the number of problem areas and are now able to just focus on the systems pertaining to transmit which would be the modem, BUC and associated cabling. Replace suspect components After locating the faulty unit, replace it according the procedures in this section. Return the faulty component to the factory according to the instructions in Section 8. Conduct testing After replacing a component, test the system with normal operating procedures to be sure the problem is corrected. Be sure the symptoms are gone and that no new problems have been created. Annotate problem resolution After the equipment is repaired and back on-line, be sure to record in the system’s operating log a description of the problem and how you corrected it. This information will help future operators with their troubleshooting Prevent failures in the future Always follow the required setup and operating procedures. Always perform preventive maintenance procedures at their scheduled intervals. Do not skip any of the maintenance procedures even if the item looks like maintenance is not required. Proper preventive maintenance helps keep the equipment operating correctly.

136

122

Removal and Replacement of Feed Assembly Components

Replacing any feed assembly components requires the dish to be placed in the STOW position and power to the dish and BUC to be removed. Do not attempt to replace any antenna feed assembly components with power applied.

137

123

RF TroubleshootingVisual VSAT Access

A common problem with the Visual VSAT application is ensuring it has sole rights to the appropriate COM port for communicating to the Linkway S2 Modem and that the designated laptop has the correct IP address for COM port communication. First of all, on the laptop make sure the IP address is set to 10.255.255.3 with a Net Mask of 255.255.255.0, no Gateway and no DNS server IP addresses. Once the IP address is set, make sure that HyperTerminal is not connected to COM 7 – this is the COM port used to connect to the Linkway S2 Modem. If either of these are not accomplished before opening this application then it will display a connection error message and must be closed and re-opened after settings are made. Another indication that there are issues with the software connecting to devices are the Comms indicators under both the Linkway and ACU sections. If either of these is Red then it indicates that the Visual VSAT application cannot communicate with the device. If this occurs then the application must be closed, settings checked/changed and then the application re-opened. The Visual VSAT is an accurate troubleshooting tool. In the case where the SNAP has encountered any problems in the RF component of the system, the Visual VSAT will often provide an indication of the location of the problem by not illuminating on the specific step the problem occurred. The SNAP can be split into two sections for troubleshooting using the Visual VSAT. From ‘Startup’ to ‘Data Sat Lock’ indicates RF components. From ‘RX Lock’ to ‘Network Lock’

138

indicates problems with the Modem. Using the Visual VSAT a technician is able to narrow down what section to begin troubleshooting. To access the VisualVSAT program: Double click the VisualVSAT icon on the desktop screen of the laptop computer Click the drop-down box and log in as “Admin” with “Password” as the password. Click “Login”. The Visual VSAT Setup Screen is displayed. This screen gives you a status of the full end to end acquisition process. NOTE: While settings changes can be made to the ACU (TracStar) through this program it is NOT RECOMMENDED. Doing so will also write any other settings from within the application whether they conflict with the current settings or not. Note that the nine indicators show a series of steps. It must start at the left and go one indicator at a time to the right. Each step must be completed successfully before progressing to the next step.

139

124

Power is applied and the system is initializing.

The system has found a known reference satellite

The system has transmitted a signal to the satellite and it has been acknowledged.

The system has received a signal from the satellite. When lit, indicates that the proper satellite and network have been found.

The compass has acquired data to determine the direction the reflector is pointing.

The GPS unit has acquired data from GPS satellites and has determined the location of the SNAP system.

The system has found the data satellite.

The system has acquired the satellite and established the transport layer.

The system is transmitting and receiving on the TDMA network.

RF Troubleshooting Cont’d

The VisualVSAT status indicators . Full lock is indicated with green illumination while un-illumination indicates non-lock. This visual provides an excellent depiction of the problem at hand; narrowing down what needs to be troubleshot. For instance, in the example above, the VisualVSAT indicates that the data satellite is not locked in. This means the SNAP system has not found the data satellite. There are several things to troubleshoot: Using the TracStar, check to see if the data satellite was acquired during a scan the sky process If the data satellite was found, using the TracStar, make sure the correct data satellite was input The following steps will provide troubleshooting steps to perform for each Visual VSAT indicator.

140

RF Troubleshooting Cont’d (Startup)

125

In the case where the Startup LED is not illuminated: Check to make sure power is applied to the RF stack Check to make sure all power switches are in the ‘ON’ position Check power switches on RF case (front and back) and on VSAT Antenna Make sure the ‘Comm’ indicator is connected for both the ACU on the Visual VSAT Verify all cables are connected to proper connection ports on VSAT and RF stack Make sure COM ports are properly mapped via the Moxa Switch

141

RF Troubleshooting Cont’d (Compass Lock)

126

In the case where the Compass Lock LED is not illuminated: The VSAT terminal may be too close to magnetic interferers such as large metal or other magnetic objects. To resolve, relocate the VSAT terminal at least 10 to 20 feet from the interferer. Make sure the compass is connected and secure on the VSAT Compass data can manually be input into the TracStar handheld. If all else fails perform this step Note: Compass interference can be caused by being too close to objects which cause magnetic interference.

142

RF Troubleshooting Cont’d (GPS Lock)

127

In the case where the GPS Lock LED is not illuminated: Make sure there is no damage to GPS receiver located on antenna boom. Make sure connection from GPS to OEE is secure (J8). Note: GPS interference can be caused by being too close to objects which cause magnetic interference. GPS signal loss can be caused by obstructions to satellite line of sight; like buildings. Repositioning the GPS receiver will eliminate many GPS receiver issues.

143

RF Troubleshooting Cont’d (Reference Satellite Lock)

128

In the case where the Reference Satellite Lock LED is not illuminated: Verify that VSAT antenna is pointed in the correct direction Check the TracStar or Visual VSAT to verify correct: Reference satellite settings Polarization Frequency Bands Verify that the correct LNB has been installed on the antenna feed assembly for your specific region: Asia: USA: Europe: Make sure power is applied to LNB Verify that receive cables are securely connected on: Rear of RF case Rear of antenna base signal entry point LNB located on Antenna Feed Assembly

144

With a continuity testing device verify that all receive cables pass the continuity check Note: Anytime the boom will be lowered the VSAT must be in the STOW position and fully powered down (BUC power and Main power).

145

RF Troubleshooting Cont’d (Data Satellite Lock)

129

In the case where the Data Satellite Lock LED is not illuminated: Verify that VSAT antenna is pointed in the correct direction Check the TracStar or Visual VSAT to verify correct: Reference satellite settings Polarization Frequency Bands Verify that the correct LNB has been installed on the antenna feed assembly for your specific region: Asia: USA: Europe:

146

RF Troubleshooting Cont’d (RX Lock)

130

In the case where the Receive (RX) Lock LED is not illuminated: Verify all cables are correctly and secure on back of modem Verify correct bootfile in MODEM. Modem command: ‘ls /home/db/’ This command allows you to view the active bootfile in the modem. ‘name of bootfile.default’ denotes the default bootfile. ‘cat /home/db/’bootfile’ This command displays the bootfile contents. ‘bootfile’ = name of actual bootfile Note: It is best not to open the bootfile in NotePad as it has the potential of corrupting the bootfile. If the bootfile must be opened or modified on a Microsoft Windows computer then use WordPad instead of NotePad.

147

RF Troubleshooting Cont’d (TX Lock)

131

In the case where the Transmit(TX) Lock LED is not illuminated: Verify all cables are connected and secure on back of modem Verify that BUC power switch is in the ON position on VSAT antenna Verify there is no attenuation set on TX signal Verify that transmit cables are securely connected on: Rear of RF case Rear of antenna base signal entry point BUC located on Antenna Feed Assembly Verify correct bootfile in MODEM. Modem command: ‘ls /home/db/’ This command allows you to view the active bootfile in the modem. ‘name of bootfile.default’ denotes the default bootfile. ‘cat /home/db/’bootfile’ This command displays the bootfile contents. ‘bootfile’ = name of actual bootfile

148

Note: It is best not to open the bootfile in NotePad as it has the potential of corrupting the bootfile. If the bootfile must be opened or modified on a Microsoft Windows computer then use WordPad instead of NotePad. If problem continues to exist verify settings with HUB node.

149

RF Troubleshooting Cont’d(Satellite Lock)

132

In the case where the Sat Acquired LED is not illuminated: Verify there is no attenuation set on TX signal Check for damage on any TX components on Antenna Feed Assembly Restart the MODEM If problem continues to exist verify settings with HUB node.

150

RF Troubleshooting Cont’d(Network Lock)

133

In the case where the Network Locked LED is not illuminated: Verify correct bootfile in MODEM Restart MODEM Re-deploy antenna If problem continues to exist verify settings with HUB node.

151

RF Troubleshooting Cont’d

The components tab under the Visual VSAT also provides real time system status. Both the RX state and TX state indicators in the left menu are linked to the status of each of these functions in the Linkway S2 Modem. The status of these functions corresponds to the actual status of the Linkway S2 Modem. A green indication means the particular part of the system is good. Yellow indicates a problem with that specific section of the system.

152

135

1

2

3

4

Loading Boot File

COM7

115200

At times the boot file for the Linkway S2 Modem must be reloaded such as if the primary Modem of the SNAP terminal fails. If this is the case, then the operator must log into the secondary modem and load the appropriate boot file onto the device. This file, if not located on the laptop computer provided with the SNAP terminal can be obtained from the MRT or Regional Hub node. Open HyperTerminal on your laptop as follows: Start - Programs - Accessories - Communications - HyperTerminal The main HyperTerminal window will appear but will be inactive. The “Connection Description” dialog box will be active and will appear within the HyperTerminal window. Enter an easy to remember name in the “Name” field within the Connection Description dialog box. Ex: Router Config, then Click the OK button. When the Connect To window appears, pull down the line menu in the Connect using: field. Choose the correct Com port that your console cable is connected to . Click OK. When the Com “X” Properties window displays, choose 115200 Bits per second and leave the remaining fields at their default setting (8, none, 1, hardware). Click OK. Once the HyperTerminal is displayed again, hit Enter a few times to trigger the communication between the Com port and the console port of the router. Select Send text file Change txt to all files

153

Select boot file from desktop Hit enter After screen scrolls through, there should be 3 checksums displayed, make sure all 3 match. Type in hw, hit enter

154

IP Phone Not Transmitting

136

155

VSAT Not Transmitting

137

156

Common Device Commands

157

Common Linkway Commands/Information2100 COMMAND LWS2 COMMAND DEFINITION DESIRED RESULT9600 115.2 K (115200) Baud rate for consoling Will be able to console in

"" (blank) root Login Will be logged into the device as Administrator

ttelnet logs into UNIX shell COSMIX Password will load - Hit Enter (password is blank "")CTRL-C (gets # prompt) takes you from UNIX shell to Hardware console A "#" sign will appearnetstat -r routing table Can diagnose problems with LinkWay routing

show_ber show_ber Raw BER statistics of all received bursts 1X10-3 to 1X10-7 BER - Can get each Terminal in meshes HEX LW ID

rb rb Receive Burst Statistics0 CRC Errors - used show_ber to get Hex LW ID and you can determine the numerical ID

rt rt or rtprt IP Route IP address for local and all remote modems should be present

ping X.X.X.X -i 1 -t 2000 -n 4 ping X.X.X.X -i 1 -t 2000 -n 4

Ping IP address of distant end modem, -i 1 directs the modem to use interface 1, -t 2000 holds the ping up for 2000 milliseconds, and –n 4 repeats the ping 4 times.

Ping response is successful Can be -I 0 based on the interface you are using, MRT, HUB or STT

rx rx Receive Statistics Modem in receive synched. (RX SYNCH)tx tx Transmit Statistics Modem is transmit synched (TX SYNCH)

tc tc Terminal Configuration

Most important field is Tx Power, should match planned power level. Console field shows power level of 0 to – 60, divide the reading by 2 to calculate actual level.

dbpr siteconf Site ConfigurationLat/lon should match position as read by the ACU, if not notify the MRT operator of current position.

hw reboot Hardware Reset Modem will reboot

dbset termconf txpower –XX termid 0x0XXX

Set transmit power on the modem in case baseline config is too low to achieve transmit synch, -xx is the new power level, 0x0xxx is the terminal ID (boot file number) for your terminal. To increase power by 1 dB, increase the tx power level by 2.

cacmodeminfo cacmodeminfo ODU (Outdoor Unit) Configuration LNB Power and Reference should be off, BUC power should be off.

caclnbpower on caclnbpower on Enables 18 VDC output on the modems Rx port to power the LNB. Should only be used in case of equipment failure.

caclnbref on caclnbref onEnables 10 MHz output on the modems Rx port to provide an external reference to the LNB. Should only be used in case of equipment failure.

cw -freq xxxx -pow xx (power level in dBm i.e.-14)

cw -freq xxxx -pow xx -t xxx(powerlevel in dBm i.e.-14, -t time in seconds)

Continuous Wave (clears when time runs out or with hw, reboot or LWS2_Stop and LWS2_Start commands) Modem will transmit a continuous wave signal. Freq is L-band (i.e. 1140000000)

dbpr ipifconf dbpr ipifconf Shows Modem IP conficuration received from the MRTDisplays LW IP address, if system is online address should be one less than router address on port F0/1

Common Linkway Commands

158

Common Router Commands

Command Description When to use

sh ip interface brief Shows interface name, IP addressing and statusVerify up or down status of interfaceVerify interface IP address

sh ip ospf neighbor Shows status of ospf neighbors Verify connection to distant end routers

sh ip routeShows known paths to other routers, how paths are known and source of the path Verify OSPF is updating path information

sh interface fa#/#(i.e. router: fa1/1switch: fa1/0/1)

Show detailed information about a specificinterface

Check access lists applied to an interfaceCheck connectivityCheck IP address and subnet mask

sh environmentDisplays temperature, fan status and otherdevice environmental information Check device temperature for overheating

sh access‐list Display all access lists on the deviceVerify access lists are in routerCheck if a user or network is being blocked

sh run Shows running configuration of deviceTo backup configurationVerify all currently used device settings

140

159

Common CME Commands

141

Command Description

show ephone shows detailed information about all registered telephony devices

show ephone summary shows summary information – useful for getting MAC address info.

show telephony-service shows current CME-related configuration info

show telephony-service all Shows more detailed information related to CME

show dial-peer voice summary Shows all configured dial-peers, to include ephone-dn

show voice call active brief shows all calls in progress

Above are some basic show commands which are very useful in troubleshooting IP phone problems. These commands are issued from the command line of the router and show various pieces of information about the phones, their status, registered phone number, etc.

160

Preventive Maintenance

161

UPS Maintenence

143

The SNAP VSAT Satellite System is designed to withstand wear and never degrade performance below specifications, to ensure peak performance and operability of the system, perform basic preventative and routine maintenance procedures. These actions will keep the system running efficiently and will help prolong the life and overall operability of the equipment. Properly store all cables for the Sub-system in the transit case. Never twist any of the cables when assembling, disassembling, or storing the Sub-system Ensure case lids are securely fastened for storage and transport to ensure lid and case deforms the same

162

SIPR Maintenance

144

163

NIPR Maintenance

145

164

Subsystem Maintenance

146

165

Satcom Definitions

166

Satcom Definitions

• Azimuth- Azimuth is just another name for direction. Azimuth is an angular measurement made in the horizontal plane. It is usually measured in degrees. You must have a correct azimuth when pointing a dish to find the satellite. Magnetic compass North will vary from true Azimuth north by the value of declination.

• BUC-Block Up-Converter- The BUC converts the L-band frequency to a higher frequency. It can be converted to Ka, Ku, C, or X band. In the SNAP system it converts it to Ku band for transmission to the satellite. The BUC also amplifies the signal to give it the power it needs to reach the satellite.

• Declination- Declination is the difference between magnetic North as reported by a compass and true North. It is very important to know when plotting your azimuth. If you have a West declination, you must subtract it from your compass reading to determine the true azimuth. If you have a East declination, you must add it to your compass reading to determine the true azimuth.

• Downlink-The signal from the satellite to the ground station.

• Elevation- Elevation is the height of an object above a fixed reference point. It is usually measure in degrees. In satcom, it is important to know the angular measurement of the satellite above the horizon.

148

167

Satcom Definitions

• FEC-Forward Error Correction- FEC is a type of error correction used in satcom equipment. It works by adding check bits to the outgoing data stream. Adding more check bits reduces the amount of available bandwidth, but this allows the receiver to detect and correct errors without the need to ask the sender for additional data

• Feedhorn- It is the part of the antenna that gathers the reflected signal from the dish and focuses it to the LNB.

• GPS-Global Positioning System- GPS is used by the terminal to determine it’s position on the Earth in latitude and longitude.

• IFL-Intra-Facility Link. The IFL refers to the cables that run between the IDU (indoor unit) and the ODU (outdoor unit).

• LNB-Low noise block converter- The LNB converts the higher frequency received from the satellite back to an L-Band frequency for use in the baseband equipment. It also amplifies the weak signal received from the satellite.

• Uplink-The signal from the ground station to the satellite.

• VSAT-Very Small Aperture Antenna- A VSAT is a two-way satellite ground station with a dish antenna that is smaller than 3 meters.

149

Documents

Table of Contents - Noodlez.org Courses PDF Student Guides... · 1-Centrix Cases 2811 Cisco Router CITRIX WAN Accelerator KG-175D-TACLANE 1-Spares Case 3 – Spare LNBs 1 – Spare