<?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: SXP over S2S VPN in Network Access Control</title>
    <link>https://community.cisco.com/t5/network-access-control/sxp-over-s2s-vpn/m-p/3459513#M491779</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi Mark,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I dont think of any caveats except the fact that SGT cannot be propagated if the ASA is running NAT. Other than that you should be good.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks&lt;/P&gt;&lt;P&gt;Karthik&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Tue, 06 Jun 2017 17:13:03 GMT</pubDate>
    <dc:creator>kthumula</dc:creator>
    <dc:date>2017-06-06T17:13:03Z</dc:date>
    <item>
      <title>SXP over S2S VPN</title>
      <link>https://community.cisco.com/t5/network-access-control/sxp-over-s2s-vpn/m-p/3459512#M491773</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi All,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Working on a trustsec design for a customer who's currently running site to site VPN between ASA 5500s. Do we have any validated design that i can use? any caveats? limitations?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Mark&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 11 Mar 2019 07:46:07 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/sxp-over-s2s-vpn/m-p/3459512#M491773</guid>
      <dc:creator>macayubi</dc:creator>
      <dc:date>2019-03-11T07:46:07Z</dc:date>
    </item>
    <item>
      <title>Re: SXP over S2S VPN</title>
      <link>https://community.cisco.com/t5/network-access-control/sxp-over-s2s-vpn/m-p/3459513#M491779</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi Mark,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I dont think of any caveats except the fact that SGT cannot be propagated if the ASA is running NAT. Other than that you should be good.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks&lt;/P&gt;&lt;P&gt;Karthik&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 06 Jun 2017 17:13:03 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/sxp-over-s2s-vpn/m-p/3459513#M491779</guid>
      <dc:creator>kthumula</dc:creator>
      <dc:date>2017-06-06T17:13:03Z</dc:date>
    </item>
    <item>
      <title>Re: SXP over S2S VPN</title>
      <link>https://community.cisco.com/t5/network-access-control/sxp-over-s2s-vpn/m-p/3459514#M491787</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi Mark,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;The closest CVD we have is here &lt;A href="http://www.cisco.com/c/dam/en/us/td/docs/solutions/CVD/Apr2016/User-to-DC_Access_Control_Using_TrustSec_Deployment_April2016.pdf" title="http://www.cisco.com/c/dam/en/us/td/docs/solutions/CVD/Apr2016/User-to-DC_Access_Control_Using_TrustSec_Deployment_April2016.pdf"&gt;http://www.cisco.com/c/dam/en/us/td/docs/solutions/CVD/Apr2016/User-to-DC_Access_Control_Using_TrustSec_Deployment_April…&lt;/A&gt; It does not however discuss straight IPsec. Actually configuration of same is very simple through the single command [crypto ikev2 cts sgt] and is documented here&amp;nbsp; &lt;A href="http://www.cisco.com/c/en/us/td/docs/ios-xml/ios/sec_usr_cts/configuration/15-mt/sec-usr-cts-15-mt-book/sec-cts-ips-tag.html" title="http://www.cisco.com/c/en/us/td/docs/ios-xml/ios/sec_usr_cts/configuration/15-mt/sec-usr-cts-15-mt-book/sec-cts-ips-tag.html"&gt;http://www.cisco.com/c/en/us/td/docs/ios-xml/ios/sec_usr_cts/configuration/15-mt/sec-usr-cts-15-mt-book/sec-cts-ips-tag.html&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;The one point to note is that a Cisco Meta Data Header (CMD) which is 8B long and follows the IPsec ESP/AH header and does require IKEv2. The CMD is an additional 8B of overhead which should be compensated for if adjusting MSS and for IP MTU.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 07 Jun 2017 14:09:45 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/sxp-over-s2s-vpn/m-p/3459514#M491787</guid>
      <dc:creator>mjessup</dc:creator>
      <dc:date>2017-06-07T14:09:45Z</dc:date>
    </item>
  </channel>
</rss>

