Comtech EF Data CDD-56X Series Vipersat - Manual (Page 73)

Chapter 3 - Using the Command Line Interface (CLI) 3-39
MN/22137, rev 1 Vipersat Configuration
Expansion Unit
The Expansion Unit menu item in the Vipersat Configuration screen
(figure 3-6) defines whether the target CDD-56X is to function as an Expansion
unit (all demods configured to operate in SCPC mode) or not. Entering E at the
command prompt will display the dialog shown in figure 3-51.
Figure 3-51 Expansion Unit prompt
The VMS uses this data when monitoring and controlling the network to deter-
mine the target CDD-56X’s function. For example, in a Hub configuration that
has STDMA enabled for the first demod, Expansion Unit should be set to No.
When configured as an Expansion unit, either as a Hub (switched) or as a
Remote (mesh), the CDD-56X is set up so that all demods are in SCPC mode
and available as resources for dedicated communications with the other end of
the satellite link.
For a Remote configuration, this parameter must be set to Yes. For a Hub
configuration, this parameter can be set to either No or Yes. Refer to table 2-1
and table 2-2 for a breakdown of network roles and related functions and
features.
Note: Setting Vipersat STDMA to Disabled alone will not force the demods into
an SCPC role—the Expansion Unit parameter must be set to Yes for this
function. Likewise, Expansion Unit must be set to No together with
STDMA Enabled for proper STDMA function.
Network ID
The Network ID that is assigned to the unit defines to what network the target
CDD-56X will belong. All units used in a network will have the same Network
ID. Enter B at the command prompt in the Vipersat Configuration screen
(figure 3-6) to display the dialog shown in figure 3-52.
NOTE