<?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 Planned Downtime in Netsight in ExtremeCloud IQ- Site Engine Management Center</title>
    <link>https://community.extremenetworks.com/t5/extremecloud-iq-site-engine/planned-downtime-in-netsight/m-p/15103#M54</link>
    <description>Hi,&lt;BR /&gt;
is there a way to stop the processing of alarms and traps for specified devices e.g. for a planned down time, like in nagios ??&lt;BR /&gt;</description>
    <pubDate>Wed, 30 Apr 2014 13:30:00 GMT</pubDate>
    <dc:creator>Hans_Meiser</dc:creator>
    <dc:date>2014-04-30T13:30:00Z</dc:date>
    <item>
      <title>Planned Downtime in Netsight</title>
      <link>https://community.extremenetworks.com/t5/extremecloud-iq-site-engine/planned-downtime-in-netsight/m-p/15103#M54</link>
      <description>Hi,&lt;BR /&gt;
is there a way to stop the processing of alarms and traps for specified devices e.g. for a planned down time, like in nagios ??&lt;BR /&gt;</description>
      <pubDate>Wed, 30 Apr 2014 13:30:00 GMT</pubDate>
      <guid>https://community.extremenetworks.com/t5/extremecloud-iq-site-engine/planned-downtime-in-netsight/m-p/15103#M54</guid>
      <dc:creator>Hans_Meiser</dc:creator>
      <dc:date>2014-04-30T13:30:00Z</dc:date>
    </item>
    <item>
      <title>RE: Planned Downtime in Netsight</title>
      <link>https://community.extremenetworks.com/t5/extremecloud-iq-site-engine/planned-downtime-in-netsight/m-p/15104#M55</link>
      <description>You can disable the alarm and enable it when you finish the upgrade.&lt;BR /&gt;
&lt;BR /&gt;
Z.</description>
      <pubDate>Thu, 01 May 2014 01:59:00 GMT</pubDate>
      <guid>https://community.extremenetworks.com/t5/extremecloud-iq-site-engine/planned-downtime-in-netsight/m-p/15104#M55</guid>
      <dc:creator>Zdeněk_Pala</dc:creator>
      <dc:date>2014-05-01T01:59:00Z</dc:date>
    </item>
    <item>
      <title>RE: Planned Downtime in Netsight</title>
      <link>https://community.extremenetworks.com/t5/extremecloud-iq-site-engine/planned-downtime-in-netsight/m-p/15105#M56</link>
      <description>You are right, but disabling the alarm would mean i get no alarms at all.&lt;BR /&gt;
For example the "Device Down" alarm:&lt;BR /&gt;
If i disable the alarm for the time of maintenance, i get no alarms at all from no device except,&lt;BR /&gt;
if i create a seperate alarm group for every single device.&lt;BR /&gt;
Than your suggestion would work, so tha i disable the alarms processing only for a selected device.&lt;BR /&gt;
But this is only for one alarm on one device, so this scales alittle bit bad.&lt;BR /&gt;
&lt;BR /&gt;
Any mor esuggestions ??&lt;BR /&gt;</description>
      <pubDate>Thu, 01 May 2014 14:27:00 GMT</pubDate>
      <guid>https://community.extremenetworks.com/t5/extremecloud-iq-site-engine/planned-downtime-in-netsight/m-p/15105#M56</guid>
      <dc:creator>Hans_Meiser</dc:creator>
      <dc:date>2014-05-01T14:27:00Z</dc:date>
    </item>
    <item>
      <title>RE: Planned Downtime in Netsight</title>
      <link>https://community.extremenetworks.com/t5/extremecloud-iq-site-engine/planned-downtime-in-netsight/m-p/15106#M57</link>
      <description>You can create device group called "not in maintenance" and aim those alarms only to this group.&lt;BR /&gt;
If some device is under maintenance, remove it from this group. If the device is back operational you need to add it to the group again.&lt;BR /&gt;
Device can be in more groups.&lt;BR /&gt;
&lt;BR /&gt;
Z.</description>
      <pubDate>Thu, 01 May 2014 15:04:00 GMT</pubDate>
      <guid>https://community.extremenetworks.com/t5/extremecloud-iq-site-engine/planned-downtime-in-netsight/m-p/15106#M57</guid>
      <dc:creator>Zdeněk_Pala</dc:creator>
      <dc:date>2014-05-01T15:04:00Z</dc:date>
    </item>
  </channel>
</rss>

