guide to aix templates - static.helpsystems.com · business critical machines ... applic ation...

guide to AIX templates

CopyrightCopyright 2010 - 2016 Halcyon - A Division of HelpSystems. All rights reserved.

This document is intended as a guide to the reports generated by using Halcyon software.

This documentation contains Halcyon proprietary and confidential information and may not be disclosed, used, or copied without the prior consent of Halcyon 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 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: April 2016

Overview Halcyon Templates are designed to provide the same level of monitoring across a number of similar devices by applying a set of user-defined rules with a single-click. 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 Templates are also available for:

• Windows

• Linux (RED HAT, OpenSUSE, Oracle)

Templates also are available for the following specialized IBM i environments:

• Infor M3 (Movex)

• Misys

• Misys Midas Plus

• SAP

• JD Edwards

• Maxava

• Quick/EDD

• Infor XA

• Infor System21

• Vision OMS/ODS

• Vision iTera

C H A P T E R

CHAPTER 1INSTALLATION

Network Server Suite comes supplied with two default monitoring templates for AIX® that cover the majority of everyday scenarios that your organization is likely to encounter.

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 rules running alongside the template rules 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.

Using the default templatesLaunch the Central Configuration Manager and select the Templates tab.

The following AIX® monitor templates are defined:

• Advanced Reporting (Data Warehouse)

• AIX System Monitoring (Standard)

• AIX System Monitoring (Advanced)

• VIOS

Note: The AIX VIOS template is covered in a separate document: A Guide to AIX Monitoring.

I n s t a l l a t i o n 1-1

Figure 1.1 Default AIX Templates available within Network Server Suite

Applying TemplatesOnce 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.

1- 2 H a l c y o n T e m p l a t e s

Figure 1.2 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 rules remain in light type face.

Figure 1.3 System level Templates

I n s t a l l a t i o n 1-3

Copy and paste This short-cut is used primarily to copy an individual system rule into an existing template rule. It is only possible to do this between same type monitors (with the exception of Event Log Monitors). For example, a Summary Performance Monitor rule can only be copied to a Summary Performance Template rule.

Modifying Individual SystemsOnce a template rule has been applied it is important to ensure that the rule details are applicable to the new system in terms of level of criteria and actions undertaken. It is good housekeeping to keep the template rules as generic as possible and fine-tune them individually at system level.

For example, a rule 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 TemplatesTemplates can be exported to and imported from other instances of Network Server Suite. Template files are saved with an extension of .csf.

Exporting and Importing Template options are accessed from within the Central Configuration Manager menu bar; Backup | Export Templates or Backup | Import Templates.

Note: 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 TemplatesIf a template is deleted it is removed from all systems to which it has been applied.


C H A P T E R

CHAPTER 2AIX® TEMPLATES

AIX® System Monitoring (Standard) TemplateThe AIX® System Monitoring (Standard) template contains rules covering all of the AIX® Monitors with the exception of the System Monitor. The following rules are defined:

AIX® Error Report MonitorThis monitor checks against the AIX® Error Report, which contains a list of logged errors. This monitor contains the following rules:

Hardware Errors - Errpt(Class=H)This rule checks for any hardware errors that are reported within the AIX® Error Report. These are identified as being of class=H. An alert is generated if any class=H errors are found within the AIX Error Report.

Software Errors - Errpt(Class=S)This rule checks for any software errors that are reported within the AIX® Error Report. These are identified as being of class=S. An alert is generated if any class=S errors are found within the AIX® Error Report.

AIX® Subsystem Report MonitorThis monitor checks for critical subsystems being present and active. It contains the following rules:

Critical Subsystem (inetd) Does Not Exist - Subsystem Does Not Exist(inetd)This rule checks for the existence of the AIX® subsystem ‘inetd’. An alert is generated if this critical subsystem is not found.

A I X ® T e m p l a t e s 2-5

Critical Subsystem (inetd) is Inoperative - Subsystem is Inoperative(inetd)This rule checks that the AIX® subsystem ‘inetd’ is active. An alert is generated if this critical subsystem is in an inoperative state.

Critical Subsystem (qdaemon) Does Not Exist - Subsystem Does Not Exist(qdaemon)This rule checks for the existence of the AIX subsystem ‘qdaemon’. An alert is generated if this critical subsystem is not found.

Critical Subsystem (qdaemon) is Inoperative - Subsystem is Inoperative(qdaemon)This rule checks that the AIX® subsystem ‘qdaemon’ is active. An alert is generated if this critical subsystem is in an inoperative state.

Critical Subsystem (syslogd) Does Not Exist - Subsystem Does Not Exist(syslogd)This rule checks for the existence of the AIX® subsystem ‘syslogd’. An alert is generated if this critical subsystem is not found.

Critical Subsystem (syslogd) is Inoperative - Subsystem is Inoperative(syslogd)This rule checks that the AIX® subsystem ‘syslogd’ is active. An alert is generated if this critical subsystem is in an inoperative state.

Logical Volume MonitorThe AIX® Logical Volume monitors the status of Logical Groups, Logical Volumes and Physical Volumes of the AIX® system and contains the following rules:

Alert when Quorum is Set To On When Disk Mirroring is Active( rootvg) - Measure(Quorum) Trigger(=0)A quorum is a state in which 51 percent or more of the physical volumes in a volume group are accessible. A quorum is also a vote of the number of Volume Group Descriptor Areas and Volume Group Status Areas (VGDA/VGSA) that are active. A quorum ensures data integrity in the event of a disk failure. When a quorum is lost, the volume group varies itself off so that the disks are no longer accessible by the Logical Volume Manager (LVM). This rule checks to ensure that the Quorum is available when disk mirroring is active and raises an alert if set to On..


Volume Group (rootvg) Does Not Exist - Volume Group rootvg Does Not ExistRoot Volume Group (rootvg) is a volume group containing the Base Operating System (BOS). This rule checks to ensure that the Root Volume Group exists and raises an alert if it is not found to be present.

Script Monitor The AIX® Script Monitor runs custom AIX® scripts and commands and checks the output against Regular Expressions. This contains the following rules:

Check for Failed Logins - Script(/var/lib/halcyon/logfails.sh denied)This rule checks for any failed login attempts. Any failed login attempts found are entered in the failedlogins.log. The rule, ‘Monitor for Failed Logins’ within the Log File Monitor, then looks for any entries within this file.

Check for Missing or Removed Disks - Script(lspv missing | removed)This rule runs the lspv command and checks to see if any disks are reported as missing or removed. An alert is raised upon discovery of either of these two conditions.

Zombie process - Report on all - Script(ps -eo stat,pid | egrep “^Z” | awk ‘{print $2}’ ^[^$])A zombie process or defunct process is a process that has completed execution (via the exit system call) but still has an entry in the process table. It is a process in the ‘Terminated state’ and can cause a resource leak. This script monitor rule, which runs every 60 seconds, 24/7, checks for any processes deemed to be in a ‘Z’ status and if found, sends an alert to the Enterprise Console, listing each process.

Zombie process count - Script(ps -eo stat,pid | egrep “^Z” | wc -l ^[^0])Similar to the previous rule, this rule runs every 60 seconds, 24/7 and checks for any processes deemed to be in a ‘Z’ status. If found, an alert is sent to the Enterprise Console, providing a count of the total number of processes.

AIX® File & Folder MonitorThe AIX® File & Folder Monitor checks the current status of specific files within the AIX® system and contains the following rules:


File (/etc/aixmibd.conf) Has Changed - File(/etc/aixmibd.conf) Trigger(Has Changed)This rule checks the file; /etc/aixmibd.conf. This file is used to configure the thresholds for many AIX® monitors. An alert is generated if a change is detected to the modified date of this file.

File (/etc/inetd.conf) Has Changed - File(/etc/inetd.conf) Trigger(Has Changed)This rule checks the file; /etc/inetd.conf. This file, also known as the super server, loads a network program based upon a request from the network. An alert is generated if a change is detected to the modified date of this file.

File (/etc/inittab) Has Changed - File(/etc/inittab) Trigger(Has Changed)This rule checks the file; /etc/inittab. This file is a script that controls most of the boot sequence. It dictates what programs and scripts to launch and at what runlevels. An alert is generated if a change is detected to the modified date of this file.

File (/etc/profile) Has Changed - File(/etc/profile) Trigger(Has Changed)This rule checks the file; /etc/profile. This file contains system wide environment details and startup programs. An alert is generated if a change is detected to the modified date of this file.

File (/etc/security/login.cfg) Has Changed - File(/etc/security/login.cfg) Trigger(Has Changed)This rule checks the file; /etc/security/login.cfg. The /etc/security/login.cfg file is an ASCII file that contains stanzas of configuration information for login and user authentication. An alert is generated if a change is detected to the modified date of the file.

File (/etc/sendmail.cf) Has Changed - File(/etc/sendmail.cf) Trigger(Has Changed)This rule checks the file; /etc/sendmail.cf. This is a lengthy and detailed configuration file and direct editing of this file should be avoided. An alert is generated if a change is detected to the modified date of the file.

File (/var/spool/cron/crontabs/root) Has Changed - File(/var/spool/cron/crontabs/root) Trigger(Has Changed)The /var/spool/cron/crontabs/root file contains commands needed for basic system control. This rule checks this file and raise an alert if any changes have been made to the file since the last time the rule ran.


Log File MonitorThe AIX® Log File Monitor checks AIX® Log Files for failed user login attempts and new entries being posted to the Cron Log file. This monitor contains the following rules:

Monitor for Failed Logins - LogFile(/var/lib/halcyon/failedlogins.log) Expression(.*) This rule checks the failedlogins.log file for any entries. An alert is generated if any failed logins are reported within the /var/lib/halcyon/failedlogins.log file.

Monitor for New Entries in Cron Log - LogFile(/var/adm/cron/log) Expression(.*)This rule checks the /var/adm/cron/log for any new entries. The cron daemon, that controls the automatic running of commands creates a log of its activities in the /var/adm/cron/log file. An alert is generated if any new entries are recorded in this log file.

CPU, Filesystem and Memory MonitorThe AIX® CPU, Filesystem and Memory Monitor template contains the following rules, that measure filesystem, memory and CPU performance and alerts if thresholds are breached.

Filesystem (/) Disk Space Used >=80% - Group(Filesystem) Volume(/) Type(UsedPercent) Trigger(>=80%)This rule checks that the root filesystem ‘/’ on volume ‘/’ has more than 20% free space available at all times. An alert is generated if the available disk space on filesystem ‘/’ equals or exceeds 80 percent.

Filesystem (/) Does Not Exist - Group(Filesystem) Volume(/) Trigger(Does Not Exist)This rule checks that the root filesystem ‘/’ is in existence on volume ‘/’. An alert is generated if the root filesystem ‘/’ is not found on volume ‘/’.

Filesystem (/) Inode Used >=90% - Group(Filesystem) Volume(/) Type(I-Nodes Used %) Trigger(>=90%)This rule checks the percentage Inode used on root filesystem ‘/’. An inode is a data structure in UNIX operating systems that contains important information pertaining to files within a file system. When a file system is created in UNIX, a set amount of inodes are also created. Usually, about 1 percent of the total file system disk space is allocated to the inode table. An alert is generated if the percentage Inode used on root filesystem ‘/’ equals or exceeds 90 percent.


Filesystem (/home) Disk Space Used >=80% - Group(Filesystem) Volume(/home) Type(UsedPercent) Trigger(>=80%)This rule checks that the filesystem ‘/home’ on volume ‘/home’ has more than 20% free space available at all times. An alert is generated if the available disk space on filesystem ‘/home’ equals or exceeds 80 percent.

Filesystem (/home) Does Not Exist - Group(Filesystem) Volume(/home) Trigger(Does Not Exist)This rule checks that the filesystem ‘/home’ is in existence on volume ‘/home’. An alert is generated if the root filesystem ‘/home’ is not found on volume ‘/home’.

Filesystem (/home) Inode Used >=90% - Group(Filesystem) Volume(/home) Type(I-Nodes Used %) Trigger(>=90%)This rule checks the percentage Inode used on filesystem ‘/home’. An alert is generated if the percentage Inode used on root filesystem ‘/home’ equals or exceeds 90 percent.

Filesystem (/tmp) Disk Space Used >=80% - Group(Filesystem) Volume(/tmp) Type(UsedPercent) Trigger(>=80%)This rule checks that the filesystem ‘/tmp’ on volume ‘/tmp’ has more than 20% free space available at all times. An alert is generated if the available disk space on filesystem ‘/tmp’ equals or exceeds 80 percent.

Filesystem (/tmp) Does Not Exist - Group(Filesystem) Volume(/tmp) Trigger(Does Not Exist)This rule checks that the filesystem ‘/tmp’ is in existence on volume ‘/tmp’. An alert is generated if the root filesystem ‘/tmp’ is not found on volume ‘/tmp’.

Filesystem (/tmp) Inode Used >=90% - Group(Filesystem) Volume(/tmp) Type(I-Nodes Used %) Trigger(>=90%)This rule checks the percentage Inode used on filesystem ‘/tmp’. An alert is generated if the percentage Inode used on root filesystem ‘/tmp’ equals or exceeds 90 percent.

Filesystem (/usr) Disk Space Used >=80% - Group(Filesystem) Volume(/usr) Type(UsedPercent) Trigger(>=80%)This rule checks that the filesystem ‘/usr’ on volume ‘/usr’ has more than 20% free space available at all times. An alert is generated if the available disk space on filesystem ‘/usr’ equals or exceeds 80 percent.

2- 1 0 H a l c y o n T e m p l a t e s

Filesystem (/usr) Does Not Exist - Group(Filesystem) Volume(/usr) Trigger(Does Not Exist)This rule checks that the filesystem ‘/usr’ is in existence on volume ‘/usr’. An alert is generated if the root filesystem ‘/usr’ is not found on volume ‘/usr’.

Filesystem (/usr) Inode Used >=90% - Group(Filesystem) Volume(/usr) Type(I-Nodes Used %) Trigger(>=90%)This rule checks the percentage Inode used on filesystem ‘/usr’. An alert is generated if the percentage Inode used on root filesystem ‘/usr’ equals or exceeds 90 percent.

Filesystem (/var) Disk Space Used >=80% - Group(Filesystem) Volume(/var) Type(UsedPercent) Trigger(>=80%)This rule checks that the filesystem ‘/var’ on volume ‘/var’ has more than 20% free space available at all times. An alert is generated if the available disk space on filesystem ‘/var’ equals or exceeds 80 percent.

Filesystem (/var) Does Not Exist - Group(Filesystem) Volume(/var) Trigger(Does Not Exist)This rule checks that the filesystem ‘/var’ is in existence on volume ‘/usr’. An alert is generated if the root filesystem ‘/var’ is not found on volume ‘/usr’.

Filesystem (/var) Inode Used >=90% - Group(Filesystem) Volume(/var) Type(I-Nodes Used %) Trigger(>=90%)This rule checks the percentage Inode used on filesystem ‘/var’. An alert is generated if the percentage Inode used on root filesystem ‘/var’ equals or exceeds 90 percent.

Sustained CPU >95% - Group(CPU) CPU(0) Type(Load) Trigger(>95%)This rule checks the sustained usage of the CPU. An alert is generated if the sustained CPU load exceeds 95% at any one time.

AIX® Process MonitorThe AIX® Process Monitor is used to check that critical processes exist on the system. This monitor contains the following rules:

Critical Process (biod) Does Not Exist - Type(Process By Name) Process(biod) Trigger(DoesNotExist)The biod daemon is required on systems that are either mounting (as a client) or exporting (as a server) filesystems via NFS. This rule checks that the critical process, biod, exists on the system and generates an alert if it is not present.


Critical Process (cron) Does Not Exist - Type(Process By Name) Process(cron) Trigger(DoesNotExist)The cron daemon runs shell commands at specified dates and times. This rule checks that the critical process, cron, exists on the system and generates an alert if it is not present.

Critical Process (errdemon) Does Not Exist - Type(Process By Name) Process(errdemon) Trigger(DoesNotExist)This critical process starts the error logging daemon (errdemon) and writes entries to the error log. This rule checks that this critical process exists on the system and generates an alert if it is not present.

Critical Process (inetd) Does Not Exist - Type(Process By Name) Process(inetd) Trigger(DoesNotExist)The inetd critical process provides Internet service management for a network. This rule checks that the inetd process exists on the system and generates an alert if it is not present.

Critical Process (portmap) Does Not Exist - Type(Process By Name) Process(portmap) Trigger(DoesNotExist)The portmap daemon helps clients map program number and version number pairs to the port number of a server. This rule checks that the portmap process exists on the system and generates an alert if it is not present.

Critical Process (qdaemon) Does Not Exist - Type(Process By Name) Process(qdaemon) Trigger(DoesNotExist)The qdaemon tracks both job requests and the resources necessary to complete the jobs, where the resources may be a real printer, some other real device, or even a file. This rule checks that the qdaemon process exists on the system and generates an alert if it is not present.

Critical Process (syncd) Does Not Exist - Type(Process By Name) Process(syncd) Trigger(DoesNotExist)A file synchronization program, the syncd daemon flushes pages at regularly scheduled intervals. This rule checks that the syncd process exists on the system and generates an alert if it is not present.

Critical Process (writesrv) Does Not Exist - Type(Process By Name) Process(writesrv) Trigger(DoesNotExist)The writesrv daemon enables the ability of users on remote machines to use the ‘write’ command to send messages to users on the local system. This rule checks that the writesrv process exists on the system and generates an alert if it is not present.


AIX® Ping MonitorThis monitor contains a single rule:

Check Server Can Ping Router - Host(1.2.3.4) Timeout(2000) Attempts(4) Success(50%) TTL(128)This rule checks that the server can ping a defined user-defined router. The host address of this template needs to be amended to the actual IP address of the router that you wish to monitor. An alert is generated if the success rate is less than 50% over the four attempts that the ping makes to communicate with the router.

Note: All actions for each of the above rules 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) TemplateThe AIX® System Monitoring (Advanced) template contains all of the rules available in the basic template and adds additional rule coverage.

AIX® Error Report MonitorThis contains the basic rules plus these additional rules:

Error Logger Errors - Errpt(Class=O)This rule checks for any hardware errors that are reported within the AIX® Error Report. These are identified as being of class=O. An alert is generated if any class=H errors are found within the AIX® Error Report.

Undetermined Errors - Errpt(Class=U)This rule checks for any hardware errors that are reported within the AIX® Error Report. These are identified as being of class=U. An alert is generated if any class=U errors are found within the AIX® Error Report.

AIX® Subsystem MonitorThis contains the basic rules plus these additional rules that cover non-critical subsystems:

Optional Subsystem (dhcpcd)Does Not Exist - Subsystem Does Not Exist(dhcpcd)This rule checks for the existence of the AIX® subsystem ‘dhcpcd’. An alert is generated if this optional subsystem is not found.


Optional Subsystem (dhcpcd) is Inoperative - Subsystem is Inoperative(dhcpcd)This rule checks that the AIX® subsystem ‘syslogd’ is active. An alert is generated if this optional subsystem is in an inoperative state.

Optional Subsystem (lpd)Does Not Exist - Subsystem Does Not Exist(lpd)This rule checks for the existence of the AIX® subsystem ‘lpd’. An alert is generated if this optional subsystem is not found.

Optional Subsystem (lpd) is Inoperative- Subsystem is Inoperative(lpd)This rule checks that the AIX® subsystem ‘lpd’ is active. An alert is generated if this optional subsystem is in an inoperative state.

Optional Subsystem (sendmail)Does Not Exist - Subsystem Does Not Exist(sendmail)This rule checks for the existence of the AIX® subsystem ‘sendmail’. An alert is generated if this optional subsystem is not found.

Optional Subsystem (sendmail) is Inoperative- Subsystem is Inoperative(sendmail)This rule checks that the AIX® subsystem ‘sendmail’ is active. An alert is generated if this optional subsystem is in an inoperative state.

AIX® Logical Volume MonitorThis contains the basic rules plus these additional rules:

Stale Physical Partitions Exist (/Mounted on rootvg hd4) - Measure(Stale Physical Partitions) Trigger(=0)A STALE physical partition is a physical partition that contains data you cannot use. This rule checks to see if any stale physical partitions exist on the Root Volume Group hd4.

Stale Physical Partitions Exist (/home Mounted on rootvg hd1) - Measure(Stale Physical Partitions) Trigger(=0)This rule checks to see if any stale physical partitions exist on the Root Volume Group hd1.


Stale Physical Partitions Exist (/tmp Mounted on rootvg hd3) - Measure(Stale Physical Partitions) Trigger(=0)This rule checks to see if any stale physical partitions exist on the Root Volume Group hd3.

Stale Physical Partitions Exist (/usr Mounted on rootvg hd2) - Measure(Stale Physical Partitions) Trigger(=0)This rule checks to see if any stale physical partitions exist on the Root Volume Group hd2.

Stale Physical Partitions Exist (/usr Mounted on rootvg hd9) - Measure(Stale Physical Partitions) Trigger(=0)This rule checks to see if any stale physical partitions exist on the Root Volume Group hd9.

Stale Physical Volumes on rootvg - Measure(Stale Physical Volumes) Trigger(=0)A physical volume is stale if its contents reflect a version of the logical volume that is known to VOL to be earlier than the current version. This rule checks for the presence of stale physical volumes on the Root Volume Group.

Script MonitorThis contains the basic rules plus these additional rules:

Console Log - Script(/var/lib/halcyon/conslog.sh .+)This rule checks the console log for any errors and raises an alert should any be found.

Disk I/O Busy >75% Possible I/O Bound SystemThis rule checks the disk for input and output activity and raises an alert if the activity percentage is higher than 75% which would suggest that the disk is too busy.

Disk I/O Wait >25% Possible I/O Bound System This rule checks the disk for input and output activity and raises an alert if the disk is waiting for more than 25% for activity which would suggest that the disk is too idle.

Sustained Disk Utilization >=80%This rule checks the percentage of time that the physical disk is active and raises an alert if the activity level is constantly higher than 80 percent.


Verify Operations Status of Path to MPIO DeviceBeginning with AIX® 5.2, all SCSI SCSD disk drives are automatically configured as MPIO devices and a select number of Fibre Channel disk drives can be configured as MPIO Other disk. Other devices can be supported, providing the device driver is compatible with the MPIO implementation in AIX. This rule checks to ensure that MPIO is enabled.

AIX® File & Folder MonitorThis contains the basic rules plus these additional rules:

File (/etc/environment) Has Changed - File(/etc) Trigger(Exists)The /etc/environment file contains variables specifying the basic environment for all processes. When a new process begins, the exec subroutine makes an array of strings available that have the form Name = Value. This array of strings is called the environment. This rule checks this file and raises an alert if any changes have been made.

File (/etc/hostmibd.conf) Has Changed - File(/etc) Trigger(Exists)The hostmibd.conf file provides the configuration information for the hostmibd dpi2 sub-agent. This rule checks this file and raises an alert if any changes have been made.

File (etc/netsvc.conf) Has Changed - File(/etc) Trigger(Exists)The /etc/netsvc.conf file is used to specify the ordering of name resolution for the sendmail command, gethostbyname subroutine, gethostaddr subroutine, and gethostent subroutine and alias resolution for the sendmail command. This rule checks this file and raises an alert if any changes have been made.

File(/etc/resolv.conf) Has Changed - File(/etc) Trigger(Exists)The etc/resolv.conf configuration file contains information that determines the operational parameters of the DNS resolver routines installed in the operating system, typically the IP addresses of nameservers available to a host. This rule checks this file and raises an alert if any changes have been made.

Log File MonitorThis contains the same two rules available in the AIX® System Monitoring (Basic) template.


CPU, Filesystem and Memory MonitorThis contains the basic rules plus these additional rules:

Page File Used <30% (Suggests Too Much Paging Space) - Group(Memory) Type(Page File Used %) Trigger(=30%)This rule checks the page file used memory and raises an alert if the percentage figure falls under 30 percent, which would suggest that there is too much paging space assigned.

Page File Used >70% (Suggests Not Enough Paging Space) - Group(Memory) Type(Page File Used %) Trigger(=70%)This rule checks that page file used memory and raises an alert if the percentage figure exceeds 70 percent, which would suggest that there is too little paging space assigned.

Paging Space >95% - Group(Memory) Type(Page File Used %) Trigger(=95%)This rule checks that the paging space available for use does not exceed 95%. An alert is raised if this figure is exceeded.

Process MonitorThis contains the basic rules plus these additional rules checking optional processes:

Optional Process (aixmibd) Does Not Exist - Type(Process By Name) Process(aixmibd) Trigger(Does Not Exist)The process ‘aixmibd’ provides the AIX® Enterprise Management Information Base (MIB) extension subagent, for use with the Simple Network Management Protocol (SNMP), that collects data from system for variables defined in the AIX® Enterprise Specific MIB. This rule checks that the aixmibd process exists on the system and generates an alert if it is not present.

Optional Process (hostmibd) Does Not Exist - Type(Process By Name) Process(hostmibd) Trigger(Does Not Exist)The hostmibd command starts the hostmibd dpi2 sub-agent. The hostmibd daemon is normally executed during system startup when /etc/rc.tcpip shell script is called. This rule checks that the hostmibd process exists on the system and generates an alert if it is not present.


Optional Process (rpc.lockd) Does Not Exist - Type(Process By Name) Process(rpc.lockd) Trigger(Does Not Exist)This daemon processes lock requests and asks the rpc.statd daemon to monitor those requests. This rule checks that the rpc.lockd daemon exists on the system and generates an alert if not present.

Optional Process (rpc.statd) Does Not Exist - Type(Process By Name) Process(rpc.statd) Trigger(Does Not Exist)This daemon works with the rpc.lockd daemon to provide locking functions. This rule checks that the rpc.statd daemon exists on the system and generates an alert if not present.

Optional Process (sendmail) Does Not Exist - Type(Process By Name) Process(sendmail) Trigger(Does Not Exist)The sendmail command receives formatted text messages and routes the messages to one or more users. Used on a network, the sendmail command translates the format of a message's header information to match the requirements of the destination system. The program determines the network of the destination system by using the syntax and content of the addresses. This rule checks that the sendmail process exists on the system and generates an alert if not present.

Optional Process (snmpd) Does Not Exist - Type(Process By Name) Process(snmpd) Trigger(Does Not Exist)The snmpd process starts the Simple Network Management Protocol (SNMP) agent as a background process. This rule checks that the snmpd process exists on the system and generates an alert if not present.

Optional Process (snmpmibd) Does Not Exist - Type(Process By Name) Process(snmpmibd) Trigger(Does Not Exist)The snmpmibd command starts the snmpmibd Distributed Protocol Interface (DPI) version 2 (dpi2) sub-agent. This command may only be issued by a user with root privileges or by a member of the system group. This rule checks that the snmpmibd process exists on the system and generates an alert if not present.

Optional Process (sshd) Does Not Exist - Type(Process By Name) Process(sshd) Trigger(Does Not Exist)The Open Secure Shell daemon helps secure network connections. This rule checks that the sshd process exists on the system and generates an alert if not present.


Ping MonitorThis contains the same rule as available in the AIX® System Monitoring (Basic) template.

Note: All actions for each of the above rules 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.

Oracle JDE EnterpriseOne templateOracle's JD Edwards EnterpriseOne® is an integrated applications suite of comprehensive enterprise resource planning software.

The Oracle JDE EnterpriseOne AIX template contains the following components:

Script Monitor

JDE: Monitor Overnight NIGHTOPR Batch Processes - Script(jdejobs nightopr ^([a-zA-Z0-9]+).*)This Script Monitor rule monitors for any jobs running under the overnight NIGHTOPR batch processes that are still running and raises an alert accordingly if any are found.

File and Folder Monitor

JDE: Monitor changes in JDE.INI - File or Folder(JDE_BASE\JDE.INI) Include(*) Trigger(Exists)JDE.INI is the main configuration file for JD Edwards EnterpriseOne installations. This rule monitors for any changes in this file and raises an alert if any modifications are recorded.

Log File Monitor

JDE: Monitor JDE LogFiles - LogFile(/var/log/jde/jde*) Expression(.+)This Log File Monitor rule checks a specific JD Edwards log file for any changes and raises an alert if any are found.

Note: Each log file to be monitored must be entered as a separate rule. Use the copy rule facility to save time.


Process Monitor

JDE: Execute Submitted Jobs Process Active - Type(Process By Name) Process(runbatch) Trigger(Does Not Exist) runbatch.exe is the job responsible for executing the submitted reports. This Process Monitor rule checks that the runbatch job is active and an alert is raised if it is found to not exist in the monitored system.

JDE: Kernel Processes Active - Type(Process By Name) Process(jde_k) Trigger(Does Not Exist)jdes_k is the job responsible for co‐ordination between the net and the queues. This Process Monitor rule checks that the jde_k job is active and an alert is raised if it is found to not exist in the monitored system.

JDE: Kernel Process Count - Type(Process By Name) Process(jde_k) Measure(NumberOfProcesses) Trigger(<4)jdes_k is the job responsible for co‐ordination between the net and the queues. This Process Monitor rule checks that at least four instances of the jde_k job are active and an alert is raised if any less than this number are found in the monitored system.

JDE: Network Listener Process Active - Type(Process By Name) Process(jde_n) Trigger(Does Not Exist)jde_n is a network listener that listens for connection requests. Depending on the jde.ini setting, zero, one, or more of these processes can run simultaneously. This Process Monitor rule checks that the jde_n job is active and an alert is raised if it is found to not exist in the monitored system.

JDE: Network Listener Process Count - Type(Process By Name) Process(jde_n) Measure(NumberOfProcesses) Trigger(<3)jde_n is a network listener that listens for connection requests. Depending on the jde.ini setting, zero, one, or more of these processes can run simultaneously. This Process Monitor rule checks that at least three instances of the jde_n job are active and an alert is raised if any less than this number are found in the monitored system.


AIX Reporting TemplateReporting 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 rule templates, a change made at rule level is reflected across all systems where that rule is implemented.

A basic reporting template, Advanced Reporting (Data Warehouse) covering the following performance measurements is shipped with Network Server Suite as standard.

Advanced Reporting (Data Warehouse) template

File & Folder MonitorThe File and Folder Monitor within the Advanced Reporting (Data Warehouse) template contains a single rule.

Monitor /var/lib/halcyon/advreport.dat in case >128MB - File(/var/lib/halcyon) Include(advreport.dat) Trigger(Exists)This rule is a Halcyon self-checking entry to ensure that data for the Advanced Reporting template is being collected regularly. If the advreport.dat file is bigger than 128MB, an alert is raised to warn you that data may not be being collected as expected.

AIX Reporting fieldsThis AIX reporting template contains the following reporting fields:

• CPU CPU Load

• Filesystem Filesystem Space Used %

• Memory Page File Used %

• Memory Physical Memory Used %

• Process By Name CPU Usage %


ContactHalcyon - A division of HelpSystems

US: 800-328-1000

Outside US: +44 (0) 1252 618 030www.helpsystems.com/halcyon

TrademarksWindows® is a registered trademark of Microsoft® Corporation.

AIX® is a registered trademark of International Business Machines Corporation

Linux® is a registered trademark of Linus Torvalds

All other trademarks are respective of their own companies.

http://www.halcyonsoftware.com/learnmore

http://www.halcyonsoftware.com/technical

http://www.halcyonsoftware.com

guide to aix templates - static.helpsystems.com · business critical machines ... applic ation...

Documents