Prognosis Self Monitoring V2.

1
Description .................................................................................................................................................... 2
Deployment ................................................................................................................................................... 3
Support ........................................................................................................................................................ 12

Project Owners: Adam Annen (US) & Gerald Chaston (AU)

Version 2.1: 12/16/2016

Page 1 of 12
Description
The Prognosis Self Monitoring solution is a Threshold with supporting displays/dashboard and is designed to help
Prognosis administrators to simplify managing their Prognosis environment and detect issues in Prognosis from a top
level managing node. Its features cover the following areas:

• common critical errors in Prognosis error logs 'wvlog' with suggested solutions;
• old patch levels, low disk space and connectivity with Prognosis servers;
• databases wrapping too short or overdue for updates or auto-summarization failing;
• thresholds and analysts that stopped running;
• easy generate, retrieve 'irfax' and 'wvlog' diagnostics for requesting Support;
• alerts for Health Check issues found.

Prognosis Self Monitoring V2.1 includes:

Health Check Central display

Database Surveillance display\dashboard
Alerts Surveillance display\dashboard
Threshold for the key critical health check items on these displays\dashboards

Some of the key criteria behind these solutions are:

Management node only settings - No configurations or changes to monitoring nodes

- This allows scaling to very large environments and prevents the solution becoming a burden
Concentrate on areas not already monitored by other thresholds/analysts
Only show problems on the displays/dashboards/threshold
Easily maintainable
IR Support to install and train the Prognosis Administrator on it.

Platforms: UC monitored environments, Windows Infrastructure (Only 10.3 and above)

Page 2 of 12
Deployment
This Solution can be installed on the very top level Managing or Reporting Node for it to see all Prognosis servers in the
environment. If installed at the WEBUI node level, it can be published to the web as dashboards. Note: If you install at
this level, nodes above webui level will not be monitored. You could do a 2nd install there if needed and limit the
Prognosis Servers nodegroup to just that one node.

Step 1: Version Check & Hotfix install (If Needed)

1. If Prognosis Self Monitoring is to monitor any Prognosis servers with Prognosis versions 10.3, 10.4 or 10.5 then
make sure to apply the hotfix for a irpromgr memory leak issue. The hot fix files are the irfrmwrk_10x.zip files in
the 'PrognosisSelfMonitoring.zip' file.
The fix should go in the server directory (NB: NOT the server\x64 directory as promgr is 32 bit) after backing up
the existing files.
- Note: This fix needs to go on every 10.x node (Including monitoring nodes)
- No fix is needed for 11.0 Patch 4 or higher nodes/environments (Including 11.0 no patch)
2. If you have lower versions of Prognosis installed than 10.3, then you should use ‘Prognosis Self Monitoring Lite
(V1.x) instead.

Step 2: Create the Prognosis Servers nodegroup

1. Using the Windows Client Node Navigator expand the Prognosis Node and expand Configurations.
2. Right click on NODEGROUP and select Properties.

Page 3 of 12
3. Right click on ‘Current Configuration’ and select “Add”, then “Node Group”.

4. In the “Add New Node Group” dialog box enter “Prognosis Servers” and click OK.

5. The dialog box will close showing the Nodegroup Configuration window again. The new “Prognosis Servers”
entry will show in the list. Right click “Prognosis Servers” and select Properties. Then click the “+” symbol above
the bottom section and to the right side of the window.
6. The “Data View Definition” window will show. Expand “All” at the top of the “Available Data Fields” list. Navigate
to PrognosisNode, Highlight ‘SymbolicProcessIDOfRegisterer’ only and click the “>>” button to add it to the

Page 4 of 12
 “Selected Data Fields” list.

7. Click on the Nodes tab and select “Entire Network”.

8. Click on the Where Clause Tab and in the Where Clause section enter:
SYMBPROC = "NETRTR"
9. Click OK and the “Data View Definition” window will close.
10. The “Prognosis Servers” Properties window will be shown and should match the following image:

11. Click OK again to save it and wait 5 minutes for the changes to take effect.

Step 3: Create the prompts needed for the displays

1. In the Windows Client go to the Options Dropdown menu and select Maintain Prompts

Page 5 of 12
 2. Click the + symbol at the top of the window and then type in the values as per below screenshot:

3. Click OK button to save it.

4. While still in Maintain prompts, create another new prompt called #KBNumber
- Click the + symbol at the top of the window and then type in the values as per below screenshot

5. Click the OK button to save it, and then OK again to exist ‘Maintain Prompts’

Step 4: Install the files

1. Download 'PrognosisSelfMonitoring.zip' file.

Note: This is to be supplied by direct download link only. (Email servers typically will block or modify it).

Page 6 of 12
 2. Save 'PrognosisSelfMonitoring.zip' file to the Prognosis directory where Prognosis is installed. Such as
'C:\Prognosis' directory.
3. Right click the Zip and select ‘Extract All’ but before clicking ok, delete the end potion of the path so it only has
the path to your Prognosis install and no subfolder after that:
I.e. C:\Prognosis\, or D:\Prognosis\ etc

Note: The Zip should already contains the correct folder structure. If extracted exactly as per above, the files will
all go to the right subdirectories.
Note if this is applying a new version let new files overwrite existing files.

Step 5: Restart the Prognosis Service on the Prognosis Self Monitoring node only

1. Restart Prognosis for it to load the new record definitions.

Step 6: Configure 3 new command extractors (PSM V2.1 new feature)

1. Edit the EXTRACTOR configuration (In the Windows Client ) and add these lines to the bottom:

!Extractor Lines for Prognosis Self Monitoring

EXTRACT COMMAND (FSCOL, PSM\dbhealth.ext, irperl PSM\check_dbs.pl, 300, 0 )
EXTRACT COMMAND (FSCOL, PSM\thhealth.ext, irperl PSM\check_thresholds.pl, 300, 0 )
EXTRACT COMMAND (FSCOL, PSM\anhealth.ext, irperl PSM\check_analysts.pl, 300, 0 )

Note: the above 300 (5 minute) timing can be modified. It controls the refresh rate of the data for the
database/alert stats. For very large environments consider a 30 minute value.

2. Click Start to apply this EXTRACTOR configuration update and then click Close to exit.

Step 7: Post Install Configuration

1. Start the 'Prognosis Health Check' threshold.

It does 3 things:
- Populates the UC Devices Not Monitored pane in the Health Check Central dashboard.
- Detects the same conditions as displayed in the Health Check Central dashboard.
- Has a disabled condition 'zSendAlerts' condition that can be enabled and adjusted in order to have these alerts
sent to desired external systems such as SMTP email, SMS or SNMP trap destinations.
Note: Because the only condition that sends emails is disabled, this will not spam regarding existing problems.
The idea is to clean up the problems initially detected before enabling this zSendAlerts condition.

Page 7 of 12
2. Set up database surveillance:

2.1 Open the "Prognosis Health Check – Database Surveillance" display and use the “Update in client” links to
populate the PSM\dbs.txt with all the databases running on all Prognosis servers in the environment.

2.2 Copy the output text, expected to look like this:

Page 8 of 12
2.3 Paste the text into C:\Prognosis\Server\Configuration\PSM\dbs.txt

2.4 Save and close dbs.txt.

2.5 Repeat this

dbs.txt.
2.6 In EXTRACTOR configuration click Start to trigger it to scan those databases listed in dbs.txt.

2.7 Wait 5 minutes (depending how many and link speeds) for data to populate into this display. Expected result
is a display looking like this:

Page 9 of 12
 Note: Thresholds and Analysts also need setting up similar to the above (Refer to User Guide for more details on
all 3

3. Similarly, for thresholds and analysts open the "Prognosis Health Check - Alert Surveillance" display and use the
“Update in Client” links to populate the PSM\thresholds.txt and PSM\analysts.txt and with all the thresholds and
analysts running on all Prognosis servers in the environment.

Page 10 of 12
Page 11 of 12
Support
This Solution is currently provided as a non-GA customization. It is still supported by Product Support per region.
Support will help install this Solution on one top level Node. Updates to the Solution will be emailed as they become
available.

For problems found by this Solution, the recommendation is to first review the indicated Knowledge Base (KB) Article via
the Support Portal and follow the recommendations to rectify each problem. If this does not resolve the problem, then
please log a Support Case that includes:

1. Screenshot of the Prognosis Self Monitoring display showing the problem detected.
2. IRFAX and WVLOG from the affected system/s.
3. Information and screenshots indicating the results of the recommended KB Article.

Support Portal https://support.ir.com:

• Log Support cases

• Search Knowledge Base Articles
• Download all Patches

Online Portal: https://online.prognosis.com

• Download Prognosis and latest Patches

• Online Help Link
• Training Resources
• Community Forum

Page 12 of 12