[j-nsp] Too much packet loss during switchover on MPLS network

[Doug Hanks]

I would assume the customer would want to make sure L2 works and fails over before they start stacking on BGP and other goodies.

From: Keegan Holley [mailto:keegan.holley at sungard.com]
Sent: Monday, March 14, 2011 1:08 PM
To: Doug Hanks
Cc: Gökhan Gümüş; Diogo Montagner; juniper-nsp at puck.nether.net
Subject: Re: [j-nsp] Too much packet loss during switchover on MPLS network

If I were a customer I wouldn't accept that.  Especially after the first test failed.
On Mon, Mar 14, 2011 at 4:00 PM, Doug Hanks <dhanks at juniper.net<mailto:dhanks at juniper.net>> wrote:
Can they just ignore all the stuff that’s riding on top of your VPLS service and try pinging across the VPLS tunnel?  For example add secondary IPs to the CE like 10.0.0.0/30<http://10.0.0.0/30>.

From: Keegan Holley [mailto:keegan.holley at sungard.com<mailto:keegan.holley at sungard.com>]
Sent: Monday, March 14, 2011 12:57 PM
To: Doug Hanks
Cc: Gökhan Gümüş; Diogo Montagner; juniper-nsp at puck.nether.net<mailto:juniper-nsp at puck.nether.net>

Subject: Re: [j-nsp] Too much packet loss during switchover on MPLS network

They may be doing BGP with their own resources over the VPLS and pinging something that requires it to be up..  The bottom line is it doesn't take 41s to failover a properly working LSP to another path.

2011/3/14 Doug Hanks <dhanks at juniper.net<mailto:dhanks at juniper.net>>
If it’s VPLS, the customer wouldn’t be using BGP though.  That’s why I mentioned STP.

From: Keegan Holley [mailto:keegan.holley at sungard.com<mailto:keegan.holley at sungard.com>]
Sent: Monday, March 14, 2011 12:47 PM
To: Gökhan Gümüş
Cc: Doug Hanks; Diogo Montagner; juniper-nsp at puck.nether.net<mailto:juniper-nsp at puck.nether.net>

Subject: Re: [j-nsp] Too much packet loss during switchover on MPLS network

Another to way to check would be to figure out when you start seeing mac-addresses from the customer in the vpls tables.  That will mean the network has failed over properly.  Do you know what the customer topology looks like?  They could be waiting for BGP to fail over or something else that inherently slow.  I doubt this is a problem with your mpls config, especially if you see your lsp switch.  It's hard to guess without knowing your's or the customer's topology though.
On Mon, Mar 14, 2011 at 3:42 PM, Gökhan Gümüş <ggumus at gmail.com<mailto:ggumus at gmail.com>> wrote:
No, they are not using rapid ping, i can confirm it.

I do not agree with Spanning tree issue.
Just for note, i am just de-activating one circuit via CLI to trigger transition from primary to secondary.

Gokhan

2011/3/14 Doug Hanks <dhanks at juniper.net<mailto:dhanks at juniper.net>>
I'm sure they were using a rapid ping, so it didn't take anywhere near 45 seconds.  If they were using a regular ping, however, it maybe a STP issue.

Also are you using pre-signaled LSPs?

-----Original Message-----
From: juniper-nsp-bounces at puck.nether.net<mailto:juniper-nsp-bounces at puck.nether.net> [mailto:juniper-nsp-bounces at puck.nether.net<mailto:juniper-nsp-bounces at puck.nether.net>] On Behalf Of Keegan Holley
Sent: Monday, March 14, 2011 11:15 AM
To: Diogo Montagner
Cc: juniper-nsp at puck.nether.net<mailto:juniper-nsp at puck.nether.net>; Gökhan Gümüş
Subject: Re: [j-nsp] Too much packet loss during switchover on MPLS network

On Mon, Mar 14, 2011 at 1:25 PM, Diogo Montagner
<diogo.montagner at gmail.com<mailto:diogo.montagner at gmail.com>>wrote:

> Do you have FRR enabled on the LSPs ?
>

Node protection and link-protection is the same thing as fast re-route.

Is it configured correctly though?  You have to configure a secondary path
under protocols mpls and then enable it for FRR/node protection.  You can't
just enable it and have it work.
Also, what does the topology look like?  Could you just be waiting for
customer routing/spanning tree?  Even without FRR your lsp's failover at the
speed of your IGP when a link is shut down.  None of them take 41 seconds.

>
>
> On Tue, Mar 15, 2011 at 12:46 AM, Gökhan Gümüş <ggumus at gmail.com<mailto:ggumus at gmail.com>> wrote:
> > Dear all,
> >
> > I have a problem with one of our customer.
> >
> > Customer has been deployed with VPLS. We are using primary path and
> > secondary path ( standby ) to handle VPLS traffic between sites.
> >
> > Within a maintenance window, we made a failover test. Customer was
> pinging
> > remote site continuosly and we would like to test how many packets are
> being
> > lost during switchover. When i triggered transition from primary to
> > secondary, customer lost 41 packets during ping test. Then i implemented
> > node-link-protection and link protection in case they help but customer
> > experienced same amount of packet loss during transition.
> >
> > My question, is it a normal behaviour? From my perspective it is not a
> > normal behaviour.
> >
> > Has anybody such an experince?
> >
> > Thanks and regards,
> >
> > Gokhan
> > _______________________________________________
> > juniper-nsp mailing list juniper-nsp at puck.nether.net<mailto:juniper-nsp at puck.nether.net>
> > https://puck.nether.net/mailman/listinfo/juniper-nsp
> >
>
> _______________________________________________
> juniper-nsp mailing list juniper-nsp at puck.nether.net<mailto:juniper-nsp at puck.nether.net>
> https://puck.nether.net/mailman/listinfo/juniper-nsp
>
_______________________________________________
juniper-nsp mailing list juniper-nsp at puck.nether.net<mailto:juniper-nsp at puck.nether.net>
https://puck.nether.net/mailman/listinfo/juniper-nsp