<?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: API call for MX warm spare status in Network Platform API</title>
    <link>https://community.cisco.com/t5/network-platform-api/api-call-for-mx-warm-spare-status/m-p/5451421#M7991</link>
    <description>&lt;P&gt;&lt;A href="https://developer.cisco.com/meraki/api-v1/#!get-network-appliance-warm-spare" target="_blank" rel="nofollow noopener noreferrer"&gt;https://developer.cisco.com/meraki/api-v1/#!get-network-appliance-warm-spare&lt;/A&gt;&lt;/P&gt;</description>
    <pubDate>Tue, 01 Jun 2021 16:22:54 GMT</pubDate>
    <dc:creator>jdsilva</dc:creator>
    <dc:date>2021-06-01T16:22:54Z</dc:date>
    <item>
      <title>API call for MX warm spare status</title>
      <link>https://community.cisco.com/t5/network-platform-api/api-call-for-mx-warm-spare-status/m-p/5451420#M7990</link>
      <description>&lt;P&gt;Hi,&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;is there an API call to find out the current warm spare status (Current Master/Passive;ready) in a network?&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN class="lia-inline-image-display-wrapper lia-image-align-inline" image-alt="StefanRzepczyk_0-1622555036516.png" style="width: 400px;"&gt;&lt;span class="lia-inline-image-display-wrapper" image-alt="image.png"&gt;&lt;img src="https://community.cisco.com/t5/image/serverpage/image-id/262490iF4A7EA266B7007B6/image-size/large?v=v2&amp;amp;px=999" role="button" title="image.png" alt="image.png" /&gt;&lt;/span&gt;&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;I am setting up a monitoring page for our NOC. The goal is to show all networks with both MXes (warm spare mode) and the respective uplink statuses on one page (site centric).&lt;/P&gt;&lt;P&gt;Thanks,&lt;/P&gt;&lt;P&gt;Stefan&lt;/P&gt;</description>
      <pubDate>Tue, 01 Jun 2021 13:44:41 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-platform-api/api-call-for-mx-warm-spare-status/m-p/5451420#M7990</guid>
      <dc:creator>StefanRzepczyk</dc:creator>
      <dc:date>2021-06-01T13:44:41Z</dc:date>
    </item>
    <item>
      <title>Re: API call for MX warm spare status</title>
      <link>https://community.cisco.com/t5/network-platform-api/api-call-for-mx-warm-spare-status/m-p/5451421#M7991</link>
      <description>&lt;P&gt;&lt;A href="https://developer.cisco.com/meraki/api-v1/#!get-network-appliance-warm-spare" target="_blank" rel="nofollow noopener noreferrer"&gt;https://developer.cisco.com/meraki/api-v1/#!get-network-appliance-warm-spare&lt;/A&gt;&lt;/P&gt;</description>
      <pubDate>Tue, 01 Jun 2021 16:22:54 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-platform-api/api-call-for-mx-warm-spare-status/m-p/5451421#M7991</guid>
      <dc:creator>jdsilva</dc:creator>
      <dc:date>2021-06-01T16:22:54Z</dc:date>
    </item>
    <item>
      <title>Re: API call for MX warm spare status</title>
      <link>https://community.cisco.com/t5/network-platform-api/api-call-for-mx-warm-spare-status/m-p/5451422#M7992</link>
      <description>&lt;P&gt;Thanks for your answer!&lt;BR /&gt;&lt;BR /&gt;This API call tells you the primary and spare MX &lt;U&gt;serial&lt;/U&gt;. I am looking for a specific one that tells you the &lt;U&gt;status&lt;/U&gt; which is master and which is passive/ready.&lt;/P&gt;</description>
      <pubDate>Wed, 02 Jun 2021 06:27:38 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-platform-api/api-call-for-mx-warm-spare-status/m-p/5451422#M7992</guid>
      <dc:creator>StefanRzepczyk</dc:creator>
      <dc:date>2021-06-02T06:27:38Z</dc:date>
    </item>
    <item>
      <title>Re: API call for MX warm spare status</title>
      <link>https://community.cisco.com/t5/network-platform-api/api-call-for-mx-warm-spare-status/m-p/5451423#M7993</link>
      <description>&lt;P&gt;Seems that there is no API call for the warm spare &lt;U&gt;status&lt;/U&gt;. As a workaround I am using this:&lt;BR /&gt;&lt;A href="https://developer.cisco.com/meraki/api-v1/#!get-device-appliance-performance" target="_blank" rel="nofollow noopener noreferrer"&gt;https://developer.cisco.com/meraki/api-v1/#!get-device-appliance-performance&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&lt;EM&gt;Description: Return the performance score for a single MX. &lt;U&gt;Only primary&lt;/U&gt; MX devices supported. &lt;/EM&gt;&lt;BR /&gt;&lt;EM&gt;If no data is available, a 204 error code is returned.&lt;/EM&gt;&lt;/P&gt;&lt;P&gt;So if I have two MXes in one network as warm spare and I get a score, this MX has to be the master.&lt;/P&gt;&lt;P&gt;Does anyone have a better idea?&lt;/P&gt;</description>
      <pubDate>Wed, 02 Jun 2021 12:08:37 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-platform-api/api-call-for-mx-warm-spare-status/m-p/5451423#M7993</guid>
      <dc:creator>StefanRzepczyk</dc:creator>
      <dc:date>2021-06-02T12:08:37Z</dc:date>
    </item>
    <item>
      <title>Re: API call for MX warm spare status</title>
      <link>https://community.cisco.com/t5/network-platform-api/api-call-for-mx-warm-spare-status/m-p/5451424#M7994</link>
      <description>&lt;P&gt;Same question, i'm searching for an API that is able to detect master/master, or split brain status.&lt;BR /&gt;The workaround mentioned does not work for this.&lt;/P&gt;</description>
      <pubDate>Thu, 02 May 2024 08:37:05 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-platform-api/api-call-for-mx-warm-spare-status/m-p/5451424#M7994</guid>
      <dc:creator>ksumann</dc:creator>
      <dc:date>2024-05-02T08:37:05Z</dc:date>
    </item>
    <item>
      <title>Re: API call for MX warm spare status</title>
      <link>https://community.cisco.com/t5/network-platform-api/api-call-for-mx-warm-spare-status/m-p/5451425#M7995</link>
      <description>&lt;P&gt;We are also looking for this so the status of the HA pair can be monitored from Auvik.&lt;/P&gt;</description>
      <pubDate>Mon, 19 May 2025 23:12:20 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-platform-api/api-call-for-mx-warm-spare-status/m-p/5451425#M7995</guid>
      <dc:creator>skincaid_CN</dc:creator>
      <dc:date>2025-05-19T23:12:20Z</dc:date>
    </item>
    <item>
      <title>Re: API call for MX warm spare status</title>
      <link>https://community.cisco.com/t5/network-platform-api/api-call-for-mx-warm-spare-status/m-p/5451426#M7996</link>
      <description>&lt;P&gt;Thanks for reviving this thread.&lt;BR /&gt;In most cases, while both MXs are up - primary should be active. while primary is down and warm spare is up - warm spare should be active.&lt;BR /&gt;The availability status of the devices is available via &lt;A href="https://developer.cisco.com/meraki/api-v1/get-organization-devices-availabilities/" target="_blank" rel="nofollow noopener noreferrer"&gt;&lt;SPAN&gt;getOrganizationDevicesAvailabilities.&lt;/SPAN&gt;&lt;/A&gt; However, as pointed out, a split brain status is not available via API currently.&lt;BR /&gt;&lt;BR /&gt;There is an feature request for it, and if you can contact your Cisco account team - ask them to promote "MXIDEA-I-511". They'd know what to do.&lt;/P&gt;</description>
      <pubDate>Tue, 20 May 2025 00:24:07 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-platform-api/api-call-for-mx-warm-spare-status/m-p/5451426#M7996</guid>
      <dc:creator>obrigg</dc:creator>
      <dc:date>2025-05-20T00:24:07Z</dc:date>
    </item>
    <item>
      <title>Re: API call for MX warm spare status</title>
      <link>https://community.cisco.com/t5/network-platform-api/api-call-for-mx-warm-spare-status/m-p/5451427#M7997</link>
      <description>&lt;P&gt;Email sent.&lt;/P&gt;</description>
      <pubDate>Wed, 21 May 2025 17:10:31 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-platform-api/api-call-for-mx-warm-spare-status/m-p/5451427#M7997</guid>
      <dc:creator>skincaid_CN</dc:creator>
      <dc:date>2025-05-21T17:10:31Z</dc:date>
    </item>
  </channel>
</rss>

