Second Notification subscription through a BSD server
Home  » Operations Manager  » Second Notification subscription through a BSD server

Second Notification subscription through a BSD server
Posted: Tue, Jan 19, 2010 4:55 PM :: Rank: 0
Author
Points: 360
Level: System Center Hero

Hey guys,

I am going to create the second Notification Channel as the redundancy. This channel is going through a BSD server, the server admin has already configured the relay on it, but I still cannot get the alert from it.

The designation is: Once the Exchange server is down, SCOM can still send alerts to my Rogers Cell email account, like cellnumber@pcs.rogers.com. I sent an email from my outlook to the cell account, and it works. I disabled the Exchange channel in SCOM, after a while, when a new alert came out, SCOM said failed to send notification over smtp protocol to my outlook email account, but didn't transfer it to my cell.

Can anybody help me with this? Thanks in advance.

Peter

 

   Report Abuse
Re: Second Notification subscription through a BSD server
Posted: Wed, Jan 20, 2010 3:53 AM :: Rank: 0
Author
Points: 30179
Level: System Center Expert
Hi Peter,



three things to check:

1) examine the RMS Operations Manager log. Maybe you'll see some error message with details why email sending failed.

2) log on to your RMS and try to send a test mail to this account through your BSD server using telnet: http://blogs.crsw.com/mark/archive/2006/07/06/2032.aspx

This way you can rule out firewall, authentication issues.

3) examine the logs on the smtp server to find out what happened. maybe the mail is rejected or there's some trouble relaying the mail.



cheers,

Stefan

http://www.code4ward.net
Accepted Answer
   Report Abuse
Re: Second Notification subscription through a BSD server
Posted: Thu, Jan 21, 2010 5:55 PM :: Rank: 0
Author
Points: 360
Level: System Center Hero
Thanks Stefan,

Tested sending email via Telnet, works fine. Looks like firewall and authentication are configured correctly.

I found the reason, it's because of the 'Subscription Criteria' settings. I am confused what 'Conditions' of Criteria I should choose? to make it sending all alerts when the exchange goes down.



Thanks,

Peter
   Report Abuse
Re: Second Notification subscription through a BSD server
Posted: Fri, Jan 22, 2010 3:44 AM :: Rank: 0
Author
Points: 30179
Level: System Center Expert
In the criteria section you could choose: raised by any instance of a specific group and include all exchange related groups.



cheers
   Report Abuse
Re: Second Notification subscription through a BSD server
Posted: Mon, Jan 25, 2010 12:38 AM :: Rank: 0
Author
Points: 360
Level: System Center Hero
Thanks Stefan. This is what I want. Great help!



Peter
   Report Abuse
Re: Second Notification subscription through a BSD server
Posted: Thu, Feb 04, 2010 11:45 AM :: Rank: 0
Author
Points: 360
Level: System Center Hero
Stefan, there comes another task,

How can I monitor the BSD server itself. How to monitor the SMTP protocol on this BSD server?



Thanks,

Peter
   Report Abuse
Re: Second Notification subscription through a BSD server
Posted: Thu, Feb 04, 2010 1:40 PM :: Rank: 0
Author
Points: 30179
Level: System Center Expert
Peter, the easiest way would be to configure a port monitor to see if port 25 is listening on the BSD server.



cheers,

Stefan
   Report Abuse
Re: Second Notification subscription through a BSD server
Posted: Fri, Feb 05, 2010 2:52 PM :: Rank: 0
Author
Points: 360
Level: System Center Hero
Cool! Thanks Stefan.

I put two watch nodes to monitor the DMZ server port 25, and got the alerts for that.

Source: SMTP Monitoring for DMZ01 on Port 25 TCP Port Check Group

Description: TCP Port Check Dependency Monitor that rolls up health for all Watcher Nodes Monitoring SMTP Monitoring for PRDCGDMZ01 on Port 25. This monitors mx1.company.com on port 25.



Another alert:

Source: SMTP Monitoring for PRDCGDMZ01 on Port 25

Description: A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond. ServerName: mx1.megenergy.com Port: 25



Any ideas, Stefan?



by the way, how does this monitor work? I set every 5 minutes to check it, but don't know how many fault checks will generate an alert?



Thanks in advance.



Peter
   Report Abuse
Re: Second Notification subscription through a BSD server
Posted: Sat, Feb 06, 2010 1:59 AM :: Rank: 0
Author
Points: 30179
Level: System Center Expert
Peter,

make sure your watcher nodes are not blocked by a firewall or something. If you can telnet to the host on port 25 from the watcher nodes, the monitor should go green again.



When you set the check interval to 5 minutes, each of your monitor will create an alert when port 25 is not responding. When port 25 is available again, the alerts will be closed automatically.
   Report Abuse
Re: Second Notification subscription through a BSD server
Posted: Mon, Feb 08, 2010 7:30 PM :: Rank: 69
Author
Points: 360
Level: System Center Hero
Thanks Stefan,

Telnet to the monitored 25 port, is that the way how watch nodes check the port 25, and generate alerts regarding the telnet?



Peter
   Report Abuse
Re: Second Notification subscription through a BSD server
Posted: Tue, Feb 09, 2010 5:14 AM :: Rank: 0
Author
Points: 30179
Level: System Center Expert
SCOM doesn\t actually use telnet but it does a basic port query. Telnet is just a convinient way to see if tcp port communication is working. You could also use portqry tool or whatever to check that.



cheers
   Report Abuse

Home  » Operations Manager  » Second Notification subscription through a BSD server
Top Contributors
Featured Members
Pete Zerger
Points: 72684
Level: System Center Expert
Tommy Gunn
Points: 47503
Level: System Center Expert
Simon Skinner
Points: 40804
Level: System Center Expert
Andreas Zuckerhut
Points: 30700
Level: System Center Expert
Stefan Koell
Points: 30179
Level: System Center Expert