ACTMON

Purpose

The ACTMON control file entry applies to IP management and AON functions.

The ACTMON control file entry defines active monitoring policy for critical resources in the network. When a resource is actively being monitored, the NetView® program sets a timer to check the status of the resource. If the resource is not active, the NetView program initiates failure processing (also known as recovery monitoring) and suspends active monitoring in favor of recovery monitoring. Once the resource becomes active, the NetView program resumes active monitoring.

Syntax

Notes:

¹ This parameter is valid only when OPTION=IP390 is specified.

where:

DEFAULTS|option|restype|resname

DEFAULTS: Required if you are going to perform any active monitoring. This statement defines active monitoring definitions for any component. Valid parameters for this statement are INTVL, STATUS, and OPID.
option: Required. For each option installed with AON (as defined by your INSTALLOPT control file statements) you might have an ACTMON definition containing active monitoring definitions that apply to any resource managed by that option. This statement does not initiate any active monitoring actions or timers. If you do not want to define any option-wide defaults, this statement is not necessary. The OPTION keyword must be defined and must be the same as the type field of this entry. RESTYPE is not a valid keyword for this entry.
The option specified on the ACTMON statement for a resource must match the option definition for the resource in the loader table. For example, to define ACTMON for a session, its option parameter must match the EZLRT definition for SESSION in member FKVTABLE. Specify OPTION=SA on the ACTMON statement for the session.
restype: Not required. This statement defines active monitoring definitions that apply to all resources of a particular type. These must be component resource types as indicated in theIBM Z® NetView Automation Guide and the definition tables. The OPTION and RESTYPE keywords are required on this statement. The value of the RESTYPE keyword must be the same as the restype in the type field of this entry.
resname: Required for active monitoring. This statement causes active monitoring timers to be set for the resource. The OPTION and RESTYPE keywords are required for this statement. All the other keywords must be defined either at this level or at the restype, option, or DEFAULTS level ACTMON statements. The values on the most specific definition take precedence. For TCP/IP resources, resname can be either an IP address or a HOSTNAME. AON does not support resources with an IP Version 6–format address.

INTVL

Required at some level. This value might be defined differently for each resource you want to monitor, or might be defined at any non-specific level definition (DEFAULTS, option, or restype). The format is hh:mm or mmm. If ACTMON IPPORT is not defined, the default is 10 minutes.

STATUS

Required at some level. This value can be defined differently for each resource to be monitored or at a nonspecific level definition (DEFAULTS, option, or restype). Parentheses are optional for a single status.

You can use a wildcard character in the last position and a negation symbol in the first position of the STATUS value. See Table 1 for examples of the STATUS specification.

Table 1. Status specification examples
STATUS specification	Search
ACTIV	Explicit status match of ACTIV
ACT*	Match that begins with ACT
/ACTIV	All statuses except ACTIV
/ACT*	All statuses except those beginning with ACT

OPTION

Indicates the AON automation component that is responsible for automating the resource to be actively monitored. ACTMON definitions at this level can be applied to active monitoring against resource types that are supported by the particular automation component. Valid values for this field are the AON automation components defined in the INSTALLOPT option definition of the control file.

Do not use OPTION if you specify ACTMON DEFAULTS.

RESTYPE

Indicates the resource type to be actively monitored. Any ACTMON definitions at this level can be applied to active monitoring against resources of a particular type. Valid values for this field are any AON resource type definitions defined in the EZLRT statement of the AON option definition table (EZLTABLE, FKVTABLE, or FKXTABLE).

Do not use RESTYPE if you specify ACTMON DEFAULTS or ACTMON option.

OPID

Optional. This value might be defined differently for each resource to be monitored, or might be defined at any non-specific level definition (DEFAULTS, option, or restype). Valid values are those defined as valid AUTOOPS in the control file AUTOOPS statements. If a single AUTOOP statement has two operator IDs, the first ID is referred to by the AUTOOP type field and the second is referred to by the same name with a 2 appended to it. If this keyword is not coded, the INSTALLOPT ACTMONOP definition is used. All active monitoring activities are routed to this operator ID. You can add AUTOOPS statements and automation operators to distribute the active monitoring workload.

SP

Required and is valid only for resources managed by AON or IP management. Defines which TCP/IP for 390 service point reports and manages the resource and which service point AON routes status queries to (pings) for active monitoring. There must be a TCP390 definition that matches the value in this parameter. See TCP390 for more information about TCP390 definitions. You can define this value differently for each resource you want to monitor, or you can define it at any nonspecific level definition (DEFAULTS, TCP390, or resource_type).

FORMAT

Specifies one of the following options to be used to determine the status of the resource.

PING: Pings the resource to check its status.
SNMP: Uses SNMP MIB polling to check the status of the resource.

MIBVAR1 – n

Multiple MIBVAR statements can be defined and are required only for SNMP thresholding (requires FORMAT=SNMP).

CORRELATE

Set to Y for trap correlation of IPHOST, IPROUTER, or IPTN3270 and the respective interface. Set the CORRELATE parameter to Y for resources only when SNMP is available. All known interfaces are used to correlate the status. Only use correlation for interfaces installed on critical IPHOSTs or IPROUTERs. N is the default.

EXIT14

Defines additional processing of SNMP interface table. The default value is NONE. Called for FORMAT=SNMP.

EXIT15

Defines additional processing of user-defined thresholds (MIBVAR). The default value is NONE.

Usage notes

The ACTMON statement requires that the IPMGT or AON tower be enabled.
The active monitoring function checks the availability of a router’s IP address and the IP address of its links (interfaces). If the NetView program cannot ping a link, it starts failure processing for that link. The NetView program also puts the router in a LINKDOWN status, but active monitoring continues.
The active monitoring function causes both the host name and IP address of a name server to be pinged. If the host name cannot be pinged, the name server is not operational and the NetView program starts failure processing.

Examples

The following example shows the ACTMON DEFAULTS control file entry that is required for the NetView program to perform active monitoring:
```
ACTMON DEFAULTS,INTVL=01:00,STATUS=ACT
```
Active monitoring is started every hour for each ACTMON entry and the specific resource that is defined to the NetView program. If the status is ACT (also matches ACTIVE and ACT/S), the resource is available and active monitoring is rescheduled. If the status is not ACT, failure processing with the EZLEFAIL routine is started for the resource. These values can be overridden at any other level (option, restype, or resname).
The following example shows active monitoring of AON/SNA subarea option resources:
```
ACTMON SA,OPTION=SA,INTVL=00:30,OPID=NETOPER2
```
For every actively monitored resource managed by the AON/SNA subarea option, the monitoring interval is every 30 minutes. The automation operator ID NETOPER2 (defined in CGLOBAL) starts the active monitoring. These values can be overridden at the restype or resname level. The STATUS value (in this case ACT) is taken from the ACTMON DEFAULTS entry unless it is overridden at a lower level.
In this example, any resources that are of an NCP resource type (PU T4/5) are actively monitored every 10 minutes. All other values, such as STATUS and OPID, must be defined at the ACTMON DEFAULTS or ACTMON SA level, or defined for each NCP to be actively monitored.
```
ACTMON NCP,OPTION=SA,RESTYPE=NCP,INTVL=00:10
```
In this example, active monitoring is started for resource NCP1, which is an NCP. Using the previous examples, it is monitored every 10 minutes (from the ACTMON NCP statement) on automation operator NETOPER2 (from the ACTMON SA statement) looking for a status of ACT* (from the ACTMON DEFAULTS statement).
```
ACTMON NCP1,OPTION=SA,RESTYPE=NCP
```
In this example, PU01 is a PU resource type and managed by the AON/SNA subarea option:
```
ACTMON PU01,OPTION=SA,RESTYPE=PU
```
Active monitoring is influenced by the following ACTMON definitions, if they exist:
```
ACTMON DEFAULTS,...
ACTMON SA,OPTION=SA,...
ACTMON PU,OPTION=PU,RESTYPE=PU,...
```
The PU resources managed by the AON/SNA subarea option are actively monitored every hour. NCP resources are actively monitored every 10 minutes. NCP1 is monitored every 30 minutes. NCP2 is monitored every 10 minutes (default).
```
ACTMON PU,OPTION=SA,RESTYPE=PU,INTVL=01:00
ACTMON NCP,OPTION=SA,RESTYPE=NCP,INTVL=10
ACTMON NCP1,OPTION=SA,RESTYPE=NCP,INTVL=30
ACTMON NCP2,OPTION=SA,RESTYPE=NCP
```
In this example, AONNET2 starts active monitoring for resources managed by the AON/SNA subarea option, except for NCP active monitoring, which is started by AONBASE:
```
AUTOOPS NETOPER,ID=(AONNET,2),...
AUTOOPS BASEOPER,ID=AONBASE,...
INSTALLOPT SA,ACTMONOP=NETOPER2,...
ACTMON NCP,OPTION=SA,RESTYPE=NCP,OPID=BASEOPER
```