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 [mailto:snort...@yahoo.com.au] Sent: Thursday, March 14, 2013 9:12 AM To: Eric Krichbaum; 'Jonathan Lassoff' Cc: 'juniper-nsp' Subject: Re: [j-nsp] 3750 and 4200 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> Sent: Wednesday, 13 March 2013 9:36 PM Subject: RE: [j-nsp] 3750 and 4200 More likely, it's the forced "on" mode which disables LACP. Try it with mode active. -----Original Message----- From: juniper-nsp-boun...@puck.nether.net [mailto:juniper-nsp-boun...@puck.nether.net] On Behalf Of Jonathan Lassoff Sent: Wednesday, March 13, 2013 8:34 PM To: snort bsd Cc: juniper-nsp Subject: Re: [j-nsp] 3750 and 4200 It's strange that one end shows the interface as up, but the other does not. Is it possible that you're using SFPs that only do 1000base-T? What if you take the individual ports out of the ae / etherchannel and just go point-to-point, does the link show as up then? Maybe try cabling up to the management port (a known 100base-T port) or a laptop and see if the link shows up? At least that way, you could rule out the Cisco being wrong about the link status. --j On Wed, Mar 13, 2013 at 3:40 PM, snort bsd <snort...@yahoo.com.au> wrote: > 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 juniper side remain down. could anyone give me some ideas? no lacp activated on both side. > > for cisco: > > cisco-3750#sh int fast1/0/9 > FastEthernet1/0/9 is up, line protocol is up (connected) > Hardware is Fast Ethernet, address is 0018.b99f.5d8b (bia 0018.b99f.5d8b) > MTU 1500 bytes, BW 100000 Kbit, DLY 100 usec, > reliability 255/255, txload 1/255, rxload 1/255 > Encapsulation ARPA, loopback not set > > cisco-3750#sh interfaces por10 > Port-channel10 is up, line protocol is up (connected) > Hardware is EtherChannel, address is 0018.b99f.5d8c (bia 0018.b99f.5d8c) > MTU 1500 bytes, BW 200000 Kbit, DLY 100 usec, > reliability 255/255, txload 1/255, rxload 1/255 > Encapsulation ARPA, loopback not set > Full-duplex, 100Mb/s, link type is auto, media type is unknown > input flow-control is off, output flow-control is unsupported > Members in this channel: Fa1/0/9 Fa1/0/10 > > > interface Port-channel10 > switchport access vlan 100 > switchport mode access > > interface FastEthernet1/0/9 > switchport access vlan 100 > switchport mode access > switchport nonegotiate > channel-group 10 mode on > > > for juniper: > > user@4200-1# run show interfaces terse ge-0/0/9 > Interface Admin Link Proto Local Remote > ge-0/0/9 up down > ge-0/0/9.0 up down aenet --> ae1.0 > > user@4200-1# run show interfaces ae1 terse > Interface Admin Link Proto Local Remote > ae1 up down > ae1.0 up down eth-switch > > > user@4200-1# show interfaces ge-0/0/9 > ether-options { > no-auto-negotiation; > link-mode full-duplex; > speed { > 100m; > } > 802.3ad ae1; > } > > user@4200-1# show interfaces ae1 > > ae1 { > aggregated-ether-options { > minimum-links 1; > link-speed 100m; > } > unit 0 { > family ethernet-switching { > port-mode access; > } > } > } > > > _dave > _______________________________________________ > juniper-nsp mailing list juniper-nsp@puck.nether.net > https://puck.nether.net/mailman/listinfo/juniper-nsp _______________________________________________ juniper-nsp mailing list juniper-nsp@puck.nether.net https://puck.nether.net/mailman/listinfo/juniper-nsp _______________________________________________ juniper-nsp mailing list juniper-nsp@puck.nether.net https://puck.nether.net/mailman/listinfo/juniper-nsp
