07-28-2015 11:43 AM
We're running a pair of ACEs SM version 5.3 on the 6509's.
I was wondering if someone happened to know if ACE appends the port number that it forwards the packet to the back-end server on to the url, as in the following:
client is typing http://www.cisco.com
the back-end server is listening on port 115
The ACE is sending the following url to the server: http://www.cisco.com:115
I ran a tcpdump on the ACE, but saw only the url, without the port being appended. Yet, the server folks claim they are seeing the port appended when they look at the server logs.
Thanks.
Solved! Go to Solution.
08-07-2015 07:13 PM
Hi Greg,
Not sure what is ACE SM but ACE LB by default won't add the port to the URL. If server is listening on port, let's say 115 and VIP is listening on port 115, then we simply forward the packet by rewriting the destination MAC and IP. If server is listening on port 115 and VIP on port 80 and if you have defined the server with port 115 under serverfarm, then ACE simply rewrites the MAC, IP and destination.port.
ACE won't append anything in the URL unless you tell it to and if pcaps don't show it, then it didn't happen.
Regards,
Kanwal
Note: Please mark answers if they are helpful.
08-07-2015 07:13 PM
Hi Greg,
Not sure what is ACE SM but ACE LB by default won't add the port to the URL. If server is listening on port, let's say 115 and VIP is listening on port 115, then we simply forward the packet by rewriting the destination MAC and IP. If server is listening on port 115 and VIP on port 80 and if you have defined the server with port 115 under serverfarm, then ACE simply rewrites the MAC, IP and destination.port.
ACE won't append anything in the URL unless you tell it to and if pcaps don't show it, then it didn't happen.
Regards,
Kanwal
Note: Please mark answers if they are helpful.
Find answers to your questions by entering keywords or phrases in the Search bar above. New here? Use these resources to familiarize yourself with the community: