We also using alarm notifier on primary and secondary server and using the
setscript to block email on secondary if primary is up. Following are the some
part of setscript
$Server is the name of active spectroSERVER and $hostname is the local name of
the server:
==========================================================
SERVER="$9"
SERVER=`echo $SERVER | tr "[:lower:]" "[:upper:]"`
SERVER=`echo "$SERVER" | sed 's/.XXX.COM$//'`
# Get the hostname of the server
#--------------------------------------------------
HOSTNAME=`hostname`
HOSTNAME=`echo $HOSTNAME | tr "[:lower:]" "[:upper:]"`
HOSTNAME=`echo "$HOSTNAME" | sed 's/.XXX.COM$//'`
if [ "$SERVER" = "$HOSTNAME" ]
then
From: Henrichs, Joern [mailto:[email protected]]
Sent: Tuesday, July 20, 2010 4:44 AM
To: spectrum
Subject: WG: [spectrum] AW: HA/FO SANM
Hi List,
Garry just send me an excellent solution to the problem I mentioned with
regards to Alarm Notifier fault tolerance and he allowed me to share it.
The beauty of his solution is, that it uses an attribute on the model which has
the alarm instead of checking files of attributes on the vnm model.
The latter could have some performance impact, especially if a lot of alarms
are generated in a short period of time. Garry's solution just uses the SANM
functionality to pass any attribute of the alarmed model at almost no cost.
Mit freundlichen Grüssen - Best regards
Joern Henrichs
Senior System Engineer
ISS Service Desk Remote Betrieb
Computacenter AG & Co. oHG
Services & Solutions
Voltastraße 1, 60486 Frankfurt, Germany
Tel.: +49 69 97779 342
Mobile: +49 173 2946155
Fax: +49 69 97779 110
Short-Dial: 22342
E-Mail:
[email protected]<mailto:[email protected]>
WWW: www.computacenter.de<http://www.computacenter.de/>
Von: Garry Harst [mailto:[email protected]]
Gesendet: Montag, 19. Juli 2010 04:59
An: Henrichs, Joern
Betreff: Re: [spectrum] AW: HA/FO SANM
Hiya
Just trawling through the emails from Spectrum and found your email
I have a Primary / Secondary Spectrum installation and run Notifier on both
I've set it so whenever an alarm is checked the precedence value on the model
is checked.
On the primary if Precedence is 10 (primary running) it sends the message, if
the precedence is 20 it stops email processing
On the Secondary its the other way around - 20 = send , 10 do not send
So if the Primary server goes down completeley then precedence is now 20 so
secondary sends.
If Spectroserver stops on Primary the precedence is now 20 so secondary sends
If both are running but we have a comms error so they can;t see each other then
both send (can't see a way around this but its not a common issue)
Here is a line from the SetScript on the primary, hope it all flows from there
if [ "$SANM_0X12C0A" = "20" ]
then
echo "SS Secondary is running"
echo "Precedence = $SANM_0X12C0A"
exit 0
fi
On Fri, Jul 16, 2010 at 7:16 PM, Henrichs, Joern
<[email protected]<mailto:[email protected]>>
wrote:
Hi Jim,
we are running Notifiers only on the Main Location Server landscape for ease of
administration.
The Notifier itself is fault tolerant. If the primary SpectroSERVER application
crashes it reconnects to the secondary.
But be aware, that if the machine dies - you need to start the Notifiers
manually on the secondary server.
We have been thinking from time to time how we could run the same Notifiers on
both primary and secondary and process alarms depending on the SpectroSERVER
status, but we did not find a good way yet.
Cheers,
Joern
Joern Henrichs
Senior System Engineer
ISS Service Desk Remote Betrieb
Computacenter AG & Co. oHG
Services & Solutions
Voltastraße 1, 60486 Frankfurt, Germany
Tel.: +49 69 97779 342
Mobile: +49 173 2946155
Fax: +49 69 97779 110
Short-Dial: 22342
E-Mail:
[email protected]<mailto:[email protected]>
WWW: www.computacenter.de<http://www.computacenter.de/>
Von: Pfleger, Jim
[mailto:[email protected]<mailto:[email protected]>]
Gesendet: Dienstag, 15. Juni 2010 16:27
An: spectrum
Betreff: [spectrum] HA/FO SANM
Hello fellow Spectrum admins-
We're running Spectrum 9.1.3 on four landscapes, each with a primary and a
failover server, along with another landscape pair acting as a trap director
only. I've looked through the SANM documentation and the Wiki, but it's not
clear to me how best to set up SANM in this environment to be fault-tolerant.
It seems like we have two options:
1. Run SANM on every server, give each notifier process a unique name, and
restrict each notifier to alarms from that server via policy
2. Run SANM on just one landscape pair and have it manage alarms for all
landscapes
I'm not certain that method 1 is necessary, or even possible; method 2 may be
sufficient, since the odds of losing both machines in the same landscape seem
quite small.
Is there another option I haven't considered? How are y'all doing this?
Thank you,
Jim
--
JIM PFLEGER | Application Architect | Insight Networking |
insight.com<http://insight.com/>
o. 480.889.9680 f. 480.889.9599
[email protected]<http://[email protected]>
The information contained in this message and any attachment may contain
privileged or confidential information protected from disclosure. If you are
not the intended recipient, or an employee or agent responsible for delivering
this message to the intended recipient, you are hereby notified that any
review, dissemination, distribution or copying of this information is strictly
prohibited. If you have received this transmission in error, please notify the
sender immediately by replying to this message and destroying the original and
all copies. Thank you.
* --To unsubscribe from spectrum, send email to
[email protected]<mailto:[email protected]> with the body: unsubscribe spectrum
[email protected]<mailto:[email protected]>
-----------------------------------
Computacenter AG & Co. oHG, mit Sitz in Kerpen (Amtsgericht Köln HRA 18096)
Vertretungsberechtigte Gesellschafter:
Computacenter Aktiengesellschaft, mit Sitz in Köln (Amtsgericht Köln HRB 28384)
Vorstand: Oliver Tuszik (Vorsitzender), Dr. Karsten Freihube, Hans-Georg
Freitag, Frank Kottmann, Reiner Louis
Aufsichtsrat: Michael Norris (Vorsitzender)
Computacenter Management GmbH, mit Sitz in Köln (Amtsgericht Köln HRB 28284)
Geschäftsführer: Ulrich Irnich, Jürgen Stauber
Visit us on the Internet:
http://www.computacenter.de<http://www.computacenter.de/>
Visit our Online-Shop:
https://shop.computacenter.de<https://shop.computacenter.de/>
This email is confidential. If you are not the intended recipient, you must not
disclose or use the information contained in it. If you have received this mail
in error, please tell us immediately by return email and delete the document.
-----------------------------------
* --To unsubscribe from spectrum, send email to
[email protected]<mailto:[email protected]> with the body: unsubscribe spectrum
[email protected]<mailto:[email protected]>
-----------------------------------
Computacenter AG & Co. oHG, mit Sitz in Kerpen (Amtsgericht Köln HRA 18096)
Vertretungsberechtigte Gesellschafter:
Computacenter Aktiengesellschaft, mit Sitz in Köln (Amtsgericht Köln HRB 28384)
Vorstand: Oliver Tuszik (Vorsitzender), Dr. Karsten Freihube, Hans-Georg
Freitag, Frank Kottmann, Reiner Louis
Aufsichtsrat: Michael Norris (Vorsitzender)
Computacenter Management GmbH, mit Sitz in Köln (Amtsgericht Köln HRB 28284)
Geschäftsführer: Ulrich Irnich, Jürgen Stauber
Visit us on the Internet: http://www.computacenter.de
Visit our Online-Shop: https://shop.computacenter.de
This email is confidential. If you are not the intended recipient, you must not
disclose or use the information contained in it. If you have received this mail
in error, please tell us immediately by return email and delete the document.
-----------------------------------
* --To unsubscribe from spectrum, send email to
[email protected]<mailto:[email protected]> with the body: unsubscribe spectrum
[email protected]
----------------------------------------
This message is intended exclusively for the individual(s) or entity to
which it is addressed. It may contain information that is proprietary,
privileged or confidential or otherwise legally exempt from disclosure.
If you are not the named addressee, you are not authorized to read,
print, retain, copy or disseminate this message or any part of it.
If you have received this message in error, please notify the sender
immediately by e-mail and delete all copies of the message.
---
To unsubscribe from spectrum, send email to [email protected] with the body:
unsubscribe spectrum [email protected]
