<?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 ASA 5510 service based in Network Security</title>
    <link>https://community.cisco.com/t5/network-security/asa-5510-service-based/m-p/1900145#M457392</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Also wats the code that you using on the ASA.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Fri, 06 Apr 2012 07:27:50 GMT</pubDate>
    <dc:creator>srirmoha</dc:creator>
    <dc:date>2012-04-06T07:27:50Z</dc:date>
    <item>
      <title>ASA 5510 service based</title>
      <link>https://community.cisco.com/t5/network-security/asa-5510-service-based/m-p/1900143#M457383</link>
      <description>&lt;P&gt;Is there a way to NAT based on availability of a protocol?&amp;nbsp; Put another way can the ASA have a NAT entry for a web server that includes a primary inside address, and a secondary inside address to use in case the primary isn't responding?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I know this is the realm of load balancers, but I have a special situation with limited resources.&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;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Rick&lt;/P&gt;</description>
      <pubDate>Mon, 11 Mar 2019 22:50:46 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/asa-5510-service-based/m-p/1900143#M457383</guid>
      <dc:creator>0rsnaric</dc:creator>
      <dc:date>2019-03-11T22:50:46Z</dc:date>
    </item>
    <item>
      <title>Re: ASA 5510 service based</title>
      <link>https://community.cisco.com/t5/network-security/asa-5510-service-based/m-p/1900144#M457387</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi Rick,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;For this situation I guess you would need to add NAT and ACL statements for both the Primary and secondary IP's.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Whenever the Primary IP fails and the server fallback to secondary then, the ASA would start using the second nat statement for the request coming in for your secondary IP.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Now I understand you would have only one public ip for both the primary and secondary private ip, is that so???&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 06 Apr 2012 07:27:32 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/asa-5510-service-based/m-p/1900144#M457387</guid>
      <dc:creator>srirmoha</dc:creator>
      <dc:date>2012-04-06T07:27:32Z</dc:date>
    </item>
    <item>
      <title>ASA 5510 service based</title>
      <link>https://community.cisco.com/t5/network-security/asa-5510-service-based/m-p/1900145#M457392</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Also wats the code that you using on the ASA.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 06 Apr 2012 07:27:50 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/asa-5510-service-based/m-p/1900145#M457392</guid>
      <dc:creator>srirmoha</dc:creator>
      <dc:date>2012-04-06T07:27:50Z</dc:date>
    </item>
    <item>
      <title>Re: ASA 5510 service based</title>
      <link>https://community.cisco.com/t5/network-security/asa-5510-service-based/m-p/1900146#M457396</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt; this is not possible&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;you can not statically map a public to 2 different private IP's to the same public IP on the same port&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;either you do port forwarding for 2 differant IP's on 2 differant ports like below&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt; stat (in,out) tcp 2.2.2.2 80 1.1.1.1 80&lt;/P&gt;&lt;P&gt; stat (in,out) tcp 2.2.2.2 443 1.1.1.2 443&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;but that does not solve you problem&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;so basically what you are trying to achive is not possible.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 06 Apr 2012 08:38:45 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/asa-5510-service-based/m-p/1900146#M457396</guid>
      <dc:creator>Amit Rai</dc:creator>
      <dc:date>2012-04-06T08:38:45Z</dc:date>
    </item>
    <item>
      <title>ASA 5510 service based</title>
      <link>https://community.cisco.com/t5/network-security/asa-5510-service-based/m-p/1900147#M457398</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi,&lt;/P&gt;&lt;P&gt;I know this is a load balancing solution but do you manage the DNS Server for the web server? If so you could implement DNS round-robin:&lt;/P&gt;&lt;P&gt;&lt;A class="jive-link-external-small" href="http://en.wikipedia.org/wiki/Round-robin_DNS"&gt;http://en.wikipedia.org/wiki/Round-robin_DNS&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Cheers&lt;/P&gt;&lt;P&gt;Sean&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 06 Apr 2012 08:51:05 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/asa-5510-service-based/m-p/1900147#M457398</guid>
      <dc:creator>sean_evershed</dc:creator>
      <dc:date>2012-04-06T08:51:05Z</dc:date>
    </item>
  </channel>
</rss>

