04-21-2015 02:33 AM
Hi All,
Currently Im using nat to translate client source ip address, nat pool is configured on server side vlan interface.
but now I dont want to translate client source ip address:
-I have changed real server gateway to ace interface ip.
-I already remove nat configuration but now I cannot access to the vip using browser but I can ping vip.
But now I cannot access to vip through browser, any idea?
Design:
client--------------CORE--------ACE------------------Real Server.
Thanks
Solved! Go to Solution.
04-21-2015 03:29 AM
Hi Mohamad,
Can you please share the configurations?
Are you facing this problem with a single serverfarm or all of them has got the same issue.
Krishna
04-21-2015 03:29 AM
Hi Mohamad,
Can you please share the configurations?
Are you facing this problem with a single serverfarm or all of them has got the same issue.
Krishna
04-21-2015 03:46 AM
04-21-2015 05:45 AM
Hi Mohamad,
The configuration looks good. Can you please share the output of 'show serverfarm'
Krishna
04-21-2015 09:36 PM
Hi Krishna,
#sh serverfarm
serverfarm type rservers predictor current conns
+--------------------+---------+--------+------------------+---------------
SF_KALAM
HOST 2 ROUNDROBIN 0
SF_Kalam1
HOST 1 ROUNDROBIN 0
SF_Kalam2
HOST 1 ROUNDROBIN 0
SF_Kalam3
HOST 1 ROUNDROBIN 0
04-27-2015 08:17 PM
Need help/advise regarding routing to make this method working.
When I change server gateway to ace server vlan interface, my server cannot communicate with other vlans. From context, I can ping server vlan and other vlans.
*Core interface -172.16.36.254 (server vlan),172.19.30.254(client vlan).
*Lb interface - 172.16.36.70, 172.19.30.65
*Real Server ip is using default gateway 172.16.36.70
Routing what I have done:
CORE- ip route 172.16.36.0 255.255.255.0 172.16.36.70
ip route 172.19.30.0 255.255.255.0 172.19.30.65
LB- ip route 0.0.0.0 0.0.0.0 172.19.30.254
Can someone help me to verify this?
Thanks
04-22-2015 10:04 AM
Additional info:
there is a result of show conn:
conn-id np dir proto vlan source destination state
----------+--+---+-----+----+---------------------+---------------------+------+
1679012 1 in TCP 301 172.16.30.215:60714 172.19.30.62:80 SYNSEEN
1162987 1 out TCP 36 172.16.36.62:80 172.16.30.215:60714 INIT
04-23-2015 06:37 AM
Hi Mohamad,
What is the default gateway configured for the Load Balancer. Where is the IP 172.16.36.254 is configured. Can you please change the default gateway to 172.13.30.x subnet IP.
From the output I see that Sync packets are never completing the 3-way handshake.
Krishna
04-24-2015 02:33 PM
Hi Krishna,
IP 172.16.36.254 is at Core interface, so do I need to change the route to 172.19.30.254 (interface at core)? Already done that but nothing happen.
Info:
*Core interface -172.16.36.254 (server vlan),172.19.30.254(client vlan).
*Lb interface - 172.16.36.70, 172.19.30.65
*Real Server ip is using default gateway 172.16.36.70
After I reboot the real server, it cannot communicate with other vlan after changing it gateway to 172.16.36.70.It seems have routing issue. what would you suggest the routing at core/LB?
thanks
.
04-23-2015 06:49 AM
Add this config as well:
policy-map multi-match int36
class VS_Kalam1
loadbalance vip inservice
loadbalance policy VS_Kalam1-l7slb
loadbalance vip icmp-reply active
class VS_Kalam2
loadbalance vip inservice
loadbalance policy VS_Kalam2-l7slb
loadbalance vip icmp-reply active
class VS_Kalam3
loadbalance vip inservice
loadbalance policy VS_Kalam3-l7slb
loadbalance vip icmp-reply active
class VS_Kalam
loadbalance vip inservice
loadbalance policy VS_Kalam-l7slb
loadbalance vip icmp-reply active
interface vlan 36
description "Server Side"
ip address 172.16.36.70 255.255.255.0
access-group input INBOUND
service-policy input int36
service-policy input management_vlan
no shutdown
Krishna
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