This is a pretty common error when you are bringing pre-configured devices
together in a chassis cluster.
My advice would be to run the following from edit mode on each box:
delete interfaces
delete vlans
delete security
delete protocols
Then commit and cable them together (control AND
This is a pretty common error when you are bringing pre-configured devices
together in a chassis cluster.
+1
set interfaces fab0 fabric-options member-interfaces ge-0/0/2
set interfaces fab1 fabric-options member-interfaces ge-5/0/2
In case of SRX650 this should be ge-0/0/2 and ge-9/0/2
Hello All
I have two EX4200 switches connected back to back to each other with
interfaces in trunk mode as following:
Case(1) back to back connection using ethernet cable
(VL11 IP: 10.1.1.1/30) EX4200 ---TRUNK
(Ethernet)-EX4200 (VL11 IP: 10.1.1.2/30)
è
I believe it is not valid for Ethernet interfaces dear salbad
-Original Message-
From: juniper-nsp-boun...@puck.nether.net
[mailto:juniper-nsp-boun...@puck.nether.net] On Behalf Of Mohammad Salbad
Sent: Sunday, March 06, 2011 1:41 PM
To: juniper-nsp@puck.nether.net
Subject: [j-nsp] Layer
Ala' Amira would like to recall the message, [j-nsp] Layer 2
Fragmentation.
___
juniper-nsp mailing list juniper-nsp@puck.nether.net
https://puck.nether.net/mailman/listinfo/juniper-nsp
On Sunday, March 06, 2011 07:41:10 pm Mohammad Salbad wrote:
The case is that I didn’t change the configuration on the
switches I just replaced the Ethernet cable with
wireless backhaul devices and then I can’t ping with
larger mtu sizes, and this is because the wireless
devices I’m using
There's no such thing as Ethernet fragmentation. There's no sequence number
field or next frame packet headers and no control message protocol to control
it. You could create a gre tunnel and set the MTU and/or fragmentation there.
Sent from my iPhone
On Mar 6, 2011, at 6:41 AM, Mohammad
7 matches
Mail list logo
