10-12-2011 06:36 AM
Hi,
I have CSS in single arm deployment model. I want to configure port redirection for the servers. Servers are actually running web service on port TCP 3636. Which is accessibale by VIP http://192.168.200.87:3636 but I dont want to give user this URL I want the user to use standard HTTP URL as mention below
I want user to open http://192.168.200.87 and once they access this URL automatically CSS redirect them to port 3636. How I can achive this. I am using IP addresses for the load balancing.
service MYSERVER_1
ip address 192.168.200.40
keepalive port 3636
keepalive type tcp
active
service MYSERVER_2
ip address 192.168.200.38
keepalive type tcp
keepalive port 3636
active
content MYSERVERS
add service MYSERVER_1
add service MYSERVER_2
protocol tcp
port 3636
advanced-balance sticky-srcip
vip address 192.168.200.87
active
group MYSERVER
add destination service MYSERVER_1
add destination service MYSERVER_2
vip address 192.168.200.87
active group MYSERVER
How i can do this and make the user traffic for http to redirect to port 3636.
Solved! Go to Solution.
10-13-2011 09:28 AM
Hi,
Your server/app might be asking the client to open a connection in port 3636, additionally to the content rule in port 80, add a new rule in port 3636 as the one you used to have but still send the initial request in port 80.
content MYSERVERS
add service MYSERVER_1
add service MYSERVER_2
protocol tcp
port 3636
advanced-balance sticky-srcip
vip address 192.168.200.87
active
Let us know the results.
__ __
Pablo
10-12-2011 01:08 PM
Hi,
What you need to do here is actually configure the port under the service itself and change to content rule from port 3636 to 80. It would look like this
service MYSERVER_1
ip address 192.168.200.40
keepalive port 3636
keepalive type tcp
port 3636
active
service MYSERVER_2
ip address 192.168.200.38
keepalive type tcp
keepalive port 3636
port 3636
active
content MYSERVERS
add service MYSERVER_1
add service MYSERVER_2
protocol tcp
port 80
advanced-balance sticky-srcip
vip address 192.168.200.87
active
This should do the trick
HTH
__ __
Pablo
10-12-2011 10:41 PM
Hi,
Thanks for the reply, I did the same configuration as mention by you, but after this configuration web page is not opening. Though if i will revert back the changes same web page with port 3636 will work for me.
service MYSERVER_1
ip address 192.168.200.40
keepalive port 3636
keepalive type tcp
port 3636
active
service MYSERVER_2
ip address 192.168.200.38
keepalive type tcp
keepalive port 3636
port 3636
active
content MYSERVERS
add service MYSERVER_1
add service MYSERVER_2
advanced-balance sticky-srcip
vip address 192.168.200.87
protocol tcp
port 80
active
Above is the latest configuration.
10-13-2011 09:28 AM
Hi,
Your server/app might be asking the client to open a connection in port 3636, additionally to the content rule in port 80, add a new rule in port 3636 as the one you used to have but still send the initial request in port 80.
content MYSERVERS
add service MYSERVER_1
add service MYSERVER_2
protocol tcp
port 3636
advanced-balance sticky-srcip
vip address 192.168.200.87
active
Let us know the results.
__ __
Pablo
10-14-2011 03:41 AM
Hi,
It is working for me. Thanks for the support. Appreciated.
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide