[c-nsp] ISP / MPLS "POP" design
CiscoNSP List
cisconsp_list at hotmail.com
Wed Nov 6 20:26:58 EST 2013
Thanks Mark,
IS-IS does look quite good - Im going to try it out on a few spare 7200's
> > A couple of options:
>
> 1. Customers pay for two links, and either run them
> as active/active or active/backup. You need to
> ask yourself whether protection for your customer
> services is native or a billable add-on.
> Different ISP's have different philosophies,
> especially driven by the nature of local markets.
>
> 2. You mirror VLAN and IP address configuration
> between both routers, and only turn one up when
> the other fails (needs automation to avoid hair
> loss).
I think this is a good option - Config-wise, Im thinking the best way is to have some templated scripts....can Rancid be configured to do something like this? i.e. You enter in variables (vlan, vrf, rd, ip address etc), and rancid creates the config based of a template, and then can also login to each device and apply?
Im also not sure how to automate "turning on" the backup link reliably, and then also to "turn off" the backup link once the "primary" 7200 is back online.
>
> 3. Use MC-LAG, but this is hardware dependent. Plays
> back into point 1), above, commercially.
Dont think this is supported on the 4948 unfortunately...
Thanks again for your responses.
More information about the cisco-nsp
mailing list