On Fri, Sep 19, 2008 at 08:36:25AM -0500, Richard A Steenbergen wrote:
Juniper includes all L2 overhead
Not really. For Ethernet, Juniper does NOT include the 4 octets FCS
(frame checksum). So Cisco 1500 == Juniper 1514, not 1518 as one might
guess. Now enable vlan-tagging on the Juniper
On Sun, Oct 05, 2008 at 01:48:41PM +0200, Daniel Roesen wrote:
On Fri, Sep 19, 2008 at 08:36:25AM -0500, Richard A Steenbergen wrote:
Juniper includes all L2 overhead
Not really. For Ethernet, Juniper does NOT include the 4 octets FCS
(frame checksum). So Cisco 1500 == Juniper 1514, not
Thank you all !!!
Regards,
Swamy
--- On Sat, 9/20/08, Harry Reynolds [EMAIL PROTECTED] wrote:
From: Harry Reynolds [EMAIL PROTECTED]
Subject: RE: [j-nsp] BGP Hold time expiry
To: Richard A Steenbergen [EMAIL PROTECTED], juniper-nsp@puck.nether.net
Cc: [EMAIL PROTECTED]
Date: Saturday, September
Hi,
The EBGP session failed between Juniper and other vendor with the following log
in Juniper Chassis.
Juniper chassis sent the Hold timer expired Notification and ceased the session.
Could you please let me know the reason for this Holdtime expiry? Were there
any TCP session failure or any
@puck.nether.net
Cc: Narayana Swamy
Subject: [j-nsp] BGP Hold time expiry
Hi,
The EBGP session failed between Juniper and other vendor with the following log
in Juniper Chassis.
Juniper chassis sent the Hold timer expired Notification and ceased the session.
Could you please let me know the reason
- Original Message -
From: Harry Reynolds [EMAIL PROTECTED]
Aside from a problem with the EBGP link, I am thinking
perhaps a PMTU issue. [...]
I used to run into this type of thing on FRF.16 FRATM
links, where the ATM side is a Cisco device -- MTU=4470B on
the Cisco and 1600B on the
On Fri, Sep 19, 2008 at 10:20:47AM -0700, Kevin Oberman wrote:
Looks a lot like an MTU mismatch. BGP does not do PMTU and sets do not
fragment, so the MTUs need to be the same on both ends. Things like VLAN
or tunneling can mess this up.
You can try capturing the traffic to confirm this. I
@puck.nether.net
Cc: [EMAIL PROTECTED]
Subject: Re: [j-nsp] BGP Hold time expiry
On Fri, Sep 19, 2008 at 10:20:47AM -0700, Kevin Oberman wrote:
Looks a lot like an MTU mismatch. BGP does not do PMTU and sets do not
fragment, so the MTUs need to be the same on both ends. Things like
VLAN
8 matches
Mail list logo