Re: [j-nsp] Design issue when dual homing customer edge equipment to 2 different pop locations

Hi Matt, I used to run VPLS multihoming in my network, I used LDP based VPLS between the MX routers, not BGP based VPLS, that based on our tests LDP based VPLS convergence time (MAC flush) was much faster than BGP based. The loop prevention mechanism I used was vstp, that it gives the ability

Re: [j-nsp] Design issue when dual homing customer edge equipment to 2 different pop locations

puck.nether.net > Subject: [j-nsp] Design issue when dual homing customer edge equipment to > 2 different pop locations > > Hi All, > > What I'm facing is an issue getting a vpls mac table to flush. > > Our typical design with a protected ethernet service would be a

Re: [j-nsp] Design issue when dual homing customer edge equipment to 2 different pop locations

eds. Matt -Original Message- From: Kevin Shymkiw [mailto:kshym...@gmail.com] Sent: Monday, March 12, 2012 3:54 PM To: Haynes, Matthew Subject: Re: [j-nsp] Design issue when dual homing customer edge equipment to 2 different pop locations Is this Internet or P2P? Kevin On Mon, Mar 12, 201

[j-nsp] Design issue when dual homing customer edge equipment to 2 different pop locations

Hi All, What I'm facing is an issue getting a vpls mac table to flush. Our typical design with a protected ethernet service would be a customer edge device ( or devices ) with dual fiber connections up to two separate pop locations. The pop's themselves always have an aggregation switch with 10