Académique Documents
Professionnel Documents
Culture Documents
Document Document Number: Number: 851674 851674 Revision: Revision: P01 P01 Date: February 16, 2010
Document Number: 851674 Revision: Date: Proprietary Notice: P01 February 16, 2010 Copyright 2010 Advantech Satellite Networks, Inc. All rights reserved. The information contained herein is proprietary to Advantech Satellite Networks or third party proprietary information which Advantech Satellite Networks is obligated to protect and shall not be disclosed in whole or in part without the prior written permission of Advantech Satellite Networks.
Page ii
Table of Contents
1
1 1 3
4
4 6 7 7 8 9 10 10
Chapter 3. Installation
3.1 Installation Requirements 3.1.1 ODU Installation 3.1.2 IDU Unpacking - Model 5420 3.1.3 Computer for IDU Configuration 3.2 Installing the IDU 3.2.1 Step 1. Site Selection 3.2.2 Step 2. Making Power and Cable Connections 3.3 Accessing the IDU Web Interface 3.3.1 SSL Secure HTTP Access 3.4 Steps for Basic IDU Installation and Configuration 3.5 File Management 3.5.1 Configuring Access to an FTP server 3.5.2 Upgrading Software 3.5.3 Transferring Configuration Files 3.5.4 Delta Configuration 3.5.5 Configuration Backup and Restore 3.6 Installer Configuration
12
12 12 12 13 13 13 13 14 15 16 17 17 18 19 19 20 21
Page iii
34
34 35 36 37 41 42 43 45 48 48 48 49 49 50 50 51 52 52 53 54 55 55
57
57 59 61 61 62 62 63 63 63 64
Page iv
IDU Users Manual S5420 DVB-S2 SCPC 851674 P01 Appendix A. Glossary Appendix B. Parameters in Web Interface Pages Appendix C. Menu Result Page Appendix D. 65 68 69
Page v
Page vi
Chapter 1
Warning: The following general safety precautions must be observed during all phases of operation, service and repair of this equipment. Failure to comply with these precautions or with specific warnings elsewhere in this documentation violates safety standards of design, manufacture and intended use of the equipment. Advantech Satellite Network assumes no liability for the customers failure to comply with these requirements.
Please review the following important safety information before installation and use of the equipment.
Page 1
Page 2
Page 3
Chapter 2
Getting Started
This manual covers installation and satellite network configuration of Advantech Model 5420 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 Series 5420 part number 850643-365 and 850643-366.
Note: This SW load doesnt 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 the IDU 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.
Page 4
Page 5
Page 6
Figure 2.2 SIT Schematic Diagram For more information about the IDU, see section 2.3.
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.
Page 7
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 protective 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 forward link communication. Ethernet connector. 10/100BaseT Ethernet Interface on RJ-45 connector. For ethernet connection with LAN or host computer. Reset. The Reset button resets the IDUs ethernet IP address to its default value of 10.10.10.10. The IP address remains at this value until the unit is rebooted. To push the 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. For return link communication. Serial Port. DB-9 connector to input the GPS coordinated. The pin 9 carries +24V.
Page 8
Installer Menu
Monitoring SIT Operational State: FL Status: RL Status: IDU Power Level: IDU TX Status: TX Frequency (in 100Hz): RL Measured Es/No: FL Measured Eb/No: OAM Active Acquired Ready Mode -9.5 Enabled 10500000 8.0 19.9(db)
Figure 2.6 Typical IDU Web Interface Page All IDU web pages display the following information.
Page 9
Page 10
Page 11
Chapter 3
Installation
3.1.2 IDU Unpacking - Model 5420 Carefully unpack the IDU and check for any damage during shipment. Ensure that the Model 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.
Page 12
Page 13
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 LED on the front of the IDU). After a few seconds, the Ready LED should be illuminated as 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 the Ready LED is flashing, indicating that the IDU is currently in HOLD mode. When in HOLD mode, transmission is disabled. The IDU will remain in HOLD mode until it is put out of HOLD mode by the user. The IDU will remain in HOLD mode even after a reboot or power cycle. It is the users resposibility to put the IDU out of HOLD mode when it is properly configured, thus avoiding disturbing the Network. One of the very last 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 outer rotating nut of the connector. The cable and the main body of the connector must not rotate or twist. Hand tighten only.
Page 14
Note: If the computer is unable to open the IDU home page, it may be necessary to temporarily modify the computer's IP address so that it is in the correct range to access the IDU. For instructions about how to do this, consult Windows on-line documentation. After communication with the IDU has been established, the IDUs ethernet IP address can then be changed to an address accessible from the computer, and the computer's IP address can be changed back to its normal setting.
The IDU home page is used to log in to IDU web pages. The home page can be accessed from any IDU web page by clicking the Login link near the upper left corner of the page.
Note: For access to the IDUs web page over the satellite network, the SITs OAM IP 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 Windows operating systems use a short (30 second to 2 minute) default time-out for encrypted
Page 15
1. Start the Registry Editor (Regedit.exe). 2. Locate and click the following key in the registry: HKEY_LOCAL_MACHINE\System\CurrentControlSet\Control\SecurityProviders\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. For example, 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 their default values.
For more information about the IDU web interface, see section 2.4.
PLEASE THIS SECTION ENTIRELY BEFORE STARTING THE INSTALLATION/ CONFIGURATION. The Superuser Menu of the IDU web interface is used to set installation parameters for the SIT. The Superuser Menu is accessed from the IDU web interface Home Page by logging in as follows: Username: superuser Password: su001pwd (factory default password) The Superuser Menu contains Configuration Links along the left side. A typical installation procedure is as follows:
Page 16
Page 17
3.5.2 Upgrading Software A software upgrade may be performed as part of a regular maintenance procedure, for problems fixes or for new features available in the IDU.
Page 18
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 correct path (see section 3.5.1). 3. Transfer the delta configuration file to the IDU by clicking Download delta.xml on the File Management page. 4. Apply the delta configuration by clicking Apply Delta Config and Reboot on the File Management page. If one or more Delta Configuration parameters is incorrect, the first error found in the delta.xml file will be displayed, once the button "Apply Delta Configuration and Reboot is selected. A message similar to the following will appear:
Page 19
The error should be corrected in the delta.xml file and the Transfer Procedure re-started until 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 internally on the IDU. The IDU writes all configuration changes to this file, and it reads this file when it reboots. This configuration file is automatically saved as sitcfg.old when the IDU reboots. When the IDU boots up, it checks whether the current configuration file (sitcdg.xml) contains valid values for all parameters. If the it is not valid, the IDU automatically restores the sitcfg.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. This can be used when the downloaded configuration is not working as expected to revert to the state before the las reboot. In order to restore and reboot from the backup configuration, go to the File Management page and click Reboot with Backup Configuration.
Note: The backup doesn't work in the case of a delta config.
Page 20
The Installation Configuration page is used to view and modify the SIT's installation parameters. Follow this procedure to configure installation parameters for your site. 1. Carefully review all the parameters on this page and modify them according to your installation, as described in the table below. 2. When you are done, click the Save Installation Configuration button at the bottom of the page. This opens the Installer Menu Result page. 3. You must reboot the IDU for the installation configuration to be implemented on the IDU. Click Reboot IDU, the IDU will reboot (this takes about 1 minute), and you will be returned to the IDU home page.
Page 21
SIT Name
RL RF Spectral Inversion
Page 22
Table 3.2 Description of Installation Configuration Parameters When you have finished modifying these parameters, click Save Installation Configuration at the bottom of the section. This opens the Installer Menu Result page. Depending on the combination of parameters that you changed, you may be required to perform an action before the changes take effect (see Appendix C).
Page 23
Page 24
Page 25
SCPC Tx Pilot
Page 26
Page 27
Page 28
Table 3.4 Network Settings Parameters When you have finished modifying these parameters, click Save Network Configuration at the bottom of the page. This opens the Menu Result page. Depending on the combination of parameters that you changed, you may be required to perform an action before the changes take effect (see Appendix C).
Page 29
The IDU leaves the factory configured in HOLD State in order to prevent any undesired transmission. 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/Off control buttons. The Disable IDU Tx - Carrier OFF button disable the carrier on the IDU Tx port. The Enable IDU Tx - Carrier ON button puts it back. The Carrier OFF doesnt survive a reboot nor a power cycle - the IDU will come back with 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 State prior to the reboot.
Page 30
The Test Control page enables the installer to test the SIT's access to the satellite network Return 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's return link. The table below describes the parameters in this section. For a description of how parameters in the table are coded, see Appendix B.
Parameter Description Three test modes are available. CW: This command will produce a continuous wave signal (unmodulated) 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 progress The factory default setting is CW. The symbol rate of the test signal. This only need to be selected for CM test mode. The factory default setting is 0. 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.
Test Mode
Output Frequency
Page 31
Page 32
Note: This is the final step in a basic IDU installation. If the IDU has been successfully installed, the next task is to configure, if required, the Advanced options (see Chapter 4).
Page 33
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 Configuration
Page 34
Figure 4.1 Typical Configuration of Traffic Queues Use the Queue Management page to configure traffic queues. Traffic queues are configured 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 a traffic queue. To view which traffic queues have already been defined, scroll down the Queue Management 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 Queue Table Entry. By default, there is a single queue table entry. To add a new queue table entry, click Create a new Queue Table Entry. This takes you to the Menu Result page, which displays the entry number of the queue you have just created. Next, return to the Queue Management 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. A maximum of four queues can be defined, a high priority traffic queue and low priority
Page 35
Table 4.1 Queue Table Entry Parameters When you have finished modifying these parameters, click Save This Queue Table Entry. This opens the Superuser Menu Result page. Depending on the combination of parameters that you changed, you may be required to perform an action before the changes take 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 be selected 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
Page 36
Filter patterns are defined in a filter pattern table, where each entry in the table corresponds to a filter pattern. To view which filter patterns have already been defined, go to the Filter Pattern Table Configuration section of the Queue Management page. To view the properties of a filter pattern (table entry), click on an entry in the Filter Pattern Table Configuration dropdown box and review the fields below the box. To delete a filter pattern, click on the entry in 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 table entry, click Create a new Filter Pattern Table Entry. This takes you to the Menu Result page, 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 new queue 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 filter pattern. In general, you will want to filter traffic based on the source and/or destination IP addresses of the traffic. This is done by specifying the following IP addresses of the traffic: 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 traffic and a source IP netmask of 255.255.255.255. The destination IP address and netmask should be set to 0.0.0.0 (traffic is not filtered by destination IP address). Filter pattern 1 is then assigned to the high priority queue.
Page 37
Page 38
IP Source Mask
IP Destination Address IP Destination Mask IP Protocol Type IP Protocol Type Mask IP TOS Field Minimum Number
Page 39
Table 4.2 Filter Pattern Table Entry Parameters When you have finished modifying these parameters, click Save This Filter Pattern Table Entry. This opens the Superuser Menu Result page. Depending on the combination of parameters that you changed, you may be required to perform an action before the changes take effect (see Appendix D).
Page 40
Page 41
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, the Routing Management page is used to configure the IDU to statically route any traffic destined to host network 1 through router 1.
Note: Routes should only be added for the IDUs ethernet interface. The gateways (routers) should be configured with their IP addresses on the IDUs ethernet interface LAN.
Page 42
host network 1
host network 2
Router 2
host network 4
host network 5
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 topology or traffic changes, based on information from routing protocol transmissions. Routers in an internetwork automatically exchange information with all other routers, enabling them to build their own table of routes to various networks. Dynamic routing requires a dynamic routing protocol such as the Routing Information Protocol (RIP) supported by the IDU. Dynamic routing is configured through the Dynamic Route Configuration section of the Routing Management page. Table 4.4 explains the various configuration parameters.
Router 1
IDU
Page 43
Parameter
Description This flag is used to enable and disable the RIP service. Note: This flag must be Enabled for the other RIP parameters to have any effect.
RIP server enable flag Note: The Hubs routing table must be updated manually if a new route is added at the IDU The default setting is Disabled. 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. 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 Supplier flag is Enabled. RIP Gateway Warning: Enabling the RIP Gateway will force the IDU to ignore any advertisement for default routers received from other RIP peers: only enable this feature if the IDU is in fact the main gateway. The default setting is Disabled. 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.
RIP Supplier
RIP mode
Page 44
To allow the IDU to act as a DHCP server on your network, use the SIT Ethernet DHCP Mode drop-down list, select DHCP Server and click on the Configure DHCP Mode button.
Note: Upon modifying the SIT Ethernet DHCP Mode parameter, the Superuser Menu Result page will be displayed prompting you to reboot the SIT. The change will 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 page displays information about client devices that have obtained an IP from the IDU. The table shows the MAC Address of the device that requested an IP as well as the Client IP Address that the SIT assigned to it. The IDUs DHCP server functionality can be tailored to your specific network topology: you can configure subnetworks with individual settings, giving you full control over the DHCP servers behavior. The section DHCP Server Status and Control is used to Control and to get the status of the DHCP server. The button Start DHCP Server / Shutdown DHCP Server / Restart DHCP Server 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 status"). The button Revert to Last Valid DHCP Configuration button will trigger the following actions: Import the "dhcpd.conf_lastValid" file into the DHCP Server database;
Page 45
Page 46
domain-name-servers: The domain-name-servers option specifies a list of Domain Name System (STD 13, RFC 1035) name servers available to the client. Servers should be listed in order of preference. The maximum number of domain-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 use when resolving hostnames via the Domain Name System. Format: string of 255 characters maximum. 2. The "SUBNETS" sub-section is used to define subnets for assigning dynamic IP addresses. It is defined by its "subnet" and "netmask" pair. The user can define up to 8 subnets. The "CREATE a new Subnet Entry" and "SAVE/DELETE This Subnet Entry" 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 first contains the same options as in the global options sub-section. The user can define up to 8 subnet ranges consisting of a Start and a End Address. To Add/Delete Subnet Range the user must use the "Subnet Range Submit" Button. 3. The "HOSTS" sub-section is used to define fixed IP Address related to particular MAC addresses. The user can define up to 8 HOST entry. The "CREATE a new Host Entry" and "SAVE/DELETE This Host Entry" Buttons are availble to manage the Host entries. Each HOST Entry contains the same options as the Global Options. The Host Entry Mandatory 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".
Page 47
Parameter
Description 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. User Interface to IDU Satellite interface Multicast Traffic Forward IP Address. The factory default is 224.0.0.0. User Interface to IDU Satellite interface Multicast Traffic Forward IP Mask. The factory default is 255.255.255.255.
When this flag is set to enable, the IDU will proceed with IGMPv2 queries on its Ethernet port and allow multicast data forwarding. The factory default setting is Disabled. Press the Save button in order to keep the configuration.
Page 48
When no MMT is received by the IDU, the Default Multicast Mapping Table defines the Multicast IP Addresses/PID filter pairs that are used to forward the Multicast traffic from the satellite interface to the terrestrial interface. If an MMT is received, then the Default Multicast Mapping Table will be by-passed and all 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 New Default Multicast Mapping Entry button. This is used for entering an entry initially not in service. After clicking this button, a refresh (or reload) of the Default Multicast Mapping Table Configuration page will display a new entry with default parameters. To delete an entry, choose the Default Multicast Mapping Table entry from the Default Multicast Mapping Selection drop-down box. Next, click Delete this Default Multicast Mapping Entry. To view or modify a Default Multicast Mapping Table entry, choose the entry from the Default Multicast Mapping Selection drop-down box. The table below describes the parameters that can be viewed or modified.
Parameter Multicast IP Address Multicast PID Multicast Mapping Entry Status Description This parameter specifies the Multicast IP Address for the current Multicast table. This parameter specifies the PID for the current Multicast table. This will define the status for the entry. The factory default setting is "Not In Service".
Table 4.6 Default Multicast Mapping Entry Configuration Parameters When you have finished modifying these parameters, click Save This Default Multicast Mapping Entry at the bottom of the page. This opens the Menu Result page. Depending on the combination of parameters that you changed, you may be required to perform an action before the changes take effect (see Appendix C).
Page 49
Table 4.7 MIB Trap Flag Configuration Parameters When you have finished modifying these parameters, click Save MIB Trap Flags 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 to perform an action before 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 Table Entry button. This is used for entering an entry initially not in service. After clicking this button, a refresh (or reload) of the MIB Trap Configuration page will display a new entry with default parameters. To delete an entry, choose the trap table entry from the Trap Destination Table Entry Selection drop-down box. Next, click Delete this MIB Trap Table Entry.
Page 50
Table 4.8 Trap Destination Table Entry Configuration Parameters When you have finished modifying these parameters, click Save This MIB Trap Table 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 to perform an action before the changes take effect (see Appendix C).
Page 51
Table 4.9 MIB Access Policy Configuration Parameters When you have finished modifying these parameters, click Save MIB Access Policy Flags. This opens the Satnetwork Menu Result page. Depending on the combination of parameters that you changed, you may be required to perform an action before the changes take 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 the MIB 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 Entry button. To delete an entry, choose the trap table entry from the MIB Access Policy Table Entry 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 Access Policy Table Entry Selection drop-down box. The table below describes the parameters that can be viewed or modified.
Page 52
Parameter Access Policy IP Address Access Policy Netmask Access Policy Community Name Access Policy Management Entity Name Access Policy Status
Description IP address of the network management entity. The factory default setting is 10.2.0.1. Network mask for the network management entity. The factory default setting is 255.0.0.0. The name of the corresponding community. The factory default setting is HUBManager. Management entity name. The factory default setting is PrimaryTM. This will define the status for the entry. - Active - Not in service The factory default setting is Active.
Table 4.10 MIB Access Policy Table Entry Configuration Parameters When you have finished modifying these parameters, click Save This MIB Access Policy Table 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 to perform 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 the defined 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 Entry button. To delete an entry, choose the trap table entry from the MIB Access View Table Entry 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 Access View Table Entry Selection drop-down box. The table below describes the parameters that can be viewed or modified.
Page 53
Description Displays the community name with its associated group OID that it can view. The factory default setting is HUBManager. Displays the OID of the access view group. The factory default setting is 1.1. Note that this setting is invalid. Defines the level of access rights the community has. The supported values are as follows: - Read only - Read-write - Not accessible The factory default setting is Read Only. This will define the status for the entry. - Active - Not in service The factory default setting is Active.
Table 4.11 MIB Access View Rights Table Entry Configuration Parameters When you have finished modifying these parameters, click Save This MIB Access View Rights Table 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 to perform an action before the changes take effect (see Appendix C).
4.7 PEP
Because satellite communication combines very high data rates (typically 4 to 40 Mbps over the forward link) with long round-trip delays (typically 600ms to 2s), TCP generally performs poorly over satellite links. Under these conditions, even a very small packet loss rate over the satellite link or minor terrestrial congestion results in significant congestion and traffic slowdown. By contrast, even with a loss rate that would dramatically lower TCP performance, the PEP suffers almost no reduction in data throughput. The PEP enables consistent, reliable performance for TCP/IP traffic under all conditions. It does this by replacing TCP with a Flight Protocol (FP) over the satellite link. The Flight Protocol is designed to optimize the use of available bandwidth. The PEP also requires a gateway PEP device installed at the satellite network.
Page 54
Page 55
Table 4.12 Forward Link Control and Managements Settings When you have finished modifying these parameters, click Save Forward Link Configuration 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 to perform an action before the changes take effect (see Appendix C).
Page 56
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
Page 57
Parameter Rx State
Description
The state shows locked when the demodulator is locked, and not locked otherwise. Rx/Tx State Tx State The state shows Enable when it is transmitting, and HOLD otherwise. Rx Status The state shows Acquired when the demodulator is locked, and not Acquired otherwise. Status Tx Status The state shows Initiazed when configured The state shows Ready when data can be transmitted Rx SNR Displays the Rx SNR value or, Not valid when there is no signal. Rx SNR/Tx Power Tx Power Displays the configured Tx Power. RF Frequency IF Frequency Displays the configured Rx and Tx RF frequencies. Displays the IF Rx and Tx IF frequencies. The IF frequency is derived from the configured RF frequency and the configured mixing frequency. Displays the configured Rx and Tx symbol rates, and the equivalent data rate (Tx only).
Symbol Rate
Page 58
MODCOD
Roll-Off
Pilot
Page 59
Ordering. From the drop-down list, choose whether to display the latest event first or the earliest event first. Severity. From the drop-down list, choose to display the messages by their severity level (alarm, error, event, all). Log location. From the drop-down list, choose to display the messages logged from the FLASH or the RAM of the IDU. All messages are logged in the RAM while only the most important messages are saved in the FLASH. Note that an IDU reset erases the 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 to FTP Server as SITLOG.BIN file button.
Note: The SITLOG.BIN file cannot be viewed by the user. It must be sent to Advantech Satellite Networks for decoding. To save a text record of the messages, 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 message to 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 a message occurred, if it happened more than once consecutively.
Page 60
Page 61
Description Current size of the queue, in IP packets Total amount of data received by the IDU over the return link, shown in IP packets and (bytes), since the queue was defined. Number of IP packets received by the IDU over the return link that have been discarded since the queue was defined. Total amount of data sent by the IDU over the return link, shown in IP packets and (bytes), since the queue was defined. Number of IP packets sent by the IDU over the return link that have been discarded since the queue was defined.
The Multicast Active Membership Monitoring Page is used to monitor the IGMP Querier and HOST states, PID and MAC for each Multicast Active Membership.
Page 62
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 This table contains the following elements: Interface BytesIn PktsIn BytesOut PktsOut Flags Local
Page 63
Page 64
Appendix A
Glossary
ACQ AGC Alarm BUC CRA CSC dB dBm dBW DVB-RCS Eb/No EIRP Error ESD FCA Filter pattern
Acquisition burst, used by the SIT to log on to the satellite network. Automatic Gain Control. A non-recoverable fault in the IDU that requires user intervention. See Transmitter. Continuous rate assignment. The return link rate capacity which is provided in full for each and every superframe while required. Common signalling channel burst, used by the SIT to log on to the satellite network. Decibel. Decibel milliwatts. A logarithmic measure of power, referenced to 1 milliwatt (1 mW = 0 dBm). Decibel watts. A logarithmic measure of power referenced to 1 watt (1 W = 0 dBW). Digital Video Broadcast-Return Channel System. An open standard for providing twoway broadband access over satellite. Signal to noise ratio. Effective isotropic radiated power. A measure of the amount of power radiated by the ODU. A problem with the IDU that does not require user intervention. Electrostatic discharge. Free capacity assignment. The return link volume capacity which is assigned to the IDU from capacity that would otherwise be unused. 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. Forward link. The path carrying communication from a hub (or gateway), via satellite, to SITs. It is based on the DVB/MPEG standard. File transfer protocol. Used for transferring software, configuration and other files to and
Page 65
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. 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. 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. Intermediate Frequency. Inter-facility link cables. See IDU. A section of the IDU web interface used for initial installation of the SIT. Internet Protocol. Local area network. The ODU component responsible for receiving forward link signals. 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. Multi-frequency time-division multiple access. Management information base. Operation, administration and maintenance. 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. Object Identifier. See ODU. Personal computer. Program Clock Reference. Performance Enhancing Proxy Packet Identification. Point-to-Point Protocol over Ethernet A code exchanged and used by computers that protects data sent and received by a web browser from unauthorized viewing or modification. Quality of Service 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. Rate-based dynamic capacity. The return link rate-based capacity that is requested dynamically by a SIT and assigned by the hub. 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 packets.
IDU
IDU Name IF IFL cables Indoor unit Installer page IP LAN LNB MAC Address MF-TDMA MIB OAM ODU OID Outdoor unit PC PCR PEP PID PPPoE Public key QoS Queue
Page 66
Routing Information Protocol Return link Return link sub-system. The part of the gateway responsible for receiving return link communication from SITs and relaying it to terrestrial networks (e.g. the Internet). It also manages all aspects of return link communication, including SIT logon, SIT synchronization, and allocation of return link capacity. Receive. Software image. A file containing IDU software that is downloaded and installed in the IDU. See SIT. The section of the IDU web interface used for initial satellite network configuration of the IDU. 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). Secure socket layer encryption. SSL protects data sent and received by a web browser from unauthorized viewing or modification. A section of the IDU web interface used for operation and maintenance of the IDU. Synchronization burst, used by the SIT to log on to the satellite network. Time-division multiple access. User data sent over the satellite network forward or return links. See Queue. Also called the BUC. The part of the ODU responsible for generating the return link signal. Transmit. Uplink power control. Volume-based dynamic capacity. The return link volume-based capacity that is requested dynamically by a SIT and assigned by the hub. Virtual Channel Connection. Virtual Channel Identifier. Voice over IP. Virtual Path Identifier. 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.
SSL Superuser page SYNC TDMA Traffic Traffic Queue Transmitter Tx ULPC VBDC VCC VCI VoIP VPI Web interface
Page 67
Appendix B
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 SIT from operating properly. Parameters underlined are read-only fields.
Page 68
Appendix C
When changes to parameters are saved, the Menu Result page opens. This page confirms that changes made to parameters are valid. It also prompts you to perform an action enabling the changes to take effect. Different parameters require different actions to be taken 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 the parameter take effect: if you made a change to a parameter requiring a reboot as well as to one which only requires logging off the SIT, it will prompt you to reboot the SIT. Any changes made to parameters are only implemented on the IDU after the appropriate action has been taken (if any is required). If you wish to continue modifying parameters, there is no need to perform the action right. 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 the configuration to be implemented on the IDU. Click button at the bottom of the Menu Result 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), you will be returned to the IDU home page.
Page 69