s5420 Idu Dvb-s2 Scpc User Manual 851674 Rev p01

IDU User’s Manual S5420DVB-S2 SCPC

Document Number: 851674

Revision: P01

Date: February 16, 2010


Revision: P01

IDU User’s ManualS5420 DVB-S2 SCPC

IDU User’s Manual S5420 DVB-S2 SCPC

851674 P01


Revision: P01

Date: February 16, 2010

Proprietary Notice: Copyright © 2010 Advantech Satellite Networks, Inc. Allrights reserved.The information contained herein is proprietary to Advan-tech Satellite Networks or third party proprietary informationwhich Advantech Satellite Networks is obligated to protectand shall not be disclosed in whole or in part without theprior written permission of Advantech Satellite Networks.

February 16, 2010 Advantech Satellite Networks Proprietary Page ii


851674 P01

Table of Contents

Chapter 1. Important Safety Information 11.1 RF Radiation Hazard 11.2 General Safety Warnings 11.3 Protection Against Electrostatic Discharge 3

Chapter 2. Getting Started 42.1 Introduction to DVB-S2 SCPC 42.2 Satellite Interactive Terminals (SITs) 62.3 IDU Overview 7

2.3.1 Model 5420 72.4 Overview of the IDU Web Interface 8

2.4.1 IDU Web Interface Page 92.4.2 Using the IDU Web Interface 10

2.5 Overview of Installation and Satellite Networking 10

Chapter 3. Installation 123.1 Installation Requirements 12

3.1.1 ODU Installation 123.1.2 IDU Unpacking - Model 5420 123.1.3 Computer for IDU Configuration 13

3.2 Installing the IDU 133.2.1 Step 1. Site Selection 133.2.2 Step 2. Making Power and Cable Connections 13

3.3 Accessing the IDU Web Interface 143.3.1 SSL Secure HTTP Access 15

3.4 Steps for Basic IDU Installation and Configuration 163.5 File Management 17

3.5.1 Configuring Access to an FTP server 173.5.2 Upgrading Software 183.5.3 Transferring Configuration Files 193.5.4 Delta Configuration 193.5.5 Configuration Backup and Restore 20

3.6 Installer Configuration 21

February 16, 2010 Advantech Satellite Networks Proprietary Page iii


851674 P01

3.7 SCPC Management 243.8 Network Configuration 283.9 IDU Control 30

3.9.1 Disabling and Enabling Transmission (HOLD State) 303.9.2 Carrier ON and Carrier OFFl 303.9.3 Reboot 30

3.10 Test Control 313.10.1 Test Control 313.10.2 Power Level 323.10.3 Default IF Power Level 323.10.4 Actions 32

3.11 Superuser Password Configuration 32

Chapter 4. Advanced Configurations 344.1 Queue Management 34

4.1.1 Step 1. Define Traffic Queues 354.1.2 Step 2. Select Filter Pattern Table Configuration settings 364.1.3 Step 3. Apply Filter Patterns 37

4.2 Routing Management 414.2.1 Static Routing 424.2.2 Dynamic Routing 43

4.3 DHCP Management 454.4 Multicast Configuration 48

4.4.1 Tx Multicast Source Support 484.4.2 Rx Multicast Source Support 484.4.3 Rx Default Multicast Mapping Table Configuration 49

4.5 MIB Trap 494.5.1 Enabling or Disabling MIB Trap Flags 504.5.2 Configuring the Trap Destination Table 50

4.6 MIB Access Policy 514.6.1 Setting Global Options for the MIB Access Policy 524.6.2 Managing Access Policy Table Entries 524.6.3 Managing Access View Rights Table Entries 53

4.7 PEP 544.8 Web Page Management (Logo) 554.9 Forward Link Control Management (FLCM) 55

Chapter 5. IDU Monitoring 575.1 IDU Monitoring 575.2 IDU Log 595.3 Network Interface Stats 615.4 Active Connection Monitoring 615.5 Forward Link PID Statistics 625.6 Multicast Active Membership Monitoring 625.7 Multicast Statistics 63

5.7.1 IGMP Statistics Table 635.7.2 Virtual Interfaces (Vifs) Statistics Table 635.7.3 Multicast Routing Cache Table 64

February 16, 2010 Advantech Satellite Networks Proprietary Page iv


851674 P01

Appendix A. Glossary 65

Appendix B. Parameters in Web Interface Pages 68

Appendix C. Menu Result Page 69

Appendix D.

February 16, 2010 Advantech Satellite Networks Proprietary Page v


851674 P01

February 16, 2010 Advantech Satellite Networks Proprietary Page vi


851674 P01

Chapter 1 Important Safety Information

Warning: The following general safety precautions must be observed duringall phases of operation, service and repair of this equipment. Failure tocomply with these precautions or with specific warnings elsewhere in thisdocumentation violates safety standards of design, manufacture andintended use of the equipment. Advantech Satellite Network assumes noliability for the customer’s failure to comply with these requirements.

Please review the following important safety information before installation and use of theequipment.

1.1 RF Radiation Hazard

Warning: The powerful radio frequency (RF) signal from the ODU transmitterand antenna can be very hazardous. Ensure that all transmission from theODU has been disabled before approaching it.

1.2 General Safety Warnings• This equipment generates, uses, and can radiate RF energy and may cause interfer-

ence to radio communications or could cause harm or injury to a non-alert person ifnot installed and used in accordance with this documentation.

• The equipment described in this manual is designed for use by properly trained per-sonnel. Only qualified personnel who are aware of hazards involved shall carry outinstallation and maintenance and repair of the exposed equipment.

• The user must verify all local regulations before installing the IDU.

• Read all safety and operating instructions before operating the equipment.

• Retain all safety and operating instructions for future reference.

• Read all warnings instructions on the unit and the operating instructions.

February 16, 2010 Advantech Satellite Networks Proprietary Page 1


851674 P01

• Exceeding the maximum rated AC input voltage could result in damage to the unit.Operating with a fuse of improper rating could result in a fire hazard.

• Operating the unit with the safety ground wire of the supply or the power cord discon-nected could result in a shock hazard.

• Do not operate this unit with the enclosure ungrounded and floating.

• No operator serviceable parts inside. Refer servicing to qualified personnel.

• To prevent electrical shock, do not remove covers.

• Do not spill food or liquids on your unit. Doing so can cause fire or electric shock byshorting out internal components.

• Do not use the equipment in damp surroundings and avoid direct contact with water.

• Never place the equipment in direct sunlight, and keep your unit away from radiatorsand heat sources.

• If the unit has a fan, do not cover the fan opening when the unit is in use, as this willimpede the ventilation required.

• Unplug the equipment from the AC power outlet before cleaning. The outside of theequipment may be cleaned using a lightly dampened cloth. Do not use any cleaningliquids containing alcohol, methylated spirit or ammonia.

• Do not use accessories or attachments not recommended by the manufacturer, as theymay cause hazards and will void the warranty.

• Install the equipment on a flat and stable surface.

• Route power supply cords and interconnecting cables so that they are unlikely to bewalked on or pinched by items placed upon or against them. Pay particular attentionto cords at plugs, convenience receptacles, and the point where they exit from theunit.

• Never insert objects of any kind into the unit through openings, as the objects maytouch dangerous voltage points or short out parts. This could cause fire or electricshock.

• When replacement parts are required, ensure that the service technician uses replace-ment parts specified by the manufacturer. Unauthorized substitutions may damage theunit or cause electric shock or fire, and will void the warranty.

• Always turn the power off and wait 5 seconds before disconnecting or connecting anycables to the IDU.

• Do not short or overload any output connectors or cables, these may cause a seriousdamage to the unit and will void the warranty of the unit.

• Upon completion of any service or repair to the unit, ask the service technician to per-form safety checks to ensure that the SIT is in proper operating condition.

• For continued protection against fire hazard, replace all fuses only with same type andrating.

• Do not operate the system in the presence of flammable gases or fumes. Operation ofany electrical system in such an environment constitutes a definite safety hazard.



851674 P01

1.3 Protection Against Electrostatic Discharge• Static electricity can harm delicate components inside your equipment. To prevent

static damage, discharge static electricity from your body before you touch any ofyour equipment’s electronic components, such as the microprocessor boards. You cando so by touching an unpainted metal surface on the grounded equipment chassis. Asyou continue to work inside the equipment, periodically touch an unpainted metalsurface to remove any static charge your body may have accumulated. You can alsotake the following steps to prevent damage from electrostatic discharge (ESD):

• When unpacking a static-sensitive component from its shipping carton, do notremove the component from the anti-static packaging material until you are readyto install the component in your equipment. Just before unwrapping the anti-staticpackaging, be sure to discharge static electricity from your body.

• When transporting a sensitive component, first place it in an anti-static container orpackaging.

• Handle all sensitive components in a static-safe area. If possible, use anti-staticfloor pads and workbench pads.

• This unit is provided with a protective ground incorporated in the power cord. Themains plug shall only be inserted in a socket outlet provided with a protective earthcontact. Any interruption of the protective conductor, inside or outside the equipment,is likely to make the equipment dangerous. Intentional interruption is prohibited. Ifyou are unable to insert the plug into the outlet, contact an electrician to replace theoutlet. Do not defeat the safety purpose of the ground-type plug.

• Unplug the unit power cord by gripping the power plug, not the cord.

• Do not place the unit on an unstable cart, stand, tripod, bracket, table, or on a bed,sofa or rug. The unit may fall, causing personal injury and damage to the unit.

• Do not overload wall outlets or extension cords, as this can result in a risk of fire orelectrical shock.

• We recommend using an outlet that contains surge suppression or ground fault protec-tion. For added protection during a lightning storm, or when the SIT is left unattendedand unused for long periods of time, unplug it from the wall outlet and disconnect thelines between the indoor unit and the antenna. This will prevent damage caused bylightning or power line surged.

• Unplug the unit from the wall outlet and refer servicing to authorized service person-nel whenever the following occurs:

• The power supply cord or plug is damaged;

• Liquid has been spilled, or objects have fallen into the indoor unit;

• The unit has been exposed to rain or water;

• The unit has been dropped or the chassis has been damaged;

• The unit exhibits a distinct change in performance.



851674 P01

Chapter 2 Getting Started

This manual covers installation and satellite network configuration of Advantech Model5420 indoor units (IDUs). It is intended for use with the IDU software version 9620Rxx,where xx is the revision number.

This SW load exclusively runs on the following Advantech IDU HW platforms Series5420 part number 850643-365 and 850643-366.

Note: This SW load doesn’t run on the following Advantech IDU H/W platforms· Series 1000 (all)· Series 2000 (all); Series 3000 (all)· Series 4000 (all); any Series 5000 other than S5420

Note: The IDU 5420 is designed for DVB-S2 SCPC. It can also operate as theIDU 5120 when a DVB-RCS software image is loaded in.

• For an introduction to SITs and satellite networking, see section 2.1.

• For an introduction to the IDU, see section 2.2 and section 2.3.

2.1 Introduction to DVB-S2 SCPCThe SCPC network provides for a simple introduction of return channel services. Each user terminal is assigned a single return channel carrier with a corresponding demodulator. The S5420 can be used in two network architecture: point-to-point, and point-to-multi-point.

The point-to-point architecture will generally consists of two stand-alone S5420s, one at each location. The transmission of one is received by the other.



851674 P01

The other network configuration is point-to-multi-point, where all the SCPC remotes share a common receive high-rate broadcast carrier emanating from a Gateway. Each remote puts up a DVB-S2 SCPC carrier towards the Gateway. For each of the remote, there is a matching DVB-S2 demodulator located at the Gateway. Usually this type of con-figuration will be managed from the Gateway.

The SCPC gateway is relatively simple and provides for basic network configurations and IP access. An important element of the system is that the Forward Link is always a high-rate broadcast carrier providing increased efficiency over a set of Forward Link SCPC car-riers with simpler routing in the SCPC gateway.

Figure 2.1 shows the architecture of a point-to-multi-point SCPC system. The SCPC net-work is designed to carry IP traffic only.

The system consists of a scalable SCPC Gateway and a set of user terminals. Each termi-nal is assigned a SCPC return link carrier at installation with the option for reconfiguration of this carrier either locally or remotely. The assigned return link bandwidth can vary with the system requirements.

The Forward Link is a standard DVB-S2 carrier using DVB-MPE (Multiprotocol Encap-sulation) for IP Traffic. The forward link can vary from 1 to 40 MSps.

Similarly, the return link is a standard DVB-S2 carrier using DVB-MPE (Multiprotocol Encapsulation) for IP Traffic. The return link can vary from 256 kb/s up to 10 Mb/s.

It should be noted that in a point-to-point scenario, the data rate range varies from 256 kb/s to 10 Mb/s in each direction.

The SCPC terminal is also equipped with a very stable reference oscillator as it can't rely on the presence of a Network Clock Reference (NCR) when operating in SCPC mode.



851674 P01

Figure 2.1 Point-to-multipoint DVB-S2 SCPC System

2.2 Satellite Interactive Terminals (SITs)SITs are made up of two components, as shown in the figure below.

• The outdoor unit (ODU) consists of an antenna subsystem and an RF transceiverassembly. The antenna is made up of a reflector dish and a transmitter (or BUC) thatgenerates the return link signal.

• The ODU is connected via two inter-facility link (IFL) cables to the IDU. The IDU isresponsible for network access and is the ethernet interface with the LAN or hostcomputer.



851674 P01

Figure 2.2 SIT Schematic Diagram

For more information about the IDU, see section 2.3.

2.3 IDU Overview2.3.1 Model 5420

The Model 5420 IDU has a 1U rack-mount form factor. The front panel contains 6 indica-tor LEDs. Power and cable connections are at the back of the unit.

Figure 2.3 Model 5420 IDU

The figure below shows a schematic diagram of the IDU front panel.

Figure 2.4 Front View - Model 5420 IDU

The front panel contains the following LEDs (from left to right).

• Power LED - Green. Indicates power on when lit.



851674 P01

• IDU Ready - Green. Indicates IDU is ready when lit. When flashing it indicates theSIT is in “Hold” state.

• LINK - Amber. Indicates that the Ethernet port is connected.

• ACT - Amber. Indicates activity on the Ethernet port of the IDU.

• Rx - Green. Indicates forward link is acquired when lit. When flashing it indicates thetuner is locked.

• Tx - Green. Indicates return link is acquired when lit.

The figure below shows a schematic diagram of the IDU back panel.

Figure 2.5 Back View - Model 5420 IDU

The shaded areas are as follows (from left to right).

• Power cable connector. Provides AC power interface for IDU and ODU, and protec-tive grounding of the IDU. Requires C14 type power cord, not supplied with the IDU(AC Inlet: IEC-60320 C13 socket). 110-220 VAC, 50/60Hz (auto-ranging).

• Power switch. Turns IDU power on or off.

• Fuse. Fast Acting Glass Fuse 250V, 2A.

• IDU IN connector. F-Female 75 ohm connector for IFL cable from ODU. For forwardlink communication.

• Ethernet connector. 10/100BaseT Ethernet Interface on RJ-45 connector. For ethernetconnection with LAN or host computer.

• Reset. The Reset button resets the IDUs ethernet IP address to its default value of10.10.10.10. The IP address remains at this value until the unit is rebooted. To pushthe reset button, insert a paper clip (or equivalent) into the hole for about one second.

• IDU OUT connector. F-Female 75 ohm connector for IFL cable from the ODU. Forreturn link communication.

• Serial Port. DB-9 connector to input the GPS coordinated. The pin 9 carries +24V.

2.4 Overview of the IDU Web InterfaceThe IDU web interface provides the user interface with the IDU. The IDU web interfacecan be accessed from any computer with a network or Internet connection to the IDU. TheIDU web interface enables the operator to:

• Set installation parameters

• Configure the SIT to access the satellite network

• Test and troubleshoot satellite links

• Configure passwords and security settings on the SIT



851674 P01

• Monitor SIT alarms and events

• Manage how the SIT queues and transfers data over the satellite network.

2.4.1 IDU Web Interface Page

The figure below shows a typical IDU web interface page (does not represent the actualIDU web page).

• IDU Name. The IDU name is shown at the top left of each page. When managingmultiple IDUs simultaneously on the same LAN, it is useful to identify each IDU’sscreen with a different label. This label also appears in the title bar of the web browserwindow. The IDU name shown in the figure is “SIT_Default_Name”.

• MAC Address. The MAC address is shown at the top left of each page. The SITMAC address is a unique address assigned to each SIT. The MAC address shown inthe figure is “00-40-fd-01-ef-a0”.

• S/W Revision. The software version is shown at the top left of each page. The soft-ware version shown in the figure is V4001.R00.

• Logo. A logo is displayed at the top right of each page. The logo can be changed bythe user. The logo shown in the figure is that of Advantech Satellite Network.

• Login. A login link is provided at the left of each page. It can be selected at any timeto return to the web interface home page.

Figure 2.6 Typical IDU Web Interface Page

All IDU web pages display the following information.

IDU NAME:

MAC ADDRESS:

S/W REVISION:

SIT_Default_Name

00-40-fd-01-ef-a0 .

V4001.R00

Page Links

IDU Monitoring

Installation

Test Control

Network Configuration

File Management

Installer Password

Monitoring

SIT Operational State: OAM Active

FL Status: Acquired

RL Status: Ready Mode

IDU Power Level: -9.5

IDU TX Status: Enabled

TX Frequency (in 100Hz): 10500000

RL Measured Es/No: 8.0

FL Measured Eb/No: 19.9(db)

Login Installer Menu



851674 P01

• Page links. Links to pages in the IDU web interface are shown at the left of eachpage. Links shown in the figure are “IDU Monitoring”, “Installation”, “Test Control”,“Static User Password” and “Installer Password”.

• Content. The center of the page displays the page content, including parameters andmonitoring information. In the figure, this information is located below the “Installa-tion Configuration” title.

• IDU Help. Click on IDU parameters or monitoring information to obtain a pop-updescription of that field. This information is also contained in this manual.

2.4.2 Using the IDU Web Interface

The IDU web interface is designed for three types of tasks. These tasks are normally doneby a the installer, a service provider or satellite network operator.

• Installation. This includes physical installation, cable connections, initial access tothe user interface for installation configuration and for transmitting a test signal overthe air.

• Satellite Network Configuration. This includes configuring the IDU for access tothe satellite network (forward and return links) and MIB configuration..

• Operation and Maintenance. This includes:

• Monitoring the status of the IDU, including forward and return links, operationalstate and alerts.

• Troubleshooting the IDU's satellite network connections.

• Controlling the IDU, including acquiring and disabling satellite links.

• Configuring the IDU's access to the LAN or local PC, including its ethernetaddress.

To perform any these tasks, log in to the web interface as “installer”.

2.5 Overview of Installation and Satellite NetworkingTo get a SIT up and running, the outdoor unit (ODU) and indoor unit (IDU) must be prop-erly installed, and the IDU software must be correctly configured. If you are installing asingle SIT, the IDU software should be configured after the ODU and IDU have beenphysically installed on-site. This enables the installer to verify that the configuration iscorrect. The following steps are involved in installing a single SIT:

1. Install the outdoor unit (ODU). For help with this procedure, see the ODUInstallation and Pointing Manual.

2. Install and configure the indoor unit (IDU). See Chapter 3.

3. Configure the IDU for access to the satellite network. See Chapter 4.

Typically, however, multiple SITs that use the same satellite beam contain very similar configura-tions. In this case, the most efficient method is to pre-configure all the IDUs before physicallyinstalling them in the field. Then the installer only needs to configure a small number of site-specificparameters at install time.



851674 P01

You can monitor the current status of the SIT at any time during the installation and networking pro-cedure. For more information, see Chapter 5.

Note: The procedures described in this document assume familiarity with satellitenetworks, satellite network equipment installation.



851674 P01

Chapter 3 Installation

3.1 Installation RequirementsBefore beginning IDU installation, ensure that:

• The outdoor unit (ODU) has been installed (section 3.1.1).

• The IDU has been unpacked (section 3.1.2).

• A computer is available for IDU configuration (section 3.1.3).

3.1.1 ODU Installation

The ODU should be installed following the procedures described in the ODU Installationand Pointing Manual (from Advantech Satellite Network) and the antenna system assem-bly manual (from the antenna manufacturer). Two coaxial (IFL) cables should be routedfrom the ODU to the site where the IDU will be installed. The cables should be connectedat the ODU end to the LNB and transmitter. At the IDU end, each cable should be care-fully labeled with the name of the component it leads to (either the LNB or the transmit-ter).

Note: Permanent damage to both the LNB and transmitter may occur if the IFLcoaxial cables are switched.

3.1.2 IDU Unpacking - Model 5420

Carefully unpack the IDU and check for any damage during shipment. Ensure that theModel 5420 IDU comes with:

• A 1 m ethernet cable.

• Rack mounting brackets and screws.

•

See section 2.3.1 for a picture and description of the IDU.



851674 P01

3.1.3 Computer for IDU Configuration

You will need a PC or laptop computer in order to access the IDU web pages and config-ure the IDU. This may be the same computer that will be used with the IDU to access thesatellite network.

The connection between the computer and the IDU is made with an ethernet cable (sup-plied with the IDU).

Note: For the IDU HW platforms 850643-365, the web pages are accessed usingan HTTP secure connection. The computer must be running Windows XP or laterand have a network card with an RJ-45 connector. It must have either NetscapeCommunicator (version 4.61 or higher), Internet Explorer (version 5.5 or higher) orMozilla Firefox (version 1.0 or higher). The browser must support SSL 2.0 and 3.0,RSA with 512 bit exchange and DES with 56 bit encryption. Internet Explorer 7.0and Mozilla Firefox 2.0 don’t support SSL 2.0 by default it need to be configured.

3.2 Installing the IDUTo install the IDU

(1) select an appropriate site

(2) make power and cable connections.

3.2.1 Step 1. Site Selection

The IDU must be installed indoors in an area free of oil, dust or sand. The site should beclose to the computer, ethernet router or hub that will be using the IDU to access the satel-lite network. Environmental conditions must stay within the product specifications.

3.2.2 Step 2. Making Power and Cable Connections

Make power and cable connections as follows.

1. Connect the coaxial IFL cables from the ODU to the back of the IDU. For adescription of the IDU back panel, see section 2.3.

• Attach the coaxial cable labelled "LNB" (Rx) to the connector labelled IDU IN.

• Attach the coaxial cable labelled "Transmitter" (Tx) to the connector labelled IDUOUT.

2. Connect one end of ethernet cable to the computer's RJ-45 ethernet port, and connectthe other end to the 10/100 BaseT connector on the back of the IDU.

3. Connection to a GPS device: the IDU needs to know its location while operating inDVB-RCS. This step is not required when operating in SCPC. So only do this stepfor DVB-RCS operation (with the proper DVB-RCS software loaded in). Connect aserial cable between the serial port of the IDU and a GPS. The IDU interface to



851674 P01

external GPS device is done via a rear panel DB9-F connector. All signals are RS-232C +/- 5V unless noted otherwise. It’s pin-out can be found in the Table 3.1

Table 3.1 Serial Port Connector PIN-OUT

4. Connect the IDU to the AC power source. The IDU runs on 110-220 VAC, 50/60 Hz(auto-ranging).

5. Verify that the Power LED is illuminated on the front of the IDU (the left-most LEDon the front of the IDU). After a few seconds, the Ready LED should be illuminatedas well (the second LED from the left on the front of the IDU).

6. The IDU is put into HOLD mode before leaving the factory, so make sure that theReady LED is flashing, indicating that the IDU is currently in HOLD mode. When inHOLD mode, transmission is disabled. The IDU will remain in HOLD mode until it isput out of HOLD mode by the user. The IDU will remain in HOLD mode even after areboot or power cycle. It is the user’s resposibility to put the IDU out of HOLD modewhen it is properly configured, thus avoiding disturbing the Network. One of the verylast step of the IDU instllation/configuration is to put the IDU out of HOLD mode.

Note: When screwing the cables to the connectors, be sure to turn only the outerrotating nut of the connector. The cable and the main body of the connector mustnot rotate or twist. Hand tighten only.

3.3 Accessing the IDU Web InterfaceThe next step in installation is to access the IDU web interface. This web interface is usedfor monitoring and configuring the IDU.

The IDU is factory configured with the default Ethernet IP address 10.10.10.10 and subnetmask of 255.255.255.0. Initial access of the IDU home page must be made at this address.To do this, open the web browser on the computer and type the address <http://10.10.10.10>. The IDU home page appears.

Pin No. Function Note

1 DCD

2 TX

3 RX

4 DTR

5 GND

6 TUNER_LOCK0-5VDC signal limited to 2 mA, switches to ground when IDU DVB tuner acquires lock

7 RTS

8 CTS

9 +24V WARNING: Be careful to not damage your equipment. Limited to 200 mA by IDU.



851674 P01

Note: If the computer is unable to open the IDU home page, it may be necessaryto temporarily modify the computer's IP address so that it is in the correct range toaccess the IDU. For instructions about how to do this, consult Windows on-linedocumentation. After communication with the IDU has been established, theIDU’s ethernet IP address can then be changed to an address accessible from thecomputer, and the computer's IP address can be changed back to its normalsetting.

The IDU home page is used to log in to IDU web pages. The home page can be accessedfrom any IDU web page by clicking the Login link near the upper left corner of the page.

Note: For access to the IDU’s web page over the satellite network, the SIT’s OAMIP address must be used. The factory default OAM IP address is 172.16.0.1.

Figure 3.1 IDU Web Interface Home Page

3.3.1 SSL Secure HTTP Access

This section only applies to IDU HW platforms 850643-365 (series 5420V).These IDUs contain an encryption chip.

Access to IDU web pages is encrypted using SSL 2.0 and 3.0. Some browsers and Win-dows operating systems use a short (30 second to 2 minute) default time-out for encrypted



851674 P01

web pages. This means that after a short period of inactivity, the user will be required tolog in again. Typically, a longer time-out will be more convenient for IDU configuration.

The time-out can be set at up to 30 minutes (the maximum time-out for the IDU). The fol-lowing procedure describes how to modify the time-out in a registry setting of InternetExplorer. This procedure can be used in computers running Windows ME or later (it is notapplicable to Windows 98).

Warning: Incorrectly editing the registry may severely damage youroperating system.

1. Start the Registry Editor (Regedit.exe).

2. Locate and click the following key in the registry:

HKEY_LOCAL_MACHINE\System\CurrentControlSet\Control\SecurityPro-viders\SCHANNEL

3. On the Edit menu, click Add Value.

4. Type ClientCacheTime, click the REG_DWORD data type, and then click OK.

5. In the Data box, type a decimal value in milliseconds, and then click OK. Forexample, a value of 1800000 (decimal) corresponds to a time-out of 30 minutes.

Note: Keys are not displayed in the registry unless you change them from theirdefault values.

For more information about the IDU web interface, see section 2.4.

3.4 Steps for Basic IDU Installation and Configuration

Note: If a configuration file was provided with the IDU, follow the instructions thatcame with this file before accessing the Installer Menu.

PLEASE THIS SECTION ENTIRELY BEFORE STARTING THE INSTALLATION/CONFIGURATION.

The Superuser Menu of the IDU web interface is used to set installation parameters for theSIT. The Superuser Menu is accessed from the IDU web interface Home Page by loggingin as follows:

Username: superuser

Password: su001pwd (factory default password)

The Superuser Menu contains Configuration Links along the left side. A typical installa-tion procedure is as follows:



851674 P01

1. Use the File Management link to upgrade to the latest (or desired) software version,and/or to load a pre-configured configuration file. Proceed to section 3.5 if an upgradeis required.

2. Use the Installation link to set installation parameters (section 3.6).

3. Use theSCPC Configuration link to set the Tx and Rx parameters (section 3.7).

4. Use the Network Configuration link to set the network parameters (section 3.8).

5. Use the IDU Control link to put the IDU out of HOLD mode (section 3.9) This stepshould only be done when you are ready to transmit using the appropriate parameters.You should also refer to section 3.9 if you need to put up a CW carrier during theinstallation process.

6. Use the Test Control link to access the test mode and be able to transmit a CW carrier,when required during the installation process.

7. If so desired, you can change the Superusaer password for added security (section3.11), make sure to memorize the password.

You can monitor the current status of the SIT during the installation procedure. For moreinformation, see section 5.

3.5 File ManagementThe IDU can send files to and receive files from an FTP server. The FTP server can be ona computer directly connected to the IDU, on a LAN, or accessed over the satellite net-work. This feature is useful for:

• Upgrading the IDU's software (see section 3.5.2).

• Transferring configuration files to and from the IDU (see section 3.5.3 and section3.5.4).

For security reasons, the IDU is not capable of browsing the FTP server. It can only sendor receive specific files in a particular directory of the FTP server.

Before you can send or receive files, you must configure the IDU to access an FTP server(see below).

3.5.1 Configuring Access to an FTP server

Use the File Management page to configure the IDU to access an FTP server.

Four parameters must be configured.

• Server Username. Enter the username used to log in to the FTP server.

• Server Password. Enter the password used to log in to the FTP server.

• Server IP Address. Enter the IP address of the FTP server.

• Server Path. Enter the path, if any, of the files located on the FTP server using for-ward slashes (“/”). This is the path that any FTP client with the username set abovewould see.



851674 P01

When you are done, click Save FTP Configuration. The FTP configuration is activeimmediately.

Note: The server IP address defines where the IDU will take the new softwareimage. This IP address must be accessible by the IDU, whether at the userinterface or remotely over the satellite interface.

3.5.2 Upgrading Software

A software upgrade may be performed as part of a regular maintenance procedure, forproblems fixes or for new features available in the IDU.

General Comments Concerning Software Upgrades

Normally, performing a software upgrade is straight forward and low risk, since the IDUhas a fail-safe mechanism to prevent corruption. However, there has been cases of fail-ures. To mitigate the risk of a software failure, follow these suggestions:

• When possible, perform the software upgrade during a low internet traffic period.

• When possible, local software upgrades are preferred to remote software upgrades.

•

Software Upgrade Using The Web Page

The software upgrade functionality is available through the File Management web page ofthe Installer menu. It is also available in the Superuser menu.

The IDU contains two versions (or images) of the software, a current image which is theone in use and an alternate image. These software versions are shown in the S/W IMAGEID section of the page.

Follow this procedure to upgrade IDU software.

1. Ensure that the software upgrade file (e.g. “IDUv9620r00.sit”) is located on the FTPserver.

2. Ensure that the IDU has been configured to access the FTP server with the correctpath (see section 3.5.1 above).

3. In the S/W Image Filename field, enter the name of the software upgrade file (e.g."IDUv9620r00.sit"). Next, click Save S/W Image Filename.

4. FTP Transfer of the software image: Click the Download S/W Image button to begindownloading software from the FTP server to the IDU. The IDU will verify that thefile is an IDU software file before it begins downloading. You can monitor theprogress of the download. During this time, you cannot download any other files.

5. Click Reboot From Alternate. The IDU will reboot using the newly downloadedsoftware version.



851674 P01

6. Return to the File Management page and click Validate S/W Image. This indicates tothe IDU that the upgraded software was installed and runs correctly. As a fail-safemechanism, if you do not validate the new software version within 10 minutes ofrebooting, the IDU will automatically reboot with the previous (alternate) softwareversion.

If you wish to run the previous (alternate) software version, click Reboot from Alternate.

3.5.3 Transferring Configuration Files

It is easy to download a new configuration file to the IDU. You can also upload, or export,the IDU's configuration file to the FTP server for use on other IDUs. These tasks are doneusing the File Management page.

To download a new configuration file to the IDU, first ensure that the new configurationfile is named “sitcfg.xml” and is located on the FTP server path configured above. Then,click Download sitcfg.xml.

To upload the IDU's configuration file to the FTP server, click Upload sitcfg.xml. Thesitcfg.xml file will be transferred to the FTP server.

3.5.4 Delta Configuration

Delta configuration changes are applied to the IDU using the delta.xml configuration file.

Transfer Procedure

1. Ensure that the delta.xml file is located on the FTP server (see section 3.5.3).

2. Ensure that the IDU has been configured to access the FTP server with the correctpath (see section 3.5.1).

3. Transfer the delta configuration file to the IDU by clicking Download delta.xml onthe File Management page.

4. Apply the delta configuration by clicking Apply Delta Config and Reboot on theFile Management page.

If one or more Delta Configuration parameters is incorrect, the first error found in thedelta.xml file will be displayed, once the button "Apply Delta Configuration and Reboot isselected. A message similar to the following will appear:



851674 P01

The error should be corrected in the delta.xml file and the Transfer Procedure re-starteduntil all the errors are cleared and the option to Reboot appears.

3.5.5 Configuration Backup and Restore

SIT configuration information is contained in a configuration file (sitcfg.xml) stored inter-nally on the IDU. The IDU writes all configuration changes to this file, and it reads thisfile when it reboots.

This configuration file is automatically saved as sitcfg.old when the IDU reboots. Whenthe IDU boots up, it checks whether the current configuration file (sitcdg.xml) containsvalid values for all parameters. If the it is not valid, the IDU automatically restores thesitcfg.old and reboots from it.

When the user calls "Downloads sitcfg.xml", the file sitcfg.old is saved the backup file(sitcfg.bak). The user can force a restore and reboot from the backup configuration. Thiscan be used when the downloaded configuration is not working as expected to revert to thestate before the las reboot.

In order to restore and reboot from the backup configuration, go to the File Managementpage and click Reboot with Backup Configuration.

Note: The backup doesn't work in the case of a delta config.

IDU NAME:

MAC ADDRESS:

S/W REVISION:

SIT_Default_Name

00-40-fd-01-ef-a0 .

V4001.R00

Login Installer Menu Result

Error occured while processing the Delta Config file.

First error found: Data error at line 15

Use the above browser menu to return to previous page or

Return To Previous Page



851674 P01

3.6 Installer Configuration

The Installation Configuration page is used to view and modify the SIT's installationparameters.

Follow this procedure to configure installation parameters for your site.

1. Carefully review all the parameters on this page and modify them according to yourinstallation, as described in the table below.

2. When you are done, click the Save Installation Configuration button at the bottomof the page. This opens the Installer Menu Result page.

3. You must reboot the IDU for the installation configuration to be implemented on theIDU. Click Reboot IDU, the IDU will reboot (this takes about 1 minute), and youwill be returned to the IDU home page.



851674 P01

Some parameters in the following table must be configured for each installation, others areoptional, and others must not be changed from their default values.

Parameter Description

Installation Owner Name of the installation owner.

Installation Date and Work Order Number Installation date and work order number of the installation.

Satellite Service Provider ID Identity of the satellite service provider.

SIT Name

Label for the SIT being configured. This label will appear at the top of the web interface window and in the web browser title bar. It is useful to identify the web interface for each SIT with a different label when using multiple SITs simultaneously on the same LAN.

ODU Antenna SizeODU Antenna size in cm. This parameter is for informational use only and is not employed by the IDU. The factory default setting is “89”.

ODU SSPA PowerODU sub-system power amplifier (SSPA) power in 0.1 W steps. This is for informational use only and is not employed by the IDU. The factory default setting is “20”.

ODU Maximum EIRP

ODU Maximum effective isotropic radiated power (EIRP) in 0.1 dBm steps. This is for informational use only and is not employed by the IDU.The factory default setting is “740”.

RL RF Spectral Inversion

This flag is used to control the RL RF spectrum. The IDU will invert the RF spectrum when the flag is set to "Enabled" and not invert the RF spectrum when set to "Disabled".The default value is "Disabled".

ODU Tx mixing frequency

The ODU Tx mixing frequency (in MHz) is added to the IDU Tx frequency to obtain the SIT Tx frequency.If the test mode is enabled, it should be stopped before changing the ODU Tx mixing frequency.The factory default setting is "13050", which corresponds to a 13.05GHz mixing frequency in the ODU (Ku band output).

ODU Rx Low/High Band Frequency Threshold

Threshold for the Rx low-high band at Ku band. A frequency below the threshold will be in the low band. A frequency above the threshold will be in the high band. The factory default setting is “11700”.

ODU Rx Low Band Mixing Frequency

The ODU Rx low band mixing frequency (in MHz) is subtracted from the SIT Rx frequency in Ku band to obtain the IDU Rx frequency in L band (if in low band). The factory default setting is “9750”.

ODU Rx High Band Mixing Frequency

The ODU Rx high band mixing frequency (in MHz) is subtracted from the SIT Rx frequency in Ku band to obtain the IDU Rx frequency in L band (if in high band). The factory default setting is “10600”.



851674 P01

Table 3.2 Description of Installation Configuration Parameters

When you have finished modifying these parameters, click Save Installation Configura-tion at the bottom of the section. This opens the Installer Menu Result page. Dependingon the combination of parameters that you changed, you may be required to perform anaction before the changes take effect (see Appendix C).

ODU Present flag

With the ODU present flag enabled, the following actions will be taken by the IDU:• The IDU will compensate for the frequency error caused by the ODU• 24 V DC will be present at the IDU OUT port of the IDU to supply

voltage to the ODU SSPA• 13/18 V polarisation selection for the ODU LNB• 22 kHz on/off for High/Low frequency band selection for the LNBWith the flag disabled, the IDU is used mainly in a lab environment (IF). The factory default settings is “Enabled”.

ODU Tx 24V DC Flag

This parameter determines if the IDU can output 24 DC at its Tx port.

Note: This flag has the behaviour described above onlyif the ODU present flag is enabled, if not, the Tx port 24DC is always off

The factory default settings is “Disabled”.

Operation with Deployable Antenna Flag

This parameter specifies if the IDU shall inhibit transmission of the 22 kHz tone and the DC voltage on the IDU Rx port.

If a deployable antenna is used, then this parameter shall be set to "Enabled" for the IDU to completely inhibit transmission of the 22 kHz tone, regardless of the frequency band selected on the FL. Also, the DC voltage on the Rx port is set to 0V, regardless of which polarisation was selected. If a normal fixed antenna is used, then this parameter should be set to "Disabled", the IDU will operate as usual by generating on its Rx port the 22 kHz tone or not, depending on the frequency band selected, as well as the 13/18VDC voltage, depending on the polarisation selected.

The factory default setting is "Disabled".

Low Power Mode Flag

When the low power mode is enabled, the ODU transmit power is ON only when the IDU is logged on. If this mode is disabled then the ODU transmit power is always on.

Note: This flag has the behaviour described above onlyif the ODU present flag is enabled, if not, the ODUtransmit power is always off.

The factory default settings is “Enabled”.




851674 P01

3.7 SCPC ManagementThe SCPC Management page is used to configure the SCPC parameters.



851674 P01

For a description of how parameters in the table are coded, see Appendix B.


SCPC Rx Frequency (kHz)

This parameter specifies the forward link default frequency (in kHz) and shall be specified in terms of the ODU receiving frequency (e.g. Ku band). The frequency must be entered in multiples of 125 kHz.The factory default setting is "11450000".

SCPC Rx Symbol Rate (100 symbols/sec)

This setting specifies the Symbol rate, in 100 Symb/s when the SCPC mode is selected.The factory default setting is "40000".

SCPC Rx Coding Rate

This setting specifies the Rx coding rate when the SCPC mode is selected. Available coding rate: - Auto-Rate Setting; - R=1/2; - R=2/3; - R=3/4; - R=5/6; - R=7/8.The factory default setting is "Auto-Rate Setting".

SCPC Rx Unicast Traffic PID

This parameter specifies the PID for the unicast IP traffic that the IDU will filter on when the SCPC mode is selected.The factory default setting is "0".

Rx CRC Check Bypass Flag

When in CRC check bypass, MPEG sections are received without CRC check being made. When not in CRC bypass, MPEG sections are received only if CRC matches the proper computed value.

SCPC Tx Frequency (kHz)

This parameter specifies the Tx Frequency (in 100Hz) when the SCPC mode is selected.The factory default setting is "11700".



851674 P01

Table 3.3 SCPC Configuration Parameters

SCPC Tx Modulation & Coding Rate

This parameter specifies the Tx Modulation & Coding Rate when the SCPC mode is selected. Available Tx Modulation & Coding Rate are: - S2 QPSK 1/4 - S2 QPSK 1/3 - S2 QPSK 2/5 - S2 QPSK 1/2 - S2 QPSK 3/5 - S2 QPSK 2/3 - S2 QPSK 3/4 - S2 QPSK 4/5 - S2 QPSK 5/6 - S2 QPSK 8/9 - S2 QPSK 9/10- S2 8PSK 3/5- S2 8PSK 2/3- S2 8PSK 3/4- S2 8PSK 5/6- S2 8PSK 8/9- S2 8PSK 9/10

The factory default is S2 QPSK 1/2.

SCPC Tx Symbol Rate ( symbols/sec)

This parameter specifies the Tx Symbol Rate when the SCPC mode is selected.The factory default setting is “64000”.

SCPC Tx Roll-off Factor

The roll-off factor determines how tight the occupied bandwidth will be. The possible values are 0.35, 0.25 and 0.20.The factory default is “0.35”.

SCPC Tx Pilot

The pilot are symbols added at regular interval to help synchronization. They are usually used in low SNR/low symbol rate situations.The possible values are ON or OFF.The factory default is OFF

SCPC Tx S2 Frame Length

The possible values are:Short Frame, 16200 bitNormal Frames, 64800 bit

The factory default is Short Frames.

SCPC Tx Power Level (dBm)

This parameter specifies the Maximum transmit IF power level used by the IDU. The IDU output level is expressed in dBm. The range is from 0 to -31.5 dBm. The level corresponds to attenuation that is relative to an output of 0 dBm.The factory default value is set to "-31.5".

SCPC Tx Unicast Traffic PID

This parametr specifies the PID for the unicast IP traffic that theIDU will transmit when the SCPC mode is selected.The factory default setting is "0".



851674 P01

When you have finished modifying these parameters, click Save SCPC Configuration atthe bottom of the page. This opens the Menu Result page. Depending on the combinationof parameters that you changed, you may be required to perform an action before thechanges take effect (see Appendix C).



851674 P01

3.8 Network ConfigurationThe Network Configuration page enables you to view and modify SIT IP addresses, SITpopulation ID, and related parameters. The SIT makes use of two IP addresses.

• The ethernet interface IP address is the user interface IP address on the ethernet port(see section 2.3). This IP address and mask is for the user LAN (terrestrial network)connected directly to the IDU.

• The satellite interface OAM (operation, administration and maintenance) IP addressis the SIT IP address of the satellite interface. It is used for SIT management (OAM)purposes.

The table below describes the parameters in the Network Settings section of the page.


SIT Ethernet I/F IP Address

IP address on the ethernet interface port, used by the user LAN (terrestrial) network connected directly to the IDU. The factory default setting is “10.10.10.10”.

SIT Ethernet I/F IP Mask

Associated net mask for SIT ethernet I/F address. This mask determines the SIT LAN subnet. The factory default setting is “255.255.255.0”.

SIT Satellite I/F OAM IP Address

The SIT IP address on the satellite interface. It is used by the hub for SIT management (OAM) purposes. The factory default setting is “172.16.0.1”.

SIT Satellite I/F Traffic IP Address

Address only employed for traffic IPSec tunnelling.The factory default setting is "60.47.47.47".

OAM Release Timeout (msec, 0 = no timeout):

OAM VCC will be released if no OAM data is transmitted for the duration of the timeout (in msec). This timer is valid only when the SIT state is "OamActive". If the time expires, the SIT state will then go from "OamActive" to "Initialized". A value of "0" disables the timeout.The factory default setting is "0".

Traffic Release Timeout (msec, 0 = no timeout):

Traffic VCC will be released if no traffic is transmitted for the duration of the timeout (in msec). This timer is valid only when the SIT state is "Active". If the time expires, the SIT state will then go from "Active" to "OamActive". A value of "0" disables the timeout.The factory default setting is "0"

PEP Enable Flag

The Performance Enhancing Proxy (PEP) is activated by selecting Enabled for this flag.The PEP accelerates all TCP traffic when this flag is Enabled. The factory default setting is “Disabled”.

Note: see section 4.7 for more details on the PEP.

High priority IP packet timeout (msec)

This parameter specifies the timeout value for the IP packets of the high priority queue. The value is specified in msec. The factory default setting is “4000”.

Table 3.4 Network Settings Parameters



851674 P01

When you have finished modifying these parameters, click Save Network Configurationat the bottom of the page. This opens the Menu Result page. Depending on the combina-tion of parameters that you changed, you may be required to perform an action before thechanges take effect (see Appendix C).

Low priority IP packet timeout (msec)

This parameter specifies the timeout value for IP packets of the low priority queue. The value is specified in msec. The factory default setting is “4000”.


Table 3.4 Network Settings Parameters



851674 P01

3.9 IDU ControlYou can control a SIT's access to the satellite network using the IDU web interface. Usethe IDU Control page to:

• Enter or leave the HOLD State.

• Set IDU Carrier ON or OFF.

• Reboot the IDU.

3.9.1 Disabling and Enabling Transmission (HOLD State)

The HOLD state is a state where the IDU transmission is disabled. The HOLD State sur-vives a reboot or a power cycle, so the only way to get out of the HOLD State is by doingthe Return Link Enable command.

There are two control buttons related to HOLD State:

• Return Link Enable - Leaving HOLD State.

• Return Link Disable - Entering HOLD State.

The IDU leaves the factory configured in HOLD State in order to prevent any undesiredtransmission. Part of the installation process, the IDU will be put out of HOLD State(Return Link Enable) by the installer when the Tx parameters are properly configured.

It is also a good practice to put the IDU in HOLD State while modifying Tx parameters,minimizing the risk of generating interference.

3.9.2 Carrier ON and Carrier OFFl

The transmission off the IDU can be interrupted momentarely by using the Carrier On/Offcontrol buttons.

The Disable IDU Tx - Carrier OFF button disable the carrier on the IDU Tx port. TheEnable IDU Tx - Carrier ON button puts it back.

The Carrier OFF doesn’t survive a reboot nor a power cycle - the IDU will come backwith Carrier ON.

3.9.3 Reboot

The Reboot control button can be used to reboot the IDU, if it was necessary.

Note: The IDU will return in HOLD State after the reboot if it was in HOLD Stateprior to the reboot.



851674 P01

3.10 Test Control

Warning: Test control commands should not be used in normal operation ofthe SIT. They must only be used with specific test procedures obtained fromthe service provider. Unauthorized or incorrect use of these commands maydisrupt the satellite network.

The Test Control page enables the installer to test the SIT's access to the satellite networkReturn link.

This page contains the following sections.

• Test Control

• Power Level

• Default IF Power Level

• Actions

3.10.1 Test Control

Use the Test Control section to execute a test of the SIT's access to the satellite network'sreturn link. The table below describes the parameters in this section.


Table 3.5 Test Parameters


Test Mode

Three test modes are available.• CW: This command will produce a continuous wave signal (unmodu-

lated) at the desired frequency. This feature is useful at installation time.• CM: This command will produce a continuous QPSK modulated signal.• NONE: This command stops the test if a test signal is in progressThe factory default setting is “CW”.

Symbol Rate (in KSymbol/s)

The symbol rate of the test signal. This only need to be selected for CM test mode.The factory default setting is “0”.

Output Frequency

All tests require the output frequency to be selected. The frequency is entered in multiples of 100 Hz. Frequency compensation will be accurate in test mode as well, provided an ODU is connected and the forward link is present and stabilized.Setting the frequency to “0” will stop the test mode and the IDU will therefore return to its normal mode of operation (re-acquiring the forward link, etc.…).The factory default setting is “0”.



851674 P01

Notes about test control:

• It is always safer to turn the IDU off when working at the antenna. However, the“Disable IDU Tx” button can be used to shut off the IDU output in order to work infront of the antenna.

• Reboot is not required when going from test mode to normal mode.

• The initial test command set will use the last configured power level. Subsequently,all the test commands will use the current power level setting.

• Click the Execute button to begin testing. To stop the test, enter “NONE” for testmode or “0” for output frequency and click Execute.

3.10.2 Power Level

Use the Power Level (dBm steps) parameter to set the power level for the current test.

The IDU output level is expressed in dBm. The range is from 0 to –31.5 dBm. The levelcorresponds to attenuation that is relative to an output of 0 dBm. The factory default valueis set to “0”.

Type in an appropriate power level, then click Set.

3.10.3 Default IF Power Level

Use the Default IF Power Level (dBm steps) parameter to set the maximum power levelfor the IDU. This is the maximum transmit IF power level used by the IDU. Type in anappropriate power level, then click Save Default Power IF Level.

3.10.4 Actions

You can disable the transmission of the SIT, but transmission is automatically enabledafter a reboot of the IDU. To do this, click the Disable IDU Tx button. The transmissionwill remain disabled until you click the Enable IDU Tx button or the IDU is rebooted.This may be helpful during installation.

3.11 Superuser Password ConfigurationUse the Superuser Password Configuration page to change the password used to accessthe Superuser Menu. It is recommended that you change this password from the factorydefault.

The Superuser password can be changed as follows.

1. Type the existing password in the Old Password field. During installation, this istypically the factory default password “ins001pwd”.

2. Type a new password in the New Password field.

3. Retype the new password in the Retype New Password field.

4. Click Change Password to implement the change.



851674 P01

Note: This is the final step in a basic IDU installation. If the IDU has beensuccessfully installed, the next task is to configure, if required, the Advancedoptions (see Chapter 4).



851674 P01

Chapter 4 Advanced Configurations

This section covers the various advanced options available for the IDU. The options are:

• Ueque Management (QoS)

• Routing Management

• DHCP Management

• Multicast Configuration

• MIB Trap

• MIB Access Policy

• PEP

• Web Page Logo

• Forward Link Control Management (FLCM) - Web page link Multicast Configura-tion

4.1 Queue ManagementThe IDU implements a scheme for Quality of Service (QoS). QoS is a feature that priori-tizes selected types of traffic to achieve higher service performance. Real time applica-tions, such as Voice over IP (VoIP), are intolerant of latency or delay and as a result QoSis an essential feature for wireless multimedia transmission.

To configure QoS on the IDU, simply assign a queue to each type of traffic coming fromthe PC or LAN, then assign a different priority to each queue. You can also use the queuesto separate the OAM traffic from the host LAN traffic.

By default, the IDU is configured with a single traffic queue. This means that the IDUrelays stored data over the return link in the order in which it is received, in a first-in first-out fashion.



851674 P01

The figure below shows a typical setup in which queues are used. You can assign VoIPtraffic to queue 1 and Internet traffic to queue 2, and then specify that all queue 1 trafficmust have priority over any queue 2 traffic. In this way, you can ensure that VoIP serviceis not degraded or interrupted by file transfers or other activity elsewhere on the LAN.

Figure 4.1 Typical Configuration of Traffic Queues

Use the Queue Management page to configure traffic queues. Traffic queues are config-ured in three steps.

1. Define traffic queues (section 4.1.1).

2. Select Filter Pattern Table Configuration settings (section 4.1.2)

3. Apply filter patterns to direct traffic into each queue (section 4.1.3).

4.1.1 Step 1. Define Traffic Queues

Traffic queues are defined in a queue table, where each entry in the table corresponds to atraffic queue.

To view which traffic queues have already been defined, scroll down the Queue Manage-ment page to the Queue Table Configuration field. To view the properties of a queue(table entry), click on an entry in the drop-down box and review the fields below the box.To delete a queue, click on the entry in the drop-down box, then click Delete This QueueTable Entry.

By default, there is a single queue table entry. To add a new queue table entry, click Cre-ate a new Queue Table Entry. This takes you to the Menu Result page, which displaysthe entry number of the queue you have just created. Next, return to the Queue Manage-ment page, and be sure to refresh the display to see the new queue table entry just created(to do this, click the Refresh button in your browser).

Once a queue table entry has been created, you must define properties for the queue. Amaximum of four queues can be defined, a high priority traffic queue and low priority

Voice over IPtraffic Internet traffic

To ODU and return link



851674 P01

traffic queues. The parameter “Quality of Service Priority Weight” determines the priorityof the queue. The traffic in the high priority queue will have priority over the traffic in thelow priority queue as explained in the two following examples.

If the high priority traffic has to take absolute precedence on the low priority traffic (strictpriority), the “Quality of Service Priority Weight” should be set to “1” for the high priorityqueue, and “0” for the low priority queue.

To avoid starvation of the low priority traffic, in the case where there is both a low and ahigh priority queue, it is best to configure the priority weight as follows:

• high priority queue priority weight = 6;

• low priority queue priority weight = 2.

In this case 75% of the allocations will be assigned to the high priority queue (6/(6+2) and25% will be assigned to the low priority queue (2/(6+2).

Other weights can be used, to match the desired QoS characteristics.

If the queues use the same priority weight (both “0” or “1”), then no priority differencewill be made by the IDU and it will send the data in the order in which they are received.

High priority packets use the high priority time-out to define how long the packets remainin the SIT's transmit buffer; while low priority packets use the low priority time-out.

The table below describes the parameters in queue table entries.

Table 4.1 Queue Table Entry Parameters

When you have finished modifying these parameters, click Save This Queue TableEntry. This opens the Superuser Menu Result page. Depending on the combination ofparameters that you changed, you may be required to perform an action before the changestake effect (see Appendix D).

4.1.2 Step 2. Select Filter Pattern Table Configuration settings

Once queues have been created in the queue table, the filter pattern settings must beselected in the Filter Pattern Configuration table. The setting is either “Mask “or “Range”.

This setting is applicable to three filter pattern parameters:

• Tos Field Type


Quality of Service Type Reserved for future use.

Quality of Service Priority Weight

Queues configured with the same priority weight have an equal opportunity to transmit data. The factory default setting is “0”.

Queue status“Not in Service” indicates that the queue has been disabled. “Active” means that the queue is operational. The factory default setting is “Active”.



851674 P01

• Udp Src Port Number Type

• Udp Dst Port Number Type

They will be defined by a range of addresses going from the minimum to the maximumvalue if the setting “Range” is selected or by a subnet if “Mask” is selected.

4.1.3 Step 3. Apply Filter Patterns

Once filter pattern settings have been selected in the Filter Pattern Configuration table, fil-ter patterns must be defined and applied in order to direct certain types of IP traffic intoeach queue. One filter pattern should be defined for each queue. Filter patterns can also beused to block data from being transmitted over the satellite network.

Note: To avoid ambiguity, it is recommended to configure a filter pattern for theOAM IP address of the IDU.

Filter patterns are defined in a filter pattern table, where each entry in the table corre-sponds to a filter pattern.

To view which filter patterns have already been defined, go to the Filter Pattern TableConfiguration section of the Queue Management page. To view the properties of a filterpattern (table entry), click on an entry in the Filter Pattern Table Configuration drop-down box and review the fields below the box. To delete a filter pattern, click on the entryin the drop-down box, then click Delete This Filter Pattern Table Entry.

By default, there is a single filter pattern table entry. To add a new filter pattern tableentry, click Create a new Filter Pattern Table Entry. This takes you to the Menu Resultpage, which displays the entry number of the filter pattern you have just created. Next,return to the Queue Management page, and be sure to refresh the display to see the newqueue table entry just created (to do this, click the Refresh button in your browser).

Once a filter pattern table entry has been created, you must define properties for the filterpattern. In general, you will want to filter traffic based on the source and/or destination IPaddresses of the traffic. This is done by specifying the following IP addresses of the traf-fic:

• Source IP address

• Source IP netmask

• Destination IP address

• Destination IP netmask

In the VoIP example above, filter pattern 1 includes only traffic from the VoIP computer.This is done by setting the filter pattern to include the source IP address of the VoIP trafficand a source IP netmask of 255.255.255.255. The destination IP address and netmaskshould be set to 0.0.0.0 (traffic is not filtered by destination IP address). Filter pattern 1 isthen assigned to the high priority queue.



851674 P01

Filter pattern 2 includes all other traffic. This is done by assigning all IP addresses andmasks a value 0.0.0.0 (traffic is not filtered by source or destination IP address). Filter pat-tern 2 is then assigned to the low priority queue.



851674 P01

The table below describes the parameters in the filter pattern table entries.


IP Source Address The source IP address segment that will be allowed by the filter. A mask value 0.0.0.0 indicates that traffic is not filtered by IP source address. A mask value 255.255.255.255 indicates that only traffic from the IP source address is allowed by the filter. The factory default setting is “0.0.0.0”.

IP Source Mask

IP Destination Address

The destination IP address segment that will be allowed by the filter. A mask value 0.0.0.0 indicates that traffic is not filtered by IP destination address. A mask value 255.255.255.255 indicates that only traffic from the IP destination address is allowed by the filter. The factory default setting is “0.0.0.0”.

IP Destination Mask

IP Protocol Type The IP protocol type range that will be allowed by the filter. A mask value of 0x00 indicates that traffic is not filtered by protocol type. A mask value of 0xFF indicates that only traffic from this protocol type is allowed by the filter. The factory default setting is “0x00”.

IP Protocol Type Mask

IP TOS Field Mini-mum Number

The IP Type Of Service range that will be allowed by the filter. A mask value of 0x00 indicates that traffic is not filtered by type of service. A mask value of 0xFF indicates that only traffic from this type of service is allowed by the filter.

Note: This is only displayed when the Tos Field Type isRange.

The factory default setting is “0x00”.

IP TOS Field Maxi-mum Number

IP TOS Field The IP Type Of Service range that will be allowed by the filter. A mask value of 0x00 indicates that traffic is not filtered by type of service. A mask value of 0xFF indicates that only traffic from this type of service is allowed by the filter.

Note: This is only displayed when the Tos Field Type isMask.


IP TOS Field Mask

TCP/UDP Minimum Source Port Number

The TCP/UDP Source Port Number range that will be allowed by the filter. A mask value of 0x00 indicates that traffic is not filtered by TCP/UDP source port. A mask value of 0xFF indicates that only traffic from this TCP/UDP source port number is allowed by the filter.

Note: This is only displayed when the Udp Src PortNumber Type is Range.


TCP/UDP Maximum Source Port Number



851674 P01

Table 4.2 Filter Pattern Table Entry Parameters

When you have finished modifying these parameters, click Save This Filter PatternTable Entry. This opens the Superuser Menu Result page. Depending on the combinationof parameters that you changed, you may be required to perform an action before thechanges take effect (see Appendix D).

TCP/UDP Source Port Number

The TCP/UDP Source Port Number range that will be allowed by the filter. A mask value of 0x00 indicates that traffic is not filtered by TCP/UDP source port. A mask value of 0xFF indicates that only traffic from this TCP/UDP source port number is allowed by the filter.

Note: This is only displayed when the Udp Src PortNumber Type is mask.


TCP/UDP Source Port Number Mask

TCP/UDP Minimum Destination Port Number

The TCP/UDP Destination Port Number range that will be allowed by the filter. A mask value of 0x00 indicates that traffic is not filtered by TCP/UDP destination port. A mask value of 0xFF indicates that only traffic from this TCP/UDP destination port number is allowed by the filter.

Note: This is only displayed when the Udp Dst PortNumber Type is Range.


TCP/UDP Maximum Destination Port Number

TCP/UDP Destina-tion Port Number

The TCP/UDP Destination Port Number range that will be allowed by the filter. A mask value of 0x00 indicates that traffic is not filtered by TCP/UDP destination port. A mask value of 0xFF indicates that only traffic from this TCP/UDP destination port number is allowed by the filter.

Note: This is only displayed when the Udp Dst PortNumber Type is Mask.


TCP/UDP Destina-tion Port Number Mask

Filter Pattern Sit Queue Table Entry Number

Assign the filter pattern to a queue table entry previously defined (see section 4.1.1 above). The factory default setting is “1”.

Filter Pattern Status“Not in Service” indicates that the filter pattern has been disabled. “Active” means that the filter pattern is operational. The factory default setting is “Active”.



851674 P01

4.2 Routing ManagementThe IDU’s routing feature enables the SIT to support multiple local LANs (subnets).

The default gateway of the IDU is its satellite interface, so any traffic processed by theIDU will be sent over the air (satellite network) unless the destination IP address of thepacket falls in the range of the IDU’s ethernet interface IP segment, in which case the traf-fic is sent to the IDU’s ethernet port (IDU ethernet LAN).

However, it is possible to use the IDU’s routing feature to route traffic that does not fall inits ethernet interface IP segment to its ethernet interface. This traffic is then forwarded to arouter on the IDU’s ethernet interface LAN. The router then forwards the packet toanother LAN. This permits the use of multiple LANs behind the IDU.

The IDU supports two types of routing:

• Static Routing (section 4.2.1)

• Dynamic Routing (section 4.2.2)

Both are configured through the Routing Management page.

The current routing configuration is reflected in the Current Routing Table. Each entryin the table represents a route: the Control column will indicate User for a static route andNetwork for a dynamically controlled route.

Note: For the Hub to forward any internet traffic to a host located behind a routerat the IDU side, it must have its routing table manually updated. There is currentlyno provisioning done between the IDU and the Hub to automatically update thehub’s routing information with respect to the IDU’s routing table (whether the IDUrouting is static or using RIP)



851674 P01

4.2.1 Static Routing

Static routes are configured using the Static Route Table Configuration section of theRouting Management page. Table 4.3 describes the parameters for configuring static rout-ing.

Table 4.3 Static Routing Management

Use the Submit button to apply the requested change to the Routing Table.

Figure 4.2 shows an example of a typical set-up on the IDU LAN. In this example, theRouting Management page is used to configure the IDU to statically route any traffic des-tined to host network 1 through router 1.

Note: Routes should only be added for the IDU’s ethernet interface. Thegateways (routers) should be configured with their IP addresses on the IDU’sethernet interface LAN.


Destination The destination IP address and mask corresponding to a host network. This network should be outside the IDU ethernet interface LAN.Mask

Gateway The gateway, usually a router, to which the IDU will forward the corre-sponding IP traffic.

Action

Actions are:• Add Route to add a route to the IDU’s routing table.• Delete Route to delete a route from the IDU’s routing table.

Note: The Hub’s routing table must be updatedmanually if a new route is added at the IDU



851674 P01

Figure 4.2 Typical Routing on the IDU Ethernet interface Network

4.2.2 Dynamic Routing

In contrast to static routing, Dynamic Routing adjusts automatically to network topologyor traffic changes, based on information from routing protocol transmissions. Routers inan internetwork automatically exchange information with all other routers, enabling themto build their own table of routes to various networks. Dynamic routing requires adynamic routing protocol such as the Routing Information Protocol (RIP) supported bythe IDU.

Dynamic routing is configured through the Dynamic Route Configuration section of theRouting Management page. Table 4.4 explains the various configuration parameters.

Router 2

IDU

Eth

ern

et

LA

N IDU

IDU Ethernet

InterfaceRouter 1

PC1 on IDU

Ethernet network

PC2 on IDU

Ethernet network

host network 4

host network 2

host network 3

host network 5

host network 1

To/from

Satellite

Interface

IDU Ethernet

network



851674 P01

Table 4.4 Dynamic Routing Management


RIP server enable flag

This flag is used to enable and disable the RIP service.

Note: This flag must be Enabled for the other RIPparameters to have any effect.

Note: The Hub’s routing table must be updatedmanually if a new route is added at the IDU

The default setting is “Disabled”.

RIP Supplier

When Enabled, this flag instructs the IDU to become a RIP Supplier, updating other RIP peers with its own routes every 30 seconds. When Disabled, the IDU will simply listen to route updates from other RIP suppliers. The default setting is “Disabled”.

RIP Gateway

When this flag is Enabled, the default route “0.0.0.0” (if set), will be sent in the RIP messages to other RIP peers, indicating that the IDU is to be the Gateway.

Note: This flag only has an effect if the RIP Supplierflag is Enabled.

Warning: Enabling the RIP Gateway will force theIDU to ignore any advertisement for default routersreceived from other RIP peers: only enable thisfeature if the IDU is in fact the main gateway.

The default setting is “Disabled”.

RIP mode

RIP version 2 Mode can be either Broadcast or Multicast Mode. If the RIP Server is configured to be a RIP supplier then the RIP server will send Broadcast message or multicast message depending on the RIP Mode configuration.The default setting is “Broadcast”.



851674 P01

4.3 DHCP ManagementDynamic Host Control Protocol (DHCP) is a method for a device to dynamically assign IPaddresses from a central server to client devices on a network. DHCP simplifies adminis-tration and configuration of PCs on a network. The IDU has the ability to act as a DHCPserver on the Ethernet-side of the SIT. The DHCP Management page is used to configureDHCP on the IDU.

The DHCP Mode Selection Configuration section of this page is where you can globallyenable or disable DHCP Server functionality.

Note: If the IDU is not currently in DHCP Server mode, this will be the onlysection visible on the page.

To allow the IDU to act as a DHCP server on your network, use the SIT Ethernet DHCPMode drop-down list, select DHCP Server and click on the Configure DHCP Mode but-ton.

Note: Upon modifying the SIT Ethernet DHCP Mode parameter, the SuperuserMenu Result page will be displayed prompting you to reboot the SIT. The changewill not take effect until you do so (see Appendix D).

When the IDU is in DHCP Server mode, the DHCP Clients Table section of the pagedisplays information about client devices that have obtained an IP from the IDU. The tableshows the MAC Address of the device that requested an IP as well as the Client IPAddress that the SIT assigned to it.

The IDU’s DHCP server functionality can be tailored to your specific network topology:you can configure subnetworks with individual settings, giving you full control over theDHCP server’s behavior.

The section ‘DHCP Server Status and Control’ is used to Control and to get the statusof the DHCP server.

The button “Start DHCP Server” / “Shutdown DHCP Server” / “Restart DHCPServer” changes depending on the DHCP Server status:

• Start DHCP Server (when the status is "Not Started");

• Shutdown DHCP Server (when the status are: "Starting" and Running");

• Restart DHCP Server (when the status are "Stopped", "Error" and "Unable to get sta-tus").

The button “Revert to Last Valid DHCP Configuration” button will trigger the follow-ing actions:

• Import the "dhcpd.conf_lastValid" file into the DHCP Server database;



851674 P01

• Validate the DHCP server database section;

• Shutdown the DHCP Server (if running);

• Clears the leases table;

• Construct the "dhcpd.conf" file based on the database configurations;

• Starts the DHCP server with the new "dhcpd.conf" file as configuration input.

The button "APPLY ALL SAVED CHANGES" will trigger the following actions:

• Validate the DHCP server database section;

• Shutdown the DHCP Server (if running);

• Clears the leases table;

• Construct the "dhcpd.conf" file based on the database configurations;

• Starts the DHCP server with the new "dhcpd.conf" file as configuration input.

If this process fails, error messages will appear under the "DHCP Sever Status and Con-trol" line. There are two options to fix the problems:

• Correct the mistake and re-apply the changes;

• Revert to Last Valid Configuration and perform the changes from scratch.

The “DHCP Server Configuration” is divided into three main sections:

1. The "Global Options" sub-section contains the options that will be applied to the"SUBNETS" and "HOST" sections unless the same option is specified within thesesections. The available global options are:

•max-lease-time: Time should be the maximum length in seconds that will beassigned to a lease. The only exception to this is that Dynamic BOOTP leaselengths, which are not specified by the client, are not limited by this maximum.

•default-lease-time: Time should be the length in seconds that will be assigned toa lease if the client requesting the lease does not ask for a specific expirationtime.

•subnet-mask: The subnet mask option specifies the client's subnet mask as perRFC 950. If no subnet mask option is provided anywhere in scope, as a last resortdhcpd will use the subnet mask from the subnet declaration for the network onwhich an address is being assigned. The option subnet-mask statement will over-ride the subnet mask declared in the subnet statement. Format: ip-address.

Example: 255.255.255.0

•routers: The routers option specifies a list of IP addresses for routers on the cli-ent's subnet. Routers should be listed in order of preference. The maximumnumber of routers is 4.

Format: ip-address [, ip-address...].

Examples:



851674 P01

• - one router: 10.10.10.1

• - two routers: 10.10.10.1, 10.10.10.2

•domain-name-servers: The domain-name-servers option specifies a list ofDomain Name System (STD 13, RFC 1035) name servers available to the client.Servers should be listed in order of preference. The maximum number ofdomain-name-servers is 4.

Format: ip-address [, ip-address...].

Examples:

• - one domain-name-servers: 10.10.10.1

• - two domain-name-servers: 10.10.10.1, 10.10.10.2

•domain-name: This option specifies the domain name that client should usewhen resolving hostnames via the Domain Name System. Format: string of 255characters maximum.

2. The "SUBNETS" sub-section is used to define subnets for assigning dynamic IPaddresses. It is defined by its "subnet" and "netmask" pair. The user can define up to 8subnets. The "CREATE a new Subnet Entry" and "SAVE/DELETE This SubnetEntry" Buttons are available to manage the Subnet entries. To activate a SUBNET,the "Subnet Entry Status" field must be set to "active".

Each SUBNET contains “Subnet Entry Options” and “Subnet Ranges”. The firstcontains the same options as in the global options sub-section. The user can define upto 8 subnet ranges consisting of a Start and a End Address. To Add/Delete SubnetRange the user must use the "Subnet Range Submit" Button.

3. The "HOSTS" sub-section is used to define fixed IP Address related to particularMAC addresses. The user can define up to 8 HOST entry. The "CREATE a new HostEntry" and "SAVE/DELETE This Host Entry" Buttons are availble to manage theHost entries.

Each HOST Entry contains the same options as the Global Options. The Host EntryMandatory Parameters are:

•hardware ethernet: DHCP Client MAC Address

•fixed-address: fixed IP Address given to a related MAC Address

•defined in the "hardware ethernet" field above.

•Host Entry Status

Note: To activate a HOST entry, the "Host Entry Status" field must be set to"active".



851674 P01

4.4 Multicast ConfigurationThe multicast configuration is divided in three main areas:

• Tx Multicast Source Support, which is the configuration of the IDU as a multicastsource.

• Rx Multicast Source Support, which is the configuration to enable or disable recep-tion of multicast.

• Rx Default Multicast Mapping Table Configuration, which lists the multicast streamsof interest.

4.4.1 Tx Multicast Source Support

Three parameters need to be configured for the IDU to source multicast.

Table 4.5 Tx Multicast Configuration Parameters

4.4.2 Rx Multicast Source Support

When this flag is set to enable, the IDU will proceed with IGMPv2 queries on it’s Ethernetport and allow multicast data forwarding.

The factory default setting is “Disabled”.

Press the Save button in order to keep the configuration.


Tx Multicast Source Enable Flag

When enabled, the IDU will allow multicast data forwarding from the host interface to the satellite interface.The accepted multicast addresses forwarded will be in function of the Tx Multicast Source IP Address and the Tx Multicast Source IP Mask settings.The factory deault setting is “Disabled”NOTE: Multicast addresses from 224.0.0.0 to 224.0.0.255 will NOT be forwarded because they are considered local.

Tx Multicast Source IP Address

User Interface to IDU Satellite interface Multicast Traffic Forward IP Address.The factory default is “224.0.0.0”.

Tx Multicast Source IP Mask

User Interface to IDU Satellite interface Multicast Traffic Forward IP Mask.The factory default is “255.255.255.255”.



851674 P01

4.4.3 Rx Default Multicast Mapping Table Configuration

When no MMT is received by the IDU, the Default Multicast Mapping Table defines theMulticast IP Addresses/PID filter pairs that are used to forward the Multicast traffic fromthe satellite interface to the terrestrial interface.

If an MMT is received, then the Default Multicast Mapping Table will be by-passed andall IP Address/PID filter will be reset.

Table 4.6 describes Default Multicast Mapping Table Configuration settings.

Entries in the Default Multicast Mapping table are added and deleted as follows.

• To add a new entry to the Default Multicast Mapping table, click the Create A NewDefault Multicast Mapping Entry button. This is used for entering an entry initiallynot in service. After clicking this button, a refresh (or reload) of the Default MulticastMapping Table Configuration page will display a new entry with default parameters.

• To delete an entry, choose the Default Multicast Mapping Table entry from theDefault Multicast Mapping Selection drop-down box. Next, click Delete this DefaultMulticast Mapping Entry.

To view or modify a Default Multicast Mapping Table entry, choose the entry from theDefault Multicast Mapping Selection drop-down box. The table below describes theparameters that can be viewed or modified.

Table 4.6 Default Multicast Mapping Entry Configuration Parameters

When you have finished modifying these parameters, click Save This Default MulticastMapping Entry at the bottom of the page. This opens the Menu Result page. Dependingon the combination of parameters that you changed, you may be required to perform anaction before the changes take effect (see Appendix C).

4.5 MIB TrapThe MIB Trap Configuration page is used to configure which SIT traps are sent and whichentity at the hub can receive the traps.

The MIB Trap Configuration page enables you to:


Multicast IP Address

This parameter specifies the Multicast IP Address for the current Multicast table.

Multicast PID This parameter specifies the PID for the current Multicast table.

Multicast Mapping Entry Status

This will define the status for the entry.The factory default setting is "Not In Service".



851674 P01

• Enable or disable MIB trap flags.

• Configure the trap destination table.

4.5.1 Enabling or Disabling MIB Trap Flags


Table 4.7 MIB Trap Flag Configuration Parameters

When you have finished modifying these parameters, click Save MIB Trap Flags at thebottom of the page. This opens the Satnetwork Menu Result page. Depending on thecombination of parameters that you changed, you may be required to perform an actionbefore the changes take effect (see Appendix C).

4.5.2 Configuring the Trap Destination Table

Entries in the trap destination table are added and deleted as follows.

• To add a new entry to the trap destination table, click the Create A New Trap TableEntry button. This is used for entering an entry initially not in service. After clickingthis button, a refresh (or reload) of the MIB Trap Configuration page will display anew entry with default parameters.

• To delete an entry, choose the trap table entry from the Trap Destination Table EntrySelection drop-down box. Next, click Delete this MIB Trap Table Entry.


General Trap Flag

This flag enables/disables the use of traps.The factory default setting is “Disabled”.

Reboot Status Trap Flag

This flag enables/disables the use of the reboot status flag.- Send trap- Do not send flagThe factory default setting is “Send trap”.



851674 P01

To view or modify a trap destination table entry, choose the entry from the Trap Destina-tion Table Entry Selection drop-down box. The table below describes the parameters thatcan be viewed or modified.

Table 4.8 Trap Destination Table Entry Configuration Parameters

When you have finished modifying these parameters, click Save This MIB Trap TableEntry at the bottom of the page. This opens the Satnetwork Menu Result page. Depend-ing on the combination of parameters that you changed, you may be required to performan action before the changes take effect (see Appendix C).

4.6 MIB Access PolicyThe MIB Access Policy Configuration page is used to configure MIB access policies thatdefine which entities the SIT will recognize as having administrative privileges. Once anaccess policy has been established, the associated access view rights for the entry can bedefined.

The MIB Access Policy Configuration page enables you to:

• Set global options for the MIB access policy.

• Create, delete, view and modify access policy table entries.

• Create, delete, view and modify access view rights table entries.


Trap Destination – Entity

Trap destination management entity. This shall match a defined entity from the access policies.The factory default setting is “PrimaryTM”.

Trap Destination – Object ID

The OID of the trap to be sent. The factory default setting is “3.4.0.1”. Note that this setting is invalid.

Trap Destination – Status

Traps will only be sent to destinations whose status is “Active” - Active- Not in ServiceThe factory default setting is “Active”.



851674 P01

4.6.1 Setting Global Options for the MIB Access Policy


Table 4.9 MIB Access Policy Configuration Parameters

When you have finished modifying these parameters, click Save MIB Access PolicyFlags. This opens the Satnetwork Menu Result page. Depending on the combination ofparameters that you changed, you may be required to perform an action before the changestake effect (see Appendix C).

4.6.2 Managing Access Policy Table Entries

This section of the page permits the definition of access policies. This is done through theMIB access policy table.

Entries in the access policy table are added and deleted as follows.

• To add a new entry to the table, click the Create A New Access Policy Table Entrybutton.

• To delete an entry, choose the trap table entry from the MIB Access Policy TableEntry Selection drop-down box. Next, click Delete This MIB Access Policy Entry.

To view or modify an access policy table entry, choose the entry from the MIB AccessPolicy Table Entry Selection drop-down box. The table below describes the parametersthat can be viewed or modified.


MIB Private Enterprise Number

The private MIB enterprise number. The factory default setting is “2696” and corresponds to the DVB-RCS MIB.

MIB Access Policy Usage Flag

This flag enables the use of access policies. If enabled, the access policies and access view rights of the next sections must be defined.

Note: This flag enables the use of access policies. Ifenabled, the access policies (section 4.6.2) and accessview rights (section 4.6.3) must be defined. Note thatonly the access view rights of the DVB-RCS MIB mustbe defined, the ASN private MIB is fully accessible withany access policy defined. If disabled, the IDU is stillaccessible by SNMP using as a read community "public"and as a set community "private". This last setting is notadvisable since any entity can then access the IDU bySNMP.

The factory default setting is “Disabled”.



851674 P01

Table 4.10 MIB Access Policy Table Entry Configuration Parameters

When you have finished modifying these parameters, click Save This MIB Access PolicyTable Entry at the bottom of the page. This opens the Satnetwork Menu Result page.Depending on the combination of parameters that you changed, you may be required toperform an action before the changes take effect (see Appendix C).

4.6.3 Managing Access View Rights Table Entries

This section of the page permits the definition of the level of access view rights for thedefined access policies. This is done through the MIB access view rights table.

Entries in the access view rights table are added and deleted as follows.

• To add a new entry to the table, click the Create A New Access View Table Entrybutton.

• To delete an entry, choose the trap table entry from the MIB Access View TableEntry Selection drop-down box. Next, click Delete This MIB Access View Entry.

To view or modify an access view table entry, choose the entry from the MIB AccessView Table Entry Selection drop-down box. The table below describes the parameters thatcan be viewed or modified.


Access Policy – IP Address

IP address of the network management entity.The factory default setting is “10.2.0.1”.

Access Policy – Netmask

Network mask for the network management entity.The factory default setting is “255.0.0.0”.

Access Policy – Community Name

The name of the corresponding community.The factory default setting is “HUBManager”.

Access Policy – Management Entity Name

Management entity name.The factory default setting is “PrimaryTM”.

Access Policy – Status

This will define the status for the entry.- Active- Not in serviceThe factory default setting is “Active”.



851674 P01

Table 4.11 MIB Access View Rights Table Entry Configuration Parameters

When you have finished modifying these parameters, click Save This MIB Access ViewRights Table Entry at the bottom of the page. This opens the Satnetwork Menu Resultpage. Depending on the combination of parameters that you changed, you may be requiredto perform an action before the changes take effect (see Appendix C).

4.7 PEPBecause satellite communication combines very high data rates (typically 4 to 40 Mbpsover the forward link) with long round-trip delays (typically 600ms to 2s), TCP generallyperforms poorly over satellite links. Under these conditions, even a very small packet lossrate over the satellite link or minor terrestrial congestion results in significant congestionand traffic slowdown.

By contrast, even with a loss rate that would dramatically lower TCP performance, thePEP suffers almost no reduction in data throughput. The PEP enables consistent, reliableperformance for TCP/IP traffic under all conditions. It does this by replacing TCP with aFlight Protocol (FP) over the satellite link. The Flight Protocol is designed to optimize theuse of available bandwidth. The PEP also requires a gateway PEP device installed at thesatellite network.


Access View – Community Name

Displays the community name with its associated group OID that it can view.The factory default setting is “HUBManager”.

Access View – Group OID

Displays the OID of the access view group.The factory default setting is “1.1”. Note that this setting is invalid.

Access View – Rights

Defines the level of access rights the community has. The supported values are as follows:- Read only- Read-write- Not accessibleThe factory default setting is “Read Only”.

Access View – Status

This will define the status for the entry.- Active- Not in serviceThe factory default setting is “Active”.



851674 P01

4.8 Web Page Management (Logo)You can customize the look of the IDU web interface pages by replacing the defaultAdvantech Satellite Networks logo with your own logo. This is done using the Web PageManagement page.

The filename of the new logo must be “logo.gif”, and it must be located on the FTP serverpath (refer to File Management section). The file must be in GIF format and be less than10kb in size. To display correctly, the file should have dimensions of about 246 pixelswide by 43 pixels high.

To download a new logo, click Download LOGO.GIF file. The new logo will appearwhen the web page is refreshed.

4.9 Forward Link Control Management (FLCM)The FLCM is used in a point-to-multipoint configuration where commands can be initi-ated from the central location towards one or several remote IDUs, this is an unidirectionallink. Please refer to the Forward Link Control Management User Manual for more details.

Table 4.12 describes Forward link control and management settings.



FLCM Multicast PIDPID used by the IDU for Forward Link Control and Management when multicast or broadcast addressing is used.The factory default setting is “931”.

FLCM Multicast Group

The multicast group number will be used by the IDU to extract the proper UDP packet from the FLCM multicast PID.The group number corresponds to a multicast IP address. The multicast range for the FLCM is 239.255.255.1 to 239.255.255.254 and is directly mapped to a group number. As an example, a group number of 10 corresponds to a multicast address of 239.255.255.10.

Note: Address 239.255.255.255 corresponds to abroadcast address that all IDUs will receive.

The factory default setting is “10”.

Table 4.12 Forward Link Control and Managements Settings



851674 P01

When you have finished modifying these parameters, click Save Forward Link Configu-ration at the bottom of the page. This opens the Satnetwork Menu Result page. Depend-ing on the combination of parameters that you changed, you may be required to performan action before the changes take effect (see Appendix C).

FLCM UDP PortThe UDP port used by the IDU to receive the Forward Link Control and Management message.The factory default setting is “1500”.

FLCM Test Mode Frequency

The default frequency the IDU will use to transmit a test signal when commanded by the FLCMThe factory default setting is “0”.

FLCM Test Mode Rate

Do not use. This parameter is not valid in this load. It will be replaced by symbol rate in a future load.


Table 4.12 Forward Link Control and Managements Settings



851674 P01

Chapter 5 IDU Monitoring

This section covers the various monitoring capabilities of the IDU:

• IDU Monitoring

• IDU Log

• Network Interface Stats

• Active Connection Monitoring

• Forward Link PID Statistics

• Multicast Active Membership Monitoring

• Multicast Statistics

5.1 IDU MonitoringThe IDU monitoring page is the one that would normally be displayed when one needs tohave an overview of what is happening. A table shows several parameters, both for Rx andTx. The parameters are listed in the table below.



851674 P01


Rx/Tx State

Rx State

The state shows “locked” when the demodulator is locked, and “not locked” otherwise.

Tx State

The state shows “Enable” when it is transmitting, and “HOLD” otherwise.

Status

Rx Status

The state shows “Acquired” when the demodulator is locked, and “not Acquired” otherwise.

Tx Status

The state shows “Initiazed” when configuredThe state shows “Ready” when data can be transmitted

Rx SNR/Tx Power

Rx SNR

Displays the Rx SNR value or, “Not valid” when there is no signal.

Tx Power

Displays the configured Tx Power.

RF Frequency Displays the configured Rx and Tx RF frequencies.

IF FrequencyDisplays the IF Rx and Tx IF frequencies. The IF frequency is derived from the configured RF frequency and the configured mixing frequency.

Symbol Rate Displays the configured Rx and Tx symbol rates, and the equivalent data rate (Tx only).



851674 P01

Table 5.1 IDU Monitoring Parameters

5.2 IDU LogThe IDU Log page displays alarms, errors and other events recorded by the IDU.

• An alarm is a non-recoverable fault that normally requires user intervention. Alarmsare indicated in red.

• An error is a problem that does not normally require user intervention. Errors are indi-cated in blue.

• Other events are indicated in black text.

MODCOD

Rx MODCOD

Displays the MODCOD of the receive signal or, “Not valid” when there is no signal.

Tx MODCOD

Displays the configured Tx MODCOD.

Roll-Off

Rx Roll-Off

Displays the Roll-Off of the receive signal or, “Not valid” when there is no signal.

Tx Roll-Off

Displays the configured Tx Roll-Off.

Pilot

Rx Pilot

Displays the Pilot of the receive signal or, “Not valid” when there is no signal.

Tx Pilot

Displays the configured Tx Pilot.

Frame Length

Rx Frame Length

Displays the Frame Length of the receive signal or, “Not valid” when there is no signal.

Tx Frame Length

Displays the configured Tx Frame Length.

PID Displays the configured Rx and Tx PIDs



851674 P01

The IDU stores up to approximately 5000 records in a circular buffer (when the buffer isfull, each new record causes the oldest record to be deleted). It is possible to configure thedisplay.

• Filtering. From the drop-down list you can choose to display the last 20 events, allevents since the last reboot, or all events stored in the IDU.

Note: The option “all events” should only be used when it’s absolutely necessary.The web browser might take a long time to update the page if the circular buffer isfull.

• Ordering. From the drop-down list, choose whether to display the latest event first orthe earliest event first.

• Severity. From the drop-down list, choose to display the messages by their severitylevel (alarm, error, event, all).

• Log location. From the drop-down list, choose to display the messages logged fromthe FLASH or the RAM of the IDU. All messages are logged in the RAM while onlythe most important messages are saved in the FLASH. Note that an IDU reset erasesthe messages in the RAM.

Click Apply to implement your choices.

You can download a complete list of events to the FTP server using the Dump Log toFTP Server as SITLOG.BIN file button.

Note: The SITLOG.BIN file cannot be viewed by the user. It must be sentto Advantech Satellite Networks for decoding. To save a text record of themessages, copy and paste the text from the web browser into a text file.Alternatively, save the IDU Log page in html format.

The messages displayed in the IDU log page contains the following elements:

• The date and time.

• The severity. Alarm, error or event.

• Unique message number. This is a unique number mapped to the displayed messageto facilitate when debugging.

• Type of message. This shows in which IDU module the message took place.

• The description.

• Consecutive occurrences of the same message. A number showing how many times amessage occurred, if it happened more than once consecutively.



851674 P01

Note: Some messages have their message number underlined. In thiscase, click to have a Help page appear with additional information.

5.3 Network Interface StatsThe "Network Interface Stats" table shows the Rx/Tx packet statistics for the ethernet andsatellite interfaces.

It displays also the stats for the Rx/Tx packet discards.

The possible reasons for the Rx packet discard can be:

For the Ethernet Interface:

- Receiver ring buff overflow

- Received packet with crc error

- Received frame alignment error

- Received fifo overrun

- Receiver missed packet

- No space in IDU buffers

For the Satellite Interface


- Invalid SPI (IPSec)

The possible reasons for the Tx packet discard can be:

For the Satellite Interface


For the Ethernet Interface:

- Packet matches no filter pattern

- Packet too old to send

Click Start Refreshing to enable automatic refreshing of data on this page. Choose a dif-ferent refresh rate from the drop-down box, if required.

5.4 Active Connection MonitoringThe Active Connection Monitoring page displays information about currently active traf-fic queues. The IDU supports multiple traffic queues, where each queue can be defined toinclude traffic from a certain source IP subnet, traffic to a certain destination subnet, orother parameters.

An active traffic queue is one that is receiving data from the return link. Each row in theActive Connection Monitoring page displays information about one active traffic queue.



851674 P01

The first row corresponds to the OAM traffic queue, if one has been defined (see QueueManagement section).

Click Start Refreshing to enable automatic refreshing of data on this page. Choose a dif-ferent refresh rate from the drop-down box, if required.

The parameters displayed on the Active Connection Monitoring page are those configuredfor each traffic queue (see section 4.1). The only exception to this is the Queue Occupancywhich refers to the number of packets currently in the queue.

For more detailed information about queue data throughput, click the Chan Id parameter.This opens the Uplink Channel Statistics page. In addition to configuration parameters foreach queue, this page shows queue statistics, as described in the table below.

Table 5.2 Uplink Channel Statistics

5.5 Forward Link PID StatisticsThe Web page shows a table displaying the receive unicast PIDs,

The following elements are shown for each PIDs

• Number of incoming packets and bytes

• Number of incoming packet discards

• Number of incoming packet errors

5.6 Multicast Active Membership Monitoring

The Multicast Active Membership Monitoring Page is used to monitor the IGMP Querierand HOST states, PID and MAC for each Multicast Active Membership.

Statistic Description

Queue Occupancy Current size of the queue, in IP packets

InPkts (bytes) Total amount of data received by the IDU over the return link, shown in IP packets and (bytes), since the queue was defined.

InPktDiscards Number of IP packets received by the IDU over the return link that have been discarded since the queue was defined.

OutPkts (bytes) Total amount of data sent by the IDU over the return link, shown in IP packets and (bytes), since the queue was defined.

OutPktDiscards Number of IP packets sent by the IDU over the return link that have been discarded since the queue was defined.



851674 P01

This page contains the following elements:

• Active Group: The Multicast Active Group

• IGMP Querier State: The IGMP Querier State

• PID: PID used for this Multicast Active Group

• MAC: MAC used for this Multicast Active Group

5.7 Multicast Statistics

The Multicast Statistics Page is used to get IGMP and Multicast traffic Statistics.

5.7.1 IGMP Statistics Table

This table contains the following elements:

• IGMP Type

• Interface

• Membership Reports Sent

• Total Messages Received

• Membership Queries Received

• Membership Reports Received

• Received Report for our Groups

• IGMP Messages Errors

• Received Invalid Report

• Received with too few bytes

• Received with bad checksum

• Received invalid queries

5.7.2 Virtual Interfaces (Vifs) Statistics Table


• Interface

• BytesIn

• PktsIn

• BytesOut

• PktsOut

• Flags

• Local



851674 P01

• Remote

5.7.3 Multicast Routing Cache Table


• Group

• Origin

• Iif

• Pkts

• Bytes

• Wrong

• Oifs



851674 P01

Appendix A Glossary

ACQ Acquisition burst, used by the SIT to log on to the satellite network.AGC Automatic Gain Control.

Alarm A non-recoverable fault in the IDU that requires user intervention.BUC See Transmitter.CRA Continuous rate assignment. The return link rate capacity which is provided in full for

each and every superframe while required.CSC Common signalling channel burst, used by the SIT to log on to the satellite network.

dB Decibel.

dBm Decibel milliwatts. A logarithmic measure of power, referenced to 1 milliwatt (1 mW = 0 dBm).

dBW Decibel watts. A logarithmic measure of power referenced to 1 watt (1 W = 0 dBW).DVB-RCS Digital Video Broadcast-Return Channel System. An open standard for providing two-

way broadband access over satellite.Eb/No Signal to noise ratio.

EIRP Effective isotropic radiated power. A measure of the amount of power radiated by the ODU.

Error A problem with the IDU that does not require user intervention.ESD Electrostatic discharge.FCA Free capacity assignment. The return link volume capacity which is assigned to the IDU

from capacity that would otherwise be unused.

Filter pattern A set of criteria applied to all data received from a local PC or LAN. Filter patterns can be used to assign data to traffic queues (see Queue). They can also be used to block data from being transmitted over the satellite network.

FL Forward link.Forward link The path carrying communication from a hub (or gateway), via satellite, to SITs. It is

based on the DVB/MPEG standard.FTP File transfer protocol. Used for transferring software, configuration and other files to and



851674 P01

from the IDU on the local network.Hub The central terrestrial element of a DVB-RCS system, the hub (or gateway) is responsible

for connecting the satellite network with the Internet or other network and for managing all aspects of the forward and return satellite links.

IDU Indoor unit. The unit of the SIT responsible for the ethernet interface with the LAN or local computer, as well as all aspects of network management. It is connected via two IFL cables with the outdoor unit.

IDU Name The IDU name is shown at the top left of each web interface page. It is used to identify each IDU when managing multiple IDUs simultaneously on the same LAN.

IF Intermediate Frequency.IFL cables Inter-facility link cables.

Indoor unit See IDU.

Installer page A section of the IDU web interface used for initial installation of the SIT.IP Internet Protocol.

LAN Local area network.LNB The ODU component responsible for receiving forward link signals.

MAC Address The IDU medium access layer (MAC) address is a unique address permanently assigned to each IDU. The MAC address is shown at the top left of all web interface pages.

MF-TDMA Multi-frequency time-division multiple access.MIB Management information base.

OAM Operation, administration and maintenance.ODU Outdoor unit. It consists of an antenna, transmitter (BUC), and RF transceiver assembly.

The ODU is connected via two inter-facility link (IFL) cables to the IDU.

OID Object Identifier.Outdoor unit See ODU.

PC Personal computer.PCR Program Clock Reference.

PEP Performance Enhancing ProxyPID Packet Identification.

PPPoE Point-to-Point Protocol over EthernetPublic key A code exchanged and used by computers that protects data sent and received by a web

browser from unauthorized viewing or modification.

QoS Quality of ServiceQueue Data traffic held in an IDU memory buffer. This traffic is received from a local PC or

LAN, and it will be sent over the satellite network return link. The IDU can hold multiple traffic queues.

RBDC Rate-based dynamic capacity. The return link rate-based capacity that is requested dynam-ically by a SIT and assigned by the hub.

Return link The path carrying communication from SITs to the gateway. It uses a multi-frequency time-division multiple access (MF-TDMA) scheme carrying ATM cells or MPEG pack-ets.



851674 P01

RIP Routing Information ProtocolRL Return link

RLSS Return link sub-system. The part of the gateway responsible for receiving return link com-munication from SITs and relaying it to terrestrial networks (e.g. the Internet). It also man-ages all aspects of return link communication, including SIT logon, SIT synchronization, and allocation of return link capacity.

Rx Receive.S/W image Software image. A file containing IDU software that is downloaded and installed in the

IDU.Satellite interactive

terminalSee SIT.

Satnetwork page The section of the IDU web interface used for initial satellite network configuration of the IDU.

SIT Satellite interactive terminal. SITs in a DVB-RCS system are connected, via satellite links, with a hub. They provide remote access to the Internet and perhaps other networks at the hub. SITs are made up of an outdoor unit (ODU) and an indoor unit (IDU).

SSL Secure socket layer encryption. SSL protects data sent and received by a web browser from unauthorized viewing or modification.

Superuser page A section of the IDU web interface used for operation and maintenance of the IDU.SYNC Synchronization burst, used by the SIT to log on to the satellite network.TDMA Time-division multiple access.Traffic User data sent over the satellite network forward or return links.

Traffic Queue See Queue.Transmitter Also called the BUC. The part of the ODU responsible for generating the return link sig-

nal.Tx Transmit.

ULPC Uplink power control.

VBDC Volume-based dynamic capacity. The return link volume-based capacity that is requested dynamically by a SIT and assigned by the hub.

VCC Virtual Channel Connection.VCI Virtual Channel Identifier.

VoIP Voice over IP.

VPI Virtual Path Identifier.Web interface The IDU web interface provides the user interface with the IDU. The IDU web interface

can be accessed from any computer with a network or Internet connection to the IDU. The web interface is viewed in a web browser.



851674 P01

Appendix B Parameters in Web Interface Pages

Parameters in web interface pages are described in this documentation as follows:

• Parameters in bold must be modified to site-specific values during installation.

• Parameters in regular type may be modified if desired.

• Parameters in italics must not be modified, as any modification may prevent the SITfrom operating properly.

• Parameters underlined are read-only fields.



851674 P01

Appendix C Menu Result Page

When changes to parameters are saved, the Menu Result page opens. This page confirmsthat changes made to parameters are valid. It also prompts you to perform an actionenabling the changes to take effect. Different parameters require different actions to betaken in order for them to take effect:

• Reboot the SIT

• Logoff the SIT

• Re-acquire the Forward Link

• Nothing (parameter change takes effect immediately)

The Menu Result Page will prompt you for the “worst case” action required to make theparameter take effect: if you made a change to a parameter requiring a reboot as well as toone which only requires logging off the SIT, it will prompt you to reboot the SIT. Anychanges made to parameters are only implemented on the IDU after the appropriate actionhas been taken (if any is required).

• If you wish to continue modifying parameters, there is no need to perform the actionright. Click the Back button on your browser to return to a superuser menu page.

• If you are done modifying parameters, you must perform the required action for theconfiguration to be implemented on the IDU. Click button at the bottom of the MenuResult Page which is labelled with the action to be perform.

Note: If the action performed is to reboot the IDU (this takes up to 1 minute), youwill be returned to the IDU home page.


s5420 Idu Dvb-s2 Scpc User Manual 851674 Rev p01

Documents

Transcript of s5420 Idu Dvb-s2 Scpc User Manual 851674 Rev p01