Cisco Support Community
cancel
Showing results for 
Search instead for 
Did you mean: 
Announcements

Welcome to Cisco Support Community. We would love to have your feedback.

For an introduction to the new site, click here. And see here for current known issues.

Redundancy of Servers using nat/SLB by checking server aliveness using track and IP sla

My requirements are:--

1. I want to access Machine_2, Machine_3 i.e. 172.19.19.2, 172.19.19.3 in a redundancy mode i.e. Active and passive mode.

2. But always request goes to active say 172.19.19.2 and once this is down then only requests should go to passive say 172.19.19.3.

3. These servers (172.19.19.2 & 172.19.19.3) should be visible to outside world over a virtual IP say 10.150.1.1.

4. Means clients from 10.20.0.0/24 can access these redundant server using V_IP (10.150.1.1).

 

I want some solution/configuration for this problem using cisco L3 switches or routers. Preferably either using nat or SLB.

I had tried, NAT and SLB both but I found some limitations to achieve this requirements.

My observations:--

1. With SLB its difficult to achieve Active/passive kind of redundancy, whereas it's purely working in load balance  fashion. We can only define weight for servers and minimize the requests hitting it. Available Weight value is <1-255> 

2. With NAT I am not able to create nat table for request originating from outside to inside. Once request start from inside to outside then only nat table is creating and lasting for 24 hours i.e default time-out for nat table. If in between primary server goes down, then also nat table is not creating for secondary server unless nat table is forcefully deleted on router.

​So please suggest me some solution to achieve redundancy from outside to inside servers by analyzing their reach-ability in Active/passive mode.

Thanks

Rajesh 

41
Views
0
Helpful
0
Replies