<?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: Delay IP Configuration in Cloud Networking Platform</title>
    <link>https://community.cisco.com/t5/cloud-networking-platform/delay-ip-configuration/m-p/5453457#M12392</link>
    <description>&lt;P&gt;If this is for the management IP - why bother making it static at all?&lt;/P&gt;</description>
    <pubDate>Sat, 26 Jan 2019 05:51:37 GMT</pubDate>
    <dc:creator>Philip D'Ath</dc:creator>
    <dc:date>2019-01-26T05:51:37Z</dc:date>
    <item>
      <title>Delay IP Configuration</title>
      <link>https://community.cisco.com/t5/cloud-networking-platform/delay-ip-configuration/m-p/5453455#M12390</link>
      <description>&lt;P&gt;Is there a way to set a time that a Meraki Switch will go from a DHCP to a hard coded IP? I am swapping out old switches and I want the new Meraki's to have same IP but can't take the old ones down without the new ones up. My thought is if I can swap the IPs and then turn off the port on the Meraki that is connected to the old switches. Bad idea possibly... just brainstorming here.&lt;/P&gt;&lt;P&gt;thank you! &lt;/P&gt;</description>
      <pubDate>Fri, 25 Jan 2019 23:02:35 GMT</pubDate>
      <guid>https://community.cisco.com/t5/cloud-networking-platform/delay-ip-configuration/m-p/5453455#M12390</guid>
      <dc:creator>ham737</dc:creator>
      <dc:date>2019-01-25T23:02:35Z</dc:date>
    </item>
    <item>
      <title>Re: Delay IP Configuration</title>
      <link>https://community.cisco.com/t5/cloud-networking-platform/delay-ip-configuration/m-p/5453456#M12391</link>
      <description>&lt;P&gt;In most cases the IP is just used for management purposes. Can't you use a temporary address, take out the old switch and change the IP after that? That change should be bumpless. Or do you have routes pointing to its IP address?&lt;/P&gt;</description>
      <pubDate>Fri, 25 Jan 2019 23:18:15 GMT</pubDate>
      <guid>https://community.cisco.com/t5/cloud-networking-platform/delay-ip-configuration/m-p/5453456#M12391</guid>
      <dc:creator>BrechtSchamp</dc:creator>
      <dc:date>2019-01-25T23:18:15Z</dc:date>
    </item>
    <item>
      <title>Re: Delay IP Configuration</title>
      <link>https://community.cisco.com/t5/cloud-networking-platform/delay-ip-configuration/m-p/5453457#M12392</link>
      <description>&lt;P&gt;If this is for the management IP - why bother making it static at all?&lt;/P&gt;</description>
      <pubDate>Sat, 26 Jan 2019 05:51:37 GMT</pubDate>
      <guid>https://community.cisco.com/t5/cloud-networking-platform/delay-ip-configuration/m-p/5453457#M12392</guid>
      <dc:creator>Philip D'Ath</dc:creator>
      <dc:date>2019-01-26T05:51:37Z</dc:date>
    </item>
  </channel>
</rss>

