<?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 purview pv-fc-180 GRE and direct connect configuration question. in ExtremeCloud IQ- Site Engine Management Center</title>
    <link>https://community.extremenetworks.com/t5/extremecloud-iq-site-engine/purview-pv-fc-180-gre-and-direct-connect-configuration-question/m-p/43836#M5781</link>
    <description>We have a PV-FC-180 configured as a collector coming off of our two main core switches (BD 8810s) in our main office, they're direct connected.&lt;BR /&gt;
&lt;BR /&gt;
I have a management interface and a direct connection to the Purview server (pv-a-300).&lt;BR /&gt;
&lt;BR /&gt;
There are two issues I have;&lt;BR /&gt;
&lt;BR /&gt;
1) A campus building with another BD8810 and a VMWare infrastructure connected via MAN that I would also like to feed into my Purview.  Is it possible to set up a GRE tunnel between the BD8810 and the FC-180 despite my current configuration mode being directly connected?&lt;BR /&gt;
&lt;BR /&gt;
2) Remote offices (small) that we'd like to feed data into Purview to get application response times from their perspectives. Is this something else we'd have to form a GRE tunnel to?</description>
    <pubDate>Tue, 27 Sep 2016 05:23:00 GMT</pubDate>
    <dc:creator>Ron_Prague</dc:creator>
    <dc:date>2016-09-27T05:23:00Z</dc:date>
    <item>
      <title>purview pv-fc-180 GRE and direct connect configuration question.</title>
      <link>https://community.extremenetworks.com/t5/extremecloud-iq-site-engine/purview-pv-fc-180-gre-and-direct-connect-configuration-question/m-p/43836#M5781</link>
      <description>We have a PV-FC-180 configured as a collector coming off of our two main core switches (BD 8810s) in our main office, they're direct connected.&lt;BR /&gt;
&lt;BR /&gt;
I have a management interface and a direct connection to the Purview server (pv-a-300).&lt;BR /&gt;
&lt;BR /&gt;
There are two issues I have;&lt;BR /&gt;
&lt;BR /&gt;
1) A campus building with another BD8810 and a VMWare infrastructure connected via MAN that I would also like to feed into my Purview.  Is it possible to set up a GRE tunnel between the BD8810 and the FC-180 despite my current configuration mode being directly connected?&lt;BR /&gt;
&lt;BR /&gt;
2) Remote offices (small) that we'd like to feed data into Purview to get application response times from their perspectives. Is this something else we'd have to form a GRE tunnel to?</description>
      <pubDate>Tue, 27 Sep 2016 05:23:00 GMT</pubDate>
      <guid>https://community.extremenetworks.com/t5/extremecloud-iq-site-engine/purview-pv-fc-180-gre-and-direct-connect-configuration-question/m-p/43836#M5781</guid>
      <dc:creator>Ron_Prague</dc:creator>
      <dc:date>2016-09-27T05:23:00Z</dc:date>
    </item>
    <item>
      <title>RE: purview pv-fc-180 GRE and direct connect configuration question.</title>
      <link>https://community.extremenetworks.com/t5/extremecloud-iq-site-engine/purview-pv-fc-180-gre-and-direct-connect-configuration-question/m-p/43837#M5782</link>
      <description>Hi Ron,&lt;BR /&gt;
&lt;BR /&gt;
While I can't speak to the specifics regarding GRE on   those devices, it may not be relevant to the solution.  Purview (Extreme   Analytics) can use a GRE tunnel from remote switches,  but this is used   to forward across the MirrorN packets sourcing from that switch.    Currently this is only available on a S or K series switch, along with a   Analytics Collector appliance.&lt;BR /&gt;
&lt;BR /&gt;
Thanks&lt;BR /&gt;
Jeff&lt;BR /&gt;</description>
      <pubDate>Tue, 04 Oct 2016 23:00:00 GMT</pubDate>
      <guid>https://community.extremenetworks.com/t5/extremecloud-iq-site-engine/purview-pv-fc-180-gre-and-direct-connect-configuration-question/m-p/43837#M5782</guid>
      <dc:creator>Dudley__Jeff</dc:creator>
      <dc:date>2016-10-04T23:00:00Z</dc:date>
    </item>
  </channel>
</rss>

