Configuring OTM alarm notification

The CallPilot server generates alarms. Alarms with the following severity levels are sent out as SNMP traps to the NMS:

0 undefined
1 critical
2 major
3 minor

To configure OTM Alarm Notification to receive CallPilot SNMP traps

  1. From the OTM Alarm Notification window, select Configuration › Run Options.
    The Alarm Notification Run Options Property Sheet appears.

  2. Select the Control Files tab. The Control Files tab lists three files: Devices.txt, Config.txt, and Scripts.txt. You must modify each of these files.

  3. To modify Devices.txt, click Browse beside the file name.
    The Open dialog box appears with the file name selected.
    Note: The dialog box displays the default files that are provided when OTM is installed. The remainder of this procedure refers to the default file names.

  4. Click Open.
    The file opens in an editor where you can modify the file.

  5. In the Devices.txt file, add the following line:
    CALL_PILOT IP_ADDRESS_OF_SERVER
    where:
    CALL_PILOT is the name displayed under Device Type in the OTM Alarm Notification window. It can be any value.
    IP_ADDRESS_OF_SERVER is the actual IP address of the server that sends the traps to this NMS client.
    CALL_PILOT 47.235.12.85

  6. To modify Config.txt, click Browse beside the file name.  
    The Open dialog box appears with the file name selected.

  7. Click Open.
    The file opens in an editor where you can modify the file.

  8. In the Config.txt file, add the following block of text:
    device CALL_PILOT 6.1 6.2 6.3 6.4 {
    1.3.6.1.4.1.562.3.8.2.5.2.1.2.0 string $nbFltAlarmTimeStamp "Event Time"
    1.3.6.1.4.1.562.3.8.2.5.2.1.3.0 integer $nbFltAlarmEventCode "Error Code"
    1.3.6.1.4.1.562.3.8.2.5.2.1.4.0 integer $nbFltAlarmEventType "Alarm Type"
    1.3.6.1.4.1.562.3.8.2.5.2.1.5.0 integer $nbFltAlarmEventSeverity "Severity"
    1.3.6.1.4.1.562.3.8.2.5.2.1.8.0 string $nbFltAlarmOriginator "Component Name"
    1.3.6.1.4.1.562.3.8.2.5.2.1.9.0 string $nbFltAlarmDescription "Operator Data"
    }
    ...
    where:
    CALL_PILOT is the same name that is defined in the Devices.txt file.

  9. To modify sample_an_script.txt, click Browse beside the file name.
    The Open dialog box appears with the file name selected.

  10. Click Open.
    The file opens in an editor where you can modify the file.

  11. In the sample_an_script.txt file, add the following blocks of text:
    ...
    /* This is a sample definition for using a log file. All events sent to this notification are appended to the filename defined below. Note that Windows “long” file names are not supported. */
    notification file CALLPILOT_file {
    filename:="c:\Nortel\callpilot_log.txt";
    }
    ...
    /* This is a sample definition for using a numeric pager */
    notification npagerCALLPILOT_NumericPager {
    phone:="9,378-6388";
    ...
    /* if pager has PIN number insert */
    /* pin:=”101565”; */  
    }
    ...
    where:
    CALLPILOT_NumericPager is any name (it is used in the script code below)
    "9,378-6388" is the pager number
    ...
    /*******************************/
    /* Scripts for CALLPILOT Traps */
    /*******************************/
    /* Add the following lines */
    script CALLPILOTScript {
    /* This rule looks for all CallPilot events and remaps them to the
    OTM event format */
    rule check_critical {
    if ($CurrentTrapDevice="CALL_PILOT") {
     /* Prints event to OTM Alarm Notification console - optional*/
     send(con,"CALLPILOT alarm: ",
    $nbFltAlarmTimeStamp," - " ,
    $nbFltAlarmEventCode," - " ,
    $nbFltAlarmEventType," - " ,
    $nbFltAlarmEventSeverity," - ",
    $nbFltAlarmOriginator," - ",
    $nbFltAlarmDescription);
    /* Appends event to log file - optional*/
     send(CALLPILOT_file,"NGEN alarm: ",
    $nbFltAlarmTimeStamp," - " ,
    $nbFltAlarmEventCode," - " ,
    $nbFltAlarmEventType," - " ,
    $nbFltAlarmEventSeverity," - ",
    $nbFltAlarmOriginator," - ",
    $nbFltAlarmDescription);
    /* Sends message to numeric pager - optional */
    send(NGEN_NumericPager,$nbFltAlarmEventCode);
     }
    }
    }
    ...
    Note: By default, these three files are located in C:\Nortel\Common Data\Alarm Notification\Control Files, but this is user selectable on installation of OTM.

  12. After modifying the files, click OK.
    The Alarm Notification Run Options Property Sheet closes.

  13. In the OTM Alarm Notification window, select Maintenance › Start.
    CallPilot traps appear in the OTM Alarm Notification window list view as they are generated by the CallPilot server.