Configuring the Alert Monitor › Forward Alerts

Forward Alerts

Alerts are normally displayed on the alert monitor; however, you can define them so that they are forwarded automatically to the following platforms:

• EM Console in CA NSM NetMaster Option
• UNIX platforms as SNMP traps
• CA NetMaster NM for SNA or Tivoli NetView (TME10) systems, as generic alert NMVTs
• CA Service Desk servers, as CA Service Desk requests or incidents

You can apply filter criteria to forward different types of alerts to different platforms.

Implement Alert Forwarding

You implement alert forwarding by using Customizer parameter groups.

Note: TNGTRAP and SERVICEDESK do not have clear alert events. Only active alerts and considerations are forwarded.

To implement alert forwarding

1. Enter /PARMS at the prompt.

   The Customizer : Parameter Groups list appears.

2. Enter U beside the $NM ALERTS parameter group in the Interfaces category.

   The ALERTS - Alert Monitor Interface panel appears.

3. Complete the following field:

   Dest Type

   Specifies the type of alert forwarding to use.

   When you press Enter, the fields dynamically change to match the specified destination type.

4. (Optional) Press F8 (Forward) and repeat step 3 for each Definition ID, as required.

   Note: For more information about the fields, press F1 (Help).

5. Press F6 (Action).

   The details are applied.

6. Press F3 (File).

   The details are saved.

Forward to CA NSM NetMaster Option

To receive alerts on CA NSM NetMaster Option, you must load the rules to reformat the alert messages for display on the EM Console.

To forward alerts to the EM Console in CA NSM NetMaster Option

1. Use FTP to download the message definition rules in binary mode from the UNIEMMSG member of your CC2DSAMP data set created at installation. For example, using the Windows FTP client from the prompt:

   >ftp myhost
   Connected to myhost.mycompany.com.
   User (myhost.mycompany.com:(none)): user01
   331 Send password please. 
   Password: xxxxxxxx 
   230 USER01 is logged on. Working directory is "/u/users/user01". 
   ftp>cd "prefix.NMC1.CC2DSAMP" 
   250 The working directory "prefix.NMC1.CC2DSAMP" is a partitioned data set 
   ftp>binary 
   200 Representation type is Image 
   ftp> get uniemmsg uniemmsg.txt 
   200 Port request OK. 
   125 Sending data set prefix.NMC1.CC2DSAMP(UNIEMMSG) FIXrecfm 80 
   250 Transfer completed successfully. 
   ftp: 3200 bytes received in 0.67Seconds 4.77Kbytes/sec. 
   ftp>quit
   

2. From a Windows prompt on the destination CA NSM NetMaster Option EM Server, load the message definition rules from the downloaded file. Enter the following command at the prompt to define the rules to event management:

   cautil -f "uniemmsg.txt"
   

3. Enter the following command to load the rules:

   oprcmd opreload
   

4. On CA NetMaster NM for TCP/IP, set the alert forwarding destination to TNGTRAP.

Forward as an SNMP Trap Definition

The MIB definition for alerts forwarded as SNMP traps is provided in member $AMTRAP, supplied in the dsnpref.NMC1.CC2SAMP data set. You can download this member to your UNIX system and compile it.

Note: When copying this member to your UNIX system, you can rename it to avoid problems on some UNIX systems where the $ sign has special meaning.

The supplied MIB defines two traps with the following object identifiers:

• $AMTRAP = 1.3.6.1.4.1.1126.1.2.1.2 (for an alert)
• $AMTRAPC = 1.3.6.1.4.1.1126.1.2.1.3 (when an alert is cleared)

Forward to CA Service Desk

Before you can forward alert details to CA Service Desk to create requests, you must implement CA Service Desk Integration. For more information, see the CA Common Services for z/OS CA Service Desk Integration Guide.

Do not forward any alerts to CA Service Desk until CA Service Desk integration is completely and correctly implemented; otherwise, all alert forwarding requests to CA Service Desk fail.