User Manual

Configuration MP.11-R Installation and Management
Interface Parameters
79
• Maximum Satellites: 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: 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 (BSU Only) for details on configuration). This field is inactive
and makes no difference whether is enabled or disabled.
• Automatic Multi-Frame Bursting: 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 Roaming Configuration). In this case, each active SFC is
limited to send a single data message. Total throughput available to the 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 Roaming Configuration), 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:
– Automatic Multi-Frame Burst Support – The system will continuously monitor which of the active SFCs has the
highest priority and dynamically enable Multi-Frame burst for the highest priority SFC only, keeping all the lower
priority SFCs with Multi-Frame burst disabled. If there are multiple SFCs having the same, highest priority, all of
them will have Multi-Frame burst enabled. The maximum number of data messages sent in a burst is defined by
the parameter “Number of data messages in a burst” and it can be different for each SFC (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 Roaming Configuration), and enabling Automatic Multi-Frame Bursting (this
parameter). In this case, even the lowest priority SFC will have Multi-Frame burst dynamically enabled as long as
it is the only SFC in the system that has traffic. By default, configuring even a single high priority SFC with
automatic multi-frame bursting enabled will decrease throughput of low priority best-effort traffic to approximately
76% of maximum available throughput, because low priority traffic will have Multi-Frame burst disabled to optimize
bandwidth for the high priority traffic.
• Registration Timeout: This is the registration process time-out of an SU on a BSU. Default is 5 seconds.
Satellite Density Receive Sensitivity Threshold Defer Threshold
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:
4100%
3 97.6%
2 92.9%
1 76.2%