<?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: PoE Overload/Fault with AP3715i in ExtremeWireless (Identifi)</title>
    <link>https://community.extremenetworks.com/t5/extremewireless-identifi/poe-overload-fault-with-ap3715i/m-p/46482#M4256</link>
    <description>Hi Doug.  We just RMA'd (3) 3715s with this issue today (case # 01167363).  I should have the replacements in a couple of days and these should be on their way back to you guys by the end of the week.&lt;BR /&gt;
&lt;BR /&gt;
-Rich P.&lt;BR /&gt;
&lt;BR /&gt;</description>
    <pubDate>Tue, 10 Nov 2015 02:24:00 GMT</pubDate>
    <dc:creator>Rich_Pacheco</dc:creator>
    <dc:date>2015-11-10T02:24:00Z</dc:date>
    <item>
      <title>PoE Overload/Fault with AP3715i</title>
      <link>https://community.extremenetworks.com/t5/extremewireless-identifi/poe-overload-fault-with-ap3715i/m-p/46480#M4254</link>
      <description>Hi.  I was wondering if anyone is seeing the same issue I am.  I have over 1200 APs installed on a couple of C5210 controllers running 09.21.01.0179 code.  Those 1200+ APs are broken down to the following three models:&lt;BR /&gt;
&lt;BR /&gt;
650+ are 3715i&lt;BR /&gt;
390+ are 3825i&lt;BR /&gt;
150+ are 3610i&lt;BR /&gt;
&lt;BR /&gt;
These are connected to either C3G124-48P (running 06.61.09.0012) or C5G124-48P2 (running 06.81.01.0027 code) switches.&lt;BR /&gt;
&lt;BR /&gt;
It seems like every week or so I get a 3715i AP that is down and when I look at the switch port, it says "PoE Overload or Fault".  When I replace the AP with another new 3715i, the switch port is fine and the new AP comes up instantly so it doesn't appear to be a switch issue.   I've tried connecting the problem AP to different PoE switches in our lab as well as just plugging it in to a PoE Injector and it won't come up.  It's dead, so we get it RMA'd and a day later a new one shows up.  I wouldn't care if this happening once in a while, but I've had to replace 20+ access points and it only seems to happen to the 3715i.  We've opened a case with the GTAC a few months ago, but never heard back.  I'm getting tired of replacing APs.  I was just curious if anyone was having the same problem.&lt;BR /&gt;
&lt;BR /&gt;
Regards,&lt;BR /&gt;
-Rich&lt;BR /&gt;
&lt;BR /&gt;</description>
      <pubDate>Mon, 09 Nov 2015 23:53:00 GMT</pubDate>
      <guid>https://community.extremenetworks.com/t5/extremewireless-identifi/poe-overload-fault-with-ap3715i/m-p/46480#M4254</guid>
      <dc:creator>Rich_Pacheco</dc:creator>
      <dc:date>2015-11-09T23:53:00Z</dc:date>
    </item>
    <item>
      <title>RE: PoE Overload/Fault with AP3715i</title>
      <link>https://community.extremenetworks.com/t5/extremewireless-identifi/poe-overload-fault-with-ap3715i/m-p/46481#M4255</link>
      <description>Hello Rich, &lt;BR /&gt;
&lt;BR /&gt;
Sorry you have had issues with the 3715. If you can provide the ticket number I will look into it for you. We can have a failure analysis run for you on your most recent RMA. &lt;BR /&gt;
&lt;BR /&gt;
Regards, &lt;BR /&gt;
Doug</description>
      <pubDate>Tue, 10 Nov 2015 02:18:00 GMT</pubDate>
      <guid>https://community.extremenetworks.com/t5/extremewireless-identifi/poe-overload-fault-with-ap3715i/m-p/46481#M4255</guid>
      <dc:creator>Doug</dc:creator>
      <dc:date>2015-11-10T02:18:00Z</dc:date>
    </item>
    <item>
      <title>RE: PoE Overload/Fault with AP3715i</title>
      <link>https://community.extremenetworks.com/t5/extremewireless-identifi/poe-overload-fault-with-ap3715i/m-p/46482#M4256</link>
      <description>Hi Doug.  We just RMA'd (3) 3715s with this issue today (case # 01167363).  I should have the replacements in a couple of days and these should be on their way back to you guys by the end of the week.&lt;BR /&gt;
&lt;BR /&gt;
-Rich P.&lt;BR /&gt;
&lt;BR /&gt;</description>
      <pubDate>Tue, 10 Nov 2015 02:24:00 GMT</pubDate>
      <guid>https://community.extremenetworks.com/t5/extremewireless-identifi/poe-overload-fault-with-ap3715i/m-p/46482#M4256</guid>
      <dc:creator>Rich_Pacheco</dc:creator>
      <dc:date>2015-11-10T02:24:00Z</dc:date>
    </item>
    <item>
      <title>RE: PoE Overload/Fault with AP3715i</title>
      <link>https://community.extremenetworks.com/t5/extremewireless-identifi/poe-overload-fault-with-ap3715i/m-p/46483#M4257</link>
      <description>Got it, thanks Rich.</description>
      <pubDate>Tue, 10 Nov 2015 02:26:00 GMT</pubDate>
      <guid>https://community.extremenetworks.com/t5/extremewireless-identifi/poe-overload-fault-with-ap3715i/m-p/46483#M4257</guid>
      <dc:creator>Doug</dc:creator>
      <dc:date>2015-11-10T02:26:00Z</dc:date>
    </item>
    <item>
      <title>RE: PoE Overload/Fault with AP3715i</title>
      <link>https://community.extremenetworks.com/t5/extremewireless-identifi/poe-overload-fault-with-ap3715i/m-p/46484#M4258</link>
      <description>Hello Rich&lt;BR /&gt;
I have opened a new case # 01167380 to track these failures and to inquire with our Quality Group to see if we are noticing any POE failure trends.</description>
      <pubDate>Tue, 10 Nov 2015 02:52:00 GMT</pubDate>
      <guid>https://community.extremenetworks.com/t5/extremewireless-identifi/poe-overload-fault-with-ap3715i/m-p/46484#M4258</guid>
      <dc:creator>Craig_Guilmette</dc:creator>
      <dc:date>2015-11-10T02:52:00Z</dc:date>
    </item>
    <item>
      <title>RE: PoE Overload/Fault with AP3715i</title>
      <link>https://community.extremenetworks.com/t5/extremewireless-identifi/poe-overload-fault-with-ap3715i/m-p/46485#M4259</link>
      <description>Thanks Craig.&lt;BR /&gt;</description>
      <pubDate>Tue, 10 Nov 2015 03:11:00 GMT</pubDate>
      <guid>https://community.extremenetworks.com/t5/extremewireless-identifi/poe-overload-fault-with-ap3715i/m-p/46485#M4259</guid>
      <dc:creator>Rich_Pacheco</dc:creator>
      <dc:date>2015-11-10T03:11:00Z</dc:date>
    </item>
  </channel>
</rss>

