Will not work my my requirement as $SERVER is the name of SS on which the alarm is generated.
Saurabh Bohra O: 860-766-0842 | M: 860-385-3597 | e-mail: [email protected] From: Belliveau, Alan P [mailto:[email protected]] Sent: Tuesday, February 11, 2014 2:51 PM To: Bohra, Saurabh; spectrum Subject: RE: SANM / AN in DSS environment I haven't had time to try this...but check this out.. Issue : How can the SPECTRUM Alarm Notifier be configured to run in a fault tolerant environment? Issue : AlarmNotifier fault tolerance Issue : Alarm Notifier does not fail over when the primary server fails. How can the Alarm Notifier be configured so that alarm notifications will still occur whent the secondary server is active? Cause : Alarm Notifier is not a fault tolerant application. Fix : Alarm Notifier can be configured to run in a fault tolerant environment so that alarm notification still occurs when the primary server is down and the secondary server is active. In order to do this, the AlarmNotifier application must be running on both the primary and secondary SpectroSERVERs. The SetScript file (located in the <SPECROOT>/Notifier directory) will need to be modified on both the primary and the secondary machine to include an if/then statement that utilizes the $SERVER parameter. On the primary machine, you will need to add an if/then statement to the SetScript file so that if the $SERVER parameter equals the name of the primary SpectroSERVER, then send the email notification. On the secondary machine, you will need to add an if/then statement to the SetScript file so that if the $SERVER parameter equals the name of the secondary SpectroSERVER, then send the email notification. If you are using the UpdateScript and ClearScript, the same modifications will need to be made. Assumption: Primary Server hostname = specpri Secondary Server hostname = specsec SetScript on Primary Server if [ "$SERVER" = "specpri" ] then < ... script to send email here ... > else < ... do not send email ... > fi SetScript on Secondary Server if [ "$SERVER" = "specsec" ] then < ... script to send email here ... > else < ... do not send email ... > Fi Let me know if this makes sense.... Alan Belliveau Sr Support Engineer CA Technologies | 273 Corporate Dr Suite 200 | Portsmouth, NH 03801 Office: +42511 | [email protected] <mailto:[email protected]>[CA]<http://www.ca.com/us/default.aspx>[Facebook]<https://www.facebook.com/CATechnologies>[Twitter]<http://twitter.com/CAInc>[LinkedIn]<http://www.linkedin.com/company/1372?goback=.cps_1244823420724_1> Should you have any concerns, please feel free to contact my manager:- Max McGregor, Manager, CA Technologies Support Tel: +1-508-628-8650 [email protected]<mailto:[email protected]> P Please consider the environment before printing this e-mail. From: Bohra, Saurabh [mailto:[email protected]] Sent: Tuesday, February 11, 2014 2:43 PM To: spectrum Subject: RE:[spectrum] SANM / AN in DSS environment Thanks everyone who responded to my emails and pointed me to "Redundant AlarmNotifier on http://www.dachsug.ch/wiki/index.php/Alarming"; page. After reading the notes from this page "Every alarm has an attribute with the assiciated precedense. On a primary SpectroServer this value is normmally "10", on the backup SS it is "20".", my gut feeling was this approach will NOT work in my case as we have *distributed* environment. This solution will only work 1. If you have a standalone environment OR 2. If you are running AN on *ALL* the DSS. In my case I want to run AN *only* on MLS and FT MLS. Some of you will ask why do I say the above. Take in consideration the following scenario (I tested it out in our production environment, yes PRODUCTION). - Created Test AN on MLS and FT MLS to start with processd. Modified the SetScript based on the Wiki page and start AN. Configured a SANM policy for it. 1. Generate an alarm on primary DSS-2 (non MLS SS) 2. ALARM PRECEDENCE was 10, MLS AN picked up the code and sent email notification to me. 3. Shut down my MLS SS (simulate a SS crash). processd, AN and other processes were running. 4. Generate the same alarm on primary DSS-2. 5. ALARM PRECEDENCE was 10, MLS AN picked up the code and sent email notification to me. 6. Shut down my MLS SS and processd (to simulate something really went south). 7. Generate the same alarm on primary DSS-2. 8. ALARM PRECEDENCE was 10, my MLS was *DOWN* and so *NO* email. So configuring AN in the way suggest in the Wiki link will not solve my problem. I have another idea which I am currently pursuing to make AN running on MLS and FT MLS smart enough to automatically send out emails in any scenarios (assuming at least one of them is running :)). Thanks, Saurabh Bohra O: 860-766-0842 | M: 860-385-3597 | e-mail: [email protected]<mailto:[email protected]> From: Bohra, Saurabh Sent: Monday, February 10, 2014 11:07 AM To: spectrum Subject: [spectrum] SANM / AN in DSS environment All, We have a distributed spectrum environment. I want to run AN only on my MLS and Backup MLS servers. Currently when an alarm passes my SANM filter for any landscape both the ANs (primary and the one on FT MLS servers) sends emails (duplicate). Is there a way to make AN running on *FT MLS* server smart enough to *automatically* send emails *ONLY* if Primary SS/AN is down? Thanks, Saurabh Bohra Sr. Network Mgmt Systems Analyst ESPN Inc. O: 860-766-0842 | M: 860-385-3597 | e-mail: [email protected]<mailto:[email protected]> * --To unsubscribe from spectrum, send email to [email protected]<mailto:[email protected]> with the body: unsubscribe spectrum [email protected]<mailto:[email protected]> * --To unsubscribe from spectrum, send email to [email protected]<mailto:[email protected]> with the body: unsubscribe spectrum [email protected]<mailto:[email protected]> --- To unsubscribe from spectrum, send email to [email protected] with the body: unsubscribe spectrum [email protected]
<<inline: image001.jpg>>
<<inline: image002.jpg>>
<<inline: image003.jpg>>
<<inline: image004.jpg>>
