<?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: EoX API Get EoX by Software Release String(s) in Services Discussions</title>
    <link>https://community.cisco.com/t5/services-discussions/eox-api-get-eox-by-software-release-string-s/m-p/4862727#M1010</link>
    <description>&lt;P&gt;Hi Julien - Did you ever figure this issue out?&amp;nbsp; I'm stuck with the same issue.&lt;/P&gt;&lt;P&gt;-Lon.&lt;/P&gt;</description>
    <pubDate>Mon, 26 Jun 2023 19:32:44 GMT</pubDate>
    <dc:creator>LonThompson</dc:creator>
    <dc:date>2023-06-26T19:32:44Z</dc:date>
    <item>
      <title>EoX API Get EoX by Software Release String(s)</title>
      <link>https://community.cisco.com/t5/services-discussions/eox-api-get-eox-by-software-release-string-s/m-p/3879456#M514</link>
      <description>&lt;P&gt;Hello,&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Using EoX API, we encountered difficulties to choose the right EoL informations for IOS XE softwares and hardwares.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;For example, we have an ASR-903 router with IOS XE 16.5.1 software version.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Using the Get EoX By Software Release String(s) method, we request the EoX API.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;PRE&gt;GET https://api.cisco.com/supporttools/eox/rest/5/EOXBySWReleaseString/1?responseencoding=json&amp;amp;input1=16.5(1) &lt;/PRE&gt;&lt;P&gt;&amp;nbsp;PS : We found out that we needed to write 16.5(1) instead of 16.5.1.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Then, we get multiple results but none of these correspond to the ASR-903.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;And for the 6 records we get from the API, there are some different EoL informations.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;How are we suppose to know which EoL informations for IOS XE 16.5.1 are the good ones for ASR-903 ?&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;We were looking for an EoX method to query providing software string and hardware product id but we didn't find.&lt;/P&gt;&lt;P&gt;For the Software Suggestion API we can provide both informations.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Thanks for your answers.&lt;/P&gt;</description>
      <pubDate>Tue, 25 Jun 2019 17:24:22 GMT</pubDate>
      <guid>https://community.cisco.com/t5/services-discussions/eox-api-get-eox-by-software-release-string-s/m-p/3879456#M514</guid>
      <dc:creator>Julien.Senechal.AMS</dc:creator>
      <dc:date>2019-06-25T17:24:22Z</dc:date>
    </item>
    <item>
      <title>Re: EoX API Get EoX by Software Release String(s)</title>
      <link>https://community.cisco.com/t5/services-discussions/eox-api-get-eox-by-software-release-string-s/m-p/4862727#M1010</link>
      <description>&lt;P&gt;Hi Julien - Did you ever figure this issue out?&amp;nbsp; I'm stuck with the same issue.&lt;/P&gt;&lt;P&gt;-Lon.&lt;/P&gt;</description>
      <pubDate>Mon, 26 Jun 2023 19:32:44 GMT</pubDate>
      <guid>https://community.cisco.com/t5/services-discussions/eox-api-get-eox-by-software-release-string-s/m-p/4862727#M1010</guid>
      <dc:creator>LonThompson</dc:creator>
      <dc:date>2023-06-26T19:32:44Z</dc:date>
    </item>
    <item>
      <title>Re: EoX API Get EoX by Software Release String(s)</title>
      <link>https://community.cisco.com/t5/services-discussions/eox-api-get-eox-by-software-release-string-s/m-p/5088269#M1109</link>
      <description>&lt;P&gt;I'm experiencing the same problem myself. Any updates here?&lt;/P&gt;</description>
      <pubDate>Thu, 02 May 2024 23:04:55 GMT</pubDate>
      <guid>https://community.cisco.com/t5/services-discussions/eox-api-get-eox-by-software-release-string-s/m-p/5088269#M1109</guid>
      <dc:creator>nauto</dc:creator>
      <dc:date>2024-05-02T23:04:55Z</dc:date>
    </item>
  </channel>
</rss>

