Filter
Top Products
Set Node Addresses On the Host Machines
8
Cisco BTS 10200 Softswitch Cabling and IRDP Procedures - AXmp Option
OL-4883-02
Set Node Addresses On the Host Machines
The following procedure explains how to set or change the node addresses on the host machines. This
procedure can be used on systems that are new, and on systems that are in service.
When multiple host machines are on a common CCPU Net, you must give each machine a unique node
address.
Note If two or more machines on a common CCPU Net have identical node addresses, unpredictable
operation can occur.
Step 1 Action: Disconnect CCPU Net A and CCPU Net B cables from the rear of one of the host machines.
Result: The red alarm light on the front of the unit will become illuminated. This is expected.
Why: The host machines communicate with each other through the CCPU Net cables. Disconnecting
these cables will isolate each unit and prevent non-unique addressed units from interacting.
Step 2 Action: Attach to console port. Connect to CCN CLI. You should see the following prompt
nodename(XX) ccncli>
where XX is the current node address in hexadecimal and nodename is the current name of that node.
Note If you don't see this prompt, depress the following keys ‘control+]’ followed by ‘.’ then press the
enter key two times. This will take you to the CCN CLI. If not, check your serial connection.
You should be using a straight cable, connecting at 38,400bps, 8,N,1.
Result: The prompt will report the current node setting.
Step 3 Action: From the CCN CLI prompt, type the following command ‘initmode on’.
Result: you will receive an echo of ‘initmode on’.
Why: This tells the CCN (control Computer) what state the system should be in when it is powered-up
or reset.
Step 4 Action: Set the jumpers on the unit.
Background: The host machines have jumpers on the receptacle that are used to set the node address of
the server. This node address is used to control the node alarming and out-of-band control commands
that go from node to node.
Caution The host machines should never be configured with duplicate addresses. If duplicate addresses are used,
commands designated for one system may be received by more than one system, and spurious operation
may result. For example, if two nodes have duplicate addresses, turning one node off may cause the
second node to turn off.