our company gets a new Ethernet WAN. I am looking for a working dynamic routing design.
The company more or less wants me to use ospf.
(But i am open to an alternative if there is a good reason)
The WAN consists of one or more vlans. The provider puts a SP-VLAN on his infrastructure for the company, and we are
able to put Customer-VLANS on top of it as needed.
I intend to use as few as possible vlans for the WAN cloud.
We will have 2 routers at each remote site, each connected via ethernet with different bandwidth!! to the WAN cloud/vlan.
My main problem is, if i define one single vlan as WAN, that the primary router at each remote site sees all other
neighbors in the WAN subnet with identical metrics, but their bandwidth is different. I don't have an idea
how to tell ospf that some of the next hops in that single broadcast domain are less preferabl than others.
Here is what i tried:
## Having one single cloud for wan: (single customer-vlan)
- easy to configure
- number of neighbors might be a problem (can grow up to approx 60 neighbors)
- backup router at each site has an high ouput cost that forces traffic to go to the primary router. So far so good.
- primary router with low cost sees all other sites in that cloud with equal metric, even the other sites have
fast and slow ethernet uplinks into the cloud.
##Having one cloud (customer vlan) for primary connections, one cloud (customer vlan) for backup connection.
Backup basically works, BUT:
when the HQ primary connection fails, any other site might act as a transit between primary cloud and backup cloud.
I intended to use a distribute-list out to prevent remote sites from transit, but distribute-list out is not supported in ospf.
So how can i solve this? What might be a good design for that?
Can another routing protocl solve that?