Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations strongm on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

TM Alarm Notifications

Status
Not open for further replies.

SharpAdam

Vendor
Mar 12, 2007
57
US
Greetings all!

I'm working with TM on receiving SNMP traps from my CS1ks.

My working config involves sending a test alarm in 117, I can see the alarm show up in TM's alarm monitor, and I get an email sent to me according to my script.txt file.

Here is my issue -
I'm attempting to dial an alpha pager.
Code:
script Pagers
{
   function forward_apager() 
   {
      if ($CurrentTrapDevice = "CALL_SERVER") 
    	{
		send(adam_text_message, $ErrorCode, " : ",$OperatorData, ".");
    	}   
    }
     
    rule forward_apager_critical 
    {
    	if ($NormalizedSeverity = Critical ) 
    	{
        	forward_apager();
     	}
    }
}

When an alarm is received when this code is in script.txt, the alarm notification window disappears (and an error is generated in the Windows Application Log).

I am able to comment out the line
Code:
send(adam_text_message, $ErrorCode, " : ",$OperatorData, ".");
and the alarm notification utility doesn't crash (but of course I don't get paged either). So I know that my problem lies in either code above or in accessing the modem and sending the message.

I have a PCI softmodem installed on COM3. I have COM3 set under the notification tab of Alarm Notification Run Options.

If anyone has any thoughts on this I'd appreciate it!!
 
Sounds like a problem with the script....Do you have the following included in your script for an alpha pager? There is a default script that comes with the software (Sample_AN_script.txt) that can be modified, or you can copy the pager section into your existing script.




// Numeric and Alpha Pagers
// ****************************************************************************

// =======================================================================
// This is a sample definition for using a numeric pager
// To use, the phone number should be changed to your pager number
// and the notification (as well as the references to it) should be
// uncommented.
// =======================================================================

/*
notification npager sample_numeric_pager {
phone:="9,555-1212";
}
*/

// =======================================================================
// This is a sample definition for using an alpha pager
// To use, the phone number should be changed to your pager number,
// your PIN number should be added, and the notification (as well
// as the references to it) should be uncommented.
// =======================================================================

/*
notification apager sample_alpha_pager {
phone:="9,555-1212";
pin:="101565";
}
*/

script Pagers {
/*
function forward_apager() {
if ($CurrentTrapDevice = "CALL_SERVER" or $CurrentTrapDevice = "COMMON_MIB_DEVICE") {
send( sample_alpha_pager, $CurrentTrapSource,":", $AlarmCode, "!" );
}
else {
send( sample_alpha_pager, $CurrentTrapSource,":", $ErrorCode, "!" );
}
}

rule forward_apager_critical {
if ($NormalizedSeverity = Critical ) {
forward_apager();
}
}
*/
}
 
all I did was modify the sample script. I left the part where I define my pager off my post to avoid any spam pages ;) Not that anyone on the internet would spam me...

I'm pretty sure its.

I've even gone so far as to take out any variables....

Code:
notification apager adam_text_message {
   phone:="18009094602";
   pin:="<censored>";
}

script Pagers
{	
   function forward_apager() 
   {
      if ($CurrentTrapDevice = "CALL_SERVER") 
    	{
   		send(adam_text_message, "Testing");
    	}   
    }
     
    rule forward_apager_critical 
	{
    if ($NormalizedSeverity = Critical ) 
    {
        		forward_apager();
     			}
  	}
}

This still causes the application to crash.

I was able to make a bit of progress though. After "Alarm Notification" gets the alarm, I see the following...

--> Critical CALL_SERVER alarm received! INI000 - 2009 02 25 17 32 00 <blah blah blah>
Error: Failed to open notify spool file 'C:\Program Files\Nortel\Telepony Manager\Common Data\Alarm Notification\Temporasy F|3720.1176533362'

And yes, they really did spell Temporary incorrectly...

I had to pull a screen shot in order to get this information as the app crashes right after this appears.

I'm off to the pic to research this one and will post back with details of my search.
 
and for what its worth, I'm not actually INI'ing my switch everytime I want to test an alarm. I know someone is wondering about it. I'm using 117's TEST ALARM command.
 
After a reboot of the TM server, I'm getting application crash error reports on AlrmNotify.exe.

I'm thinking a TM reload is in order...
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top