On Wed, Mar 31, 2010 at 10:27 PM, jack daniels <[email protected]>wrote:
> CAN Link state tracking help in this case ? > > can LINK STATE tracking detect remorte upstream failure ? > > > > http://www.cisco.com/en/US/docs/switches/lan/catalyst3750/software/release/12.2_40_se/configuration/guide/swethchl.html > > On Wed, Mar 31, 2010 at 7:25 PM, Harold 'Buz' Dale <[email protected]>wrote: > >> I think there is an LACP timeout – requesting LACPDUs every 30 seconds >> once the link is up by default and this can be changed to every second. >> >> Buz >> >> >> >> *From:* jack daniels [mailto:[email protected]] >> *Sent:* Wednesday, March 31, 2010 9:29 AM >> >> *To:* Harold 'Buz' Dale >> *Subject:* Re: [c-nsp] L2 Link Failover >> >> >> >> But how wil LACP HELP as this LACP handshake is done at the time of >> beginging when PORTCHANNEL COMES up. ONce etherchannel is up , link are >> brought out of the etherchannel ONLY when physical interface goes >> down....EVEN though with LACP enabled how will it detect failure of link in >> middle and TAKE the failed LINK OUT OF ETHERCHANNEL >> >> On Wed, Mar 31, 2010 at 6:54 PM, Harold 'Buz' Dale <[email protected]> >> wrote: >> >> I’d look into using LACP act detect ive on both ends of your channel. >> Something like..Although I guess you won’t need to trunk since it is only >> one vlan. Please let me know if this helps. >> >> Thanks, >> >> Buz >> >> >> >> interface Port-channel1 >> >> description description LACP Channel to SW2 >> >> switchport >> >> switchport trunk encapsulation dot1q >> >> switchport trunk allowed vlan 2 >> >> switchport mode trunk >> >> switchport nonegotiate >> >> no ip address >> >> mls qos trust dscp >> >> >> >> interface GigabitEthernet1/1 >> >> description description LACP Channel to SW2 >> >> channel-group 1 mode active >> >> >> >> >> >> *From:* jack daniels [mailto:[email protected]] >> *Sent:* Wednesday, March 31, 2010 9:12 AM >> >> >> *To:* Harold 'Buz' Dale >> *Subject:* Re: [c-nsp] L2 Link Failover >> >> >> >> I can implement anything or do any changes if it helps my requirement >> >> On Wed, Mar 31, 2010 at 6:35 PM, Harold 'Buz' Dale <[email protected]> >> wrote: >> >> Actually I was thinking that using LACP should detect end-to-end >> connectivity over the MetroE via LACPDUs and even if the MetroE connection >> to the MetroE Cloud shows link, if there is a fault in the cloud, the LACP >> channel should drop until it hears from the other end. >> >> If you are using LACP then I have to get another theory of what I think is >> going on …. >> >> Thanks, >> >> Buz >> >> >> >> *From:* jack daniels [mailto:[email protected]] >> *Sent:* Wednesday, March 31, 2010 8:59 AM >> *To:* Harold 'Buz' Dale >> *Subject:* Re: [c-nsp] L2 Link Failover >> >> >> >> nops not using , how ill FEC help , please help with that >> >> On Wed, Mar 31, 2010 at 6:18 PM, Harold 'Buz' Dale <[email protected]> >> wrote: >> >> Are you using FEC or LACP for your link aggregation? >> Thanks, >> Buz >> >> >> -----Original Message----- >> From: [email protected] [mailto: >> [email protected]] On Behalf Of jack daniels >> >> Sent: Wednesday, March 31, 2010 8:10 AM >> To: [email protected] >> Subject: [c-nsp] L2 Link Failover >> >> Hi guys, >> >> I'm facing a solution challage , appriaciate if you guys can help >> >> >> PC1---(VLAN 2)SW1-----------------METRO ETHERNET Link >> 1 ----------------------------------SW2 (VLAN2)---PC2 >> |---------------------Metro ETHERNET LINK 2 >> ---------------------------| >> >> >> >> I have L2 extended LAN between SW1 and SW2 across Metro ethernet network >> from SP. >> >> I have CONFIGURED ETHERCHANNEL using both LINKS >> >> But issue is when in between my link 1 or my link 2 goes down , BUT My >> links >> in PORTCHANNEL are UP. SO traffic is blackholed. >> >> Please advise >> >> _______________________________________________ >> cisco-nsp mailing list [email protected] >> https://puck.nether.net/mailman/listinfo/cisco-nsp >> archive at http://puck.nether.net/pipermail/cisco-nsp/ >> >> >> >> >> >> >> > > _______________________________________________ cisco-nsp mailing list [email protected] https://puck.nether.net/mailman/listinfo/cisco-nsp archive at http://puck.nether.net/pipermail/cisco-nsp/
