I have TM3.2, CS-1000MG v5.5 trying to get Alarm notification to work. Been studying the books to try and figure this out. I see the alarms in TM System Alarms & the web alarms. I config my device. I set up email. But when I start the Alarm Notification. I see nothing in the Network event(top) pane. The Console(Bottom) pane just has the compiling file stuff and Beginning execution in the Alarm Notification window. No errors. No emails. Any help appreciated.
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!
TM3.2 Alarm Notification Console 1
- Thread starter Dphone
- Start date
-
1
- #2
Have you issued the "set open alarm" command in Ld 117? This command allows the PBX is send SNMP traps to the TM server's IP address. If you haven't yet done this, then consult the IO guide for the proper syntax.
If you've done issued this command and it's still not working, make sure that you properly set up your devices.txt file -- there are examples in the stock devices.txt file that clue you into how this file should be formatted.
Once you get traps to appear in the window, if you want to test your email script, you can send test critical messages in ld 117, using the "test alarm" command. For example, if you enter:
test alarm dta 011
.... it should send a critical alarm to your Alarm Notification window.
If you've done issued this command and it's still not working, make sure that you properly set up your devices.txt file -- there are examples in the stock devices.txt file that clue you into how this file should be formatted.
Once you get traps to appear in the window, if you want to test your email script, you can send test critical messages in ld 117, using the "test alarm" command. For example, if you enter:
test alarm dta 011
.... it should send a critical alarm to your Alarm Notification window.
- Thread starter
- #3
I have issued the set open_alarm. I have the device set to the IP address of you our Meridian1. I see the alarms in the TM System Alarms & the web alarms but not in the Console. I changed the script to notify my email also. It doesn't. I didn't expect to get an email until I can get the alarms to show up on the upper part of the console.
By default, only critical alarms will show up in the console portion of the Alarm Notification. Also, unless you've changed the stock script, you should have a file in the root of the c: drive called sample_log.txt
This file should have all of the critical alarms that have arrived since you first ran the alarm notification application.
If your critical alarms are showing up in the upper portion of the alarm notification window but are not showing up in the console and/or log, then I would suggest that you find a copy of the default (stock) script and start over.
This file should have all of the critical alarms that have arrived since you first ran the alarm notification application.
If your critical alarms are showing up in the upper portion of the alarm notification window but are not showing up in the console and/or log, then I would suggest that you find a copy of the default (stock) script and start over.
- Thread starter
- #5
Jephph thanks for help. I don't have a sample_Log.txt file. in C: The alarms are not showing up in the upper or lower portion of the alarm notification window. In the lower portion all I have is the "Compiling the files'C:\Program Files\Nortel\Telephone Manager\Common Data\Alarm Notification\Control Files\my_scripts.txt'" and Beginning execution at: and the date and time.
Dan -- regarding my last post:
I'm going to assume that your traffic light is red -- which is actually the color that you want, despite it being counter-intuitive. A red traffic light indicates that your scripts got started properly.
Because you're telling us that your Web Alarm application is showing alarms properly, I'm going to guess that your problem is related to having an improperly formatted DEVICES file. If the PBX that you're monitoring is 5.0 or above, you need to make sure that you use "COMMON_MIB_DEVICE" in your DEVICES file, rather than "Meridian1".
As an example, if you have a 5.5 PBX with an IP address of 137.135.128.253 that you want the Web Alarm app to ID as "Jasper", you would place this line as the last line of your DEVICES file:
COMMON_MIB_DEVICE 137.135.128.253 Jasper
Save the change (make sure that you delete the old value so that you don't have duplicate mappings), then restart your scripts by toggling the traffic light to green then back to red. Log into the PBX, and that should generate a couple of events that you should see in the upper window of the Alarm Notification app.
Interestingly enough, I found that you can format the DEVICES file improperly, but the Web Alarms app may function normally if the device type is wrong (i.e. Meridian1) in the DEVICES file.
Hopefully, this is what is happening to you, because it sounds like you're very very close.
I'm going to assume that your traffic light is red -- which is actually the color that you want, despite it being counter-intuitive. A red traffic light indicates that your scripts got started properly.
Because you're telling us that your Web Alarm application is showing alarms properly, I'm going to guess that your problem is related to having an improperly formatted DEVICES file. If the PBX that you're monitoring is 5.0 or above, you need to make sure that you use "COMMON_MIB_DEVICE" in your DEVICES file, rather than "Meridian1".
As an example, if you have a 5.5 PBX with an IP address of 137.135.128.253 that you want the Web Alarm app to ID as "Jasper", you would place this line as the last line of your DEVICES file:
COMMON_MIB_DEVICE 137.135.128.253 Jasper
Save the change (make sure that you delete the old value so that you don't have duplicate mappings), then restart your scripts by toggling the traffic light to green then back to red. Log into the PBX, and that should generate a couple of events that you should see in the upper window of the Alarm Notification app.
Interestingly enough, I found that you can format the DEVICES file improperly, but the Web Alarms app may function normally if the device type is wrong (i.e. Meridian1) in the DEVICES file.
Hopefully, this is what is happening to you, because it sounds like you're very very close.
- Thread starter
- #8
Only items that match your script are going to show up in your "Console" section. Also, by default, they'll show up in the c:\sample_log.txt file. By default, only critical alarms will trigger a console/log entry.
Earlier in this thread, I explained how to trigger a test alarm in LD 117. Scroll up and follow those instructions and you should see a critical alarm in the upper section and you should see an entry in your Console window (as well as an entry in the c:\sample_log.txt file).
Give it a try and let us know if that works as advertised or not.
Warning: because you're on 5.5, email notification will not work with the stock script -- call it an oversight on Nortel's part, or whatever, but you'll need to make a script modification in order to get that to work.
Respond back with the results of the test critical alarm, and I'll clue you into what you have to change in order to get email notification to work.
Earlier in this thread, I explained how to trigger a test alarm in LD 117. Scroll up and follow those instructions and you should see a critical alarm in the upper section and you should see an entry in your Console window (as well as an entry in the c:\sample_log.txt file).
Give it a try and let us know if that works as advertised or not.
Warning: because you're on 5.5, email notification will not work with the stock script -- call it an oversight on Nortel's part, or whatever, but you'll need to make a script modification in order to get that to work.
Respond back with the results of the test critical alarm, and I'll clue you into what you have to change in order to get email notification to work.
- Thread starter
- #10
- Thread starter
- #12
- Thread starter
- #13
Ok -- you will not get email to work until you solve that problem. Did you save a copy of the original SCRIPTS.TXT file?
If so, activate that original script, then send a test critical alarm to see if you can get the console to log that critical alert. Don't modify the original SCRIPTS.TXT file at all -- it should work for this purpose right out of the box.
If you didn't keep a copy, then let me know and we can get you a copy of that script.
If so, activate that original script, then send a test critical alarm to see if you can get the console to log that critical alert. Don't modify the original SCRIPTS.TXT file at all -- it should work for this purpose right out of the box.
If you didn't keep a copy, then let me know and we can get you a copy of that script.
- Thread starter
- #15
- Thread starter
- #16
Download these in the next 24 hours, before they evaporate:
1) Default scripts.txt:
ftp://155.70.16.252/incoming/uswo/scripts.txt
2) image of what you should see after generating a test critical alert after activating the default scripts.txt file:
ftp://155.70.16.252/incoming/uswo/Alarm_notification.jpg
3) Working scripts.txt file that has the correct syntax in the "email" section to allow critical alarming from a version 5.5 PBX:
ftp://155.70.16.252/incoming/uswo/scripts-email_working.txt
---------------
Suggested action:
* copy the 1st file to c:\program files\nortel\telephony manager\common data\alarm notification\control files folder.
* Activate the default scripts.txt
* Send a DTA 011 test alarm and see if you get the result that is reflected in the JPG file that you downloaded.
* Assuming that all is working correctly, edit the scripts-email_working.txt file's "email" section so that you replace all of the XXXXX's with your company's data. Activate that script and send another test DTA 011 alert and see if your email server sends it to the address that you configure.
Have fun and good luck.
1) Default scripts.txt:
ftp://155.70.16.252/incoming/uswo/scripts.txt
2) image of what you should see after generating a test critical alert after activating the default scripts.txt file:
ftp://155.70.16.252/incoming/uswo/Alarm_notification.jpg
3) Working scripts.txt file that has the correct syntax in the "email" section to allow critical alarming from a version 5.5 PBX:
ftp://155.70.16.252/incoming/uswo/scripts-email_working.txt
---------------
Suggested action:
* copy the 1st file to c:\program files\nortel\telephony manager\common data\alarm notification\control files folder.
* Activate the default scripts.txt
* Send a DTA 011 test alarm and see if you get the result that is reflected in the JPG file that you downloaded.
* Assuming that all is working correctly, edit the scripts-email_working.txt file's "email" section so that you replace all of the XXXXX's with your company's data. Activate that script and send another test DTA 011 alert and see if your email server sends it to the address that you configure.
Have fun and good luck.
- Thread starter
- #18
Thanks for all your help. It is working. The Ld 117 Test alarm was not giving me a Critical Alarm in the upper Panel. It was just giving me a "Info" under Severity instead of "Critical". Once I forced a critical alarm to happen it also display in the lower console and sent me email.
- Thread starter
- #20
- Status
Similar threads
- Locked
- Question