: 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
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/
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.
>
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
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
5 matches
Mail list logo
