12 High Availability for Windows Demo Guide — September 2004
Preparing to Run the Demo
assigned using the physical slot number of the boards installed in your system. For example, the
following redundant.cfg file entry assigns no backup boards for the boards in physical slots 1, 4
and 5, but assigns the board installed in physical slot 3 as a backup for the board installed in
physical slot 2:
[PhysicalBoardRedundancy]
BoardPair = 1, 0
BoardPair = 2, 3
BoardPair = 4, 0
BoardPair = 5, 0
Notes: 1. An entry of 0 indicates that a board does not have a backup board assigned.
2. Entries in the redundant.cfg file must be formatted exactly as shown in the example, with a space
before and after the =, and a space after each comma that separates the initial/backup board pairs.
3.2.2 Editing the .config File for the Revenue Generating
Application
If you are running the Revenue Generating Application/Peripheral Fault Manager program set, you
must edit the Intel® NetStructure board’s .config file and generate a new .fcd file so that your
board(s) can operate in loopback mode.
Refer to the Intel® NetStructure™ on DM3™ Architecture for cPCI Configuration Guide for
complete information about .config file parameters, .config file naming conventions, editing the
.config file and using the fcdgen utility to generate a new .fcd file.
Use the following procedure to configure boards used by the RGA to operate in loopback mode:
1. Determine the correct configuration file set (.config, .pcd, .fcd) for your board based on
network protocol.
2. Locate the .config file in c:\program files\dialogic\data .
3. Open the .config file with a text editor and change the CCS_PROTOCOL_MODE (ISDN
Protocol Mode) parameter (number 0x17) to 1 for each network interface that is receiving
calls via the crossover cable that was installed according to the instructions in Section 3.1,
“Connecting to External Equipment”, on page 11. For example, if you have a DM/V960-4T1-
cPCI board installed in your system, and the J1 network interface is connected to the J2
network interface via a crossover cable, you must edit the .config file to ensure that the
CCS_PROTOCOL_MODE (ISDN Protocol Mode) parameter for the J2, or second,
network interface is set to 1 for NETWORK_MODE. Likewise, if the J3 network interface is
connected to the J4 network interface via a second crossover cable, you must set the
CCS_PROTOCOL_MODE (ISDN Protocol Mode) parameter for the J4, or fourth, network
interface to 1 for NETWORK_MODE.
The following example is taken from the qs_isdn_qsigt1.config file, note that the
CCS_PROTOCOL_MODE (ISDN Protocol Mode) parameter has already been changed to
1 (NETWORK_MODE) for the second network interface [CCS.2] and the fourth network
interface [CCS.4]:
