[c-nsp] Redundancy with OSPF

[Pete S.]

you could redistribute the default route, or default route originate,
into OSPF on your edge, one router having a higher metric on the
redist so as to make it a backup connection.

If you want to load balance, leave the metric the same, although
you'll run into some asynchronous routing I'm sure.

Upon growing larger, you may want to look at BGP peering with your ISP
for ease of transition to your own address space, and eventual carrier
redundancy.

--Pete

On 7/11/07, Bruno Filipe <brun0_filipe at yahoo.com> wrote:
> Case study::
>
> The Customer is connecting to the same ISP from two different locations for redundancy purposes. The primary connection to the ISP is the one from R1, THE MAIN IDEA is to have the traffic flowing via the connection between R1 and R2 to the ISP in case the link to ISP via R1 goes DOWN (OSPF is running between R1 and R2)....Can you guys advice taking intno account that there's ip unnumbered to FastEthernet0/0 in Multilink 1 and local network that IP address as gateway to the Internet.
>
>
>
>
>       Public INTERNET
>       |              |
>       |              |
>    ___|__         ___|__
>   |      |       |      |
>   | ISP  |       | ISP  |
>   |Border|       |Border|
>    ------         ------
>      |               |
>      |               |
>      |               |
>    __|__          ___|__
>   |     |        |      |
>   | ISP | \      | ISP  |
>   | Core|   \  / | Core |
>    -----     /\   ------
>      |     /    \    |
>      |   /        \  |
>    __|_/_          _\|___
>   |      |        |      |
>   |  ISP |        | ISP  |
>   | Aggr.|        | Aggr.|
>    ------          ------
>     |               |
>     |               |
>     |               |
>    _|__            _|__
>   |    |          |    |
>   | R1 |----------| R2 |
>    ----            ----
>     |               |
>     |               |
>     |               |
>
>
> [ R1 - Customer ABC site#1 ]
>
> interface Multilink1
>  ip unnumbered FastEthernet0/0
>  no cdp enable
>  ppp multilink
>  multilink-group 1
> !
> interface Multilink2
>  ip address 172.16.0.246 255.255.255.252
>  no cdp enable
>  ppp multilink
>  multilink-group 2
> !
> interface Serial0/0:0
>  no ip address
>  encapsulation ppp
>  ppp multilink
>  multilink-group 1
> !
> interface Serial0/1:0
>  no ip address
>  encapsulation ppp
>  ppp multilink
>  multilink-group 1
> !
> interface FastEthernet0/0
>  ip address 192.168.0.129 255.255.255.224
> !
> ip route 0.0.0.0 0.0.0.0 Multilink1
> !
> router ospf 100
>  log-adjacency-changes
>  network 172.16.1.244 0.0.0.3 area 0
>
>
> [ R2 - Customer ABC site#2 ]
> interface Multilink1
>  ip unnumbered FastEthernet0/0
>  no cdp enable
>  ppp multilink
>  multilink-group 1
> !
> interface Multilink2
>  ip address 172.16.0.245 255.255.255.252
>  no cdp enable
>  ppp multilink
>  multilink-group 2
> !
> interface Serial0/0:0
>  no ip address
>  encapsulation ppp
>  ppp multilink
>  multilink-group 1
> !
> interface Serial0/1:0
>  no ip address
>  encapsulation ppp
>  ppp multilink
>  multilink-group 1
> !
> interface FastEthernet0/0
>  ip address 192.168.0.1 255.255.255.224
> !
> router ospf 100
>  log-adjacency-changes
>  network 172.16.1.244 0.0.0.3 area 0
> !
>
> Regards
>
> Bruno Filipe
>
>
>
> ____________________________________________________________________________________
> TV dinner still cooling?
> Check out "Tonight's Picks" on Yahoo! TV.
> http://tv.yahoo.com/
> _______________________________________________
> cisco-nsp mailing list  cisco-nsp at puck.nether.net
> https://puck.nether.net/mailman/listinfo/cisco-nsp
> archive at http://puck.nether.net/pipermail/cisco-nsp/
>