8.2 Ethernet Interface
8.2.1 Overview
The Mini CO SSPA supports several IP network protocols to provide a full featured remote M&C interface over an Ethernet LAN:
•IPNet protocol – redirection of standard Paradise Datacom LLC serial protocol over UDP transport layer protocol. This protocol is fully supported in Paradise Datacom’s Universal M&C software.
•SNMPv1 protocol - protocol intended for integration into large corporate NMS archi- tectures.
In order to utilize either of the protocols listed above, the relevant interface option has to be turned on. Refer to Sections 8.2.2 IPNet interface and 8.2.4.5 Configuring SSPA unit to work with SNMP protocol for details.
Of course, standard IP level functions such as ICMP Ping and ARP are supported as well. There is currently no support for dynamic IP settings, all IP parameters.
8.2.2 IPNet Interface
8.2.2.1 General Concept
Satcom system integrators are recognizing the benefits of an Ethernet IP interface. These benefits include:
•Unsurpassed system integration capabilities;
•Widely available, inexpensive support equipment (network cable; network hubs);
•Ability to control equipment over Internet;
•Ease of use
Implementation of the raw Ethernet interface is not practical due to the limitations it places on M&C capabilities by the range of a particular LAN. It is more practical to use an Ethernet interface in conjunction with the standard OSI (Open System Interconnect) model to carry a stack of other protocols. In an OSI layered stack, an Ethernet interface can be represented as a Data Link layer. All upper layers are resolved through a set of IP protocols. In order to keep data bandwidth as low as possible (which is important when M&C functions are provided through a
UDP (User Datagram Protocol) was chosen over TCP (Transmission Control Protocol) because it is connectionless; that is, no
Paradise Datacom provides a
70 | 208143 REV - | Operations Manual, HPA3, Mini Compact Outdoor SSPA |