Best practice MPLS design/configuration for small service provider

[jackawang]

We are a small regional service provider and did not have MPLS supported on our network.  To start supporting MPLS, I’d like to get opinions and recommendations on the best practice configuration. 

Here is what we have today –

• We have our own BGP AS and multiple /24s.
• We are running OSPF on the Cores and BGP on the Edge routers peering with ISPs.
• We peer with multiple tier-1 ISPs for internet traffic. We do not provide public transit.

What we want for phase one MPLS implementation –

• Configure basic MPLS /vpn functionality.
• No QoS optimization required for phase 1.

We have Cisco ME 3600X for  PE. Any recommendations will be appreciated.

[jackawang]

Any advise or web link would be appreciated. Please help.

[fsebera]

Jack,

Try this link, it has everything you need, perhaps more

http://www.cisco.com/en/US/docs/ios/mpls/configuration/guide/15_1/mp_15_1_book.html

Regards

Frank

[shivjain]

Hi Jack

I have few BCP which I am sharing with you as below mentioned:-

1. Use public AS for MP-iBGP

2. Use Seperate subnets for Loopbacks

3. Never do the summarization of Loopbacks.

4. Follow Hierarchical Design

5. Use SSM in the core for mVPN customers.

6. Try to aviod vrf route leaking

7. Never use two loopbacks in case of Hierarchical Design

8 Try to use different RRs for IPv4 and VPNv4

regards

shivlu jain

www.mplsvpn.info

[devang_etcom]

Not sure what kind of devices or routers you have in your network but looks for if you have support for labeled multicast for MVPN support. That will avoid other complexity of using other control protocols (like PIM) in core.

PE redundancy can be obtained by BGP attributes, CE-PE connectivity can be tunned using IGP or VRRP/HSRP...

You can have mutiple RSVP TEs for various contract traffic and you can bind various kind of traffic to different RSVP Tunnels based on contract or service with your customer.

RSVP-TE with link/node protection design will be of great help to achieve quicker failover.