User's Manual

Configuration MP.11 4954-R Installation and Management

Interface Parameters

Take care when configuring a remote interface; check the available signal level first, using Remote Link Test.

WARNING: When the remote interface accidentally is set at too small a value and communication is lost, it

cannot be reconfigured remotely and a local action is required to bring the communication back.

Therefore, the best place to experiment with the level is at the unit that can be managed without

going through the link; if the link is lost, the setting can be adjusted to the correct level to bring

the link back.

To set the Satellite Density, click the Configure button, then the Interfaces tab and the Wireless sub-tab. Make your

density selection from the drop-down menu. This setting requires a reboot of the unit.

Sensitivity threshold settings related to the density settings for the unit are:

• Maximum Satellites (BSU only): You can specify a maximum value of 250 in this field, because up to 250 SUs can

be connected to a BSU. If a BSU already has as many SUs as specified in this field, a new SU cannot connect to the

BSU.

• No-Sleep Mode (BSU only): No-Sleep Mode was a feature used to control jitter in Tsunami MP.11 products running

2.2.6, and earlier, versions of software. The introduction of QoS and the new WORP resource scheduling mechanism

have eliminated the need for No-Sleep Mode. Furthermore, QoS provides better control over jitter and latency-

sensitive applications (see QoS (Quality of Service) Parameters for details on configuration). This field is inactive and

makes no difference whether is enabled or disabled.

• Automatic Multi-Frame Bursting (BSU only): In order to achieve higher throughput, WORP protocol allows each

side (BSU or SU) to send a burst of up to 4 data messages instead of a single data message. The sole criteria for

sending a burst is enough traffic to be sent out. This feature is called Multi-Frame Bursting support.

Automatic Multi-Frame bursting optimizes multi-burst performance when configuring QoS high-priority Service Flows.

Three scenarios may be defined:

– No Multi-Frame Burst Support –To disable Multi-Frame burst support, click Configure > Network > Roaming,

and select “Disable” on the drop-down box (see BSU Screen). In this case, each active SFC is limited to send a

single data message. Total throughput available to remaining best effort traffic is around 76% of the maximum

available throughput.

Multi-Frame Burst Support – The system will enable Multi-Frame burst for all SFCs, but the maximum number of

data messages sent in a burst will be defined by the parameter “Number of data messages in a burst” for each of

the SFCs (see Service Flow Class (SFC). This scenario is set by clicking Configure > Network > Roaming and

enabling Multi-Frame burst on the drop-down box (see BSU Screen), and disabling Automatic Multi-Frame

Bursting (this parameter).

The maximum number of data messages in a burst directly influences the total throughput of the system. Typical

values are:

Set Satellite Density to: For a Receive Sensitivity Threshold of: And a Defer Threshold of:

Large -95 dBm -62 dBm

Medium -86 dBm -62 dBm

Small -78 dBm -52 dBm

Mini -70 dBm -42 dBm

Micro -62 dBm -36 dBm

No. of messages in a burst: % of the maximum throughput:

4 100%

3 97.6%

2 92.9%

1 76.2%