Etherchannel

jmc012

Quick question, is it normal to have to do a reload when you configure etherchannel? When I configured it the ports went down and wouldn't even come back up when I removed the commands. But etherchannel does work when I reload the switches.
Thanks

networker050184

No that is not normal behavior. What do you mean by the ports went down and wouldn't come back up?

cisco_trooper

Did you no shut the etherchannel interface??

jmc012

cisco_trooper wrote: »

Did you no shut the etherchannel interface??

networker050184:
The ports were down/down showing not connected.

I'm not sure if I tried a no shut on the etherchannel, but the etherchannel did come up when I reloaded. I'm going to try it one more time doing the no shut on the etherchannel. I thought something didn't seem right.
Thanks

jmc012

jmc012 wrote: »

networker050184:
The ports were down/down showing not connected.

I'm not sure if I tried a no shut on the etherchannel, but the etherchannel did come up when I reloaded. I'm going to try it one more time doing the no shut on the etherchannel. I thought something didn't seem right.
Thanks

Well I tried it again and it worked fine, I'm thinking the last time I did it I took to long to configure it between switches and the ports or the etherchannel went into err-disabled and a shut, no shut would have corrected it instead of a reload. The reason I'm thinking that is the ports went into err-disabled while I was taking off the etherchannel.
Does that sound reasonable?

I just got my switches off e-bay last week, so I finally get to do some real life labs with switches.
Thanks

luke_bibby

You probably configured the links to negotiate an etherchannel using PAgP or LACP so if one side is configured before the other the negotiation would have failed until you brought them down and back up again (or in your case, reloaded the switches)