Table of Contents - Noodlez.org Courses PDF Student Guides/Master Reference...– Reference (RB) –...

Table of Contents

Chapter 1 Linkway Overview Chapter 2 Linkway Principle of Operations Chapter 3 TDMA Network Configuration Chapter 4 Configuration Chapter 5 Generating Boot Files Chapter 6 Troubleshooting and Maintenance Chapter 7 Adding Control Groups

TAB

Insert Tab # 1 Here

Linkway Overview

3

Terminal Equipment (1)

Patch PanelEthernet

SwitchNMS Computer

Linkway TDMA Modem -MRT

Backup Linkway TDMA Modem - AMRT

KVM Switch

NCCKVM Terminal

ANCC

Power Distribution Panel

The NMS/NCC terminal equipment stack consists of several components. At the top of the stock is a signal patch panel, used for testing and integration of signals within the network. Below the signal patch panel is an Ethernet switch, which provides connectivity for network devices, which utilize an RJ-45 connector. Underneath the Ethernet switch are two Linkway modems, either 2100s or S2s. The uppermost Linkway serves as the designated MRT, while the lower Linkway is AMRT. In the example above, they are both Linkway 2100s. Beneath the Linkway, modems are the systems used in operating and configuring the NCC and the ANCC. The first is a KVM (Keyboard-Video-Monitor) switch, which connects to the NCC, followed by the NCC itself. Below these devices is a second KVM switch, and the ANCC. The lowermost component of the stack is a power distribution panel.

4


• Patch Panel– Provides a means to route signals between units within the

terminal and to transmit/receive RF.

• Ethernet Switch– Layer 2 (Ethernet) aggregation point for the MRT sub-system.

• NMS Computer– Network Management System (NMS) Computer is the principle

administrator interface with the Network Control Center (NCC).


• Linkway TDMA Modem– Primary TDMA modem. This is the MRT.

• Backup Linkway TDMA Modem– Secondary TDMA Modem - AMRT

• KVMSwitch– Allows operator to select screen display on KVM between NMS

Computer, NCC or ANCC.• Position 1 = NCC• Position 2 = ANCC• Position 3 = NMS

• NCC– Network Control Center. SUN server that acts as the centralized

control point for the Linkway Network.

5


• ANCC– Alternate Network Control Center. This server acts as a

backup to the NCC.

• Power Distribution Panel– Routes power to the units mounted in this equipment rack.

Provides surge protection.

6

Linkway IP Modem

• Multi-carrier, multi-rate, TDMA Modem• Up to 256 carriers can be supported in a Linkway network.• All carriers on a transponder can be shared by all users dynamically

on demand.• Accepts IP inputs via 10baseT, 8-pin RJ-45 jack.• Maximum input data rate is 3 Mbps duplex.• Output is a L-band carrier at 5 Msps bandwidth.• TT Linkway IP modem and MRT Linkway IP modem are identical

with the exception MRT Linkway IP modem is used by the NCC to communicate with all other Linkway terminals in the network and does not carry traffic.

The Linkway IP Modem is a multi-carrier, multi-rate TDMA modem. It routes traffic within the network in which it is configured using IP addressing. Unlike the IP-capable, devices, which you may be more familiar with, the Linkway modems’ IPs, are not propagated throughout the rest of the data network and the internet. Instead, data from the Linkways is routed within a closed Class A IP address. This IP address will vary depending on how the terminal was configured at the NMS. Since the Linkway modem transmits a TDMA signal, all Linkways within a network share the satellite bandwidth allocated to that network. Rather than having a static set of frequencies on which to transmit, Linkways instead dynamically acquire bandwidth from the pool that the network has been allocated. An MRT (or AMRT) is essentially the same as a Linkway found on an STT, SPOP, or SNAP, with the exception that it does pass traffic as these terminals do.

7

Network Control Center (NCC)

• Central control for the Linkway network.• NCC software is installed on a single rack unit Sunfire™ V120

server.– UltraSPARC™ IIi 650 MHz processor.– 512 MB RAM– 36 GB hard drive– Full color video card– DVD/CD combo drive

• Also acts as a web server to accept NMS commands.• Communicates with the Linkway IP via layer 2 through the Ethernet

Switch.

Network Management System (NMS)

• Web based, used for monitoring network status and performance, and for performing modifications to the network. NOTE: LINKWAY OPERATING SOFTWARE PRIOR TO RELEASE 6.0 MUST USE NETSCAPE VERSION 4.79 IN ORDER FOR THE NMS TO FUNCTION.

• Primary interface is using MS Windows IE browser

• Installed on an external laptop.

• Principle administrator interface with the NCC.

8

Typical Linkway Network

• Master Reference Terminal (MRT) – Controls network timing and resource allocation. DOES NOT CARRY NETWORK DATA.

• Traffic Terminal (TT) – Interface between terrestrial and TDMA network.

• Alternate MRT (AMRT) – Backup terminal for the MRT. DOES NOT CARRY NETWORK DATA.

• Supports Star, Hybrid, and Mesh Topologies.

A typical Linkway network consists of an MRT, an AMRT, and a number of Traffic Terminals. The AMRT serves as a backup to the MRT if it should fail for any reason. As previously stated, neither the MRT nor the AMRT actually passes traffic. A Linkway network can be configured as a star, hybrid, or mesh topology, all of which will be explained in more depth in the following sections.

9

Star Topology

• Central hub with many remotes.• Remotes can only communicate via the hub.• Hub is usually assigned to administer the network.

Hub2 or more Linkway Modems

The Star topology is the most basic of topologies. In this topology, also known as a “Hub and Spoke”, each Traffic Terminal within the network is only communicating through the MRT or AMRT. Individual terminals do not communicate directly with other in this topology, only with the MRT. The disadvantage of this topology is that all traffic must be processed through the MRT, which can possibly cause congestion within the network.

10

Mesh Topology

• Many terminals, no centralized hub location.• One or two terminals assigned to administer the

network.• This topology resembles a Brigade’s JNN architecture.

Hybrid Topology

• Consists of two or more hubs.• Provides mesh connectivity between hubs.• Terminal must communicate through a hub.

Hub

Hub Hub

11

Redundancy Options

• The MRT and AMRT when located together is known as Local Redundancy.

• When the MRT and AMRT are located at separate sites is geographic redundancy.

• Push package employs local redundancy.• MRT and AMRT are peers.• Alternate is not a hot spare.• Upon MRT failure, the NCC will command switch to

AMRT.• When MRT recovers, there is not an auto switch back.

Local Redundancy Example

• In normal operations the NCC is controlling the network, NCC and ANCC are peers.• The ANCC is updated with any network changes via a database update from the

NCC every 7 minutes.• The NCC/ANCC are continually pinged by each other to ensure operation.• If no ping response, ANCC verifies switch function than assumes control of the

network.• When NCC recovers, switch back does not occur.• NOTE: Having two active NCC’s on one network will result in network failure.

MRT

AMRT

NCC

ANCC

L-band Com

biner

Ethernet Switch

12

MRT System IP Addresses

Each TT must be on an individual sub-net examples:

TT-1- 10.1.3.1TT-2- 10.1.4.1TT-3- 10.1.5.1

Set per Cut Sheet

NMS(10.1.1.5)

NCC(10.1.1.2)

ANCC(10.1.1.3)

Ethernet Switch(10.1.1.1)

MRT(10.1.1.4)

AMRT(10.1.1.9)

• The JNN subnetmask is 255.255.255.248 to allow 6 useable hosts per TT (or MRT/AMRT) modem.

• The MRT is used for power balancing and pinging.

• The AMRT is used for pinging.

13

Questions?

TAB

Insert Tab # 2 Here

Linkway Principle of

Operations

16

Bursts

• The Linkway network uses a series of bursts to establish/maintain timing and to pass data.– Reference (RB) – Carries NCC commands and timing feedback

to the network and establishes receive timing.– Acquisition (AB) - From TT’s to the NCC to establish network

timing, only used when a TT enters the network.– Control (CB) – From TT’s to the NCC to update the NCC of TT

status, the NCC uses this burst to maintain timing, and updates the TT’s during the next RB.

– Signaling (SB) – TT bandwidth requests to the NCC. Also known as Aloha bursts, a TT can transmit at any time. May result in collisions. In the case of collisions, MRT will resettiming and TT’s will again access network at random times.

– Traffic (TB) – Data carrier from TT to TT.

17

Bursts Example (1)

• NCC establishes the network via the MRT.– MRT transmits RB.– MRT receives original RB.– NCC uses time between RB

transmit and receive to establish network timing and synchronization.

NCC

MRT

RB

RBBursts Example (2)

• NCC begins TT synchronization via the MRT.– MRT transmits RB.– TT’s receives RB and

establish timing reference.– TT’s read RB to establish

AB assignment.– TT’s continue to receive RB

every frame to maintain timing reference.MRT

NCC

RB

RB

RB

RB

TTTT

TT

RB

18

Bursts Example (3)

• After TT’s are receive synched they must become transmit synched to enter the network.

– Each TT has been assigned a specific AB burst time to prevent collisions.

– AB’s have an impact time window of 40,000 clocks to allow for timing error.

– NCC via the MRT sends RB containing timing corrections to specific TT.

– A TT is considered transmit synched when it sends 3 AB frames at exact correct clock.

MRT

NCC

RBAB

AB

AB

TTTT

TTAB

RB

RB

RBRB

Bursts Example (4)

• After a TT has achieved network synch, AB is no longer used, TT’s now transmit CB.

– Each TT is assigned a specific control frame ID.

– CB contains TT status and bandwidth reporter message.

– MRT receives CB and measures timing and frequency

– NCC sends corrections to TT’s. Corrections keep TT’s synchronized with

MRT

NCC

RB

CB

CB

CB

TTTT

TT

CB

RB

RB

RBRB

19

Bursts Example (5)

• When a TT needs more bandwidth to send traffic it sends a SB to the MRT.– SB’s are Aloha Bursts

and subject to collisions.

– If a TT does not receive a burst assignment to send traffic, it sends the request again on a SB.

MRT

NCC

RBCB

CB

CB

TT

TT

TTCB

RB

RB

RBRB

SB

SB

Bursts Example (6)

• TT’s transport data from site to site using traffic bursts.

– In smaller networks only carrier “0”, is utilized.

– As network demand increases, additional carriers may be added with the proper approval.

– Additional carrier enlarges the bandwidth pool that is assigned as needed.

MRT

NCC

RB

CB

CB

CB

TT

TT

TT

CB

RB

RB

RBRB

TB

TB

20

Questions?

TAB

Insert Tab # 3 Here

TDMA Network Configuration

23

Terms to Know

• Hyper Terminal – A protocol that allows a computer to function as a terminal working from a remote computer.

• FTP - A communications protocol governing the transfer of files from one computer to another over a network.

• Boot File – As pertains to Linkway; the file that contains the operating parameters of the modem; the file is loaded into the modem during boot. Typical Information in a boot file includes data about transmitting, receiving, symbol rate, forward error correction (FEC), terminal id, and a few other parameters.

Step by Step Startup

NOTE: The following assumes the antenna has been peaked and polled on the satellite.

• Configure Network and generate boot files.• FTP boot files from NCC to NMS. NOTE: The boot files will have to be

transported to the TT sites via e-mail, memory stick or some other means.

• Telnet into the Linkway modem.• Load boot files.• Access the satellite per operator’s instructions with CW.• Verify network performance, MAINTENANCE.

24

Starting the NCC (1)

• On the NCC log into the Sun server as user: linkway.• Open a terminal window.• At the prompt type: ncc_start<enter>• Start the ANCC only AFTER all configuration is

complete.• After any changes to the NCC database, the NCC

must be restarted for changes to take effect.

Starting, stopping, or making changes to the NCC can also be accomplished remotely via Telnet or another remote access client such as PuTTy. While the interface is not as user-friendly (there are no icons, nor is the mouse enabled), it remains an option for remote access. To connect to the NCC remotely, first Telnet to its IP address. Next, login normally as user linkway. From the linkway user prompt, continue as above.

25

Starting the NCC (2)

• To verify the NCC is running, in the terminal window type: ncc_stat<enter>

• You should see the following:

[NCC:~] ncc_stat

ProcessPIDLINKWAY NCC 471LINKWAY SNMP Subagent 402LINKWAY NCC Support Process 340NMS Server 401Web Server process(es) 269 270 411 412 409

[NCC:~]

26

NMS (1)

NMS (2)

• In addition to NCC processes, a web server also runs on the active NCC.

• Providing connectivity exists, any web client requests may access the NMS via a web browser.

• Primary interface for system administration and day to day operation.

• In Linkway 6.0 and greater the NMS can not control the MRT untilthe MRT is in the network.

• If there is a change in status (whether operator change or database change), the NMS screen needs to be refreshed to view the changes.

27

NMS Login

• To browse to the server enter the IP of the active NCC, with :30000 at the end.– Example: http://10.1.1.2:30000 for the NCC.

• ANCC will not support NMS processes unless it becomes active.• Enter User id: linkway• Enter Password: linkway• Click the Submit Login button

NMS Login – The NMS Login is the web-based, Graphical User Interface (GUI) to the NCC. It provides a visual, “point-and-click” configuration option for each Linkway network segment, as well as a variety of diagnostic tools and views. Since the NMS is located on the NCC, the NMS cannot be used on the ANCC unless the NCC has failed and the ANCC has taken control of the network. Since the NCC and ANCC have separate IP addresses, it is important know which one is in control of the network, as only the IP address of the active NCC will allow the NMS to connect.

28

NMS Main Screen

MenuButtons

NCC Connection StatusUp = GreenDown = Red

Network Admin StatusEnabled = GreenDisenabled = Red

MRT IDMRT Always 120

AMRT Always 140

Terminal StatusActive = GreenInactive = Red

Network Admin Status – This display shows the level or privileges available to the user currently logged into the NMS. If the user has admin privileges, this will be green. If the user can only view the NMS’ configuration, but not make any changes, this will be red. NCC Connection Status – This displays the status of the current connection status to the NCC. Please note that if the connection between the NCC and the NMS is lost, then restored, the Connection Status indicator will continue to display red. Before the NMS will recognize the restored connection, the web interface must be refreshed. Ref. Terminal ID – The reference terminal ID shows the terminal ID (in hexadecimal format) of the reference terminal currently acting as the MRT. If the primary MRT is controlling the network, then this will display “0x00000120”. If the MRT passes control of the network to the AMRT, this will display “0x00000140”. These hexadecimal values are always applied to the MRT and the AMRT and will not change regardless of network configuration.

29

Terminal Status – These indicators show the terminal status of the traffic terminals within the Linkway network. Depending on the geographic coordinates entered for each terminal during initial configuration, they will also display an approximation of the terminal’s location. Please note that if terminals are co-located, the first terminal will be displayed at the correct location, and all succeeding terminals will be displayed directly to its right. In the screen capture above, for example, the NMS is monitoring six terminals co-located in central Georgia, as indicated by the terminal on the far left. Menu Buttons – These provide a graphical user interface (GUI) to access the Linkway network’s configuration and management functions.

30

Network Status

• Accessed from main screen Network Status button.

• Lists Terminal ID, Terminal Names, Status, and Alarms for every terminal configured in the network.

Network Status – The Network Status screen provides a list of Terminal IDs within the network and information about those terminals, specifically their names, transmit/receive status, and alarms. While the Network Status screen can be accessed from the main NMS screen, it will also appear as a pop-up if a terminal experiences a change in status or alarm state, but only if the NMS is currently connected to the active NCC. A terminal’s status will only appear as “Up” once it has successfully synced with the MRT.

31

Network Status – Event Log

• Lists all events logged in the NCC since last reset.

Network Status – Event Log – Any event, such as a status change or alarm within the network, will appear in the Event Log. The Event Log will record every event that occurs on the network since the NMS was started, or since the last reset of the Event Log itself. To clear the Event Log, click on the “Reset” button on the bottom of the Event Log screen.

32

Configuration

• Accessed from main screen Configuration button.

• Primary interface to make any changes to the network. More on this later in the lesson.

Configuration – The Configuration screen is the top menu for making changes to the Linkway network via the NMS. Via the Configuration screen, almost any value within the Linkway network can be altered. Each segment of the Linkway network is represented by a further menu selection within the Configuration menu, allowing for easy access to each.

33

Burst Time Plan

• Accessed from main screen Burst Time Plan button.

• Displays current burst time plan.

• Updated real time.

The Burst Time Plan The burst time plan is a graphical representation of bursts, and thus traffic within the network. Since each burst on the TDMA network is approximately 28 ms in duration, each individual burst cannot be displayed. The burst time plan is therefore only a rough approximation of traffic, and should not be taken as completely accurate. It does, however, serve as a useful guideline in determining what traffic is going over which carrier, and to which degree, since each individual burst (represented as a colored bar) corresponds to a different kind of burst. The key for the colors of burst are located in the lower-right hand corner of the screen when the burst time plan is displayed. Located on the left hand side of the screen are the carrier IDs for each carrier within the network. Carrier IDs begin with Carrier 0 (on which all network administrative bursts, such as reference and signaling bursts, are displayed), and typically continue in sequential order.

34

Diagnostic Tests

• Accessed from main screen Diagnostic Tests button.

• Primary interface to run tests on the system.

• Tests can be selected via a pull down menu, or by typing the command in the command line.

Diagnostic Tests – The Diagnostic Tests screen provides a variety of tools to assess the health and functionality of the Linkway network. While all the test commands can be entered directly into a Linkway modem, the Diagnostic Tests screen provides a GUI that allows the NMS operator to quickly and easily enter these commands into any Linkway currently synced with the network. The default terminal ID in the “To Terminal” dropdown box in the upper portion of the screen is “0x00000120”, which is the terminal ID of the MRT. However, by changing the terminal ID in the “To Terminal” dropdown, the same diagnostic commands can be sent to any terminal currently synced with the MRT. The result of these tests will be the same as if they were entered locally at the distant end. Obviously, if a terminal is not synced with the MRT, these tests cannot be performed from this screen.

35

User Admin

• Accessed from main screen User Admin button.

• Primary interface to view, delete, or add users.

Operation

During setup of the MRT the following major steps shall be accomplished.

1.Power-up the MRT2.Perform Space Segment Configuration3.Perform Site and Terminal Configuration4.Perform IP Configuration5.Generate Boot Files6.Load Boot Files7.Synchronize Database8.Access Satellite9.Enter Network10.Verify Modem Performance

36

Power Up the Equipment Rack (1)

1. Inspect the Power Distribution unit and insure the main power switch is in the off position and that all of the rack elevation rocker positions are in the off position (lower half depressed).

Main Power SwitchRack Elevation Rocker Switches


2. Locate the power cord in the rear of the equipment rack and plugit into a convenient 110 VAC outlet in the center section of theSTT.

3. Connect STT ground strap to MRT Package ground block.

4. Position the main power switch on the Power Distribution Unit (PDU) to the ON position.

5. Place each rocker switch to the on position (top half depressed).

6. Power up the NMS computer.

37


7. Power up the NCC and the ANCC by closing the power switch located on the back of the unit.

8. Using two people, slide the rack into the center section of the STT.

9. Right-click on the NMS computer control pad. A window will appear at the approximate position of the cursor.

10. Navigate from this window as indicated below through Graphics Options to Dual Notebook and Monitor.


11. Open the KVM terminal.12. Select position 1 on the switch panel. You will see the Welcome to

NCC Screen after the units completes power-up.13. Enter linkway for the User Name.14. Enter datapath1 for the password. Note that the cursor will

remain stationary while the password is being entered, this is normal.

15. The screen will display a navigation banner across the bottom after a successful logon.

16. Hover the cursor over the various icons and examine the names of each selection group. Hover over the group titled Hosts, then select This Host. A new window will display.

17. Start the NCC by typing the following command; ncc_start.18. Press enter.

38


19. Monitor status of the NCC as it starts by entering the command ncc_stat, then press enter. A two-column response display will appear. Repeat this command every minute until each Process ID (PID) in the right-hand column has a number assigned. This indicates that the NCC is up and operational. DO NOT START THE ANCC UNTIL ALL CONFIGURATIONS ARE COMPLETE.

20. Select position 3 on the switch panel. This will result in the NMS being displayed on the KVM.

21. Double-click on Internet Explorer. A screen will appear that requests a username and password. NOTE: ENSURE THE ADDRESS FOR THE APPROPRIATE NCC IS ENTERED IN THE ADDRESS BAR OF INTERNET EXPLORER.

22. Enter linkway for the username and password. The screen shall change to NMS Main Screen.

39

Questions?

TAB

Insert Tab # 4 Here

Configuration

42

Space Segment Configuration (1)

• From the Configuration screen– Click Space Segment

Configuration


• Click on Satellite Parameters

• Click the OK button.

43


• Name Field: Enter the name of the satellite.

• Nominal Longitude: Enter the orbit longitude of the satellite. NOTE: Degrees East

– The NCC will use this information to calculate system timing.

NOTE: If Longitude is in degrees West, subtract from 360 with the result in degrees East.

• IF Loop: Pull down menu.– Yes – IF Loop enabled– No – Normal operations– If IF Loop is changed, NCC must

be stopped and restarted and L-band carrier transmit and receive frequencies must be the same for an IF loop.


• All terminals should be in Control Group 0.

• Adding additional control groups is an advanced topic covered later in this lesson.

44


• Click on Carrier Administration


45


• Enter carrier data from cut sheet.• Carriers 1 – 254

– Can be added or deleted from the NMS– Does not require the NCC to be stopped

and restarted– CAN NOT BE EDITED, MUST BE

DELETED THEN ADDED TO CHANGE AN EXISTING CARRIER.

• Carrier 0– Must be modified on NCC.– Log on to NCC as user linkway.– Open a file manager window.– Navigate to

home/linkway/etc.datapath/etc/dbnew– Double click on the carrier.tdb file.– Edit the file– Save the file– Stop and restart the NCC.

When modifying carrier information in the NCC, ensure that that the values in the carrier.tdb file are the same as presented in the cut sheet.

46


• Click on Network Parameters



• Enter information from the cut sheet.

• Enable Network Admin• MRT Terminal id is

always 120.

47

Site Configuration (1)

• From the Configuration screen– Click Site

Configuration


• Window displays basic information about all configured sites.

• Site ID 0x000000120 is ALWAYS the MRT.

• NOTE: MRT cannot be deleted from list.

• NOTE: Terminals must be deleted from a site before a site can be deleted.

• To edit a configured site, click the Site Details button.

• To add a new site click the Add Site button.

48


• Window is broken into the following fields:

– Site Details• Linkway

– Pull down menu– Select the version of

Linkway modem the site will be using.

• Control Group– Pull down menu– Always 0

• Site Type– Pull down menu– Choose Traffic Terminal

site, Master Reference Terminal Site, Alternate Reference terminal as appropriate.

• Site ID – Auto assigned by the NCC

• Site Name – Per Cut Sheet

49


– Position• Longitude – Enter

terminals longitude in degrees east.

• Latitude – Enter terminals latitude in degrees north.

• NOTE: Accuracy is very important as the NCC uses position to calculate timing. If possible, double check Lat/Long via terminals STT ACU.

– Antenna Position• Auto populated based

upon Position and Satellite entries.

When entering longitude and latitude, a margin of error of roughly fifty miles from the site’s actual position exists. However, any geographical deviation from the site’s actual position will increase the time the terminal takes to sync with the rest of the network. It is therefore prudent to make this entry as accurate as possible to ensure the terminals quick entry into the network.

50


– ODU Information• Type – Pull down menu:

Unknown• M&C Link Type – Pull down

menu: RS232• BUC Power – Off• RF (KHz) – Tx and Rx

frequency range center frequencies.

– Tx: 1,300,000 KHz + 13,050,000 (BUC LO) KHz = 14,350,000 KHz

– Rx: 1,300,000 KHz + 10,750,000 KHz(LNB LO) KHz = 12,050,000 KHz

– DOES NOT CHANGE WITH CENTER FREQUENCY, ONLY CHANGES WHEN LNB/BUC IS CHANGED.

• LNB Power – Power not checked and Reference not checked

• Click Submit

The transmit and receive center frequencies shown here are used as a reference. While the calculations for determining a site’s center frequency remain the same, if the site’s BUC or LNB are changed so that it uses a different local oscillator frequency, these calculations will have to reflect that change.

51


• Click the Add Terminal Button.


• Name: Recommend same as Site Name.

NOTE: Ensure that site name can EASILY identify the Brigade, Battalion, JNN node number or other unit designation.

• TX Power: -30 to 0 dBm– NMS CAN NOT ACTIVELY

CONTROL POWER SETTINGS UNTIL THE TERMINALS ENTER THE NETWORK.

• Max Tx Rate: Set to cut sheet if different from carrier. Normally left at 5 Msym/sec.

• UPC Enabled: NO!!• Click the Submit button

52

IP Configuration (1)

• From the Configuration screen– Under Protocol/Services

Configuration, select IPfrom the pull down menu.

– Click on the Protocol/Services Configuration button


• Display gives Site ID, Interface, Status, and Type.

• Interface 2 is the only interface number used in an IP Network.

• To configure an existing site, click on the site, then click the Configure button.

• Add a new interface, click the Add button.

53


• IP Address– Enter the IP Address and the

Subnet Mask from the cut sheet.

• Routing– Routing Protocol

• Per cut sheet.– RIP (Routing Information

Protocol) Parameters• Not used by the Army in JNN


• Permanent Virtual Circuit –– Not tied to physical network

path– Bandwidth is reserved for the

PVC.

• To configure a PVC– Click the PVC button

54


• To add a PVC click the Add button.

55


• Mode – Must be Unicast• Source

– Select the Site and Interface from the pull down menus.

• Destination– Enter the Destination Site

Information• CIR (Committed Information

Rate)– Varies depending on final

network configuration.

JNN typically has a CIR of 0 and 0 but if using for power balancing, use 64 and 64. This way all the circuits will have the same data rates and is easier to see if a circuit is power balanced as referenced to all the other circuits.

56

Auto vs Manual PVC’s

• Auto PVC’s make a logical connection to every terminal in the network to every other terminal in the network.– Make connections that are not needed.– Clog the network with unwanted bandwidth

• Manual PVC’s makes the operator determine which terminals talk to other terminals.– Miss connections that may be needed– Must have logical method of keeping track of network

57

Questions?

TAB

Insert Tab # 5 Here

Generating Boot Files

60

Generating Boot Files (1)

• New boot files need to be generated:– New network configuration is complete.– The following changes are made to an active

network:• Transmit and/or Receive center frequencies• Carrier 0 frequency • TDMA Frame Structure• Site Identity

61


• In the Diagnostic Screen:

– In the Command field type makeboot

– In the To Terminal Field select NCC from the pull down menu.

– Click the Send Button.– You should see

confirmation of one boot file made for each terminal configured.

– File boot.420 is for terminal 420 etc.

Remember that the Diagnostic Screen is just a GUI to the NCC. The “makeboot” command can also be entered directly into the command prompt of the NCC.

62


• Now that the boot files are generated they have to be moved from the NCC Sun box to the NMS Laptop.

• We FTP the files.– The only FTP program NOT to use is Windows

Explorer.


• Open a DOS Command window.• Change directory to where you want the boot files saved.• At the prompt type ftp<enter>• At the prompt type open(IP address of the NCC)

63


• Enter the NCC username and password when asked.• User linkway message will be displayed.• At the prompt type cdetc.datapath/etc/bootdb• At the prompt type ascii to select the ASCII transfer mode.

64


• At the prompt type get (file name of file to transfer) to transfer one file

An alternative to the get is mget boot.*. The mget boot.* command will transfer all bootfiles, since in Unix and Unix-like systems the * serves as a wildcard. Before each file is transferred, the user will be prompted to confirm the transfer. Type yes at each prompt.

65


• To end the session at the prompt type:– Close<enter> Closes the FTP session– Bye<enter> Quits the FTP application– Exit<enter> Closes the command window.

66

Common FTP Commands

• pwd – tells you what directory you are in.• ls – lists files in the directory.• get – gets one file.• mget – gets more than one file.• open – starts an ftp connection with an ftp server• close – stops an ftp connection with an ftp server

These commands will also work in a UNIX environment.

67

Load the Bootfile

• After generating bootfiles for you network, begin by loading the MRT’s bootfile, identified as Terminal 120. This process is the same as if the MRT Linkway modem was in an STT.

68

Database Synchronization (1)

• After all configurations have been completed the NCC and ANCC must have their databases synchronized.


• Log on to the active NCC computer.

• Navigate to the /home/linkway/

etc.datapath directory.• Delete the <other NCC

hostname>.previous file.

69


• Log on to the backup NCC computer.

• Navigate to the /home/linkway/

etc.datapath directory.• Delete the <other NCC

hostname>.previous file.• Start the backup NCC by

entering the following command at the prompt: ncc_start

NOTE: This process may take up to one hour to complete

70

Access the Satellite

• Once the NCC and ANCC databases have been synced, the satellite terminal serving as the host for the MRT may access the satellite.

– If the terminal is already on the bird, contact the controllers to access the carrier.

71

Entering the Network (1)

• The modem will receive synch, indicated by a blinking “SAT” light.

• The modem will then transmit synch, indicated by a solid “SAT” light.

• MRT site should be green on the NMS.

Entering the Network (2)

• Verify TT’s are entering the network.• If not, assist as applicable.

72

Verify Modem Performance (1)

• The following steps should be performed upon entrance into the TDMA network and then daily as part of routine maintenance.

• In the Diagnostics window enter the command cb, then select the MRT from the pull down window, then click on the Send button.– The clear burst command will erase all burst statistics.

• In the Diagnostics window enter the command rbtp, then send it to the MRT.– Displays receive burst time plan of the modem.– Used to identify bursts and from which terminal they are coming

from.


73


• RBTP Status Fields

– List the ID, type, transmit and receive terminals, and all otherrelative carrier information.


• In the Diagnostic window enter the command rx, then send it to the MRT.

– Displays receive status of the modem.– Powerful tool for maintenance and troubleshooting.

• Allows user to identify bursts ID between terminals.

74



• Receive Status Fields– State

• RxSynced – TT modem has locked on to the reference burst.

• Search – TT modem has not locked on to the reference burst.

– If the modem stays in this state for several minutes verify the MRT is transmitting and there are no local downlink problems.

75


• Receive Status Fields

– RefBurstRawBer – BER of the modem pre FEC.• Should be 10E-3 or better. If below indicates a problem that will

have to be isolated.

– Rxatten – Value of the modems internal attenuator setting, range of 0 – 40.

• Optimal setting is 20. NOTE: NOT REQUIRED TO BE AT 20. JNN is typically at 36 – 28.

• If setting is near or at maximum, attenuation may have to be added to the receive chain.

• If setting is near or at minimum, power may have to be added at the MRT, or attenuation taken out of the MRT transmit chain.


• In the Diagnostic window enter the command rb, then hit send it to the MRT.– Displays reference burst statistics of the modem.– Ensures power is not too high or too low.

76


Above is a visual representation of the Diagnostic screen when the “rb” command is entered. This command shows the receive bursts statistics for all sites shooting into the terminal in which the command was entered, in this case, the MRT or AMRT. The first terminal identified is the MRT’s receive bursts statistics, followed by the other terminals within the network. The receive bursts statistics for this particular network are particularly poor, as can be seen from the screenshot. All terminals are experiencing massive amounts of “misses”, meaning they did not receive the burst when they were expecting to, and Terminal 3 is being forced to make a large number of Viterbi corrections, indicating that it is taking many forward errors. Additionally, Terminal 3 is experiencing many CRC (Cyclic Redundancy Check) errors, meaning that the data it is receiving from the MRT is heavily corrupted.

77


• Reference Burst Status Fields– Burst ID 1, the MRT reference burst is the most important

burst. TT will not remain in the network without the reference burst.

– Detects – Number of times the modem has “detected”, or received the RB.

• Number should be steadily increasing.– Misses – Number of times the modem has NOT received the

RB.• Number should be very small, if the number continues to

increase, the problem will have to be isolated.

Detects – This is the number of times, which the distant end terminal has received, or “detected” receive bursts from the MRT. This number will gradually rise as the terminal becomes synced with the network, and should continue to do so as long as the terminal remains synced. The “Detects” field will reset itself after 40,000 receive bursts have been detected, or an operator enters the “cb” command, which will clear burst statistics. Misses – This is the number of times the terminal has not detected the receive burst when it was expected. The number of misses may rise during initial syncing of the terminal, but should not continue to rise by a noticeable degree once the terminal is fully synced. If the number of misses does continue to rise, there is likely a problem with the terminal’s receive, or, possibly, with the TDMA network itself.

78


• Reference Burst Status Fields– VitCorrs – Number of Viterbi corrections performed by the

modem.• Should be low, but some will always be present, compare over

24 hour window to baseline system.• If the number is increasing rapidly, indicates a problem that will

have to be isolated.– FrEr – Frequency Error in Hertz.

• Within +/- 100 Hertz• If not, contact customer service.• Modem will have to be replaced with a known good modem.

Viterbi Corrections – Invented by Andrew Viterbi in the 1960’s, the Viterbi Algorithm is a mathematical means of predicting and correcting errors, or Forward Error Correction. While there will always be a small number of Viterbi Corrections (since no means of RF transmission is free of errors), a rising number of Viterbi Corrections indicates that the data being received is increasingly full of errors. If the number of Viterbi Corrections continues to rise, there is a problem within the network. The recommended timeframe over which to compare Viterbi Corrections is 24 hours. Frequency Errors – Since TDMA bursts occur over a number of frequencies within an allocated block, they must be very precise. If the TDMA modem is experiencing frequency deviation more than 100 Hz, it is mostly malfunctioning and must be replaced with a new modem.

79


• Reference Burst Status Fields– Power – Receive power in dB’s.

• Range +6 to -6• Should be within .5 of 0, 0 = - 55 dBm.• If not within .5 of 0, using the NMS raise/lower power on

the MRT until the power is correct.• Repeat power balancing on all terminals in the network,

MRT to TT, and TT to TT.– RSCorrs – Number of Reed-Solomon corrections.

• Should be low, 10 to 20 per day maximum.• A higher number indicates a degrading system and the

problem needs to be corrected.– CRCErrs – Number of uncorrectable errors.

• Steady/rapid increase indicates a poor RF link.• Link failure is highly probable, the problem needs

correction as soon as possible.

Power – This field is the receive power of the terminal in dB’s. The optimal receive power is within .5 dB of 0. If any terminals receive power is outside optimal, the network in all likelihood needs to be power balanced. Reed Solomon Corrections – Similar to Viterbi Corrections. Should this number increase noticeably over a 24-hour period, there is a problem within the network. Cyclic Redundancy Check Errors – When sending data to another terminal, the MRT (or another terminal), uses an algorithm to create an alphanumeric representation of that data called a Cyclic Redundancy Check. If, when the distant end receives this information, it does not match the Cyclic Redundancy Check, it displays an error. If these errors continue to occur, the RF linkage between terminals is poor and troubleshooting should commence.

80


• In the Diagnostic window enter the command show_ber, then send it to the MRT.– Displays raw BER statistics of the modem.


81


• Show_BER Status Fields– Bits – Number of bits encountered, will increase over time.– BitErrors – Number of bit errors received. Will increase over

time.– BER – Raw Bit Error Rate.

• Should be 10E-5 or better. If below indicates a problem that will have to be isolated.

The “show_ber” command will display the BER, or Bit Error Rate for the terminal. The Bit Error Rate is the number of errors that the terminal experiences compared to the number of bits it is actually receiving. For example, if ten bits are received as well as one error, the Bit Error Rate will be one in ten, or 0.1. This would be considered so high as to be unusable, and Bit Errors are typically only found for several million bits received. BER is shown using scientific notation, so a BER of 10E-5 would be 10, followed by zeroes, or 1,000,000, meaning one error is received for every million bits. Alternatively, this is an error rate of .0000001.

82


• In the Diagnostic window enter the command tx, then send it to the MRT.– Displays transmit statistics of the modem.

The “tx” command is shorthand for “transmit”. As the name implies, it will display transmit statistics for any modem in which it is entered. This command will provide diagnostic and troubleshooting information in the event that a terminal is experiencing a degraded signal or is having trouble syncing with the network. Additionally, it will provide general performance information useful for peaking and polling, as well as increasing the efficiency of the network.

83


84


• Transmit Status Fields– State

• TxSynced – TT modem has transmitted 3 consecutive AB’s at the correct time.

• Search – TT modem has not transmitted 3 consecutive AB’s at the correct time.

– If the modem stays in this state for several minutes verify the MRT is transmitting and there are no local downlink problems.

After entering the “tx” command, the whole of the terminal’s transmit status is displayed. The first line contains the transmit “State” in which the terminal is when the command is entered. When the terminal initially is powered up and has acquired receive sync, its transmit state will be “Search”. In the Search phase, the terminal has not yet sent three Acquisition Bursts in timing sync with the MRT. In other words, it is still searching for the synchronization acknowledgement from the MRT. Once the requisite Acquisition Bursts have been sent with the correct time, they enter the “TxSynced” or Transmit Synced state, meaning the terminal can now transmit over the network.

85


• Transmit Status Fields– TxSyncLosts – Total number of times modem has lost

transmit synch.• Should be at or near 0.

– A steadily increasing value indicates a system problem that needs to be isolated and corrected.

The “Transmit Synchronization Loss” field shows the operator the number of times that the terminal has transmit sync once it

86


• Repeat the above steps for EVERY terminal in the network.

Verify TDMA Modem Performance

• Ping from Modem to Modem– In the Diagnostic window type the following command:

• ping xx.xx.xx.xx -i 1 -t 4000.• ping (IP address of modem you are reaching), -i = Interface 0,

and –t, time 4000 ms.• Because of the bursty nature of the TDMA modem, ping must be

held-up for a period of time to ensure a burst catches it.

87

NCC Shutdown

• To shutdown the NCC Sun workstation use the following steps:– On the Sun workstation log on as user linkway.– Open a terminal window and type ncc_stop<enter> at the

prompt. This stops the NCC processes.– At the prompt type su<enter>– When the password is asked for, at the prompt type

root<enter>. You are now logged in as the super user.– At the prompt type: shutdown –i5 -g0<enter>.– Press the y key in response to any confirmation questions.– Repeat the procedure for the ANCC.– FAILURE TO SHUTDOWN THE SUN WITHOUT USING

THE ABOVE PROCEDURE MAY RESULT IN DAMAGE TO DATA, FILE SYSTEM, AND OPERATING SYSTEM.

88

Questions?

TAB

Insert Tab # 6 Here

Trouble Shooting and

Maintenance

91

Trouble Shooting and Maintenance (1)

• If the MRT and/or AMRT are ever replaced the ethertab file in both the NCC and ANCC must be edited to reflect the new MAC address of the new Linkway.

• If not already open, open a file manager window.• Open the /home/linkway/etc.datapath/etc folder.• Double click on the ethertab file to open it in the text editor.• The first line of the file should appear similar to:

00 a0 94 00 51 37 21 #MRT• The second line of the file should appear similar to:

00 a9 84 00 52 36 41 #AMRT• Enter the MRT/AMRT Ethernet address into the file. The address can

be found on a sticker on the back of the Linkway modem.• Do not change the 21/41 in the file; the only changes should be the

first six pairs of numbers.• Save the file and close the window.

Trouble Shooting andMaintenance (2)

• Symptom– MRT is the only terminal in the network that has achieved transmit

and receive sync.• Cause

– Wrong satellite information entered on the NMS.• Symptom

– The MRT will not transmit sync, attempts to receive sync before bursting.

• Cause– NCC is not communicating with the MRT. Check the following:

• Ethertab file is correct.• Connection between NCC and Switch, and Switch and MRT are

correct. (Should be straight thru cables.)• Bad MRT or NCC, change to ANCC and/or AMRT.

92

Trouble Shooting andMaintenance (3)

• Symptom– No terminals are achieving sync.

• Cause– System fault in the MRT Satellite terminal, check HPA, LNB, and

cables via wiring diagrams.• Symptom

– One terminal will not enter the network.• Cause

– Satellite terminal problem on the distant end, assist in troubleshooting as applicable.

– Ensure terminal is peaked on the satellite.– Boot File is incorrect. Ensure terminal is configured correctly,

especially latitude and longitude.

93

Questions?

TAB

Insert Tab # 7 Here

Adding Control Groups

96

Why an Additional Control Group?

• If a network becomes too busy or has too many terminals, one RB is not sufficient to update the TT’s in a timely manner.

• Symptoms of this are dropped PVC’s, PVC tables having to be reloaded, and TTP timeouts in the conolog files in the ETC directory.

Since network timing is controlled via receive bursts from the MRT, if there are too many terminals on the network or too much data is being passed, the traffic bursts will become too numerous for one traffic burst to control. If sufficient control over timing within the network is not maintained, the number of traffic collisions will increase, resulting in lost data, which will then have to be retransmitted. This lag in the network will cause PVCs to be dropped, necessitating their re-entry in PVCs tables. Therefore, it is essential that additional receive bursts are introduced to the network to better control timing and increase network efficiency. Additional control groups provide these additional receive bursts.

97

When to add a Control Group

• Only add a control group when instructed to by network operations or when it is part of the initial configuration.

Since improperly added control groups can actually increase network latency, as well as errors, it is important to add an additional control group when absolutely necessary as determined by network engineers.

98

Adding Control Groups Procedure (1)

• On the active NCC copy the carrieradmin.tdb file from db to dbnew.

• Open the file in file manager.

• Copy and paste the four lines of text, four times with a blank line between each group.

The information contained in the carrieradmin.tdb file determines what traffic goes over what carrier. Since the db directory provides an initial back up and configuration function, copying and then altering the file in the dbnew directory will actually provide the information from which the NCC controls the carriers.

99

Adding Control GroupsProcedure (2)

• Edit the groups so that the first group is SrcCGroup: 0; DstCGroup: 0; Second Group is SrcCGroup: 0; DstCGroup: 1; Third Group is SrcCGroup: 1; DstCGroup: 0; Fourth Group is SrcCGroup: 1; DstCGroup: 1.

• Copy and paste the four groups, change carrier ID to 1 in the second set of four.

• Repeat for all carriers.

• Save and close the file.

This control group information delineates which control groups can transmit and receive on which carrier. For example, in the default settings, Control Group 0 can send information to itself (since SrcCGroup 0 has a DstCGroup value of 0), as well as to Control Group 1 (DstCGroup 1). Control Group 1 is configured in the same manner. Changing the Carrier ID to 1 means that those Control Groups originating from that carrier will only burst over that carrier.

100


• Copy cgroup.tdb from db to dbnew.

• Open the file.

• Copy and past the first two lines of the file, leaving a space between the entries.

• Change the second entry to CGroupId : 1

• Save and close the file.

Editing the cgroup.tdb file and moving the edited to file to dbnew simply tells the NCC that there is now more than one Control Group to be used.

101


• The Sigburstdef.tdb file must now be edited.– Open a file manager window and navigate to

/home/linkway/etc.datapath/etc/dbnew and find the Sigburstdef.tdb file.

– If the file does not exist go to the /home/linkway/etc.datapath/etc/db directory and copy the Sigburstdef.tdb file to the dbnew directory.

– If the file does exist copy the file to the current directory and rename it as Sigburstdef.old.

Renaming the sigburstdef.tdb file as sigburstdef.old helps to identify which sigburstdef file is the original and which is the edited version.

102


• In the file manage window, double click on the Sigburstdef.tdbfile.

• To the left is an example of the file.


• Ensure there is a space after the last entry in the file.• Copy all the text in the file and paste it below the

existing file text.

103


At this point the file should display two groups of four burst ID’s each labeled 1 – 4.

Burst ID’s


Change the second group of four burst ID’s to 5 – 8.

Burst ID’s

104


• In Burst ID 5 change the following lines:– Carrier ID to 1.– Dst to 0x1ffff– DataSink to 0x1ffff

Once the CarrierId is altered to 1 from 0, the edited bursts identified in the sigburstdef.tdb file will ONLY appear on Carrier 1.

105


• In Burst ID’s 6 through 8 change the following lines:– Carrier ID to 1.– Src to 0x1ffff– DataSrc to 0x1ffff– Additional control groups replace the 1 with 2 etc. until all control groups are configured.


• Review the file to ensure it is correct.• Save and close the Sigburstdef.tdb file.

106


• Open the routab.tdbfile in a window.

• Copy the first five lines and paste it into four groups.

• Edit groups 2 through 4 as shown.

• Repeat as necessary for each additional control group.

107


• Review the file to ensure it is correct.• Save and close the routab.tdb file.• Stop and restart the NCC processes• Start the NMS on the NMS laptop.• Open the Burst Time Plan window and verify the

additional control group is present.• Any existing Site that will be assigned to a new control

group, must be deleted, reconfigured, and added to the correct control group.

When viewing the Burst Time Plan, ensure that the two control groups appear on two separate carriers. Once again, if there is more than one control group on a single carrier, signaling collisions will occur. If, for some reason, the Burst Time Plan cannot be viewed graphically, enter the command rbtpon the MRT. More than one control group on one carrier will result in the number of Viterbi Corrections on the MRT rising quickly.

108

Adding Control Groups Validation

• Burst Time Plan should display a control group on each carrier that one has been assigned.

109

Questions?

Table of Contents - Noodlez.org Courses PDF Student Guides/Master Reference...– Reference (RB) –...

Documents

Transcript of Table of Contents - Noodlez.org Courses PDF Student Guides/Master Reference...– Reference (RB) –...