High Availability Demo Guide

High Availability Demo Guide
High Availability for Windows
Demo Guide
September 2004
05-1924-002
INFORMATION IN THIS DOCUMENT IS PROVIDED IN CONNECTION WITH INTEL® PRODUCTS. NO LICENSE, EXPRESS OR IMPLIED, BY
ESTOPPEL OR OTHERWISE, TO ANY INTELLECTUAL PROPERTY RIGHTS IS GRANTED BY THIS DOCUMENT. EXCEPT AS PROVIDED IN
INTEL'S TERMS AND CONDITIONS OF SALE FOR SUCH PRODUCTS, INTEL ASSUMES NO LIABILITY WHATSOEVER, AND INTEL DISCLAIMS
ANY EXPRESS OR IMPLIED WARRANTY, RELATING TO SALE AND/OR USE OF INTEL PRODUCTS INCLUDING LIABILITY OR WARRANTIES
RELATING TO FITNESS FOR A PARTICULAR PURPOSE, MERCHANTABILITY, OR INFRINGEMENT OF ANY PATENT, COPYRIGHT OR OTHER
INTELLECTUAL PROPERTY RIGHT. Intel products are not intended for use in medical, life saving, or life sustaining applications.
Intel may make changes to specifications and product descriptions at any time, without notice.
This High Availability for Windows Demo Guide as well as the software described in it is furnished under license and may only be used or copied in
accordance with the terms of the license. The information in this manual is furnished for informational use only, is subject to change without notice,
and should not be construed as a commitment by Intel Corporation. Intel Corporation assumes no responsibility or liability for any errors or
inaccuracies that may appear in this document or any software that may be provided in association with this document.
Except as permitted by such license, no part of this document may be reproduced, stored in a retrieval system, or transmitted in any form or by any
means without express written consent of Intel Corporation.
Copyright © 2004, Intel Corporation
BunnyPeople, Celeron, Chips, Dialogic, EtherExpress, ETOX, FlashFile, i386, i486, i960, iCOMP, InstantIP, Intel, Intel Centrino, Intel Centrino logo,
Intel logo, Intel386, Intel486, Intel740, IntelDX2, IntelDX4, IntelSX2, Intel Inside, Intel Inside logo, Intel NetBurst, Intel NetMerge, Intel NetStructure,
Intel SingleDriver, Intel SpeedStep, Intel StrataFlash, Intel Xeon, Intel XScale, IPLink, Itanium, MCS, MMX, MMX logo, Optimizer logo, OverDrive,
Paragon, PDCharm, Pentium, Pentium II Xeon, Pentium III Xeon, Performance at Your Command, Sound Mark, The Computer Inside., The Journey
Inside, VTune, and Xircom are trademarks or registered trademarks of Intel Corporation or its subsidiaries in the United States and other countries.
* Other names and brands may be claimed as the property of others.
Publication Date: September 2004
Document Number: 05-1924-002
Intel Converged Communications, Inc.
1515 Route 10
Parsippany, NJ 07054
For Technical Support, visit the Intel Telecom Support Resources website at:
http://developer.intel.com/design/telecom/support
For Products and Services Information, visit the Intel Telecom Products website at:
http://www.intel.com/design/network/products/telecom
For Sales Offices and other contact information, visit the Where to Buy Intel Telecom Products page at:
http://www.intel.com/buy/wtb/wtb1028.htm
High Availability for Windows Demo Guide – September 2004
Contents
Revision History . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4
About This Publication . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Purpose . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Intended Audience . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
How to Use This Publication . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Related Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
5
5
5
5
6
1
Demo Description. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7
2
System Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9
2.1
2.2
3
Preparing to Run the Demo . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11
3.1
3.2
3.3
4
Connecting to External Equipment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Editing Configuration Files. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
3.2.1 Editing the redundant.cfg File for Peripheral Board Redundancy. . . . . . . . . . . . .
3.2.2 Editing the .config File for the Revenue Generating Application. . . . . . . . . . . . . .
RSS Program Prerequisite . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
11
11
11
12
14
Running the Demo . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15
4.1
4.2
4.3
5
Hardware Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9
Software Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9
Starting the Demo . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Using the Demo . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
4.2.1 Using the Revenue Generating Application/Peripheral Fault Manager Programs
4.2.2 Using the Redundant System Slot Program . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Stopping the Demo . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
15
15
16
19
19
Demo Details. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21
5.1
Files Used by the Demo . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21
High Availability for Windows Demo Guide – September 2004
3
Revision History
This revision history summarizes the changes made in each published version of this document.
Document No.
Publication Date
Description of Revisions
05-1924-002
September 2004
RSS Program Prerequisite section: Added information about when a takoever event
occurs, the SBC that went from ACTIVE to STANDBY must be rebooted before
becoming ACTIVE again. Added note about RSS steps required after initial
installation of the Intel® Dialogic System Software.
05-1924-001
November 2002
Initial version of document.
High Availability for Windows Demo Guide — September 2004
4
About This Publication
The following topics provide information about this publication:
• Purpose
• Intended Audience
• How to Use This Publication
• Related Information
Purpose
This publication provides information about the set of sample programs that demonstrate how to
integrate peripheral hot swap and redundant system slot into Intel® Dialogic cPCI computer
telephony systems.
The high availability demo is designed to illustrate how you can develop an application that
coincides with the Intel® Continuum of Availability, wherein you can expand system capacity
without completely restructuring your application.
Note:
Refer to the Economics of High Availability: An Intel® Primer white paper located at
http://www.intel.com/network/csp/resources/white_papers/ for complete information about the
various high availability architectures.
Intended Audience
This publication is written for the following audience:
• Distributors
• System Integrators
• Toolkit Developers
• Independent Software Vendors (ISVs)
• Value Added Resellers (VARs)
• Original Equipment Manufacturers (OEMs)
• End Users
How to Use This Publication
Refer to this publication after you have installed the hardware and the Intel® Dialogic® system
software that includes the high availability demo programs.
High Availability for Windows Demo Guide — September 2004
5
About This Publication
This publication assumes that you are familiar with the following:
• redundant system slot and peripheral hot swap high availability architectures
• C and C++ programming languages
• computer telephony terms and concepts
• Windows* operating system
The information in this guide is organized as follows:
• Chapter 1, “Demo Description” provides a description of the demo programs.
• Chapter 2, “System Requirements” lists the software and hardware required to run the demo
programs.
• Chapter 3, “Preparing to Run the Demo” provides instructions that must be followed before
running the demo programs.
• Chapter 4, “Running the Demo” includes information about running the demo programs.
• Chapter 5, “Demo Details” lists the files used by the demo programs.
Related Information
Refer to the following documents and Web site for more information about the software packages
and procedures used to develop the high availability demo programs:
• Event Service API for Windows Library Reference
• Event Service API for Windows Programming Guide
• Native Configuration Manager API for Windows Library Reference
• Native Configuration Manager API for Windows Programming Guide
• System Release for Windows Administration Guide
• System Release for Windows Software Installation Guide
• Intel® NetStructure™ on DM3™ Architecture Configuration Guide
• Global Call API Programming Guide
• Global Call API Library Reference
• System Release Guide
• System Release Update
• Economics of High Availability: An Intel® Primer white paper located at
http://www.intel.com/network/csp/resources/white_papers/
• http://developer.intel.com/design/telecom/support/ (for technical support)
• http://www.intel.com/network/csp/ (for product information)
6
High Availability for Windows Demo Guide — September 2004
Demo Description
1.
1
This chapter provides a brief description of the programs that comprise the High Availability demo.
The High Availability demo illustrates how to build a scalable, highly-available application with
Intel® Dialogic® System Software. When the demo programs are run in conjunction with one
another, they support a system that is capable of the following:
• detection of peripheral board faults
• fault identification to determine the origin of faults so that the component can be diagnosed
and corrected or replaced
• fault isolation to prevent the fault from affecting the rest of the system
• Single Board Computer (SBC) redundancy and peripheral board redundancy to restore the
system to an operational state if a critical fault occurs
• dynamic scalability, allowing you to add new peripheral boards to increase system capacity
The demo consists of the following programs:
Revenue Generating Application/Peripheral Fault Manager Program Set
The Revenue Generating Application (RGA)/Peripheral Fault Manager (PFM) program set
illustrates how to develop a highly available call control application using the following Intel®
Dialogic libraries:
• Global Call API Library
• Event Service API Library
• Native Configuration Manager API Library
• Standard Runtime API Library
The Revenue Generating Application uses the Global Call API library to make and receive
calls with the Intel® NetStructure™ boards in your system. As the RGA makes and receives
calls, the Peripheral Fault Manager (PFM) uses the Event Service API event notification
framework (ADMIN_CHANNEL and FAULT_CHANNEL events) and the Power On Self
Test-on-demand utility to provide the following features, all of which are done without
stopping the RGA:
• monitoring peripheral boards for Control Processor (CP) and Signal Processor (SP) faults
(fault detection)
• automatically running Power On Self Test (POST) diagnostics on any peripheral board
that generates a CP or SP fault (fault identification and diagnosis)
• automatically restarting a peripheral board that passes POST diagnostics (fault recovery)
• prompting a system administrator to replace a peripheral board that fails POST
diagnostics (fault isolation)
• basic hot swap of peripheral boards (fault repair)
Note: The Revenue Generating Application and the Peripheral Fault Manager must be run
in tandem.
High Availability for Windows Demo Guide — September 2004
7
Demo Description
Redundant System Slot Program
The Redundant System Slot (RSS) program is used in conjunction with the cPCI chassis
vendor demo that is installed as part of the Redundant System Slot Software package from the
Intel® Dialogic® CompactPCI for Windows CD-ROM. The RSS program demonstrates
redundant Single Board Computer (SBC) support on cPCI systems. One of the SBCs operates
in Active mode while the second (redundant) SBC operates in Standby mode. The chassis
vendor’s RSS software, as described in the Redundant System Slot Software for the Intel®
NetStructure™ ZT 5550 High Availability Processor Board Software Manual, is used to
generate a TAKEOVER event, which simulates a system-critical fault on the Active SBC. The
application notifies the RSS program via the Pigeon Point Hot Swap APIs or the rhdemo.exe
that a TAKEOVER event has occurred and automatically switches system control to the
Standby SBC.
Note:
8
Refer to the Intel® NetStructure™ ZT 5550 High Availability Processor Board Software Manual
located in the rss directory on your Intel® Dialogic system release CompactPCI for Windows 2000
CD-ROM for complete information about generating a TAKEOVER event.
High Availability for Windows Demo Guide — September 2004
System Requirements
2.
2
This chapter describes the requirements for running the various programs of the High Availability
demo. Topics include:
• Hardware Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9
• Software Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9
2.1
Hardware Requirements
To run the High Availability demo programs, you need the following hardware:
• A cPCI chassis that supports peripheral hot swap and/or redundant system slot architectures
Note: Refer to the Release Guide for a list of supported chassis.
• At least one Intel® NetStructure board
Note: The Revenue Generating Application (RGA) supports a maximum of five boards.
However, if there are both voice and network devices in the system, the ratio of
network devices (“dti”) to voice devices (“dxxx”) for all boards used by the RGA
must be less than or equal to five. Refer to the Standard Runtime Library API
Programming Guide for a complete overview of network and voice devices.
• At least one T1 or E1 crossover cable
Note: Crossover cables are only required to run the Revenue Generating
Application/Peripheral Fault Manager program set.
2.2
Software Requirements
To run the High Availability demo programs, you need to install the Intel® Dialogic® system
software, including the Hot Swap Kit and the Redundant System Slot software. Refer to the Intel
Dialogic System Software Installation Guide for complete information about installing the system
software.
High Availability for Windows Demo Guide — September 2004
9
System Requirements
10
High Availability for Windows Demo Guide — September 2004
Preparing to Run the Demo
3.
3
This chapter provides information about procedures to follow before running the High Availability
demo programs. Topics include:
• Connecting to External Equipment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11
• Editing Configuration Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11
• RSS Program Prerequisite . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14
3.1
Connecting to External Equipment
You must connect each of the board’s T1/E1 network interfaces with a crossover cable so that the
board can operate in loopback mode. For example, if you have a DM/V960-4T1-cPCI board
installed in your system, you must use a T1 crossover cable to connect the J1 network interface to
the J2 network interface and use a second crossover cable to connect the J3 network interface to the
J4 network interface. This allows the Revenue Generating Application to make calls on the
channels of the J1 and J3 network interfaces and receive those same calls on the channels of the J2
and J4 network interfaces.
3.2
Editing Configuration Files
This section provides information about editing configuration files for the Revenue Generating
Application program. The following topics are included:
• Editing the redundant.cfg File for Peripheral Board Redundancy
• Editing the .config File for the Revenue Generating Application
3.2.1
Editing the redundant.cfg File for Peripheral Board
Redundancy
The Revenue Generating Application (RGA) allows you to optionally configure your system for
peripheral board redundancy. Peripheral board redundancy allows you to assign a backup board for
each board that is initially used by the RGA. If a board has a backup board defined and the initial
board is taken out of the system due to a Hot Swap removal, the RGA automatically begins making
and receiving calls on the backup board.
If you are configuring your system for peripheral board redundancy, you must set up the
initial/backup board pairs by manually editing the redundant.cfg file (located at c:\program
files\dialogic\samples\HA\rgademo).
The redundant.cfg file contains one section, [PhysicalBoardRedundancy]. The
[PhysicalBoardRedundancy] section contains entries for assigning board pairs. Board pairs are
High Availability for Windows Demo Guide — September 2004
11
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-4T1cPCI 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]:
12
High Availability for Windows Demo Guide — September 2004
Preparing to Run the Demo
[CCS.1]
! Q.931 Timer Values in milliseconds
Setparm=0x0b,4000
! Q.931 timer 303. Default=4000 msec.
Setparm=0x0d,4000
! Q.931 timer 305. Default=4000 msec.
Setparm=0x0e,4000
! Q.931 timer 308. Default=4000 msec.
Setparm=0x0f,10000 ! Q.931 timer 310. Default=10000 msec.
Setparm=0x10,4000
! Q.931 timer 313. Default=4000 msec.
Setparm=0x15,1000
! TEI retry timer Default=1000 msec.
Setparm=0x16,900
! TEI state 4 min stability time. Default=900 msec.
Setparm=0x13,0
Setparm=0x18,0
Setparm=0x17,0
Setparm=0x7,11
Setparm=0x9,0
! Symmetrical C.R. protocol. 0=disable 1=enable
! Enable Feature Test
! ISDN Protocol Mode. 0 = USER_MODE; 1=NETWORK_MODE
! CCS_SWITCH_TYPE - QSIGE1 = 10, QSIGT1 = 11
! 0=disabled, 1=enable Layer 2 access.
! When Layer 2 access is enabled call control is no longer
! supported for the channels on this line.
[CCS.2]
! Q.931 Timer Values in milliseconds
Setparm=0x0b,4000
! Q.931 timer 303. Default=4000 msec.
Setparm=0x0d,4000
! Q.931 timer 305. Default=4000 msec.
Setparm=0x0e,4000
! Q.931 timer 308. Default=4000 msec.
Setparm=0x0f,10000 ! Q.931 timer 310. Default=10000 msec.
Setparm=0x10,4000
! Q.931 timer 313. Default=4000 msec.
Setparm=0x15,1000
! TEI retry timer Default=1000 msec.
Setparm=0x16,900
! TEI state 4 min stability time. Default=900 msec.
Setparm=0x13,0
Setparm=0x18,0
Setparm=0x17,1
Setparm=0x7,11
Setparm=0x9,0
! Symmetrical C.R. protocol. 0=disable 1=enable
! Enable Feature Test
! ISDN Protocol Mode. 0 = USER_MODE; 1=NETWORK_MODE
! CCS_SWITCH_TYPE - QSIGE1 = 10, QSIGT1 = 11
! 0=disabled, 1=enable Layer 2 access.
! When Layer 2 access is enabled call control is no longer
! supported for the channels on this line.
[CCS.3]
! Q.931 Timer Values in milliseconds
Setparm=0x0b,4000
! Q.931 timer 303. Default=4000 msec.
Setparm=0x0d,4000
! Q.931 timer 305. Default=4000 msec.
Setparm=0x0e,4000
! Q.931 timer 308. Default=4000 msec.
Setparm=0x0f,10000 ! Q.931 timer 310. Default=10000 msec.
Setparm=0x10,4000
! Q.931 timer 313. Default=4000 msec.
Setparm=0x15,1000
! TEI retry timer Default=1000 msec.
Setparm=0x16,900
! TEI state 4 min stability time. Default=900 msec.
Setparm=0x13,0
Setparm=0x18,0
Setparm=0x17,0
Setparm=0x7,11
Setparm=0x9,0
! Symmetrical C.R. protocol. 0=disable 1=enable
! Enable Feature Test
! ISDN Protocol Mode. 0 = USER_MODE; 1=NETWORK_MODE
! CCS_SWITCH_TYPE - QSIGE1 = 10, QSIGT1 = 11
! 0=disabled, 1=enable Layer 2 access.
! When Layer 2 access is enabled call control is no longer
! supported for the channels on this line.
[CCS.4]
! Q.931 Timer Values in milliseconds
Setparm=0x0b,4000
! Q.931 timer 303. Default=4000 msec.
Setparm=0x0d,4000
! Q.931 timer 305. Default=4000 msec.
Setparm=0x0e,4000
! Q.931 timer 308. Default=4000 msec.
Setparm=0x0f,10000 ! Q.931 timer 310. Default=10000 msec.
Setparm=0x10,4000
! Q.931 timer 313. Default=4000 msec.
Setparm=0x15,1000
! TEI retry timer Default=1000 msec.
Setparm=0x16,900
! TEI state 4 min stability time. Default=900 msec.
Setparm=0x13,0
Setparm=0x18,0
Setparm=0x17,1
Setparm=0x7,11
Setparm=0x9,0
! Symmetrical C.R. protocol. 0=disable 1=enable
! Enable Feature Test
! ISDN Protocol Mode. 0 = USER_MODE; 1=NETWORK_MODE
! CCS_SWITCH_TYPE - QSIGE1 = 10, QSIGT1 = 11
! 0=disabled, 1=enable Layer 2 access.
! When Layer 2 access is enabled call control is no longer
! supported for the channels on this line.
4. Save and close the updated .config file.
5. Use the fcdgen utility to generate an updated .fcd file for your Intel® NetStructure board.
6. Download the .pcd file and the updated .fcd file to your board(s) and start the Intel® Dialogic
System Services using the procedures outlined in the Intel® NetStructure™ on DM3™
Architecture for cPCI Configuration Guide.
High Availability for Windows Demo Guide — September 2004
13
Preparing to Run the Demo
3.3
RSS Program Prerequisite
As a prerequisite to running the Redundant System Slot (RSS) program, you must install the Intel®
Dialogic® system software, including the Redundant System Slot component, on both the Active
SBC and the Standby SBC. Both SBCs must be running Windows 2000*.
Note:
14
When the Intel® Dialogic System Software is installed for the first time on both SBCs, only the
Active SBC will have the drivers installed and the boards enumerated. The Standby SBC will not
have the boards enumerated in the system. To address this, you must prep the boards on the
Standby SBC by performing a cooperative switchover and enabling the boards. After this is done,
the Standby SBC can download and activate the boards when a the application notifies the RSS
demo that a failover/takeover event has occurred. This nofification is done via the Pigeon Point Hot
Swap APIs or the Pigeon Point rhdemo.exe demo program.
High Availability for Windows Demo Guide — September 2004
Running the Demo
4.
4
This chapter provides instructions on using the High Availability demo. Topics include:
• Starting the Demo . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15
• Using the Demo . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15
• Stopping the Demo . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19
4.1
Starting the Demo
If you are running the Revenue Generating Application/Peripheral Fault Manager (PFM) program
set, the Peripheral Fault Manager application must be started first. The default location of the PFM
executable file (pfmanager.exe) is C:\program files\dialogic\samples\HA\pfmanager. When the
PFM program is started, it displays a list of installed Intel® NetStructure™ boards according to
their physical slot number. When the PFM has detected all Intel® NetStructure boards in your
system, you must then start the Intel® Dialogic® System by clicking on the Start command from
the PFM’s System menu.
After you have started the Intel® Dialogic System and the PFM indicates that all boards are
‘Started’, you can then start the RGA demo. The default location of the RGA demo executable
(rgademo.exe) is C:\program files\dialogic\samples\HA\rgademo. When the RGA program is
started, it immediately opens the channels on the installed boards and begins making and receiving
calls. If a board has been designated as a backup board in the redundant.cfg file, it is displayed in
STANDBY mode.
Note:
Boards designated as backup boards do not begin making/receiving calls until the initial board in
the board pair is physically removed from the system.
You can start the RSS demo by running the rssmanager5084.exe or rssmanager5085.exe file. The
default location for this file is C:\program files\dialogic\samples\HA\rssmanager5084 or
C:\program files\dialogic\samples\HA\rssmanager5085 depending on the RSS-compatible chassis
you are using. Refer to the Release Guide for a list of chassis that support RSS.
4.2
Using the Demo
This section contains information about using the various programs that comprise the high
availability demo. The following topics are included:
• Using the Revenue Generating Application/Peripheral Fault Manager Programs
• Using the Redundant System Slot Program
High Availability for Windows Demo Guide — September 2004
15
Running the Demo
4.2.1
Using the Revenue Generating Application/Peripheral Fault
Manager Programs
The Revenue Generating Application main window provides information about each board used by
the application. The RGA main window displays the following information for each board:
• board number
• unique Addressable Unit Identifier (AUID)
• physical slot number
• current status
• number of calls processed by each board (number is updated every 100 calls)
• event notification framework events that are received by the Peripheral Fault Manager and
passed to the RGA. The following event notification framework events may be displayed in the
RGA main window:
– DLGC_EVT_BLADE_STOPPED
– DLGC_EVT_BLADE_REMOVED
– DLGC_EVT_BLADE_DETECTED
– DLGC_EVT_BLADE_STARTED
To stop processing calls on a board without using the PFM, access the RGA main window and
enter ‘p’, followed by the board number of the board you want to stop. This closes all open
channels on the specified board.
You can refresh the display on the RGA main window at anytime by pressing ‘r’.
Diagnosing Faults with the Peripheral Fault Manager
The Peripheral Fault Manager includes a DlgAdminConsumer object that is registered with the
event notification framework’s FAULT_CHANNEL. The object monitors the FAULT_CHANNEL
for the following events:
DLGC_EVT_CP_FAILURE
Generated when a Control Processor (CP) fault occurs on a board being used by the Revenue
Generating Application.
DLGC_EVT_SP_FAILURE
Generated when a Signal Processor (SP) fault occurs on a board being used by the Revenue
Generating Application.
When the Peripheral Fault Manager detects a CP or SP fault event, the following routine is
automatically invoked:
1. The PFM informs the RGA that a CP or SP fault has been generated by a board in the system.
2. The PFM instructs the RGA to quiesce the board. The RGA responds by stopping all calls on
the board and displays the board’s status as ‘quiesced’.
16
High Availability for Windows Demo Guide — September 2004
Running the Demo
3. After the board has been ‘quiesced’ by the RGA, the PFM calls the NCM_StopBoard( )
function to stop the board. This generates a DLGC_EVT_BLADE_STOPPED event that is
displayed in the RGA main window.
4. After the board has been successfully stopped, the PFM invokes the dm3post utility to perform
a Power On Self Test (POST) on the board that generated the CP/SP fault.
4a. If the board passes the POST, the PFM automatically calls the NCM_StartBoard( )
function to re-start the board.
4b. If the board fails the POST, the PFM main window displays a “Replace This Board”
message next to the failed board. You must then highlight the failed board in the PFM
main window and click Remove from the Device menu. You can then physically remove
the board from the chassis when the Out of Service (Blue) LED lights on the board’s
backplane.
Using the Peripheral Fault Manager to Replace a Board
The following procedure describes how to remove and replace (peripheral hot swap) a board that is
being used by the Revenue Generating Application:
1. In the Peripheral Fault Manager main window, highlight the board you wish to remove and
replace.
2. On the Device menu, click Stop. The PFM informs the RGA of the stop board request. The
RGA responds by updating the board’s status to ‘quiesced’, meaning it is no longer using the
board to make and receive calls.
3. After the board has been quiesced, the PFM invokes the NCM_StopBoard( ) function to stop
the board. When the board has been successfully stopped, the RGA displays the following
information in its main window:
Event Detected:
DLGC_EVT_BLADE_STOPPED with auid X, board Y, slot Z
where X is the Addressable Unit Identifier (AUID) of the board that is being stopped, Y is the
board number and Z is the slot number occupied by the board.
4. On the PFM main window Device menu, click Remove to remove the board’s configuration
information from the NCM database. This generates a DLGC_EVT_BLADE_REMOVED
event that is displayed in the RGA main window.
5. When the board entry is deleted from both the RGA main window and the PFM main window,
the Out of Service (Blue) LED on the board’s backplane will light up. You can then unlock the
board’s extraction handles and physically remove the board from the chassis.
6. Insert a replacement board into the system and wait for the board to complete its initial Power
On Self Test (POST). When the Plug and Play* observer service detects the newly inserted
board, a DLGC_EVT_BLADE_DETECTED event is generated and displayed in the RGA
main window.
High Availability for Windows Demo Guide — September 2004
17
Running the Demo
7. Configure the board for use by the RGA according to the procedures outlined in Chapter 3,
“Preparing to Run the Demo”.
8. Highlight the board in the Peripheral Fault Manager main window and click Start from the
Device menu. This generates a DLGC_EVT_BLADE_STARTED event that is displayed in
the RGA main window.
9. The RGA creates an entry for the board in its main window and automatically begins making
and receiving calls with the inserted board.
Using the Peripheral Fault Manager to Add a Board
The following procedure is used to add a board for use by the Revenue Generating Application
(expand system capacity):
1. Insert a board into your cPCI chassis. The Plug and Play* observer service detects the newly
inserted board and generates a DLGC_EVT_BLADE_DETECTED event. This event is
displayed in the RGA main window.
2. Configure the board for use by the RGA according to the procedures outlined in Chapter 3,
“Preparing to Run the Demo”.
3. In the PFM main window, highlight the inserted board and select Start from the Device menu.
This generates a DLGC_EVT_BLADE_STARTED event that is displayed in the RGA main
window.
4. The RGA then creates an entry for the board in its main window and automatically begins
making and receiving calls with the added board.
Using the Peripheral Fault Manager to Remove a Board
The following procedure shows how to remove a board that is being used by the Revenue
Generating Application:
1. In the Peripheral Fault Manager main window, highlight the board you wish to remove.
2. On the Device menu, click Stop. The PFM informs the RGA of the stop board request. The
RGA responds by updating the board’s status to ‘quiesced’, meaning it is no longer using the
board to make and receive calls.
3. After the board has been quiesced, the PFM invokes the NCM_StopBoard( ) function to stop
the board. When the board has been successfully stopped, the RGA displays the following
information in its main window:
Event Detected:
DLGC_EVT_BLADE_STOPPED with auid X, board Y, slot Z
where X is the Addressable Unit Identifier (AUID) of the board that is being stopped, Y is the
board number and Z is the slot number occupied by the board.
18
High Availability for Windows Demo Guide — September 2004
Running the Demo
4. On the PFM main window Device menu, click Remove to remove the board’s configuration
information from the NCM database. This generates a DLGC_EVT_BLADE_REMOVED
event that is displayed in the RGA main window.
5. When the board entry is deleted from both the RGA main window and the PFM main window,
the Out of Service (Blue) LED on the board’s backplane will light up. You can then unlock the
board’s extraction handles and physically remove the board from the chassis.
4.2.2
Using the Redundant System Slot Program
When you have generated a TAKEOVER event according to the procedures outlined in the Intel®
NetStructure™ ZT 5550 High Availability Processor Board Software Manual, the Redundant
System Slot program will immediately transfer system control to the Standby SBC. However, keep
in mind that when a TAKEOVER event occurs, the SBC that went from Active to Standby must be
rebooted before becoming Active again.
4.3
Stopping the Demo
To stop the Revenue Generating Application, press ‘q’ in the main window.
You must stop the Intel® Dialogic® System before stopping the Peripheral Fault Manager
program. Click Stop from the System menu to stop the Intel Dialogic System and then click Exit
to exit the Peripheral Fault Manager program.
High Availability for Windows Demo Guide — September 2004
19
Running the Demo
20
High Availability for Windows Demo Guide — September 2004
5
Demo Details
5.
This chapter provides more details about the High Availability demo programs. Topics include:
• Files Used by the Demo. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21
5.1
Files Used by the Demo
Table 1 lists some of the files used by the High Availability demo programs:
Table 1. Files Used by the High Availability Demo Programs
Directory
File Name
Purpose
c:\program files\dialogic\samples\HA\rgademo
rgademo.exe
Revenue Generating Application
executable file
c:\program files\dialogic\samples\HA\rgademo
redundant.cfg
file used by the Revenue Generating
Application to assign initial/backup
pairs for peripheral board redundancy
c:\program files\dialogic\samples\HA\rgademo
pfconsumer.cpp
implements an event handler for the
Event Service API
ADMIN_CHANNEL and the
FAULT_CHANNEL
c:\program files\dialogic\samples\HA\rgademo
mainThread.cpp
primary Revenue Generating
Application source code file
c:\program files\dialogic\samples\HA\pfmanager
pfmanager.exe
Peripheral Fault Manager executable
file
c:\program files\dialogic\samples\HA\pfmanager
pfmain.cpp
primary Peripheral Fault Manager
source code file
c:\program files\dialogic\samples\HA\pfmanager
adminhandler.h
defines and implements a class that
is derived from the Event Service API
CEventHandlerAdaptor::HandleEvent
()
c:\program files\dialogic\samples\HA\rssmanager
rssmanager508
4.exe
redundant system slot program
executable
rssmanager508
5.exe
High Availability for Windows Demo Guide — September 2004
21
Demo Details
22
High Availability for Windows Demo Guide — September 2004
Index
A
R
ADMIN_CHANNEL 7
Redundant System Slot 8
redundant.cfg file 11
revenue generating application 7, 12
rgademo.exe 15
rssmanager.exe 15
C
CCS_PROTOCOL_MODE (ISDN Protocol Mode) 12
config file 12
CP fault 7
crossover cable 11
E
Event Service API Library 7
F
S
SP fault 7
Standard Runtime API 7
T
TAKEOVER event 8
FAULT_CHANNEL 7
fcd file 12
fcdgen 12
G
Global Call API 7
I
initial/backup board pairs 12
L
loopback mode 11
N
Native Configuration Manager API Library 7
NETWORK_MODE 12
P
pcd file 12
peripheral fault manager 7
pfmanager.exe 15
POST 7
Power On Self Test 7
High Availability for Windows Demo Guide — September 2004
23
24
High Availability for Windows Demo Guide — September 2004
Was this manual useful for you? yes no
Thank you for your participation!

* Your assessment is very important for improving the work of artificial intelligence, which forms the content of this project

Download PDF

advertising