<?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: C35 premature failures in ExtremeWireless (Identifi)</title>
    <link>https://community.extremenetworks.com/t5/extremewireless-identifi/c35-premature-failures/m-p/30465#M467</link>
    <description>Can't remember exactly, but no, it wasn't a C35, instead some four digit monster (52xx?), about twice as deep as the C35, hence it wouldn't even fit in our rack. At that point we concluded that it might be a bit to easy to get the diamond badge as a EN partner...&lt;BR /&gt;</description>
    <pubDate>Thu, 09 Mar 2017 15:35:00 GMT</pubDate>
    <dc:creator>Hennes_Hoffmann</dc:creator>
    <dc:date>2017-03-09T15:35:00Z</dc:date>
    <item>
      <title>C35 premature failures</title>
      <link>https://community.extremenetworks.com/t5/extremewireless-identifi/c35-premature-failures/m-p/30456#M458</link>
      <description>Having experienced two premature failures of C35 units, I am wondering, especially after the recent coverage of the Atom C2xxx issue, if more problems are on the way? Has extreme observed unusually high failure rates (my personal experience is a clear yes, 50% in 18 months) and are there plans how to tackle this?&lt;BR /&gt;
&lt;BR /&gt;
Thanks&lt;BR /&gt;</description>
      <pubDate>Tue, 07 Mar 2017 22:42:00 GMT</pubDate>
      <guid>https://community.extremenetworks.com/t5/extremewireless-identifi/c35-premature-failures/m-p/30456#M458</guid>
      <dc:creator>Hennes_Hoffmann</dc:creator>
      <dc:date>2017-03-07T22:42:00Z</dc:date>
    </item>
    <item>
      <title>RE: C35 premature failures</title>
      <link>https://community.extremenetworks.com/t5/extremewireless-identifi/c35-premature-failures/m-p/30457#M459</link>
      <description>Hi Hennes&lt;BR /&gt;
&lt;BR /&gt;
Sorry about the inconvenience faced.&lt;BR /&gt;
Could you provide more details for Premature failures.&lt;BR /&gt;
Do you observe any logs related to this issue.&lt;BR /&gt;
&lt;BR /&gt;
Regards&lt;BR /&gt;
Rajesh&lt;BR /&gt;
&lt;BR /&gt;</description>
      <pubDate>Wed, 08 Mar 2017 08:14:00 GMT</pubDate>
      <guid>https://community.extremenetworks.com/t5/extremewireless-identifi/c35-premature-failures/m-p/30457#M459</guid>
      <dc:creator>Rajesh_Jeevendr</dc:creator>
      <dc:date>2017-03-08T08:14:00Z</dc:date>
    </item>
    <item>
      <title>RE: C35 premature failures</title>
      <link>https://community.extremenetworks.com/t5/extremewireless-identifi/c35-premature-failures/m-p/30458#M460</link>
      <description>Hi Rajesh,&lt;BR /&gt;
&lt;BR /&gt;
  As far as I understand it, these failures come out of the blue. The C2718 in the C35 is - at least potentially - affected. The two failures we experienced came without prior indication. Something I noticed: Looking at the reports via the web gui, I see a cpu utilisation of 7.xx - suggesting something close to 100% on an eight core system, looking at the system state via the shell I get some top-style display showing 99% idle?&lt;BR /&gt;
&lt;BR /&gt;
Thanks,&lt;BR /&gt;
Hennes&lt;BR /&gt;</description>
      <pubDate>Wed, 08 Mar 2017 15:13:00 GMT</pubDate>
      <guid>https://community.extremenetworks.com/t5/extremewireless-identifi/c35-premature-failures/m-p/30458#M460</guid>
      <dc:creator>Hennes_Hoffmann</dc:creator>
      <dc:date>2017-03-08T15:13:00Z</dc:date>
    </item>
    <item>
      <title>RE: C35 premature failures</title>
      <link>https://community.extremenetworks.com/t5/extremewireless-identifi/c35-premature-failures/m-p/30459#M461</link>
      <description>Hi Hennes,&lt;BR /&gt;
I expect to have more information to share on this subject in a few hours.</description>
      <pubDate>Wed, 08 Mar 2017 22:23:00 GMT</pubDate>
      <guid>https://community.extremenetworks.com/t5/extremewireless-identifi/c35-premature-failures/m-p/30459#M461</guid>
      <dc:creator>Drew_C</dc:creator>
      <dc:date>2017-03-08T22:23:00Z</dc:date>
    </item>
    <item>
      <title>RE: C35 premature failures</title>
      <link>https://community.extremenetworks.com/t5/extremewireless-identifi/c35-premature-failures/m-p/30460#M462</link>
      <description>Please take a look at these two articles. We will be sending a notification and I'll post that here when it goes out.&lt;BR /&gt;
&lt;BR /&gt;
&lt;A href="https://extremeportal.force.com/ExtrArticleDetail?n=000013784" target="_blank" rel="nofollow noreferrer noopener"&gt;FN-415: WS-C35 (30135) WLAN Appliance may fail due to degradation of a clock signal&lt;/A&gt;&lt;BR /&gt;
If you have trouble with the FAQ link in the above article, you can access it here: &lt;A href="https://extremeportal.force.com/ExtrArticleDetail?n=000014059" target="_blank" rel="nofollow noreferrer noopener"&gt;WS-C35 Clock Issue - FAQ&lt;/A&gt;&lt;BR /&gt;</description>
      <pubDate>Thu, 09 Mar 2017 05:03:00 GMT</pubDate>
      <guid>https://community.extremenetworks.com/t5/extremewireless-identifi/c35-premature-failures/m-p/30460#M462</guid>
      <dc:creator>Drew_C</dc:creator>
      <dc:date>2017-03-09T05:03:00Z</dc:date>
    </item>
    <item>
      <title>RE: C35 premature failures</title>
      <link>https://community.extremenetworks.com/t5/extremewireless-identifi/c35-premature-failures/m-p/30461#M463</link>
      <description>Thanks for that. The originally shipped 35s are 5As, the replacements were 5Ds, so all well below 5J. We run two redundant setups (=4 C35), but given the sudden nature of the failures and the possible strain on getting replacements, what would be your advice? Giving up on redundancy and safe two units offline keeping them as cold spares until the equipment gets replaced? &lt;BR /&gt;</description>
      <pubDate>Thu, 09 Mar 2017 15:35:00 GMT</pubDate>
      <guid>https://community.extremenetworks.com/t5/extremewireless-identifi/c35-premature-failures/m-p/30461#M463</guid>
      <dc:creator>Hennes_Hoffmann</dc:creator>
      <dc:date>2017-03-09T15:35:00Z</dc:date>
    </item>
    <item>
      <title>RE: C35 premature failures</title>
      <link>https://community.extremenetworks.com/t5/extremewireless-identifi/c35-premature-failures/m-p/30462#M464</link>
      <description>I'd leave the pair running - if one should fail let's say tomorrow then RMA the unit, should be done in 24hours.&lt;BR /&gt;</description>
      <pubDate>Thu, 09 Mar 2017 15:35:00 GMT</pubDate>
      <guid>https://community.extremenetworks.com/t5/extremewireless-identifi/c35-premature-failures/m-p/30462#M464</guid>
      <dc:creator>Ronald_Dvorak</dc:creator>
      <dc:date>2017-03-09T15:35:00Z</dc:date>
    </item>
    <item>
      <title>RE: C35 premature failures</title>
      <link>https://community.extremenetworks.com/t5/extremewireless-identifi/c35-premature-failures/m-p/30463#M465</link>
      <description>24hours? Maybe in the US? Despite a 24/7 service contract (Diamond Partner)we waited Friday to Monday to receive a previous generation controller as a cold spare (not sufficiently compatible to run paired). I believe it was almost three weeks after we got the proper replacement, which unfortunately turned out to be NOS. &lt;BR /&gt;</description>
      <pubDate>Thu, 09 Mar 2017 15:35:00 GMT</pubDate>
      <guid>https://community.extremenetworks.com/t5/extremewireless-identifi/c35-premature-failures/m-p/30463#M465</guid>
      <dc:creator>Hennes_Hoffmann</dc:creator>
      <dc:date>2017-03-09T15:35:00Z</dc:date>
    </item>
    <item>
      <title>RE: C35 premature failures</title>
      <link>https://community.extremenetworks.com/t5/extremewireless-identifi/c35-premature-failures/m-p/30464#M466</link>
      <description>Sorry, yes I mean next business day which is Monday if you open the ticket on Friday.&lt;BR /&gt;
&lt;BR /&gt;
What is a "previous generation controller " - was it a C35 and why was it not able to pair with the running one.&lt;BR /&gt;</description>
      <pubDate>Thu, 09 Mar 2017 15:35:00 GMT</pubDate>
      <guid>https://community.extremenetworks.com/t5/extremewireless-identifi/c35-premature-failures/m-p/30464#M466</guid>
      <dc:creator>Ronald_Dvorak</dc:creator>
      <dc:date>2017-03-09T15:35:00Z</dc:date>
    </item>
    <item>
      <title>RE: C35 premature failures</title>
      <link>https://community.extremenetworks.com/t5/extremewireless-identifi/c35-premature-failures/m-p/30465#M467</link>
      <description>Can't remember exactly, but no, it wasn't a C35, instead some four digit monster (52xx?), about twice as deep as the C35, hence it wouldn't even fit in our rack. At that point we concluded that it might be a bit to easy to get the diamond badge as a EN partner...&lt;BR /&gt;</description>
      <pubDate>Thu, 09 Mar 2017 15:35:00 GMT</pubDate>
      <guid>https://community.extremenetworks.com/t5/extremewireless-identifi/c35-premature-failures/m-p/30465#M467</guid>
      <dc:creator>Hennes_Hoffmann</dc:creator>
      <dc:date>2017-03-09T15:35:00Z</dc:date>
    </item>
    <item>
      <title>RE: C35 premature failures</title>
      <link>https://community.extremenetworks.com/t5/extremewireless-identifi/c35-premature-failures/m-p/30466#M468</link>
      <description>I'm pretty sure that Extreme knows exactly which boxes are affected and who bought them.&lt;BR /&gt;
So how about Extreme checks the database and informs affected partners/customers.&lt;BR /&gt;
&lt;BR /&gt;
Because my boss doesn't like the idea that I make a road trip thru the whole country just to check a sticker on the bottom of every unit that we've sold.&lt;BR /&gt;
&lt;BR /&gt;
Regarding the FAQ - what if I don't contact Extreme till June 9th ?</description>
      <pubDate>Thu, 09 Mar 2017 20:33:00 GMT</pubDate>
      <guid>https://community.extremenetworks.com/t5/extremewireless-identifi/c35-premature-failures/m-p/30466#M468</guid>
      <dc:creator>Ronald_Dvorak</dc:creator>
      <dc:date>2017-03-09T20:33:00Z</dc:date>
    </item>
    <item>
      <title>RE: C35 premature failures</title>
      <link>https://community.extremenetworks.com/t5/extremewireless-identifi/c35-premature-failures/m-p/30467#M469</link>
      <description>Regarding your last question.  Extreme will honor replacement requests after June 9.  we are asking customers to submit before that date when possible to assist with quantity planning and distribution logistics.&lt;BR /&gt;
&lt;BR /&gt;
The earlier questions are addressed in &lt;A href="https://gtacknowledge.extremenetworks.com/articles/Solution/FN-415-WS-C35-30135-WLAN-Appliance-may-fail-due-to-degradation-of-a-clock-signal" target="_blank" rel="nofollow noreferrer noopener"&gt;Field Notice 415 &lt;/A&gt;&lt;BR /&gt;
&lt;BR /&gt;
Please let us know if there are more questions.   &lt;BR /&gt;</description>
      <pubDate>Sat, 11 Mar 2017 00:36:00 GMT</pubDate>
      <guid>https://community.extremenetworks.com/t5/extremewireless-identifi/c35-premature-failures/m-p/30467#M469</guid>
      <dc:creator>Weidle__Bert</dc:creator>
      <dc:date>2017-03-11T00:36:00Z</dc:date>
    </item>
  </channel>
</rss>

