High Availability for Windows Demo Guide — September 2004 7
1
1.Demo Description
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.
