[c-nsp] BGP Routing Failover for multiple classes of customers

[Bruce Pinsky]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Richard J. Sears wrote:
> Bruce - 
> 
> You are very close on this issue. Basically its a business model issue. 
> 
> Provider_1 is cheap bandwidth, provider_2 is more expensive bandwidth
> and the customer want cheap unless cheap is broken. So yes, I am trying
> to fix a broken business model with engineering as someone already
> suggested.
> 
> Initially I was going to use PBR support for Multiple Tracking Objects
> and use a set next hop statement in my route maps to manage this process.
> I would use prepending to manage inbound traffic as much as would have
> been possible.
> 
> The problem is very simple - The SUP720 is not supported on the code rev
> required to do this (12.2(25)S) - at least not that I could see. Maybe
> someone could log into CIsco and see if its just my CCO login that
> prevents me from seeing that, but when I hit the SUP720,  12.2 stops at
> 12.2.18 and I show nothing for the SUP720 on 12.3 or 12.4
> 

Nope, the Sup720 is only supported in the 12.2SX release train.  The
features in 12.2(25)S will show up in SX at a later date.

Could you go with a VRF for those customers that need the primary/fallback
model?

- --
=========
bep

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.0 (MingW32)

iD8DBQFDIKCBE1XcgMgrtyYRAiNmAKDWJl6lug6e7FoQPFaqD8RMIonQsACgnFYK
XFNc4QK4yTvIsr8qpgN0ftk=
=qRPR
-----END PGP SIGNATURE-----