UHP IP SUBSYSTEM

Planning and Building UHP Networks

UHP IP TRAFFIC PROCESSING AND ROUTING
INCLUDES:
• Static routing
• RIP v.2 announcing
• Prioritization and DSCP
• Voice Codecs
• RTP header Compression
• Traffic Shaper
• Policies
• IP Acceleration
• VLAN support (4095 VLANs)
• Multicast routing (static and IGMP)
• L2 bridging
• DHCP protocol
 UHP- IP
H
ARCHITECTURE
Modulator M TS
L

SCPC Demod.
IP router Local IP stack
svlan receive

TDMA Demod.
IP addresses “sub interfaces”

IP Routes
SVLAN encapsulation

SVLAN decapsulation LAN

QoS BASIC PRIORITIZATION
 UHP PRIORITIES
Instead of a configured policy, one of 8 built-in traffic priority queues can be selected in
the Tx Map route record. The number and assignment of priorities complies with the
IEEE 802.1q standard
BASIC ROUTER CLI COMMANDS

Adding IP-address to the Ethernet interface: The address and mask are separated with a blank.
Multiple addresses can be defined. If non-zero VLAN is specified then the address is added to
the route Table of this VLAN.

Adding static route

Route for transmitting IP-network via satellite. Parameters:

ml|mm|mh - Transmit priority (High, Medium, Low).
0-14095 - SVLAN number (0 – transmit without SVLAN encapsulation).
0-500 - Traffic Shaper channel number to pass the traffic. Optional parameter. If it is not
specified, the traffic will go via channel 0, the configuration of which should be checked at least
once to avoid surprises.
1-14095 - VLAN number to which the record refers.
BASIC ROUTER CLI COMMANDS

Add SVLAN reception from one of demodulators. When VLAN is specified the traffic will go
to its route Table instead of the basic one.

Delete address, route or map.

Delete record on SVLAN reception.

IP ROUTING - IP ADDRESS
IP ROUTING - STATIC ROUTE
IP ROUTING - TX MAP
IP ROUTING - SVLAN RECEIVE
TYPICAL IP CONFIGURATION
TYPICAL IP CONFIGURATION USING VLANS
L2 BRIDGING
• Bridging allows transfer of non-IP packets through UHP networks and
transparent merging of Ethernet segments through satellite channels.

• Bridging always works on some VLAN

• Packets tagged with this VLAN are bridged, not routed

• Other VLANs can be routed

• Several VLANs can work in bridge mode concurrently

•Traffic received on one side of satellite link with one VLAN, on the other side of the link can
be passed to the LAN with different VLAN, or untagged and vice versa

•In bridge mode all traffic entering the router is transmitted on another side. MAC filtering
and learning is not performed as attached Ethernet switch already performs these functions
BRIDGE COMMANDS

• Bridge selected VLAN to the satellite. On the other side of the link it is enough to
issue a command svlan receive … to perform traffic pass to the LAN.

• UHP router supports 802.1p (VLAN priority bits). If the bridge map is configured
using the MD queue, then tagged frames will be automatically reallocated to the
output queue according to the static levels of priority:
• 0, 1 - low
• 2, 3 - med
• 4, 5, 6, 7 - high

Remove bridging from selected VLAN.

BRIDGE SETTINGS
TYPICAL CONFIGURATION “BRIDGE”
TYPICAL IP CONFIGURATION USING VLANS
ROUTING TABLE
ROUTING TABLE CLI
UHP QoS
Quality of service in UHP has several mechanisms providing prioritizing and traffic regulation.
UHP QoS POLICIES

Policies enable the classification of IP packets and according to this classification,

perform certain actions on these packets.

Policy is referenced from IP map . One policy can be used for an unlimited number of
maps and works for all maps independently.

Each policy is a set of rules. Rules are of two types checks and actions. Checks
perform matching of packet header fields against predefined ranges. Actions
perform some actions on the packets.
POLICIES – CREATE-EDIT-INSERT
UHP QoS POLICIES (AND)
Inside the policy, a sequence of checks is usually followed by a sequence of actions.
Checks can be omitted. A policy containing only actions performs actions on all
packets unconditionally. If needed, after a sequence of actions another sequence of
checks can start.
UHP QoS POLICIES (OR)

Example shows that checks can have "OR" treatment rather than "AND" treatment
("Skip" flag). If any of checks matches, policy immediately jumps to nearest actions.
UHP QoS POLICIES
Example 1

All routes using this policy will immediately use the Action in this policy without any
check conditions and traffic will be sent to the high priority queue to the modulator.
UHP QoS POLICIES
Example 2

All routes using this policy will first check for the presence of the DSCP = 46 label in the packet
header. In case of coincidence, the policy will use Action (Action1 = queue HIGH) over the packet,
and it will be sent to the high priority queue for the modulator. If the check does not find
matches for the DSCP = 46 label, no actions will be performed.
UHP QoS POLICIES
Example 3
Both conditions will be checked in this policy (DSCP = 46 & UPD source ports = 5060-5061). If both
conditions coincide, an action will be taken on IP packets (Action1 = queue HIGH) and the traffic will be
sent to the high priority queue to the modulator.

If at least one of the conditions does not match, no action will be taken on IP packets.
UHP QoS POLICIES
Example 4

Both conditions will be checked in this policy (DSCP = 46, UPD source ports = 5060-5061). If one of the
conditions matches, an action will be taken on the traffic (Action1 = queue HIGH) and the traffic will be
sent to the high priority queue to the modulator.

If both conditions do not match, no action will be taken on the packets.

UHP QoS POLICIES
Example 5
 UHP TRAFFIC SHAPERS
Traffic shaper (TS) is intended for adjustment of the bandwidth occupied by data
streams in transmitting via a satellite.

TS is based on the streams concept – controlled “pipes” for traffic between router
and modulator.

Most often it serves to highlight a guaranteed band or speed limit

UHP routers support up to 2040 shaper channels. Each channel is an adjustable

"pipe" for IP traffic. The shaper is between the router and the modulator.
Advanced -> QoS -> Shaper

A traffic shaper along with policies is a key element in ensuring the quality of service
(QoS) of UHP equipment.
UHP TRAFFIC SHAPERS
 UHP TRAFFIC SHAPERS
Each channel is an adjustable "pipe" for IP traffic. The shaper is between the router
and the modulator .
 UHP TRAFFIC SHAPER
TS = 800 Kbps

CIR = 200 Kbps MIR = No Limit CIR = 400 Kbps MIR = No Limit

Load in TS channel
TRAFFIC SHAPER CHANNEL CONFIGURATION
TRAFFIC SHAPER CHANNEL CONFIGURATION
Traffic directions to the channels
Traffic is routed to the channel by setting the channel number in the TX Map records
of the routing table.
Traffic directions to the channels
Several TX Map entries can use the same channel, it transmits their total traffic. SVLAN
and priorities of these TX Map entries may be different.
TRAFFIC SHAPER MONITORING
VOIP & BANDWIDTH REQUESTS
• To make a request for bandwidth from a Hub, stations analyze the speed, packet size and type of
traffic it needs to transmit.

• The stations have two parallel running band request algorithms - for low-priority (plus medium-
priority) and high-priority real-time traffic.

• Traffic type is determined by the modulator queue (P1-P7), through which the traffic passes .

• For low-priority and medium priority (P1-P5), traffic, analysis is made at the modulator level of
transmission queue length and the transit traffic speed.

• The higher priority is the wider bandwidth requested by Terminal.

• For high-priority real-time traffic (P6-P7), basically only speed is analyzed.

• In the UHP platform, RT traffic is always considered as a stream (VoIP, videoconferencing).

• This approach makes it possible to predicatively allocate a bandwidth for this traffic.
 CODEC CONFIGURATION EXAMPLE

1. First call starts. High-priority modulator 3. One of the calls drops. Terminal still does not
traffic exceeded threshold value. Real- decrease its bandwidth request, since it does not
time bandwidth for full codec speed is
know whether the call is completed or whether
requested (16K).
there is just a pause. 10-second time-out count is
started.
2. Second call starts. Traffic exceeded
value of 20К (codec + threshold). Dual 4. Within 10 seconds traffic did not exceed 20K,
codec-rate bandwidth is requested Terminal refuses from one codec bandwidth
(32К).
5. Second call is being completed, traffic drops below
4К, and 10-second time-out count is started.
CODEC CONFIGURATION

Codec speed: For RT applications. For VoIP, it can be 8 or 16 kbit, for video conferencing – 384 or
512 kbit. A command set value shall be 10 to 15% higher than the codec known speed to allow
some bandwidth margin for headers and traffic bursts.

Threshold: Minimal speed after which it is considered that RT application started operation
and it is necessary to request a bandwidth for the entire codec. Usually, this value is
selected as 0.25 of the codec’s bandwidth.
Timeout: Time interval during which traffic should be lower than minimal so as to refuse
from RT bandwidth request.
RTP HEADER COMPRESSION

• When transmitting VoIP traffic by IP-protocol the size of headers of IP, UDP and RTP
protocols (in total not less than 42 bytes) can exceed the size of the voice portion of the
packet.

• Transmission of such packets via satellite is extremely inefficient with respect to bandwidth
usage, hence use is made of compression of protocols headers based on the fact that only few
fields change from packet to packet, and furthermore this change can often be predicted.

• In most cases the router compresses packet headers to up to two bytes.

• Header compression reduces network overhead and speeds up the transmission of either
Real-Time Transport Protocol (RTP) packets.

• In most cases the UHP router compress packet headers to up to two bytes.
 RTP HEADER COMPRESSION
To make compression work, it is essential that at the transmitting side (or at both sides) the ranges of UDP
(destination) port packets that the router will try to compress be adjusted accordingly. Compression will work
also in simplex mode (in one direction only). Packets passing successful compression will always be sent with high
priority.
The bottom idea is to pass only RTP packets to the compress RTP policy. SIP packets, or any other type of packet,
should not use the compress RTP policy.

RTP compression is activated by policies set-up.

RTP STATISTICS
Statistics of the compression can be obtained using # show rtp command.

Each string is a single compressed flow.

STATIC MULTICASTING AND IGMP
STATIC MULTICAST

• To collect Multicast traffic from LAN of a specified address you have to assign a
map for this traffic on the modulator. The router will itself understand that the
address (network) belongs to the Multicast range and will tune LAN to receive it.

• At the other side, to transmit this traffic to LAN it is necessary (apart from the
command to receive SVLAN used to receive this traffic) to assign a static route to
the Multicast address (network) of the transmitted traffic, having selected, as the
destination address, any address within the range of any of the IP networks
assigned to the router. The device with such address may be missing, it is more
important that the packets be routed to LAN.
IGMP

IGMP Join

IGMP Join

IGMP Join

Video
server
IGMP Join

Clients Head end & HUB

IGMP