On Saturday, October 02, 2010 04:58:35 am Chris Evans wrote:
> Cisco is different. They typically don't include layer 2
> overhead on the display/config where as juniper does...
In IOS XR, Cisco now do.
On Ethernet, for instance, in IOS XR on the CRS, for
example, you'd have to explicitly add
Cisco is different. They typically don't include layer 2 overhead on the
display/config where as juniper does...
On Oct 1, 2010 4:55 PM, "Michel de Nostredame" wrote:
> On Fri, Oct 1, 2010 at 4:10 AM, Wojciech Owczarek
> wrote:
>> This is just the way Juniper do things, just that it's not consis
On Fri, Oct 1, 2010 at 4:10 AM, Wojciech Owczarek
wrote:
> This is just the way Juniper do things, just that it's not consistent
> across all of their platforms. I've once been told by a Juniper
> engineer that 1514 vs. 1518 MTU value is displayed (on the EX
> platform at least) because the 4 by
ge-
From: juniper-nsp-boun...@puck.nether.net
[mailto:juniper-nsp-boun...@puck.nether.net] On Behalf Of Felix
Schueren
Sent: 01 October 2010 06:59
To: juniper-nsp@puck.nether.net
Subject: Re: [j-nsp] weird MTU size on "show interface"
On 01.10.10 07:26, Michel de Nostredame wrote:
> Hi,
>
On 01.10.10 07:26, Michel de Nostredame wrote:
> Hi,
>
> I was checking my EX4200 trying to resolve a strange connection
> problem with my vendor through a Metro Ethernet.
> During that time I found another weird situation (it is not related to
> the metroEthernet connection).
>
> I setup two top
Hi,
I was checking my EX4200 trying to resolve a strange connection
problem with my vendor through a Metro Ethernet.
During that time I found another weird situation (it is not related to
the metroEthernet connection).
I setup two topology to test
EX4200.ae0 ===(LACP,trunk)=== ae0.M10
On above
6 matches
Mail list logo
