These steps can be performed with the redundancy manager (RMG) demonstration program or with an application that uses the Health Management service. In this topic, it is assumed that the RMG demonstration program is used.
The RMG demonstration program (rmg.exe [Windows] or rmg [UNIX]) is located in the following directories:
|
Operating system |
Directory |
|
Windows |
\Program Files\Dialogic\tx\bin\ |
|
UNIX |
/opt/dialogic/tx/bin/ |
For more information, refer to the RMG demonstration program overview.
In a single node system, both boards of the redundant set are in the same machine. A separate instance of the RMG demonstration program must be invoked for each board of the redundant set.
One board is arbitrarily designated as node 1 of the redundant set. The other board is designated as node 2 of the redundant set. In this example, board 1 is node 1 and board 2 is node 2. Each RMG must also designate a UDP port over which to communicate with the other RMG. By default, this port number is 1700. However, when the boards are on the same machine they must use different ports. For this example, the RMG for board 1 uses port 1700 and the RMG for board 2 uses port 1701.
For the first board, type the following command from an MS-DOS prompt:
rmg -b 1 -n 1 -p 1701
For this example, board 1 (-b 1) is designated as node 1 (-n 1). Its local port is 1700 (default), and the port number of its mate is 1701 (-p 1701).
For the second board, type the following command:
rmg -b 2 -n 2 -l 1701
For this example, board 2 (-b 2) is designated as node 2 (-n 2). Its local port is 1701 (-l 1701), and the port number of its mate is 1700 (default).
To use RMG in a dual node system, both machines must have an IP network connection to the other machine. This must be a different connection from the Ethernet crossover that links the two TX boards.
In a dual node system, each board of the redundant set is in a different machine. A separate instance of RMG must be invoked for each board of the redundant set.
One board is arbitrarily designated as node 1 of the redundant set. The other board is designated as node 2 of the redundant set. In this example, board 1 of machine A is node 1 and board 1 of machine B is node 2. To communicate with its mate, each RMG must also designate the IP address and UDP port of its mate. Since the boards are on separate machines, they can both use the default UDP port number, 1700.
For the first board, on machine A, type the following from an MS-DOS prompt:
rmg -b 1 -n 1 -m 1.1.1.2
For this example, board 1 (-b 1), of machine A, is designated as node 1 (-n 1). Its partner is machine B, whose IP address is 1.1.1.2. Its local port is 1700 (default), and the port number of its mate is 1700 (default).
Alternatively, the host name of machine B is specified with the -m command line option. Under Windows (with Microsoft Networking) or under UNIX, the host name can be used.
For the second board, on machine B, type:
rmg -b 1 -n 2 -m 1.1.1.1
For this example, board 1 (-b 1) of machine B is designated as node 2 (-n 2). Its partner is machine A, whose IP address is 1.1.1.1. Its local port is 1700 (default), and the port number of its mate if 1700 (default).
Alternatively, the host name of machine A is specified with the -m command line option. Under Windows (with Microsoft Networking) or under UNIX, the host name can be used.
Each RMG, on startup, attempts to load its designated board if the board has not already been loaded. The load script used is defined in the HMI configuration file. Refer to HMI configuration for more information.
The first node that starts RMG becomes the primary node. For this example, it is assumed that node 1 starts RMG first, which loads the board on node 1 first, and then goes to the primary state. The RMG for node 1 displays:
Board 1, Node 1 Board Loading
Board 1, Node 1 Now Starting
Board 1, Node 1 Board Isolated
Board 1, Node 1 Board Connected
Board 1, Node 1 Now Primary
It is assumed that node 2 starts RMG second. Node 2 goes to the backup state. The RMG for node 2 displays:
Board 1, Node 2 Board Loading
Board 1, Node 2 Now Starting
Board 1, Node 2 Board Isolated
Board 1, Node 2 Board Connected
Board 1, Node 2 Now Backup
|
If... |
Then the... |
For more information, refer to... |
|
Both RMG applications display Now Primary |
RMG applications are not communicating. |
|
|
The board connected event is not displayed |
Boards are not communicating |
If the RMG demonstration programs are not communicating, both of the boards go to the primary state (the Now Primary message displays for both boards). If this occurs, check the following items:
Physical IP network connection for each node.
IP addresses (or host names) used when RMG is started.
The local UDP port number of one RMG application matches the remote UDP port number of the other RMG application.
If a board connected event is not displayed by either RMG, there is a problem with the board to board connection.
Use the txalarm utility to determine the board communication state. During a successful system startup, the inter-board communication status should become connected, as shown in the following sample alarm output:
<05/14/1999 14:53:14> txmon 1 19745 Initialization complete
<05/14/1999 14:53:14> mtp 1 1 Configuring MTP Layer 1
. . .
<05/14/1999 14:53:14> mtp 1 1 MTP3: Ready...
<05/14/1999 14:53:14> txmon 1 19746 Task [mtp ] registered
<05/14/1999 14:53:14> txmon 1 19748 Mate board found at IP address
64.0.21.132
<05/14/1999 14:53:15> mtp 1 1 MTP3 Connected
<05/14/1999 14:53:15> isup 1 1 Registering ISUP Layer
<05/14/1999 14:53:15> isup 1 1 ISUP: Ready...
<05/14/1999 14:53:15> txmon 1 19746 Task [isup ] registered
. . .
<05/14/1999 14:53:17> mtp 1 18179 MTP3 Link 0 Up
If the boards cannot communicate after being downloaded, they remain isolated. During isolation, the signaling links terminated on the backup cannot be brought into service, and the backup board will not correctly reflect the state of the network. The most likely causes of isolation during turn-up of a new installation are:
Ethernet ports on the mated boards are not properly connected with a crossover cable.
txmon task was not downloaded when the board was loaded.
Mate IP addresses are not configured properly for both boards.
Once the boards are properly connected, enter the status (S) command to each RMG. Each RMG displays the following status:
RMG Board n Status
---------------------------
State :ACTIVE
Network Status : UNKNOWN
Heartbeats Sent: nnn Received: nnn
HMI Board n Status
-------------------------
Heartbeats Sent: nnn Received: nnn
Link State : Connected
Network State : Not Reported
mtp State = Primary
isup State = Primary
Confirm that the state is active and the link state is connected.