You have to keep in mind that there are some commands, mostly L1/L2 related, that apply only to individual members, so things can sometimes get more tricky. Hopefully you'll get a warning and nothing more if you try to configure them under the port-channel interface.
-- Tassos [email protected] wrote on 19/1/2013 14:57: > Hi, > >> Known bug? Feature? You can alter a port-channel configuration and >> expect it to propagate to the members, correct? > yes - changes to the port-channel are propagated to the members... if you do > it the > other way around then the interface WONT match the port-channel and the link > will go down. > (and if you only have a single member on that port-channel due to eg a link > being currently > down then that could mean no service/access to the end of that link - classic > chop > your feet off) > > not seen your issue (ie ALWAYS add to the PoXX and seen the changes work..) > > alan > _______________________________________________ > 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/
