Re: [j-nsp] path-mtu-discovery

2009-10-09 Thread Harry Reynolds
: Harry Reynolds Cc: juniper-nsp Subject: RE: [j-nsp] path-mtu-discovery Harry, Experts, that makes a lot of sense: mss is an indirect indication of the mtu But what about non TCP traffic, ICMP for example, 'path-mtu-discovery' doesn't seem to work. Following setup shows that when j

Re: [j-nsp] path-mtu-discovery

2009-10-09 Thread Bit Gossip
r-nsp-boun...@puck.nether.net > [mailto:juniper-nsp-boun...@puck.nether.net] On Behalf Of Bit Gossip > Sent: Thursday, October 08, 2009 5:08 AM > To: juniper-nsp > Subject: [j-nsp] path-mtu-discovery > > Experts, > I guess that the effect of this command is to maintain a cach

Re: [j-nsp] path-mtu-discovery

2009-10-08 Thread Harry Reynolds
nsp-boun...@puck.nether.net] On Behalf Of Bit Gossip Sent: Thursday, October 08, 2009 5:08 AM To: juniper-nsp Subject: [j-nsp] path-mtu-discovery Experts, I guess that the effect of this command is to maintain a cache of all the active connection and for each of them assign the discovered value of the

[j-nsp] path-mtu-discovery

2009-10-08 Thread Bit Gossip
Experts, I guess that the effect of this command is to maintain a cache of all the active connection and for each of them assign the discovered value of the max mtu allowed accross the path. At least the output of 'show system connections inet extensive' doesn't show any trace of PMTU; Anyidea of w

Re: [j-nsp] Path MTU Discovery - MPLS VPN

2009-05-27 Thread tim.hunt
: mas...@nexlinx.net.pk Subject: Re: [j-nsp] Path MTU Discovery - MPLS VPN To: tim.h...@bt.com Cc: juniper-nsp@puck.nether.net Message-ID: <28064.196.46.241.57.1243439161.squir...@nexmail1.nexlinx.net.pk> Content-Type: text/plain;charset=iso-8859-1 the vrf IP address is drawn from a

Re: [j-nsp] Path MTU Discovery - MPLS VPN

2009-05-27 Thread masood
path mtu check requires at least one IP address must be associated with each vrf. If an IP address is not associated with the routing instance, icmp reply messages cannot be sent. BR// Masood Blog: http://weblogs.com.pk/jahil/ > Hi, > > I've been trying to get Path MTU Discovery working for M/

Re: [j-nsp] Path MTU Discovery - MPLS VPN

2009-05-27 Thread masood
009 16:28 > To: Hunt,TJ,Tim,DMH2 R > Cc: > Subject: Re: [j-nsp] Path MTU Discovery - MPLS VPN > > path mtu check requires at least one IP address must be associated with > each vrf. If an IP address is not associated with the routing instance, > icmp reply messages cannot be sent. >

Re: [j-nsp] Path MTU Discovery - MPLS VPN

2009-05-27 Thread tim.hunt
look at the RFC. Cheers, Tim. -Original Message- From: mas...@nexlinx.net.pk [mailto:mas...@nexlinx.net.pk] Sent: 27 May 2009 16:28 To: Hunt,TJ,Tim,DMH2 R Cc: Subject: Re: [j-nsp] Path MTU Discovery - MPLS VPN path mtu check requires at least one IP address must be associated with each vrf

[j-nsp] Path MTU Discovery - MPLS VPN

2009-05-27 Thread tim.hunt
Hi, I've been trying to get Path MTU Discovery working for M/J-series, appreciate that the M-series requires vrf-mtu-check setting. Having done this I've tried testing it by launching Pings (DF set) with a larger MTU than the link, but I'm getting no response at all - expecting ICMP response. Ha