WLC 4404 LAG Mode question

Unanswered Question
Jan 16th, 2008

What port channel id does the controller use or how can I find out? I created the port-channel to the controller and enabled lag mode but the interfaces are not coming up. Any help would be appreciated. Thank you!

I have this problem too.
0 votes
  • 1
  • 2
  • 3
  • 4
  • 5
Overall Rating: 0 (0 ratings)
Loading.
ankbhasi Wed, 01/16/2008 - 20:37

Hi Friend,

When you enable LAG on controller you have to reboot the controller first. Also when it is rebootting you have to go ahead and create channel-group on the switch ports which are connected to the controller and at the time when you define channel group you can define the group number.

Something like this

interface gig1/0/1

switchport trunk encapsulation dot1q

switchport mode trunk

channel-group 1 mode on

interface gig1/0/2

switchport trunk encapsulation dot1q

switchport mode trunk

channel-group 1 mode on

This will automatically create a port channel with number 1 and you can see the same using command "sh etherchannel summary"

HTH

Ankur

*Pls rate all helpfull post

leigh_mcdade Thu, 01/17/2008 - 05:18

Are you using the GLC-T modules in the controller? These have an issue with bringing up the ports on the controller for some reason. I have installed these at a few customer sites and had to reboot the controller several times to get all ports up and in the channel. If the controller goes down for any reason there is no guarantee that all ports will come up in the channel when it comes back online. I think this must be an unfixed bug in the software as it seems to happen across different versions, or a hardware fault on the controller as I have tested the same GLC-T modules in a 3750 and they work fine with my laptop connected to them.

Hope that helps.

schadmin Thu, 01/17/2008 - 07:18

This may be the issue. I will have to check it out when I get in tomorrow. Is it just the GLC-T? If I use the Fiber version of the SFP (I think GLC-MM-SX) then that should be fine?

leigh_mcdade Thu, 01/17/2008 - 07:45

Yes, that's correct. I don't ever recall having the problem with the fibre SFP modules.

dennischolmes Mon, 01/21/2008 - 15:12

Ankur,

Could you verify this with someone in the controller group. It's the first Ive heard of this with the copper modules. This would need to be addressed or the customer would need to create 4 different virtual interfaces for the 4404s when using copper SFP modules to insure reliability.

Actions

This Discussion

 

 

Trending Topics: Other Wireless Mobility

client could not be authenticated
Network Analysis Module (NAM) Products
Cisco 6500 nam
reason 440 driver failure
Cisco password cracker
Cisco Wireless mode