Is this an
Bjørn Tore @ mobil
Den 13. mars 2013 kl. 23:40 skrev snort bsd snort...@yahoo.com.au:
hi all:
i have a cisco 3750 fastethernet switch connecting to a juniper 4200, with
portchannel on cisco side and aggregated interface juniper side. the cisco
side shows as connected but
Might it be that the EX can't link to FE, but only to GE? I know the -F only
takes gig, unless you use a certain SFP.
Bjørn Tore @ mobil
Den 13. mars 2013 kl. 23:40 skrev snort bsd snort...@yahoo.com.au:
hi all:
i have a cisco 3750 fastethernet switch connecting to a juniper 4200, with
We had issues before with LAGs between cisco and SRX. The links were
showing as up and then intermittently went down. We fixed it by setting
the LACP periodic interval to slow and it corrected it all.
Seems that cisco defaults to slow and Juniper to fast. Just a mismatch in
LACP packets.
HTH
well, both ends are copper links, but links on 3750 are f10/100 and that of
juniper are 10/100/1000.
_dave
From: Jonathan Lassoff j...@thejof.com
To: snort bsd snort...@yahoo.com.au
Cc: juniper-nsp juniper-nsp@puck.nether.net
Sent: Wednesday, 13 March 2013
well, i deliberately not to activate lacp at this moment. just want to see
physical links up...
_dave
From: Eric Krichbaum e...@telic.us
To: 'Jonathan Lassoff' j...@thejof.com; 'snort bsd' snort...@yahoo.com.au
Cc: 'juniper-nsp' juniper-nsp@puck.nether.net
That's correct but in this case one is LACP (802.3ad) and one is not so it
won't bring up the links at all.
Eric
From: snort bsd [mailto:snort...@yahoo.com.au]
Sent: Thursday, March 14, 2013 9:17 AM
To: Jonathan Lassoff; Eric Krichbaum
Cc: juniper-nsp
Subject: Re: [j-nsp] 3750 and 4200
Then you'll have to take them out of the LAG and just have them be normal
ports. Just stick them in an unused vlan for safety and you should be able
to get link. When you're ready to LAG them back use mode active on the
cisco side to the 802.3ad on the Juniper.
Eric
From: snort bsd
I missed paret of this thread, so if this was suggested prior, my
apologies.
On you AE bundle, I believe you need to explicitly define LACP:
ae1 {
aggregated-ether-options {
lacp {
active;
}
-Bill
From: snort bsd
Ive seen this happen with bad sfp as well as not setting mode to active
Try setting up a simple ptp to remove portchan setting out of the equation, if
that works and shows up/up on both ends, try setting to mode active on the
portchan settings
If ur ptp doesn't work... Try diff port,
I'm probably missing an obvious search term, but I didn't find this
myself, so asking...
How does an M10i hash packets to choose a link on a LAG interface? Is
it configurable? This is on a PE-4FE-TX if it matters.
I found a document that says EX switches used a fixed (non-configurable)
hash
On 3/14/13 1:33 PM, Chris Adams wrote:
I'm probably missing an obvious search term, but I didn't find this
myself, so asking...
How does an M10i hash packets to choose a link on a LAG interface? Is
it configurable? This is on a PE-4FE-TX if it matters.
thanks all for replies. both ends (physical are up now, with no lacp. as simple
as just rebooted cisco switch.
really lacp isn't my concern at this moment.
From: snort bsd snort...@yahoo.com.au
To: Jonathan Lassoff j...@thejof.com; Eric Krichbaum
12 matches
Mail list logo