<?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 shared public IP with same tcp port (round robin/load balance) in Network Security</title>
    <link>https://community.cisco.com/t5/network-security/shared-public-ip-with-same-tcp-port-round-robin-load-balance/m-p/2233798#M357732</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;thanks sourav for your time.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;it means that I need HLB..&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;yann&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Tue, 14 May 2013 13:53:36 GMT</pubDate>
    <dc:creator>yann.boulet</dc:creator>
    <dc:date>2013-05-14T13:53:36Z</dc:date>
    <item>
      <title>shared public IP with same tcp port (round robin/load balance)</title>
      <link>https://community.cisco.com/t5/network-security/shared-public-ip-with-same-tcp-port-round-robin-load-balance/m-p/2233794#M357728</link>
      <description>&lt;P&gt;Hi all,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I want to know if I can do that with my ASA5515-X, I have two servers that can do the same thing, there are SSO servers, What I want to do is to publish the 2 servers on Internet with the same public IP address and on TCP 443.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="font-size: 10pt;"&gt;Is it supported ? will it works like load balancing per sessions ?&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;or do I need to add an HLB between ASA and my SSO servers ?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks&lt;/P&gt;</description>
      <pubDate>Tue, 12 Mar 2019 01:39:15 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/shared-public-ip-with-same-tcp-port-round-robin-load-balance/m-p/2233794#M357728</guid>
      <dc:creator>yann.boulet</dc:creator>
      <dc:date>2019-03-12T01:39:15Z</dc:date>
    </item>
    <item>
      <title>shared public IP with same tcp port (round robin/load balance)</title>
      <link>https://community.cisco.com/t5/network-security/shared-public-ip-with-same-tcp-port-round-robin-load-balance/m-p/2233795#M357729</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi Yann,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;You can configure the ASA to allow traffic to your SSO server from outside on two public IP's. Users can hit either of the IP to reach the inside server. Now, load balancing would be achieved based on source devices sending request to public IP's. If source machine son internet use one public IP more to access the server, ASA can't do anything to load balance in such scenario. Here is how you can accomplish this:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Assuming SSO server on inside is 192.168.16.110 and two public IP's are 192.168.17.110 and 192.168.17.111&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;object network SSO_1&lt;/P&gt;&lt;P&gt; host 192.168.17.110&lt;/P&gt;&lt;P&gt;object network SSO_2&lt;/P&gt;&lt;P&gt; host 192.168.17.111&lt;/P&gt;&lt;P&gt;object network SSO&lt;/P&gt;&lt;P&gt; host 192.168.16.110&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;object service https&lt;/P&gt;&lt;P&gt; service tcp source eq https&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;nat (inside,outside) source static SSO SSO_1 service https https&lt;/P&gt;&lt;P&gt;nat (inside,outside) source static SSO SSO_2 service https https&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Hostname(config)# sh xl&lt;/P&gt;&lt;P&gt;2 in use, 6 most used&lt;/P&gt;&lt;P&gt;Flags: D - DNS, i - dynamic, r - portmap, s - static, I - identity, T - twice&lt;/P&gt;&lt;P&gt;TCP PAT from inside:192.168.16.110 443-443 to outside:192.168.17.110 443-443&lt;/P&gt;&lt;P&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp; flags sr idle 0:00:06 timeout 0:00:00&lt;/P&gt;&lt;P&gt;TCP PAT from inside:192.168.16.110 443-443 to outside:192.168.17.111 443-443&lt;/P&gt;&lt;P&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp; flags sr idle 0:00:08 timeout 0:00:00&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Verification:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Hostname(config)#&amp;nbsp;&amp;nbsp;&amp;nbsp; packet-tracer input outside tcp 4.4.4.4 discard 192.168.17.110 443&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Phase: 1&lt;/P&gt;&lt;P&gt;Type: UN-NAT&lt;/P&gt;&lt;P&gt;Subtype: static&lt;/P&gt;&lt;P&gt;Result: ALLOW&lt;/P&gt;&lt;P&gt;Config:&lt;/P&gt;&lt;P&gt;nat (inside,outside) source static SSO SSO_1 service https https&lt;/P&gt;&lt;P&gt;Additional Information:&lt;/P&gt;&lt;P&gt;NAT divert to egress interface inside&lt;/P&gt;&lt;P&gt;Untranslate 192.168.17.110/443 to 192.168.16.110/443&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Phase: 2&lt;/P&gt;&lt;P&gt;Type: ACCESS-LIST&lt;/P&gt;&lt;P&gt;Subtype: log&lt;/P&gt;&lt;P&gt;Result: ALLOW&lt;/P&gt;&lt;P&gt;Config:&lt;/P&gt;&lt;P&gt;access-group outside in interface outside&lt;/P&gt;&lt;P&gt;access-list outside extended permit ip any any&lt;/P&gt;&lt;P&gt;Additional Information:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Phase: 3&lt;/P&gt;&lt;P&gt;Type: CONN-SETTINGS&lt;/P&gt;&lt;P&gt;Subtype:&lt;/P&gt;&lt;P&gt;Result: ALLOW&lt;/P&gt;&lt;P&gt;Config:&lt;/P&gt;&lt;P&gt;Additional Information:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Phase: 4&lt;/P&gt;&lt;P&gt;Type: IP-OPTIONS&lt;/P&gt;&lt;P&gt;Subtype:&lt;/P&gt;&lt;P&gt;Result: ALLOW&lt;/P&gt;&lt;P&gt;Config:&lt;/P&gt;&lt;P&gt;Additional Information:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Phase: 5&lt;/P&gt;&lt;P&gt;Type: NAT&lt;/P&gt;&lt;P&gt;Subtype: rpf-check&lt;/P&gt;&lt;P&gt;Result: ALLOW&lt;/P&gt;&lt;P&gt;Config:&lt;/P&gt;&lt;P&gt;nat (inside,outside) source static SSO SSO_1 service https https&lt;/P&gt;&lt;P&gt;Additional Information:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Phase: 6&lt;/P&gt;&lt;P&gt;Type: IP-OPTIONS&lt;/P&gt;&lt;P&gt;Subtype:&lt;/P&gt;&lt;P&gt;Result: ALLOW&lt;/P&gt;&lt;P&gt;Config:&lt;/P&gt;&lt;P&gt;Additional Information:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Phase: 7&lt;/P&gt;&lt;P&gt;Type: FLOW-CREATION&lt;/P&gt;&lt;P&gt;Subtype:&lt;/P&gt;&lt;P&gt;Result: ALLOW&lt;/P&gt;&lt;P&gt;Config:&lt;/P&gt;&lt;P&gt;Additional Information:&lt;/P&gt;&lt;P&gt;New flow created with id 3670, packet dispatched to next module&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Result:&lt;/P&gt;&lt;P&gt;input-interface: outside&lt;/P&gt;&lt;P&gt;input-status: up&lt;/P&gt;&lt;P&gt;input-line-status: up&lt;/P&gt;&lt;P&gt;output-interface: inside&lt;/P&gt;&lt;P&gt;output-status: up&lt;/P&gt;&lt;P&gt;output-line-status: up&lt;/P&gt;&lt;P&gt;Action: allow&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;++++++++++++++++++++++++++++++++++++++++++++++++++++++++++&lt;/P&gt;&lt;P&gt;Hostname(config)#&amp;nbsp;&amp;nbsp;&amp;nbsp; packet-tracer input outside tcp 4.4.4.4 discard 192.168.17.111 443&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Phase: 1&lt;/P&gt;&lt;P&gt;Type: UN-NAT&lt;/P&gt;&lt;P&gt;Subtype: static&lt;/P&gt;&lt;P&gt;Result: ALLOW&lt;/P&gt;&lt;P&gt;Config:&lt;/P&gt;&lt;P&gt;nat (inside,outside) source static SSO SSO_2 service https https&lt;/P&gt;&lt;P&gt;Additional Information:&lt;/P&gt;&lt;P&gt;NAT divert to egress interface inside&lt;/P&gt;&lt;P&gt;Untranslate 192.168.17.111/443 to 192.168.16.110/443&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Phase: 2&lt;/P&gt;&lt;P&gt;Type: ACCESS-LIST&lt;/P&gt;&lt;P&gt;Subtype: log&lt;/P&gt;&lt;P&gt;Result: ALLOW&lt;/P&gt;&lt;P&gt;Config:&lt;/P&gt;&lt;P&gt;access-group outside in interface outside&lt;/P&gt;&lt;P&gt;access-list outside extended permit ip any any&lt;/P&gt;&lt;P&gt;Additional Information:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Phase: 3&lt;/P&gt;&lt;P&gt;Type: CONN-SETTINGS&lt;/P&gt;&lt;P&gt;Subtype:&lt;/P&gt;&lt;P&gt;Result: ALLOW&lt;/P&gt;&lt;P&gt;Config:&lt;/P&gt;&lt;P&gt;Additional Information:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Phase: 4&lt;/P&gt;&lt;P&gt;Type: IP-OPTIONS&lt;/P&gt;&lt;P&gt;Subtype:&lt;/P&gt;&lt;P&gt;Result: ALLOW&lt;/P&gt;&lt;P&gt;Config:&lt;/P&gt;&lt;P&gt;Additional Information:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Phase: 5&lt;/P&gt;&lt;P&gt;Type: NAT&lt;/P&gt;&lt;P&gt;Subtype: rpf-check&lt;/P&gt;&lt;P&gt;Result: ALLOW&lt;/P&gt;&lt;P&gt;Config:&lt;/P&gt;&lt;P&gt;nat (inside,outside) source static SSO SSO_1 service https https&lt;/P&gt;&lt;P&gt;Additional Information:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Phase: 6&lt;/P&gt;&lt;P&gt;Type: IP-OPTIONS&lt;/P&gt;&lt;P&gt;Subtype:&lt;/P&gt;&lt;P&gt;Result: ALLOW&lt;/P&gt;&lt;P&gt;Config:&lt;/P&gt;&lt;P&gt;Additional Information:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Phase: 7&lt;/P&gt;&lt;P&gt;Type: FLOW-CREATION&lt;/P&gt;&lt;P&gt;Subtype:&lt;/P&gt;&lt;P&gt;Result: ALLOW&lt;/P&gt;&lt;P&gt;Config:&lt;/P&gt;&lt;P&gt;Additional Information:&lt;/P&gt;&lt;P&gt;New flow created with id 3671, packet dispatched to next module&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Result:&lt;/P&gt;&lt;P&gt;input-interface: outside&lt;/P&gt;&lt;P&gt;input-status: up&lt;/P&gt;&lt;P&gt;input-line-status: up&lt;/P&gt;&lt;P&gt;output-interface: inside&lt;/P&gt;&lt;P&gt;output-status: up&lt;/P&gt;&lt;P&gt;output-line-status: up&lt;/P&gt;&lt;P&gt;Action: allow&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;-&lt;/P&gt;&lt;P&gt;Sourav&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 06 May 2013 14:41:42 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/shared-public-ip-with-same-tcp-port-round-robin-load-balance/m-p/2233795#M357729</guid>
      <dc:creator>sokakkar</dc:creator>
      <dc:date>2013-05-06T14:41:42Z</dc:date>
    </item>
    <item>
      <title>shared public IP with same tcp port (round robin/load balance)</title>
      <link>https://community.cisco.com/t5/network-security/shared-public-ip-with-same-tcp-port-round-robin-load-balance/m-p/2233796#M357730</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;thanks sourav,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;but in your scenario I can only use one of my 2 internal SSO servers ?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;thx&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Yann&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 07 May 2013 08:30:37 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/shared-public-ip-with-same-tcp-port-round-robin-load-balance/m-p/2233796#M357730</guid>
      <dc:creator>yann.boulet</dc:creator>
      <dc:date>2013-05-07T08:30:37Z</dc:date>
    </item>
    <item>
      <title>shared public IP with same tcp port (round robin/load balance)</title>
      <link>https://community.cisco.com/t5/network-security/shared-public-ip-with-same-tcp-port-round-robin-load-balance/m-p/2233797#M357731</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi Yann,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;My bad! I misunderstood your question. I provided config for one server on inside and allow connections to it from internet using two mapped IP's. Now, in your case we will need the ASA to load balance the incoming requests on a public IP to two internal servers on TCP 443. Which I am afraid to tell but can't be accomplished on ASA.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;ASA will need to have two mapped IP's in this case. However, you can put some load balancing device in b/w for which we can have a one to one static or port forward on TCP 443 and that can load balance the request received on its IP to two inside servers.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;-&lt;/P&gt;&lt;P&gt;Sourav&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 07 May 2013 12:40:03 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/shared-public-ip-with-same-tcp-port-round-robin-load-balance/m-p/2233797#M357731</guid>
      <dc:creator>sokakkar</dc:creator>
      <dc:date>2013-05-07T12:40:03Z</dc:date>
    </item>
    <item>
      <title>shared public IP with same tcp port (round robin/load balance)</title>
      <link>https://community.cisco.com/t5/network-security/shared-public-ip-with-same-tcp-port-round-robin-load-balance/m-p/2233798#M357732</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;thanks sourav for your time.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;it means that I need HLB..&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;yann&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 14 May 2013 13:53:36 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/shared-public-ip-with-same-tcp-port-round-robin-load-balance/m-p/2233798#M357732</guid>
      <dc:creator>yann.boulet</dc:creator>
      <dc:date>2013-05-14T13:53:36Z</dc:date>
    </item>
    <item>
      <title>shared public IP with same tcp port (round robin/load balance)</title>
      <link>https://community.cisco.com/t5/network-security/shared-public-ip-with-same-tcp-port-round-robin-load-balance/m-p/2233799#M357733</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Yes, that is correct.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;-&lt;/P&gt;&lt;P&gt;Sourav&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Please rate the helpful posts, ask question if you need any further help.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 14 May 2013 13:56:04 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/shared-public-ip-with-same-tcp-port-round-robin-load-balance/m-p/2233799#M357733</guid>
      <dc:creator>sokakkar</dc:creator>
      <dc:date>2013-05-14T13:56:04Z</dc:date>
    </item>
  </channel>
</rss>

