I'm by no means recommending it, but you could get around the issue by using
something like CE <-> vPE BGP peering..?
Its a hack, but i'm sure you could make it go. Failover times would be
longer, states might get screwed up, just an idea...
On 8 September 2010 08:13, Sascha Pollok wrote:
> O
Hi,
On Wed, Sep 08, 2010 at 09:43:21AM +0100, Phil Mayers wrote:
> That's how HSRP is supposed to work.
s/supposed to work/implemented today/
But yes. *sigh*.
gert
--
USENET is *not* the non-clickable part of WWW!
//www.muc.de/~gert/
On 09/08/2010 08:13 AM, Sascha Pollok wrote:
This reminds me of a long-time wish that I have that has not been
satisfied yet :) As I would like to also influence the traffic
from the backbone to the PE (thus, to connected routes redistributed
into the IGP) I would like to modify the admin distan
On 8 September 2010 08:44, Michael Sprouffske wrote:
So, I have this hsrp lab setup with a coulple PE routers and come CE routers.
Everything works and all is well. I wanna know how the 2 PE routers that are
playing in the hsrp role notify other PE routers upstream or if they do. So
for ex
Hi,
On 8 September 2010 08:44, Michael Sprouffske wrote:
> So, I have this hsrp lab setup with a coulple PE routers and come CE
> routers. Everything works and all is well. I wanna know how the 2 PE
> routers that are playing in the hsrp role notify other PE routers upstream or
> if they do
So, I have this hsrp lab setup with a coulple PE routers and come CE routers.
Everything works and all is well. I wanna know how the 2 PE routers that are
playing in the hsrp role notify other PE routers upstream or if they do. So
for example, I have one CE1 router attached to PE1 and PE2 a
