Thanks for the great response Cristi. The 2 SSs will not be configured to be distributed. They will actually be seperate pollers with just one SS fowarding alarms to the other SS (at least this is what the customer is looking for). As a follow up question, can SSs be 'daisychained' in that fashion? What are the various methods for sending alarms between SSs? Also, true the Alarm Notifier is not fault tolerant? But, if you have the same policy/filter configurations on both the primary and secondary, then they should both behave the same when either box is active. Correct? Thanks again.
Calvin On Tue, Apr 7, 2009 at 5:02 PM, Mitrana Cristian < [email protected]> wrote: > Calvin Lane wrote: > >> Hello everyone, >> >> I have a customer that wants to design a failover/fault tolerant >> soluction such that all SPECTRUM data/events/alarms are funnelled through >> one primary SpectroServer that forwards alarms over to a Netcool object >> server. Please refer to the attached diagram and let me know if this >> conceptual design is feasible. Thanks. >> >> > Using Spectrum just to send alarms kind of defeats the purpose ... as its > primary function is to act as a NFM and not as a NPM. > The above scenario implies 2 SS with failover backups (distributed ?). As > it was discussed in the past on the list, the Alarm Notifier (which I assume > you must be using it to forward alarms to Netcool) is not fault tolerant so > you really don't have an option in the proposed scenario. > Maybe if you monitor the failover process (from Netcool ?) you could > trigger Alarm Notifier start on the failover and then stop it on failback. > Look under the 9.0 documents for failover to see how this kind of monitoring > could be done. > > hth, > -- > Cristi Mitrana > > --- > 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]
