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