Configuring a failover solution

I'm a little confused about what you mean about one ISP not wanting to use the others IP addresses. If I understand you correctly, here is one way to do that you want to do.

Network-------PixA-----HSRPActive------2600-T1 A---ISPA Virtual IP Address Network-------PixA-----HSPRStandby---2600-T1 B---ISPB

By the way are you running any routing protocols here? Let me know if this helps.

ISP A doesn't want to advertise ISP B's rather small block of IPs.

Won't work. This will take care of out bound traffic perhaps, but what about incoming traffic?

Hsb,

This is why I asked if he is running any routing protocols. I'm still not sure if this is exactly what he wants to do.

But IF he can run BGP between the two 2600s and the ISPs, then he can influence the inbound routes using the "AS path prepend" command.

Let's get realistic... no ISP is going to BGP multihome /29 prefixes.

The original poster (OP) is looking for a SOHO like solution (ping based routing with automatic failover and NAT for inside surfers) that is a common feature on high end SOHO toys (e.g. LinkSys RV042) but requires significant effort to support on "real" Cisco routers.

To the OP-- ~~~~~~~~~~~~~~~~~~

Questions like yours come up routinely in this forum, and have been answered before. Try google groups and a search for ping based routing. The good news is that as you describe your environment, you should be able to set up reliable failover (for inside users going out to the Internet, not for outsider's trying to reach services offered on your public IPs). However, there is not enough info to provide specific guidance, nor an indication of what types of services you are trying to preserve.

Load balancing, rather than simple failover, is much more difficult unless you want to buy additional hardware.

Unless multiple servers are explicitly supported by the application, there is no reliable solution for general services offered to the public short of BGP multihoming that will keep inside servers available to outsiders during an ISP failure. So you can protect insiders accessing outside services and incoming email pretty easily, but you should assume that your web site will go down until the ISP supporting its IP address comes back to life.

Good luck and have fun!

If you are providing a service to external users you could consider mounting the service at a hosting company.

Ping Based/Policy Based Routing/SAA based routing

are all worth searching for on Cisco.

There seems to be some disagreement on what to call it:-(