HP NonStop PATHWAY application monitoring using Reflex 80:20
The Reflex 80:20 Pathway automatic detection utility allows Reflex users to generate full graphical, drill-down object trees for the real-time monitoring of servers, terminals, programs and TCP's.
Supplied agents provide full status and information on all of these components and EMS events can also be directly mapped to the graphical component that is either vulnerable or critical.
Reflex 8020 PATHWAY application monitoring includes an autodetection utility and two status agents. These modules provide an array of monitoring functions for checking TERMINALS, OBJECTS, SERVERS, TCPs, PROGRAMS as well as complete configuration checking (using SPI) including:
- DEBUG ON/OFF
- number of supporting processes defined
- HOMETERM / program not present
- server running from a ZZBI file
- server FROZEN etc.
Autodiscovery Module - Pathway Systems
The Reflex 80:20 Pathway Auto-Discovery utility is designed to easily scan and load various user-definable Pathway components for a nominated Pathway system.
PATHAD supports the loading of the following PATHWAY components:
• Servers
• Terminals
• Programs
• TCP’s
REFLEX PATHWAY MONITORING module (PWYMON)
This is a polling module that checks the status of nominated Pathway serverclasses at regular intervals.
It can also be used to alert on situations which will produce a DOWN event or a VULNERABLE event. An UP event will be issued for when the situation has been resolved.
DOWN event situations
• The serverclass is running with less than the minimum number of processes, e.g. alert if the serverclass is running with less than 2 processes.
• The serverclass has debug enabled.
• The home terminal configured for the serverclass does not exist.
• The object that the serverclass is configured to use does not exist.
VULNERABLE event situations
• The serverclass is running against a ZZBI object.
• The serverclass is in a frozen state.
When the state returns back to an acceptable state then a corresponding UP event will be issued.
EMS event range:
SSID:
INSIDER.50.0
UP event:
6000
VULNERABLE event:
6001
DOWN event:
6002
A Reflex Transit file - TRANPWYM - is provided for the above events. The Reaction for all events utilises a format string value of ~manager~.~subject~, which relates to the EMS event tokens for 'Pathmon Process' and 'Pathway Server' respectively.
The contents of the transit file can be imported via the RFIMEX utility.
Monitoring Pathway ServerClasses
The Pathway serverclasses that are to be monitored are listed in a PWYLIST file. There can be a maximum of 10 PWYLIST files, which are named PWYLIST0 to PWYLIST9. Each file can have multiple serverclasses declared for monitoring.
These files are standard EDIT type files (filecode 101) and are typically stored in the Reflex data subvolume (RFLXDAT).
The contents of the PWYLIST files follow a strict format as follows:
| ? |
PATHMON |
Server Name |
Min |
DBUG |
HT |
PROG |
ZZBI |
FRZN |
| |
|
|
|
|
|
|
|
|
| Y |
$CPMN |
SERVER-NCP |
1 |
Y |
Y |
Y |
Y |
Y |
| Y |
$RFLX |
REFLEX-ADMIN |
1 |
Y |
Y |
Y |
Y |
Y |
| Y |
$RFLX |
REFLEX-SMON |
1 |
Y |
Y |
Y |
Y |
Y |
| Y |
$RFLX |
FILE-METS-MONIT |
5 |
Y |
Y |
Y |
Y |
Y |
Column references
• Any lines that have a ? in column 0 are treated as a comment.
• A Y in column 0 means that the declaration on that line is enabled; any other character means that the declaration is disabled.
• Column 2 is used to declare the Pathmon in which the serverclass is configured.
• Column 10 is used to declare the serverclass name.
• Column 31 is used to specify the minimum number of processes that the serverclass should have running.
• Column 41 is used to specify if debug alerting is required; values allowed are Y/N.
• Column 46 is used to specify if valid home terminal alerting is required; values allowed are Y/N.
• Column 51 is used to specify if valid program alerting is required; values allowed are Y/N.
• Column 56 is used to specify if ZZBI alerting is required; values allowed are Y/N.
• Column 61 is used to specify if frozen serverclass alerting is required; values allowed are Y/N.
An example file - PWYLIST0 - can be found in the Reflex data subvolume (RFLXDAT).
Reflex Admin / File Alias configuration
Each PWYLIST file that is to be used must be declared in the Admin / File Alias screen of Reflex, which shows the contents of
the Reflex DATACONF file. The File Aliases specified must be in the range PWYLIST0 to PWYLIST9.
Reflex Admin / Parameters configuration
The Admin / Parameters screen contains configuration details that are used by the Pathway Monitoring module, which are:
• PWYMON-INTERVAL - specifies the time interval in seconds, between monitoring polls to the specified Pathway serverclasses.
• PATHMON-PROCESS - specifies the Pathmon that Reflex is running under.