<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic Down Server Interface Alert in Alerting</title>
    <link>https://community.splunk.com/t5/Alerting/Down-Server-Interface-Alert/m-p/126107#M1981</link>
    <description>&lt;P&gt;Hey guys,&lt;BR /&gt;
Trying to set up an alert that will send an email &lt;STRONG&gt;when an interface goes down but does not come up within a certain timeframe&lt;/STRONG&gt;.  I'm assuming 10-15 minutes should suffice.  We're having an issue when running updates or rebooting a server, the interface does not come up properly sometimes.  &lt;/P&gt;

&lt;P&gt;This was a test run of what the logs would look like searching for USPK10OLLBS01 and /Common/tcp:&lt;/P&gt;

&lt;P&gt;I'm pretty bad with the searching logic so I could really use some help!  Thanks much, these are the logs i'm working with below during a test down state on one of the interfaces.  It reports a couple ups, but only one down.&lt;/P&gt;

&lt;P&gt;2/3/15 &lt;BR /&gt;
10:29:00.000 AM &lt;BR /&gt;
Feb  3 10:29:00 10.10.0.19 Feb  3 10:29:06 uspk10ollbs01 notice mcpd[6642]: 01070727:5: Pool /Common/UAT-BTS-Batch member /Common/USPK10OLBTSBA02:80 monitor status up. [ /Common/tcp: up ]  [ was node down for 0hr:0min:3sec ]&lt;BR /&gt;
host = 10.10.0.19 source = udp:514 sourcetype = syslog&lt;BR /&gt;
2/3/15 &lt;BR /&gt;
10:28:57.000 AM &lt;BR /&gt;
Feb  3 10:28:57 10.10.0.19 Feb  3 10:29:03 uspk10ollbs01 notice mcpd[6642]: 01070638:5: Pool /Common/UAT-BTS-Batch member /Common/USPK10OLBTSBA02:80 monitor status node down. [ /Common/tcp: up ]  [ was down for 0hr:0min:16sec ]&lt;BR /&gt;
host = 10.10.0.19 source = udp:514 sourcetype = syslog&lt;BR /&gt;
2/3/15 &lt;BR /&gt;
10:28:41.000 AM &lt;BR /&gt;
Feb  3 10:28:41 10.10.0.19 Feb  3 10:28:47 uspk10ollbs01 notice mcpd[6642]: 01070638:5: Pool /Common/UAT-BTS-Batch member /Common/USPK10OLBTSBA02:80 monitor status down. [ /Common/tcp: down ]  [ was up for 856hrs:4mins:2sec ]&lt;/P&gt;</description>
    <pubDate>Tue, 03 Feb 2015 21:45:00 GMT</pubDate>
    <dc:creator>Timmac</dc:creator>
    <dc:date>2015-02-03T21:45:00Z</dc:date>
    <item>
      <title>Down Server Interface Alert</title>
      <link>https://community.splunk.com/t5/Alerting/Down-Server-Interface-Alert/m-p/126107#M1981</link>
      <description>&lt;P&gt;Hey guys,&lt;BR /&gt;
Trying to set up an alert that will send an email &lt;STRONG&gt;when an interface goes down but does not come up within a certain timeframe&lt;/STRONG&gt;.  I'm assuming 10-15 minutes should suffice.  We're having an issue when running updates or rebooting a server, the interface does not come up properly sometimes.  &lt;/P&gt;

&lt;P&gt;This was a test run of what the logs would look like searching for USPK10OLLBS01 and /Common/tcp:&lt;/P&gt;

&lt;P&gt;I'm pretty bad with the searching logic so I could really use some help!  Thanks much, these are the logs i'm working with below during a test down state on one of the interfaces.  It reports a couple ups, but only one down.&lt;/P&gt;

&lt;P&gt;2/3/15 &lt;BR /&gt;
10:29:00.000 AM &lt;BR /&gt;
Feb  3 10:29:00 10.10.0.19 Feb  3 10:29:06 uspk10ollbs01 notice mcpd[6642]: 01070727:5: Pool /Common/UAT-BTS-Batch member /Common/USPK10OLBTSBA02:80 monitor status up. [ /Common/tcp: up ]  [ was node down for 0hr:0min:3sec ]&lt;BR /&gt;
host = 10.10.0.19 source = udp:514 sourcetype = syslog&lt;BR /&gt;
2/3/15 &lt;BR /&gt;
10:28:57.000 AM &lt;BR /&gt;
Feb  3 10:28:57 10.10.0.19 Feb  3 10:29:03 uspk10ollbs01 notice mcpd[6642]: 01070638:5: Pool /Common/UAT-BTS-Batch member /Common/USPK10OLBTSBA02:80 monitor status node down. [ /Common/tcp: up ]  [ was down for 0hr:0min:16sec ]&lt;BR /&gt;
host = 10.10.0.19 source = udp:514 sourcetype = syslog&lt;BR /&gt;
2/3/15 &lt;BR /&gt;
10:28:41.000 AM &lt;BR /&gt;
Feb  3 10:28:41 10.10.0.19 Feb  3 10:28:47 uspk10ollbs01 notice mcpd[6642]: 01070638:5: Pool /Common/UAT-BTS-Batch member /Common/USPK10OLBTSBA02:80 monitor status down. [ /Common/tcp: down ]  [ was up for 856hrs:4mins:2sec ]&lt;/P&gt;</description>
      <pubDate>Tue, 03 Feb 2015 21:45:00 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Alerting/Down-Server-Interface-Alert/m-p/126107#M1981</guid>
      <dc:creator>Timmac</dc:creator>
      <dc:date>2015-02-03T21:45:00Z</dc:date>
    </item>
    <item>
      <title>Re: Down Server Interface Alert</title>
      <link>https://community.splunk.com/t5/Alerting/Down-Server-Interface-Alert/m-p/126108#M1982</link>
      <description>&lt;P&gt;Try something like this (assuming host name is NOT extracted. Remove the first regex for host if its extracted)&lt;/P&gt;

&lt;PRE&gt;&lt;CODE&gt;your base search  | rex "(?&amp;lt;HostName&amp;gt;\w+)\snotice.*was down for (?&amp;lt;hour&amp;gt;\d+)hrs\:(?&amp;lt;minute&amp;gt;\d+)mins\:(?&amp;lt;second&amp;gt;\d+)sec\s*\]" | eval Downtime=round((hour*3600 + minute*60 + second)/60,2)  | where Downtime&amp;gt;15
&lt;/CODE&gt;&lt;/PRE&gt;

&lt;P&gt;You can schedule this search and setup alert. &lt;BR /&gt;
&lt;A href="http://docs.splunk.com/Documentation/Splunk/6.2.1/Alert/Setupalertactions#Configure_email_notification_for_alerts"&gt;http://docs.splunk.com/Documentation/Splunk/6.2.1/Alert/Setupalertactions#Configure_email_notification_for_alerts&lt;/A&gt;&lt;/P&gt;</description>
      <pubDate>Tue, 03 Feb 2015 23:06:45 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Alerting/Down-Server-Interface-Alert/m-p/126108#M1982</guid>
      <dc:creator>somesoni2</dc:creator>
      <dc:date>2015-02-03T23:06:45Z</dc:date>
    </item>
  </channel>
</rss>

