Hi all,
It has been a long time since I updated this post. I had been working with
support and had opened an enhancement request to have AN as a high
availability product. However, I believe until CA Engineering gets enough
clients using this scenario they will not include in their development path.
I did test the ServiceDesk integration in FT and OneClick created duplicate
tickets in SD and closed the old ones. I have received email from support
that this issue will be fixed in SPECTRUM 8.1 HF 16 and 9.0 HF 1 the details
are as follows:
Here is how this will work in a failover situation::
1) When failing over from primary to secondary, primary alarms that are sent
to service desk will not be cleared.
2) As secondary becomes active existing issues in the network will we
identified by the secondary and alarms will be generated.
3) At the point where the primary becomes active again as issues in the
network are identified new alarms will be created. Secondary alarms will not
be cleared in Service Desk. Original primary alarms as they are resolved
will not be cleared in Service Desk but new alarms identified will.
Cheers,
Saurabh
On Wed, Jul 23, 2008 at 11:32 AM, Saurabh Bohra <[EMAIL PROTECTED]>wrote:
> Hi all,
>
> Thanks for all your suggestions. In last 3 days I had been doing the
> testing of all the suggestions provided by the list users and my conclusion
> is AlarmNotifier will generate duplicate notifications when Primary SS fails
> to FT SS.
>
> The scenarios tested by me were as follows
>
> Scenario 1 - FT SS in warm standby.
> Test1 - Generate device down alarm while Primary SS is up. Shutdown Primary
> SS.
> Result - AN on primary SS sends notification. When Primary SS was shutdown,
> FT SS will activate the models and will regenerate all the alarms at that
> point AN on FT SS will resend the notifications (duplications).
>
> Test2 - Bring the device back up while FT SS is running and then Start the
> Primary SS
> Result - Only one notification sent from AN on FT SS. (worked as expected)
>
> Test3 - When FT SS is running raise a device down alarm
> Result - AN on FT sends notification
>
> Test 4 - Bring back Primary SS, while the alarm is still there on FT SS
> (from Test3)
> Result - AN on primary resends notification (duplications)
>
> At this point I called up support and was suggested to have FT SS in hot
> standby so that the secondary SS is also polling
>
> Scenario 2 - FT SS in hot standby.
> Same test cases were run as Scenario 1 and result was also the same.
>
>
>
> After these tests definitely my NSM integration will have duplicate events
> sent. I have not yet tested my ServiceDesk Integration.
>
> Friends let me know if you have any other suggestions.
>
> Regards,
> Saurabh
>
>
>
> On Fri, Jul 18, 2008 at 8:16 AM, Maslobojev, Alexander <
> [EMAIL PROTECTED]> wrote:
>
>> Hi Saurabh,
>>
>> we are running AlarmNotification on both servers: primary and secondary.
>> In the notification script we have code which checks the name of the
>> SpectroSERVER where Alarm comes from and compares it with the local
>> hostname. If it is the same then alarm will be sent, if not then the
>> currecnt server is secondary and alarm will not be sent.
>>
>> Here is the example in Perl:
>>
>> $spsrv->{'HOSTNAME'} = get_host();
>> $spsrv->{'SpectroServer'} = $ARGV[8];
>>
>> my $tmp_host = (split(/\./,$spsrv->{HOSTNAME}))[0]; # in case of fqdn
>> my $srv_active = (split(/\./,$spsrv->{'SpectroServer'}))[0]; # in case of
>> fqdn
>> unless ($srv_active eq $tmp_host) {
>> $spsrv->err_exit("VNM: $ss_active. The server is secondary, alarm
>> will not be sent");
>> }
>> I hope this helps.
>>
>> Regards,
>>
>> *Alexander Maslobojev
>> HIM Network & Security
>>
>> SAP Hosting AG & Co. KG*
>> *****Raiffeisenring 15*
>> *D-68789 St. Leon-Rot Germany*
>> *****T +49 6227 762647*
>> *****F +49 6227 7835255*
>> *M +49 160 3603700**
>> E** [EMAIL PROTECTED]
>> ***
>> Sitz der Gesellschaft/Registered Office: St. Leon-Rot,
>> Deutschland/Germany; Persönlich haftende Gesellschafterin/Partner liable to
>> unlimited extent: SAP AG, Vorstand/Executive Board: Henning Kagermann
>> (Sprecher/CEO), Léo Apotheker (Sprecher/CEO), Werner Brandt, Claus
>> Heinrich, Gerhard Oswald, John Schwarz, Peter Zencke; Vorsitzender des
>> Aufsichtsrats/Chairperson of SAP Supervisory Board: Hasso Plattner;
>> Registergericht/Commercial
>> Register Mannheim HRB 350269
>>
>> Geschäftsführende Kommanditistin/Managing limited partner: SAPHosting
>> Beteiligungs GmbH; Geschäftsführer/Managing Director: Thomas Besthorn,
>> Wolfgang Krips; Registergericht/Commercial Register Mannheim HRB 351725
>>
>> Diese E-Mail kann Betriebs- oder Geschäftsgeheimnisse oder sonstige
>> vertrauliche Informationen enthalten. Sollten Sie diese E-Mail irrtümlich
>> erhalten haben, ist Ihnen eine Kenntnisnahme des Inhalts, eine
>> Vervielfältigung oder Weitergabe der E-Mail ausdrücklich untersagt. Bitte
>> benachrichtigen Sie uns und vernichten Sie die empfangene E-Mail. Vielen
>> Dank.
>>
>> This e-mail may contain trade secrets or privileged, undisclosed, or
>> otherwise confidential information. If you have received this e-mail in
>> error, you are hereby notified that any review, copying, or distribution of
>> it is strictly prohibited. Please inform us immediately and destroy the
>> original transmittal. Thank you for your cooperation.
>>
>> ------------------------------
>> *Von:* Saurabh Bohra [mailto:[EMAIL PROTECTED]
>> *Gesendet:* Freitag, 18. Juli 2008 00:34
>> *An:* spectrum
>> *Betreff:* [spectrum] Alarm Notifier in Fault Tolerant
>>
>> Hi all,
>>
>> We have a client who wants Alarm Notifer to run in Fault Tolerant
>> environment. So when Primary SS is running then the Notifier on Primary SS
>> should send notification. However if Secondary SS is running the Notifier
>> from secondary SS should send notifications.
>>
>> The condition is that they want to automatically switch over to notifier
>> on secondary SS when primary SS fails.
>>
>> Thanks in advance,
>> Saurabh
>>
>> - --To unsubscribe from spectrum, send email to [EMAIL PROTECTED] with
>> the body: unsubscribe spectrum [EMAIL PROTECTED]
>>
>>
>
> - --To unsubscribe from spectrum, send email to [EMAIL PROTECTED] with
> the body: unsubscribe spectrum [EMAIL PROTECTED]
>
>
---
To unsubscribe from spectrum, send email to [EMAIL PROTECTED] with the body:
unsubscribe spectrum [EMAIL PROTECTED]
