20. Mesh VSATs
Mesh topology configurations enable direct VSAT-to-VSAT connectivity using a single satellite hop.
The main advantage of mesh operation (compared to star) is the low latency for real-time traffic and
reduced satellite bandwidth usage.
STM‘s mesh-capable VSATs are the SatLink 2900 and SatLink1910. The CLI command device show
in the example below shows the correct hardware required for the mesh operation (for the SatLink 1910):
# device show
System Information:
Name : MESH TERM-8 009F82
Location :
Contact :
System Up time : 0 days, 01:08:47
Core temperature : 36.0 degrees C.
CPU Load : 18%
System time(UTC) : 2 March 2009 15:06:21
Broadcast Message : not set
HW:
Model : SatLink 1910
HW ID : 103798
Main board ID : 120014 R1.1
Plugin-card HW:
Model : SatLink 150
HW ID : 108305
Revision : 2.0
Serial Number : 0408030009
MAC addresses:
Ethernet (LAN) : 00:20:0e:00:9f:82
Satellite (DVB) : 00:20:0e:00:9f:82
By default, a mesh VSAT only supports 1 mesh connection, where a mesh connection is one QoS class
link to another mesh VSAT. Support for more simultaneous connections is achieved by purchasing a SW
license mesh-connection n, where n = 2, 4, 6, 8, 10, 14, or 16.
The example below shows the CLI command sw show printout for a VSAT supporting a maximum of 8
simultaneous mesh connections. These 8 simultaneous connections can be realized as 4 QoS class links to
2 remote mesh VSATs, only 1 QoS class link to 8 remote mesh VSATs, or any combination in between.
# sw show
SW versions:
Boot : 9.0.1.7
Current : 13.0.2.65
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 : 234.5.6.7