4400, Problems with Trunk Connection

Unanswered Question
Jun 1st, 2007

Hi All, i have 2 4400 Controllers to integrate. Both are connected via LAG, Switchconfig config follows the Deployment Guide. with no dynamic Interface configured, everything works fine. With the first dynamic Interface i configured, my trouble begans. The Mangement Interface is no more reachabel, nor ping or https goes through. With dynamic Interface disabled, everything works fine. I changed to an other chassis, with no Channel Config but with only one Interface and a Trunk, same picture. Any idea? Regards, Michael

I have this problem too.
0 votes
  • 1
  • 2
  • 3
  • 4
  • 5
Overall Rating: 0 (0 ratings)
ankbhasi Fri, 06/01/2007 - 10:07

Hi Michael,

Can you please confirm which version of code you are running? Also can you post the output of "sh interface summary" & "sh lag" and also the port config of switchport on which this controller is connected?



MICHAEL SCHROEDER Fri, 06/01/2007 - 23:13

Hi Ankur, the 4400 are running For the Moment we have disabled LAG and are using a single Trunk Connection. I had checked this befor, LAG was enabled and from the Switch Side the Etherchannel was established. All necessary VLANS were allowed and one of them (which with the Management and AP-Manager IP) were configured as native VLAN. Thank you for replying, best regards, Michael

rupert.wever Sat, 06/02/2007 - 10:14

And are the management / ap-management interface are configured as vlan0 on the controller -or- is the native vlan tagged as well?

MICHAEL SCHROEDER Sun, 06/03/2007 - 01:14

Hi Rupert, the VLAN with the Management/AP-Manager IPs is configured as native on the Trunk and untagged (0) configured on the Controller. Regards, Michael


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