Cisco Support Community
cancel
Showing results for 
Search instead for 
Did you mean: 
Community Member

MPLS Design Best Practices for SP

When deploying a new MPLS backbone for a Service Provider, what will be consider the best practices in general? For example what about the following list and any other items:

- Define the Internet as a VRF?

- Use private ASNs?

- Define a VRF per special service?

- Use at least two route reflectors?

- Use OSPF as IGP?

- Limit the CE-PE routing support to OSPF and BGP?

What will be the best approach for management of the devices? A management VRF or the nodes to natively be on a management network?

What to consider when designing from scratch?

4 REPLIES

Re: MPLS Design Best Practices for SP

William some recommended practises, although you can point out your specific constraints in adopting any.

- Define the Internet as a VRF?

(Yes Logical speperation is the way to go.)

- Use private ASNs?

(No, use a Public AS, you may have to peer outside your AS in a VRF with other AS's)

- Define a VRF per special service?

(This is Perfect , Logical Seperation)

- Use at least two route reflectors?

(Right, atleast 2 and above that depends on the size of your network)

- Use OSPF as IGP?

(I dont see any problems with OSPF in scaling for big networks)

- Limit the CE-PE routing support to OSPF and BGP?

(This aspect shouldnt impact much really, you can very well support all the protocols, as its more of serving your customers, rather than dictating the conditions.

Yes have a seperate VRF for Device Managements (also give a thought for a management subnet, which would be unique across your network)

You should generally start with a overview topology, introdcution of the objectives. And then go ahead with the suggested phy topo,

And then move on to the logical services, beggining from Core IGP, then core BGP, and then all the add on protocols, multicast , MPLS TE etc/. Then you can cover specilized service and their logic and description in the end.

Pretty much, just simply think of building out right from scratch that is Physical Layer and Move to Layer 2 and then Layer 3 Layer 4 .

So basically you doc should be index in a manner following the sequence of the OSI layers, this gives a good flow to the doc. And rest remains is the description of the logic used in each service or deployment method, that would be your skill.

HTH-Cheers,

Swaroop

Community Member

Re: MPLS Design Best Practices for SP

Thanks a lot.

I was wanting to make sure I'm not too far from what can be describe as the best practices.

Now, concerning the private ASN I was referring to the MPLS VPN cloud and not to the Internet VRF. Would it remain true in not using private ASN for the MPLS cloud?

-W

Re: MPLS Design Best Practices for SP

William since you would be designing a SP cloud, its very much possible that you may want to provide peering service as well to end customers (probably to smaller tier 3 kind of internet SP's).

If not, and this design is for purely to provide MPLS services to enterprise customers then you should be good with a private AS, where in your enterprise customers dont request for direct control of the internet and are happy with a default route.

HTH-Cheers,

Swaroop

Community Member

Re: MPLS Design Best Practices for SP

Perfect. This comparison make it more clear.

Thanks.

545
Views
10
Helpful
4
Replies
CreatePlease to create content