Re: L2 etherchannel interface tracking and shutdown

oh I forgot to tell ya, link state tracking is not an option since there
will be waste of bandwidth.

On Fri, Sep 4, 2009 at 11:10 PM, Radioactive Frog <pbhatkoti_at_gmail.com>wrote:

> Gang,
> I have a scenario below - real life exp.
>
> sw1====ether-channel===SWX-DUMB-L2===========sw2
> Cisco Dumb-no brand Cisco
>
> Connections:
> sw1-port1: mac - aa-aa-aa-aa --- goes to --sw2-port1:mac - cc-cc-cc-cc
> sw1-port2:mac - bb-bb-bb-bb --- goes to --sw2-port2:mac - dd-dd-dd-dd
>
> background:-
> Both are connected using L2 ether-channels. My port channel is up and
> running between sw1 and sw2 (yes having swX in middle, it works). Everything
> working fine. Dumb switch doesn't support anything e.g. UDLD.
>
> Problem: when i disconnect port 2 of sw1, it doesn't gets disconnected
> (error-state) at sw2. Of course the reason being a Dumb switch in middle.
> Now many of you'd think it doesn't work but its working and I have a few
> field application running in the same scenario in production.
>
> Problam: When I disconnect a cable from port#1 - traffic flow through the
> other port e.g. port#2, no problem. but when I unplug cable from port#2 it
> times out and i can see port-channel is still up. of course its the UDLD
> which suppose to shutdown the port to other end to make it work but dumb sw
> doesn't support UDLD.
>
> Now my real qustion is:
> Is it possible to configure IPSLA type of things based on MAC/Layer2 ping
> based to track far end MAC and if its not reacheable via that interface it
> shut it down.
> I can do this using TCL script and EEM on Layer3 port-channeling (IP layer)
> but don't know how to do it on MAC layer.
> so, the situation is if port#2 is down on Sw1 , sw2 shud ping mac
> cc-cc-cc-cc via its port#2 and if it pings do nothing else shutdown the self
> port.
>
> Kind of layer2 SLA on etherchannel
>
> Thankx in advance.
>
> frog

Blogs and organic groups at http://www.ccie.net
Received on Fri Sep 04 2009 - 23:18:20 ART