[c-nsp] ISP / MPLS "POP" design

[CiscoNSP List]

Thanks Adam,
 
> 1. 
> Last time I compared these, in regular IOS ISIS had more knobs than OSPF and
> vice versa in XR. 
> But what really matters is the versatility of ISIS and adaptability to new
> protocols/features as Mark mentioned. 


Im certainly going to look into ISIS.

> 
> 2.
> As Mark mentioned customer tails can be hooked up via two VLANs one going
> via 4948(A) to 7200(A) and the other one via (B) path. 
> Once you'll have the CE hooked up to two separate PEs, you can than rely on
> fast failover provided by dynamic routing. 
> Don't forget to use per PE/VRF RDs. 


re per PE RD's - So you are suggesting for each PE, I use unique RD's for a given VRF?  I could see this would assist with troubleshooting(Being able to see which PE a route originated from), are there any other benefits/why is this recommended?


> 
> Since you don't own the L2 access/aggregation an extra(backup) VLAN for a
> particular CE will almost certainly result in an additional cost for you
> which translates into premium service for customer. 
> 


Correct - Majority of our customers do choose to have redundant links(So L3 Int on both 7200's, and running dynamic routing for failover)....Im just looking for the best(least manual) way to migrate tails if we lose one of the 7200's.

Thanks again for your responses.