<?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 ISE 2.7(p4) API request get sxpconnection don't return IpAddress field in Network Access Control</title>
    <link>https://community.cisco.com/t5/network-access-control/ise-2-7-p4-api-request-get-sxpconnection-don-t-return-ipaddress/m-p/4534478#M572284</link>
    <description>&lt;P&gt;Hello!&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;The main goal is to export all our sxp connections (some hundreds) for importing them to another deployment&amp;nbsp;by csv.&lt;/P&gt;&lt;P&gt;But GUI do not allow to do it. We decided to get all connections by API, but there is a problem too. The API do not return IP addresses of peers.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Could you please advise why ISE 2.7 do not return IpAddress field in the&amp;nbsp; get request ?&amp;nbsp;&amp;nbsp;&lt;A href="https://developer.cisco.com/docs/identity-services-engine/2.6/#!sxp-connections/get-by-id" target="_blank" rel="noopener"&gt;https://developer.cisco.com/docs/identity-services-engine/2.6/#!sxp-connections/get-by-id&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;According documentation it should, but it don't (&lt;/P&gt;&lt;P&gt;the response is looks like&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;PRE&gt;{'id': 'xxxxxxx',
 'sxpPeer': 'xxxxxx', 
 'sxpVpn': 'default', 
 'sxpNode': 'xxxxxx', 
 'sxpMode': 'LISTENER', 
 'sxpVersion': 'VERSION_4', 
 'enabled': True, 
 'link': {'rel': 'self', 
          'href': 'https://xxxxxx:9060/ers/config/sxpconnections/xxxxxx', 
          'type': 'application/json'}
}&lt;/PRE&gt;&lt;P&gt;Even an sxpPeer do not correspond to NAD names, it is just SXP connection description&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
    <pubDate>Wed, 19 Jan 2022 16:46:55 GMT</pubDate>
    <dc:creator>aserov</dc:creator>
    <dc:date>2022-01-19T16:46:55Z</dc:date>
    <item>
      <title>ISE 2.7(p4) API request get sxpconnection don't return IpAddress field</title>
      <link>https://community.cisco.com/t5/network-access-control/ise-2-7-p4-api-request-get-sxpconnection-don-t-return-ipaddress/m-p/4534478#M572284</link>
      <description>&lt;P&gt;Hello!&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;The main goal is to export all our sxp connections (some hundreds) for importing them to another deployment&amp;nbsp;by csv.&lt;/P&gt;&lt;P&gt;But GUI do not allow to do it. We decided to get all connections by API, but there is a problem too. The API do not return IP addresses of peers.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Could you please advise why ISE 2.7 do not return IpAddress field in the&amp;nbsp; get request ?&amp;nbsp;&amp;nbsp;&lt;A href="https://developer.cisco.com/docs/identity-services-engine/2.6/#!sxp-connections/get-by-id" target="_blank" rel="noopener"&gt;https://developer.cisco.com/docs/identity-services-engine/2.6/#!sxp-connections/get-by-id&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;According documentation it should, but it don't (&lt;/P&gt;&lt;P&gt;the response is looks like&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;PRE&gt;{'id': 'xxxxxxx',
 'sxpPeer': 'xxxxxx', 
 'sxpVpn': 'default', 
 'sxpNode': 'xxxxxx', 
 'sxpMode': 'LISTENER', 
 'sxpVersion': 'VERSION_4', 
 'enabled': True, 
 'link': {'rel': 'self', 
          'href': 'https://xxxxxx:9060/ers/config/sxpconnections/xxxxxx', 
          'type': 'application/json'}
}&lt;/PRE&gt;&lt;P&gt;Even an sxpPeer do not correspond to NAD names, it is just SXP connection description&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Wed, 19 Jan 2022 16:46:55 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/ise-2-7-p4-api-request-get-sxpconnection-don-t-return-ipaddress/m-p/4534478#M572284</guid>
      <dc:creator>aserov</dc:creator>
      <dc:date>2022-01-19T16:46:55Z</dc:date>
    </item>
    <item>
      <title>Re: ISE 2.7(p4) API request get sxpconnection don't return IpAddress f</title>
      <link>https://community.cisco.com/t5/network-access-control/ise-2-7-p4-api-request-get-sxpconnection-don-t-return-ipaddress/m-p/4534503#M572285</link>
      <description>&lt;P&gt;I just ran some tests using curl against a 2.7p5 cluster and I noticed the same discrepancies.&amp;nbsp; Could possibly be a document bug.&amp;nbsp; I would work with TAC to get their input.&amp;nbsp; I did notice that when running queries against sxp local bindings API you can get the ip address by id, not exactly what you are looking for, but just as an FYSA.&lt;/P&gt;
&lt;P&gt;curl -k --include --header 'Content-Type:application/json' --header 'Accept: application/json' --user xx:xx -request GET https://x.x.x.x:9060/ers/config/sxpconnections/fcxxxxxx-3f68xxxx24f04&lt;/P&gt;
&lt;PRE&gt;{&lt;BR /&gt;"ERSSxpLocalBindings" : {&lt;BR /&gt;"id" : "fcxxxxxx-3f68xxxx24f04",&lt;BR /&gt;"ipAddressOrHost" : "x.x.3.2/32",&lt;BR /&gt;"sxpVpn" : "legacy-eps",&lt;BR /&gt;"sgt" : "ACAS_Service (13/000D)",&lt;BR /&gt;"link" : {&lt;BR /&gt;"rel" : "self",&lt;BR /&gt;"href" : "https://x.x.x.x:9060/ers/config/sxplocalbindings/fcxxxxxx-3f68xxxx24f04",&lt;BR /&gt;"type" : "application/json"&lt;BR /&gt;}&lt;BR /&gt;}&lt;/PRE&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Wed, 19 Jan 2022 17:22:24 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/ise-2-7-p4-api-request-get-sxpconnection-don-t-return-ipaddress/m-p/4534503#M572285</guid>
      <dc:creator>Mike.Cifelli</dc:creator>
      <dc:date>2022-01-19T17:22:24Z</dc:date>
    </item>
  </channel>
</rss>

