<?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 Documentation of &amp;quot;internal&amp;quot; NAC alarms? in ExtremeCloud IQ- Site Engine Management Center</title>
    <link>https://community.extremenetworks.com/t5/extremecloud-iq-site-engine/documentation-of-quot-internal-quot-nac-alarms/m-p/36971#M4297</link>
    <description>Hello,&lt;BR /&gt;
&lt;BR /&gt;
a couple of days ago, we encountered some alarms that we   had never seen before. Those alarms were generated by one of our NAC (it   was listed as "Source" in the alarm description) that exceeded a   certain processing limit. &lt;BR /&gt;
&lt;BR /&gt;
The alarm: "Processing queue is overflowing, RADIUS requests may be throttled"&lt;BR /&gt;
&lt;BR /&gt;
The   issue itself was solved, we now want to know where this alarm came from   and how the NAC was able to submit this information to the Management   server. As far as we know, this is not something the Management server   can gather via a simple SNMP poll. Is there some internal connection   between the two that submits this information and generates an alarm?   The alarm was not created by us via the Alarms Manager. We would like to   have this information to prepare for other alarms that are not defined   in the Alarms Manager but can be submitted by the NAC. So far, the only   option for us is to wait until the triggering event happens and then   create an alarm that looks for the given information text. &lt;BR /&gt;</description>
    <pubDate>Mon, 12 Jun 2017 16:35:00 GMT</pubDate>
    <dc:creator>Jannik_Winther</dc:creator>
    <dc:date>2017-06-12T16:35:00Z</dc:date>
    <item>
      <title>Documentation of "internal" NAC alarms?</title>
      <link>https://community.extremenetworks.com/t5/extremecloud-iq-site-engine/documentation-of-quot-internal-quot-nac-alarms/m-p/36971#M4297</link>
      <description>Hello,&lt;BR /&gt;
&lt;BR /&gt;
a couple of days ago, we encountered some alarms that we   had never seen before. Those alarms were generated by one of our NAC (it   was listed as "Source" in the alarm description) that exceeded a   certain processing limit. &lt;BR /&gt;
&lt;BR /&gt;
The alarm: "Processing queue is overflowing, RADIUS requests may be throttled"&lt;BR /&gt;
&lt;BR /&gt;
The   issue itself was solved, we now want to know where this alarm came from   and how the NAC was able to submit this information to the Management   server. As far as we know, this is not something the Management server   can gather via a simple SNMP poll. Is there some internal connection   between the two that submits this information and generates an alarm?   The alarm was not created by us via the Alarms Manager. We would like to   have this information to prepare for other alarms that are not defined   in the Alarms Manager but can be submitted by the NAC. So far, the only   option for us is to wait until the triggering event happens and then   create an alarm that looks for the given information text. &lt;BR /&gt;</description>
      <pubDate>Mon, 12 Jun 2017 16:35:00 GMT</pubDate>
      <guid>https://community.extremenetworks.com/t5/extremecloud-iq-site-engine/documentation-of-quot-internal-quot-nac-alarms/m-p/36971#M4297</guid>
      <dc:creator>Jannik_Winther</dc:creator>
      <dc:date>2017-06-12T16:35:00Z</dc:date>
    </item>
  </channel>
</rss>

