<?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: delay for SSL connections (Dial-up or LAN) in Application Networking</title>
    <link>https://community.cisco.com/t5/application-networking/delay-for-ssl-connections-dial-up-or-lan/m-p/49766#M545</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;1.Hard code the speeds on the LD interfaces and corresponding switches. &lt;/P&gt;&lt;P&gt;2.Make sure LD has correct default route statement.&lt;/P&gt;&lt;P&gt;3. If servers or vips are on different subnet than LD, make sure you have alias ip address command.&lt;/P&gt;&lt;P&gt;4.If all else fails, open a TAC case and be prepared to capture simultaneous sniffer traces on front end vlan and back end vlan. Usually, latency issues are difficult to troubleshoot.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I hope this helps!&lt;/P&gt;&lt;P&gt;Gonzalo&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Thu, 14 Mar 2002 23:30:48 GMT</pubDate>
    <dc:creator>jbaigorr</dc:creator>
    <dc:date>2002-03-14T23:30:48Z</dc:date>
    <item>
      <title>delay for SSL connections (Dial-up or LAN)</title>
      <link>https://community.cisco.com/t5/application-networking/delay-for-ssl-connections-dial-up-or-lan/m-p/49765#M544</link>
      <description>&lt;P&gt;I know a load balancer or any other equipment between 2 devices obviously introduces latency. But when a client initiates an SSL connection to a server through the LD it seems to take about 5 seconds to hand the request off to a server. And this is on ethernet right outside the firewall. The time it takes a client on dial up is obviously more. Is there any tweaks or anyway to make this faster? I am using sticky sessions based on SSL ID and the timeout is 15 minutes.&lt;/P&gt;</description>
      <pubDate>Mon, 11 Mar 2002 22:09:45 GMT</pubDate>
      <guid>https://community.cisco.com/t5/application-networking/delay-for-ssl-connections-dial-up-or-lan/m-p/49765#M544</guid>
      <dc:creator>rcrowe</dc:creator>
      <dc:date>2002-03-11T22:09:45Z</dc:date>
    </item>
    <item>
      <title>Re: delay for SSL connections (Dial-up or LAN)</title>
      <link>https://community.cisco.com/t5/application-networking/delay-for-ssl-connections-dial-up-or-lan/m-p/49766#M545</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;1.Hard code the speeds on the LD interfaces and corresponding switches. &lt;/P&gt;&lt;P&gt;2.Make sure LD has correct default route statement.&lt;/P&gt;&lt;P&gt;3. If servers or vips are on different subnet than LD, make sure you have alias ip address command.&lt;/P&gt;&lt;P&gt;4.If all else fails, open a TAC case and be prepared to capture simultaneous sniffer traces on front end vlan and back end vlan. Usually, latency issues are difficult to troubleshoot.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I hope this helps!&lt;/P&gt;&lt;P&gt;Gonzalo&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 14 Mar 2002 23:30:48 GMT</pubDate>
      <guid>https://community.cisco.com/t5/application-networking/delay-for-ssl-connections-dial-up-or-lan/m-p/49766#M545</guid>
      <dc:creator>jbaigorr</dc:creator>
      <dc:date>2002-03-14T23:30:48Z</dc:date>
    </item>
  </channel>
</rss>

