<?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: Problem with changing MX uplink settings via the API in Network Platform API</title>
    <link>https://community.cisco.com/t5/network-platform-api/problem-with-changing-mx-uplink-settings-via-the-api/m-p/5439650#M6240</link>
    <description>&lt;P&gt;&lt;SPAN&gt;Hi, as this is a PUT request, it will perform a complete replacement of all the settings specified in the call, effectively deleting and reconfiguring all existing WAN settings associated with it. In contrast, a POST request merely appends new entries without modifying or removing any existing ones.&lt;/SPAN&gt;&lt;/P&gt;</description>
    <pubDate>Tue, 20 Jun 2023 11:28:29 GMT</pubDate>
    <dc:creator>badreddine</dc:creator>
    <dc:date>2023-06-20T11:28:29Z</dc:date>
    <item>
      <title>Problem with changing MX uplink settings via the API</title>
      <link>https://community.cisco.com/t5/network-platform-api/problem-with-changing-mx-uplink-settings-via-the-api/m-p/5439648#M6238</link>
      <description>&lt;P&gt; Folks,&lt;/P&gt;&lt;P&gt;has anybody got a work around for a problem I am having with updating the MX WAN ports&lt;BR /&gt;&lt;BR /&gt;We have a customer who wants a script to disable WAN2 on all their MX 64s and it's a quite large estate &lt;/P&gt;&lt;P&gt;Although setting ["WAN2"]["enabled "] = False via updateDeviceApplianceUplinksSettings does indeed shut WAN2 the problem occurs about 10 seconds later when WAN1 seems to reset and leaves the device without WAN connectivity for 80 to 90 seconds&lt;BR /&gt;&lt;BR /&gt;Although this is a 'just in case' script the customer wants I'm not sure that they would be happy with 1500+ 90 second disconnects across their estate.&lt;BR /&gt;&lt;BR /&gt;I think the issue is because updateDeviceApplianceUplinksSettings requires values to be written to both WAN1 and WAN2&lt;BR /&gt;&lt;BR /&gt;Even though WAN1 essentially has no change it still treats the update as a change and acts accordingly.&lt;BR /&gt;&lt;BR /&gt;Has anybody found a way around this.&lt;BR /&gt;&lt;BR /&gt;Initial thought were&lt;/P&gt;&lt;P&gt;Only write to WAN2 (API complains about empty fields not being permitted)&lt;BR /&gt;&lt;BR /&gt;Use the regular ethernet port to disable the port BUT because the port is defined as a WAN port it doesn't appear as a regular ethernet port any more.&lt;BR /&gt;&lt;BR /&gt;Meraki devs, can we have please address the WAN ports individually in the future please.&lt;/P&gt;&lt;P&gt;Thanks,&lt;/P&gt;&lt;P&gt;Rob...&lt;/P&gt;</description>
      <pubDate>Tue, 20 Jun 2023 10:15:50 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-platform-api/problem-with-changing-mx-uplink-settings-via-the-api/m-p/5439648#M6238</guid>
      <dc:creator>cta102</dc:creator>
      <dc:date>2023-06-20T10:15:50Z</dc:date>
    </item>
    <item>
      <title>Re: Problem with changing MX uplink settings via the API</title>
      <link>https://community.cisco.com/t5/network-platform-api/problem-with-changing-mx-uplink-settings-via-the-api/m-p/5439649#M6239</link>
      <description>&lt;P&gt;Hi,&lt;/P&gt;&lt;P&gt;Hope this helps. &lt;/P&gt;&lt;P&gt;Can you try the "&lt;SPAN&gt;updateNetworkDeviceManagementInterfaceSettings" with WAN1 as "not configured" and WAN2 as "Disabled"&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;&lt;A href="https://developer.cisco.com/meraki/api/#!update-network-device-management-interface-settings" target="_blank" rel="nofollow noopener noreferrer"&gt;Cisco Meraki - Create with the Meraki Platform&lt;/A&gt;&lt;/SPAN&gt;&lt;/P&gt;</description>
      <pubDate>Tue, 20 Jun 2023 11:06:41 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-platform-api/problem-with-changing-mx-uplink-settings-via-the-api/m-p/5439649#M6239</guid>
      <dc:creator>Madhan kumar G</dc:creator>
      <dc:date>2023-06-20T11:06:41Z</dc:date>
    </item>
    <item>
      <title>Re: Problem with changing MX uplink settings via the API</title>
      <link>https://community.cisco.com/t5/network-platform-api/problem-with-changing-mx-uplink-settings-via-the-api/m-p/5439650#M6240</link>
      <description>&lt;P&gt;&lt;SPAN&gt;Hi, as this is a PUT request, it will perform a complete replacement of all the settings specified in the call, effectively deleting and reconfiguring all existing WAN settings associated with it. In contrast, a POST request merely appends new entries without modifying or removing any existing ones.&lt;/SPAN&gt;&lt;/P&gt;</description>
      <pubDate>Tue, 20 Jun 2023 11:28:29 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-platform-api/problem-with-changing-mx-uplink-settings-via-the-api/m-p/5439650#M6240</guid>
      <dc:creator>badreddine</dc:creator>
      <dc:date>2023-06-20T11:28:29Z</dc:date>
    </item>
    <item>
      <title>Re: Problem with changing MX uplink settings via the API</title>
      <link>https://community.cisco.com/t5/network-platform-api/problem-with-changing-mx-uplink-settings-via-the-api/m-p/5439651#M6241</link>
      <description>&lt;P&gt;Unfortunately that has the same issue as &lt;SPAN&gt;updateDeviceApplianceUplinksSettings&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;I will probably dig into meraki.py at when I get time to see if both  WAN ports have to be written with the PUT request or if I can add an extra function which allows better targeting of WAN updates&lt;BR /&gt;&lt;BR /&gt;Thanks for taking the time though&lt;BR /&gt;&lt;BR /&gt;BTW in the V1 method you can specify a single WAN port, but it still updates both &lt;/P&gt;</description>
      <pubDate>Wed, 21 Jun 2023 10:19:50 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-platform-api/problem-with-changing-mx-uplink-settings-via-the-api/m-p/5439651#M6241</guid>
      <dc:creator>cta102</dc:creator>
      <dc:date>2023-06-21T10:19:50Z</dc:date>
    </item>
  </channel>
</rss>

