mapping offered by the MFC. Untagged frames are always forwarded to the MFC. Make sure that the
Ethernet interfaces connected to the VSAT operate in VLAN trunk mode (802.1Q) and provide correct
user priority tag values.
Note that the SatLink network is an IP network and not an Ethernet MAC bridge and thus the user priority
value will not be regenerated at the egress of the SatLink network.
Let‘s say that user wants to implement a ―scavenger class‖ for, as an example, peer-to-peer traffic and a
best effort class for normal traffic, based on Ethernet user priority:
First, set the Ethernet in VLAN trunk mode and allow traffic on applicable VLAN IDs:
# eth vlan 0
Here it is assumed that all traffic is going on the single VLAN ID 0 (e.g., being the default VLAN of the
LAN). Furthermore, the user priority tag values are mapped to QoS groups:
# eth primap 0 6 maps default user priority to internal critical data (becoming external
best effort)
# eth primap 1 0 maps user priority 1 down to internal best effort (becoming scavenger)
# eth primap 2 0 maps user priority 2 down to internal best effort (becoming scavenger)
# eth primap 3 6 maps user priority 3 to internal critical data (becoming external best
effort)
# eth show
Ethernet User Priority to QoS Group mapping
Priority QoS Group
0 6
1 0
2 0
3 6
18.7 DVB-S2 16-APSK
To enable the SatLink VSAT (SatLink 1000 and 1910 Rev 3.x, SatLink 2000, and SatLink 2900) to
receive 16-APSK DVB-S2 signals, the license key must be set to configure this. The below example
shows a printout of the sw show CLI command for VSAT with the appropriate DVB-S2 16APSK
license:
# sw show
SW versions:
Boot : 14.0.0.16
Current : 14.0.0.14
Backup :
Manual SW upgrade settings:
TFTP server IP addr : 10.10.1.1
File name : new.tgz
Automatic SW upgrade settings:
Activated : No
PID : 511
IP address : 224.0.1.59
Port No. : 2001
Licenses for SW options:
NAT
To Next Page
Loading...