<?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 Re: Delay in NAC reject notification in ExtremeWireless (General)</title>
    <link>https://community.extremenetworks.com/t5/extremewireless-general/delay-in-nac-reject-notification/m-p/75323#M2631</link>
    <description>&lt;P&gt;Hello Peter,&lt;/P&gt;  &lt;P&gt;&amp;nbsp;&lt;/P&gt;  &lt;P&gt;I’m thinking out loud right now and what you could try with (when it’s possible I’d love to try this out in my environment as well):&lt;/P&gt;  &lt;P&gt;&lt;SPAN&gt;​&lt;/SPAN&gt;- email digest (Consolidate Email option under Administration &amp;gt; Options &amp;gt; Alarm) so that alarms are e-mailed not as they appear but e.g. every 5 minutes; plus NAC engine notification about State Accept or State Changed that triggers a log message, which is then taken as an alarm criteria for an alarm that takes no action, but is a clearing condition for auth reject alarm you already have; sounds like a lot of steps,&lt;/P&gt;  &lt;P&gt;- a scheduled workflow or a python script that grabs rejected end-systems and looks them up individually again after few minutes, raises an alarm only if nothing got better; might be more elegant but I’ve no idea how that gonna scale with loads of end-systems and low intervals.&lt;/P&gt;  &lt;P&gt;These are just my quick thoughts, what do you think?&lt;/P&gt;  &lt;P&gt;I didn’t encounter such requirement before but indeed sounds like a nice to have feature when you need to get alarms on every authentication failure that occured.&lt;/P&gt;  &lt;P&gt;&amp;nbsp;&lt;/P&gt;  &lt;P&gt;Hope that helps,&lt;/P&gt;  &lt;P&gt;Tomasz&lt;/P&gt;</description>
    <pubDate>Fri, 22 May 2020 18:50:42 GMT</pubDate>
    <dc:creator>Tomasz</dc:creator>
    <dc:date>2020-05-22T18:50:42Z</dc:date>
    <item>
      <title>Delay in NAC reject notification</title>
      <link>https://community.extremenetworks.com/t5/extremewireless-general/delay-in-nac-reject-notification/m-p/75322#M2630</link>
      <description>&lt;P&gt;Hello,&lt;/P&gt;  &lt;P&gt;I’m looking for a solution to have a e-mail notification, when endsystems hit reject rule, but with a kind of delay.&lt;/P&gt;  &lt;P&gt;NAC catchall rule is configured for reject. For reject events, a alarm is configured with action e-mail.&lt;/P&gt;  &lt;P&gt;Windows Clients running 802.1X (EAP-TLS).&lt;/P&gt;  &lt;P&gt;As 802.1X supplicant starts when windows is started, the switch is doing a mac-auth, in pre-windows-start-time, which hits the catch-all (reject) rule.&lt;/P&gt;  &lt;P&gt;This results in a lot of false-positive alarms, because a few seconds or minutes later (depending on system boot time and speed) the system is authenticated correctly via&amp;nbsp;802.1X.&lt;/P&gt;  &lt;P&gt;Is there a way to create a double check or a time-delay or something in this way that the alarm is only set, when reject status occurs over 1 minute or so?&lt;/P&gt;</description>
      <pubDate>Fri, 22 May 2020 14:12:06 GMT</pubDate>
      <guid>https://community.extremenetworks.com/t5/extremewireless-general/delay-in-nac-reject-notification/m-p/75322#M2630</guid>
      <dc:creator>PeterK</dc:creator>
      <dc:date>2020-05-22T14:12:06Z</dc:date>
    </item>
    <item>
      <title>Re: Delay in NAC reject notification</title>
      <link>https://community.extremenetworks.com/t5/extremewireless-general/delay-in-nac-reject-notification/m-p/75323#M2631</link>
      <description>&lt;P&gt;Hello Peter,&lt;/P&gt;  &lt;P&gt;&amp;nbsp;&lt;/P&gt;  &lt;P&gt;I’m thinking out loud right now and what you could try with (when it’s possible I’d love to try this out in my environment as well):&lt;/P&gt;  &lt;P&gt;&lt;SPAN&gt;​&lt;/SPAN&gt;- email digest (Consolidate Email option under Administration &amp;gt; Options &amp;gt; Alarm) so that alarms are e-mailed not as they appear but e.g. every 5 minutes; plus NAC engine notification about State Accept or State Changed that triggers a log message, which is then taken as an alarm criteria for an alarm that takes no action, but is a clearing condition for auth reject alarm you already have; sounds like a lot of steps,&lt;/P&gt;  &lt;P&gt;- a scheduled workflow or a python script that grabs rejected end-systems and looks them up individually again after few minutes, raises an alarm only if nothing got better; might be more elegant but I’ve no idea how that gonna scale with loads of end-systems and low intervals.&lt;/P&gt;  &lt;P&gt;These are just my quick thoughts, what do you think?&lt;/P&gt;  &lt;P&gt;I didn’t encounter such requirement before but indeed sounds like a nice to have feature when you need to get alarms on every authentication failure that occured.&lt;/P&gt;  &lt;P&gt;&amp;nbsp;&lt;/P&gt;  &lt;P&gt;Hope that helps,&lt;/P&gt;  &lt;P&gt;Tomasz&lt;/P&gt;</description>
      <pubDate>Fri, 22 May 2020 18:50:42 GMT</pubDate>
      <guid>https://community.extremenetworks.com/t5/extremewireless-general/delay-in-nac-reject-notification/m-p/75323#M2631</guid>
      <dc:creator>Tomasz</dc:creator>
      <dc:date>2020-05-22T18:50:42Z</dc:date>
    </item>
  </channel>
</rss>

