What you really want to do is load balancing or clustering. NAT is not the
correct mechanism for this, and you would be better off doing Windows
clustering (assuming it's a windows box), or some other form of cluster
server app. That's if you don't have a LB type device.
As a last resort you could do EEM...
On Mon, May 31, 2010 at 11:27 AM, Ryan West <rwest_at_zyedge.com> wrote:
> Anbu,
>
> > -----Original Message-----
> > Sent: Monday, May 31, 2010 12:17 PM
> > To: Joseph L. Brunner; Cisco certification
> > Subject: Re: NAT with redundancy
> >
> > Thanks Joe ,
> >
> > i have some more to get understand regard this and expect your help ,
> >
> > My exact requirement is, in your example the outside global
> (12.207.43.148)
> > should translate to 192.168.1.50 . if 192.168.1.50 is not available only
> it should
> > be translated to 192.168.1.52.
> >
> > So is there any method to do the NAT with IP SLA to check 192.168.1.50 is
> up
> > / down , then if it is down it want to translate to 192.168.1.52.
> >
>
> I don't think this is possible with NAT by default. You could write an
> EEM script to do that though, track the state of your IP SLA and trigger the
> proper CLI commands.
>
> -ryan
>
>
> Blogs and organic groups at http://www.ccie.net
>
> _______________________________________________________________________
> Subscription information may be found at:
> http://www.groupstudy.com/list/CCIELab.html
Blogs and organic groups at http://www.ccie.net
Received on Tue Jun 01 2010 - 16:03:09 ART
This archive was generated by hypermail 2.2.0 : Sun Aug 01 2010 - 09:11:36 ART