Network Server Suite v8.1

Network Server Suite v8.1
networkserverSUITE v8.1
User Reference
What’s New in Version 8.1
Retry of messages that errored on Sending
When using Instant Alert, any messages that errored when sent can now be retried any number
of times using an interval period of seconds or minutes.
See “Adding a GSM Interface”, “Adding a NPort Interface” or “Adding a SMTP Interface” for more
information on this new feature.
Only send messages between specific times
In Network Server Suite v8.1 it is possible to specify times between which a contact’s phone is
defined as being ‘active’. Any messages sent outside of these times are queued and are
automatically sent when the phone becomes active again.
See “Adding a Contact to the Instant Alert Address Book” for more information on this new
feature.
Improvements to Service Monitor
The Service Monitor now allows the input of generic services by use of the wildcard entry ‘*’. This
allows you to control any service on your system without having to set up multiple and specific
criteria for each instance.
See “Service Monitor” for more information.
‘Today’ value in Web Application Monitoring
The ability to compare dates has been added to the Web application monitor within Network
Server Suite v8.1. This allows users to check against a date on a webpage and see if any
modifications have been made. This facility has primarily been added to facilitate the automatic
checking of version changes as they appear on company websites.
This feature is covered in more detail within the Web Application Monitoring User Reference.
-2
Network Server Suite
Table of Contents
What’s New in Version 8.1
Introduction
Managing Device Groups . . . . . . . . . .
General Tab - Information . . . . . .
Advanced Tab - Connection . . . . .
Advanced Tab - Notes . . . . . . . .
Managing Device Types . . . . . . . . . .
Managing Applications . . . . . . . . . . .
Creating a Client Access Application .
Device Manager Options . . . . . . . . . .
1
Before Installing . . . . . . . . . . . . . . . . . . 2
Product Overview
Installation Options
3
5
AIX® Installation. . . . . . . . . . . . . . . . .
Checking the version of the AIX® Server
Manager . . . . . . . . . . . . . . . . .
Monitoring a Virtual I/O Server (VIOS) . .
Linux® Installation . . . . . . . . . . . . . . . .
Port 15000 . . . . . . . . . . . . . . . .
HALUSM running as root . . . . . . . . .
Compatibility . . . . . . . . . . . . . . .
Identifying the Interfaces
Licensing Network Server Suite
.9
10
10
10
10
10
10
Enterprise Console Default User Name and
Password . . . . . . . . . . . . . . . . .
Changing Passwords. . . . . . . . . . .
Resetting Passwords. . . . . . . . . . .
Expired Passwords. . . . . . . . . . . .
Disconnection while Logged In. . . . . .
Users and Administrators . . . . . . . .
User and Administrator Privileges . .
Adding a New User. . . . . . . . . . . .
Editing User Details . . . . . . . . . . .
Deleting a User. . . . . . . . . . . . . .
11
13
Device Manager
.
.
.
.
.
.
.
.
.
.
Overview . . . . . . . . . . . . . . . . . . .
The Enterprise Console Display . . . . . . .
The Four Panels of the Enterprise Console
Changing the display . . . . . . . . . . .
User Messages . . . . . . . . . . . . . .
Command panel . . . . . . . . . . . . . .
.
.
.
.
.
.
Alerts
33
34
34
34
35
36
38
38
40
40
41
42
43
45
46
47
Overview . . . . . . . . . . . . . . . . . . . . 47
Alert Status . . . . . . . . . . . . . . . . . . . 47
Selecting Alerts . . . . . . . . . . . . . . . . . 48
View Alert Details . . . . . . . . . . . . . . . . 48
Adding Alert Comments. . . . . . . . . . . . . 49
2nd Level Help Text . . . . . . . . . . . . . . . 49
Copying Alerts for use in 3rd Party Applications 50
Replying to Inquiry Alerts . . . . . . . . . . . . 50
Alerts received via forwarding systems . . . . . 51
Printing Alerts . . . . . . . . . . . . . . . . . . 52
Launching applications directly from Alerts . . . 52
Sending Alerts to 3rd Party Helpdesk Applications .
53
Sending an alert as a Helpdesk Email . . 54
Sending an alert as an SMS . . . . . . . 54
Acknowledging Alerts . . . . . . . . . . . . . . 54
Purging Alerts . . . . . . . . . . . . . . . . . . 55
Closing Alerts . . . . . . . . . . . . . . . . . . 56
Closing alerts received from IBM i devices 56
Deleting Alerts . . . . . . . . . . . . . . . . . 56
17
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
Enterprise Console
Overview . . . . . . . . . . . . . . . . . . . . 13
Applying Individual Licenses . . . . . . . 14
Passwords and User Names
.
.
.
.
.
.
.
.
17
17
18
18
19
19
19
20
20
21
22
Overview . . . . . . . . . . . . . . . . . . . . 22
The Display . . . . . . . . . . . . . . . . . . . 22
Discovered Devices Panel . . . . . . . . 23
Defined Devices Panel . . . . . . . . . . 23
Messages Panel . . . . . . . . . . . . . 23
Automatic Detection of Devices . . . . . . . . . 24
Manual Addition of Devices . . . . . . . . . . . 25
General Settings . . . . . . . . . . . . . . . 26
Important notes regarding LINUX® Servers
27
Advanced Settings . . . . . . . . . . . . . . 29
SNMP Settings . . . . . . . . . . . . . . . . 31
Importing and Exporting Device Settings . . . . 32
Enterprise Console Options
Overview . . . . . . . . . . . . . . . .
Options tab - General page. . . .
Options tab - Command page . .
Options tab - Advanced page. . .
Display tab - Display page . . . .
Display tab - Default Colors page
Audio. . . . . . . . . . . . . . . . .
1
57
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
57
58
58
59
59
60
61
Audio tab – Sounds page .
Audio tab - Speech page .
Changing Passwords. . . . .
Reloading Devices . . . . . . .
Reloading Address Book . . . .
Enterprise Server Options
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
61
62
62
62
63
Syslog Monitor . . . . . . . . . . . . . . . 98
Syslog Monitor Tab – Syslog Monitor page 98
Syslog Message Facilities . . . . . . . . 99
Syslog Message Severities . . . . . . . . 100
Forwarding Syslog Messages from a Linux®
Device . . . . . . . . . . . . . . . . . . 100
Advanced . . . . . . . . . . . . . . . . . . 101
Advanced Tab - Email/SMS Default settings
page . . . . . . . . . . . . . . . . . . . 101
Advanced Tab - Helpdesk Defaults page . 102
Advanced Tab - Instant Alert page . . . . 104
Advanced Tab - SQL Server page . . . . 104
Advanced Tab - Messages page . . . . . 105
Advanced Tab - License page . . . . . . 105
Editing licenses . . . . . . . . . . . . . . 107
Enterprise Server Options buttons . . . . 108
Device Dialog . . . . . . . . . . . . . . . . . . 109
View Device Dialog (Read-only Mode) . . . 109
64
Overview . . . . . . . . . . . . . . . . . . . 64
General Settings . . . . . . . . . . . . . . . 65
General tab - General page . . . . . . . . 65
General tab - Device page . . . . . . . . 65
General tab - Users page . . . . . . . . . 66
Alert Settings . . . . . . . . . . . . . . . . . 66
Alerts tab - Alerts page . . . . . . . . . . 66
Alerts Tab - Archive page . . . . . . . . . 67
Alerts tab - Alert Types page . . . . . . . 68
Editing Alert Types . . . . . . . . . . . . 69
Alerts tab - Source Types page . . . . . . 69
Adding a new Source Type . . . . . . . . 70
Editing Source Types . . . . . . . . . . . 71
Deleting Source Types . . . . . . . . . . 71
Filters . . . . . . . . . . . . . . . . . . . . 71
Adding/Editing Filters. . . . . . . . . . . . . 72
Filter tab – Filter page. . . . . . . . . . . 73
Filter tab – Default Display page . . . . . 74
Filters tab – Alert Message page . . . . . 75
Adding Filter Criteria . . . . . . . . . . . 79
Criteria tab - Criteria page . . . . . . . . 80
Setting Alert Detail Criteria for iSeries Alerts
82
Setting Alert Detail Criteria for Server
Manager Alerts . . . . . . . . . . . . . . 83
Setting Alert Detail Criteria for SNMP Trap
Alerts . . . . . . . . . . . . . . . . . . . 84
Setting Alert Detail Criteria for Syslog
Messages . . . . . . . . . . . . . . . . . 85
Criteria tab - Device Selection page . . . 86
Actions Tab – Actions page . . . . . . . . 88
Escalating the Priority of Pending Alerts . 88
Actions . . . . . . . . . . . . . . . . . . . . 93
Connection Monitor . . . . . . . . . . . . . 94
Windows, AIX and Linux Servers . . . . . 94
Halcyon iSeries software . . . . . . . . . 94
Connection Monitor working with Halcyon
Legacy software. . . . . . . . . . . . . . 95
Connection Monitor - Connection Monitor
page. . . . . . . . . . . . . . . . . . . . 95
Ping Monitor . . . . . . . . . . . . . . . . . 96
Ping Monitor - Ping Monitor page . . . . . 96
Ping Monitor Tab - Device Selection page 97
Enterprise Console Archive
Overview . . . . . . . . . . . . . .
About Archive Files . . . . . . . . .
Creating Multiple Archive Files .
Creating One Master Archive File
Viewing an Archive File . . . . .
110
.
.
.
.
.
Central Configuration Manager
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
. 110
. 110
. 111
. 112
. 112
114
Overview. . . . . . . . . . . . . . . . . . . 114
CCM Server . . . . . . . . . . . . . . . 114
Systems Tab . . . . . . . . . . . . . . . . . 115
Adding a System to Central Configuration
Manager . . . . . . . . . . . . . . . . . 117
Deleting Systems . . . . . . . . . . . . . 118
Re-installing software remotely . . . . . . 118
Templates . . . . . . . . . . . . . . . . . . 119
Advanced . . . . . . . . . . . . . . . . . . 120
Messages page. . . . . . . . . . . . . . 120
License page . . . . . . . . . . . . . . . 120
Saving Central Configuration Manager settings .
120
Central Configuration Manager Options . . . 121
CCM Server page . . . . . . . . . . . . 121
Connection page . . . . . . . . . . . . . 121
Enterprise Server Page. . . . . . . . . . 122
Installation Page . . . . . . . . . . . . . 122
Instant Alert Page . . . . . . . . . . . . 122
Logging Page. . . . . . . . . . . . . . . 122
Other Central Configuration Manager features .
123
Synchronizing Settings . . . . . . . . . . 123
2
Application Event Log/Security Event Log/
System Event Log . . . . . . . . . . . . 156
Event Log Monitors Group (Additional) . . . 156
Directory Service Event Log . . . . . . . 156
File Replication Service Log . . . . . . . 156
DNS Server Log . . . . . . . . . . . . . 156
Performance Monitors . . . . . . . . . . . . 156
Windows® Management Instrumentation
Monitor . . . . . . . . . . . . . . . . . . 156
CPU, Disk and Memory Monitor . . . . . 156
System Monitors . . . . . . . . . . . . . . . 157
File & Folder Monitor . . . . . . . . . . . 157
Log File Monitor . . . . . . . . . . . . . 157
Services Monitor . . . . . . . . . . . . . 157
TCP Monitors . . . . . . . . . . . . . . . . 157
TCP FTP . . . . . . . . . . . . . . . . . 157
TCP HTTP . . . . . . . . . . . . . . . . 157
TCP NNTP . . . . . . . . . . . . . . . . 158
TCP Ping . . . . . . . . . . . . . . . . . 158
TCP POP3 . . . . . . . . . . . . . . . . 158
TCP SMTP . . . . . . . . . . . . . . . . 158
TCP Telnet . . . . . . . . . . . . . . . . 158
TCP/UDP Generic . . . . . . . . . . . . 158
AIX® Monitors . . . . . . . . . . . . . . . . 159
AIX® Error Report Monitor . . . . . . . . 159
Subsystem Monitor . . . . . . . . . . . . 159
Logical Volume Monitor. . . . . . . . . . 159
Script Monitor. . . . . . . . . . . . . . . 159
File & Folder Monitor . . . . . . . . . . . 159
Log File Monitor . . . . . . . . . . . . . 159
CPU, Filesystem & Memory Monitor . . . 160
System Monitor . . . . . . . . . . . . . . 160
Process Monitor . . . . . . . . . . . . . 160
Ping Monitor . . . . . . . . . . . . . . . 160
Linux® Monitors . . . . . . . . . . . . . . . 160
Linux® Logical Volume Monitor . . . . . 160
Script Monitor. . . . . . . . . . . . . . . 161
File & Folder Monitor . . . . . . . . . . . 161
Log File Monitor . . . . . . . . . . . . . 161
CPU, Filesystem & Memory Monitor . . . 161
System Monitor . . . . . . . . . . . . . . 161
Process Monitor . . . . . . . . . . . . . 161
Ping Monitor . . . . . . . . . . . . . . . 161
Business Software Monitors . . . . . . . . . 162
Web Application Monitor . . . . . . . . . 162
Monitor Functions . . . . . . . . . . . . . . . . 162
Sequence Numbers . . . . . . . . . . . . . 162
Monitor Dialogs . . . . . . . . . . . . . . . . . 163
Monitor Settings and Startup Options . . . . 164
Importing and Export Central Configuration
Manager settings . . . . . . . . . . . . 123
Auto Collapse . . . . . . . . . . . . . . 124
Upgrade Systems . . . . . . . . . . . . 124
Alert Log . . . . . . . . . . . . . . . . . . . . 126
Search Page . . . . . . . . . . . . . . 126
Results Page . . . . . . . . . . . . . . 128
More Information . . . . . . . . . . . . . . 129
Instant Alert
130
Overview . . . . . . . . . . . . . . . . . . 130
Server Options . . . . . . . . . . . . . . . 130
General page . . . . . . . . . . . . . . 131
Logging page . . . . . . . . . . . . . . 132
Purge page . . . . . . . . . . . . . . . 132
Enterprise Server page . . . . . . . . . 132
Interfaces page . . . . . . . . . . . . . 132
Adding Interfaces . . . . . . . . . . . . 133
Adding a GSM Interface . . . . . . . . 133
Adding a NPort Interface . . . . . . . . 134
Adding a SMTP Interface . . . . . . . . 135
Address Book . . . . . . . . . . . . . . . 136
Adding a Contact to the Instant Alert Address
Book . . . . . . . . . . . . . . . . . . 137
Creating a Broadcast Group . . . . . . 139
Creating a schedule. . . . . . . . . . . 139
Finding a Contact . . . . . . . . . . . . 140
Message Sender . . . . . . . . . . . . . . 140
Using Lotus Notes® (v7 or later) with Instant
Alert. . . . . . . . . . . . . . . . . . . . 142
Working with Substitution Variables 146
Overview . . . . . . . . . . . . . . . . . . 146
Understanding Substitution Variables . . . 147
The basics . . . . . . . . . . . . . . . 147
Using Substitution Variables within text . 148
Adding Parameters to Substitution Variables
148
Substitution Variable Parameters . . . . . 150
Numeric Parameters . . . . . . . . . . 150
String Parameters . . . . . . . . . . . . 151
SNMP Monitoring
152
Overview . . . . . . . . . . . . . . . . . . 152
Setting up the SNMP Device in Device Manager
152
Making a Device a SNMP Trap Target . . . 153
Working with Monitors
155
About the Monitors . . . . . . . . . . . . . . 156
Event Log Monitors Group (Standard) . . . 156
3
Monitor Log Messages . . . . . . . . . . . 165
Adding Monitor filters . . . . . . . . . . . . . 165
Filter options . . . . . . . . . . . . . . . . 166
Filter page. . . . . . . . . . . . . . . . 166
Alert page . . . . . . . . . . . . . . . . 167
Advanced page . . . . . . . . . . . . . 168
Criteria options . . . . . . . . . . . . . . . 169
Criteria Summary page . . . . . . . . . 169
Adding Filter Criteria . . . . . . . . . . 170
Actions options . . . . . . . . . . . . . . . 170
Actions Summary page . . . . . . . . . 170
Adding Filter Actions . . . . . . . . . . 170
Setting the order of actions . . . . . . . 171
Event Log Monitors . . . . . . . . . . . . . . 172
Example Application Event Log Monitor filter
173
Performance Monitors . . . . . . . . . . . . . 174
CPU, Disk & Memory Monitor . . . . . . . 174
Example CPU, Disk & Memory Monitor filter
175
WMI (Windows® Management Instrumentation)
Monitor . . . . . . . . . . . . . . . . . . 176
Example WMI Monitor filter . . . . . . . 178
System Monitors. . . . . . . . . . . . . . . . 179
File & Folder Monitor . . . . . . . . . . . . 179
Example File/Folder Monitor filter . . . . 181
Log File Monitor . . . . . . . . . . . . . . 182
Selecting Log Files . . . . . . . . . . . 183
Example Log File Monitor Filter . . . . . 184
Service Monitor. . . . . . . . . . . . . . . 185
Example Service Monitor filter . . . . . 186
TCP Monitors . . . . . . . . . . . . . . . . . 187
Testing TCP Monitors . . . . . . . . . . 188
TCP Monitor Options . . . . . . . . . . 191
Example TCP Ping Monitor filter . . . . 191
Example TCP HTTP Monitor filter . . . 192
AIX® Monitors . . . . . . . . . . . . . . . . . 192
AIX® Error Report Monitor . . . . . . . . . 194
Subsystem Monitor. . . . . . . . . . . . . 196
Logical Volume Monitor . . . . . . . . . . 197
Script Monitor . . . . . . . . . . . . . . . 199
AIX® File & Folder Monitor. . . . . . . . . 200
Log File Monitor . . . . . . . . . . . . . . 202
CPU, Filesystem & Memory Monitor . . . . 203
Performance Data. . . . . . . . . . . . 204
System Monitor. . . . . . . . . . . . . . . 205
Process Monitor . . . . . . . . . . . . . . 206
AIX® Ping Monitor . . . . . . . . . . . . . 208
AIX® Actions . . . . . . . . . . . . . . . . 209
AIX® Templates . . . . . . . . . . .
AIX® Reporting . . . . . . . . . . .
Linux® Monitors. . . . . . . . . . . . .
Linux® Logical Volume Monitor . . .
Script Monitor . . . . . . . . . . . .
File & Folder Monitor . . . . . . . .
Log File Monitor . . . . . . . . . . .
CPU, Filesystem & Memory Monitor.
Performance Data . . . . . . . .
System Monitor . . . . . . . . . . .
Process Monitor . . . . . . . . . . .
Linux® Ping Monitor . . . . . . . . .
Linux® Actions. . . . . . . . . . . .
Linux® Templates . . . . . . . . . .
Linux® Reporting . . . . . . . . . .
Templates
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
. 209
. 209
. 210
. 210
. 212
. 212
. 214
. 215
. 215
. 217
. 218
. 219
. 220
. 220
. 220
221
Overview . . . . . . . . . . . . . . . . . . . . 221
Using the default templates . . . . . . . . . 222
Windows® Templates . . . . . . . . . . . . . . 223
Active Directory template . . . . . . . . . . 223
Exchange Server (Performance) template . 224
Exchange Server (Services) template . . . . 224
M3 Monitoring template . . . . . . . . . . . 225
Server Performance (Advanced) template . 226
Server Performance (Standard) template . . 227
SQL Server template . . . . . . . . . . . . 227
Terminal Services template . . . . . . . . . 228
AIX® Templates. . . . . . . . . . . . . . . . . 228
AIX System Monitoring (Standard) Template 228
AIX® System Monitoring (Advanced) Template .
231
Linux® Templates . . . . . . . . . . . . . . . . 234
RED HAT System Monitoring (Standard)
Template . . . . . . . . . . . . . . . . . . 234
RED HAT System Monitoring (Advanced)
Template . . . . . . . . . . . . . . . . . . 235
SUSE System Monitoring (Standard) Template .
237
SUSE System Monitoring (Advanced) Template
239
Creating bespoke templates . . . . . . . . . . 240
Applying Templates . . . . . . . . . . . . . . . 241
Modifying Individual Systems. . . . . . . 242
Exporting and Importing Templates . . . 243
Reporting
244
Overview . . . . . . . . . . . . . . . . . . . . 244
Applying the Reporting Monitor to a System . . 244
Purging Performance Data . . . . . . . . 245
4
Adding Reporting Fields . . . . . . .
Defining Reporting Fields . . . . . .
Setting SLA Flags In Filter Criteria
Reporting Template . . . . . . . . . . .
Exporting and Importing Settings
.
.
.
.
.
.
.
.
.
.
.
.
245
246
249
250
252
Overview . . . . . . . . . . . . . . . . . . . 252
Exporting Settings from Central Configuration
Manager . . . . . . . . . . . . . . . . . 252
Importing Settings into Central Configuration
Manager . . . . . . . . . . . . . . . . . 253
Exporting Settings from Enterprise Server
Options . . . . . . . . . . . . . . . . . . 253
Importing settings into Enterprise Server
Options . . . . . . . . . . . . . . . . . . 253
Troubleshooting
254
To Report an Error . . . . . . . . . . . . . 254
Contact Details . . . . . . . . . . . . . . . 254
Company Information
255
Head Office. . . . . . . . . . . . . . . . . 255
Copyright . . . . . . . . . . . . . . . . . . . 256
5
C
HAPTER
INTRODUCTION
CHAPTER1
This document covers the set up of Halcyon Network Server Suite and
component use. For installation guidance, please refer to the Installation Guide.
For detailed assistance while using the product, please refer to the on-line help
that is supplied with the software. For further queries and assistance, please
refer to the support section at www.halcyonsoftware.com.
As there are a variety of installation options according to what you want to
monitor, your network size, configuration and physical location, we recommend
you review the function of each of the Halcyon products and plan on which of
your networked machines you wish to install specific Halcyon products to meet
your particular monitoring requirements.
At the simplest level, all Network Server Suite products can be installed onto
one machine as detailed in the Installation Guide.
However, this assumes that the machine onto which the products are installed
is the only machine to be monitored. In practice, multiple machines, possibly
sited in different geographical locations, will require monitoring.
Halcyon Network Server Suite further extends the Halcyon portfolio to serve
Windows® 2000/2003/XP/Vista/7, AIX®, UNIX® and Linux® operating systems.
It monitors the key areas of the servers and performs pre-determined actions as
required.
Network Server Suite products have been designed to simplify the task of
dealing with a large number of error messages, and alerts and enable you to
identify and handle critical problems easily. Multiple systems can be graphically
displayed on a single screen, in an easy-to-read format. Administrators and
operators can view and respond to events directly from any machine the on
which the Enterprise Console is installed.
The suite also contains additional tools to help you ensure that your systems
are working correctly. For instance, a series of monitors, including the Ping
Monitor, can periodically verify that a particular system is available, raising an
alert if not.
Inquiry and informational messages are viewed and responded to directly from
the Enterprise Console and other types of messages can be acknowledged.
Introduction
1-1
Other alerts, displayed automatically, include TCP/IP connectivity problems,
performance problems (resource hungry jobs or capacity thresholds exceeded).
Before Installing
Read this guide thoroughly and follow these recommendations:
Review the Products
Review the Network Server Suite products and their functions to understand
how to apply them to suit your monitoring requirements.
See “Product Overview” on page 2-3 for more details.
Review your Network & Requirements
Review your network with regard to machine access and location; then plan on
which machines specific products are to be installed, taking into account:
• physical and geographical location.
• accessibility of the machine(s) you use to display alerts via the Enterprise
Console.
• accessibility of the machine(s) you use to configure the services via the
Central Configuration Console.
• the impact of additions or reductions to your network.
Retaining Existing User Names & Privileges
(this step only applies to users of pre-v4 Enterprise Console)
If you have a number of user names and privileges you wish to keep, record
these details before uninstalling older version of the Enterprise Console.
Identify the Machines on your Network
Before you start installing, we recommend recording your network name(s) and
TCP/IP addresses of each machine onto which you plan to install the Server
Manager and Enterprise Server. You need this information when you set the
products up for monitoring.
Installing Multiple Copies of the Server Manager
For Windows® machines this can now be done remotely.
Note:
Note:
1- 2
See “Adding a System to Central Configuration Manager” on page 13-117 for
more information on this feature.
For AIX® machines, use the Halcyon UNIX Server Manager (HALUSM) and
install this product on each machine locally.
Please refer to the Network Server Suite Installation Guide for detailed
information on how to install AIX® Server Manager.
Network Server Suite
C
HAPTER
PRODUCT OVERVIEW
CHAPTER 2
A suite of Halcyon products are installed and registered as part of the Network
Server Suite installation routine.
These products comprise:
• Enterprise Console v8.8: the central point (GUI) used to display alerts
(received from the Enterprise Server) and allow the administrator(s) and
operator(s) responsible for any problems/issues to take remedial action as
necessary. This product is the ‘eye’ of your network.
• Enterprise Archive Viewer v8.8: a standalone GUI dedicated to viewing
data contained in .eca (Enterprise Console Archive) files.
• Enterprise Server v8.8: a service designed to receive alerts from a variety
of sources and manage these alerts centrally via any networked machine(s)
with the Enterprise Console product installed. Any number of incoming
connections can be handled simultaneously; the only limitation(s) are
imposed by machine hardware limitations (processor speed, memory, etc.).
• Enterprise Server Options v8.8: this product (GUI) is used to configure
Enterprise Server settings. Enterprise Server Options functionality allows you
to:
• specify user access rights
• set up filters
• set up alerts
• specify ping and connection monitor defaults
• set up email messaging
• Central Configuration Console (CCMConsole) v6.1: this product is used
as a framework to host and configure associated services.
• CCM Server: a service associated with the Central Configuration Console.
Product Overview
2-3
• Server Manager v6.1: this product monitors the server environment. One
copy of the Server Manager must be installed on each server to be
monitored.
Remote installation of the Server Manager software is possible when adding
a new system. Server Manager software can also be upgraded on existing
systems.
The Server Manager is configured via the Central Configuration Manager
and enables administrators to set up system requirements centrally and then
distribute these settings to any other machines on which the Server Manager
is installed.
• SNMP Manager v1.3: this product provides control of Enterprise hubs,
routers and switches or any SNMP enabled device. It is used to identify
SNMP-enabled network devices, process traps received from these devices
and pass this data to the Enterprise Server and the SNMP monitor group as
alerts.
It polls the connected devices on a regular basis and automatically reports
the status to the Enterprise Server. The SNMP Manager also includes an
‘auto-discovery’ function that locates networked devices automatically and
builds a static list of those devices to monitor.
• Instant Alert v2.10: this product is used to send text messages to mobile
phones from either the Server Manager or Enterprise Console. Email
messages can also be sent. For ultimate flexibility, broadcast groups and
schedules can be set up so messages are sent to the appropriate on-call
personnel. A message log is provided to monitor the status of messages.
• Device Manager v2.8: a stand-alone product used for:
• auto-discovery of networked devices by poll, walk or broadcast
• manual entry of devices
• device categorization
• launching default application(s)
• Network Manager v2.6: an xml interface which operates in the background
and allows communication between all Network Server Suite products. It is
automatically installed and has no user-configurable capability.
• USM (AIX agent) v7.1: this component monitors the AIX server
environment in the same way as Server Manager (see above) monitors the
Windows server environment.
• USM (Linux agent) v7.1: this component monitors the Linux server
environment in the same way as Server Manager (see above) monitors the
Windows server environment.
• Performance Reporting v1.3: this component is used to provide a graphical
representation for CPU, DIsk and Memory performance data for up to 5 disk
drives per system
2- 4
Network Server Suite
C
HAPTER
INSTALLATION OPTIONS
CHAPTER3
Network Server Suite products can be installed in a variety of ways to suit your
networking and monitoring requirements and also the physical location of your
machines.
Default installation options within the InstallShield package comprise:
• Typical, Custom and Enterprise Console Client options:
• The Typical installation option installs all products including the Server
Manager onto one machine (all visual monitoring and configuration would
then have to be performed at this machine).
• The Custom installation option installs whichever products you select from
a given list onto one machine.
• The Enterprise Console Client installation option installs just the
Enterprise Console client component onto a single machine.
However, where you install these is dependant on your network location,
configuration and accessibility to machines for monitoring and configuration.
Please refer to the following table for an overview of possible installation
options:
Installation Options
3-5
Product
Function
Typically Installed On
Enterprise
Console
Displays alerts and other
system details via the
Enterprise Server
One or more server or
client machines, according
to who needs access to
view alerts and other
network information
Enterprise
Server
A configurable service (via
Enterprise Server Options)
One (server or client)
machine - multiple copies
of the Enterprise Console
on different machines
allow users to view the
same alerts processed by
one Enterprise Server
installation.
Receives alerts from a variety
of sources and allows users
to manage them centrally
through the Enterprise
Console
Licence: Requires a
separate licence for each
server where Enterprise
Console is installed with
its own database
3- 6
Enterprise
Server
Options
Configures Enterprise Server
settings
The same machine as
Enterprise Server
Enterprise
Console
Viewer
Allows the .eca (Enterprise
Console Archive) files to be
viewed
The same machine as the
Enterprise Server but
could be installed on any
machine which can
access the directory to
which .eca files are saved.
CCM Server
A background service
associated with the Central
Configuration Manager
Automatically installed
with the Central
Configuration Manager
Network Server Suite
Central
Configuration
Console
A host or framework within
which other products can be
configured.
One machine, this can be
any networked server or
client machine with remote
access to the Server
Manager(s) and other
hosted products.
License: The CCM must
have an authorization
code applied but the
actual machine on which
CCM runs does not need
to be assigned one of the
resulting Windows
licences in order to
operate, although it is
recommended.
Server
Manager
A configurable service hosted
by the Central Configuration
Manager
Used to set up and monitor
the server environment
Instant Alert
The machine(s) on the
network to be monitored
(these could be servers
and/or client machines)
Used to send text messages
to mobile phones from the
Server Manager or Enterprise
Console. Email messages
can also be sent
Usually installed on the
same machine as the
Central Configuration
Manager.
SNMP
Manager
Used to identify SNMP
enabled network devices,
process thresholds received
from these devices and pass
this data to the Enterprise
Server
The same machine as the
Server Manager
Network
Manager
A background service that
allows communication
between all client and server
services and GUI(s)
Automatically installed in
conjunction with any other
product.
Licence: Separate licence
required (Instant Alert
only) if installed on a
separate machine.
Installation Options
3-7
Device
Manager
A configurable stand-alone
product.
Allows auto-discovery of
network devices, manual
entry of network devices,
device categorization and
launching of device
associated applications
USM (AIX
Agent)
USM (Linux
Agent)
Typically installed on the
same machine as the
Central Configuration
Manager for convenience,
however it could be
installed on any other
networked server or client
machine.
Used to set up and monitor
the AIX server environment
The AIX machine(s) on
the network to be
monitored
Used to set up and monitor
the Linux server
environment
The Linux machine(s) on
the network to be
monitored
The diagram below shows one possible installation configuration. Products in
brackets are installed automatically as there is no user-interaction with these
products.
At the simplest level, all products can be installed onto one machine; however, it
will normally be more suitable to install different products onto different
machines to suit product function and user accessibility.
Example of Installation across a Simple Network
Figure 3.1
3- 8
Sample installation of Network Server Suite
Network Server Suite
Other products can be installed according to the following conditions and
recommendations:
• Enterprise Console – used to allow system alerts and other information to
be displayed, this product can be installed on a single or multiple machines to
suit accessibility, although a license is required for each instance of the
Enterprise Server product.
• Central Configuration Console – only one installation is normally required
as this product is used to host the Server Manager and other products used
to set up and configure the system. This product is typically installed on the
same machine as the SNMP Manager, Instant Alert, Device Manager and
the Enterprise Server.
• Server Manager – one copy must be installed on each machine to be
monitored and a license is required for each instance.
• Enterprise Server Options - used to configure the Enterprise Server.
• Device Manager - used to detect network devices, this product can be
installed on any machine, but we have shown it on the same machine as the
Central Configuration Console for ease of local access.
AIX® Installation
Halcyon UNIX® Server Manager (HALUSM) can only be installed onto an AIX®
partition running library bos.rte.libpthreads at level 5.3.0.50 or higher.
To check this, run the command:
lslpp -h bos.rte.libpthreads
An entry should be displayed as:
There may be multiple versions shown. Only one version needs to be level
5.3.0.50 or higher for the install to be successful.
If your AIX® partition is not running at this level, you must upgrade before
HALUSM can be installed on this partition.
Note:
Please refer to the Network Server Suite Installation Guide for detailed
information on how to install AIX® Server Manager.
Installation Options
3-9
Checking the version of the AIX® Server Manager
To check which version of AIX® Server Manager you are running, please use
the command:
rpm -qi halusm
Monitoring a Virtual I/O Server (VIOS)
The Virtual I/O Server is part of the PowerVM Editions hardware feature and is
software that is located in a logical partition. This software facilitates the sharing
of physical I/O resources between client logical partitions within the server.
The Virtual I/O Server provides virtual SCSI target, virtual fibre channel, Shared
Ethernet Adapter, and PowerVM™ Active Memory Sharing capability to client
logical partitions within the system. Client logical partitions can share SCSI
devices, fibre channel adapters, Ethernet adapters, and expand the amount of
memory available to logical partitions using paging space devices.
The Virtual I/O Server software requires that the logical partition be dedicated
solely for its use.
Note:
Previous work undertaken by Halcyon has shown that we are capable of
natively monitoring the Virtual I/O Server by installing the AIX Server Manager
directly onto the logical partition on which the Virtual I/O Server is installed.
Please refer to the Network Server Suite Installation Guide for detailed
information on how to install AIX® Server Manager.
Linux® Installation
Port 15000
As part of the Linux® agent installation, port 15000 is automatically opened on
the firewall, using the command:
iptables -I INPUT -p tcp -m tcp --dport 15000 -j ACCEPT
This is done so that the Linux® server can communicate with Network Server
Suite. Ideally, you should modify the entries within ‘iptables’ to restrict access
via port 15000 to internal network addresses only.
HALUSM running as root
For the purpose of monitoring the Linux server, HALUSM runs as root.
Compatibility
Halcyon Linux® Server Manager has been successfully installed and tested on
RED HAT Enterprise Linux Server v5, SUSE Linux Enterprise Server 11,
openSUSE v11.2, and CentOS v5.3 only.
Note:
3- 1 0
Please refer to the Network Server Suite Installation Guide for detailed
information on how to install Linux ®Server Manager.
Network Server Suite
C
HAPTER
IDENTIFYING THE INTERFACES
CHAPTER4
Five products are used as the interfaces to all system functions. See below for
icon identification and how each interface is used:
Icon
Product Name
Comment
“Enterprise Console”
Used to display and respond to
system alerts
“Enterprise Server
Options”
Used to configure the Enterprise
Server
“Central
Configuration
Manager”
Used to configure the Server
Manager
“Device Manager”
Used for auto-discovery or manual
entry of network devices; device
categorization and launching of
device associated applications.
“Enterprise Console
Archive”
Used to view .eca (Enterprise
Console Archive) files
Identifying the Interfaces
4-11
Icon
Product Name
Comment
“Instant Alert”
Used to send text messages to
mobile phones from either the
Server Manager or Enterprise
Console. Email messages can also
be sent.
Instant Alert comprises three
components:
• Address Book
• Message Sender
• Server Options
“Reporting”
Used to provide details of
performance data that can then be
used to generate reports using
Halcyon’s Advanced Reporting
Suite
The other installed products operate as services or are accessed via the
“Central Configuration Manager”.
4- 1 2
Network Server Suite
C
HAPTER
LICENSING NETWORK SERVER SUITE
CHAPTER5
Overview
Note:
The initial licensing of Network Server Suite is undertaken as part of the
installation.
Please refer to the Network Server Suite Installation Guide for more details
on this procedure.
This version of Network Server Suite utilizes a licensing option that is more
flexible and transparent to the user, allowing you to add, change, remove and
re-assign licences to servers across your network.
Note:
Note:
System-wide licensing is updated via Enterprise Server Options (as well as in
Central Configuration Manager) but individual licensing of systems is now solely
maintained via the Central Configuration Manager.
Please note that any authorization codes issued prior to this release of
Network Server Suite will no longer be valid. You must request a new
authorization code if you are upgrading from a previous version of Network
Server Suite.
Please refer to the “Editing licenses” on page 11-107 for more details on how
to maintain the full license code for Network Server Suite.
Licensing Network Server Suite
5-13
Figure 5.1
Product License Details
Applying Individual Licenses
As systems are added to the Central Configuration Manager, they appear as
unlicensed until a license has been assigned.
An unlicensed system is displayed as having ’No License Assigned’ and is
identified by a flashing ‘x’ symbol next to the system name in the Systems tab of
Central Configuration Manager.
Systems must be defined within Device Manager before they can be added to
Central Configuration Manager.
5- 1 4
Network Server Suite
To apply a license:
Note:
You must have spare licenses available for the Operating System to which
the unlicensed system belongs in order to assign a new license.
1 Select the Systems tab from the left-hand navigation pane of the Central
Configuration Manager. Unlicensed systems are displayed with ‘No License
Assigned’.
The System Details pane is displayed showing the current configuration,
licensing, message log settings and connection check status for this system.
In the Licensing section of this pane, the License to Use field currently
displays; ‘Unlicensed Systems’.
2 From the ‘License To Use’ field, use the drop-down menu to select the
Operating System license applicable to this system. (Only licenses that can
be applied to this system are displayed in the drop-down). Once selected, the
number of remaining licenses for the Operating System is reduced by 1)
The ‘License To Use’ field changes to reflect the assignation of the license,
with the number of licenses available being reduced by one, and the monitors
are enabled under the system ready for use.
Licensing Network Server Suite
5-15
3 From the menu bar select File | Save Settings. The settings are saved and
the system is now licensed for use within Network Server Suite.
Removing a license:
There may be occasions where you need to remove a license or re-assign a
license from one system to another.
1 From within the Systems tab of Central Configuration Manager, select the
licensed system. The ‘License To Use’ field within the Systems panel
currently shows the Operating System license applicable to this system.
2 From the ‘License To Use’ field, use the drop-down menu to select
Unlicensed Systems. Once selected, the number of remaining licenses for
the Operating System is increased by 1). The system is now displayed as
having ‘No license Assigned’
Note:
5- 1 6
3 From the menu bar select File | Save Settings. The settings are saved and
the license is removed from the system so it can no longer be used within
Network Server Suite. The license can now be re-assigned using the
procedure above.
The unlicensed system continues to be displayed within the Systems tab of
the Central Configuration Manager until it is deleted using File | Delete
System.
Network Server Suite
C
HAPTER
PASSWORDS AND USER NAMES
CHAPTER6
Enterprise Console Default User Name and Password
When the Enterprise Console is first launched the following default user name
and password is applied:
• User Name: Administrator
• Password: Administrator
When a new user is added, a default password (the text used for the user
name) is created automatically. When a new user first launches the Enterprise
Console the current user name must initially be entered as the password. A
message is then displayed advising the password has already expired and a
new password must be entered.
Changing Passwords
Passwords are changed from within Enterprise Console Options. A password
must be changed if it has expired, or a new password can be generated for
security reasons.
To change a password:
1 Launch the Enterprise Console, log in, and select Tools | Options from the
menu bar.
2 Click Password, in the bottom left-hand corner of the Enterprise Console
Options dialog, to open the Change Password dialog.
3 Enter your old password in the top box, then enter a new password and
confirm.
4 Click OK to accept and save the new password.
This is the password you must enter the next time you launch the Enterprise
Console (if you are logging in with the same user name).
Passwords and User Names
6-17
Resetting Passwords
Passwords are reset from the Enterprise Server Options | General | Users
page. Resetting a password is a temporary measure, allowing you to update an
existing user’s password if it has been forgotten.
To reset a password:
1 Launch Enterprise Server Options, and select the General | User option from
the list of options in the left pane.
2 Select an existing user and if necessary set an expiry date. This date is
applied to the password you have to create when you next log on.
3 Click Reset Password. A confirm/cancel message option is displayed.
4 Click OK to confirm the reset password command. The reset password is
now also the current user name. A confirmation message is displayed to
validate the password has been reset against the specified user name.
5 Launch the Enterprise Console and enter your user name and password.
At this stage the password is the same as your current user name (see step 4
above).
6 Enter your current user name as the password. A message is displayed
advising the current password has expired and you are prompted to create a
new one.
7 Click OK to display the Change Password dialog.
8 Enter your user name as the old password and enter a new password of your
choice. The password dialog closes and you now have access to the
Enterprise Console.
Expired Passwords
When a password has expired, a new password must be created. The expiry
period for the new password is specified on the Enterprise Server Options |
General | User page. This is a global setting and is applied to all further
passwords until changed.
If you are prompted to change an expired password:
1 Click OK when prompted to display the Change Password dialog.
2 Enter your current password as the old password.
3 Enter a new password of your choice.
4 Click OK to close the dialog and return to the Enterprise Console.
6- 1 8
Network Server Suite
Disconnection while Logged In
If you are disconnected (without logging out first) and try to log in again, the
system may assume you are already logged in and prevents access.
To rectify this situation:
1 Select your user name in the Enterprise Server Options | General | User
page and click Reset Password.
2 Keep the Enterprise Server Options open or click Cancel to close the
Enterprise Server Options and return to the Enterprise Console.
Users and Administrators
Users are added, edited and deleted from Enterprise Server Options |
General | User page. User log on details (user name and a password) are
required by each user or administrator each time they launch the Enterprise
Console.
Multiple users and administrators can be added, but name/password
combinations must be unique.
User and Administrator Privileges
Privileges can be assigned to each user according to the system access and
control required by that user.
Administrator privileges allow full control and typically, users can be granted a
limited set of privileges, or full privileges specified from the privilege options
available.
Figure 6.1
User and Administrator Privileges
There are six areas of system privilege that can be granted to a user. If the user
is entered as an administrator then access rights to these six areas are granted
automatically.
Close
Gives the user the ability to close alerts
Reply
Gives the user the ability to reply to alerts (where applicable)
Delete
Gives the user the ability to delete alerts
Passwords and User Names
6-19
Comment
Gives the user the ability to add a comment to alerts
Command
Gives the user the ability to use the Command facility of the
Enterprise Console
Purge
Gives the user the ability to purge alerts
Adding a New User
New users are added from Enterprise Server Options | General | User page.
To add a new user:
1 Click Add User.
2 Populate the Add New User dialog with new user details.
Note:
3 Click OK to accept the details and add the new user to the list of users
displayed.
At this stage, the password for the new user is the same as the user name,
but it must be changed when you log on to the Enterprise Console (see
Passwords above for further details).
Editing User Details
Note:
User and administrator details are edited from Enterprise Server Options |
General | User page.
You cannot change a user name from this option. To change a user name,
you must delete the existing user and then add a new user.
To edit user details:
1 Highlight a user from the list displayed on the General | User page and click
Edit User.
2 Edit the required details in the Edit New User dialog.
3 Click OK to accept the changes and return to the General | User page.
6- 2 0
Network Server Suite
Deleting a User
Users are deleted from the Enterprise Server Options | General | User page.
To delete a user:
1 Select and highlight a user from the list on the General | User page.
2 Select Delete User on the General | User page.
A message is displayed asking you to confirm deletion:
3 Click Yes to delete the user details and remove the user details from the list
displayed.
Passwords and User Names
6-21
C
HAPTER
DEVICE MANAGER
CHAPTER7
Overview
The Device Manager is the component of Network Server Suite that is used for:
• Loading devices so that they can be used in other components of Network
Server Suite. This can be done by automatic discovery of devices across
your network or by manually entering devices individually.
• Setting connection, display and time zone characteristics of each device.
• Categorizing devices into Types and Groups.
Note:
• Managing Applications that can be launched directly from the devices when
displayed in the Enterprise Console.
Devices must be loaded or be present in the Device Manager before they are
available for selection in other components of the Network Server Suite.
Once loaded into Device Manager, each individual system must then be
added within Central Configuration Manager before filters and other settings
can be applied. See “Adding a System to Central Configuration Manager” on
page 13-117 for more information.
Select Windows® Start | Halcyon Network Server Suite | Device Manager to
activate a Device Manager session.
The Display
By default, the Device Manager window contains three panes:
• Discovered Devices - default position left pane of the main window.
• Defined Devices - default position right pane - of the main window.
• Messages - default position lower pane - of the main window.
7- 2 2
Network Server Suite
Figure 7.1
Device Manager main dialog
Discovered Devices Panel
This panel shows the details of any devices discovered by using one of the
automatic detection routines. By default, the Device Name and IP Address are
displayed.
Defined Devices Panel
This panel shows the details of any devices which have been manually added to
the Device Manager. By default, the Device Name, Connection and Read
Timeouts are displayed.
Messages Panel
This panel shows the details of any messages sent to, from or between devices
listed in the Device Manager. Date/Time and Message details are shown by
default.
Re-arranging the display
Each pane can be minimized, closed or moved and resized as required.
Information is listed in each pane in table columns, the contents of each column
can be can be arranged in ascending/descending order by clicking any column
title to alter the view. Column positions can also be rearranged by dragging any
column horizontally along the relevant title bar and dropping in a new position.
Columns can be added to or removed from each pane by right-clicking a column
bar and selecting or deselecting the column(s) required from the pop-up menu
displayed.
Device Manager
7-23
Automatic Detection of Devices
Use the Device Discovery feature to automatically detect the presence of
devices across your network. This functionality is only available if an
authorization code that includes SNMP Traps processing has been applied.
The Device Discovery feature is accessed from Device Manager | Devices |
Discover Devices. The Device Discovery dialog is displayed.
Figure 7.2
Poll Type Device Discovery
There are three types of discovery methods that can be used when
automatically detecting devices on your network.
Discovery Criteria
Poll
Select this option to poll (connect to) a single address, range or subnet as
defined in the Poll Type setting).
Poll Type (if Poll selected as the Discovery Type)
7- 2 4
Single Address
Device Manager attempts connection to the entered IP
Address.
Range
Device Manager attempts connection to all IP Addresses
within the entered range.
Network Server Suite
Subnet
Device Manager attempts connection across a sub-network
determined by a user-identified IP Address.
Typically, a subnet may represent all the machines at one
geographic location, in one building or on the same local
area network.
Walk
Use this option to start discovery from a known TCP/IP address for a specified
sequential depth up to a maximum of 9999 addresses.
Starting Address (if Walk selected as the Discovery Type)
Enter the IP Address from which the discovery of sequential IP addresses
commences.
Walk Depth (if Walk selected as the Discovery Type)
Enter the number of connections to devices that are attempted when using
Walk as the automatic detection method.
Broadcast
Use this option to broadcast for devices from a specified TCP/IP address.
Address (if Broadcast selected as the Discovery Type)
Enter the IP Address from which the broadcast is made.
Terminate After (all Discovery Types)
The period (in seconds) after which the discovery session is terminated.
Click Start to begin the Automatic Discovery of devices sing the selected
method. Click Stop to end the session early, otherwise the discovery ceases
when the Terminate After threshold is reached.
Devices that are discovered using any one of the above means are displayed in
the Discovered Devices pane of this window and subsequently in the same
named panel of the main Device Manager window.
Use ‘drag and drop’ or double-click to move devices from the Discovered
Devices panel into the Defined Devices panel from where the details can then
be edited.
Manual Addition of Devices
Devices can also be manually added to the Enterprise network.
Either click the Add Device
icon from the toolbar or select Devices | Add
Devices from the main menu. The Add Device dialog is displayed.
There are three separate areas into which information can be entered:
• General
• Advanced
• SNMP
Device Manager
7-25
Figure 7.3
Manual Addition of Devices
General Settings
Information page
Group
Device Groups are an optional way to segregate groups of say, similar devices,
or all devices belonging to a specific department.
The Device Group (if used) can be specified using a selection from the dropdown menu. Groups are added using the Tools | Manage Groups option. See
“Managing Device Groups” on page 7-33.
Name
The Device name MUST be the same as the actual system name.
Description
Enter an accurate description by which the device can be identified.
Device Type
From the drop-down choice menu, select the device type. The following
selections are available:
• AIX® Server
• Bridge
• Fax
• Hub
• Laptop
7- 2 6
Network Server Suite
• Linux® Server
• Mail Server (assumed to be Windows® unless otherwise defined)
• Modem
• PDA
• Power/System i
• Printer
• Proxy Server
• Router
• Scanner
• Server
• Switch
• UNIX® Server
• Unknown
• Windows® Server
• Windows® Server 2003 Standard
• Workstation
Bespoke devices can be added to this list by using the Tools | Manage Device
Types option from the Device Manager menu bar (see “Managing Device
Types” on page 7-35).
Important notes regarding LINUX® Servers
Port 15000
As part of the Linux® agent installation, port 15000 is automatically opened on
the firewall, using the command:
iptables -I INPUT -p tcp -m tcp --dport 15000 -j ACCEPT
This is done so that the Linux® server can communicate with Network Server
Suite. Ideally, you should modify the entries within ‘iptables’ to restrict access
via port 15000 to internal network addresses only.
HALUSM running as root
For the purpose of monitoring the Linux ®server, HALUSM runs as root.
Compatibility
Halcyon Linux® Server Manager has been successfully installed and tested on
RED HAT Enterprise Linux Server v5, SUSE Linux Enterprise Server 11,
openSUSE v11.2, and CentOS v5.3 only..
Device Manager
7-27
Network Host/Address
Enter the IP address of the device as it is registered in your network.
Display page
Color
Specify the default color of the Device when displayed in the Enterprise
Console.
Location
If required, specify the physical geographical location of the network device.
Time Zone
If required, enter the time differential to take account of the geographical
location of the device. For example, with the host device based in the UK,
devices in Paris, France, would have a time differential of +1.00 to GMT.
The settings for this field are derived from the Windows® time zone defaults, as
found in Windows® Start | Control Panel | Date and Time.
When an alert is received from a device located in a different time zone, the
time is extracted from the incoming alert and an adjustment is made via the
setting in this field on the receiving Enterprise Console device prior to being
displayed.
Note:
Note:
Note:
Note:
The ‘Use Current’ setting for this field automatically sets the time zone to the
local setting derived from the device to which the alert is sent. This setting is
useful for devices such as printers and those that send SNMP Traps.
Ensure that the time settings on the remote device are correct prior to
activating this feature otherwise timing inaccuracies of alert data can occur.
Any changes to the Time Zone settings in this field override any pre-existing
settings on devices running “Server Manager”.
When using Time zone settings on Linux agents, a change to the time zone
is not registered until the agent is restarted manually or if the agent device is
re-booted.
Please see “Log Alerts Using” on page 11-67.
Support page
The fields on this page are used to enter the details of any support information.
None of the fields on this page are mandatory.
Contact Name
If required (or known), enter the name of associated personnel responsible for
this device.
Company
If applicable, enter the name of the associated company/division where the
device is installed.
7- 2 8
Network Server Suite
Associated Application Name
Select an application which is then associated with a device (for example
wireless configuration software). The entry in this field is then used if the
Launch Associated Application from an alert received from this device is
actioned from the Enterprise Console.
Note:
Please see “Launching applications directly from Alerts” on page 9-52.
Test Application
Used to test launch the selected application associated with the device.
Advanced Settings
Timeout page
Connection Timeout
The Device Manager abandons its connection attempt after the time period (in
seconds) specified in this field. The default setting is 120 seconds.
Read Timeout
The entry in this field sets the read timeout limit between the Device Manager
and the remote device. The default setting is 120 seconds.
Connection page
Alternative IP Address
Alternative IP Addresses can be added, via the Add button, in order to account
for devices with multi-IP address capability or those that have further IP
Addresses linked to the main IP Address.
External Interface
Should this device sit behind a firewall, enter an external IP address via which
any connection can be made to ensure that alerts are transmitted to the
Enterprise Console. See Device Groups - “Advanced Tab - Connection” on
page 7-34.
Settings page
Note:
The available fields on this page are dependent on the Device being added.
Power/System i Devices allow you to configure port connection settings.
Device Manager
7-29
Figure 7.4
Power/System i Device Settings
User Name/Password
Enter a user name and password combination used to access this device.
Serial Number
Field only displayed if the Device is a Power/System i.
Enter the serial number of the device.
Connect on Port
Field only displayed if the device is a Power/System i. The field is not applicable
to Power/System i devices running Halcyon Legacy software or Power/System i
devices that are not running Halcyon Software solutions.
The entry in this field specifies the port number on the Power/System i to which
the Enterprise Console connects. This value must match the Port Value in the
*SYSTEM Location of the Power/System i device. This value can be found as
the top entry in Configuration Menu > Work with Remote Locations on the
Power/System i device.
Figure 7.5
7- 3 0
Identifying Port Number on Power/System i Device
Network Server Suite
If the Power/System i device is running multiple environments, you would add a
device to the Device Manager to represent each individual environment as the
port setting would differ for each.
Notes page
Use this page to enter any free-text notes about the device.
SNMP Settings
These settings are used to define any SNMP capabilities of the device.
SNMP page
SNMP Capable
Check to enable the current device as being capable of sending SNMP
messages and enable the remaining fields and SNMP pages.
Object ID
Enter a unique SNMP identifier for this device.
Agent Port
Enter the port identification number to which the device is connected.
Version
Select the version of SNMP being used on the device.
Community
If required, select the identification of any community associated with the
device.
Traps page (only available if the device is enabled as SNMP capable)
Device is a Trap Target
Check to indicate if the current device is a trap target, and therefore can receive
trap messages.
Trap Port
Enter the port number used for the trapping of messages.
Trap Type
Select the type of trap for this device.
Click OK to add the device to the Device Manager.
Note:
See “SNMP Monitoring” for more information.
Device Manager
7-31
Importing and Exporting Device Settings
In addition to the automatic discovery and manual addition of devices within
Device Manager, it is also possible to export existing settings from a separate
installation of Device Manager on another machine in your enterprise and
import them to a new installation. This saves a great deal of time and also
reduces any errors that may arise through manual input of device data on
separate systems.
To export Device Settings:
1 From the Device Manager menu bar, select File | Export Devices. The
Select Export File dialog is displayed.
2 Select the directory path to which the device setting export file is saved. The
default directory is: C:\Program Files\Halcyon\Device Manager\Backup.
3 Enter a file name by which to identify the export file. The default entry for this
field is in the format of: ‘Devices-YYYY-MM-DD-HHMMSS-Ms.dsf.’ It is
recommended that you retain this setting unless your internal practices
require a specific entry format.
4 Retain the setting of ‘.dsf’ in the Save as type field and click Save to create
the named device settings file in the specified directory.
7- 3 2
Network Server Suite
To import Device Settings:
1 From the Device Manager menu bar, select File | Import Devices. You are
prompted to confirm the import action.
2 Click Yes to confirm the import of device settings and open the Select Import
File dialog.
Note:
3 From within the ‘Look In’ field, navigate to the network directory path where
the device settings file (.dsf) is stored. Click on the file that you wish to import
so that it is highlighted and then click Open to start the import process.
During the import process you are warned and prompted for action should
any existing devices on your system about to be overwritten with data from
the import file.
When the import process is complete, a system message is displayed
advising of how many devices were successfully imported. Click OK to close
this message and display the list of imported devices in the Defined Devices
panel of the Device Manager display.
Managing Device Groups
Devices can be segregated into groups of say, similar devices, or all devices
belonging to a specific department. Devices can be displayed by Group in the
Devices panel of the Enterprise Console.
Select Tools | Manage Groups to display the Device Group dialog. Click Add
to display the Add Device Group dialog.
Figure 7.6
Add Device Group
Device Manager
7-33
General Tab - Information
Name
Enter a unique name by which to identify the device group.
Description
Enter text that accurately describes the device group.
Reference
If required, enter a reference, such as Department Account Number or Asset
Number, for the device group.
Advanced Tab - Connection
Route
The route field defines a series of IP addresses that are then used to connect to
all the devices included in this group.
Note:
This can be an external IP address if required.
Use of this function, alongside an External IP Address entered in the
“Connection page” setting of the actual device, allows Enterprise Console alerts
to be passed between firewalls.
Click Add to open the Add Route Entry dialog into which a new IP Address can
be entered. Click OK to add the new connection route to the defined list.
Figure 7.7
Add route entry dialog
Advanced Tab - Notes
Notes
Use this area to enter any free-text notes that you wish to make relating to this
device group.
7- 3 4
Network Server Suite
Managing Device Types
Any devices that you may have in your organization but that are not currently
available from the Device Type list can be added using the Manage Device
Types option.
From the Device Manager menu bar select Tools | Manage Device Types and
click Add to display the Add User-Defined Device Type Dialog.
Figure 7.8
Add User-Defined Device Type
Description
Enter a meaningful description to be of the new device type.
Object ID
If the device is SNMP trap enabled, the unique object identity number should be
entered in this field.
Category
If required, select a pre-defined category with which the device type is then
associated.
Device Manager
7-35
O/S Type
From the drop-down menu, select the type of Operating System that the device
uses. The choices are:
• None
• AIX®
• i5/OS®
• Linux®
• UNIX®
• Windows®
Icon
From the drop-down choice menu, select an icon by which the device type is
identified within Network Server Suite.
Default Associated Application
From the drop-down choice menu, select an application with which the device
type is associated by default. This can be overridden when adding a new
device.
Managing Applications
Applications, such as Remote or Client Access programs can be used to quickly
access devices directly from any alerts that are generated.
Applications associated with device types are defined and managed from the
Manage Applications dialog. This allows you to add applications and edit or
delete existing applications.
There are four pre-defined applications supplied with Network Server Suite:
• Device Web Page
• pcAnywhere
• Remote Desktop Connection
• VNC
7- 3 6
Network Server Suite
Figure 7.9
Adding a new Application
Adding a new Application
1 From the Device Manager menu bar select Tools | Manage Applications.
2 Click Add.
3 Enter a Description for the application.
4 If the application is a web page enable Application is a Web Page.
5 Enter the directory path in which the application executable is stored.
6 Enter any Parameters required to launch the application upon opening
(listed Substitution and Environmental Variables may be used). The Example
field auto-completes based on the entry in this field.
7 Click OK to confirm and add the application.
Device Manager
7-37
Creating a Client Access Application
Creating a client access application is useful for when you need to directly
access an IBM iSeries device directly from within the Enterprise Console.
Note:
The IBM emulator software must be running on the same device as that on
which the Device Manager component of Enterprise Console is installed.
You must also create a separate .WS file for each iSeries device that you
wish to add. It is recommended that you name each of these as the system
name.ws to ensure that you connect to the correct device.
To create a Client Access Application:
1 From the Device Manager menu bar select Tools | Manage Applications
2 Click Add to open the Add Application dialog
3 Enter Client Access ‘System Name’ as the Description
4 In the Executable field, either type the path of where the required emulator
.ws file is stored or use the Browse button to search for and automatically
enter the file path. Note that if you use the Browse option you need to change
the search parameters to look for ‘All Files’ and not just ‘Program’ files.
Note:
5 Click OK to confirm and add the client access application.
See “Launching applications directly from Alerts” on page 9-52 for more
information on how to use the application, once it has been created.
Device Manager Options
Device Manager Options are used to specify logging and SNMP Discovery
settings.
Logging Page
Save to Log File
Check to enable the saving of device information to a log file.
Log File Name
The default setting for this field is DevManager.hlf. This entry can be overwritten
with your own choice, if required. The log file is saved in the directory C:\
Program Files\Halcyon\Device Manager\Logs unless otherwise specified.
7- 3 8
Network Server Suite
Figure 7.10 Device Manager Options
Maximum Log Size
Enter a value that indicates the maximum size, in kilobytes, of the log file. The
default setting is 1024Kb. Note that if both Informational and Diagnostic
massages are saved, increase this value.
Log Informational Messages
Click to log all messages relating to the operation of the Device Manager.
Log Diagnostic Messages
Click to enable the logging of all Device Manager diagnostic messages.
Discovery Page (for SNMP enabled devices)
Host/Address
Enter the Host Name/IP Address of the SNMP Managing device.
Refresh Interval
Select the time period, in seconds, that the SNMP connection is refreshed.
SNMP Community
If required, enter the name of the SNMP Community on which devices may be
operating.
SNMP Port
Enter the Port Number on which SNMP Devices on this network communicate.
Device Manager
7-39
C
HAPTER
ENTERPRISE CONSOLE
CHAPTER8
Overview
Enterprise Console is the Graphical User Interface (GUI) application that
connects to the Enterprise Server to manage received alerts which are
displayed on any machines which have the Enterprise Console application
installed on them.
Any number of users can be connected, although each must have a unique user
name. Individual user privileges can be set to restrict or enable operators to
perform different tasks.
If several users are on duty and one person closes or replies to an alert, their
action is broadcast to all other users.
The Enterprise Console is used to:
• Display alerts (received from devices on your network) so that
administrator(s)/operator(s) responsible for any problems/issues can
investigate and take appropriate action.
• Quickly identify devices in urgent need of attention.
• Send alert details as an email to 3rd party helpdesk applications
• Send alert details as an SMS message
• Launch Associated Applications (if defined) directly from an alert
• View full alert details
• Add comments to alerts and interact between multiple users
Enterprise Server is a service used to receive alerts from a variety of sources
and allows users to manage them centrally via any networked machines which
have the Enterprise Console application installed. Any number of incoming
connections can be handled simultaneously; the only limitation(s) are imposed
by machine hardware limitations (processor speed, memory, etc.)
8- 4 0
Network Server Suite
Logging onto the Enterprise Console
The Enterprise Console is the only component of the Network Server Suite that
currently requires a password for access.
Enter a valid user name and password to log-on to the Enterprise Console and
click OK.
Routing Options
This option allows you to use the integral network manager facility of Network
Server Suite to connect to a server that is situated behind a firewall.
To make use of this facility, click Options on the Log In dialog, to expand the
current view.
Select or enter the IP Address(es) of the server(s) to which you wish to connect.
Enter the IP address of the route by which the connection is made. Click OK.
Once entered, the information is stored so that future logons can use the same
criteria if required.
The Enterprise Console Display
Alert details, device identities, device details, action histories and associated
alert messages are displayed in four panels contained within the main
Enterprise Console window.
Figure 8.1
Enterprise Console main display
Enterprise Console
8-41
Each panel within the display can be repositioned within the window or floated
on the desktop and resized as required.
Modified settings can be saved as named layouts using the Window | Save
Layout As... menu option to save the settings. Multiple layouts can be saved
and reused, or the default (non-editable) layout can be selected at anytime.
User privileges also affect what functions are available from the layout
(privileges are set in the Enterprise Server Options | General | User | AddEdit User dialog). Context menus are available to show/hide the column
options for all panels.
The Four Panels of the Enterprise Console
The four panels of the Enterprise Console are split into:
• Inquiry Alerts
• Info Alerts
• Devices
• Details/Action History/Messages/Command
Inquiry Alerts
In its default format, the Inquiry Alerts panel displays messages that have been
directed to the Inquiry Alerts panel from a filter action setting in Enterprise
Server Options. These are usually alerts that require some form of action to be
taken on the part of the user. Alerts received from monitor filters set from within
the Central Configuration Manager console are automatically sent to this panel.
The name of this panel can be changed if required. See “Alert Panels settings”
on page 11-67 for more information.
Info Alerts
In its default format, the Info Alerts panel displays messages that have been
directed to the Info Alerts panel from a filter action setting in Enterprise Server
Options. These are usually alerts that although still probably require user
intervention are provided as information to the user. The name of this panel can
be changed if required. See “Alert Panels settings” on page 11-67 for more
information.
Devices
The Devices panel shows all the current devices that have been installed using
the Device Manager. By default, the devices are displayed by Status (i.e. those
needing urgent attention are shown at the top of the list), although it is possible
to change the sequence by clicking on any of the other four column headings.
For example, to change the sequence to display by alphabetical device name,
click the Name column heading.
If you have set up device groups, these can be displayed by selecting View |
Display | Device Groups from the menu bar.
8- 4 2
Network Server Suite
Details
This window is used to show the individual details relating to an alert selected
from either the Inquiry or Info Alerts windows. There are four different detail
options available for view:
• Details – Shows full details of the alert including Device, Key, Date and
Time, Source and Error message text. Additionally, any user comments that
have been added to the alert can be displayed from within this option.
• Action History – The Action History shows what has happened to the alert
since it was logged on the Enterprise Console.
• Messages – Shows details of any system messages that may have been
generated as a result of an action being taken.
• Command – Used to send system messages to other users
Changing the display
There are a variety of methods that you can employ to suit your personal
viewing preferences when accessing the Enterprise Console.
Stretch and Shrink
Individual panels of the Enterprise Console can be resized by using the stretch
technique. As a result, other panel(s) on the display shrinks to accommodate
the new size.
To use stretch and shrink:
1 Position the pointer over either the vertical or horizontal dividing bars
between the panel. The pointer changes to a ‘Split-Line’ shape.
2 Hold the left mouse button down and drag the border in the direction that you
wish to resize.
3 Release the button when the desired position is reached.
Drag and Drop
It is possible to reposition each of the panels to a new location within the display
window.
To use drag and drop:
1 Position the pointer over the title bar section of the panel that you wish to
move.
2 Click and hold the left mouse button down and drag the panel to the desired
position.
3 Once satisfied with the new layout, select Window | Save Layout As to save
the layout.
Note:
This takes practice to achieve the desired result. Use Window | Default
Layout from the menu bar to return to the default display setting.
Enterprise Console
8-43
Note:
Views are unique to the user. Therefore it is possible to have multiple
instances of Enterprise Console showing different panel views (containing
the same data) if more than one user is logged on simultaneously.
Note:
Enterprise Console remembers the last panel setting as used by the user and
defaults to that display upon opening.
Maximize and Hide
Maximize and Hide functions allow you to remove or fully display single panels
within the main Enterprise console window
Click
on the panel title bar to maximize the view of any panel (the arrow
orientation changes depending on the panel. Click again to return to the
previous view
Click
on the panel title bar to remove the panel from view. Use Window |
Default Layout from the menu bar to return to the default display setting.
Resizing Fonts
The text displayed within the Enterprise Console Screen can be resized to
customize the view to your own requirements. All displayed text is resized when
either the increase font or decrease font option is selected.
Increasing Font Size
To increase the font size of the Enterprise Console text click
displayed in ALL windows increases in size.
. Text
Decreasing Font Size
To decrease the font size of the Enterprise Console text click
displayed in ALL windows decreases in size.
. Text
Auto-Arrangement of Console Windows
This feature is used when viewing multiple instances of the Enterprise Console
on a single screen. Selecting this option automatically arranges multiple
console windows into the optimized viewing display.
Select Window | Arrange Windows or click the
Figure 8.2
8- 4 4
Arranging Console Windows
Network Server Suite
icon to initialize.
Selecting Columns for View and Ordering
To reduce (or increase) the number of columns displayed in any of the four
panels, right-click on a column heading to display the Column Selection pop-up
menu for the selected panel.
Active columns are indicated by a tick mark. To remove columns from the view,
click on the checkbox next to each column that you wish to remove. The tick
mark disappears to indicate that the column is no longer selected. Adding
columns back into the display is a reverse of this procedure.
From the Column Selection popup select More to display the Select Columns
dialog. From this dialog it is possible to define column ordering and set a default
width size per column.
Column Ordering
You may change the order in which the columns are displayed within any of the
four panels.
To change column order:
1 In the select columns dialog click on the name of the column that you wish
move so that it is highlighted.
2 Use Move Up (unless the column is at the top of the list) and Move Down
(unless the column is at the bottom of the list) to re-position the column in the
list.
3 Click OK to confirm.
Width of selected column (in pixels)
Select a column name from those listed to display the current column width in
this box. Enter a new figure into this box to amend the selected column size.
User Messages
Availability of users across the network is remotely monitored and messages
can be exchanged between all connected users.
The availability status of users can be set individually by each user from the
User |… menu options or the drop-down icon toolbar
. The available options
are:
• I am Available (only displayed when one of the following options active)
• I am Away
• I am on a Break
• I am at Lunch
• I am away from my Desk
• Do not Disturb (messages may be hidden when this option is selected)
Although the status is updated and distributed automatically, this function
requires a manual change to be made by each user to be accurate.
Enterprise Console
8-45
Command panel
In addition to default command options, text commands can be entered in the
Command | Chat edit box in the Details/Action History/Messages/Command
window. This can be displayed by selecting
from the toolbar.
The following commands can be entered (commands are not case-sensitive):
8- 4 6
Command
Notes
/AWAY
without message
/AWAY AT LUNCH
with a message, for example "At Lunch"
/CLS
clears the command screen
/HELP
display list of available commands
/LICENSE
displays licensing information
/MSG
sends messsage
/TIME
returns the Enterprise Server time
/VERSION
returns the Enterprise Console version
/PING
pings a server
/NICK ADMIN
sets the user's nickname
/MSG TEST
MESSAGE
sends a message to all connected users
/MSG TEST
MESSAGE
sends a message to all connected users
/MSGTO
sends a message to a specific user (can use either the
username or nickname)
/WHOIS ADMIN
returns user info for a specified user, can use either the
username or nickname
Network Server Suite
C
HAPTER
ALERTS
CHAPTER9
Overview
Alerts are generated as a result of filters that you have set up to monitor your
network for any issues or problems. When alerts, (that have an action of Send
to Enterprise Console) are received, they are displayed in one of two windows
on the Enterprise Console. These panels are initially labeled Inquiry Alerts and
Info Alerts, although these settings can be changed in Enterprise Server
Options:
• Inquiry Alerts - messages that have been directed to the Inquiry Alerts panel
from a filter action setting in Enterprise Server Options.
• Info Alerts – messages that have been directed to the Info Alerts panel from
a filter action setting in Enterprise Server Options.
Note:
By default, when a new filter is set up using Enterprise Server Options, the
setting displays the alert in the Inquiry Alerts panel of the Enterprise Console.
This setting may be changed by editing the filter in Enterprise Server Options.
Any alerts generated from filter criteria specified via monitors available in the
Central Configuration Manager and/or Templates are automatically displayed
in the Inquiry Alerts panel (or the renamed equivalent).
Alert Status
Alerts can have one of the following statuses:
Open
The alert is open and has one or more actions against currently in force.
Closed
The alert has been closed or a reply sent, but could not be archived to the
archive file. The Delete Error Message in the Alert Details indicates why the
alert could not be archived (for example, the archive filename or directory is
invalid or the archive file is in use). Only closed alerts can be deleted.
Alerts
9-47
Error
The alert is open but one or more actions have failed.
Console
Indicates that an alert has been closed\replied to from the Enterprise Console.
The alert remains visible until the console action has completed. Any pending
actions are cancelled when a user closes or replies to an alert.
Acknowl
The alert has been acknowledged and for iSeries alerts only, all outstanding
actions against the alert have been cancelled.
Selecting Alerts
There are various methods by which alerts can be selected:
Single Alerts
An alert can be selected simply by clicking directly on the message line in either
the Inquiry or Info Alerts panel.
Multiple Alerts
Multiple Alerts can be selected by holding down the CRTL key and left-clicking
on individual alerts. Selected alerts are highlighted.
Groups of Alerts
Groups of consecutive alerts can be selected by holding down the SHIFT key
and left-clicking on the first alert in the group and then left-clicking the last alert
in the group. All alerts in the group are now selected.
All Alerts
To select all alerts in either panel, right-click on an alert within the required
panel and choose Select All nn Alerts from the drop-down menu (where nn is
the name of the chosen Alert panel).
View Alert Details
Full details of individual alerts are displayed in the Details panel of the Alert
Details dialog, opened by double-clicking an alert listed in either of the alert
panels. This is the enlarged version of the Details panel displayed by default in
the bottom right-hand corner of the screen.
Alert information is displayed in tree view within collapsible categories. Rightclick anywhere in the Details panel of this dialog to display a context menu that
provides options to Expand/Collapse All and Print, the current information
displayed.
9- 4 8
Network Server Suite
Four buttons along the bottom of the Alert Details dialog allow you to navigate
through alert details sequentially (forward and backward) and move to the first
or last set of details:
Adding Alert Comments
Comments can be used to add any miscellaneous text to an alert in order to
provide more information to any other Enterprise Console users.
Comments can be added to any selected alert in one of three ways:
• Select the Add Comment icon
from the toolbar.
• Select Alerts | Add Comment from the menu bar.
• Right click on the alert and select Add Comment from the drop-down menu.
Once added, the comment icon is displayed next to the alert to make other
users aware that comment text has been added. Multiple comments can be
added to any alert.
Entered comments can be viewed in the Alert Details dialog (see “View Alert
Details”).
2nd Level Help Text
2nd level help text can be displayed for applicable alerts received from Power/
System i devices. This information can assist you in rectifying the problem that
caused the alert to be generated.
If 2nd level help text is available it is displayed as a panel in the Alert Details
dialog of the relevant Power/System i alert.
Figure 9.1
Example of 2nd Level Help Text
Alerts
9-49
Copying Alerts for use in 3rd Party Applications
Information held within an alert can be copied and exported (as a Paste
command) into a third party application, such as Microsoft® Notepad. There are
three options that can be used for copying alert information.
Copy Detail
This option copies the complete detail of the alert message.
To copy the alert detail:
1 Select the alert(s) required, (multiple alerts can be selected) and right-click.
2 From the drop down menu that appears select Copy Detail. The alert detail is
now copied and ready for pasting into a third party application.
Copy Summary
This option copies just the following items of the alert:
• Date/Time
• Device
• Inquiry
• Product
• Source
• Text
• Type
Copy XML
This option copies the alert detail as in the Copy Detail function but in XML
format. You must be logged in as an administrator to be able to use this
functionality.
Replying to Inquiry Alerts
Inquiry alerts are indicated by the
symbol on the message line.
Inquiry alerts that arrive from iSeries devices must have a reply sent instead of
being closed, (the Close Alert option is unavailable for these types of alert).
This process is used to send a recognized message back to the iSeries.
9- 5 0
Network Server Suite
To reply to an Inquiry alert:
1 Select the alert and either:
• Select the Reply icon
from the toolbar
• Select Alerts | Reply from the menu bar
• Right click on the alert and select Reply from the drop-down menu
The Reply To Alert dialog is displayed.
2 Type the required response.
3 Click OK. The inquiry alert is removed from the Enterprise Console.
Alerts received via forwarding systems
Note:
There may be instances where a direct connection cannot be made between
the IBM i device and the Enterprise Console. In such instances it is possible to
route the data via another IBM i device that does have a direct connection.
A guide on how to configure data forwarding is provided in the relevant
Halcyon software suite user reference. Please refer to this document when
creating data forwarding routines.
From within the Enterprise Console, it is important to be able to identify the
device from which the alert originated and not the device(s) that were used for
the forwarding. In order to do this, the Description column must be enabled for
view in the relevant alert panel of the Enterprise Console to which the alerts are
forwarded. Note that this column can be enabled at anytime to provide
descriptive text of the device but is essential for identifying originating systems
of forwarded alerts.
If not already enabled in the required alert panel, right-click the column heading
bar of the panel and select Description from the pop-up menu.
Figure 9.2
Selecting the Description column
Alerts
9-51
When an alert is received from a device that is not in direct connection with the
Enterprise Console, the description column displays both the originating and
forwarding device(s).
Figure 9.3
Note:
Description field showing data forwarding
Please note that this feature is not the same as the “Forward Alert action”.
Printing Alerts
Individual alert details can be generated in hard copy, directly from the
message, via the Print command. Multiple selections are permitted.
To print an alert:
1 Select the required message and either:
• Select File | Print from the menu bar
• Right click on the alert and select Print from the drop-down menu
The standard Windows® Print dialog is displayed from where the Printer and
layout options can be specified.
Launching applications directly from Alerts
When an alert is received at the Enterprise Console it is possible to launch a
remote desktop session to the device/application directly from the Enterprise
Console, providing it was not sent from the device on which Enterprise Console
is running. Such sessions can take the form of, for example; Remote Desktop,
VNC, PCAnywhere (Client Access when logging on to an iSeries machine).
Figure 9.4
9- 5 2
Launching an application directly from an alert
Network Server Suite
To launch a remote session:
1 Right-click on the alert from either the Inquiry or Info panel
2 Select Launch Associated Application.
In order to use this functionality the device must have an existing application
association relationship created within Device Manager.
Sending Alerts to 3rd Party Helpdesk Applications
Alerts can be sent to 3rd party Helpdesk applications by using either Email or
SMS to transmit the message detail.
Figure 9.5
Sending a Helpdesk email
Alerts
9-53
Sending an alert as a Helpdesk Email
To send an alert as an email:
1 Select the required alert (multiple selections are permitted) and either:
• Select Alerts | Send Alert As | Helpdesk Email from the menu bar
• Right click on the alert and select Send Alert As | Helpdesk Email from
the drop-down menus
The Send Helpdesk Email dialog is displayed.
2 Check the From option to enable an entry in this field enabling the receiving
party to identify the originator of the message. It is also a requirement of
some helpdesk applications that a recognized originating address is
supplied; otherwise the email message can be rejected. The entry in this field
must be in a format acceptable to the third party application.
3 Enter a valid To address (either that of the helpdesk application inbox or an
address pre-defined in the Instant Alert Address Book, opened by clicking
).
4 The Subject detail field is automatically completed from the alert, although
this can be overwritten if desired.
5 The substitution variables form the body of the text. An example of the text as
defined by the substitution variables is shown. The Body Text entry is
automatically created from the alert but can be amended if required, using
the substitution variables listed.
6 Click OK to send the email message to the helpdesk application.
Sending an alert as an SMS
Follow the same routine as that for ‘Sending an alert as a Helpdesk Email’ but
either enter the SMS number in the To field or use an entry from the Instant
Alert address book where SMS is set up as the message delivery default.
Acknowledging Alerts
You can acknowledge that an alert has been received by the Enterprise
Console by selecting Alerts | Acknowledge (or right-click and select
Acknowledge from the pop-up menu) against an individual or group of alerts.
Acknowledging an alert changes the alert status to ACKNOWL.
You can only acknowledge alerts with a status of Open. You cannot
acknowledge a Closed alert.
Note:
9- 5 4
The acknowledging of alerts is optional, and allows users in multiple
environments to take ownership of individual alerts.
When acknowledging alerts received from iSeries devices, all pending
actions set against the filter criteria that generated the alert are cancelled.
For alerts received from all other types of devices, only the status is changed.
Network Server Suite
When you select to Acknowledge an alert, the Acknowledge Alert dialog is
displayed. You may enter comments referring to the reason for the
acknowledgement although this is not mandatory. Click OK to acknowledge the
alert.
Figure 9.6
Acknowledge Alert dialog
Purging Alerts
Note:
Alerts are purged from the Purge dialog displayed by selecting Alerts | Purge
from the main menu. You can then select the kind of alerts to purge relevant to
selected devices and click OK to execute the command. Purged Alerts are
archived and are viewable via the Enterprise Console Archive Viewer.
See also “Purge” in Enterprise Server Options - Advanced Tab - SQL Server
for information on how to quickly clear the SQL database tables.
Figure 9.7
Purge Alerts
Alerts
9-55
Closing Alerts
Alerts remain on the Enterprise Console until they are closed (at which point
they disappear from the live console but can still be viewed using the Enterprise
Console Archive Viewer).
To close an alert:
1 Either:
• Select the Close icon
from the toolbar
• Select Alerts | Close from the menu bar
• Right click on the alert and select Close Comment from the drop-down
menu
The ‘Close Alert?’ dialog is displayed.
If required, and it is considered good housekeeping to do so, add a comment on
the reason for the closure of the alert and click OK. The alert is removed from
the Enterprise Console.
Closing alerts received from IBM i devices
If you are closing an alert that has been generated by a IBM i device, the close
request is sent to the IBM i device and the connection then closed. The status of
the alert changes to CONSOLE and stays in this status until the Power/System i
device connects back with a response.
Deleting Alerts
Note:
The delete alert action allows users with the appropriate authority to remove
alerts from the Enterprise Console panels without the need to add comments or
reply.
See “User and Administrator Privileges” on page 6-19 for more details.
Single or groups of alerts can be deleted in one go by selecting the alert(s) to be
deleted and then using Alerts | Delete. You are then prompted to confirm the
deletion.
No connection is back to the originating system and so does not filter through to
forwarded alerts.
Once deleted, the alert can only be viewed by using the Alert Log available from
within the Central Configuration Manager.
9- 5 6
Network Server Suite
C
HAPTER
ENTERPRISE CONSOLE OPTIONS
CHAPTER10
Overview
Enterprise Console Options provide additional operating and connection
parameters for the Enterprise Console. Enterprise Console Options should not
be confused with “Enterprise Server Options” which are used to set up and
maintain filters, set user access rights and license software components.
Enterprise Console Options are accessed from either the options icon on the
toolbar
or Tools | Options from the menu bar.
Figure 10.1 Enterprise Console Options
Enterprise Console Options
10-57
There are three tabs on the Enterprise Console Options dialog:
• Options
• Display
• Audio
Options tab - General page
The General page of the Options tab is used to specify connectivity parameters.
Enterprise Server settings
TCP Host/Address
Enter the TCP Host/Address details of the Enterprise Server device.
Connection Timeout (Seconds)
The entry in this field sets the time within which the Enterprise Console must be
connected to the Enterprise Server before timing out. The default setting for this
field is 20 seconds.
Read Timeout (Seconds)
The entry in this field sets the read timeout limit between the Enterprise Console
and the Enterprise Server. The default setting is 10 seconds.
Unexpected Disconnection settings
Show Login Dialog Automatically
Check this option to automatically display the Login dialog box should the
Enterprise Console be disconnected from the Enterprise Server unexpectedly.
Show Balloon Hint in System Tray
Check this option to display a balloon hint in the System Tray at the bottom of
your screen if the Enterprise Console unexpectedly disconnects from the
Enterprise Server.
Options tab - Command page
This page is used to set options for the Command panel. The Command panel
is displayed in the Enterprise Console by clicking the Command tab (displayed
as part of the Details/Action History/Messages/Command window.
The following options are available on the (Enterprise Console Options dialog)
Command page:
10- 5 8
Network Server Suite
Maximum Lines In Command Panel
This setting defines the maximum number of lines to be displayed in the
Command panel at any one time. The default setting is 100 lines.
Show Command Panel When New Message Received
Check this option to set the Command panel to pop up automatically whenever
a new message is received.
Hide New Messages When In ‘Do Not Disturb’ Mode
Check this option to specify that any new Command messages arriving at a
user console are hidden while they have an active mode of ‘Do Not Disturb’.
Options tab - Advanced page
The advanced page is used to set the Anti-Idle settings. These prevent
connection dropout during times of non-activity.
Enable Anti-Idle Mode
Opens the Anti-Idle options when selected.
Send Anti-Idle command every xx minutes
The time, in minutes, between which anti-idle commands are issued. The
default setting is 5 minutes.
Anti-Idle Response Timeout
The time, in minutes, after which the Anti-Idle routine becomes dormant due to
connection failure. The default setting is 1 minute.
Display tab - Display page
This page is used to specify the default status for alert highlights, confirmation
settings and miscellaneous (window display) settings.
Select the required check box(s) for required system display settings.
Default selections are checked unless specified.
Highlight settings
Highlight New Alerts In Bold
Check to enable any incoming alerts to the Enterprise Console to be displayed
in bold.
Highlight Devices with Critical Alerts
Check to enable the Flash mode for the device status if the highest priority alert
for that device has an alert type that can flash when displayed in the Enterprise
Console.
Confirmation settings
Display Delete Confirmation Dialog for Closed Alerts
Check to enable the display of a message prompt to confirm or cancel the
deletion of closed alerts.
Enterprise Console Options
10-59
Display Log off Confirmation Dialog
Check to enable the display of a message prompt to confirm or cancel the log
off action.
Miscellaneous settings
Log Diagnostic Messages
Check to enable the display of diagnostic messages in the Message panel. The
default setting is not checked.
Show Message Panel When Error Received
Check to enable the message panel to be displayed as the visible panel in the
Details section when an error message is received.
If Application Minimized Or Not Active When Alert Received
Check an option to determine the action to be taken if the Enterprise Console is
minimized or not active when an alert is received. This can ensure that you do
not miss any important alerts.
• Activate window and bring to foreground
• Flash window and task bar button
• Take no action
Display tab - Default Colors page
This page is used to specify default window color(s) for the alert panels and
specify default alert status colors.
Colors are selected from drop-down combo boxes associated with each option.
When Custom... is selected, the Windows® Color dialog is displayed allowing
you to define a custom color for each option.
Defining custom colors
To define a custom color, click Define Custom Colors to expand the dialog and
manually define a color, or enter a known color number in either the HSL or
RGB text boxes.
The following options are available on the (Enterprise Console Options dialog)
Default Colors page.
Inquiry Alerts (Panel One)
Window Color
The color option selected in this field is used to define the window background
color of the Inquiry Alerts panel (Panel One).
Font Color
The color option selected in this field is used to define the font color of the text in
the Inquiry Alerts panel (Panel One).
10- 6 0
Network Server Suite
Info Alerts (Panel Two)
Window Color
The color option selected in this field is used to define the window background
color of the Info Alerts panel (Panel Two).
Font Color
The color option selected in this field is used to define the font color of the text in
the Info Alerts panel (Panel Two).
Alert Status Colors
These options are used to specify status colors for the following alert types:
• Open Alerts
• Error Alerts
• Console Alerts
• Closed Alerts
Audio
When receiving alerts into the Enterprise Console it is possible to have a sound
played when the alert is displayed. Alternatively it is possible to have the alert
read out as speech when it arrives at the Enterprise Console. To allow the
speech function to work, the Microsoft Speech API (SAPI) version 5.1 runtime
must be installed. This is included in the Enterprise Console installation.
Additionally, in order for the speech or sound to be played, each filter must also
have an action of Play Sound on Alert or Speak on Alert set. This is done in
Enterprise Server Options | Filter | Actions.
Message content is taken from the Enterprise Server Options setting specified
in the Action Detail For... dialog. This can be the actual error message text as
raised by the alert or user-defined bespoke text.
Audio tab – Sounds page
Enable Sound Action
Check to be able to select a sound option.
Play Beep
For machines without a soundcard, use the Play Beep option which has been
designed specifically for this type of device.
Play Sound
Enter the directory path or click
to navigate to your own preferred sound file.
MP3 files can be used with this option.
Repeat Continuously
Check to have the sound played repeatedly until either Mute Sound icon
F12 is pressed.
Enterprise Console Options
or
10-61
Audio tab - Speech page
Speech
Enable Speak Action
Check to be able to select a speech option.
Speaker
From the drop-down choice menu, select the voice variant that you wish to
announce alerts.
Speak First Incoming Alert
This setting governs the action taken when simultaneous alerts arrive at the
Enterprise Console. Check to have just the first of the simultaneous alerts
announced. Leaving this field unchecked results in all alerts being announced.
Speech Settings
Volume
Use the slider bar to control the volume level of the speech.
Speed
Use the slider bar to control the speed at which the speech is spoken. Click
to test the current settings.
Changing Passwords
Enterprise Console passwords are changed in the Change Password dialog,
displayed by selecting Tools | Options from the main menu and clicking
Password on the Enterprise Console Options dialog. Passwords are reset
from the Enterprise Server Options General Tab | Users | Reset Password.
Reloading Devices
If you add or change the configuration of devices you can use the Reload
Devices option direct from the Enterprise Console without having to open
Enterprise Server Options. Once activated, the Devices panel of the Enterprise
Console is updated with the changes made.
To use the Reload Devices option select Tools | Reload Devices option from
the Enterprise Console menu bar.
Whenever the Enterprise Server starts or an Enterprise Console client requests
a reload of devices, the Enterprise Server sends a PING request to all iSeries
devices defined in Device Manager. If the remote iSeries does not have the
Enterprise Server in its list of Remote Locations then it is automatically added.
If a remote iSeries device has not had any communication with the Enterprise
Server and the Remote Location’s status is set to Failed, the status is changed
to Connected. Therefore this action acts as a ‘wake-up’ call for the iSeries
device.
10- 6 2
Network Server Suite
Reloading Address Book
If you add entries to the Instant Alert address book while the Enterprise Console
is open you can use the Reload Address Book option direct from the Enterprise
Console without having to open Instant Alert.
To use the Reload Address Book option select Tools | Reload Address Book
option from the Enterprise Console menu bar.
Enterprise Console Options
10-63
C
HAPTER
ENTERPRISE SERVER OPTIONS
CHAPTER11
Overview
Enterprise Server Options is a standalone application used to specify, edit and
change Enterprise Server settings; for example, message logging, user access
rights, filters, alert, Ping and Connection monitor settings. These settings are
entered via tabs displayed in the navigation bar (left pane) of the main window.
Figure 11.1 Enterprise Server Options
11- 6 4
Network Server Suite
Enterprise Server Options is accessed via Windows® Start | All Programs |
Halcyon Network Server Suite | Enterprise Console | Server Options.
Alternatively, Enterprise Server Options can be accessed from within the
Enterprise Console from Tools | Server Options.
General Settings
Note:
The general settings options are used to determine the type and location of log
file messages, device details and user settings.
All log files are saved with an extension of .hlf.
General tab - General page
Message Logging settings
Log Informational Messages
Check to log all messages relating to the operation of the Enterprise Server.
Log User Commands
Check to log all commands entered by users in the Enterprise Console.
Command Panel.
Log Diagnostic Messages
Check to log all system diagnostic messages.
Log Incoming Alert Data
Check to log all alert messages that have an action of Send Enterprise Console
assigned.
Server Details settings
Show Server Name in Caption
Check to enable the input of a specific server name in the name field.
Name
Type a name that then appears in the Enterprise Console window title bar as
‘Enterprise Console - Server Name’.
General tab - Device page
Device Location settings
Load From Host/Address
Type a host name or TCP/IP address from which devices can be loaded for use
in the Enterprise Console. Note that the device attached to this address must
have the Device Manager component installed. Click Load to confirm the
address and reload devices.
Enterprise Server Options
11-65
Connection Timeout
When the Enterprise Server needs to communicate with a remote device (one
of the devices to which it has sent an alert) it abandons its connection attempt
after the interval specified here.
The Enterprise Server tries to connect to remote systems to close an alert, reply
to an alert, gather system information or load devices.
Read Timeout
The entry in this field sets the read timeout limit between the Enterprise Console
and the remote device. The default setting is 5 seconds.
Legacy IBM Power/System i Support settings
For iSeries connections (only visible in specially licensed versions) it is possible
to state the port on which to listen for iSeries connections and the port on which
outgoing connections to the iSeries are made. This only applies to Power/
System i devices running Halcyon Legacy software.
Note:
Porting requirements for Power/System i devices can be found in the
“Settings page” of the Advanced Tab available when adding a device using
Device Manager.
Listen for Connections on Port
Specify the port number on which incoming iSeries alerts are received. The
default setting is 10000.
Connect to iSeries on Port
Specify the port number on which outgoing connections to iSeries devices are
made. The default setting is 9000.
General tab - Users page
The Users page allows you to add, edit and delete users and reset password
information for users as described in the chapter Users and User Names.
Note:
See the chapter; “Passwords and User Names” on page 6-17 for more
information on the fields and settings on this page.
Alert Settings
Alerts tab - Alerts page
Options on the Alerts page allow you to define alert conditions, specify which
date and time is logged (remote or local), select alert display icons and choose
alert actions at startup.
Alerts settings
Always Close Alerts Locally
Check to enable the ability to close alerts locally even if an error occurred while
trying to close or reply to an alert on the originating remote device.
11- 6 6
Network Server Suite
Broadcast New Alerts Every nn Seconds
This setting lets you to specify the time interval (in seconds) between new alerts
being broadcast, acting as a time delay between alerts being generated and
forwarded.
Log Alerts Using
This setting lets you to choose whether alerts are logged using the local date
and time at which the Enterprise Console received the alert or the remote date
and time of the device from which the alert was sent.
Note:
This setting must be set to Remote Date and Time if the Time Zone setting of
the Device is active, otherwise all alerts received from the device are
displayed with the Local Date and Time setting from this field.
See “Time Zone” on page 7-28 for more information regarding this setting.
Alert Panels settings
These options allow you to select the icons displayed in the alert panels one
and two of the Enterprise Console and to set the associated panel captions.
Panel One
Select the icon and caption for panel one, (by default, the top panel displayed in
the Enterprise Console and to where all alerts generated by monitors within the
Central Configuration Manager are displayed). The default settings are a red
flag icon and a caption of Inquiry Alerts.
Panel Two
Select the icon and caption for panel one, (by default, the middle panel
displayed in the Enterprise Console and to where all alerts generated by filters
created within Enterprise Server Options are displayed). The default settings
are a yellow flag icon and a caption of Info Alerts.
Alerts Tab - Archive page
Options on the Archive page allow you to define archive settings for closed/
replied or purged alerts.
Archive Settings
Save Alerts To Archive File
Check to enable the saving of alerts to archive files.
Alerts to Archive
Select the type of alerts that you wish to archive:
• Inquiry: Archive Inquiry Alerts only
• Info: Archive Info Alerts only
• Both: Archive both Inquiry and Info Alerts
Enterprise Server Options
11-67
Create Archive Files
Select the frequency (Daily, Weekly or Monthly) with which Archive files are
created. Files are created on the first day of each choice.
Archive Directory
Specify the file path and directory name used to contain archived files.
Alternatively, click
to browse to the required path and directory. The
default setting for this field is C:\Program Files\Halcyon\Enterprise Console\
Archive.
Note:
If no path is specified in this field, the archive file is saved to whichever
directory the executable file: eso.exe is held.
File Name
Specify the archive file name. This can be entered manually, automatically
(using archive and or environment variables listed on this dialog) or a using a
combination of both. An example of the current archive file naming convention
is displayed in the Example field.
Note:
Note:
When using substitution variables throughout Network Server Suite, any
entries that are made correctly are highlighted in green and those that will
result in an error are highlighted in red.
It is recommended to include a day substitution variable when archive files
are generated daily or weekly and a month substitution variable when archive
files are generated monthly. All archive files have a file extension of .eca.
If a file or directory name includes invalid characters (preventing the file or
directory from being created) an Archive Error is recorded. This is displayed in
the Enterprise Console | Alert Details page. This information is only available
for closed alerts.
Alerts tab - Alert Types page
Alert Type settings are used in the Enterprise Console Devices panel to indicate
device status.
Device status (color/description/icon/flashing) is always set to the alert type that
has the highest priority of alerts raised for that device. For example, a device
that has ten alerts with a low status, five at medium status, two at high status
and one at critical status is shown as being in Critical status in the devices panel
of the Enterprise Console, as this is the highest priority.
The re-prioritizing of alert types can be achieved by selecting an alert type and
using Move Up and Move Down to re-position it in the priority list.
11- 6 8
Network Server Suite
Figure 11.2 Alert Types
Editing Alert Types
Note:
To edit an alert type:
It is not possible to change either the Alert Type name or Alert Type icon.
1 Select the alert type from those listed so that it is highlighted.
2 Click Edit Type. The Edit Alert Type [alert type name] dialog is displayed.
3 Change the Alert Type Status Color and/or overtype the existing Alert Type
Status Text.
4 Check Flash to have the Alert Type flash on and off repeatedly in the
Enterprise Console display.
5 Click OK to confirm and save.
Alerts tab - Source Types page
Source types indicate from which element of your network enterprise that the
alert was sent. Options on the Source Types page allow you add, edit and
delete source types. These are displayed in the Source Types table.
Enterprise Server Options
11-69
Figure 11.3 Source Types
Adding a new Source Type
To add a new source type:
1 Click Add Source Type. The Add New Source Type dialog is displayed.
2 Type the Name of the new Source Type.
11- 7 0
Network Server Suite
3 Type a Description that accurately reflects the new Source Type.
4 From the drop-down menu list select a color by which the Source Type is
displayed in the Enterprise Console.
5 Click OK to confirm and save the new Source Type.
Editing Source Types
Editing Source Types is a similar process to that use when adding Source
Types.
Deleting Source Types
User Defined Source Types (indicated by a user icon) are deleted by selecting a
Source Type from the list and clicking Delete Source Type.
System default Source Types are specific to Halcyon applications and cannot
be deleted.
Filters
Note:
Enterprise Server Options filters allow you to monitor for message or events
across your network enterprise and allow you to specify what action to take
should any message or event occur.
Filters are also available from within specific system monitors supplied with
Network Server Suite. These monitors are accessed from within the Central
Configuration Monitor. See “Working with Monitors” on page 17-155 for more
information.
Each Filter is split into three separate areas:
• Filter definition
• Criteria definition
• Action definition
Options on the Filter page allow you to define (add, edit, delete and hold/
release) filters, selection criteria and actions for the logs you wish to monitor.
Note:
Details of filter settings are available to view in the alert details panel of the
Enterprise Console of any alert generated by the respective filter.
See “View Alert Details” on page 9-48 for more information.
Figure 11.4 Filter Summary
Enterprise Server Options
11-71
Summary details of currently defined filters and filter sequence numbers are
displayed in a four-column table.
Seq
The sequence number of the filter. This number defines
the order in which filters are examined when a new alert
is received
Description
The user-defined description of the filter
Log
Messages
This column indicates which filter messages are logged
by displaying Yes. When filters are not logged the cell is
left empty
Held
This column indicates which filters are Held by
displaying Yes against the corresponding filter(s).When
filters are not held (released) the corresponding cell is
left empty.
Column order can be rearranged by click-dragging, and information in each
column can be sorted (ascending/descending) by clicking on a column title.
Holding/Releasing Filters
The Hold Filter/Release Filter button allows you to Hold/Release filter(s)
selected in the Filters table (above).
Held filters are not checked against any new alerts found by the system and
remain held until released (even if the application is restarted).
Copying Filters
Copying a filter is a quick way of creating a new filter with many required
attributes already in place, allowing you to make one or two adjustments to then
create a unique filter.
To copy a filter:
1 Select the filter to be copied with a single click so that it is highlighted.
2 Right-click on the filter and select Copy Filter from the pop-up menu. The
Add New Filter dialog is displayed.
3 Click OK to produce an exact copy of the existing filter (labelled as 'Copy
of...' in the Filters section of the Filter page)
Adding/Editing Filters
Adding or Editing Filters provides access to a new series of dialogs and options
available when undertaking either of these actions. These are the same
regardless of whether you are adding or editing a filter.
11- 7 2
Network Server Suite
Figure 11.5 Adding a new filter
When you select the Add option, by either clicking Add or right-clicking in the
Filter area and selecting Add Filter, the first dialog displayed is the Add New
Filter dialog. (This is replaced by the Edit Filter dialog when editing a filter).
Filter tab – Filter page
These settings are used to determine sequence, action processing and activity
of the filter.
Filter settings
Sequence
The setting in this field defines the order in which filters are examined. Enter a
unique sequence number to specify the sequence position of the filter. Identical
sequence numbers are automatically prevented from entry.
Log Filter Messages
Check this option if you suspect that the filter is not performing as expected. By
selecting this option, diagnostic messages are written to the Message Log File
(see Message Log Options on the General Tab. Note that the Save to Log File
and Log Diagnostic Messages options must both be selected).
Note:
All log files are saved with an extension of .hlf.
Description
Type a descriptive text for the new filter. This could be a summary of the filter’s
intended use, for example; Warnings Received – Weekends Only.
Enterprise Server Options
11-73
Action settings
Action if Alert Received
If this option is selected, action(s) is (are) taken if the alert is received within the
Filter Active time range specified below.
Action if Alert Not Received
If this option is selected, action(s) is (are) taken if the alert is not received within
the Filter Active time range specified. This option is useful for time critical jobs.
Error Text
A user-defined message that is only activated when Action If Alert Not Received
is enabled.
Filter Active settings
Mon-Sun
Allows you to select/deselect on which day(s) the filter is active. The default
setting is active every day.
From – To
Allows you to specify a time range between which the monitor should scan for
events matching this filter sequence. Hours can span over midnight, for
example, 22.00 – 03.00 hours.
Filter tab – Default Display page
These settings configure the default panel, alert type, background and font
colors for alerts that have been processed against this filter for display purposes
in the Enterprise Console.
Alert Display settings
Display in Panel
Select in which of the two alert panels, any alerts raised by this filter appear.
Override Alert Type
Check to enable the display of an alternative alert type when an alert is
triggered by the filter.
Once enabled, select an alternative alert type from the drop-down choice menu.
Background Color settings
This section allows you to determine the background color of any alert
messages raised by this filter. Only one option is allowed.
Note:
11- 7 4
Use Custom... to specify a color that is not available in the background color
list.
Network Server Suite
Default Background Color
This setting keeps the default background color of the alert as defined in
Enterprise Console Options | Display | Default Colors | Alert Status option.
Device Background Color
This setting keeps the default background color of the device as defined in
Device Manager | Add Device | Display | Color option.
Selected Color
From the drop-down choice menu, select your own color choice as the
background of any alert messages raised by this filter.
Flash Background Color
This field is only enabled when either the Device Background Color or Select
Color fields is selected. Check this field to set the background colour of the alert
to flash when displayed in the Enterprise Console.
Font Color settings
This section allows you to determine the font color of any alert messages raised
by this filter. Only one option is allowed.
Note:
Use Custom... to specify a color that is not available in the background color
list.
Default Font Color
This setting retains the default font color as specified in Enterprise Console
Options | Default Colors option.
Selected Font Color
This setting allows you to set your own color choice as the as the font color
used in any alert messages raised by this filter.
Filters tab – Alert Message page
The Alert Message page is used to provide alternative text details for alerts,
allowing you to provide greater clarity and meaning to the alert when received.
Note:
The actual alert information remains the same so that any matching filter
information is captured prior to the text being changed.
Alert Message settings
Message
Enter free text and/or use the Alert, Device and Details variables (as displayed)
to generate alternative text once matching filter criteria has been proven.
An example of the current alert message text convention is displayed in the
Example field.
Within Network Server Suite, substitution variables are listed as hyperlinks.
Click on the blue text of a substitution variable to select and insert in the
Message or Alert Text Box at the current cursor position.
Enterprise Server Options
11-75
Note:
When using substitution variables throughout Network Server Suite, any
entries that are made correctly are highlighted in green and those that will
result in an error are highlighted in red.
Using Pipes with Alert Text
Alert text can be reformatted by using pipes to change the number of decimal
places reported, remove white space and so on.
Note:
For example, to change the text of an alert reporting a numerical value of
1784.238175 so that it only reports two decimal places use the parameter
&N|p2|; resulting in the alert text changing to 1784.24.
For a full list of available parameters see “Substitution Variable Parameters”.
Using Substitution Variables with Alert Detail information
For alerts that generate detail information (such as SNMP Traps), use the
&DetailsName variable to replace any entry in the left hand column of the
details section of the Alert Detail (as viewed by double-clicking the alert within
Enterprise Console) with its corresponding entry in the right hand column.
This feature is particularly useful when used for SNMP trap alerts as the
Network Server Suite has no automatic way of recognizing which object in the
trap payload actually represents the error message.
For example, in the SNMP Trap below:
11- 7 6
Network Server Suite
The trap payload is shown in the details section headed PDU. The payload
contains a list of objects (left-hand side) and a corresponding value (right-hand
side).
Any one of these PDU values can be used in the alert text by using the object
name as a substitution variable. For the purpose of this example, the PDU value
‘halEsAlertText’ is used:
When the trap is received, Network Server Suite scans the payload looking for
an object with the same name as the variable. If found, it inserts the
corresponding value into the alert text (in this case; ‘Test Alert 1’).
Note:
If this option is used with common or frequently occurring message text, be
sure to specify other criteria to ensure that the alert message generated is
correct for the actual alert received.
Using Substitution Variables with SNMP OID information
In the previous example, a matching SNMP MIB (Management Information
Base) file was used to map SNMP OIDs to object names. Without this data, the
incoming trap would have been displayed as a series of unique numbers such
as: OID 1.3.6.1.4.1.14867.1.1.2.2.1.
If there is no MIB available for the SNMP trap that you are receiving, you can
still use substitution variables to override the alert text, simply by specifying the
unique OID number as the variable name.
Note:
If you need to specify any variable that contains a space, such as OID
information, ensure that the variable text is enclosed in quotation marks.
Enterprise Server Options
11-77
Note:
To decide on which information you should capture in order to get the most
meaningful results in the alert text, setup a test filter first and see what is
generated. From this information you can then determine the details that you
want to capture and set the substitution variables accordingly.
For more information on using Substitution Variables within Network Server
Suite, see “Working with Substitution Variables” on page 15-146.
Filters tab – Advanced page
Advanced settings allow you to specify the method of counting alerts from this
filter and the processing settings applied.
Filter Count Method settings
Alert Count Method
This setting allows you to specify the method by which alerts raised by this filter
are counted.
• Filter
The standard filter counter is incremented each time an alert is
processed against this filter regardless of the alert’s source or
text.
• Source
A distinct source counter is incremented each time an alert is
processed against this filter depending on the alert’s source.
• Text
A distinct text counter is incremented depending on the alert’s
message text.
Alert Count Examples
Assume the following actions have been defined:
Seq
Action
Perform Action For
Action Type
10
Action 1
1 Alert
Change Display
Settings
20
Action 2
1 Alert
Send Email
30
Action 3
1 Alert
Send SNMP Trap
Assume the following alerts have been received:
11- 7 8
Time
Alert Message Text
Alert Source
10:00
Test Alert 1
Server Manager
10:05
Test Alert 2
Message Monitor
10:10
Test Alert 2
Message Monitor
Network Server Suite
If the Alert Count Method is Filter then:
• Action 1 is performed against the alert ’10:00 Test Alert 1’ (Filter Counter=1)
• Action 2 is performed against the alert ’10:05 Test Alert 2’ (Filter Counter=2)
• Action 3 is performed against the alert ’10:10 Test Alert 1’ (Filter Counter=3)
If the Alert Count Method is Source then:
• Action 1 is performed against the alert ’10:00 Test Alert 1’ (Server Manager
Counter=1)
• Action 1 is performed against the alert ’10:05 Test Alert 2’ (Message Monitor
Counter=1)
• Action 2 is performed against the alert ’10:10 Test Alert 1’ (Message Monitor
Counter=2)
If the Alert Count Method is Text then:
• Action 1 is performed against the alert ’10:00 Test Alert 1’ (Test Alert 1
Counter=1)
• Action 1 is performed against the alert ’10:05 Test Alert 2’ (Test Alert 2
Counter=1)
• Action 2 is performed against the alert ’10:10 Test Alert 1’ (Test Alert 1
Counter=2)
Filter Processing Settings
This option suspends the filter according to the options defined below. It is good
practice to use these options to prevent multiple alerts of the same message
being delivered:
Automatically Suspend Filter
Check to enable the following filter suspension options.
Until Triggered X Times
Specify how many times the filter is triggered before it is activated. The count
can also be within a time frame.
Within x Minutes /Hours/Days
Check to enable that a time frame is used to determine the filter trigger count
and specify a time limit that is applied to the Until Triggered x Times option.
For x Minutes/Hours/Days When Triggered x Times
Defines how many minutes/hours/days for which the filter is suspended after it
has been triggered a (user) specified number of times.
Adding Filter Criteria
Options on the (Add New Filter/Edit Filter dialog) Criteria Page allow you to
define (add, edit, delete) filter selection criteria. These are the qualifications that
the filter must meet if an alert is to be raised.
Enterprise Server Options
11-79
Note:
Details of filter criteria are displayed in a five-column table (Select/Omit, Alert
Kind/Alert Type/Source/Text). Table column order can be rearranged by clickdragging columns to the required position and information in each column can
be sorted (ascending/descending) by clicking on a column title.
No sequence number is required as each entry is checked in turn until a
match is found. Any number of selects or omits can be entered in each filter.
Criteria are added in the Add New Criteria dialog and edited in the Edit Criteria
dialog. These dialogs are displayed by clicking Add Criteria or Edit Criteria (edit
is enabled for any selected item(s) displayed in the table). Options on both
dialogs are identical.
Click Add Criteria to create a new selection criterion for the filter.
Criteria tab - Criteria page
Note:
These options also apply to the Edit Criteria dialog.
Criteria Details settings
Choose whether to select or omit this filter from action processing.
Criteria Type
• Select Check this option to select this filter for action processing.
• Omit
Check this option to omit (only) this filter from action processing.
Events matching similar selection criteria in other filters may be
selected for processing.
Alert Kind
Choose the alert kind option for this filter.
• Inquiry
• Non Inquiry
• Both
Alert Type
Define the alert type level for this filter based on selected conditional
parameters (equals, less than, greater than, etc.). Priority is taken from the Alert
Type table on the - “Alerts tab - Alert Types page”.
11- 8 0
Network Server Suite
Examples: (assuming default alert type priority has been kept):
Parameter
Alert Type
Result
=
Any Type
All Alert Types are selected
>
Error
All alert types with a higher
priority of error are selected
=
Critical
Only critical alerts are selected
Source Type
Define the source type based on conditional parameters (equals, not equal to).
Examples:
Parameter
Source Type
Result
=
Any Type
All Source Types are selected
<>
Ping Monitor
All Source Types except Ping
Monitor are selected
=
Ping Monitor
Only the Ping Monitor Source
Type is selected
Alert Text
Enter the alert text based on conditional parameters (equals, less than, greater
than, etc.). Wildcard characters can be used when defining the ‘Alert Text’. This
option is selected via the drop-down list.
Search Text From Position ... For ... Characters
Allows you to fine tune your search for specific alert text by specifying a starting
position from which to search and for a specified number of characters.
Alert Details settings
The Alert Details area is used to set textual information for incoming alerts as
shown in the example below:
Enterprise Server Options
11-81
Details Text
Define the details text. This can be generic or free text but can use specific
textual values that vary depending on the type of alert filter that is being defined.
Wildcard characters can be used when defining this text.
Note:
See the following for more information;
Setting Alert Detail Criteria for iSeries Alerts (see below)
“Setting Alert Detail Criteria for Server Manager Alerts”
“Setting Alert Detail Criteria for SNMP Trap Alerts”
“Setting Alert Detail Criteria for Syslog Messages”
Details Value
Define the details value based on conditional parameters (equals, less than,
greater than, etc.) when used in combination with entry in the Details Text field.
Wildcard characters can be used when defining the details value.
Wildcard Characters settings
The wildcard characters area is used to define characters which are then used
as substitutes for search spans or single characters.
Use ... As A Substitute For Zero or more Characters
Enter the character you wish to use as a substitute for this search span.
Use ... As A Substitute For A Single Character
Enter the character you wish to use as a substitute for a single character.
Setting Alert Detail Criteria for iSeries Alerts
When setting alert detail criteria for alerts originating from IBM iSeries devices,
specific string and integer values can be set.
String Values
The following string values are valid when entering Details Text for alerts
originating from IBM iSeries devices:
• Message ID
• Message Queue
• Message File
• Program
• System
• User
• Number
With string values, only operators ‘=’ and ‘<>’ are used. Other operators can be
used, but note that unexpected results may be generated.
11- 8 2
Network Server Suite
Textual Details Value entries should match the entry in the Details Text field
together with the selected operator. For example, to specify alert detail criteria
for a specific message ID, you may enter something similar to:
Details Text:
Message ID
Details Value:
= CPF9898
An alert is generated for any IBM iSeries Message ID of CPF9898, that also
passes other specified criteria.
Integer Values
The following integer values are valid when entering Details Text for alerts
originating from IBM iSeries devices:
• Severity
• Filter Sequence
• Selection Sequence
All operators can be applied to integer values. An example of specifying alert
detail criteria, with an integer value, for an IBM iSeries alert may be similar to:
Details Text:
Severity
Details Value:
>= 80
An alert is generated for any IBM iSeries message with a severity of greater
than or equal to 80, that also passes other specified criteria.
Setting Alert Detail Criteria for Server Manager Alerts
When setting alert detail criteria for alerts originating from the Server Manager,
specific string values can be set.
Enterprise Server Options
11-83
String Values
The following values are valid when entering Details Text for Server Manager
alerts. The operator value is usually set to equals ‘=’.
Details Text
Valid Details Value
Event Type
Error, Audit Success, Information, Warning
Source
Halcyon SNMP Manager
Category
No specific value required
Event ID
Any valid Event ID number
User
No specific value required
Message
Any valid message as displayed in the Windows Event
Log. The use of wildcards is recommended
Examples of specifying alert detail criteria for Server Manager alerts may be
similar to:
Details Text:
Event Type
Details Value:
= Error
Details Text:
Event ID
Details Value:
= 125
Details Text:
Message
Details Value:
= *Service: esInterface failed: NetMan*
In the above example, an alert is generated for any Server Manager Event Type
with a value of error, that also passes other specified criteria.
Setting Alert Detail Criteria for SNMP Trap Alerts
Alert detail criteria for SNMP trap alerts can be specified in one of two ways,
dependent on whether the incoming trap has been assigned with a valid MIB
definition, instead of the basic OID value. Operator values are usually set to
equals ‘=’.
11- 8 4
Network Server Suite
Therefore, the alert detail criteria for SNMP Trap alerts can be specified in a
similar way as follows:
With a MIB definition:
Details Text:
halEsAlertDeviceName
Details Value:
= MainServer
With an OID definition:
Details Text:
OID 1.3.6.1.4.1.14867.1.1.2.2.3.0
Details Value:
= MainServer
In the above example, an alert is generated for SNMP Trap OID
1.3.6.1.4.1.14867.1.1.2.2.3.0 with a value of MainServer, that also passes other
specified criteria.
Each trap entry has an associated type, such as ASN1_OCTSTR or ASN1_INT.
Types ASN1_INT, ASN1_COUNTER, ASN_GAUGE and ASN1_TIMETICKS
are converted to integer values and all operators can therefore apply.
Setting Alert Detail Criteria for Syslog Messages
When setting alert detail criteria for alerts originating from Syslog messages,
specific string values can be set.
String Values
The following values are valid when entering Details Text for Syslog message
alerts. The operator value is usually set to equals ‘=’.
Details Text
Valid Details Value
Facility
*user*
Severity
*error*
Raw Text
*This is a test message
(Raw Text is the actual message that is received prior to
formatting)
Enterprise Server Options
11-85
Examples of specifying alert detail criteria for Syslog messages may be similar
to:
Note:
Details Text:
Facility
Details Value:
= *user*
Details Text:
Severity
Details Value:
= *error*
In the above example, an alert is generated for any Syslog Message Severity
message with a value of *error*, that also passes other specified criteria.
See “Syslog Message Facilities” on page 11-99 for more information
See “Syslog Message Severities” on page 11-100 for more information
Details Text
Define the details text. Wildcard characters can be used when defining this text.
Details Value
Define the details value based on conditional parameters (equals, less than,
greater than, etc.). Wildcard characters can be used when defining the details
value.
Wildcard Characters
The wildcard characters area can be used to define characters to be used as
substitutes for search spans or single characters.
Use ... As A Substitute For Zero or more Characters
Enter the character you wish to use as a substitute for this search span.
Use ... As A Substitute For A Single Character
Enter the character you wish to use as a substitute for a single character.
Criteria tab - Device Selection page
The Device Selection page determines the devices from which you can receive
alerts for the required criteria. Devices must have previously been loaded using
the Device Manager in order for them to be available for selection in this screen.
11- 8 6
Network Server Suite
Information is listed in four columns:
• Group
• Device
• Name
• Device Address
Column order can be rearranged by click-dragging and information in each
column can be sorted (ascending/descending) by clicking on each column title.
To load a device into the Selected Devices section of this page, simply click on
the required device in the Available Devices section and click Add Device to
move it into the Selected Devices section.
The Clear All/Clear Selection buttons are used to clear all or selected devices
from the Selected Devices table.
Devices shown in the Available Devices are loaded from the Device Manager
as defined on the main options General | Device | Device Location page.
This section allows you to locate and specify available devices on the network
by category. Each category allows selection of items from a drop-down list, (the
contents of the Device Type and Device categories reflect available devices on
your network).
Figure 11.6 Available Devices
The categories comprise:
• Device Group: Device groups are collections of similar devices, such as all
those that belong to a specific department. Device groups are set up and
maintained in Device Manager.
Enterprise Server Options
11-87
• Category: Devices, such as servers that can be divided into specific types.
Items listed here are by default. No other items can be added to this list.
• Device Type: Device types, such as proxy servers are listed on this drop
down comprise a mix of default items and any other items identified on your
network, which are added to this list automatically.
Hide Selected Devices
This checkbox allows you to view only those devices not already listed in the
Selected Devices table (above). This avoids duplicating device information in
both tables.
The View Details button is used to open the View Device dialog, allowing you
to view the attributes of a selected device. Options for this dialog are detailed in
the View Device Dialog topics.
The Deselect All/Select All buttons are used to deselect or select all devices
listed in the Available Devices table.
Click OK to apply the Criteria.
Actions Tab – Actions page
The options on the (Add New Filter | Edit Filter dialog) Actions Page allow you
to define (add, edit and delete) actions. Any number of actions can be defined
for each filter and these actions are processed in turn if the filter selection
criteria match the alert.
Action details are displayed in a five-column table (Seq, Delay, Action, # Alerts,
Parameters). Table column order can be rearranged by click-dragging and
information in each column can be sorted (ascending/descending) by clicking
on a column title.
Actions are added and edited in the Action Detail For... dialog. This dialog is
displayed by clicking Add Action or Edit Action (edit is enabled for any selected
item(s) displayed in the table).
The full dialog title includes the name of the Action Type. This is selected from
the Action Type drop-down choice menu (see below).
Escalating the Priority of Pending Alerts
Actions are listed in the Actions For Filter table by priority of sequence number
and within each action sequence group, the time delay specified.
Actions within each sequence group can be escalated individually, by selecting
an action and clicking the up/down arrows (see below) to reposition the action in
the table:
Actions can only be prioritized individually; it is not possible to prioritize multiple
actions simultaneously.
It is important to be aware that escalating or de-escalating the priority of any
action also affects subsequent relationships between actions (within the same
sequence).
11- 8 8
Network Server Suite
Add Action For...[Action]
Click Add Action to open the Add Action For ...{Action] dialog.
Figure 11.7 Add Action For.. dialog (showing options for Send Console action)
Action Details settings
Action Sequence
Either directly type or use the choice buttons to enter the action sequence
number required. This sequence number does not have to be unique. If there
are two or more sequence numbers with the same value, all actions are
executed for the particular occurrence of that alert.
For example, if an alert is received which requires a command to execute and a
log to be written every time, both actions would be assigned the same sequence
number so both actions are executed for the same alert.
Action Type
Action types are selected from the Action Type drop-down choice menu. When
an action type is selected, an additional tab is added to the left-hand navigation
pane of the Add Action For...[Action] dialog (except for Log Only and Play
Sound at Console actions). These additional options allow you to enter
information related to the Action Type selected.
Enterprise Server Options
11-89
The following action types can be selected:
Change Display Settings action
This action changes the display settings for any alerts received at the Enterprise
Console.
Additional option:
• Display - Options on this page are detailed in the “Filter tab – Default Display
page”.
Execute Command action
This action executes a specified command when an alert is received.
Additional option:
• Command - Use substitution variables to create the command. An example
of content type is displayed in the read-only ‘Example’ field as you enter each
variable. The exact content displayed is defined by your system, network
configuration and local conditions such as date and time.
Forward Alert action
This action forwards all alerts raised by the filter to another instance of
Enterprise Server. Forwarded alerts are displayed with an additional icon and
extended information in the Alert details panel in the Enterprise Console.
Additional option:
• Forward - Options on this page allow you to define the server to which the
alerts are forwarded. Routing information is defined per device or device
group as setup in Device Manager. If an alert is forwarded from a device that
does not currently exist in the receiving server device list, a temporary device
is added until the alert is closed. If an alert is received from an iSeries device
and then forwarded onto another instance of Enterprise Console, the
receiving Console must have the routing information of the forwarding device
in order that a reply can be sent back to the originating iSeries device.
Hold Alert Filter action
This action holds the specified filter and prevents it from being selected for
further action.
Additional option:
• Filter - Options on this page allow you to hold a chosen filter.
Log Only (No Action)
No action is taken. The alert is simply logged as received.
Additional option:
• None
11- 9 0
Network Server Suite
Play Sound at Console action
This action results in a sound being played whenever an alert is received at the
Enterprise Console.
Additional option:
• None
Raise Helpdesk Ticket action
This action sends an Instant Alert message to nominated recipients whenever
an alert is received.
Additional option:
• Helpdesk - Opens the Helpdesk page that allows you to generate an email
message based upon a mixture of text and substitution variables. This can
then be used to raise a ticket on a third party helpdesk application.
Release Alert Filter action
This action releases the specified filter, previously held by the Hold Alert filter
action.
Additional option:
• Filter - Options on this page allow you to release a previously held filter.
Reset Alert Count action
This action resets the alert count of the selected filter.
Additional option:
• Filter - Options on this page allow you to select an existing filter and reset the
alert count.
Send Console action
This action closes or replies to an alert on the origination remote console.
Additional option:
• Console - Options on this page allow you to close the alert or reply with a
user-defined message.
Speak at Console action
This action plays a spoken message whenever an alert is received.
Additional option:
• Speech - Options on this page allow you to include the device name, speak
alert only or speak user-defined text.
Enterprise Server Options
11-91
Send SNMP Trap action
This action sends an SNMP Trap to the Enterprise Console.
Additional option:
• Send SNMP Trap - Options on this page allow you to select a device and
view device attributes. If a device is not currently available, a new one can be
added from the Device Manager. Device details can be reviewed in the View
Device dialog, displayed by clicking Details in the Select Device dialog. If an
application is associated with the device, the application can be launched by
double-clicking its name in the Support pane of this dialog.
Send Network Message action
This action sends a message to other users on the network when an alert is
received. The message text can contain substitution variables.
Additional option:
• Message - This page has two sections, Recipients and Message.
The Recipients page allows you to enter the network users to which the
message is sent (you must have their user names available).
The Message page allows you to input the message text and/or enter
substitution variables listed in the table below the Text box. An example of
variables content is displayed in the read-only Example field as each variable
is entered. The exact content displayed is defined by your system, network
configuration and local conditions such as the date and time.
Delay Before Action ... Minutes (not for Log Only actions)
If required, specify a time delay before the action is active (default 0 minutes).
Perform Action For
• All Alerts: The specified Action Type (above) is applied to all alerts.
• This Number of Alerts: Used to specify the number of alerts this action is
performed for. Please refer to advanced filter settings – Filter Count Method
for more details.
Comments
Add any comments you would like added to the status of this alert.
Click OK to apply the Action.
Note:
Click OK on the Add New Filter dialog to create the filter.
Use the Edit Filter option from the main Filter dialog display to amend any
settings, criteria or actions for this filter.
Set as Default
Click this button to set the currently displayed action (change as required prior
to setting) as the default action when creating new filters.
11- 9 2
Network Server Suite
Creating a Filter for Message ID Specific Events
There are many different events that are automatically generated if a specific
event occurs during the day-to-day operation of the Power/System i. This
section shows you how to create a filter that monitors and reports to the
Enterprise Console on a specific or any generic messages raised.
To create a filter for Message ID Specific Events:
1 From Windows® Start select Programs | Halcyon Network Server Suite |
Enterprise Console | Server Options
2 Select the Filters tab and click Add Filter
3 Keep all defaults and enter a Description for the new filter
4 Select the Criteria tab and click Add Criteria
5 Enter Message ID in the Details Text field
6 Select the Details Value operand as ‘=’ and enter either the specific message
ID of the message on which you wish to filter or use the wildcard symbols ‘*’
and ‘?’ to filter for generic message ID’s
7 Select the Device Selection option
8 Select the Device(s) from which you wish to receive details of any
messages. See Device Selection for more details. Click OK
9 Select the Actions tab and click Add Action
10From the drop-down menu choice select Send Console Action as the
Action Type.
11Click OK to Add the Action
12Click OK again to add the Filter
13With the filter selected in the main display, click Release Filter
14Click Apply to save the settings.
Actions
Settings on this tab of Enterprise Server Options are used to set global options
for filter actions.
Outstanding Actions settings
Process Outstanding Actions on Startup
Select this option to specify whether any pending actions are executed upon
starting a new session of Enterprise Console.
Reset Filter Alert Counters on Startup
Select this option to reset all filter counters back to zero when starting a new
session of Enterprise Console.
Enterprise Server Options
11-93
The system remembers the current count of all active filters so for example, if a
counter has an action of sending a message on the third instance of being
raised and the current count is two, the system will reset this setting back to
zero if this option is selected.
Forward Action settings
Resend Alert If Forward Action Fails
Select this option to ensure that any alerts that are raised with the forward
action, are resent if the initial forwarding action fails.
Resend Interval
Specifies the time delay (in minutes) in resending forwarding alerts.
Resend Retry Count
Specifies the number of times that the resend action is attempted.
SNMP Traps settings (only visible if NSS is licensed for SNMP Trap Support)
Resend Traps If Alert Stays Open
Select this option to ensure that any alerts that are raised with the SNMP Trap
action are resent if the initial SNMP Trap alert stays open.
Resend Interval
Specifies the time delay (in minutes) in resending SNMP Trap alerts.
Resend Retry Count
Specifies the number of times that the resend action is attempted.
Connection Monitor
The Connection Monitor is used to monitor connections to remote Windows,
AIX and Linux servers as well as monitoring Power/System i connections.
Windows, AIX and Linux Servers
Each system defined on the Central Configuration Manager has an advanced
setting of “Send Connection Check To” Enterprise Server. If this setting is
enabled, the connection monitor, providing it too is enabled, sends a connection
check to these systems every sixty minutes. If no communication is received
from a system within any sixty minute period (+ 2 minute grace period) an alert
is generated with the text as defined in the Alert Text field.
Halcyon iSeries software
The Handshake Interval setting from within the Remote Locations menu option
on the Power/System i device specifies the frequency with which this device
connects to the Enterprise Console.
Therefore, if the Handshake Interval field entry is set to 5, the Power/System i
Device attempts to connect to the Enterprise Console.
11- 9 4
Network Server Suite
Enable the Connection Monitor to indicate that the Enterprise Console is active
whenever the Power/System i device connects. If no communication is received
from the Power/System i device within any sixty minute period (+ 2 minute
grace period) an alert is generated with the text as defined in the Alert Text field.
Connection Monitor working with Halcyon Legacy software
When working with Halcyon Legacy software and with the Connection Monitor
enabled, the Connection Monitor is activated as soon as a connection check
message is received. The Halcyon Network Manager sends a connection check
message every 6 minutes (plus 4 minutes grace period). Once activated, an
alert is raised for each device that has not sent a connection check message in
the allocated timeframe.
Note:
In the above scenarios, systems that are deemed as ‘Busy’. i.e. sending a
large quantity of alerts may not make the connection as per planned interval.
Figure 11.8 Connection Monitor Settings
Connection Monitor - Connection Monitor page
Enable Connection Monitor
Click to enable the Connection Monitor and associated settings.
Continue Alerting For Failed Connection Checks
With this setting enabled, the Connection Monitor continues to send alerts for
failed connection checks even though the original connection problem has
already been reported. Alerts continue to be generated for the failed connection
until the issue is corrected.
Enterprise Server Options
11-95
Alert Text
Default alert text (Connection Check Not Received From Device &N/&A Please Investigate) is displayed in this field. This text can be edited as required.
You can also add alert and device variables to clarify the details of the
message.
Note:
An example of how the actual alert will be displayed if generated, based upon
the text and variables used, is shown in the Example field.
When using substitution variables throughout Network Server Suite, any
entries that are made correctly are highlighted in green and those that will
result in an error are highlighted in red.
Substitution Variables
Connection Monitor substitution variables comprise:
• Alert Variables (such as Date, Time, Source, Type and so on)
• Device Variables (such as Name, IP Address, Group name and so on)
These variables can be added to the error message as required to identify the
name and/or address of devices whose connections are monitored.
Ping Monitor
These options allow you to ping devices (selected in the Device Selection page)
at regular intervals. If a device ping is unsuccessful, an alert is generated with
the text as specified in the Alert Text field.
Ping Monitor - Ping Monitor page
The following options are available on the Ping Monitor page:
Enable Ping Monitor
Click to enable the Ping Monitor and associated settings.
Interval: - Minute(s)
This option sets the ping interval in minutes. Either overtype the current entry or
use the up/down arrows to adjust the setting. The default setting is 60 minutes.
Ping Timeout: - Milliseconds(s)
This setting defines the time period after which any attempted ping is deemed to
have failed. Either overtype the current entry or use the up/down arrows to
adjust the setting. The default setting is 2000 milliseconds.
Ping Attempts
This setting defines how many attempts are made to successfully connect with
the device before the alert is raised. Either overtype the current entry or use the
up/down arrows to adjust the setting. The default setting is 4 attempts.
11- 9 6
Network Server Suite
Time-to-Live
This setting defines for how long each ping is deemed active. Either overtype
the current entry or use the up/down arrows to adjust the setting. The default
setting is 128 milliseconds.
Success Percentage
This setting determines the percentage of attempts required to be successful in
order to prevent an alert being generated. For example, with this field set to
100% and Ping Attempts set to 4, it would only take one failure to generate a
success percentage of 75% and therefore raise an alert. Either overtype the
current entry or use the up/down arrows to adjust the setting. It is advised that
the success percentage is a multiple of the setting in the Ping Attempts field.
The default setting is 100%.
Detailed Ping Logging
Enable this field to generate full detailed text of the ping that appears in the Alert
Details section of any alert generated by this monitor.
Alert Text
This is the text message used to report a ping error (default is: Unable to Ping
Device &N/&A – Please Investigate {&E}. This text can be edited as required.
You can also add alert, device and ping variables to clarify the details of the
message.
Note:
An example of how the actual alert will be displayed if generated, based upon
the text and variables used, is shown in the Example field.
When using substitution variables throughout Network Server Suite, any
entries that are made correctly are highlighted in green and those that will
result in an error are highlighted in red.
Substitution Variables
Ping Monitor substitution variables comprise:
• Alert Variables (such as Date, Time, Source, Type and so on)
• Device Variables (such as Name, IP Address, Group Name and so on)
• Ping Variables (such as Ping Attempts, Failed Attempts and so on)
These variables can be added to the error message as required to identify the
name and/or address of devices whose connections are monitored.
Ping Monitor Tab - Device Selection page
The following options are available on the Device Selection page (accessed via
the Ping Monitor tab and the Add New Criteria dialog).
Please refer to “Criteria tab - Device Selection page” on page 11-86 for details
on the Device Selection fields.
Enterprise Server Options
11-97
Syslog Monitor
Note:
The Syslog Monitor is used to capture system log information from identified
devices (typically from UNIX® and Linux® servers) and forward it to the
Enterprise Console.
The Syslog Monitor is only visible if you have purchased a license for use.
Figure 11.9 Syslog Monitor Settings
Syslog Monitor Tab – Syslog Monitor page
Enable Syslog Monitor
Click to enable the Syslog Monitor.
Alert Text
This is the text message used to report a ping error (default is: &M). This text
can be edited as required. You can also add alert, device and syslog variables
to clarify the details of the message.
Note:
11- 9 8
An example of how the actual alert will be displayed if generated, based upon
the text and variables used, is shown in the Example field.
When using substitution variables throughout Network Server Suite, any
entries that are made correctly are highlighted in green and those that will
result in an error are highlighted in red.
Network Server Suite
Substitution Variables
Syslog substitution variables comprise:
• Alert Variables (such as Date, Time, Source, Type and so on)
• Device Variables (such as Name, IP Address, Group Name and so on)
• Syslog Variables (such as Facility, Severity, Message and so on)
These variables can be added to the error message as required to identify the
name and/or address of devices whose connections are monitored.
Syslog Message Facilities
Numerical Code
Facility
0
kernel messages
1
user-level messages
2
mail system
3
system daemons
4
security/authorization messages (note 1)
5
messages generated internally by syslogd
6
line printer subsystem
7
network news subsystem
8
UUCP subsystem
9
clock daemon (note 2)
10
security/authorization messages (note 1)
11
FTP daemon
12
NTP subsystem
13
log audit (note 1)
14
log alert (note 1)
15
clock daemon (note 2)
16
local use 0 (local0)
Enterprise Server Options
11-99
17
local use 1 (local1)
18
local use 2 (local2)
19
local use 3 (local3)
20
local use 4 (local4)
21
local use 5 (local5)
22
local use 6 (local6)
23
local use 7 (local7)
Syslog Message Severities
Numerical Code
Severity
0
Emergency: system is unusable
1
Alert: action must be taken immediately
2
Critical: critical conditions
3
Error: error conditions
4
Warning: warning conditions
5
Notice: normal but significant condition
6
Informational: informational messages
7
Debug: debug-level messages
Forwarding Syslog Messages from a Linux® Device
In order to be able to forward syslog messages to the Enterprise Console from a
Linux® device, the following configuration steps must be implemented:
1 Log on to the required Linux® device as a super user.
2 Enter the command:
vi/etc/syslog.conf
to open the configuration file called syslog.conf.
3 Enter *.* and press the Tab key.
4 Enter the name of the host device on which Enterprise Server is running
11- 1 0 0
Network Server Suite
For example: *.* @ENTCON
5 Restart the syslog service using the command:
/etc/rc.d/init.d/syslog restart
Advanced
The Advanced tab of Enterprise Server Options provides access to Instant Alert
and SQL Settings, License Information, Helpdesk Integration and Message
Control.
Advanced Tab - Email/SMS Default settings page
Specify Send Alert as Email/SMS Defaults
Click to enable the ability to specify send alert as email/SMS defaults.
From
Click to enable the entry of the sender details. Any emails/SMS messages that
are sent via the Send Alert As option from the Enterprise Console, default to
being from the entry in this field.
To
Enter the recipient details to where the email/SMS message is sent. Any emails/
SMS messages that are sent via the Send Alert As option from the Enterprise
Console, default to being sent to the entry in this field.
Note:
Click the Address Book icon to open the Instant Alert Address Book from
where pre-defined email users can be selected.
See “Address Book” on page 14-136 for more information regarding the
Instant Alert Address Book.
Subject
Enter the default text for the email/SMS subject title. This could be something
simple such as ‘NSS - Enterprise Console Alert’ to identify the origins of the
message.
Content
The content can be made up from typed text, substitution variables listed at the
bottom of this dialog, or a mixture of both. The message content can default to
be either:
• HTML - message is generated in HTML format by default
• Use Text Below - message uses entered text as the default
Example
Displays a textual example of the current entries in the Subject and Content
fields.
Enterprise Server Options
11-101
Note:
When using substitution variables throughout Network Server Suite, any
entries that are made correctly are highlighted in green and those that will
result in an error are highlighted in red.
Substitution Variables
Use the substitution variables to assist in the building of the message content.
Send Alert as Email/SMS substitution variables comprise:
• Alert Variables (such as Date, Time, Source, Type and so on)
• Device Variables (such as Name, IP Address, Group name and so on)
Advanced Tab - Helpdesk Defaults page
The Helpdesk Defaults page is used to specify defaults used when sending
alerts to third party helpdesk applications.
If a filter is triggered with the action of Raise Helpdesk Ticket, or right-click Send Alert As | Helpdesk Email directly from an Enterprise Console Alert is
selected, the default information entered in this dialog can be used to generate
an email that when received by the third party helpdesk application, can
automatically raise a ticket.
Figure 11.10 Helpdesk Defaults
11- 1 0 2
Network Server Suite
Entries made on this screen are subsequently displayed as defaults whenever
the Send Alert As | Helpdesk Email option is selected from the Enterprise
Console.
Helpdesk Integration settings
Specify Helpdesk Defaults
Click to enable the ability to specify helpdesk integration defaults.
From
Click to enable the entry of an email address from which the email is sent and
then enter a default email address that is used when using the Send Alert As |
Helpdesk Email option. Please note that this is a mandatory requirement of
some helpdesk applications.
To
Enter the email address to which the email is sent. This is usually a generic
helpdesk email address.
Note:
Click the Address Book icon to open the Instant Alert Address Book from where
pre-defined email users can be selected.
See “Address Book” on page 14-136 for more information regarding the
Instant Alert Address Book.
Subject
Enter the default text for the email subject title. This could be something simple
such as ‘NSS - Enterprise Console Alert’ to identify the origins of the email.
Content
The email content can be made up from typed text, substitution variables listed
at the bottom of this dialog, or a mixture of both. Most helpdesk applications
require the information to be in a specific format so that they can successfully
generate the helpdesk ticket. Please refer to your helpdesk application software
documentation for specific requirements.
Example
Displays a textual example of the current entries in the Subject and Content
fields.
Note:
When using substitution variables throughout Network Server Suite, any
entries that are made correctly are highlighted in green and those that will
result in an error are highlighted in red.
Substitution Variables
Use the substitution variables to assist in the building of the email text content.
Helpdesk substitution variables comprise:
• Alert Variables (such as Date, Time, Source, Type and so on)
• Device Variables (such as Name, IP Address, Group name and so on)
Enterprise Server Options
11-103
Advanced Tab - Instant Alert page
Figure 11.11 Instant Alert Server page
The following options are available on the Instant Alert page:
Select Server
This is used to select the server on which the instance of Instant Alert is
running.
To select the Instant Alert Server:
1 From the Advanced Settings – Instant Alert page, click Select Server. The
Select Device dialog from which the Instant Alert Device can be selected is
displayed. The device on which Enterprise Console is installed is listed by
default.
2 Highlight the required device and click Select. The selected device is now
installed as the Instant Alert Server.
Clear Server
Click to remove the currently displayed device as the Instant Alert Server.
Verify Server
Click to test the connection between the current device and the Instant Alert
Server.
Advanced Tab - SQL Server page
The SQL Server page is used to display the current details of the SQL Server
package being used.
11- 1 0 4
Network Server Suite
Figure 11.12 SQL Server Details
Refresh
Use the Refresh option to update the SQL details shown on this display.
Purge
Use Purge to clear all alerts, actions and pending alerts from the SQL database
tables. This quickly clears the tables should the Enterprise Server become
swamped with alerts.
Advanced Tab - Messages page
The messages page is used to display any system messages generated by the
Enterprise Server Options component of Network Server Suite. These can be
used as an audit trail showing all actions undertaken since the Enterprise
Server Options program was opened.
Click Clear to delete the current messages.
Advanced Tab - License page
The license page page of Enterprise Server Options shows the current Network
Server Suite licensing configuration of your network enterprise.
Note:
These details are also accessible from within the Central Configuration
Manager.
Enterprise Server Options
11-105
Figure 11.13 Product licenses
License Summary settings
License Code
Displays the current product license code for this installation of Network Server
Suite.
Product
Displays the name of the Halcyon product to which this license code applies.
Product Options
Displays any additional configuration options that may be included as part of
this license code.
Machine Reference
Displays the reference of this machine. This is used to generate a valid product
license code and may be requested by a member of Halcyon staff if a new
product license code is required.
11- 1 0 6
Network Server Suite
License Details Settings
This section shows you the details of all the licenses that you currently have in
force/available to use on your network enterprise. Information is supplied for
each type of Operating System Type for which you have been granted a
license. Use the scroll bar to view further license details if applicable.
Expiry
Date of expiry of this license code. Not applicable to Permanent
License Codes
Monitors
The number of monitors contained within this Operating System/
License Code combination. Note that some versions of Network
Server Suite may have a reduced number of monitors to cater for
specific scenarios where a full complement of monitors may not
be suitable. Click the ‘+’ symbol to expand the list and display the
available monitors
OS Types
Specifies the type(s) of Operating System for which the license
applies
Used/Free
Indicates the number of used licenses against the number of free
licenses for this Operating System
Total
Indicates the total number of licences that can be assigned for this
Operating System
Editing licenses
You may need to edit a license if you are running on the demonstration or
periodic versions of the software.
Note:
To edit a license:
Before progressing with these instructions, use the copy command from
within your email program to extract the license code from the email sent by
Halcyon Software as you will need to paste it into the Product Code field as
part of the licensing process.
1 From within Enterprise Server Options, select the Advanced Tab
2 From the Advanced menu, select License. The current license information is
displayed
3 Next to the current license code, click Edit. The Edit Product Code dialog is
displayed
4 Click Paste. The new code is now displayed in the License Code field and
any applicable license details are updated. Click OK to confirm the new code.
The Edit Product Code dialog closes
5 Click Apply to confirm the changes
6 On the Confirmation popup dialog click OK to save the settings
Enterprise Server Options
11-107
Assigning Licenses to Individual Systems
Note:
See Configuration Manager - Applying licenses for details on how to assign
licenses to individual systems.
Enterprise Server Options buttons
There are five buttons displayed at all times at the bottom of the Enterprise
Server Options dialog.
About button
Click to display version and ownership details of the Enterprise Server Options
software. Available Windows® Physical Memory is also displayed.
Import/Export button
Click the Import/Export button to import or export current Enterprise Server
Options settings from one device to another.
Exporting Enterprise Server Options settings
Settings exported from Enterprise Server Options include:
• User data
• Defined filters
To export Enterprise Server Options settings:
1 From the Windows® Start menu select Start | Programs | Halcyon
Applications | Enterprise Console | Server Options
2 Click Import/Export in the Footer section of the Enterprise Server Options
dialog.
3 Select Export and enter a Path and File Name or click
directory and file name to which the exported data is saved.
to select a
4 Click OK to save the data in the named file and location. The file is saved
with an extension of .eco.
Importing Enterprise Server Options settings
By importing settings from another instance of Enterprise Server Options, you
overwrite any existing data. This action cannot be undone.
You must have previously Exported Settings from an existing instance of
Enterprise Server Options prior to using the Import functionality.
To import Enterprise Server Options settings:
1 From the Windows® Start menu select Start | Programs | Halcyon
Applications | Enterprise Console | Server Options
2 Click Import/Export in the Footer section of the Enterprise Server Options
dialog.
11- 1 0 8
Network Server Suite
3 Select Import and click
to select a directory and an .eco file.
4 Click Open to import the data into this instance of Enterprise Server Options
and override any existing data.
Reset button
Click to restore the original Server Settings to this installation. You are
prompted to confirm this action.
Apply button
Click to apply any changes to the Enterprise Server Options. If clicked without
any settings having been changed, the following dialog is displayed:
Close button
Closes the Enterprise Server Options dialog. If you have not saved any
changed options, you are prompted to do so prior to closing.
Device Dialog
The Device Dialog is used to view, add and edit system devices and operates in
read-only or read/write mode according to the application from which the dialog
is accessed (Enterprise Server Options or Device Manager).
View Device Dialog (Read-only Mode)
Within Enterprise Server Options, the dialog (View Device Dialog) functions in
read-only mode.
The dialog is accessed via the Device Selection pages accessible from Filter |
Criteria and Ping Monitor pages by clicking View Details (active when a
device is selected from the associated list).
No changes can be made when in view only mode. For detailed information
regarding the pages, options and fields within the Device Dialog, please refer to
the section Device Manager – Adding Devices.
Enterprise Server Options
11-109
C
HAPTER
ENTERPRISE CONSOLE ARCHIVE
CHAPTER12
Overview
This utility is used to view Enterprise Console Archive (.eca) files created by the
system. The content of archive files is specified on the Enterprise Server
Options | Alerts | Archive page. Once a file has been created, it can be saved
to the default directory (the directory in which the Enterprise Server Options;
ECServOpt.exe file is installed) or a user-specified directory.
Archive files are viewed by launching the Enterprise Console Viewer, from
either Enterprise Console | Tools | Archive Viewer or Start | All Programs |
Network Server Suite | Enterprise Console | Archive Viewer and selecting a
file from the list of .eca files displayed in the Select Archive To Open dialog.
Alternatively, if you have previously opened lots of archive files, select the Open
Recent File option and select from those listed. The contents of the selected
archive file are opened into the viewer utility.
About Archive Files
Archive files contain a record of closed, replied and deleted alerts. Files can be
generated daily, weekly or monthly. Different (discrete) files can be generated if
you wish to save alerts archive details within specific time periods, or one file
can be generated which is updated with the most recent alert details.
There is no limit to the size of files that can be created, however, if you save all
of the information into one file and your system is likely to generate many alerts,
the file may eventually become very large and therefore time consuming to
navigate.
Alert details are generated for replied, closed and deleted alerts only, at the time
when a response was generated against the alert.
12- 1 1 0
Network Server Suite
Creating Multiple Archive Files
This procedure allows you to record alert details for specified, sequential
periods (daily, weekly or monthly), creating a new file for each period. Once
these settings have been specified, new files are created automatically until the
settings are modified.
1 Launch the Enterprise Server Options and select Alerts | Archive:
2 Check the Save Alerts To An Archive File option to switch on archive file
creation.
3 Specify which alerts you wish to archive in the Alerts To Archive radio
button options.
4 Select how often the archive files are generated from the Create Archive
Files drop-down combo box. Three options are available:
• Daily
• Weekly
• Monthly
5 Specify a directory and path to save the archive files into. If a directory and
path is not specified, the files are saved to a default directory (the directory in
which Enterprise Server Options .exe file is installed).
The directory can be created on any accessible machine on your network,
(archive files do not have to be localized). If the directory is shared across
your network, the archive files can be accessed by all users if required.
6 Specify the file name for the archive files and add period details using the
Substitution Variables options.
Enterprise Console Archive
12-111
Note:
These details are added to each file name as it is generated (spaces can be
added between the variables to clarify the names).
To ensure each file has a unique file name, at least two substitution variables
should be added to the file name.
An example of the file name in full is displayed in the Example read-only text
box.
7 Click OK accept and save these settings.
Creating One Master Archive File
This procedure allows you to record alert details in one master file which is
updated at the frequency specified in the Create Archive Files drop-down
combo box. New information is appended to the contents of the existing file
each time the file is generated.
Once these settings have been specified, an updated file is created
automatically until the settings are modified.
1 Launch the Enterprise Server Options and select Alerts | Archive.
2 Check the Save Alerts To An Archive File option to switch archive file
creation on.
3 Specify which alerts you wish to archive in the Alerts To Archive radio
button options.
4 Select how often the archive file is to be generated from the Create Archive
Files drop-down combo box. Three options are available:
• Daily
• Weekly
• Monthly
5 Specify a directory and path you want to save the archive file to. If a directory
and path is not specified, the file is saved to a default directory (the directory
the Enterprise Server Options .exe file is installed in).
The directory can be created on any accessible machine on your network, so
the file does not have to be localized. If the directory is shared across your
network, the archive file can be accessed by all users if required.
6 Specify an archive file name only. Do not add time details to the file name.
7 Click OK accept and save these settings.
Viewing an Archive File
To view archive file details:
1 Launch the Enterprise Console Viewer.
The Select Archive To Open dialog is displayed allowing you to choose an
archive file to view.
12- 1 1 2
Network Server Suite
2 Select a file from the .eca files listed and click Open.
The file is opened into the Enterprise Console Viewer main window.
3 Double-click on any of the alert details listed to view individual alert details in
the Alert Details window.
4 Use the navigation buttons to scroll back and forward through the available
records.
Enterprise Console Archive
12-113
C
HAPTER
CENTRAL CONFIGURATION MANAGER
CHAPTER 13
Overview
The Central Configuration Manager (CCM console) component is used to host
the Server Manager element of Network Server Suite from where you can
configure monitors and filters, apply templates and set up generic performance
reporting criteria.
Note:
Note:
Once a device has been defined within Device Manager it can be added as a
system within the Central Configuration Manager, although only servers and
workstations can be monitored through functionality within the CCM.
Printers, hubs, routers and the like can be monitored by the use of SNMP
Traps in Enterprise Server Options, if you have the appropriate license.
Once added as a system, various monitors become available that you can then
apply to monitor this system for common causes of errors and issues that may
affect stability and performance on your network enterprise. Pre-defined
templates can be used to speed up the process of applying key monitors across
the network. A reporting template can be applied at system level to provide
information on generic performance data to ensure that systems can be
maintained at optimum performance levels.
See the sections “Working with Monitors”, “Templates” and “Reporting” for
more details on how to use these functions.
CCM Server
The CCM Server is a background service associated with the Central
Configuration Manager that allows communication between devices in a similar
way to that used by the Enterprise Server.
A default CCM Server can be specified that is then applied to all devices added
as systems within the Central Configuration Manager. See Central
Configuration Manager - Options - “CCM Server page” on page 13-121 for more
details.
13- 1 1 4
Network Server Suite
Specifying an alternative CCM Server
You may need to change the CCM Server device should you have another
device situated behind a firewall with which you need to communicate. In these
instances, change the CCM Server to the Network Address Translation (NAT)
Address that your remote server uses to talk back to your Enterprise Server.
Systems Tab
Click the Systems Tab in the left-hand navigation panel of the Central
Configuration Manager to display a tree view of currently managed systems.
Systems are listed by group type (as defined in Device Manager - “Managing
Device Groups”). Each monitor is displayed beneath the system name and is
shown in bold typeface if a filter, template or reporting structure has been
applied.
Figure 13.1 Systems navigation panel
Central Configuration Manager
13-115
When at System level in the Systems panel, the System details are shown in
the main panel of the Central Configuration Manager.
Figure 13.2 Systems panel displayed at system level
System Details settings
Shows the details of both the system and the associated Enterprise Server and
CCM Server devices. Click on a device to select. Click Select to view the details
of the device that is currently highlighted.
Licensing settings
The license settings show the current number of licenses available for the
operating system to which the selected system belongs. The entry displayed in
this field changes as you change between systems on different operating
systems.
Note:
If you only have systems operating within Windows, then this is the only
operating system that is displayed in this field.
See “Applying Individual Licenses” on page 5-14 for more information on how
to license systems within Central Configuration Manager.
Message Log settings
Use the following options to set the log settings for the selected system.
On AIX® and Linux® systems, the default setting is to log messages (except
Diagnostic Messages which are File and Syslog only) to the Syslog, and
additionally to a file and or Enterprise Server device.
13- 1 1 6
Network Server Suite
Note:
All log files are saved with an extension of .hlf.
Log Error Message To
On non-AIX® and Linux® systems, error messages are automatically logged to
the error message log file. See “Logging Page” on page 13-122 for more
information. Error messages can also be logged to the Enterprise Server device
if required.
Log Informational Messages
Check to ensure that any generated Informational Messages are logged to File.
Log Diagnostic Messages
Check to ensure that any generated Diagnostic Messages are logged to File.
Advanced settings
Send Connection Check To
Automatically defaults to ensure that a connection check is periodically sent to
the Enterprise Server to ensure constant connection between the two devices. It
is recommended that this setting is left unchanged.
Adding a System to Central Configuration Manager
To add a system (which must first be defined in Device Manager) to the Central
Configuration Manager console, click
from the tool bar. The Select System
dialog is displayed.
Note:
You must be at the top level (default or Device Group name) of the system
tree in the Systems navigation panel in order for this button to be available.
All devices currently loaded via Device Manager are listed in the Select System
dialog. Highlight the required system and click Select. The Add Systems dialog
is displayed.
Figure 13.3 Add System dialog
Select the system to be added to Central Configuration Manager.
Central Configuration Manager
13-117
Note:
The Install Software On System option is activated as a default on all
systems except AIX® and Linux® Devices. This option remotely installs the
Server Manager software onto the system being added. See also: Central
Configuration Manager Options : “Installation Page” on page 13-122
If required, an alternative Enterprise Server and/or CCM Server device can be
specified by highlighting the respective device in the Add System dialog and
clicking Select. The Select System dialog is re-displayed from where an
alternative device can be chosen.
Click OK to add the system to the Central Configuration Manager and if chosen,
install the Server Manager software.
Click
to save the current settings. The Save Settings dialog is displayed. If
you have retained the default setting of installing the software on to the system,
you are required to provide valid logon details for the system. Click OK to
remotely install the software onto the system and continue saving settings.
Deleting Systems
Systems can also be deleted from the Central Configuration Manager if they are
no longer required. Simply select the required system in the left-hand navigation
pane of the systems tab and then either use File | Delete System or click the
icon from the toolbar. Remember to save the settings prior to exiting.
Re-installing software remotely
Windows Server Manager software can be re-installed remotely on any system
at any time by right-clicking on the relevant Server Manager (listed beneath the
System Name) in the Systems navigation panel and selecting Reinstall
Product.
Note:
Note:
13- 1 1 8
A remote install of Network Server Suite requires the ADMIN share to be
available.
Alternatively, software can be remotely re-installed on existing systems by
selecting Tools | Reinstall Product from the menu bar.
Required Authority: The user must have administrative account authority
on the remote system. See Central Configuration Manager Options “Installation Page” on page 13-122 for more information.
Network Server Suite
Templates
Templates are designed to provide the same level of monitoring across a
number of similar devices by applying a set of user-defined filters with a singleclick. This greatly reduces set-up time and ensures all defined systems are
covered by at least a basic level of monitoring. Should you need to make a
system-wide change at a later date, a single update covers all systems using
the template.
Click the Templates tab in the left-hand navigation panel of the Central
Configuration Manager to display the currently defined templates that are
available.
It is possible to open a template from either the left-hand or right-hand pane of
this screen.
Templates are covered in more detail in the chapter “Templates”.
Figure 13.4 Network Server Suite Templates
Central Configuration Manager
13-119
Advanced
Advanced settings of the Central Configuration manager allow you to view
connectivity messages and license information.
Messages page
The Advanced | Messages page shows details of any system messages that
are sent between the Central Configuration Manager and Remote Servers.
Use View | Clear Messages to remove the messages from this display.
License page
The Advanced | License page of the Central Configuration Manager contains
information relating to the current licensing of Network Server Suite. This is
covered in detail in the Enterprise Server Options section “Advanced Tab License page” on page 11-105.
Saving Central Configuration Manager settings
Any changes made within the Central Configuration Manager Console must be
saved prior to exiting the program otherwise the changes are cancelled.
When any changes have been made to a system configuration within the
Central Configuration Manager, the top level system name is highlighted within
the left-hand navigation panel.
Note:
Settings need to be saved when the
icon is visible on the tool bar.
When the settings are saved, the following dialog is displayed:
Figure 13.5 Save Settings dialog
13- 1 2 0
Network Server Suite
A progress bar for each agent machine is displayed when saving settings. The
disk icon changes to a tick mark encased in a green circle
to indicate that
the settings have been successfully saved.
The Saving Settings dialog remains open until you click Close unless you have
ticked the Close When Complete checkbox.
Central Configuration Manager Options
Central Configuration Manager Options are used to set specific configuration
options and are applied from Tools | Options on the menu bar.
There are six separate pages that comprise these options.
CCM Server page
This page is used to define the default CCM Server device that is then used for
CCM connections for other devices that are subsequently added to the Central
Configuration Manager.
Note:
It is recommended that the default CCM server is the same device selected
as the Enterprise Server. This setting can be overridden if required at both
default and system level. See Monitor Settings for more information.
Select Server
Click to display the Select Device dialog from which the CCM Server device can
be selected. This must have been loaded via the Device Manager prior to the
device being available for selection in this dialog.
Clear Server
Click to clear the details of the current CCM Server device.
Verify Server
Click to verify the connection between the device on which this configuration is
being undertaken and the selected CCM Server device.
Connection page
This page is used to determine timeout settings between the CCM Server and
Enterprise Server.
Connection Timeout
The entry in this field sets the time within which the CCM Server must be
connected to the Enterprise Server before timing out. The default setting is 120
seconds.
Read Timeout
The entry in this field sets the read timeout limit between the CCM Server and
the Enterprise Server. The default setting is 120 seconds.
Central Configuration Manager
13-121
Enterprise Server Page
This page is used to define the default Enterprise Server device that is then
used for processing Enterprise Server actions.
Select Server
Click to display the Select Device dialog from which the Enterprise Server
Device can be selected. This must be loaded via the Device Manager prior to
this selection being made.
Clear Server
Click to clear the current server device.
Verify Server
Click to verify the connection between the current and the selected device.
Installation Page
The options on this page are used when installing software remotely.
Use Active User
Uses the current user for logon purposes when using the remote software
installation option.
Use Specific User
Enter the User Name and Password details of the user who logon details are
used when using the remote software installation option.
Show User Details Prompt on Installation
Enable this setting to have the entered User Details requested at the point of
installation.
Note:
Required Authority: The selected user must have administrative account
authority on the remote system.
Instant Alert Page
This page is used to define the default Instant Alert device that is then used for
processing Instant Alert actions.
Select Server
Click to display the Select Device dialog from which the Instant Alert Server
Device can be selected. This must be loaded via the Device Manager prior to
this selection being made.
Clear Server
Click to clear the current server device.
Verify Server
Click to verify the connection between the current and the selected device.
Logging Page
This page provides options to log both Informational and Diagnostic messages
to ccmserver.hlf and ccmconsole.hlf log files.
13- 1 2 2
Network Server Suite
By default, these files can be found in the directory paths:
\program files\halcyon\central configuration manager\console
and
\program files\halcyon\central configuration manager\server.
Other Central Configuration Manager features
Synchronizing Settings
The Synchronize Settings option is used to ensure that system settings remain
constant between use of the Save Settings command.
This option is available from File | Synchronize Settings.
A progress bar for each agent machine is displayed when synchronizing
settings. The disk icon changes to a tick mark encased in a green circle
indicate that the settings have been successfully synchronized.
to
The Synchronizing Settings dialog remains open until you click Close unless
you have ticked the Close When Complete checkbox.
Once a change has been made to the system, such as a filter being edited, then
this option is unavailable and is replaced by the Save Settings option.
Importing and Export Central Configuration Manager settings
Because the Central Configuration Manager is the hub on which Network
Server Suite operates, it is wise to take a backup so that should the device on
which you are running CCM fails, you can easily and quickly restore settings to
a new machine.
Note:
Likewise, if you have multiple installations of Central Configuration Manager
running across your network enterprise, it is possible to save time by exporting
and then importing settings between these installations.
Any existing settings are overwritten when Central Configuration Manager
settings are imported.
Exporting Central Configuration Manager settings
1 From the Central Configuration Manager menu bar, select Backup | Export
Settings. The Save As dialog is displayed.
2 Select the directory path to which the Central Configuration Manager settings
export file is saved. The default directory is: C:\Program Files\Halcyon\
Central Configuration Manager\Console\Backup.
3 Enter a file name by which to identify the export file. The default entry for this
field is in the format of: ‘CCMServer-YYYY-MM-DD-HHMMSS-Ms.csf.’ It is
recommended that you retain this setting unless your internal practices
require a specific entry format.
Central Configuration Manager
13-123
4 Retain the setting of ‘.csf’ in the Save as type field and click Save to create
the named Central Configuration Manager settings file in the specified
directory.
Importing Central Configuration Manager settings
1 From the Central Configuration Manager menu bar, select Backup | Import
Settings. You are prompted to confirm the import action as it will overwrite all
existing systems and templates from a backup file.
2 Click Yes to confirm the import of device settings and display the Open
dialog.
3 From within the ‘Look In’ field, navigate to the network directory path where
the Central Configuration Manager settings file (.csf) is stored. Click on the
file that you wish to import so that it is highlighted and then click Open to start
the import process.
When the import process is complete, a system message is displayed
confirming the successful import of the settings. Click OK to close this
message and display the list of imported systems in the Systems tab of the
Central Configuration Manager left-hand navigation panel.
You can also export and import template settings. See “Exporting and
Importing Templates” on page 18-243.
Auto Collapse
Central Configuration Manager uses a feature called Auto Collapse (set to On
as default). This feature automatically closes the previous tree view so that the
navigation area remains as accessible as possible, which is beneficial if you
have many different systems to view and maintain.
To turn this option off and prevent the tree view from automatically collapsing,
select View | Auto Collapse from the menu bar.
Upgrade Systems
Use the upgrade systems feature to install the latest version of the software
onto remote systems. This option is available from Tools | Upgrade Systems.
Note:
13- 1 2 4
A remote upgrade of Network Server Suite requires the ADMIN share to be
available.
Network Server Suite
Figure 13.6 Upgrade System Software
All available systems are listed by default and the Check All option enabled,
meaning all systems are automatically selected for upgrade. If all the systems
are not immediately visible, you can resize this dialog.
Agent systems are listed by the group under which they are defined in Device
Manager. You can upgrade all the machines within a group or just selected
devices. Click next to any systems (or Group) that you DO NOT wish to upgrade
so that the tick mark is removed.
The upgrade process begins.
Central Configuration Manager
13-125
Depending on the settings that are in the “Installation Page” of Central
Configuration Manager Options, you may be prompted for a user logon and
password. Enter a valid user ID and password which must have administrative
account rights on the remote system.
The upgrade process continues. Check the Close When Complete option to
automatically close this dialog once the upgrade is complete. If the upgrade
process fails on one or more of the agent machines, this dialog remains open
and the systems that have not upgraded correctly are identified by a red cross
icon. Hover the mouse pointer over the icon to display the reason for failure.
Once complete, save the settings using File | Save Settings.
Alert Log
The Alert Log provides information on all alerts raised on a server-by-server
basis for a ten-day rolling time period. This setting is not user-configurable.
The Alert Log can be accessed from the Central Configuration Manager |
View | Alert Log or by clicking
on the toolbar. (not available when viewing
the Advanced Tab).
The Alert Log is split into two pages:
• Search
• Results
Search Page
The fields on this page are used to specify the criteria used to retrieve alerts
from the alert log.
Alert Created Date
The From and To fields allow you to select specific date and time criteria ranges
between which the search is conducted for alerts created.
Alert Status Date
The From and To fields allow you to select specific date and time criteria ranges
between which the search is conducted for alerts with a changed status.
13- 1 2 6
Network Server Suite
Alert Status
Click to enable the search by Alert Status.
Select which Status types are required for the search parameters:
• Pending
• Cancelled
• Error
• Closed
Use Select All to add all Alert Status Types to the search parameters.
Figure 13.7 Alert Log - Search Page
Action Status
Click to enable the search by Action Status.
Select which Action Status types are required for the search parameters
• Pending
• Cancelled
• Error
• Closed
Central Configuration Manager
13-127
Use Select All to add all Action Status Types to the search parameters
Action Type
Click to enable the search by Action Type.
• Control Service
• Execute Command
• Hold Filter
• Log Only (No Action)
• Release Filter
• Send Enterprise Console Alert
• Send Message
• Send Network Message
• Send SNMP Trap
Use Select All to add all Action Types to the search parameters
Auto Switch to Results
Enable this setting to automatically switch to the Results page once the search
has been completed.
Results Page
The results page is split into two sections; one for displaying all matching alerts
returned from the entered search criteria and the second for displaying all
matching actions returned.
13- 1 2 8
Network Server Suite
Figure 13.8 Alert Log - Results Page
Viewing Alert Details
Select the alert from those listed and click Details (in the top section). The Alert
Details dialog is displayed from where the full details of the alert can be viewed
(no amendments can be made on this screen). Use the
and
arrows to
move through previous or subsequent alerts if required.
Refresh Alert
Click Refresh Alert to refresh any highlighted alerts.
Viewing Action Details
Select the alert from those listed and click Details (in the top section). The
Action dialog is displayed from where the full details of the action can be viewed
(no amendments can be made on this screen).
More Information
Please refer to the section “Working with Monitors” on page 17-155 for more
information on using the Central Configuration Manager to create and apply
filters which can then monitor your network enterprise.
Please also see:
“Templates” on page 18-221
“Reporting” on page 19-244
for more information relating to Central Configuration Manager functionality.
Central Configuration Manager
13-129
C
HAPTER
INSTANT ALERT
CHAPTER14
Overview
Instant Alert is the Network Server Suite component used to send text
messages to mobile phones from either the Server Manager or Enterprise
Console. Email messages can also be sent. If you use a GSM data terminal, it
must be installed on the same machine as Instant Alert.
Broadcast groups and schedules can be set up so messages are sent to the
appropriate on-call personnel. A message log is provided to monitor the status
of messages.
The date/time of any message sent through Instant Alert is automatically
adjusted to take account of any local time zone setting, providing that the device
has been configured to specify a time zone other than the current local setting
and that alerts are logged using the Remote/Date Time setting
See “Time Zone” on page 7-28
See “Log Alerts Using” on page 11-67
Instant Alert comprises three components:
• Server Options
• Address Book
• Message Sender
Server Options
The Instant Alert Server Options are used to configure various interfaces
associated with Instant Alert.
To open Instant Alert Server Options select Start | All Programs | Halcyon
Network Server Suite | Instant Alert | Server Options.
14- 1 3 0
Network Server Suite
Five pages are available from within Instant Alert Server Options.
Figure 14.1 Instant Alert Server Options
General page
This page is used to define the device location details, timeout and pending.
Host/Address
Load recognized network devices from a known host, (the device on which
Device Manager is installed), by entering the local host IP address and clicking
Load. A system message advises you of how many devices have been
successfully loaded.
Connection Timeout
Specify a time (in seconds) in which the connection to the selected device must
be made before timing out. The default setting is 5 seconds.
Read Timeout
Specify a time (in seconds) in which data must be read from the device before
timing out. The default setting is 5 seconds.
Clear Pending Messages
Enable this option to ensure that any pending messages are cleared when
Instant Alert is started. This is useful if a high volume of messages have been
generated as the result of an error but are no longer required for information
purposes, for example, test messages.
Instant Alert
14-131
Logging page
Use the Logging options to specify the Informational and/or Diagnostic
messages information you wish to save to the default log file of IA.hlf (you can
override this filename if you wish). Message log files are stored by default in:
C:\Program Files\Halcyon\Enterprise Console\Logs
(or the drive and directory to which you installed Network Server Suite)
The Maximum Log Size states the maximum size of the file. The default setting
is 10240KB but this may need to be increased if both Informational and
Diagnostic messages are being saved.
Log Informational messages
Click to enable the logging of any Instant Alert information messages that are
generated.
Log Diagnostic messages
Click to enable the logging of any Instant Alert diagnostic messages that are
generated.
Purge page
The purge page of Instant Alert Server Options is used to set time periods after
which various types of Instant Alert messages are purged.
Purge Closed Messages After
Use this option to select the number of days after which closed messages are
removed from the system. The default setting is 30 days.
Purge Error Messages After
Use this option to specify the number of days after which error messages are
removed from the system. The default setting is 30 days.
Purge Old Pending Messages After
Use this option to specify the number of days after which any messages that are
still in pending status are removed from the system. the default setting is seven
days.
Enterprise Server page
This page is used to specify on which server the Enterprise Server is installed this ensures any problems with the Instant Alert product are transmitted to the
Enterprise Server machine, and then on to the Enterprise Console.
Note:
The entry on this page is usually selected as part of the Network Server Suite
installation process.
Interfaces page
This page shows the various interfaces currently defined on the system. When
Instant Alert is open for the first time this screen is empty.
Click Add to add a new interface.
14- 1 3 2
Network Server Suite
Adding Interfaces
There are three types of interface that can be used with Halcyon Instant Alert.
• GSM Interface
• NPort Interface
Note:
Note:
• STMP Interface
It is also possible to add a Lotus Notes interface if you have Lotus Notes
Client installed on the machine on which Central Configuration Manager
Server is installed. See “Using Lotus Notes® (v7 or later) with Instant Alert”
on page 14-142 for more information.
Instructions on how to attach and configure GSM and NPort NETGSM
terminals to your network can be found in the Network Server Suite
Installation and Getting Started guide.
Adding a GSM Interface
Figure 14.2 Adding a GSM Interface
1 From the Instant Alert Server Options dialog select Interfaces. Click Add
and select GSM Interface.
2 Enter the Description of the GSM Interface (or leave as the default entry).
Instant Alert
14-133
3 If this interface is going to be the Primary Interface leave Backup unchecked.
Only check the Backup option if this interface is intended as a secondary
interface should another defined Interface fail.
4 Select whether to add a Date and Time and/or Message Reference prefix to
any message sent via this interface.
5 Select the Advanced side-menu option.
6 Select the New Message Processing option required. Select Process
Immediately to send the message the instant it is raised or select Process
Every nn Minute (where nn is the time interval) to batch process all
messages received between the specified interval. If required, specify the
Delay Between Messages (in seconds).
7 Select the Logging side-menu option.
8 Use the Logging options to specify the Informational and/or Diagnostic
messages information you wish to save and set the Maximum Log Size
accordingly.
9 Select the Error side-menu option.
10Specify whether to Retry sending any messages that end in an error and if
so, how many retries to attempt per second or minute, before a failure is
returned.
11Select the Settings side-menu option.
12From the drop-down list, select the Port Number for this GSM interface.
13Select the Transmission Rate Bits Per Second. If using a TC-65 GSM
terminal use 115200. For all other GSM terminals use 19200.
14Select the option for any message transmission sent via this interface. Use
the Truncate option to limit the message size but be aware that this may
result in vital information being omitted from the message. Check Use
Concatenation Mode to enable the joining of successive messages when
the number of characters per message exceeds the permissible length.
15Click OK to confirm and add the new interface.
Adding a NPort Interface
1 From the Instant Alert Server Options dialog select Interfaces. Click Add
and select NPort Interface.
2 Enter the Description of the NPort Interface (or leave as the default entry).
3 If this interface is going to be the Primary Interface leave Backup unchecked.
Only check the Backup option if this interface is intended as a secondary
interface should another defined Interface fail.
4 Select whether to add a Date and Time and/or Message Reference prefix to
any message sent via this interface.
5 Select the Advanced side-menu option.
6 Select the Advanced side-menu option.
14- 1 3 4
Network Server Suite
7 Select the New Message Processing option required. Select Process
Immediately to send the message the instant it is raised or select Process
Every nn Minute (where nn is the time interval) to batch process all
messages received between the specified interval. If required, specify the
Delay Between Messages (in seconds).
8 Select the Logging side-menu option.
9 Use the Logging options to specify the Informational and/or Diagnostic
messages information you wish to save and set the Maximum Log Size
accordingly.
10Select the Error side-menu option.
11Specify whether to Retry sending any messages that end in an error and if
so, how many retries to attempt per second or minute, before a failure is
returned.
12Select the Settings side-menu option.
13Enter the IP Address on which the NPort device is configured and ensure
that the Port Number is set to 4001.
14Select the option for any message transmission sent via this interface. Use
the Truncate option to limit the message size but be aware that this may
result in vital information being omitted from the message. Check Use
Concatenation Mode to enable the joining of successive messages when
the number of characters per message exceeds the permissible length.
15Click OK to confirm and add the new interface.
Adding a SMTP Interface
1 Enter the Description of the SMTP Interface.
2 If this interface is going to be the Primary Interface leave Backup unchecked.
Select Backup only if this interface is going to be a secondary interface
should another defined Interface fail.
3 Select whether to add a Date and Time and/or Message Reference prefix to
any message sent via this interface.
4 Select the Advanced side-menu option.
5 Select the New Message Processing option required. Select Process
Immediately to send the message the instant it is raised or select Process
Every nn Minute (where nn is the time interval) to batch process all
messages received between the specified interval. If required, specify the
Delay Between Messages (in seconds).
6 Select the Logging side-menu option.
7 Use the Logging options to specify the Informational and/or Diagnostic
messages information you wish to save and set the Maximum Log Size
accordingly.
8 Select the Error side-menu option.
Instant Alert
14-135
9 Specify whether to Retry sending any messages that end in an error and if
so, how many retries to attempt per second or minute, before a failure is
returned.
10Select the Server side-menu option.
11Enter the Port Number on which the SMTP connection is made. Click Select
Server to select the SMTP server. (this device must have already been
loaded using the Device Manager). Highlight the required device and click
Select.
12Select the Settings side-menu option.
13Select Override From Name/Address to enter a name and IP Address from
which the messages are received. Leave blank to generate messages
address from the actual device.
14If the server requires authentication, enter the User Name and Password
required to access the server.
15Click OK to confirm and add the new interface.
Address Book
The Address Book functionality of Instant Alert is used to add, edit and delete:
• Contacts and contact details
• Broadcast groups
• Schedules
This information must be entered manually and a default message type (SMS or
Email or Lotus Notes® (if installed)) can be specified for each contact. This
default can be overridden by the message type selected from the Enterprise
Server Options (but not from the Central Configuration Manager).
The Address Book is accessed from Start | Programs | Halcyon Network
Server Suite | Instant Alert | Address Book. It may also be available from
within other component of Network Server Suite when you see this icon
.
14- 1 3 6
Network Server Suite
Figure 14.3 Instant Alert Address Book
Adding a Contact to the Instant Alert Address Book
From within the Instant Alert Address Book, either select File | Add from the
menu bar or click the
icon on the toolbar. The Add New Contact dialog is
displayed.
Figure 14.4 Adding a new contact to the Instant Alert Address Book
Instant Alert
14-137
The following pages are used when adding a contact to the Address Book.
Details page
The details page is used to enter name and personal data of the contact.
Name
Select a Prefix for the contact name from the drop down list. Note that on
changing this prefix, the figure icon alters accordingly. Now enter the full name
of the contact.
Nickname
If required, enter the nickname by which the contact is known.
Birthday
If required, enter the birthday date of the contact. If not entered, this defaults to
today’s date.
Anniversary
If required, enter the anniversary date of the contact. If not entered, this defaults
to today’s date.
Default Message Type
Select the default method of sending a message to this contact. Either SMS or
Email can be selected.
Contact Numbers page
The contact numbers page is used to add the details of this contact’s mobile
phone details. Click Add to enter new details and open the Add Contact
Number dialog. A Contact may have more than one number.
Number
Enter the mobile number on which the person can be contacted
Number Type
Only SMS is currently available as a choice in this field.
Service Provider
Not used in this release of Network Server Suite.
SMS Type
Select either Normal or Flash as the SMS message type. Flash messaging is
supported by some mobile phones and will display the message as soon as it
received, no matter what the current phone status is when the message arrives.
These types of messages are usually just used as methods of notification and
do not get logged anywhere on the mobile device.
Active
Specifies the times between which this phone is active for the receipt of
messages sent via Instant Alert.
If the message is sent to the phone outside of the period when the phone is
active, it is queued and then sent as soon as the phone becomes available
again.
14- 1 3 8
Network Server Suite
Email Addresses page
The email addresses page is used to add the email address of this contact.
Click Add to enter a new email address and open the Add Email Address dialog.
SMTP Address
Enter the email address used by the contact. Only one address may be used
per contact.
Company page
The company page can be used if the new contact works for a third party
company.
Enter the required company details for the new contact as required.
Home page
The home page can be used to enter details of the contact's home address.
When all the information for the contact has been entered, click OK to create
the contact and add it to the Instant Alert Address Book.
Creating a Broadcast Group
A broadcast group can be defined as a team of people who have an interest in a
specific function or routine. For large organizations it may be that many people
are involved in very specific routines across a department. In smaller
organizations it is likely to be one or two people that have the responsibility of
running all routines.
To create a new broadcast group:
1 From the menu bar select File | Add | Broadcast Group. The Add New
Broadcast Group dialog is displayed.
2 Enter a Name and Description for the broadcast group.
3 Select Members. Click Add to display the Select Members dialog.
4 Highlight the members required in the Available panel. Click
highlighted selections into the Selected panel. Click
members from the Selected panel into the Available panel.
to move the
to move all
5 Click OK to confirm the members selected.
6 Click OK to confirm the Broadcast Group. The new group is displayed in the
Address Book panel.
Creating a schedule
A schedule is a method of ensuring that the correct person is contacted in the
event of an alert being raised.
Instant Alert
14-139
To create a new schedule:
1 From the menu bar select File | Add | Schedule. The Add New Schedule
dialog is displayed.
2 Enter a Name and Description for the schedule
3 Select Items from the menu panel and click Add. The Add New Schedule
Item dialog is displayed.
4 Select (or enter) the Dates and Times between which the schedule applies.
5 Select the Contact to which the schedule applies.
6 Click OK. The new schedule is displayed in the main address book panel.
When selecting a schedule from the Address Book, the full detail of the
selection is displayed in the right-hand pane of the Address Book window (as
shown below).
Finding a Contact
If you have a large number of contacts held within your address book, you can
use the Find utility to pinpoint a specific person.
To use this utility either, select Edit | Find from the menu bar or click the
icon on the Address Book toolbar.
Type the starting characters of the contact name and click OK. The more
characters that you enter, the more precise the search result. The contact name
(or names that begin with the characters that you entered are now displayed in
the Address Book.
Message Sender
This is a utility allowing text messages to be sent across the network to
specified recipients.
Message Sender is accessed via: Start | All Programs | Halcyon Network
Server Suite | Instant Alert | Message Sender.
14- 1 4 0
Network Server Suite
Figure 14.5 Message Sender display
To send a basic message:
1 Complete the To Address field or use the icon
contacts currently held in the Address Book.
to display the list of
2 Enter the title of the message in the Subject field
3 Enter the body text of the message in the Message field.
4 Click the envelope icon
to send as an Email message, or click the
mobile phone icon
to send as an SMS message. Click both icons to send
as both an email and SMS simultaneously.
5 If required select the message Priority of Low, Normal or High. The default
value is Normal.
6 Click Send Message to send.
To send a message with additional options:
Follow the steps 1-5 as above. From the menu bar select View | Show Options
to display additional options which can be completed as follows:
Date
The default is today's date. Enter or select the required date from the drop-down
selection. If the date selected is earlier than today, the message is sent as soon
as Send Message is clicked. If a later date is selected, the message is held until
the date and time are reached.
Time
The default is the time at which Message Sender was opened. Enter or select
the required time from the drop-down selection.
Instant Alert
14-141
If the time selected is earlier than now, the message is sent as soon as Send
Message is clicked. If a later time is selected, the message is held until the date
and time are reached.
Count
Select the number of times you require this message to be sent.
Interval
Select the interval, in minutes, between which messages are sent. (Only used if
the Count field is increased from 1)
Click Send Message.
Using Lotus Notes® (v7 or later) with Instant Alert
It is possible to use Lotus Notes® (V7 or later) with Instant Alert providing that
the correct configuration is applied. This can be done as follows:
1 Create a local user account called HALCYONIA on the server on which
Network Server Suite is installed. This represents the Lotus Notes® user that
is used solely for Halcyon Instant Alert.
2 Make user account HALCYONIA a member of the administrators group and
then log into the account to finalize the creation of the profile.
3 Install Lotus Notes® Client onto the same server on which Network Server
Suite is installed and the user account HALCYONIA was created. Please
refer to your Lotus Notes® documentation for guidance on installation of the
client product.
4 Once Lotus Notes® Client has been successfully installed, open the Halcyon
Instant Alert Service from Windows® Start | Control Panel | Administrative
Tools | Services | Halcyon Instant Alert Server. Right-click on this service
and select Stop from the drop-down menu.
5 Double click on Halcyon Instant Alert Server. When the properties dialog is
displayed, click the Log On tab.
14- 1 4 2
Network Server Suite
Figure 14.6 Instant Alert Server Properties Log On
6 Select This Account and enter HALCYONIA with the associated password
specified when the user account was created. Click Apply and then OK.
7 Right-click on the Halcyon Instant Alert Server service and select Start from
the drop-down menu.
8 Open Instant Alert Server Options from Windows® Start | Halcyon Network
Server Suite | Instant Alert | Server Options.
9 Select Interfaces from the Options tab. Click Add. From the Select Interface
to Add dialog select Notes Interface and click OK.
Figure 14.7 Adding Lotus Notes® Interface
Instant Alert
14-143
10Configure the Notes® Interface according to your operating environment. In
the Settings menu option enable Process Notes Messages (and SMTP
Messages if you wish to continue using this format) and under Authentication
Settings enter the password associated with Lotus Notes® user
HALCYONIA. Click OK to add the Interface
Figure 14.8 Setting Notes Messages Processing
11Close the Instant Alert Server Settings and open the Address Book from
Windows® | Start | Network Server Suite | Instant Alert | Address Book.
12Click Add to add a new contact. Add Name details and then select Email
Address from the Contact menu and click Add to display the Select Type to
Add dialog.
Figure 14.9 Adding Notes® Email Address
14- 1 4 4
Network Server Suite
13Select Notes® User Name and click OK to display the Add Email Address
dialog.
14Enter the required Notes® Email Address in the format User/Domain. Click
OK to add the Notes® Email Address. Click OK on subsequent screens to
close and add the contact.
15Repeat steps 12-14 to add further Notes® Email Addresses as required.
16Use Windows® Start | Halcyon Network Server Suite | Instant Alert |
Message Sender to send a test message to the Notes® contact to ensure
successful configuration.
Instant Alert
14-145
C
HAPTER
WORKING WITH SUBSTITUTION
VARIABLES
CHAPTER15
Overview
Substitution variables are used to insert information or text within an existing
piece of text. Different variables allow you to determine the text or detail that
you wish to insert and at which point.
The commonest use of substitution variables within Network Server Suite is
when allowing you to format the text of alerts sent to the Enterprise Console or
Instant Alert to be forwarded as SMS messages or emails.
All substitution variables begin with an ampersand (&) and are usually casesensitive. When a substitution variable is used, Network Server Suite searches
for an ampersand and if found, compares the following text against a list of valid
variables. If a match is made, the existing text is replaced with the substitution
variable. Any non-matching text is left in its original condition.
When using substitution variables throughout Network Server Suite, any entries
that are made correctly are highlighted in green and those that will result in an
error are highlighted in red.
Example
In the following substitution variable:
‘User &NA is not authorized to file &FN in folder &FL’
where:
&NA equals User Name
&FN equals File Name
&FL equals Folder Directory and Name
may produce the following text:
‘User John is not authorized to file Payroll.dat in folder C:\Program Files\
15- 1 4 6
Network Server Suite
Retaining an ampersand in the existing text
If you already have an ampersand in the existing text that you wish to retain
when using substitution variables, simply insert a double ampersand to instruct
Network Server Suite that you wish to retain the original entry instead of using a
substitution variable.
An example of how this works in practice can be seen below:
Text entered as
‘Drives C, D && E are working normally’ would result in
‘Drives C, D & E are working normally’
Understanding Substitution Variables
The basics
In their most basic form, substitution variables are 2-character combinations.
However, they can be of any length and longer variables are often required
when 2 characters are not enough to differentiate one variable from another.
Generally, when a variable is used in a piece of text it is directly followed a
break character such as a space, comma, period and the like. This is
demonstrated in the example below:
‘An error has occurred for Device &Name. Please Investigate.’
where:
&Name equals Backup
produces the following text:
‘An error has occurred for Device Backup. Please investigate.’
In the above example, the use of the period tells Network Server Suite where
the substitution variable ends so that it can correctly insert the replacement text.
Substitution variables can also be placed directly next to each other as shown in
the next example which also demonstrates how substitution variables can be
used in file naming conventions:
‘HECArchive_&DD&MM&YYYY.eca’
where:
&DD equals Day
&MM equals Month
&YYYY equals Year
may produce something similar to:
‘HECArchive_18June2009.eca
Working with Substitution Variables
15-147
Using Substitution Variables within text
In the previous sections, we explored entering substitution variables as
standalone items, but there may be occasions when you need to use a
substitution variable that is immediately followed by more text.
The following example uses variables called ‘&Type’ which returns a value of
‘Run’, and ‘&Name’, which returns a value of ‘Backup’.
‘&Typetime Error Logged for System &Name’
Entered in this format, the following is returned:
‘&Typetime Error Logged for System Backup’
By using this format, entering the variable ‘&Type’ immediately followed by the
word ‘time’, results in an error as Network Server Suite is looking for the
substitution variable ‘&Typetime’, which doesn’t exist.
In order for Network Server Suite to differentiate between where the substitution
variable ends and the text begins, a pipe character followed by a semi-colon ‘|;’
(without quotes) must be inserted between the end of the variable and the start
of the text.
Therefore, by using the previous example:
‘&Type|;time Error Logged for System &Name’ now results in:
‘Runtime Error Logged for System Backup’
The ‘|;’ signifies the end of a variable and that any text that immediately follows
the semi-colon (and up to the next ampersand or break character) should be
inserted as entered. The pipe and semi-colon characters are also used when
adding parameters to substitution variables.
Adding Parameters to Substitution Variables
Parameters can be added to substitution variables to further enhance or
manipulate the values that are substituted in the text.
Parameters are added in the same way as when inserting substitution variables
within text, in that you add a pipe character ‘|’ (without quotes) to the end of the
variable. You can then add further parameters, each separated by ‘|’, finishing
with ‘|;’ when you have entered the full substitution variable with the required
parameters. This combination tells Network Server Suite when to start and end
processing of the substitution variable with parameters.
15- 1 4 8
Network Server Suite
Examples
In the following examples, the substitution variable ‘&UN’ is used to return the
text of ‘Administrator’.
If the basic form of the substitution variable was used:
‘User &UN has logged on’ would return:
‘User Administrator has logged on’
However, by using parameters you can display the user name in upper case. To
do this, add the ‘u’ parameter. (a full list of parameters can be found in
Substitution Variable Parameters). This would affect the previous example as
follows:
‘User &UN|u|; has logged on’ returning:
‘User ADMINISTRATOR has logged on’
To add multiple parameters and change the appearance of the substitution
variable even further you could specify:
‘User &UN|u|+5|; has logged on’.
This substitution variable entry would now return:
‘User ADMIN has logged on’
Note:
This is because the variable now has the parameters of firstly converting the
user name to upper case and then returning just the first five characters of the
user name.
Substitution variables can return either string or numeric values. While
applying each parameter, Network Server Suite checks to see if the variable
result is numeric. If it is, then only numeric parameters can be applied from
that point onwards. To override this behavior and treat the numeric result as
a string, the ‘s’ parameter can be used.
Working with Substitution Variables
15-149
Substitution Variable Parameters
Numeric Parameters
Parameter
Description
Example Value
Variable
Result
f
Returns the fractional part of a
floating-point number
N=1784.23
&N|f|;
0.23
I
Returns the integer part of a floatingpoint number
N=1784.23
&N|i|;
1784
pn
Formats the variable to n decimal
places from 0-9
N=1784.238175
&N|p2|;
1784.24
‘kb’
‘mb’
‘gb’
‘tb’
‘pb’
‘eb’
Converts a number representing
bytes into the respective storage unit.
The result is the decimal
representation of the byte value (i.e.
divided by 1000)
N=10273460156234512340
&N|kb|;
&N|mb|;
&N|gb|;
&N|tb|;
&N|pb|;
&N|eb|;
10273460156234512.34
10273460156234.51234
10273460156.23451234
10273460.15623451234
10273.46015623451234
10.27346015623451234
‘kib’
‘mib’
‘gib’
‘tib’
‘pib’
‘eib’
Converts a number representing
bytes into the respective storage unit.
The result is the binary representation
of the byte value (i.e. divided by 1024)
N=10273460156234512340
&N|kib|;
&N|mib|;
&N|gib|;
&N|tib|;
&N|pib|;
&N|eib|;
10032675933822765.9570
9797535091623.79487991
9567905362.91386218741
9343657.58097056854239
9124.66560641657084218
8.91080625626618246307
+n
+&v
Adds the number n to the variable
result, or adds the value of variable
&v to the result
N1=356
N2=78
&N1|+45|;
&N1|+&N2|;
401
434
-n
-&v
Subtracts the number n to the variable
result, or subtracts the value of
variable &v to the result
N1=356
N2=78
&N1|-45|;
&N1|-&N2|;
311
278
*n
*&v
Multiplies the number n to the variable
result, or multiplies the value of
variable &v to the result
N1=356
N2=78
&N1|*45|;
&N1|*&N2|;
16020
27768
/n
/&v
Divides the number n to the variable
result, or divides the value of variable
&v to the result
N1=356
N2=78
&N1|/45|;
&N1|/&N2|;
7.91111111111111111111
4.56410256410256410256
15- 1 5 0
Network Server Suite
String Parameters
Parameter
Description
Example Value
Variable
Result
t
Trims any spaces from the beginning
and end of the variable result
S=’ Error Occurred ‘
&S|t|;
‘Error Occurred’
tl
Trims any spaces from the beginning
of the variable result
S=’ Example text’
&S|tl|;
‘Example text’
tr
Trims any spaces from the end of the
variable result
S=’Example text‘
&S|tr|;
‘Example text’
l
Converts the variable result to lower
case
S=’Example Text’
&S|l|;
‘example text’
u
Converts the variable result to upper
case
S=’Example text’
&S|u|;
‘EXAMPLE TEXT’
p
Converts the variable result to proper
case. i.e. the first letter of each word
is a capital followed by lower case
characters
S=’EXAMPLE text’
&S|p|;
‘Example Text’
P
The same as the ‘p’ parameter but
preserves any existing capital letters
S=’EXAMPLE text’
&S|P|;
‘EXAMPLE Text’
n-
Removes the first n characters from
the variable result
S=’Example text’
&S|3-|;
‘mple text’
-n
Removes the last n characters from
the variable result
S=’Example text’
&S|-3|;
‘Example t’
n+
Returns the first n characters from the
variable result
S=’Example text’
&S|4+|;
‘Exam’
+n
Returns the last n characters from the
variable result
S=’Example text’
&S|+4|;
‘text’
‘s’-
Removes all characters up to and
including s from the beginning of the
variable result
S=’Example text’
&S|’ple’-|;
‘ text’
-’s’
Removes all characters from s to the
end of the variable result
S=’Example text’
&S|-’ple’|;
‘Exam‘
‘s’+
Returns all characters up to and
including s from the beginning of the
variable result
S=’Example text’
&S|’ple’+|;
‘Example’
+’s’
Returns all characters from s to the
end of the variable result
S=’Example text’
&S|+’test’|;
‘ple text’
s
Instructs Network Server Suite that
the variable result should be treated
as a string
N=1784.23
&N|s|-4|;
‘178’
Working with Substitution Variables
15-151
C
HAPTER
SNMP MONITORING
CHAPTER16
Overview
Simple Network Management Protocol (SNMP) is an "Internet-standard”
protocol for managing devices on IP networks. Devices that typically support
SNMP include routers, switches, servers, workstations, printers and so on.
Each SNMP device is capable of sending ‘traps’, pockets of information that
provide details of current operating status. For example, a network router may
send a message that an invalid logon has been attempted or a printer may send
a message that it is out of paper or that a ink cartridge needs replacing.
Network Server Suite is capable of monitoring these messages and sending an
alert whenever an issue arises.
Requirements:
• A license to use SNMP Traps must be included within the licence code
applied to the system on which SNMP Traps are being monitored.
• Devices to be monitored must exist within Device Manager.
Setting up the SNMP Device in Device Manager
Open the Device Manager component of Network Server Suite and add the
device details as you would normally. See “Manual Addition of Devices” for
more information on how to do this.
Once you have entered the basic system details, select the SNMP Tab from
within the Add Device dialog. (See screenshot overleaf)
Click SNMP Capable to register this device as being able to send SNMP Trap
information. The remaining fields on this display are now enabled.
16- 1 5 2
Network Server Suite
Figure 16.1 Adding SNMP capability to a device
Object ID
If known, enter the unique Object ID code that identifies this SNMP device. If
you do not know it, this field can be left blank as it will not affect the processing
of the SNMP Trap.
Agent Port
This field is set to 161 by default. Only change this value if required by your
operating environment.
Version
This field is set to v1 by default. Only change this value if required by your
operating environment.
Community
This field is set to public by default. Only change this value if required by your
operating environment.
Click OK to add the SNMP Device.
Making a Device a SNMP Trap Target
In order that SNMP traps may be received correctly, a device must be identified
as being able to handle the incoming information and process it into meaningful
data. For this purpose, the Enterprise Server running on the local device must
be defined as a Trap Target.
SNMP Monitoring
16-153
Defining the local Enterprise Server as a SNMP Trap Target:
1 From within Device Manager, double-click on the local device hosting the
Enterprise Server. This is normally the machine on which all of the Network
Server Suite components are installed. The Edit Device dialog is displayed.
2 Select the SNMP tab. In the options page, if not already enabled for this
device, click SNMP Capable. The Traps page is now available
3 Click Device Is A Trap Target so that it is enabled.
4 Unless required by your operating environment, leave the remaining fields on
this page set to their default settings.
5 Click OK to set this device as a SNMP Trap Target.
6 Close the Device Manager.
7 Open the Enterprise Console. Sign-on and from the menu bar click Tools |
Reload Devices. This accepts the changes made in Device Manager so that
they are recognized within Enterprise Console.
Defining SNMP Settings on the SNMP Device
Nearly all SNMP devices, and it varies by device, have a SNMP settings menu
option within their web-interface configuration options. From within these SNMP
Settings, you can identify the IP Address of the Enterprise Server, previously
set-up in Device Manager, as the Trap Target Device.
16- 1 5 4
Network Server Suite
Note:
Please refer to your individual device user reference guides and help to
assist you with entering these settings.
SNMP Monitoring
16-155
C
HAPTER
WORKING WITH MONITORS
CHAPTER17
About the Monitors
Halcyon Central Configuration Manager contains the following monitors:
Event Log Monitors Group (Standard)
Application Event Log/Security Event Log/System Event Log
These monitors provide two key features:
• Monitoring of standard Windows® event logs
• New events in the log can be filtered and alerts raised accordingly. Most
standard ‘server’ type products (such as Exchange, SQL etc) post events
into the standard logs.
Event Log Monitors Group (Additional)
These additional Event Log monitors work in the same way as the standard
event log monitors and can be applied to the event logs added to advanced
versions of Windows®.
Directory Service Event Log
This can be used, for example, to log connection problems between the server
and the global catalog.
File Replication Service Log
File replication failures and events that occur while domain controllers are being
updated with information about sysvol changes are recorded in the file
replication log.
17- 1 5 6
Network Server Suite
DNS Server Log
Events associated with resolving DNS names to Internet Protocol (IP)
addresses are recorded in this log.
Performance Monitors
Windows® Management Instrumentation Monitor
Gives administrators the ability to select the performance indicators they would
like to monitor and set up actions dependent upon user-defined thresholds.
CPU, Disk and Memory Monitor
Gives Administrators the ability to monitor the CPU, Disk and Memory statistical
data.
System Monitors
File & Folder Monitor
Checks for changes in selected folders and/or files. For example, when a new
file is created in a folder or when the size of a file changes. This is useful for
tracking the creation of files sent via FTP and also ensuring that critical files are
not deleted. In addition it can be used to check the date and time stamps of
virus .dat files.
Log File Monitor
Monitors any Windows® log file on any local or networked drive. New events
appearing in the log can be filtered and alerts raised accordingly. Filter Criteria
can include or exclude text or can use Regular Expressions to filter information.
Regular expressions allow you to select specific strings from a set of character
strings.
Note:
The Log File Monitor does not currently support files generated in Unicode.
Services Monitor
The status of services running on a server can already be monitored from the
Windows® event logs. However, this only informs the user if the service starts
and stops correctly.
The Service Monitor periodically checks the status of selected services and
trigger actions when an incorrect status is found. The actions include the ability
to start, stop, pause and resume a service.
Working with Monitors
17-157
TCP Monitors
TCP FTP
Checks the operation of FTP servers by connecting to them and issuing a
command. Alert raised if connection fails or invalid response received to
command.
TCP HTTP
Checks the operation of HTTP servers by connecting to them and requesting a
URL. Alert raised if connection fails or invalid page data returned. Pages can
also be checked for contents. Pages requiring authentication and proxy servers
are supported as are secure addresses (i.e those beginning with HTTPS). In
order for the connection to an HTTPS address to be successful, the required
domain must prefix the user name, for example; halcyon\jsmith, in the
Authentication settings tab.
Note:
Note:
HTTPS re-directs are accepted within the URL string, provided they only require
Basic authentication. Re-directs the use NTLM or Digest are not supported in
this release.
URL Authentication only works with a browser based popup request for user
name and password. HTTP and HTTPS pages that embed this information
are not supported.
If multiple criteria are specified when entering Page Must Include/Page Must
Not Include data, use Enter to separate criteria.
TCP NNTP
Checks the operation of NNTP (news) servers by connecting to them and
issuing a command. Alert raised if connection fails or invalid response received
to command.
TCP Ping
Checks the status of remote devices by sending ICMP ping. The number of ping
attempts per device and success percentage can be specified. Alert raised if
success percentage falls below threshold.
TCP POP3
Checks the operation of POP3 servers by connecting to them and issuing a
command. Alert raised if connection fails or invalid response received to
command.
17- 1 5 8
Network Server Suite
TCP SMTP
Checks the operation of SMTP(mail) servers by connecting to them and issuing
a command. Alert raised if connection fails or invalid response received to
command.
TCP Telnet
Checks the operation of TCP and User Datagram Protocol
Servers (UDP) by connecting to them and optionally issuing a command. Alert
raised if connection fails or invalid response received to command.
TCP/UDP Generic
Checks the operation of TCP and User Datagram Protocol Servers (UDP) by
connecting to them and optionally issuing a command. Alert raised if connection
fails or invalid response received to command.
AIX® Monitors
The following monitors are available for the specific monitoring of AIX® Servers.
AIX® Error Report Monitor
Monitors the output from the AIX® command ERRPT and looks for the
occurrence of specific errors. An alert is raised if the error is found.
Subsystem Monitor
Monitors the status of AIX® subsystems for one of four conditions, raising an
alert if the condition is proven.
Logical Volume Monitor
Monitors the status of Logical Groups, Logical Volumes and Physical Volumes
of the AIX® system. Alerts are raised if the criteria exists, does not exist or
triggers a pre-defined value. The current status of the Logical Groups, Logical
Volumes and Physical Volumes can be displayed when setting the filter criteria.
A test facility is also available that allows you to pre-test the filter with the
current criteria settings and make amendments as required based on the
received results.
Script Monitor
Runs custom AIX® scripts and commands and checks the output against
Regular Expressions.
Working with Monitors
17-159
File & Folder Monitor
Monitors AIX® files and folders for existence, non-existence or for any physical
changes. Alerts are raised if any of the selected conditions are proven or for any
changes in selected folders and/or files. For example, when a new file is created
in a folder or when the size of a file changes. This is useful for ensuring that
critical files are not deleted.
Log File Monitor
Monitors the standard AIX® event logs. New events in the log can be filtered
and alerts raised accordingly. Filter Criteria use Regular Expressions to filter
information. Regular expressions allow you to select specific strings from a set
of character strings.
CPU, Filesystem & Memory Monitor
Gives administrators the ability to monitor the CPU, Filesystem and Memory
statistical data of any AIX® system loaded into the Central Configuration
Manager.
System Monitor
Monitors system load average over a pre-defined time period. Alert raised if
load exceeds, equals or falls short of user-defined criteria.
Can also monitor system up-time of AIX® device.
Process Monitor
Monitors AIX® system processes by a series of processor measurements, such
as CPU Usage %, Cumulative CPU Time and so on. Alerts are raised when a
process triggers a pre-defined value.
Ping Monitor
Checks the status of remote devices by sending an ICMP ping. The number of
ping attempts per device and success percentage can be specified. An alert is
raised if success percentage falls below threshold.
17- 1 6 0
Network Server Suite
Linux® Monitors
The following monitors are available for the specific monitoring of Linux®
Servers.
Linux® Logical Volume Monitor
Monitors the status of Logical Groups, Logical Volumes and Physical Volumes
of the Linux® system. Alerts are raised if the criteria exists, does not exist or
triggers a pre-defined value. The current status of the Logical Groups, Logical
Volumes and Physical Volumes can be displayed when setting the filter criteria.
A test facility is also available that allows you to pre-test the filter with the
current criteria settings and make amendments as required based on the
received results.
Script Monitor
The Script Monitor runs custom Linux® scripts and commands and checks the
output against Regular Expressions.
File & Folder Monitor
Monitors Linux® files and folders for existence, non-existence or for any
physical changes. Alerts are raised if any of the selected conditions are proven
or for any changes in selected folders and/or files.
For example, when a new file is created in a folder or when the size of a file
changes. This is useful for ensuring that critical files are not deleted.
Log File Monitor
Monitors the standard Linux® event logs. New events in the log can be filtered
and alerts raised accordingly. Filter Criteria use Regular Expressions to filter
information. Regular expressions allow you to select specific strings from a set
of character strings.
CPU, Filesystem & Memory Monitor
Gives administrators the ability to monitor the CPU, Filesystem and Memory
statistical data of any Linux® system loaded into the Central Configuration
Manager.
System Monitor
Monitors system load average over a pre-defined time period. Alert raised if
load exceeds, equals or falls short of user-defined criteria.
Can also monitor system up-time of Linux® device.
Working with Monitors
17-161
Process Monitor
Monitors Linux® system processes by a series of processor measurements,
such as CPU Usage %, Cumulative CPU Time and so on. Alerts are raised
when a process triggers a pre-defined value.
Ping Monitor
Checks the status of remote devices by sending an ICMP ping. The number of
ping attempts per device and success percentage can be specified. An alert is
raised if success percentage falls below threshold.
Business Software Monitors
These monitors are not included in the standard release of Network Server
Suite but are fully compatible with the software. These monitors can be
purchased for an additional license fee.
Note:
Please contact; sales@halcyonsoftware.com for more information.
If you have not purchased an additional license, the Business Software
Monitors are not displayed in the Systems view of Central Configuration
Manager.
Web Application Monitor
This monitor is used to check the status of web page data and data within
programs that use websites to display information, for example IBM Blade
Centre information or Lawson M3 (Movex) applications.
Monitor Functions
All Network Server Suite monitors function in the same way. These functions
are described in the following sections.
Sequence Numbers
Note:
During configuration you can be as simple or as complex as you wish. This is
achieved in Enterprise Server Options using sequence numbers that allow
you to monitor multiple conditions for each monitor type, and escalate actions
if required. Filters are run in the numerical order in which they are listed.
Once a filter has been set up for a monitor, the monitor description in the left
pane is emboldened as shown below:
17- 1 6 2
Network Server Suite
Figure 17.1 Monitors with filter applied (shown in bold)
Monitor Dialogs
All monitors use a dialog which contains a main window showing Settings,
Filters and Templates. With the exception of the Event Log monitors, all fields
and options are identical.
Settings
These fields allow you to specify global settings for this monitor. Settings in
these fields override any individual filter settings.
Filters panel
Displays the summary details of any filters set up for the selected monitor. You
can add, edit, delete and hold/release filters from within this panel.
Templates panel
Displays the summary details of any templates currently applied to this monitor.
Working with Monitors
17-163
Figure 17.2 Application Event Log Monitor dialog
Monitor Settings and Startup Options
17- 1 6 4
Option
User Selected Functions
Interval
Specifies how frequently the monitor runs.
This can be set by seconds, minutes hours or
days.
Hold Monitor
(checkbox)
If checked, the monitor does not run. Monitors
can be held by right-clicking on the monitor
from the system list and selecting Hold
Monitor from the pop-up menu.
Startup (radio
buttons) (Event Log
Monitors only)
When Windows® restarts, NSS either ignores
or processes any events since shutdown,
depending on the selection made at these
options.
Network Server Suite
Monitor Log Messages
Error, Informational and Diagnostic messages for all monitors are assigned at
System level. Click at System level in the Systems Tab of the Central
Configuration Manager console.
Figure 17.3 Defining Message Log Settings at System Level
Log Error Messages To
The default setting is Enterprise Server. This means that any error messages
generated by the System Monitors are sent to the Enterprise Console so that
you are aware of them as soon as they occur. A copy is also saved to file.
Informational/Diagnostic Messages
No default settings are defined for these messages. If required, messages can
be saved to file or if you have enabled the Syslog Monitor, messages can be
sent via this method.
Note:
For other options available on this page, please see “System Details
settings” on page 13-116 settings and “Advanced settings” on page 13-117.
Adding Monitor filters
Once you have decided what information from your network enterprise that you
want to filter, or in some cases (more importantly), information that you want to
ignore, you need to define the following:
• what you require to be monitored. (Full monitor descriptions begin on
page 17-172.)
• the frequency with which you you want to check.
From the Monitor Summary dialog, described in the previous section, click Add
Filter, to start the process of adding filters to a selected monitor. The Add Filter
dialog is displayed.
Working with Monitors
17-165
Filter options
Filter page
The filter page is used to determine description and activity settings.
Filter settings
Description
Enter a description to accurately describe the purpose of this filter. The
description is displayed in the summary page at monitor level.
Filter Active settings
Days Active
Select the days on which the filter is active. The default setting is to run on all
days.
Times Active
Select the times of day between which the filter is active. The default setting is
24 hours from 00:00:00 to 23:59:59.
Figure 17.4 Adding Filter Detail - Filter Page
17- 1 6 6
Network Server Suite
Alert page
The Alert page of the Add Filter dialog allows you to specify the default alert
settings for any alert generated by this filter.
Each filter has default alert text assigned, which can be overridden at criteria
level so that the actual alert text is specific to the criteria from which it was
raised.
Alert Type
The alert type that is displayed in the event of any alert being raised by the filter.
This sets the level of severity for any alerts raised by this filter.
Note:
The Alert Type is automatically set to the ‘Error’ default for Event Log
Monitors, although this can be overridden if required.
Alert Text
Substitution Variables can be used with free text to compile the alert text. Use
Reset to return the Alert Text to the default setting if errors have been made
when setting replacement text.
Note:
An example of what the alert text will look like if generated, is displayed as
substitution variables and free text are added in the Alert Text field.
Figure 17.5 Adding Filter Detail - Alert page
Working with Monitors
17-167
Advanced page
The Advanced page provides options to automatically suspend the filter and
reset counters on Startup.
Advanced Settings
Automatically suspend filter
When enabled, this option automatically suspends the filter once triggered
either:
• until the trigger has been filtered a specified number of times within a
determined time frame.
• for an amount of time once the filter has been triggered a specified
number of times. This can be set as Minutes, Hours or Days so that repetitive
alerts are not generated.
The default setting suspends the filter for 30 minutes when triggered once.
Reset Counters on Startup
Click to reset counters when the filter restarts, to ensure any historical alerts still
in the system are ignored.
Figure 17.6 Advanced Filter Option tab
17- 1 6 8
Network Server Suite
Criteria options
You now need to define the monitor specific criteria necessary to generate the
alert.
The Criteria Summary page, displayed when you select the Criteria tab when
adding a filter shows the current criteria setup for this filter.
Criteria Summary page
From this page, you can Add, Edit and Delete Filter criteria.
Each separate criteria is automatically assigned a sequence number when
created. To change the criteria sequence order on this page, use the up/down
arrows on the right-hand side of this display.
Criteria Description and Parameters are also shown as part of this display.
Perform Actions For Each Criteria That Triggers
When setting filter criteria it is possible to state that actions for the first, last or
each criteria that triggers are performed.
If set to First, the first criteria in the list that triggers has its action performed and
subsequent criteria are ignored. If set to Last, every criteria in the list must be
triggered before the action is performed and if set to Each, any criteria that are
triggered in the filter sequence perform their associated actions.
Note:
This option only works for all criteria within a single filter. If you only have one
criterion set per filter, then this option has no affect. Likewise, the option is
not cross filter. Therefore, setting the perform actions for all matching criteria
on one filter does not perform actions set on a separate filter.
Example:
A CPU, Disk and Memory filter has three different levels of criteria set against
the CPU loading to perform three different actions when triggered.
1 If CPU load >= 75% then log only
2 If CPU load >= 85% then Send Enterprise Console Alert
3 If CPU load >= 95% then Send Message
The CPU load hits 94%
With Perform Actions for First Criteria That Triggers enabled, the first
criteria is triggered, the action performed and the filter returns to its monitoring
state.
Working with Monitors
17-169
With Perform Actions for Each Criteria That Triggers enabled, the first
criteria is triggered, the action performed and followed by the subsequent action
as it also matches the criteria.
With Perform Actions for Last Criteria That Triggers enabled, no action for
this filter is performed as the CPU Load percentage did not trigger the last
criteria.
Adding Filter Criteria
On the Filter Criteria summary page, click Add Criteria to open the associated
Monitor Filter Criteria dialog.
Note:
The available pages and field settings are monitor specific and are covered in
detail under each monitor, later in this chapter.
Actions options
The final step in creating a monitor filter is to define the action(s) performed
when the filter criteria is triggered.
The Actions Summary page, displayed when you select the Actions tab when
adding a filter shows the current action(s) setup for this filter.
Actions Summary page
From this page, you can Add, Edit and Delete Filter actions.
Each separate action is automatically assigned a sequence number when
created.
Action Description and Parameters are also shown as part of this display.
Adding Filter Actions
Click Add Action, to start the process of adding filters to a selected monitor.
The Select Action dialog is displayed. Specify the action to take.
• Control Service: allows NSS to start/stop/pause/resume the selected
Windows® service. This option also caters for dependency and stops or
restarts associated services if required.
• Execute Command: allows you to specify a command, e.g. to run an OS
Command or a bespoke script.
• Execute DTS Package: allows you to execute a specialized DTS package. A
DTS package is a set of related objects (connections, tasks, and workflows)
that can be used to access, transform and manipulate data from a wide
range of sources including text files and relational databases.
• Log only (no Action): stores the alert in the Server.hlf file but takes no other
action.
• Send Enterprise Console Alert: sends the alert to any defined Enterprise
Console.
17- 1 7 0
Network Server Suite
• Send Message: sends an e-mail message or can send a SMS message if a
GSM Data Terminal is installed.
• Send Network Message: sends a message to any single or multiple
services.
• Send SNMP Trap: sends an SNMP Trap to a specified device.
Figure 17.7 Selecting Filter Action
Setting the order of actions
Once the filter actions have been determined it is possible to re-sequence the
order in which they are processed. This is done by the use of the two arrows at
the right hand side of the Actions dialog.
To move a selected action, click either the up or down arrow to move one unit in
the chosen direction. If either the top or bottom action is selected, only the arrow
in which the action may be moved is available.
When the all the required actions have been added, click OK to complete the
creation of the filter and return to the main Central Configuration Manager
display.
Remember to save the settings prior to exiting the Central Configuration
Manager.
Working with Monitors
17-171
Event Log Monitors
Event Log monitors are used to monitor the standard Windows® Application,
Security and System event logs. New events sent to the logs can be filtered and
alerts raised accordingly. Most standard ‘server’ based products such as
Exchange and SQL post events into the standard logs. In some instances, you
may want to monitor if an event has not been received during a specified time.
It is also possible to setup and monitor the contents of any text-based log file
(including fixed-format and delimited) for any new entries, raising alerts
accordingly.
These standard monitors comprise:
• Application Event Log Monitor
• Security Event Log Monitor
• System Event Log Monitor
There are also three additional Event log monitors:
• Directory Service Event Log Monitor
• DNS Server Event Log Monitor
• File Replication Event Log Monitor
Examples of Use
• Failed backups
• SMTP protocol errors
• Specific event sources, categories, event IDs, event user or text
• Service status monitoring
• Security violations
Using the Browse utility
When adding criteria for Event Log monitor filters, a Browse facility lets you
view both summary and detail information about existing entries in each of the
three log types.
17- 1 7 2
Network Server Suite
Figure 17.8 Event log Viewer
By default, the 100 most recent entries are displayed. Use the Get Next button
to retrieve the specified number of Event Log Records. Click Details to display
the Event Properties dialog showing detailed information for the event log. From
this dialog you can move through further log in the summary display by using
the up and down arrows. When finished viewing the detail information, click OK
to return to the main Event Log Viewer display.
Click Select while highlighting an event log on this display to automatically
populate the filter criteria fields with the detailed log information from the
selected event log.
Example Application Event Log Monitor filter
This example filter checks that any events sent to the Windows® Application
Event Log do not contain the words ‘Backup failed’. This is useful if you have a
device on which regular backups are performed as you can then ensure that
these are completing successfully. If the filter is triggered, an alert is sent to the
Enterprise Console (although you can specify any action that suits your
circumstances).
1 From the Systems panel of the Central Configuration Manager, select the
system to which the monitor filter is applied and expand the view so that the
monitors are displayed.
2 Select the Application Event Log Monitor and click Add Filter to display
the Add Filter Detail dialog.
3 Enter a Description of ‘Check for Backup Failures’. Leave other fields on this
page as the default settings.
Working with Monitors
17-173
4 Select the Criteria tab in the left navigation pane of the Add Filter Detail
dialog and click Add Criteria.
5 In the Event Type Settings clear the Information, Warning, Audit Failure
and Audit Success settings.
6 Leave all comparison values as ‘=’. In the Event Source Value field, enter the
name of the system. This name is used in the alert message.
7 Enter ‘None’ as the Event Category Value.
8 Enter ‘9999’ as the Event ID Value.
9 Enter ‘System’ as the Event User Value.
10Using wildcards to capture any instance of backup failure, enter ‘*Backup
Failed*’ as the Event Message Value and click OK.
11Select the Actions tab in the left navigation pane of the Add Filter Detail
dialog and click Add Action.
12Select the Send Enterprise Console Alert action. Click OK to open the
Console Action dialog. Leave the fields as their default settings and click OK.
13On the Add Filter Detail dialog, click OK to create the filter, which is then
displayed in the System Filter panel for the Application Event Log monitor.
14Select File | Save Settings. The filter is now active within the monitor.
Performance Monitors
These monitors allow you to monitor generic performance counters. These
monitors can report on on installed applications, for example, if Microsoft®
Exchange Server is installed and diagnostics logging configured within
Exchange, Network Server Suite can monitor and alert you as required.
The performance monitors comprise of:
• CPU, Disk and Memory Monitor
• Windows Management Instrumentation (WMI) Monitor
CPU, Disk & Memory Monitor
The CPU, Disk and Memory monitor is used to check common attributes of
system performance.
Common examples of CPU, Disk and Memory Monitors
• CPU Load (%Processor Time, %Privilege Time, %User Time)
• Disk Space (%Available, %Used
• Memory (Page File Used/Available %, Physical Memory Used/Available %)
17- 1 7 4
Network Server Suite
Using the Performance Data utility
Prior to setting any criteria for this monitor it is advisable to use the Performance
Data button, on the Performance Criteria dialog to display the current
Performance Data for the chosen system.
Figure 17.9 Current System Performance Data dialog (for drive data)
Use the tabs in the left-hand navigation panel of this display to view the relevant
performance data of each attribute of the selected system. Data can be
displayed in Mb or Kb. Use the Refresh button to periodically update the display
or set the Auto Refresh setting.
When you have the required information, click OK to close the Performance
Data dialog.
Example CPU, Disk & Memory Monitor filter
This example filter checks that the disk space available on the C:\ drive of a
given system remains above 25%. If the filter is triggered, an alert is sent to the
Enterprise Console (although you can specify any action that suits your
circumstances).
1 From the Systems panel of the Central Configuration Manager, select the
system to which the monitor filter is applied and expand the view so that the
monitors are displayed.
Working with Monitors
17-175
2 Select the CPU, Disk & Memory Monitor and click Add Filter to display the
Add Filter Detail dialog.
3 Enter a Description of ‘C Drive Disk Space Available >25%’. Leave other
fields on this page as the default settings.
4 Select the Criteria tab in the left navigation pane of the Add Filter Detail
dialog and click Add Criteria.
5 From the Performance Group choice menu, select Disk. The entry in the
Drive field automatically defaults to the C:\ Drive.
6 From the Performance Type choice menu, select Drive Space Available
%.
7 Set the Trigger Value to > 25% and click OK.
8 Select the Actions tab in the left navigation pane of the Add Filter Detail
dialog and click Add Action.
9 Select the Send Enterprise Console Alert action. Click OK to open the
Console Action dialog. Leave the fields as their default settings and click OK.
10On the Add Filter Detail dialog, click OK to create the filter, which is then
displayed in the System Filter panel for the CPU, Disk & Memory monitor.
11Select File | Save Settings. The filter is now active within the monitor.
WMI (Windows® Management Instrumentation) Monitor
WMI is a set of specifications from Microsoft® for consolidating the
management of devices and devices and applications in a network from
Windows® computing systems. WMI is installed on all computers with
Windows® ME, 2000, XP, Vista, Windows 7 or Server 2003/2008 installed.
WMI provides users with information about the status of local or remote
computer systems. It also supports such actions as the configuration of security
settings, setting and changing system properties, setting and changing
permissions for authorized users and user groups, assigning and changing
drive labels, scheduling processes to run at specific times, backing up the
object repository and enabling or disabling error logging.
Note:
Alerts are raised if the specified instance exists, does not exist or if the criteria
triggers at a pre-determined value.
When setting WMI filter criteria, if a Specified Instance is not identified, a
wildcard query must be entered in order to be able to proceed.
Using the WMI Browse Utility
When adding criteria for WMI monitor filters, a Browse facility lets you view
both performance and non-performance information about various Windows®
system properties.
17- 1 7 6
Network Server Suite
Figure 17.10 WMI Browse utility
From the drop-down choice menus, select whether you wish to monitor for
performance on non performance and then select the system property that you
wish to monitor against.
Select specific counters and, if available, instances to drill-down into extra detail
of the system property or select all counters and instances.
Click Add to display the WMI data for your selection in the bottom panel of this
dialog together with a performance chart, showing the current data for your
selection in real-time.
Click Clear to remove the current selection from the dialog ready for a new
selection to be made.
Use Refresh to manually update the display or set the auto-refresh settings to
automatically update the data.
When you are ready to make your selection, highlight the required detail line in
the WMI Data panel of this dialog and click Select. The criteria is automatically
added to the filter.
Working with Monitors
17-177
You can now use the Test facility on the WMI Criteria dialog to check your
criteria against either the local or a remote system.
WMI Advanced Criteria settings
When adding certain types of WMI Performance criteria, the Advanced Tab can
be used to enter instances that if found by the filter can be ignored, to avoid
triggering an unnecessary alert.
To specify instances that can be ignored:
Note:
1 Having set the WMI Criteria, select the Advanced tab.
If the Ignore the following instances box is greyed out, you are unable to use
this feature for the WMI criteria selected.
2 Click Add to open the Add Instance Name dialog.
3 Enter the name of the Instance that you wish to be ignored if encountered.
Click OK.
4 Continue to add instances or click OK to save the changes and close the
Criteria dialog.
WMI Reporting
The WMI monitor is capable of generating reports based on 7 pre-defined and
25 user-defined criteria.
See “Reporting” on page 19-244 for more information on this functionality.
Example WMI Monitor filter
This example filter checks that the number of inactive terminal service sessions
is not equal to or greater than five. An alert is generated if the number of
inactive terminal service sessions matches or exceeds this threshold.
1 From the Systems panel of the Central Configuration Manager, select the
system to which the monitor filter is applied and expand the view so that the
monitors are displayed.
2 Select the WMI Monitor and click Add Filter to display the Add Filter Detail
dialog.
3 Enter a Description of ‘Inactive Terminal Service Sessions >5’. Leave other
fields on this page as the default settings.
4 Select the Criteria tab in the left navigation pane of the Add Filter Detail
dialog and click Add Criteria.
5 Click Browse to open the Windows® Management Instrumentation dialog.
6 Using Performance as the mode, select Terminal Services from the
parameters choice menu.
7 Ensure Select Counters From List is enabled and select Inactive
Sessions. Click Add.
17- 1 7 8
Network Server Suite
8 From the WMI Data panel, highlight the current line entry and click Select.
The data is now transferred into the WMI Criteria dialog.
9 Change the Trigger Value from ‘=’ to ‘>=’ and change the associated value
to 5. Click OK.
10Select the Actions tab in the left navigation pane of the Add Filter Detail
dialog and click Add Action.
11Select the Send Enterprise Console Alert action. Click OK to open the
Console Action dialog. Leave the fields as their default settings and click OK.
12On the Add Filter Detail dialog, click OK to create the filter, which is then
displayed in the System Filter panel for the WMI monitor.
13Select File | Save Settings. The filter is now active within the monitor.
System Monitors
These monitors allow you to monitor system status. Advanced logical
monitoring can be used within File & Folder monitor to alert when specific
actions external to Network Server Suite do not write to the application logs
(have or have not taken place).
These monitors comprise:
• File & Folder Monitor
• Service Monitor
Examples of File & Folder Monitors
• Anti-virus definition downloads
• Existence based on date, time, size, etc.
• Search for wildcard files and folders
Examples of Service Monitors
• Check if (Windows®) services are running
• Check startup type
• Check logon account details
File & Folder Monitor
The File and Folder monitor allows you to browse both local and remote devices
for a specific folder and check for any changes.
Working with Monitors
17-179
Figure 17.11 File/Folder Criteria dialog
By clicking
, the Browse For Folder dialog opens. This allows you to select
any folder from the devices listed in the Device Manager and drill down to select
subsequent folders as you would in the usual Windows® operating environment.
Use Results From Previous Criteria
The Use Results From Previous Criteria option can be used to perform actions
on the results generated by the previous criteria in this monitor. When this
option is enabled, the Search Path field changes to Variable.
Enter the variable ‘&EN’ to represent the Matched Name of the previous criteria.
This option is useful for scenarios such as ensuring that a series of files have
been received by FTP correctly. On receipt of the final file, an action can be
taken to copy all files to another folder.
Search Parameters
Search parameters allow you to specify to alert whether the File/Folder exists or
doesn’t exist and also set trigger actions. Trigger actions are used to determine
at which point the alert is raised.
• First Matching - The alert is triggered on the first matching instance found
• Each Matching - Separate alerts are triggered for each matching instance
found
• All - A single alert is triggered with the the information of upto 50 matching
instances found
17- 1 8 0
Network Server Suite
Scan Filter parameters
Scan filters allow you to Ignore files/folders of specific types, and/or Include or
Exclude specific filter criteria on which to search. Filters can be applied to files/
folders that fall into the following categories:
• Read Only
• System
• Temporary
• Hidden
• Archive
• Compressed
Testing
When you have entered the criteria that you require, you can use the Test
button to assess the validity of the data, and if necessary make any changes
prior to putting the filter ‘Live’.
Note:
See “Local v Remote Testing” on page 17-188 for more information.
Thresholds
When adding filter criteria for the File and Folder Monitor, size and time-stamp
threshold information can be applied to further refine the criteria requirements.
From the left-hand Criteria menu tab (displayed when adding new criteria),
select Thresholds.
You can now enter File or Folder size criteria, and/or Timestamps indicating
when the file or folder was last created, modified or accessed.
Example File/Folder Monitor filter
This File/Folder monitor filter checks that the critical system.ini file has not been
deleted.
1 From the Systems panel of the Central Configuration Manager, select the
system to which the monitor filter is applied and expand the view so that the
monitors are displayed.
2 Select the File & Folder Monitor and click Add Filter to display the Add
Filter Detail dialog.
3 Enter a Description of ‘Check for System.ini file’. Leave other fields on this
page as the default settings.
4 Select the Criteria tab in the left navigation pane of the Add Filter Detail
dialog and click Add Criteria.
5 Enter the Search Path of where the system.ini file is resident. (This is usually
C:\Windows).
6 Change the Alert If parameter to ‘File/Folder Does Not Exist’.
7 In the Scan Filters section override the Include Filter option of ‘*.*’ with
‘system.ini’.
Working with Monitors
17-181
8 Click Test (ensure that this is carried out of the local system) to determine
that the file currently exists (the criteria does not trigger). Close the Test
dialog and click OK to add the criteria detail.
9 Select the Actions tab in the left navigation pane of the Add Filter Detail
dialog and click Add Action.
10Select the Send Enterprise Console Alert action. Click OK to open the
Console Action dialog. Leave the fields as their default settings and click OK.
11On the Add Filter Detail dialog, click OK to create the filter, which is then
displayed in the System Filter panel for the File/Folder monitor.
12Select File | Save Settings. The filter is now active within the monitor.
Log File Monitor
The Log File Monitor allows you to check log files for any character string or text
within any standard Windows log or text file, whether stored locally or on a
network drive to which you have access.
Log File Monitors can raise alerts for each new line of text that is added to the
file that matches either the include/exclude filter or Regular Expression criteria.
Figure 17.12 Log File Criteria
Note:
17- 1 8 2
The default setting is ‘Include “*”.’ If left as this setting once the filter is
created, a new alert is generated for each new line added to the selected log
file.
Network Server Suite
Selecting Log Files
To select a log file to monitor, you can either type the directory path and log file
name (wildcards ‘*’ and ‘?’ are accepted) directly into the Log File field, or use
the ‘3 dot’ button to open the ‘Browse for Folder’ dialog.
From here you can navigate to the required directory path. Once the folder
containing the log file(s) that you wish to monitor has been located, click OK.
The path is now entered in the Log File field.
Note:
Click Browse to view the most recent entries in each log file within the selected
directory.
When entering or selecting a path, any file extensions that have been
entered in the “Excluded file extensions” parameter within the Advanced Tab
are omitted from the search.
Figure 17.13 Browse for Log Files
The contents of the first log file in the chosen directory path are displayed
automatically. Use the drop-down choice box to select a different log file from
those listed. Once selected, click Refresh to view the contents of this file.
Selecting data to include, exclude or use as a Regular Expression
Clicking on any line within the Log File Viewer dialog automatically selects it as
the Include/Exclude filter details or the Regular Expression detail (depending on
which option was selected prior to the Browse button being used).
Note:
When using Include/Exclude filter details, the criteria is entered into the
option in which the cursor was last positioned prior to the Browse option
being selected.
Alternatively, simply type the required text/character string into the relevant filter
setting. Wildcards ‘*’ and ‘?’ can be used to construct the required string.
Working with Monitors
17-183
Use Enter to add multiple lines of text to the filter. When entering multiple lines
of text, be aware that an alert is raised if any of the text is found/not found in the
selected log file(s).
Advanced Settings
Advanced settings within the Log File Monitor allow you to exclude files with
specific extensions and specify whether any entries that have been generated
since the monitor was last stopped, are ignored or processed.
Excluded file extensions
Use this field to enter the extension of any files that you wish the Log File
Monitor to ignore when browsing or searching for files. File extensions that are
included by default are:
• .exe
• .dll
• .bin
• .res
• .ico
• .wmv
• .avi
• .xvid
• .identcache
Startup
Allows you to choose whether the monitor processes or ignores all entries
generated since the monitor was last stopped.
Error if Folder Path Not found
You can raise an alert if the entered search path is not found when the filter is
run. Check this field so that if the Search Path does not exist an alert is sent to
the Enterprise Console. if this option is not checked, any search path errors are
ignored.
Once the filter details have been selected or entered, click OK.
Note:
The Log File Monitor does not currently support files generated in Unicode.
Example Log File Monitor Filter
The following filter checks the Enterprise Console Log named Console.hfl and
sends a text alert if text is found in the log file that indicates that no response
has been received from the server for 1 minute.
17- 1 8 4
Network Server Suite
1 From the Systems panel of the Central Configuration Manager, select the
system to which the monitor filter is applied and expand the view so that the
monitors are displayed.
2 Select the Log File Monitor and click Add Filter to display the Add Filter
Detail dialog.
3 Enter a Description of ‘Check Enterprise Console Log For Error’. Leave
other fields on this page as the default settings.
4 Select the Criteria tab in the left navigation pane of the Add Filter Detail
dialog and click Add Criteria. The Log File Criteria dialog is displayed.
5 Click the ‘3 Dot’ button next to the Log File field. From the Browse for Folder
dialog, navigate to the following path: C:\Program Files\Halcyon\Enterprise
Console\Logs\Console.hlf (this assumes that you followed a typical
installation of Network Server Suite). Click OK.
6 Returning to the Log File Criteria dialog, ensure that the cursor is positioned
in the Include Filter field and remove the existing entry of ‘*’.
7 Select the Actions tab in the left navigation pane of the Add Filter Detail
dialog and click Add Action.
8 Select the Send Instant Alert Message action. Click OK to open the
Message Action dialog.
9 Ensure that the intended recipient is listed in the Recipients field and that
SMS is selected as the Message Type (assumes Recipients exist in Instant
Alert Address Book and that they have a mobile number configured). Click
OK to confirm the action.
10On the Add Filter Detail dialog, click OK to create the filter, which is then
displayed in the System Filter panel for the Log File Monitor.
11Select File | Save Settings. The filter is now active within the monitor.
Service Monitor
The Service monitor allows you to ensure that critical services, such as AntiVirus software, are running on the selected device.
A useful feature of this is that it automatically allows you to control the service
dependent on the result of the alert. For example, if the monitor detects that the
Anti-Virus software has stopped running, the monitor can automatically restart
the service without the need for your interaction.
You can also start (or stop) any generic service by overtyping the service from
within the Display Name field and using ‘*’ as a wildcard. For example, typing
‘HAL*’ would perform the specified action on any service beginning with the
characters HAL.
When setting the Control Service action for a service monitor, you have the
choice of using the service from the criteria (i.e. if a service has stopped, this is
the service you require starting) or using another of the listed services to
perform the required action.
Working with Monitors
17-185
Using the Service Browse Utility
When adding criteria for Service monitor filters, a Browse facility lets you view
the list of services that are currently running on the device being monitored.
Selecting a service from within this display automatically populates the criteria
detail.
Figure 17.14 Browse Services utility
Example Service Monitor filter
This Service monitor filter checks anti-virus software and restarts it if it has
stopped.
1 From the Systems panel of the Central Configuration Manager, select the
system to which the monitor filter is applied and expand the view so that the
monitors are displayed.
2 Select the Service Monitor and click Add Filter to display the Add Filter
Detail dialog.
3 Enter a Description of ‘Check and Restart Anti-Virus’. Leave other fields on
this page as the default settings.
17- 1 8 6
Network Server Suite
4 Select the Criteria tab in the left navigation pane of the Add Filter Detail
dialog and click Add Criteria.
5 Either select the anti-virus service from the Display Name choice menu or
click Browse, highlight the anti-virus service from those services listed and
click Select. The Service Name, Status and Startup Type fields on the
Criteria dialog are automatically populated.
6 In the Service Thresholds section of the Criteria dialog, set the Status
operator to ‘=’ and the value as ‘Stopped’.
7 In the left navigation pane of the Criteria page, click Alert.
8 Enable the Override Filter Default option and change the Alert Text to
‘Anti-Virus software service had stopped. Automatically restarted by Halcyon
NSS’. Click OK.
9 Select the Actions tab in the left navigation pane of the Add Filter Detail
dialog and click Add Action.
10Select the Send Enterprise Console Alert action. Click OK to open the
Console Action dialog. Leave the fields as their default settings and click OK.
11On the Add Filter Detail dialog, click OK to create the filter, which is then
displayed in the System Filter panel for the Service monitor.
12Select File | Save Settings. The filter is now active within the monitor.
TCP Monitors
These monitors allow you to monitor typical network services to port level,
internally and externally.
All monitors check a specific IP address or host name with optional port,
username and password.
TCP monitors comprise:
• TCP FTP monitor
• TCP HTTP monitor
• TCP NNTP monitor
• TCP Ping monitor
• TCP POP3 monitor
• TCP SMTP monitor
• TCP Telnet monitor
• TCP/UDP Generic monitor
These features can be used to monitor and check any combination of
applications as long as they support access by host name or IP address and
port number.
All TCP monitors have a default interval setting of 5 minutes between
connections.
Working with Monitors
17-187
Testing TCP Monitors
All TCP monitors have Test facilities that give you the ability to try the current
settings prior to creating the filter. In most instances, a command and trigger
value can be applied so that you can fine-tune the criteria to your requirements.
Local v Remote Testing
Test options allow you to run the tests from either the local or remote device. If
you run the test locally, you are testing from the machine on which you are
creating the filter, typically the machine on which Central Configuration
manager is installed. If you run the test remotely, it is run from server agent on
the device for which the filter is intended.
Example:
By creating a TCP HTTP filter on a remote system to find an instance of
‘monitoring’ on www.halcyonsoftware.com, you would expect both the local and
remote tests to return the same result.
However, the remote system may be behind a firewall, or connect via a proxy
server, in which case the local test would still pass but the remote test would
fail, and you would have to reconfigure the filter criteria (for that remote device
only) to provide authentication /proxy server details in order for the criteria to
return the desired result.
It is therefore good practice to test both locally and remotely on all filters where
the option is available to ensure that the results are as expected.
Detailed Logging
Activate detailed logging to receive a comprehensive report of the test results.
17- 1 8 8
Network Server Suite
Figure 17.15 Detailed Logging of Test Results
Test Results
When using the Command and Trigger Value Options it is always advisable to
use the test facility to ensure that you have applied the correct trigger value to
the command being used in order to generate the expected result. The following
two examples demonstrate the different results obtained when using two
different settings:
Example One:
In the following example, the test on the SMTP monitor is to ensure that the
Response code 250 is not received from the HELO Command.
When Test is used the following result is obtained:
Working with Monitors
17-189
In the above example, an alert IS NOT have been raised as the response was
250 and the trigger value was set at <> (not equal to). Any other result, other
than 250 would have resulted in an alert being raised.
Example Two:
In the following example, the test on the SMTP monitor is to ensure that the
Response code 250 is received from the HELO Command.
When Test is used, the following result is obtained:
An alert IS raised as the response was again 250 but the trigger value in this
instance was set at = (equals). Therefore the correct response of 250 triggered
the criteria and raised an alert. Any response other than 250 would have passed
this test.
17- 1 9 0
Network Server Suite
TCP Monitor Options
Please refer to the following table for the possibilities available for each TCP
Monitor:
TCP Monitor
Test
Facility?
Command?
Trigger
Values?
Options
FTP



HTTP



NNTP



PING



POP3



=, <>
SMTP



=, >, >=, <,
<=, <>
Telnet



=, >, >=, <,
<=, <>
UDP/Generic



=, <>
=, >, >=, <,
<=, <>
=, >, >=, <,
<=, <>
Example TCP Ping Monitor filter
The following instructions create a simple TCP Ping Monitor filter.
1 From the Systems panel of the Central Configuration Manager, select the
system to which the monitor filter is applied and expand the view so that the
monitors are displayed.
2 Select the TCP Ping Monitor and click Add Filter to display the Add Filter
Detail dialog.
3 Enter a Description of ‘Ping Connection’. Leave other fields on this page as
the default settings.
4 Select the Criteria tab in the left navigation pane of the Add Filter Detail
dialog and click Add Criteria.
5 Enter the IP Address of the device to which the ping connection is sent.
6 Keep the system defaults and click Test to experiment with these settings.
Close the Test dialog and make any changes to the default settings that are
more suited to your own operational environment. Re-test if required. When
finished, click OK.
Working with Monitors
17-191
7 Select the Actions tab in the left navigation pane of the Add Filter Detail
dialog and click Add Action.
8 Select the Send Enterprise Console Alert action. Click OK to open the
Console Action dialog. Leave the fields as their default settings and click OK.
9 On the Add Filter Detail dialog, click OK to create the filter, which is then
displayed in the System Filter panel for the TCP Ping monitor.
10Select File | Save Settings. The filter is now active within the monitor.
Example TCP HTTP Monitor filter
The following instructions create a simple TCP HTTP Monitor filter.
1 From the Systems panel of the Central Configuration Manager, select the
system to which the monitor filter is applied and expand the view so that the
monitors are displayed.
2 Select the TCP HTTP Monitor and click Add Filter to display the Add Filter
Detail dialog.
3 Enter a Description of ‘HTTP Web Page Check’. Leave other fields on this
page as the default settings.
4 Select the Criteria tab in the left navigation pane of the Add Filter Detail
dialog and click Add Criteria.
Note:
5 Enter the actual URL of the web page that you wish to monitor or the IP
Address of the web server on which the page is hosted.
Using generic pages such as www.google.com can lead to a denial of service
as the host machine may believe that it the subject of a malicious attack.
6 If required, enter text that either must or must not be included in the
returned page text. Click Test to experiment with these settings. Close the
Test dialog and make any changes to the settings and text (if entered). Retest if required. When finished, click OK.
7 Select the Actions tab in the left navigation pane of the Add Filter Detail
dialog and click Add Action.
8 Select the Send Enterprise Console Alert action. Click OK to open the
Console Action dialog. Leave the fields as their default settings and click OK.
9 On the Add Filter Detail dialog, click OK to create the filter, which is then
displayed in the System Filter panel for the TCP HTTP monitor.
10Select File | Save Settings. The filter is now active within the monitor.
AIX® Monitors
Forming the AIX® Server Manager, these monitors allow you to monitor aspects
of any AIX® system located on your network and loaded into Network Server
Suite via the Device Manager. The AIX® monitors work in the same way as the
Windows® monitors, in that you create filters, set criteria and specify actions.
17- 1 9 2
Network Server Suite
Each filter has default alert text assigned, which can be overridden at criteria
level so that the actual alert text is specific to the criteria from which it was
raised.
Figure 17.16 AIX® Monitors
There are ten types of AIX® Monitor available:
• AIX® Error Report Monitor
• Subsystem Monitor
• Logical Volume Monitor
• Script Monitor
• File & Folder Monitor
• Log File Monitor
• CPU, Filesystem & Memory Monitor
• System Monitor
• Process Monitor
• Ping Monitor
Working with Monitors
17-193
AIX® Error Report Monitor
The AIX® Error Report Monitor checks the output from the ERRPT command
and looks for specific errors occurring within the report.
To run the ERRPT command type:
ERRPT -A
at a valid input point. Output is produced which is similar in appearance to that
shown below:
Note:
In order to set meaningful filter criteria it is useful to have familiarity with the
contents of the ERRPT output.
Adding filter criteria allows you to apply a trigger value from a pre-defined list of
common variables, set a comparator and enter a suitable description for the
trigger value. Click Add Parameter to open the Add Error Report Parameter
dialog from where these settings can be entered.
17- 1 9 4
Network Server Suite
Figure 17.17 Add Error Report Parameter dialog
Click Browse to open the Error Reports dialog that shows the current error
report contents.
Figure 17.18 Browse AIX Error Report details
Click on an item from within this report and the full details are shown in the
Details pane of this dialog. Click Select to select this error as the parameter.
Once the error report parameter details have been specified, click OK to add
the parameter to the criteria for this filter.
Working with Monitors
17-195
Subsystem Monitor
The AIX® Subsystem Monitor is a simple monitor that checks the AIX®
subsystems for one of five conditions:
• Subsystem Exists
• Subsystem Does Not Exist
• Subsystem Is Operative
• Subsystem Is Inoperative
• Subsystem Is Stopping
Subsystems can be specified by Name or by Group. An alert is raised when the
chosen condition is met for the specified Subsystem Name or Group.
Figure 17.19 Subsystem Monitor criteria
Click Browse to open the Subsystems dialog, listing all the subsystems and
status information. Click on a subsystem to highlight and then click Select. The
Subsystem Parameters for this criteria are automatically populated with the
data from the selected subsystem.
17- 1 9 6
Network Server Suite
Figure 17.20 Browse AIX Subsystems
Once the Subsystem parameters have been defined for the criteria, click Test
to ensure that the returned results are the same as would be expected if the
filter was live.
Click OK to define and confirm the subsystem parameters as criteria for this
filter.
Logical Volume Monitor
AIX® uses a Logical Volume Manager (LVM) to manage, at a logical level, all of
the file systems and directories created within an AIX® system. The LVM maps
data between logical and physical storage, allowing data to be discontiguous,
span multiple disks, flexible and dynamically expanded.
Working with Monitors
17-197
The Halcyon AIX® Logical Volume Monitor checks the Volume Group, Physical
Volumes and Logical Volumes of the AIX® system as defined in the LVM.
• Volume Groups: The containers for both the Physical and Logical Volumes.
• Physical Volumes: The Physical Volumes are segmented into physical
Partitions
• Logical Volumes: The Logical Volumes are logical partitions logged to the
physical partitions.
Filter criteria change depending on the type of logical volume being monitored.
However for each Monitor Type you can specify if a logical volume exists, does
not exist or if a performance type triggers user-defined criteria.
Figure 17.21 AIX Logical Volume Criteria
When setting filter criteria, click Display Status to open the Logical Volume
Status window which displays the individual properties of each of the three
Logical Volume monitor types.
Once the criteria has been set, click Test to ensure that the returned results are
the same as would be expected if the filter was live.
Click OK to define the entered parameters as criteria for this filter.
Practical Examples
1 A stale physical partition is a physical partition which contains data that you
cannot use. Monitoring for Stale Physical Partitions alerts you when this
happens so that you can take correcting action to update the stale partitions
so that they contain the same information as valid physical partitions.
2 Monitoring for Free Physical Partitions can alert you to when a low level of
space remains on your AIX® system
17- 1 9 8
Network Server Suite
Figure 17.22 Logical Volume Status (using Display Status)
Script Monitor
The AIX® Script Monitor is a high-level monitor that runs a user-defined script or
command against a Regular Expression.
The entered script must exist and must use the absolute path, not a relative
path.
Alerts are raised if the selected Regular Expression is matched.
Figure 17.23 Script Monitor criteria
Working with Monitors
17-199
Once the criteria has been set, click Test to ensure that the returned results are
the same as would be expected if the filter was live.
Click OK to define the entered parameters as criteria for this filter.
AIX® File & Folder Monitor
The AIX® File and Folder monitor allows you to browse both local and remote
devices for a specific folder and check for any changes.
Figure 17.24 AIX® File/Folder Criteria dialog
By clicking
, the Select Folder dialog opens. This allows you to select any
folder from the AIX® device and drill down to select subsequent folders.
Search Parameters
Search parameters allow you to specify to alert whether the File/Folder exists or
does not exist. Check the Include Sub-Folders option to ensure that the AIX®
sub-folders are included in any search.
Trigger actions are used to determine at which point the alert is raised and can
be set against events happening against individual files, folders or file or folder.
17- 2 0 0
Network Server Suite
• First Matching - The alert is triggered on the first matching instance of the
File, Folder or File or Folder found
• Each Matching - Separate alerts are triggered for each matching instance
found for each File, Folder or File or Folder found.
Scan Filter parameters
Scan filters allow you to include or exclude specific filter criteria on which to
search.
Include/Exclude Filters
Include and Exclude Filters allow you to enter a list of files or folders to include
or exclude from the scan. Wildcards (*) can be used as a full or part
replacement for file/folder name characters. When inserting file/folder names,
use carriage return to generate a new line on which the next file/folder name
can be entered.
Permission Filters
Permission Filters allow you to specify the access rights to the files/folders for
which you are scanning. The permission filters are split into three types:
• User: The owner of the file or folder
• Group: The group to which the owner belongs
• Other: Everyone else
Permission levels allow to you define, within each type, whether the file can be
read, written or executed, by specifying:
• Granted: Permission allowed
• Not Granted: Permission denied
• Both: Permission is not checked
Thresholds
When adding filter criteria for the File and Folder Monitor, size and time-stamp
threshold information can be applied to further refine the criteria requirements.
From the left-hand Criteria menu tab (displayed when adding new criteria),
select Thresholds.
Note:
You can now enter File or Folder size criteria, and/or Timestamps indicating
when the file or folder was last created, modified or accessed.
When entering User Filters of User Name and Group Name, you must enter
the actual names and not their numerical representations.
Error Reporting if the Search Path is Not Found
You can raise an alert if the entered search path is not found when the filter is
run. From the Criteria menu tab, select Advanced. Ensure that the Error If
Search Path Is Not Found option is checked. If the Search Path does not exist
an alert is sent to the Enterprise Console. if this option is not checked, any
search path errors are ignored.
Working with Monitors
17-201
Testing
When you have entered the criteria that you require, click Test to assess the
validity of the data, and if necessary make any changes prior to putting the filter
‘Live’.
Click OK to define the entered parameters as criteria for this filter.
Log File Monitor
The AIX® Log File Monitor discovers and monitors log files. When criteria are
added, the monitor searches the Unix Syslog configuration file (/etc/syslog.conf)
and examines the /var/log/directory and its subdirectories for plain files. A
typical discovery routine may include the following log files:
/var/log/daemon
/var/log/kern
/var/log/mail
/var/log/messages
/var/log/secure
/var/log/sudo
/var/log/syslog
/var/log/user
although many more log file examples are supplied as default.
Figure 17.25 AIX® Log File Criteria
17- 2 0 2
Network Server Suite
Log File Monitors can raise alerts for each new line of text that is added to the
file that matches both the comparison and Regular Expression criteria.
Click Browse to view the most recent entries in each log file. Selecting an entry
from within this dialog, automatically enters it as the Regular Expression criteria
for the current filter.
Figure 17.26 Browse for AIX® Log Files
Click OK to define the entered parameters as criteria for this filter.
CPU, Filesystem & Memory Monitor
The AIX® CPU, Filesystem and Memory Monitor operates in the same way as
the Windows® CPU, Disk & Memory Monitor and is used to check common
attributes of system performance.
Working with Monitors
17-203
Performance Data
Prior to setting any criteria for this monitor it is advisable to click the
Performance Data button to display the current Performance Data.
Figure 17.27 AIX® Performance Data (Drives)
The three tabs show relevant information for each category, with Drive
information available for each mounted drive. From this information it is possible
to set filters with more accurate criteria than would otherwise have been
possible.
CPU Monitor
The CPU monitor is used to monitor either the load or the spare capacity of the
machine’s CPU. Use the Performance Data feature to obtain a current
'snapshot' of the system on which threshold decisions can be made.
An alert is triggered when the entered percentage is reached or equalled.
Filesystem Monitor
The Filesystem monitor is used to monitor both Drive Space and I-Node usage.
An I-Node is a data structure on a file system on Linux® and other Unix-like
operating systems that stores all the information about a file except its name
and its actual data.
A data structure is a way of storing data so that it can be used efficiently.
Different types of data structures are suited to different types of applications,
and some are highly specialized for specific types of tasks.
17- 2 0 4
Network Server Suite
Drives and I-Nodes can be monitored by physical or percentage space available
or by space used.
An alert is triggered when the selected criteria value for the required drive and
Performance Type is reached. Alternatively, alerts can be raised if the drive
exists or does not exist.
Memory Monitor
The AIX® Memory monitor is used to monitor different aspects of the memory
usage of the AIX® device. Physical memory, virtual memory, page file, memory
load and buffers used can all be monitored and alerts raised when specific
trigger value targets are reached.
When you have entered the criteria that you require, click Test to assess the
validity of the data, and if necessary make any changes prior to putting the filter
‘Live’.
Click OK to define the entered parameters as criteria for this filter.
System Monitor
Load averages are a simple measure of the number of processes that are ready
to run but required to wait for access to the CPU. A load average of more than
two on a system with a single CPU, for example, would indicate that the system
is unable to keep up with the processes that are being submitted.
Load average represents the load averages over 1, 5, and 15-minute intervals
prior to a server's transmission. The load averages are multiplied by 10 to
represent the value in decimal format.
An alert is sent when the trigger value for the condition is breached.
Figure 17.28 System Criteria for Filter
Working with Monitors
17-205
System Uptime
The System monitor can also be used to monitor System Uptime which displays
the length of time that the system has been running. Trigger values for this type
of criteria can be set for Seconds, Minutes or Hours. A filter can be set up with
an alert action that is triggered in the event of the system stopping.
When you have entered the criteria that you require, click Test to assess the
validity of the data, and if necessary make any changes prior to putting the filter
‘Live’.
Click OK to define and confirm the entered parameters as criteria for this filter.
Process Monitor
The Process Monitor is used to monitor all processes running on the AIX®
system. Processes can be monitored by Process Name, Process Owner or
Process Identification Number (PID).
Figure 17.29 AIX Process Criteria
17- 2 0 6
Network Server Suite
The type of measurement used to evaluate the process can be any one of the
following:
• CPU Usage %
• Cumulative CPU Time (default)
• Elapsed Time
• Number of Processes
• Process Physical Memory Used
• Process Physical Memory Used %
• Virtual Memory Size
To determine which processes are currently running, click Browse to display
the Processes dialog. This dialog displays the processes running on the AIX®
together with detailed information regarding their current system usage.
Figure 17.30 Browse AIX® Processes
Working with Monitors
17-207
Double-click (or single-click followed by Select) on any process in this window
to select it for use in the main criteria window.
Alerts are generated if the process exists or does not exist. Additionally, alerts
can be generated if the criteria triggers against the selected process when it
exceeds, equals or falls beneath a certain size.
When you have entered the criteria that you require, click Test to assess the
validity of the data, and if necessary make any changes prior to putting the filter
‘Live’.
Click OK to define the entered parameters as criteria for this filter.
AIX® Ping Monitor
The AIX® Ping Monitor checks the status of remote devices by sending ICMP
ping. The number of ping attempts per device and success percentage can be
specified. An alert is raised if success percentage falls below threshold.
Figure 17.31 AIX Ping Monitor Criteria
Host/Address
Enter the IP Address of the ping destination device.
Ping Timeout: - Milliseconds(s)
This setting defines the time period after which the ping times out. Default
setting is 2000.
Ping Attempts
Defines how many attempts are made (default 4) before the alert is raised.
17- 2 0 8
Network Server Suite
Success Percentage
This setting gives an indication of ping success rate (default 100%).
Time-to-Live
This setting defines for how long the ping is active (default setting is 128
milliseconds). Substitution Variables can be used to form the basis of the alert
text.
When you have entered the criteria that you require, click Test to assess the
validity of the data, and if necessary make any changes prior to putting the filter
‘Live’.
Click OK to define the entered parameters as criteria for this filter.
AIX® Actions
Only three actions are available when creating AIX® Monitor filters:
• Execute Command
• Send Enterprise Console Alert
Note:
• Send Instant Alert Message
See “Adding Filter Actions” on page 17-170 for more information on these
three action types.
AIX® Templates
Note:
These work in the same way as the templates applied to Windows® Servers.
Please see “AIX® Templates” on page 18-228 for more information.
AIX® Reporting
It is not currently possible to generate reports based upon AIX® system activity.
Working with Monitors
17-209
Linux® Monitors
The Linux® Server Manager, contains monitors that allow you to monitor
aspects of any licensed Linux® system located on your network and loaded into
Network Server Suite via the Device Manager. The Linux® monitors work in the
same way as the Windows® monitors, in that you create filters, set criteria and
specify actions.
Figure 17.32 Linux® Monitors
There are eight Linux® Monitors available:
• Linux® Logical Volume Monitor
• Script Monitor
• File & Folder Monitor
• Log File Monitor
• CPU, Filesystem & Memory Monitor
• System Monitor
• Process Monitor
• Ping Monitor
Linux® Logical Volume Monitor
Linux® uses a Logical Volume Manager (LVM) to manage, at a logical level, all
of the file systems and directories created within the Linux® system. The LVM
maps data between logical and physical storage, allowing data to be
discontiguous, span multiple disks, flexible and dynamically expanded.
17- 2 1 0
Network Server Suite
Figure 17.33 Linux Logical Volume Criteria
The Halcyon Linux® Logical Volume Monitor checks the Volume Group,
Physical Volumes and Logical Volumes of the Linux® system as defined in the
LVM.
• Volume Groups: The containers for both the Physical and Logical Volumes.
• Physical Volumes: The Physical Volumes are segmented into physical
partitions
• Logical Volumes: The Logical Volumes are logical partitions logged to the
physical partitions.
Filter criteria performance types change depending on the type of logical
volume being monitored. However for each monitor type you can specify if a
logical volume exists, does not exist or if a performance type triggers userdefined criteria.
When setting filter criteria, it is possible to use Display Status to open the
Logical Volume Status window which displays the individual properties of each
of the three Logical Volume monitor types.
When you have entered the criteria that you require, click Test to assess the
validity of the data, and if necessary make any changes prior to putting the filter
‘Live’.
Click OK to define the entered parameters as criteria for this filter.
Working with Monitors
17-211
Script Monitor
The Linux® Script Monitor is a high-level monitor that runs a user-defined script
or command against a Regular Expression.
The entered script must exist and must use the absolute path, not a relative
path.
Alerts are raised if the selected Regular Expression is matched.
When you have entered the criteria that you require, click Test to assess the
validity of the data, and if necessary make any changes prior to putting the filter
‘Live’.
Click OK to define the entered parameters as criteria for this filter.
File & Folder Monitor
The Linux® File and Folder monitor allows you to browse both local and remote
devices for a specific folder and check for any changes.
By clicking
, the Select Folder dialog opens. This allows you to select any
folder from the Linux® device and drill down to select subsequent folders.
Search Parameters
Search parameters allow you to specify to alert whether the File/Folder exists or
does not exist. Check the Include Sub-Folders option to ensure that the Linux®
sub-folders are included in any search.
Trigger actions are used to determine at which point the alert is raised and can
be set against events happening against individual files, folders or file or folder.
• First Matching - The alert is triggered on the first matching instance of the
File, Folder or File or Folder found
• Each Matching - Separate alerts are triggered for each matching instance
found for each File, Folder or File or Folder found.
17- 2 1 2
Network Server Suite
Figure 17.34 Linux® File/Folder Criteria dialog
Scan Filter parameters
Scan filters allow you to include or exclude specific filter criteria on which to
search.
Include/Exclude Filters
Include and Exclude Filters allow you to enter a list of files or folders to include
or exclude from the scan. Wildcards (*) can be used as a full or part
replacement for file/folder name characters. When inserting file/folder names,
use carriage return to generate a new line on which the next file/folder name
can be entered.
Permission Filters
Permission Filters allow you to specify the access rights to the files/folders for
which you are scanning. The permission filters are split into three types:
• User: The owner of the file or folder
• Group: The group to which the owner belongs
• Other: Everyone else
Permission levels allow to you define, within each type, whether the file can be
read, written or executed, by specifying:
• Granted: Permission allowed
• Not Granted: Permission denied
• Both: Permission is not checked
Working with Monitors
17-213
Thresholds
When adding filter criteria for the File and Folder Monitor, size and time-stamp
threshold information can be applied to further refine the criteria requirements.
From the left-hand Criteria menu tab (displayed when adding new criteria),
select Thresholds.
Note:
You can now enter File or Folder size criteria, and/or Timestamps indicating
when the file or folder was last created, modified or accessed.
When entering User Filters of User Name and Group Name, you must enter
the actual names and not their numerical representations.
Error Reporting if the Search Path is Not Found
You can raise an alert if the entered search path is not found when the filter is
run. From the Criteria menu tab, select Advanced. Ensure that the Error If
Search Path Is Not Found option is checked. If the Search Path does not exist
an alert is sent to the Enterprise Console. if this option is not checked, any
search path errors are ignored.
Testing
When you have entered the criteria that you require, click Test to assess the
validity of the data, and if necessary make any changes prior to putting the filter
‘Live’.
Click OK to define the entered parameters as criteria for this filter.
Log File Monitor
The Linux® Log File monitor discovers and monitors log files. When criteria are
added, the monitor searches the Unix Syslog configuration file (/etc/syslog.conf)
and examines the /var/log/directory and its subdirectories for plain files.
Use Browse to view the most recent entries in each log file. Selecting an entry
from within this dialog, automatically enters it as the Regular Expression criteria
for the current filter.
17- 2 1 4
Network Server Suite
Figure 17.35 Browse for Linux® Log Files
Log File Monitors raise alerts for each new line of text that is added to the file
that matches both the comparison and Regular Expression criteria.
When you have entered the criteria that you require, click Test to assess the
validity of the data, and if necessary make any changes prior to putting the filter
‘Live’.
Click OK to define the entered parameters as criteria for this filter.
CPU, Filesystem & Memory Monitor
The Linux® CPU, Filesystem and Memory monitor operates in the same way as
the Windows® CPU, Disk & Memory monitor and is used to check common
attributes of system performance.
Performance Data
Prior to setting any criteria for this monitor it is advisable to click Performance
Data to display the current Performance Data.
Working with Monitors
17-215
Figure 17.36 Linux® Performance Data
The three tabs show relevant information for each category, with Drive
information available for each mounted drive.
CPU Monitor
This monitor is used to monitor either the load or the spare capacity of the
machine’s CPU. Use the Performance Data feature to obtain a current
'snapshot' of the system on which threshold decisions can be made.
From this information it is possible to set filters with more accurate criteria than
would otherwise have been possible.
An alert is triggered when the entered percentage is reached or equalled.
Filesystem Monitor
The Filesystem monitor is used to monitor both Drive Space and I-Node usage.
An I-Node is a data structure on a file system on Linux® and other Unix-like
operating systems that stores all the information about a file except its name
and its actual data.
A data structure is a way of storing data so that it can be used efficiently.
Different types of data structures are suited to different types of applications,
and some are highly specialized for specific types of tasks.
Drives and I-Nodes can be monitored by physical or percentage space available
or by space used.
17- 2 1 6
Network Server Suite
An alert is triggered when the selected criteria value for the required drive and
Performance Type is reached. Alternatively, alerts can be raised if the drive
exists or does not exist.
Memory Monitor
The Linux® Memory monitor is used to monitor different aspects of the memory
usage of the Linux® device. Physical memory, virtual memory, page file,
memory load and buffers used can all be monitored and alerts raised when
specific trigger value targets are reached.
Test
Use the Test facility (available from the Performance Criteria dialog) to test the
filter with the current criteria and make any adjustments as required, based
upon the results returned, prior to setting the actual filter.
Click OK to define the entered parameters as criteria for this filter.
System Monitor
Load averages are a simple measure of the number of processes that are ready
to run but required to wait for access to the CPU. A load average of more than
two on a system with a single CPU, for example, would indicate that the system
is unable to keep up with the processes that are being submitted.
Load average represents the load averages over 1, 5, and 15-minute intervals
prior to a server's transmission. The load averages are multiplied by 10 to
represent the value in decimal format.
An alert is sent when the trigger value for the condition is breached.
Figure 17.37 System Criteria for Filter
Working with Monitors
17-217
System Uptime
The Linux® System monitor can also be used to monitor System Uptime which
displays the length of time that the system has been running. A filter can be set
up with an alert action that is triggered in the event of the system stopping.
When you have entered the criteria that you require, click Test to assess the
validity of the data, and if necessary make any changes prior to putting the filter
‘Live’.
Click OK to define the entered parameters as criteria for this filter.
Process Monitor
The Linux® Process monitor is used to monitor all processes running on the
system. Processes can be monitored by Process Name, Process Owner or
Process Identification Number (PID).
The type of measurement used to evaluate the process can be any one of the
following:
• Cumulative CPU Time (default)
• CPU Usage %
• Number of Processes
• Process Physical Memory Used %
• Process Physical Memory Used
• Elapsed Time
• Virtual Memory Size
To determine which processes are currently running, use Browse to display the
Processes dialog. This Processes dialog displays the processes running on the
Linux® system together with detailed information regarding their current system
usage. Double-click any process in this window to select it for use in the main
criteria window.
Alerts are generated if the process exists or does not exist. Additionally, alerts
can be generated if the criteria triggers against the selected process when it
exceeds, equals or falls beneath a certain size.
When you have entered the criteria that you require, click Test to assess the
validity of the data, and if necessary make any changes prior to putting the filter
‘Live’.
Click OK to define the entered parameters as criteria for this filter.
17- 2 1 8
Network Server Suite
Figure 17.38 Browse Linux® Processes
Linux® Ping Monitor
The Linux® Ping Monitor checks the status of remote devices by sending ICMP
ping. The number of ping attempts per device and success percentage can be
specified. An alert is raised if success percentage falls below threshold.
Figure 17.39 Linux Ping Monitor criteria
Working with Monitors
17-219
Host/Address
Enter the IP Address of the ping destination device.
Ping Timeout: - Milliseconds(s)
This setting defines the time period after which the ping times out. Default
setting is 2000.
Ping Attempts
Defines how many attempts are made (default 4) before the alert is raised.
Success Percentage
This setting gives an indication of ping success rate (default 100%).
Time-to-Live
This setting defines for how long the ping is active (default setting is 128
milliseconds). Substitution Variables can be used to form the basis of the alert
text.
When you have entered the criteria that you require, click Test to assess the
validity of the data, and if necessary make any changes prior to putting the filter
‘Live’.
Click OK to define the entered parameters as criteria for this filter.
Linux® Actions
Only three actions are available when creating Linux® Monitor filters:
• Execute Command
• Send Enterprise Console Alert
Note:
• Send Instant Alert Message
See “Adding Filter Actions” on page 17-170 for more information on these
three action types.
Linux® Templates
Note:
These work in the same way as the templates applied to Windows® Servers.
Please see “Linux® Templates” on page 18-234 for more information.
Linux® Reporting
It is not currently possible to generate reports based upon Linux® system
activity.
17- 2 2 0
Network Server Suite
C
HAPTER
TEMPLATES
CHAPTER18
Overview
Templates are designed to provide the same level of monitoring across a
number of similar devices by applying a set of user-defined filters with a singleclick. This greatly reduces set-up time and ensures all systems are covered by
at least a basic level of monitoring. Should you need to make a system-wide
change at a later date, a single update covers all systems using the template.
Network Server Suite comes supplied with seven default monitoring templates
for Windows® that cover the majority of everyday scenarios that your
organization is likely to encounter. A reporting template is also included.
Additionally, there are two pre-configured templates that can be applied to AIX®
devices and two templates each to cover the RED HAT® and SUZE® versions
of the Linux® operating system.
Templates are created using the Central Configuration Manager and can then
be quickly applied to all systems. More than one template can be applied to a
system at any one time and it is also possible to have individual filters running
alongside the template filters on any system.
Basic templates which monitor devices for routine issues and concerns such as
low disk space, memory and so on can be deployed enterprise-wide. Business
critical machines may require the application of an ‘advanced’ template
additionally covering, for example, application event log and service monitoring.
Additionally, it is also possible to create and apply templates to cover the
generic performance reporting of systems in your enterprise. See “Reporting
Template” for more information on creating and applying reporting templates.
Templates
18-221
Using the default templates
Launch the Central Configuration Manager and select the Templates tab.
Figure 18.1 Network Server Suite Templates
The following Windows® monitor templates are defined:
• “Active Directory template”
• “Exchange Server (Performance) template”
• “Exchange Server (Services) template”
• “M3 Monitoring template”
• “Server Performance (Advanced) template”
• “Server Performance (Standard) template”
• “SQL Server template”
• “Terminal Services template”
18- 2 2 2
Network Server Suite
The following AIX® templates are defined:
• “AIX System Monitoring (Standard) Template”
• “AIX® System Monitoring (Advanced) Template”
The following Linux® templates are defined:
• “RED HAT System Monitoring (Standard) Template”
• “RED HAT System Monitoring (Advanced) Template”
• “SUSE System Monitoring (Standard) Template”
• “SUSE System Monitoring (Advanced) Template”
The Reporting template:
• Reporting (Performance)
is also included. See “Reporting Template” on page 19-250 for more
information.
Windows® Templates
Active Directory template
Active Directory is a centralized and standardized system that automates
network management of user data, security, and distributed resources, and
enables interoperation with other directories. Active Directory is designed
especially for distributed networking environments.
The Active Directory template contains seven generic performance filters:
• Counter(DRA Inbound Bytes Total/sec) Trigger(>=1)
• Counter(DRA Inbound Object Updates Remaining in Packet) Trigger(>=5)
• Counter(DRA Outbound Bytes Total/sec) Trigger(>=10240)
• Counter(DRA Pending Replication Synchronizations) Trigger(>=50)
• Counter(DS Name Cache hit rate) Trigger(<=99)
• Counter(LDAP Client Sessions) Trigger(>=250)
Note:
• Counter(NTLM Authentications) Trigger(>=100)
All actions for each of the above filters within this template are set to a default
of sending an alert to the Enterprise Console. You must manually change this
setting if you require an alternative action to be taken upon the generation of
an alert.
Templates
18-223
Exchange Server (Performance) template
This template covers the performance of the Exchange Server, including mail
server, email client and groupware applications (such as shared calendars).
The Exchange Server
performance filters:
(Performance)
template
contains
six
generic
• Counter(Active User Count) Trigger(>=200)
• Counter(Messages/Sec) Trigger(>=10)
• Counter(Work Queue Length) Trigger(>=10)
• Instance(_Total) Counter(Average Delivery Time) Trigger(=10,000,000)
• Instance(_Total) Counter(Send Queue Size) Trigger(>=20)
Note:
• Instance(_Total) Counter(Send Queue Size) Trigger(>=10)
All actions for each of the above filters within this template are set to a default
of sending an alert to the Enterprise Console. You must manually change this
setting if you require an alternative action to be taken upon the generation of
an alert.
Exchange Server (Services) template
This template covers services used by Exchange Server.
The Exchange Server (Services) template contains seven system service filters:
• Service(Microsoft® Exchange IMAP4) Status(<> ‘Started’) Startup(=
Automatic) Logon A/C(=’Local System’)
• Service(Microsoft® Exchange Information Store) Status(<>’Started’)
Startup(=’Automatic’) Logon A/C(=’Local System’)
• Service(Microsoft® Exchange Management) Status(<>’Started’) Startup (=
‘Automatic’) Logon A/C(=’Local System’)
• Service(Microsoft® MTA Stacks) Status(<>’Started’) Startup(= ‘Automatic’)
Logon A/C(=’Local System’)
• Service(Microsoft® Exchange POP3) Status(<>’Started’) Startup
(=’Automatic’) Logon A/C(=’Local System’)
• Service(Microsoft® Exchange Routing Engine) Status(<>’Started’) Startup (=
‘Automatic’) Logon A/C(=’Local System’)
Note:
18- 2 2 4
• Service(Microsoft® System Attendant) Status(<>’Started’) Startup (=
‘Automatic’ Logon A/C(=’Local System’)
All actions for each of the above filters within this template are set to a default
of sending an alert to the Enterprise Console. You must manually change this
setting if you require an alternative action to be taken upon the generation of
an alert.
Network Server Suite
M3 Monitoring template
Note:
The M3 Monitoring template includes monitors for Lawson M3 applications and
uses Web Application Monitor, Service and TCP HTTP monitoring components.
If you have not purchased the Web Application Monitor, this templates only
includes the Service and TCP HTTP elements.
The M3 Monitoring template contains the following components:
Web Application Monitor
• Checking for looping M3 auto job - URL(http://127.0.0.0.1:6788/
showlog?addr=127.0.0.1&port6101) Timeout(5 Secs) TriggerType(first
Matching) TriggerObject(Table)
• High severity for NEWS page - URL(http://127.0.0.1:6666/news) Timeout(5
Secs) TriggerType(Each Matching) TriggerObject(Row)
• Instances of an interactive job for a specified user - URL(http://
127.0.0.1:6666/) Timeout(15 Secs) TriggerType(Each Matching)
TriggerObject(Row)
• Interaction auto job validation - URL(http://127.0.0.1:6666/) Timeout(15
Secs) TriggerType(First Matching) TriggerObject(Row)
• Interactive job CPU% Check - URL(http://127.0.0.1:6666/) Timeout(15 Secs)
TriggerType(Each Matching) TriggerObject(Row)
• ServerView Counters Check - URL(http://127.0.0.1:6666/) Timeout(15 Secs)
TriggerType(First Matching) TriggerObject(Row)
• ServerView Dumplogs in NEWS page - URL(http://127.0.0.1:6666/news)
Timeout(5 Secs) TriggerType(Each Matching) TriggerObject(Row)
• ServerView Status Check - URL(http://127.0.0.1:6666/) Timeout(15 Secs)
TriggerType(Each Matching) TriggerObject(Row)
• Supervisor Check - URL(http://127.0.0.1:6666/) Timeout(25 Secs)
TriggerType(First Matching) TriggerObject(Table)
• Transaction Server Check - URL(http://127.0.0.1:6666/) Timeout(25 Secs)
TriggerType(First Matching) TriggerObject(Table)
Service Monitor
• Backup Exec Services Started - Service(Backup Exec Remote Agent for
Windows Systems) Status(<>’Started’)
• MapGenServer - Service(MapGenServer) Status(<>’Started’)
• MecService - eCollaborator - Service(MECServer) Status(<>’Started’)
• Print Spooler Service <> Started - Service(printSpooler) Status(<>’Started’)
• StreamServe - Production - Service(StreamServe Prod) Status(<>’Started’)
Templates
18-225
• StreamServe - Standard environment - Service(StreamServe zSTD)
Status(<>’Started)
• StreamServe - Test - Service(StreamServe Test) Status(<>’Started’)
• StreamServe Repository Server <> Started - Service(StreamServe
Repository Server) Status(<>’Started’)
TCP HTTP Monitor
Note:
• Check CONNECT Site - URL(http://192.168.219.14:8780/) Timeout(5 Secs)
Include(‘News’) NotInclude(‘404’)
All actions for each of the above filters within this template are set to a default
of sending an alert to the Enterprise Console. You must manually change this
setting if you require an alternative action to be taken upon the generation of
an alert.
Server Performance (Advanced) template
The Server Performance Advanced template covers the more technical aspects
of server performance aside from those covered by the basic CPU, Disk and
Memory template.
The Server Performance Advanced template contains six generic performance
filters:
• Memory Available Bytes - Counter(Available Mbytes) Trigger(<=50)
• Memory Committed Bytes - Counter(% Committed Bytes In Use) Trigger(>=
90)
• Memory Pages per second – Counter(Pages/sec) Trigger(>=20)
• Physical Disk - %Disk Time - Instance(_Total) Counter(% Disk Time)
Trigger(>= 99)
• Processor - % Processor Time - Instance(_Total) Counter(% Processor
Time) Trigger(>=90)
Note:
18- 2 2 6
• System Processor Queue Length - Counter(Processor Queue Length)
Trigger(>= 10)
All actions for each of the above filters within this template are set to a default
of sending an alert to the Enterprise Console. You must manually change this
setting if you require an alternative action to be taken upon the generation of
an alert.
Network Server Suite
Server Performance (Standard) template
The Server Performance (Standard) template provides three summary
performance filters to cover standard performance indicators of servers and
workstation devices.
• CPU Utilization - Group(CPU) Instance(_Total) Type(% Processor Time)
Trigger(>= 98%)
• Disk space C drive - Group(Disk) Instance(C) Type(Drive Space Used %)
Trigger(>= 75%)
Note:
• Physical memory – Group(Memory) Type(Physical Memory Used %) Trigger
(>= 90%)
All actions for each of the above filters within this template are set to a default
of sending an alert to the Enterprise Console. You must manually change this
setting if you require an alternative action to be taken upon the generation of
an alert.
SQL Server template
The SQL Server template contains fifteen generic performance filters to monitor
the integrity and performance of an SQL Server device.
• SQL Server Monitoring & Performance - Counter(Buffer cache hit ratio)
Trigger(<=99)
• SQL Server Monitoring & Performance - Counter(Connection Memory (KB))
Trigger(>=20480)
• SQL Server Monitoring & Performance - Counter(Full Scans/sec)
Trigger(>=50)
• SQL Server Monitoring & Performance - Counter(Optimizer Memory (KB))
Trigger(>=10240)
• SQL Server Monitoring & Performance - Counter(Page Splits/sec)
Trigger(>=10)
• SQL Server Monitoring & Performance - Counter(SQL Compilations/sec)
Trigger(>=5)
• SQL Server Monitoring & Performance - Counter(Stolen Pages)
Trigger(>=10000)
• SQL Server Monitoring & Performance - Counter(Table Lock Escalations/
sec) Trigger(>=10)
• SQL Server Monitoring & Performance - Counter(User connections)
Trigger(>=100)
• SQL Server Monitoring & Performance - Instance(Database)
Counter(Number of Deadlocks/sec) Trigger(>1)
• SQL Server Monitoring & Performance - Instance(First Triggered Instance)
Counter(Cache Hit Ratio) Trigger (<=75)
Templates
18-227
• SQL Server Monitoring & Performance - Instance(_Total) Counter(Active
Transactions) Trigger(>=10)
• SQL Server Monitoring & Performance - Instance(_Total) Counter(Cache Hit
Ratio) Trigger(<=75)
• SQL Server Monitoring & Performance - Instance(_Total) Counter(Percent
Log Used) Trigger(>= 75)
Note:
• SQL Server Monitoring & Performance - Instance =(_Total)
Counter(Transactions/sec) Trigger(>= 25)
All actions for each of the above filters within this template are set to a default
of sending an alert to the Enterprise Console. You must manually change this
setting if you require an alternative action to be taken upon the generation of
an alert.
Terminal Services template
The Terminal Services template provides six generic performance filters:
• Terminal Services Performance - Counter(Active Sessions) Trigger(>=2)
• Terminal Services Performance - Counter(Inactive Sessions) Trigger(>=2)
• Terminal Services Performance - Instance(Console) Counter(% Processor
Time) Trigger(>=20)
• Terminal Services Performance - Instance(Console) Counter(Total Bytes)
Trigger (>=100,000)
• Terminal Services Performance - Instance(Console) Counter(Total
Timeouts) Trigger(>=100,000)
Note:
• Terminal Services Performance - Instance(Console) Counter(Total Errors)
Trigger(>=5)
All actions for each of the above filters within this template are set to a default
of sending an alert to the Enterprise Console. You must manually change this
setting if you require an alternative action to be taken upon the generation of
an alert.
AIX® Templates
AIX System Monitoring (Standard) Template
The AIX® System Monitoring (Standard) template contains filters covering all of
the AIX® Monitors with the exception of the System Monitor.
The following filters are defined:
AIX® Error Report Monitor
This contains the following two filters:
18- 2 2 8
Network Server Suite
• Hardware Errors - Errpt(Class=H)
• Software Errors - Errpt(Class=S)
Subsystem Report Monitor
This contains the following six filters:
• Critical Subsystem (inetd) Does Not Exist - Subsystem Does Not Exist(inetd)
• Critical Subsystem (inetd) is Inoperative - Subsystem is Inoperative(inetd)
• Critical Subsystem (qdaemon) Does Not Exist - Subsystem Does Not
Exist(qdaemon)
• Critical Subsystem (qdaemon) is Inoperative - Subsystem is
Inoperative(qdaemon)
• Critical Subsystem (syslogd) Does Not Exist - Subsystem Does Not
Exist(syslogd)
• Critical Subsystem (syslogd) is Inoperative - Subsystem is Inoperative(inetd)
Logical Report Monitor
This contains the following two filters:
• Alert when Quorum is set to Off When Disk Mirroring is active (rootvg)
Measure(Quorum) Trigger(=0)
• Volume Group (rootvg) Does Not Exist - Volume Group rootvg Does Not
Exist
Script Monitor
This contains the following two filters:
• Check for Failed Logins - Script(/var/lib/halcyon/logfails.sh denied)
• Check for Missing or Removed Disks - Script(lspv missing | removed)
File & Folder Monitor
This contains the following seven filters:
• File (/etc/aixmibd.conf) Has Changed - File(/etc/aixmibd.conf) Trigger(Exists)
• File (/etc/inetd.conf) Has Changed - File(/etc/inetd.conf) Trigger(Exists)
• File (/etc/inittab) Has Changed - File(/etc/inittab) Trigger(Exists)
• File (/etc/profile) Has Changed - File(/etc/profile) Trigger(Exists)
• File (/etc/security/login.cfg) Has Changed - File(/etc/security/login.cfg)
Trigger(Exists)
• File (/etc/sendmail.cf) Has Changed - File(/etc/sendmail.cf) Trigger(Exists)
• File (/var/spool/cron/crontabs/root) Has Changed - File(/var/spool/cron/
crontabs/root) Trigger(Exists)
Templates
18-229
Log File Monitor
This contains the following two filters:
• Monitor for Failed Logins - LogFile(/var/lib/halcyon/failedlogins.log
Expression(.*)
• Monitor for New Entries in Cron Log - LogFile(/var/adm/cron/log)
Expression(.*)
CPU, Filesystem and Memory Monitor
This contains the following sixteen filters:
• Filesystem (/) Disk Space Used >=80% - Group(Filesystem) Volume(/)
Type(UsedPercent) Trigger(>=80%)
• Filesystem (/) Does Not Exist - Group(Filesystem) Volume(/) Trigger(Does
Not Exist)
• Filesystem (/) Inode Used >=90% - Group(Filesystem) Volume(/)
Type(UUsedInodesPercent) Trigger(>=90%)
• Filesystem (/home) Disk Space Used >=80% - Group(Filesystem) Volume(/
home) Type(UsedPercent) Trigger(>=80%)
• Filesystem (/home) Does Not Exist - Group(Filesystem) Volume(/home)
Trigger(Does Not Exist)
• Filesystem (/home) Inode Used >=90% - Group(Filesystem) Volume(/home)
Type(UUsedInodesPercent) Trigger(>=90%)
• Filesystem (/tmp) Disk Space Used >=80% - Group(Filesystem) Volume(/
tmp) Type(UsedPercent) Trigger(>=80%)
• Filesystem (/tmp) Does Not Exist - Group(Filesystem) Volume(/tmp)
Trigger(Does Not Exist)
• Filesystem (/tmp) Inode Used >=90% - Group(Filesystem) Volume(/tmp)
Type(UUsedInodesPercent) Trigger(>=90%)
• Filesystem (/usr) Disk Space Used >=80% - Group(Filesystem) Volume(/usr)
Type(UsedPercent) Trigger(>=80%)
• Filesystem (/usr) Does Not Exist - Group(Filesystem) Volume(/usr)
Trigger(Does Not Exist)
• Filesystem (/usr) Inode Used >=90% - Group(Filesystem) Volume(/usr)
Type(UUsedInodesPercent) Trigger(>=90%)
• Filesystem (/var) Disk Space Used >=80% - Group(Filesystem) Volume(/var)
Type(UsedPercent) Trigger(>=80%)
• Filesystem (/var) Does Not Exist - Group(Filesystem) Volume(/var)
Trigger(Does Not Exist)
• Filesystem (/var) Inode Used >=90% - Group(Filesystem) Volume(/var)
Type(UUsedInodesPercent) Trigger(>=90%)
• Sustained CPU >95% - Group(CPU) CPU(0) Type(Load) Trigger(>95%)
18- 2 3 0
Network Server Suite
Process Monitor
This contains the following eight filters:
• Critical Process (biod) Does Not Exist - Type(Process By Name)
Process(biod) Trigger(DoesNotExist)
• Critical Process (cron) Does Not Exist - Type(Process By Name)
Process(cron) Trigger(DoesNotExist)
• Critical Process (errdemon) Does Not Exist - Type(Process By Name)
Process(errdemon) Trigger(DoesNotExist)
• Critical Process (inetd) Does Not Exist - Type(Process By Name)
Process(inetd) Trigger(DoesNotExist)
• Critical Process (portmap) Does Not Exist - Type(Process By Name)
Process(portmap) Trigger(DoesNotExist)
• Critical Process (qdaemon) Does Not Exist - Type(Process By Name)
Process(qdaemon) Trigger(DoesNotExist)
• Critical Process (syncd) Does Not Exist - Type(Process By Name)
Process(syncd) Trigger(DoesNotExist)
• Critical Process (writesrv) Does Not Exist - Type(Process By Name)
Process(writesrv) Trigger(DoesNotExist)
Ping Monitor
This contains a single filter:
Note:
• Check Server Can Ping Router - Host(1.2.3.4) Timeout(2000) Attempts(4)
Success(50%) TTL(128)
All actions for each of the above filters within this template are set to a default
of sending an alert to the Enterprise Console. You must manually change this
setting if you require an alternative action to be taken upon the generation of
an alert.
AIX® System Monitoring (Advanced) Template
The AIX® System Monitoring (Advanced) template contains all of the filters
available in the Standard template and adds additional filter coverage.
AIX® Error Report Monitor
This contains the standard filters plus these additional two filters:
• Error Logger Errors - Errpt(Class=O)
• Undetermined Errors - Errpt(Class=U)
Subsystem Monitor
This contains the standard filters plus these additional six filters:
• Critical Subsystem (dhcpcd) Does Not Exist - Subsystem Does Not
Exist(dhcpcd)
Templates
18-231
• Critical Subsystem (dhcpcd) is Inoperative - Subsystem is
Inoperative(dhcpcd)
• Critical Subsystem (lpd) Does Not Exist - Subsystem Does Not Exist(lpd)
• Critical Subsystem (lpd) is Inoperative - Subsystem is Inoperative(lpd)
• Critical Subsystem (sendmail) Does Not Exist - Subsystem Does Not
Exist(sendmail)
• Critical Subsystem (sendmail) is Inoperative - Subsystem is
Inoperative(sendmail)
Logical Volume Monitor
This contains the standard filters plus these additional six filters:
• Stale Physical Partitions Exist (/Mounted on rootvg hd4) - Measure(Stale
Physical Partitions) Trigger(>0)
• Stale Physical Partitions Exist (/home Mounted on rootvg hd1) Measure(Stale Physical Partitions) Trigger(>0)
• Stale Physical Partitions Exist (/tmp Mounted on rootvg hd3) - Measure(Stale
Physical Partitions) Trigger(>0)
• Stale Physical Partitions Exist (/usr Mounted on rootvg hd2) - Measure(Stale
Physical Partitions) Trigger(>0)
• Stale Physical Partitions Exist (/var Mounted on rootvg hd9) - Measure(Stale
Physical Partitions) Trigger(>0)
• Stale Physical Partitions on rootvg - Measure(Stale Physical Partitions)
Trigger(>0)
Script Monitor
This contains the standard filters plus these additional five filters:
• Console Log - Script(/var/lib/halcyon/conslog.sh.+)
• Disk I/O Busy >75% Possible I/O Bound System - Script(iostat 1 1 | grep
hdisk0 | awk ‘{print$2}’ ^[7-9]{1}[0-9]{1}\..$|^100\..$)
• Disk I/O Wait >25% Possible I/O Bound System - Script(iostat 1 1 | awk
‘FNR==5{print$6} 2{1}[6-9]{1}\..$|^[3-9]{1}[0-9]{1}\..$|^100\..$)
• Sustained Disk Utilisation >=80% - Script(iostat -d 1 1 | awk
‘FNR==5{print$2}’[8-9][0-9].)
• Verify Operation Status of Path to MPIO Device - Script(lspath | grep -v
Enabled.+)
File & Folder Monitor
This contains the standard filters plus these additional four filters:
• File (/etc/environment) Has Changed - File(/etc/environment) Trigger(Exists)
• File (/etc/hostmibd.conf) Has Changed - File(/etc/hostmibd.conf)
Trigger(Exists)
18- 2 3 2
Network Server Suite
• File (/etc/netsvc.conf) Has Changed - File(/etc/netsvc.conf) Trigger(Exists)
• File (/etc/resolv.conf) Has Changed - File(/etc/resolv.conf) Trigger(Exists)
Log File Monitor
This contains the same two filters available in the AIX® System Monitoring
(Standard) template.
CPU, Filesystem and Memory Monitor
This contains the standard filters plus these additional three filters:
• PageFile Used <30% (Suggests Too Much Paging Space) - Group(Memory)
Type(UsedPageFilePercent) Trigger(<30%)
• PageFile Used >70% (Suggests Not Enough Paging Space) Group(Memory) Type(UsedPageFilePercent) Trigger(>70%)
• Paging Space >95% - Group(Memory) Type(UsedPageFilePercent)
Trigger(>95%)
Process Monitor
This contains the standard filters plus these additional eight filters:
• Optional Process (aixmibd) Does Not Exist - Type(Process By Name)
Process(aixmibd) Trigger(DoesNotExist)
• Optional Process (hostmibd) Does Not Exist - Type(Process By Name)
Process(hostmibd) Trigger(DoesNotExist)
• Optional Process (rpc.lockd) Does Not Exist - Type(Process By Name)
Process(rpc.lockd) Trigger(DoesNotExist)
• Optional Process (rpc.statd) Does Not Exist - Type(Process By Name)
Process(rpc.statd) Trigger(DoesNotExist)
• Optional Process (sendmail) Does Not Exist - Type(Process By Name)
Process(sendmail) Trigger(DoesNotExist)
• Optional Process (snmpd) Does Not Exist - Type(Process By Name)
Process(snmpd) Trigger(DoesNotExist)
• Optional Process (snmpmibd) Does Not Exist - Type(Process By Name)
Process(snmpmibd) Trigger(DoesNotExist)
• Optional Process (sshd) Does Not Exist - Type(Process By Name)
Process(sshd) Trigger(DoesNotExist)
Ping Monitor
This contains the same filters as available in the AIX® System Monitoring
(Standard) template.
Note:
All actions for each of the above filters within this template are set to a default
of sending an alert to the Enterprise Console. You must manually change this
setting if you require an alternative action to be taken upon the generation of
an alert.
Templates
18-233
Linux® Templates
RED HAT System Monitoring (Standard) Template
The RED HAT System Monitoring (Standard) template contains filters covering
all of the Linux® Monitors with the exception of the System Monitor. The
following filters are defined:
Linux® Logical Volume Monitor
This contains the following two filters:
• Logical volume (LogVol00) status <> available - Measure(Status) Trigger (<>
available)
• Logical volume (LogVol01) status <> available - Measure(Status) Trigger (<>
available)
Script Monitor
This contains the following filter:
• Check for Failed Raid Drives - Script(mdadm -D /dev/md0 | grep Failed
Devices 1|2|3)
File & Folder Monitor
This contains the following five filters:
• File (/etc/crontab) Has Changed - File(/etc/) Trigger(Exists)
• File (/etc/inittab) Has Changed - File(/etc/) Trigger(Exists)
• File (/etc/sendmail.cf) Has Changed - File(/etc/mail) Trigger(Exists)
• File (/etc/profile) Has Changed - File(/etc/) Trigger(Exists)
• File (/etc/xinetd.conf) Has Changed - File(/etc/) Trigger(Exists)
Log File Monitor
This contains the following filter:
• Monitor for Failed Logins in Secure Log - LogFile(/var/log/secure) Expression
(failure)
CPU, Filesystem and Memory Monitor
This contains the following five filters:
• Filesystem (/) Disk Space Used >=80% - Group(Filesystem) Volume(/)
Type(Filesystem Space Used %) Trigger(>=80%)
• Filesystem (/) Does Not Exist - Group(Filesystem) Volume(/) Trigger(Does
Not Exist)
18- 2 3 4
Network Server Suite
• Filesystem (/) Inode Used >=90% - Group(Filesystem) Volume(/) Type(INodes %) Trigger(>=90%)
• Paging Space >95% - Group(Memory) Type(Page File Used %)
Trigger(>95%)
• Sustained CPU >95% - Group(CPU) CPU(0) Type(Load) Trigger(>95%)
Process Monitor
This contains the following six filters:
• Critical Process (crond) Does Not Exist - Type(Process By Name)
Process(crond) Trigger(DoesNotExist)
• Critical Process (gdm-binary) Does Not Exist - Type(Process By Name)
Process(gdm-binary) Trigger(DoesNotExist)
• Critical Process (sshd) Does Not Exist - Type(Process By Name)
Process(sshd) Trigger(DoesNotExist)
• Critical Process (syslogd) Does Not Exist - Type(Process By Name)
Process(syslogd) Trigger(DoesNotExist)
• Critical Process (xfs) Does Not Exist - Type(Process By Name) Process(xfs)
Trigger(DoesNotExist)
• Critical Process (xinetd) Does Not Exist - Type(Process By Name)
Process(xinetd) Trigger(DoesNotExist)
Ping Monitor
This contains a single filter:
Note:
• Check Server Can Ping Router - Host(1.2.3.4) Timeout(2000) Attempts(4)
Success(50%) TTL(128)
All actions for each of the above filters within this template are set to a default
of sending an alert to the Enterprise Console. You must manually change this
setting if you require an alternative action to be taken upon the generation of
an alert.
RED HAT System Monitoring (Advanced) Template
The RED HAT System Monitoring (Advanced) template contains all of the filters
available in the Standard template and adds additional filter coverage.
File & Folder Monitor
This contains the standard filters plus these additional three filters:
• File (/etc/resolv.conf) Has Changed - File(/etc/) Trigger(Exists)
• File (/etc/sysconfig/iptables) Has Changed - File(/etc/sysconfig)
Trigger(Exists)
• File (/etc/vsftpd.conf) Has Changed - File(/etc/vsftpd) Trigger(Exists)
Templates
18-235
Log File Monitor
This contains the standard filter plus these additional two filters:
• Monitor for MySQL Errors - LogFile(/var/log/mysqld.log) Expression (error|
failure)
• Monitor for Samba Errors - LogFile(/var/log/samba/smbd.log) Expression
(error|failed)
CPU, Filesystem and Memory Monitor
This contains the standard filters plus these additional five filters:
• Filesystem (/boot) Disk Space Used >=80% - Group(Filesystem) Volume(/
boot) Type(Filesystem Space Used %) Trigger(>=80%)
• Filesystem (/boot) Does Not Exist - Group(Filesystem) Volume(/boot)
Trigger(Does Not Exist)
• Filesystem (/boot) Inode Used >=90% - Group(Filesystem) Volume(/boot)
Type(I-Nodes %) Trigger(>=90%)
• PageFile Used <30% (Suggests Too Much Paging Space) - Group(Memory)
Type(UsedPageFilePercent) Trigger(<30%)
• PageFile Used >70% (Suggests Not Enough Paging Space) Group(Memory) Type(UsedPageFilePercent) Trigger(>70%)
Process Monitor
This contains the standard filters plus these additional ten filters:
• Optional Process (httpd) Does Not Exist - Type(Process By Name)
Process(httpd) Trigger(DoesNotExist)
• Optional Process (mysqld) Does Not Exist - Type(Process By Name)
Process(mysqld) Trigger(DoesNotExist)
• Optional Process (postmaster) Does Not Exist - Type(Process By Name)
Process(postmaster) Trigger(DoesNotExist)
• Optional Process (rpc.idmapd) Does Not Exist - Type(Process By Name)
Process(rpc.idmapd) Trigger(DoesNotExist)
• Optional Process (rpc.statd) Does Not Exist - Type(Process By Name)
Process(rpc.statd) Trigger(DoesNotExist)
• Optional Process (sendmail) Does Not Exist - Type(Process By Name)
Process(sendmail) Trigger(DoesNotExist)
• Optional Process (smbd) Does Not Exist - Type(Process By Name)
Process(smbd) Trigger(DoesNotExist)
• Optional Process (spamd) Does Not Exist - Type(Process By Name)
Process(spamd) Trigger(DoesNotExist)
• Optional Process (squid) Does Not Exist - Type(Process By Name)
Process(squid) Trigger(DoesNotExist)
18- 2 3 6
Network Server Suite
• Optional Process (vsftpd) Does Not Exist - Type(Process By Name)
Process(vsftpd) Trigger(DoesNotExist)
Note:
All actions for each of the above filters within this template are set to a default
of sending an alert to the Enterprise Console. You must manually change this
setting if you require an alternative action to be taken upon the generation of
an alert.
SUSE System Monitoring (Standard) Template
The SUSE® System Monitoring (Standard) template contains filters covering all
of the Linux® Monitors with the exception of the System Monitor. The following
filters are defined:
Linux® Logical Volume Monitor
This contains the following two filters:
• Logical volume (LogVol00) status <> available - Measure(Status) Trigger (<>
available)
• Logical volume (LogVol01) status <> available - Measure(Status) Trigger (<>
available)
Script Monitor
This contains the following filter:
• Check for Failed Raid Drives - Script(mdadm -D /dev/md0 | grep Failed
Devices 1|2|3)
File & Folder Monitor
This contains the following five filters:
• File (/etc/crontab) Has Changed - File(/etc/) Trigger(Exists)
• File (/etc/inittab) Has Changed - File(/etc/) Trigger(Exists)
• File (/etc/sendmail.cf) Has Changed - File(/etc/mail) Trigger(Exists)
• File (/etc/profile) Has Changed - File(/etc/) Trigger(Exists)
• File (/etc/xinetd.conf) Has Changed - File(/etc/) Trigger(Exists)
Log File Monitor
This contains the following filter:
• Monitor for Failures in Messages Log - LogFile(/var/log/messages)
Expression (error|fail)
Templates
18-237
CPU, Filesystem and Memory Monitor
This contains the following five filters:
• Filesystem (/) Disk Space Used >=80% - Group(Filesystem) Volume(/)
Type(Filesystem Space Used %) Trigger(>=80%)
• Filesystem (/) Does Not Exist - Group(Filesystem) Volume(/) Trigger(Does
Not Exist)
• Filesystem (/) Inode Used >=90% - Group(Filesystem) Volume(/) Type(INodes %) Trigger(>=90%)
• Paging Space >95% - Group(Memory) Type(Page File Used %)
Trigger(>95%)
• Sustained CPU >95% - Group(CPU) CPU(0) Type(Load) Trigger(>95%)
Process Monitor
This contains the following six filters:
• Critical Process (crond) Does Not Exist - Type(Process By Name)
Process(crond) Trigger(DoesNotExist)
• Critical Process (gdm-binary) Does Not Exist - Type(Process By Name)
Process(gdm-binary) Trigger(DoesNotExist)
• Critical Process (sshd) Does Not Exist - Type(Process By Name)
Process(sshd) Trigger(DoesNotExist)
• Critical Process (syslogd) Does Not Exist - Type(Process By Name)
Process(syslogd) Trigger(DoesNotExist)
• Critical Process (xfs) Does Not Exist - Type(Process By Name) Process(xfs)
Trigger(DoesNotExist)
• Critical Process (xinetd) Does Not Exist - Type(Process By Name)
Process(xinetd) Trigger(DoesNotExist)
Ping Monitor
This contains a single filter:
• Check Server Can Ping Router - Host(1.2.3.4) Timeout(2000) Attempts(4)
Success(50%) TTL(128)
Note:
18- 2 3 8
All actions for each of the above filters within this template are set to a default
of sending an alert to the Enterprise Console. You must manually change this
setting if you require an alternative action to be taken upon the generation of
an alert.
Network Server Suite
SUSE System Monitoring (Advanced) Template
The SUSE® System Monitoring (Advanced) template contains all of the filters
available in the Standard template and adds additional filter coverage.
File & Folder Monitor
This contains the standard filters plus these additional three filters:
• File (/etc/resolv.conf) Has Changed - File(/etc/) Trigger(Exists)
• File (/etc/sysconfig/iptables) Has Changed - File(/etc/sysconfig)
Trigger(Exists)
• File (/etc/vsftpd.conf) Has Changed - File(/etc/vsftpd) Trigger(Exists)
Log File Monitor
This contains the standard filter plus these additional two filters:
• Monitor for MySQL Errors - LogFile(/var/log/mysqld.log) Expression (error|
failure)
• Monitor for Samba Errors - LogFile(/var/log/samba/smbd.log) Expression
(error|failed)
CPU, Filesystem and Memory Monitor
This contains the standard filters plus these additional five filters:
• Filesystem (/boot) Disk Space Used >=80% - Group(Filesystem) Volume(/
boot) Type(Filesystem Space Used %) Trigger(>=80%)
• Filesystem (/boot) Does Not Exist - Group(Filesystem) Volume(/boot)
Trigger(Does Not Exist)
• Filesystem (/boot) Inode Used >=90% - Group(Filesystem) Volume(/boot)
Type(I-Nodes %) Trigger(>=90%)
• PageFile Used <30% (Suggests Too Much Paging Space) - Group(Memory)
Type(UsedPageFilePercent) Trigger(<30%)
• PageFile Used >70% (Suggests Not Enough Paging Space) Group(Memory) Type(UsedPageFilePercent) Trigger(>70%)
Process Monitor
This contains the standard filters plus these additional ten filters:
• Optional Process (httpd) Does Not Exist - Type(Process By Name)
Process(httpd) Trigger(DoesNotExist)
• Optional Process (mysqld) Does Not Exist - Type(Process By Name)
Process(mysqld) Trigger(DoesNotExist)
• Optional Process (postmaster) Does Not Exist - Type(Process By Name)
Process(postmaster) Trigger(DoesNotExist)
Templates
18-239
• Optional Process (rpc.idmapd) Does Not Exist - Type(Process By Name)
Process(rpc.idmapd) Trigger(DoesNotExist)
• Optional Process (rpc.statd) Does Not Exist - Type(Process By Name)
Process(rpc.statd) Trigger(DoesNotExist)
• Optional Process (sendmail) Does Not Exist - Type(Process By Name)
Process(sendmail) Trigger(DoesNotExist)
• Optional Process (smbd) Does Not Exist - Type(Process By Name)
Process(smbd) Trigger(DoesNotExist)
• Optional Process (spamd) Does Not Exist - Type(Process By Name)
Process(spamd) Trigger(DoesNotExist)
• Optional Process (squid) Does Not Exist - Type(Process By Name)
Process(squid) Trigger(DoesNotExist)
• Optional Process (vsftpd) Does Not Exist - Type(Process By Name)
Process(vsftpd) Trigger(DoesNotExist)
Note:
All actions for each of the above filters within this template are set to a default
of sending an alert to the Enterprise Console. You must manually change this
setting if you require an alternative action to be taken upon the generation of
an alert.
See “Applying Templates” on page 18-241 for further information on how to
use these templates across your system enterprise.
Creating bespoke templates
Launch the Central Configuration Manager and select the Templates tab.
Either select File | Add Template from the menu bar or click the Add template
icon
to display the Add Template dialog.
Templates can only be added at the top level of ‘Windows Templates’.
Templates require a name and description to be applied and it is good practice
to choose labels that are meaningful and identify the tasks that the template
undertakes.
Figure 18.2 Add Template dialog
18- 2 4 0
Network Server Suite
From the Template selection screen it is possible to select the monitors and
filters that form the basis of the template.
Note:
It is only possible to open the filter dialog of the monitor from the Templates tab. The
monitor settings option is only accessible from the Systems tab. This means that it is
not possible to apply the ‘Hold’ monitor status (or other monitor settings) to a
template. This must be done on an individual system basis after the template has
been applied.
Monitor filters are created in templates in the same way as in ‘standalone’
monitors, (please refer to the section ‘Working with Monitors’ for more
information on monitors) with the following exceptions:
Monitor Groups
Exception
Event Log Monitors
When adding criteria and using the Browse
facility, you must first select an Example
Device from which to select the specific
event that you wish to monitor. If the
template is applied to a system that does
not run the event, the filter is ignored.
Performance Monitors
When adding criteria, an Example Device
must be selected prior to selection of the
actual criteria.If selecting Generic
Performance criteria directly from the
Browse facility on the Example Device, it is
the current settings on this device that is
applied to the template.
System Monitors (Service)
When adding criteria, you must first select
an Example Device from which to select
the specific service that you wish to
monitor. If the template is applied to a
system that does not run the service, the
filter is ignored.
When a template filter has been created, the associated monitor is shown in
bold type as it does in the Systems dialog. The number of filters applied per
monitor is also shown in both panes of the Template dialog.
Applying Templates
Once a template has been created it can then be applied to other systems via
the Templates tab of the Central Configuration Manager.
Templates can be applied directly to each system shown in the Template
Systems panel.
Templates
18-241
Figure 18.3 Applying Templates
Once saved, the System to which the template has been applied is shown in
bold type to Server Manager Level only. Individual monitors and filters remain in
light face.
Figure 18.4 System level Templates
Copy and paste
This short-cut is used primarily to copy an individual system filter into an existing
template filter. It is only possible to do this between same type monitors (with
the exception of Event Log Monitors). For example, a Summary Performance
Monitor filter can only be copied to a Summary Performance Template filter.
Modifying Individual Systems
Once a template filter has been applied it is important to ensure that the filter
details are applicable to the new system in terms of level of criteria and actions
undertaken. It is good housekeeping to keep the template filters as generic as
possible and fine-tune them individually at system level.
18- 2 4 2
Network Server Suite
For example, a filter applied across twenty systems with an action of sending a
SMS message, initiates twenty identical messages to the same resource should
an alert be raised.
Exporting and Importing Templates
Templates can be exported to and imported from other instances of Network
Server Suite. Template files are saved with an extension of .csf.
Note:
Exporting and Importing Template options are accessed from within the Central
Configuration Manager menu bar; Backup | Export Templates or Backup |
Import Templates.
Imported Templates do not override any existing templates on the system to
which they are imported but add additional templates that did not previously
exist.
Deleting Templates
If a template is deleted it is removed from all systems to which it has been
applied.
Templates
18-243
C
HAPTER
REPORTING
CHAPTER19
Overview
Network Server Suite includes a reporting function that captures performance
data allowing you to generate summarized or detailed reports based on the
performance of monitored systems in your enterprise. Reporting is activated at
system level rather than across the entire enterprise so it is possible to select
which systems to include.
Note:
Performance data can then be fed into the Halcyon Advanced Reporting Suite
from where performance reports can be designed, generated and distributed.
Please refer to the Advanced Reporting Suite Installation Guide and
Advanced Reporting Suite Report Designer User Reference for more
information on how to use performance data from Network Server Suite
within Advanced Reporting Suite.
Applying the Reporting Monitor to a System
To apply Performance Monitoring to a system:
1 From within the Central Console Manager, in the left-hand navigation panel,
expand the view of the system to which you want to apply the performance
reporting.
2 Expand Report Monitors and select Reporting.
Note:
3 In the Reporting Panel under Settings, click Capture Reporting Data.
Even though the report monitor has been applied to the system, this system
must still be added in the Web Interface of the Advanced Reporting Suite in
order that the performance data is collected. Please refer to the Advanced
Reporting Suite Installation Guide for more information on how to do this.
4 Click File | Save Settings to apply the reporting settings to this system.
19- 2 4 4
Network Server Suite
Note:
Performance Reporting is automatically applied across all disks installed on
the system. You do not need to specify each disk separately.
Purging Performance Data
To prevent historic performance data from taking up excessive storage space,
you can define the period of time after which this data is deleted from the
system. This means that after this time period, the data is unavailable for
collection by the Halcyon Data Collector Service within the Advanced Reporting
Suite. Data can be purged after a defined period of Hours or Days.
Setting the Purge Time Period
1 From within the Central Console Manager, in the left-hand navigation panel,
expand the view of the system to which you want to apply the performance
reporting.
2 Expand Report Monitors and select Reporting.
3 In the Reporting Panel under Settings, set the Purge Captured Data After
option to the number of hours or days that you wish to retain the information.
4 Select whether the time period is in Hours or Days.
5 Click File | Save Settings to apply the purge settings to this system
Adding Reporting Fields
Note:
The quickest way to add reporting fields to a system is to apply the Reporting
template which contains five pre-defined, commonly-used performance
reporting fields.
See “Reporting Template” for more information.
Reporting fields are used to determine what performance data should be
collected from each system in order to form the basis of performance reporting
for this device. The available fields are based upon the Windows Management
Instrumentation (WMI) monitor. An unlimited number of user-defined fields can
be added for each system.
To Add a Reporting Field:
Note:
1 From the Reporting Panel, click Add Field. The WMI Reporting Data dialog
is displayed.
See “WMI (Windows® Management Instrumentation) Monitor” for more
information relating to the options on this dialog.
Reporting
19-245
Figure 19.1 Adding a Reporting field
Defining Reporting Fields
The simplest way to define a specific reporting field is to use the Browse option
to scan the current system for the generic performance object on which data is
collected.
The following screenshot shows the monitoring of Active Sessions of Terminal
Services on the selected system. Note that the current value is not transposed
to the defined reporting field.
19- 2 4 6
Network Server Suite
Figure 19.2 WMI Browse Performance Data dialog
Performance data is added using a series of drop-down menu options and
choice buttons.
Category drop-down
Select whether you are going to check for the Performance or Non-Performance
of the intended data object.
Object drop-down
Use the drop-down menu to select the WMI Object on which you wish to report
the performance data. Use the scroll-bar to see options further options not
initially displayed. Click on an object in the list to select it.
Reporting
19-247
Counters/Instances
Depending on the chosen object you now have the ability to select individual
counters and instances unique to the object type or select all (or a combination
of one counter and all instances or all counters and one instance).
Click Add to begin generating Performance Data on the chosen counters/
instances which are listed in the data field together with their corresponding
graphical color representation.
Data can be automatically refreshed every 3 seconds, by default, by clicking the
Auto-Refresh option. The period of time between refreshing can be increased or
decreased as required.
When you are satisfied with your choices, highlight the entry in the WMI field
data panel at the bottom of this dialog. The Select button is now enabled.
Click Select to re-open the WMI Reporting Data dialog. All fields on this dialog
are auto-filled with the selected WMI performance data.
Click OK to add the WMI definition to the reporting fields in the selected field
slot.
Continue to add further WMI Reporting data as required for this system.
When you have finished adding performance data fields click File | Save
Settings to apply the changes to this system.
The selected fields (providing that they do not contain a null data value) are now
available for inclusion in a Performance Data report for this system that can be
generated using the Advanced Reporting Suite Report Designer and Web
Interface components.
19- 2 4 8
Network Server Suite
Setting SLA Flags In Filter Criteria
Aside from using the Report Monitoring tool to check for performance data on a
system, it is also possible to set Service Level Agreement (SLA) flags against
most other system monitors when setting filter criteria. These SLA flags can
then be reported against in the Advanced Reporting Suite using a pre-defined
report template that is shipped with the product.
SLA flags can be set for filter criteria within the following Windows monitors:
• Web Application Monitor (if installed)
• CPU, Disk and Memory Monitor
• WMI Monitor
• Service Monitor
• TCP FTP Monitor
• TCP HTTP Monitor
• TCP NNTP Monitor
• TCP Ping Monitor
• TCP POP3 Monitor
• TCP SMTP Monitor
• TCP Telnet Monitor
Note:
• TCP/UDP Generic
SLA reporting is not currently available for AIX or Linux systems.
To set a SLA Flag from within Filter criteria:
1 Create the monitor filter as you would do normally (see “Adding Filter
Criteria” for more information).
2 On most monitors, there are three pages to complete when setting filter
criteria; Criteria, Alert and Advanced. Select the Advanced page.
Note:
3 Click the SLA Statistic field so that it is enabled (See screenshot overleaf).
The SLA flag is measured against the specific criteria defined for this filter.
If you are setting multiple SLA flags for different criteria and/or monitors, we
recommend that you create a Send Enterprise Console alert action so that
you can determine which of the SLA criteria has failed.
4 Providing that all the other information required to create the filter has been
entered, click OK to save this filter criteria as an SLA flag. Click OK again on
the Add Filter Detail dialog to save this filter.
5 Click File | Save Settings to apply the filter to this system.
Reporting
19-249
Note:
SLA Statistic checking is not affected by the suspension of the filter, (SLA
data is still gathered even if the filter is suspended) but is dependent on the
time period when the filter is active (SLA data is not gathered outside the
times when the filter is active).
Note:
We recommend that when creating SLA flags within filters, that all SLA
criteria are kept together in the same filter that use the ‘“Perform Actions For
Each Criteria That Triggers” option, otherwise SLA failures may or may not
be indicated correctly.
System performance against the specified SLA flags can then be viewed on
the SLA Statistics report (automatically included as a Report Template within
Advanced Reporting Suite) for this system.
Note:
See the Advanced Reporting Suite Installation Guide for more information.
Reporting Template
Reporting templates allow you to apply the same reporting criteria across
multiple systems in your enterprise. By using a reporting template you ensure
that you are generating like-for-like reports across the same generic
performance measurements of your systems. As with filter templates, a change
made at filter level is reflected across all systems where that filter is
implemented.
A basic reporting template covering the following performance measurements is
shipped with Network Server Suite as standard:
• Processor (% Processor Time)
• Win32_PageFileUsage (Allocated Base Size)
• Win32_PageFileUsage (Current Usage)
• Win32_Volume (Capacity)
• Win32_Volume (Free Space)
19- 2 5 0
Network Server Suite
Note:
Reporting templates are created by adding a new template to the Templates tab
of the Central Configuration Manager. It is good practice to give a reporting
template an identification label that distinguishes it from any filter templates that
may already exist.
See “Defining Reporting Fields” for more information on how to add
Performance Data fields to the default or your own Report Templates.
Applying a Reporting Template
Report templates are applied from the Systems tab of the Central Configuration
Manager at Server Manager level. The reporting template is assigned from the
Reporting Templates section. Note that all templates (Filter and Reporting
appear in the drop-down choice menu so be careful when making your
selection. The default Reporting template is called Reporting (Performance).
Figure 19.3 Applying Reporting Templates
Repeat the process for each server manager on which the reporting template is
to be installed.
Note:
The Performance Data for the specified fields in the assigned Report Template
can now be sent to a report from within the Advanced Reporting Suite.
Server Manager Reporting is configured independently of Reporting
Templates.
Reporting
19-251
C
HAPTER
EXPORTING AND IMPORTING SETTINGS
CHAPTER20
Overview
From within Central Configuration Manager and Enterprise Server Options it is
possible to Export and Import settings between different machines on your
network. This substantially decreases the time required to deploy Halcyon
Network Server Suite across your enterprise.
Exporting Settings from Central Configuration Manager
Settings exported from Central Configuration Manager include:
• All systems
• Defined Filters
• Defined Templates
• Defined Reporting activities
Select Backup | Export Settings from the Central Configuration Manager
menu bar.
The file generated is saved as an XML document with an automatically
generated file name identifying the Component – Date (yyyy-mm-dd) – Time
(hh:mm:ss). You can override this file name if desired.
The generated file is saved is to a backup directory of the Central Configuration
Manager by default, although this setting can also be overridden if required.
(Note that when importing settings, the Central Configuration Manager defaults
to the backup directory as the initial location when searching for compatible
files).
20- 2 5 2
Network Server Suite
Importing Settings into Central Configuration Manager
Note:
By importing settings from another instance of Central Configuration
Manager, you overwrite any existing data. This action cannot be undone.
Select Backup | Import Settings from the Central Configuration Manager
Menu bar.
Select Yes to replace the existing Systems with the imported data.
Exporting Settings from Enterprise Server Options
Settings exported from Enterprise Server Options include:
• User data
• Defined filters
Click Import/Export in the Footer section of the Enterprise Server Options
dialog.
Select the Export option and enter a File Name or click
to select a directory
and file name to which the exported data is saved. Click Open to save the data
in the named file and location.
Importing settings into Enterprise Server Options
Note:
By importing settings from another instance of Enterprise Server Options,
you overwrite any existing data. This action cannot be undone.
Click Import/Export in the Footer section of the Enterprise Server Options
dialog.
Select the Import option and click
to select a directory and an .eco file. Click
Open to import the data into this instance of Enterprise Server Options.
Exporting and Importing Settings
20-253
C
HAPTER
TROUBLESHOOTING
CHAPTER21
If you discover an error with this product, please review the section below; ‘To
Report an Error’, then contact Halcyon Software on the numbers below.
To Report an Error
The following checklist guides you through the steps necessary to report an
error. When completed, please contact Halcyon Technical Support.
1 Has logging been turned on?
2 Logging can be switched on from the individual monitors Monitor Settings
tab, refer to Filters Tabs Dialog Options.
3 What Halcyon services are running?
4 Has any hardware or software been installed, moved or changed?
5 What were you trying to achieve – have you got details?
6 Have you taken a screenshot of the error?
Contact Details
If you have a query and would like to report an error with the application, please
contact your local Halcyon Software office and ask for technical support.
For details of your local office or reseller, please visit www.halcyonsoftware.com
and access the Contact Us, Support or Partners options.
You can also email Halcyon Software Technical Support via:
technicalservices@halcyonsoftware.com
21- 2 5 4
Network Server Suite
C
HAPTER
COMPANY INFORMATION
CHAPTER22
Head Office
Halcyon Software Limited
5 The Forum
Minerva Business Park
Lynch Wood
Peterborough
Cambridgeshire
PE2 6FT
United Kingdom
Tel:
+44 (0) 1733 234995
URL:
http://www.halcyonsoftware.com/
For details of your local office or reseller, please visit www.halcyonsoftware.com
and access the Contact Us, Support or Partners options.
You can also email us directly using the following email addresses:
Technical Support:technicalservices@halcyonsoftware.com
Sales: sales@halcyonsoftware.com
Accounts:accounts@halcyonsoftware.com
Company Information
22-255
Copyright
Copyright 2009-2013 Halcyon Software Limited. All rights reserved.
• Windows is a registered trademark of Microsoft Corporation in the United
States and other countries.
• UNIX is a registered trademark of The Open Group in the United States
and other counties.
• Linux is a registered trademark of Linus Torvalds in the United States and
other countries.
• AIX is a registered trademark of International Business Machines in the
United States and other countries.
• RED HAT is a registered trademark of Red Hat, Inc. in the United States
and other countries.
• SUSE is a registered trademark of Novell, Inc. in the United States and
other countries
• IBM is a registered trademark of International Business Machines in the
United States and other countries
This document is intended as a guide to using Network Server Suite from
Halcyon Software. This documentation contains Halcyon proprietary and
confidential information and may not be disclosed, used, or copied without the
prior consent of Halcyon Software Limited, or as set forth in the applicable
license agreement. Users are solely responsible for the proper use of the
software and the application of the results obtained.
Although Halcyon Software Limited has tested the software and reviewed the
documentation, the sole warranty for the software may be found in the
applicable license agreement between Halcyon Software Limited and the user.
Publication Revision: January 2013
22- 2 5 6
Network Server Suite
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