Filter
Top Products
Multiserver 5000
74
Next, select option 3 from the remote Command
Facility menu.
It may seem to be a paradox to use the term “local
node” when configuring the remote Multiserver.
Remember that when the remote Multiserver’s
Command Facility is accessed, in essence you are at
the remote site working as a local user. Therefore,
the Command Facility—and the work that you do
within the Command Facility—is considered local
to that Multiserver.
Select option 13, Node IDs, from the Configure
Local Nodes Menu.
At the ENTER NODE-ID # [240] prompt, enter
the node number. Press <cr> (refer to Section 3.4,
Syntax for Node Numbers and IDs, to review syntax
requirements).
Enter the node ID. Press <cr>.
The unit will reset and you will be returned to the
Command Facility on the local Multiserver.
(If you select C, your configuration will be placed
into temporary storage so that you can continue to
configure additional IDs. This should only be used
if you will be configuring the IDs of feeder muxes
that are attached to the remote Multiserver. Should
you configure a node ID, press C, and then exit the
Node ID Menu, your new configuration will be lost.
The old node ID(s) will remain intact.)
Once the remote node is renamed, access the
Command Facility of the remote node (explained
above) to configure remote ports and/or remote
feeder muxes (see Section 8.6 The Mux Link for
more information on configuring feeder muxes).
Exit the remote Command Facility when finished
(option 12). This will return you to the Command
Facility Main Menu on the local Multiserver.
COMMAND FACILITY MAIN MENU [!240]
CONFIGURE LOCAL NODES
3
CONFIGURE LOCAL NODES [!240]
NODE IDS
13
NODE ID CONFIGURATION
LOCAL NODE
1
ENTER NODE-ID # [240]: 50
ENTER NODE-ID (^X TO ABORT)
[!240]:
DENVER
** SELECT "Y" TO RESET SYSTEM
WHEN NODE CHANGES MADE **
ENTER "Y" TO RESET
"C" TO CONTINUE: Y