1. Home
  2. Nortel Networks
  3. Alteon Cross Protocol Persistence

Alteon Cross Protocol Persistence

I'm attempting to do clientIP based persistence on a 180e running

10.30.7.

The persistence works fine with pbind client for HTTPS, but when a user connects using FTP they will not the server affinity from the HTTPS session on the new connection. I'm using both hash metric and clientIP pbinds on all services.

Is there any way to make the persistent sessions carry over to different services?

/c/slb/real 3 ena rip 10.0.70.21 /c/slb/real 4 dis rip 10.0.70.22 /c/slb/group 2 metric hash add 3 add 4 /c/slb/virt 1/service https group 2 pbind clientip dbind ena /c/slb/virt 1/service ftp group 2 ftpp ena pbind clientip

Reply to
Tom
Loading thread data ...

You don't really need to have pbind clientIP enabled for those services if you are using hash. In fact it's not recommended as it creates redundant persistent session entries. Hash uses the source IP, as long as the source IP doesn't change then your FTP and HTTPS sessions should hit the same server.

If you plan on using pbind clientIP with RR or LC metric then there is no guarantee that FTP and HTTPS will hit the same server. However, HTTP and HTTPS ARE bound together by pbind clientIP. This is required fro shopping cart persistence.

Is your user behind a proxy server? Some ISPs will not proxy HTTPS but will proxy HTTP, FTP, etc. The 180e will see two different IPs from the same client.

Angler

Tom wrote:

Reply to
Angler

Cabling-Design.com Forums website is not affiliated with any of the manufacturers or service providers discussed here. All logos and trade names are the property of their respective owners.