Prompt	Comment
Notifier Name:	Notifier Name (optional) is the user-defined name of the Alert.
Command Line:	The name of and path to the Third Party Software. "Tokens" can be placed between alphanumeric characters, words to control startup parameters. When a Token is found, it is replaced with dynamic content represented by the token. Example of a valid Third Party Software paths\names: Local drive: C:\UTILS\ALERTALL.EXE Network drive: \\NTSERVER\C$\UTILS\ALERTALL.EXE Access permissions relating to using UNC paths apply. The account ipMonitor runs within must have permission to read and run this file on the remote network machine.
Alert Parameters:	Alert Parameters determine what details will be reported in the Alert String. Alert Range: Configurable Alert Ranges make it possible to receive all possible alerts notifications or only some of them.

Notes regarding Spawn 3rd Party Software Alerts

1. "Notifier Name" is simply for organization of the configured content. It doesn't have anything to do with binding Alerts to Profiles. Multiple alerts can have the same name without interfering with each other.

2. "Alert Range" makes it possible to select which triggered Alerts will be acted on. For example, a senior administrator might be Alerted only if the event is not handled in a timely manner by someone else. By default the value of 1- is supplied (note, no terminating number), meaning email will be sent the first Alert and all subsequent Alerts. Ranges work in exactly the same manner that printing ranges work in Microsoft Word. 1-3 would Alert 1st, 2nd & 3rd Alerts. 1,2,4 would Alert 1st, 2nd & 4th Alerts, skipping the 3rd. 1-3,6-9 would Alert 1st through 3rd, then skip 4th & 5th and resume alerting for 6th through 9th.

3. When configuring the Alert to spawn a batch file, you must call CMD.EXE and pass the name of the batch file as a parameter.
   eg.
   Full path to exec: c:\winnt\system32\cmd.exe
   Command line parameters: /C c:\test.bat %n "%s"

4. Tokens are shown below.

   Tokens
   %%	a single "%"
   %D	date (YYYY-MM-DD)
   %T	time (HH:MM:SS)
   %a	Monitor: address field (short format)
   %A	Monitor: address field (long format)
   %b	Monitor: status (1 for UP, 0 for down)
   %s	Monitor: status full text
   %t	Monitor: type
   %i	Monitor: internal ID
   %n	Monitor: name
   %c	Monitor: comment
   %f	Monitor: frequency
   %F	Monitor: error frequency
   %N	Monitor: notify failures
   %m	Monitor: maximum duration
   %M	Monitor: maximum alerts
   %S	Monitor: number of alerts sent
   %x	Monitor: continuous failures
   %X	Monitor: continuous critical failures
   %p	Profile: name
   %P	Alert: name
   %qa	SNMP Trap: IP address from last Trap received
   %qb	SNMP Trap: Specific Trap identifier from the last Trap (applies to    Enterprise specific Traps only)
   %qc	SNMP Trap: Community from the last Trap
   %qd	SNMP Trap: Textual description of the Trap from the last Trap:    "Cold Start", "Warm Start", "Link Down", "Link Up",    "Authentication Failure", "egp Neighbor Loss",    "Enterprise Specific"
   %qe	SNMP Trap: Enterprise used for the last Trap

   example:
   C:\UTILS\GETPERF.EXE %a %m
   C:\UTILS\GETPERF.EXE 10.10.10.2 300