So, I'm still not quite sure what you are looking for, but are you looking for something similar to the below diagram? If so let me know and I can expand on an explaination, or let me know what is missing from this and I'll do my best to get you an example that would be helpful.
Best guess Image http://www.brokenhaze.com/sf_images/demo.png
Ok, so since this seems to be what you are looking to accomplish - I'll go into a little more detail as to what it says (Note as I said in a comment to the question I won't do the work for your but i'll explain it so that you can do it yourself)
First the basic pieces of the diagram. The grey boxes with arrows in them represent the routers, the lines connecting the routers to other pieces are some sort of physical medium - Ethernet, Serial, whatever. The Line with a bunch of little lines represents an Ethernet network which can have just about anything - clients, servers, embedded devices and the like attached to it.
I've used CIDR notation to describe the networks.
Now lets label the routers in the following way:
ROUTER1 - The router with the 192.168.1.1/24 and 192.168.2.1/30 and 192.168.2.5/30 IPs
ROUTER2 - The router with the 192.168.2.2/30 and 192.168.3.1/24 IPs
ROUTER3 - The router with the 192.168.2.6/30 and 192.168.4.1/24 IPs
And now I'll match them up to what you would see from the example you gave me of your sh ip route
This is your output:
C 170.27.0.0116 is directly connected, serial 0/2/0
D 170.26.0.0116 [ 90/20514560 via 170.27.0.1 00:52:15 serial 0/2/0
C 170.28.0.0116 is directly connected . FastEthernet 0/0
A sh ip route on ROUTER2 in my example would produce something similar:
C 192.168.2.0 is directly connected, serial 0/2/0
D 192.168.1.0 [ 90/20514560 via 192.168.2.1 00:52:15 serial 0/2/0
D 192.168.4.0 [ 90/20514560 via 192.168.2.1 00:52:15 serial 0/2/0
C 192.168.3.0 is directly connected . FastEthernet 0/0
What this is telling me is that ROUTER2 knows the following:
- It knows about the 192.168.3.0/24 and 192.168.2.1/30 networks because it has a direct physical connection to them. Meaning it has an interface assigned to an ip on that network that is in an up/up state.
- It knows about the 192.168.1.0/24 network because of a RIP (off the top of my head i think D is the symbol for RIP) announcement to it from ROUTER1
- It knows about the 192.168.4.0/24 network because of a RIP announcement to it from ROUTER1 which would have gotten it's announcement from ROUTER3
So in a very brief summary, this diagram shows you how all the routers are connected and additionally what networks are behind them. You could also put another label on each of the interfaces showing which networks you announce to the other routers via RIP, OSPF, BGP, RIP2, etc.
I hope that helps you out and let me know if you need any more clarification on any of what is going on here.
Put external routers into HSRP/VRRP pair. Get an AS. Start doing BGP with your ISPs.
Then, everywhere inside your environment, the paths will be static. You just need to have failover, and that's what's achieved with VRRP/HSRP and firewalls in A/A or A/S configuration.
Alternatives are messier and/or less robust:
- Dynamic throughout is an unnecessary hassle.
- Static outbound on the firewalls would make it difficult/inflexible/impossible to use both uplinks simultaneously.
- Inbound redundancy will be a world of pain without kludges like PePLink/Ecessa/EdgeXOS.
Best Answer
I think I solved my problem. Because both on CITY and MAIN OSPF is configured, i set up a default route to ISP on main and then issue the command
default-information originate. This will propagate my default route. Also MAIN router will update any change that happens to the default route.Then on CITY i configure a default route to ISP but with a administrative distance greater than 110(OSPF). It seems now that everything is working