[j-nsp] MTU problem

S B akdamar at gmail.com
Mon Apr 25 10:14:58 EDT 2005


Hi ,
I did not understand double push issue at the ingress PE1 as mentioned
 Dang's mail. .According to my opinion there are two mpls header ,that
is correct but one of this vpn header and the other  is ldp
header.That is why there are 2 mpls header.One mpls header adds 4
bytes header.So total mpls headers 2x4=8 bytes.

Anyway I solved the mtu problem.Increasing the mtu size in PE routers
solved the problem.

Thanks all of you for your kindly helps..

On 4/25/05, Dang Hai <danglhai at gmail.com> wrote:
> Packet from site A is double push at the ingress PE1, so it contains 2 mpls
> labels in this vpn scenario.
> 
> Need to increase mtu between Pe-P to max support mtu + 2 x 20 bytes (at
> least)
> 
> Dang
> 
> ----- Original Message -----
> From: "S B" <akdamar at gmail.com>
> To: <juniper-nsp at puck.nether.net>
> Sent: Thursday, April 21, 2005 4:26 PM
> Subject: [j-nsp] MTU problem
> 
> > Hi all,
> >
> > site A -----  PE1--- MPLS cloud ---- PE2 --- site B
> >
> > There is a SAP server on site B.The users on site A  could not login
> > SAP server.However they can reach every server on Site B and they
> > could use SiteB's internet connection.There is no any filter on the PE
> > routers.I think this is a mtu problem .The mtu of ldp running
> > interfaces is 1488 btye.I increase it 1500.But it did not solve my
> > problem.Have you got any idea about the problem?
> >
> > Best Regards.
> >
> > Ps:There are cisco routers and cisco switches on site a and site b.The
> > pe routers are juniper.
> >
> > _______________________________________________
> > juniper-nsp mailing list juniper-nsp at puck.nether.net
> > http://puck.nether.net/mailman/listinfo/juniper-nsp
> 
>



More information about the juniper-nsp mailing list