<?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: Hardware Replacement Cycle in Cloud Networking Platform</title>
    <link>https://community.cisco.com/t5/cloud-networking-platform/hardware-replacement-cycle/m-p/5410232#M3801</link>
    <description>&lt;P&gt;I would not exchange the MS225-24P with the same model. Instead you or your customer might discuss upcoming changes or needs so you might end up with a different model (48P model or a L3 one etc.)&lt;/P&gt;&lt;P&gt;I terms of Wifi: Yes, there are some changes, but I think that WiFi 6 is enough for today and the next year's. But, it might be an idea to exchange the APs in order to be more flexible (Cisco Classic / Meraki ones share the same chassis)&lt;/P&gt;&lt;P&gt;Nevertheless, let's see what kind of major changes will follow, so it might be an idea to exchange it due to a breaking change.&lt;/P&gt;</description>
    <pubDate>Tue, 20 Jun 2023 07:08:15 GMT</pubDate>
    <dc:creator>MerryAki</dc:creator>
    <dc:date>2023-06-20T07:08:15Z</dc:date>
    <item>
      <title>Hardware Replacement Cycle</title>
      <link>https://community.cisco.com/t5/cloud-networking-platform/hardware-replacement-cycle/m-p/5410229#M3798</link>
      <description>&lt;P&gt;Just wondering how everyone deal with switch replacement cycles.&lt;/P&gt;&lt;P&gt;My aim is to replace hardware every 4-5 years depending a few things however equipment that is due to be replaced (MS225-24P) is still a current model so would you replace equipment with exactly the same model ( There is no requirement for a higher model) just for the sake of replacing it or just extend it use until a replacement model is released?&lt;/P&gt;&lt;P&gt;I understand that the longer equipment is used the more likely it is to fail however I have spares so that isn't of great concern &lt;/P&gt;</description>
      <pubDate>Mon, 19 Jun 2023 22:44:12 GMT</pubDate>
      <guid>https://community.cisco.com/t5/cloud-networking-platform/hardware-replacement-cycle/m-p/5410229#M3798</guid>
      <dc:creator>BlakeRichardson</dc:creator>
      <dc:date>2023-06-19T22:44:12Z</dc:date>
    </item>
    <item>
      <title>Re: Hardware Replacement Cycle</title>
      <link>https://community.cisco.com/t5/cloud-networking-platform/hardware-replacement-cycle/m-p/5410230#M3799</link>
      <description>&lt;P&gt;Hi,&lt;/P&gt;&lt;P&gt;I am just sharing my thoughts on this discussion. Switch replacement can be for following reasons.&lt;/P&gt;&lt;P&gt;1. Switch is showing stack overflows, CPU or Memory hikes, dropping packets&lt;/P&gt;&lt;P&gt;2. EoL is announced and EoS is expected shortly&lt;/P&gt;&lt;P&gt;3. Switch port and backplace capacities are not meeting the growing application needs&lt;/P&gt;&lt;P&gt;Need not to worry using the same model switch for longer if you are not under any of the above situations.&lt;/P&gt;</description>
      <pubDate>Tue, 20 Jun 2023 05:19:44 GMT</pubDate>
      <guid>https://community.cisco.com/t5/cloud-networking-platform/hardware-replacement-cycle/m-p/5410230#M3799</guid>
      <dc:creator>Madhan kumar G</dc:creator>
      <dc:date>2023-06-20T05:19:44Z</dc:date>
    </item>
    <item>
      <title>Re: Hardware Replacement Cycle</title>
      <link>https://community.cisco.com/t5/cloud-networking-platform/hardware-replacement-cycle/m-p/5410231#M3800</link>
      <description>&lt;P&gt;I generally 'prepare' the business for replacement in 3 years but look to hold out equipment for 5.&lt;/P&gt;&lt;P&gt;That way there will be budget available when 5 years comes around.&lt;/P&gt;&lt;P&gt;In my experience, AP's almost always need replacing at 5 years.&lt;/P&gt;&lt;P&gt;But I agree regarding switches - swapping them out for the sake of it isn't really necessary. If they're not EOL/EOS, have more life in them and there's no requirement to replace, I tend to push them a bit further. &lt;/P&gt;</description>
      <pubDate>Tue, 20 Jun 2023 06:29:52 GMT</pubDate>
      <guid>https://community.cisco.com/t5/cloud-networking-platform/hardware-replacement-cycle/m-p/5410231#M3800</guid>
      <dc:creator>Brash</dc:creator>
      <dc:date>2023-06-20T06:29:52Z</dc:date>
    </item>
    <item>
      <title>Re: Hardware Replacement Cycle</title>
      <link>https://community.cisco.com/t5/cloud-networking-platform/hardware-replacement-cycle/m-p/5410232#M3801</link>
      <description>&lt;P&gt;I would not exchange the MS225-24P with the same model. Instead you or your customer might discuss upcoming changes or needs so you might end up with a different model (48P model or a L3 one etc.)&lt;/P&gt;&lt;P&gt;I terms of Wifi: Yes, there are some changes, but I think that WiFi 6 is enough for today and the next year's. But, it might be an idea to exchange the APs in order to be more flexible (Cisco Classic / Meraki ones share the same chassis)&lt;/P&gt;&lt;P&gt;Nevertheless, let's see what kind of major changes will follow, so it might be an idea to exchange it due to a breaking change.&lt;/P&gt;</description>
      <pubDate>Tue, 20 Jun 2023 07:08:15 GMT</pubDate>
      <guid>https://community.cisco.com/t5/cloud-networking-platform/hardware-replacement-cycle/m-p/5410232#M3801</guid>
      <dc:creator>MerryAki</dc:creator>
      <dc:date>2023-06-20T07:08:15Z</dc:date>
    </item>
    <item>
      <title>Re: Hardware Replacement Cycle</title>
      <link>https://community.cisco.com/t5/cloud-networking-platform/hardware-replacement-cycle/m-p/5410233#M3802</link>
      <description>&lt;P&gt;We have adopted an end of support refresh lifecycle for networking equipment for some time now.  With Cisco and Meraki routers, switches and APs, we have only had 2-3 fail during lifetime.  Those were two ISRs (design fault) and an old Catalyst 2950 where the integrated PSU failed, but it still worked on the RPS.&lt;/P&gt;&lt;P&gt;We do move them though, so you won't find an MR32 in a busy public area, but might do in a fire exit corridor.&lt;/P&gt;</description>
      <pubDate>Tue, 20 Jun 2023 09:24:24 GMT</pubDate>
      <guid>https://community.cisco.com/t5/cloud-networking-platform/hardware-replacement-cycle/m-p/5410233#M3802</guid>
      <dc:creator>CMR</dc:creator>
      <dc:date>2023-06-20T09:24:24Z</dc:date>
    </item>
    <item>
      <title>Re: Hardware Replacement Cycle</title>
      <link>https://community.cisco.com/t5/cloud-networking-platform/hardware-replacement-cycle/m-p/5410234#M3803</link>
      <description>&lt;P&gt;&lt;SPAN&gt;In my experience,&lt;/SPAN&gt;&lt;/P&gt;&lt;UL&gt;&lt;LI&gt;&lt;SPAN&gt;If they're not EOL/EOS, or&lt;/SPAN&gt;&lt;/LI&gt;&lt;LI&gt;&lt;SPAN&gt;If there is no requirement for a higher model, or&lt;/SPAN&gt;&lt;/LI&gt;&lt;LI&gt;&lt;SPAN&gt;If there is no degradation in the existing switch,&lt;/SPAN&gt;&lt;/LI&gt;&lt;/UL&gt;&lt;DIV&gt;&lt;SPAN&gt; &lt;/SPAN&gt;&lt;/DIV&gt;&lt;DIV&gt;&lt;SPAN&gt;..there seem to be no need of replacing with the same model. I'd recommend to wait until a newer model is announced to &lt;SPAN&gt;gauge&lt;/SPAN&gt; the benefits of replacement.&lt;/SPAN&gt;&lt;/DIV&gt;</description>
      <pubDate>Tue, 20 Jun 2023 11:33:53 GMT</pubDate>
      <guid>https://community.cisco.com/t5/cloud-networking-platform/hardware-replacement-cycle/m-p/5410234#M3803</guid>
      <dc:creator>vinisha</dc:creator>
      <dc:date>2023-06-20T11:33:53Z</dc:date>
    </item>
    <item>
      <title>Re: Hardware Replacement Cycle</title>
      <link>https://community.cisco.com/t5/cloud-networking-platform/hardware-replacement-cycle/m-p/5410235#M3804</link>
      <description>&lt;P&gt;Good to know my thoughts match what has been said. Yes this discussion was only about switches. AP's are on a strict 4 year replacement cycle. &lt;/P&gt;</description>
      <pubDate>Tue, 20 Jun 2023 19:55:42 GMT</pubDate>
      <guid>https://community.cisco.com/t5/cloud-networking-platform/hardware-replacement-cycle/m-p/5410235#M3804</guid>
      <dc:creator>BlakeRichardson</dc:creator>
      <dc:date>2023-06-20T19:55:42Z</dc:date>
    </item>
  </channel>
</rss>

