Reading into this more I don't think it will do what I'm looking for it to do..
I have two paths that I'd like to port-channel. Since they don't support LACP the only thing I can do is do static configuration, but if the path of one of the links takes a hit there is no end to end notifications that will cause an interface to go down or be taken out of forwarding. With LACP you can do this because the ports will debundle. I was hoping that CFM would take the path out of service, but I don't think that is the case. Thoughts? On Tue, Feb 5, 2013 at 12:20 PM, Chris Evans <[email protected]>wrote: > Oh really... I was reading on CFM, but though it used the EOAM DMACs... > > let me check into that more! thanks! > > Anyone have details on using CFM? > > > On Tue, Feb 5, 2013 at 3:10 AM, Adam Vitkovsky <[email protected]>wrote: > >> Have you tried CFM? It uses standard Ethernet frames, though CCMs are >> mcast >> frames >> >> >> adam >> >> > _______________________________________________ cisco-nsp mailing list [email protected] https://puck.nether.net/mailman/listinfo/cisco-nsp archive at http://puck.nether.net/pipermail/cisco-nsp/
