<?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 Site Engines Capability in ExtremeCloud IQ- Site Engine Management Center</title>
    <link>https://community.extremenetworks.com/t5/extremecloud-iq-site-engine/site-engines-capability/m-p/69810#M8161</link>
    <description>Hi, I have a specific flow and would like to understand how this would work and be configured in site engines.&lt;BR /&gt;&lt;BR /&gt;We will have licenses for 250 devices which will be monitored for reach-ability. When a device become unavailable, we would like the NMS to log the trail and also forward a &lt;STRONG&gt;generic&lt;/STRONG&gt; log towards a secondary NMS. &lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;From a Customer perspective, a on-site technician will receive the generic Log saying "error on network" and contact a network technician who will then log into the Site engines to investigate the specific issue.&lt;BR /&gt;&lt;BR /&gt;The same generic message should also exist for the 100 or so VSP Fabric switches if they encounter any error / critical messaging and alert the Site Engines NMS. All switches will be configured and managed by SE via SNMPv3.&lt;BR /&gt;&lt;BR /&gt;I hope this is clear enough. I believe this should be possible but would like to understand how exactly this works and if there are any limitations considering all devices being monitored will consume a license.&lt;BR /&gt;&lt;BR /&gt;Thanks in advance</description>
    <pubDate>Tue, 01 Mar 2022 22:52:06 GMT</pubDate>
    <dc:creator>SteveT</dc:creator>
    <dc:date>2022-03-01T22:52:06Z</dc:date>
    <item>
      <title>Site Engines Capability</title>
      <link>https://community.extremenetworks.com/t5/extremecloud-iq-site-engine/site-engines-capability/m-p/69810#M8161</link>
      <description>Hi, I have a specific flow and would like to understand how this would work and be configured in site engines.&lt;BR /&gt;&lt;BR /&gt;We will have licenses for 250 devices which will be monitored for reach-ability. When a device become unavailable, we would like the NMS to log the trail and also forward a &lt;STRONG&gt;generic&lt;/STRONG&gt; log towards a secondary NMS. &lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;From a Customer perspective, a on-site technician will receive the generic Log saying "error on network" and contact a network technician who will then log into the Site engines to investigate the specific issue.&lt;BR /&gt;&lt;BR /&gt;The same generic message should also exist for the 100 or so VSP Fabric switches if they encounter any error / critical messaging and alert the Site Engines NMS. All switches will be configured and managed by SE via SNMPv3.&lt;BR /&gt;&lt;BR /&gt;I hope this is clear enough. I believe this should be possible but would like to understand how exactly this works and if there are any limitations considering all devices being monitored will consume a license.&lt;BR /&gt;&lt;BR /&gt;Thanks in advance</description>
      <pubDate>Tue, 01 Mar 2022 22:52:06 GMT</pubDate>
      <guid>https://community.extremenetworks.com/t5/extremecloud-iq-site-engine/site-engines-capability/m-p/69810#M8161</guid>
      <dc:creator>SteveT</dc:creator>
      <dc:date>2022-03-01T22:52:06Z</dc:date>
    </item>
    <item>
      <title>Re: Site Engines Capability</title>
      <link>https://community.extremenetworks.com/t5/extremecloud-iq-site-engine/site-engines-capability/m-p/69811#M8162</link>
      <description>You could configure a custom criteria alarm that activates when you receive certain events and then triggers an email or log forwarding as a reaction.</description>
      <pubDate>Wed, 02 Mar 2022 19:10:06 GMT</pubDate>
      <guid>https://community.extremenetworks.com/t5/extremecloud-iq-site-engine/site-engines-capability/m-p/69811#M8162</guid>
      <dc:creator>AdrianO</dc:creator>
      <dc:date>2022-03-02T19:10:06Z</dc:date>
    </item>
  </channel>
</rss>

