ND SatCom SKYWAN IDU 1070, Manual

Page: 116 / 154

112 Network Design and Engineering Guide 2010-10-26
Data Networking
SkyWAN
®
Internet Protocol Features
Figure 4-4 SkyWAN
®
Hybrid IP Data and Management Network
For simplicity the station’s LAN networks have been removed from the diagram, only the IP
over satellite networks are displayed. Like in the previous example, all the meshed stations are
connected via their Sat-UT1 (SatOne) interfaces to a common meshed core IP subnetwork. Ad-
ditionally there are two star subnetworks to which the hub stations are connected via their Sat-
UT2 (SatTwo) interfaces. The star terminals are connected via their Sat-UT1 (SatOne) inter-
face to their star subnetwork. IP packet forwarding from a star terminal to a non-hub meshed
station would still be possible, however requires two satellite hops.
Note that the satellite management interfaces of the star terminals are still connected to the
same satellite management network like the meshed stations. To ensure network management
connectivity, the station to which the
Sky NMS PC is connected must have direct satellite link
connectivity to every station. This condition is always fulfilled for the master and backup master
station, but may be possible also for other meshed stations.
4.2.3 Static Routing
IP packet forwarding to remote networks may be enabled by manual configuration of static
routes. The static routes are defined in the usual way by defining the destination network and
the next router hop to reach this network. Using static routes is a simple procedure which does
not consume additional bandwidth due to routing protocol updates.
However, in larger networks with a more complex topology maintaining the static route tables
on each station may become difficult. Also automatic rerouting in case of link or station failures
is not supported by static routing. In a network where redundancy is required, dynamic routing
will be needed.
The following features are supported on Sky WAN
®
IDUs: