09-20-2011 11:15 AM - edited 07-03-2021 08:48 PM
Hello, we took one of our controllers and turned LAG on and since then it is unreachable on the WCS. The controller is running version 7.0.116.0 and the WCS is running 7.0.172.0. I can access teh WLC no problem through web interface and CLI, as I can also do this with the WCS as well, but the WCS cannot access the WLC.
From CLI i can ping the WCS from the Controller and get a response, but from CLI on the WCS, I cannot ping the controller. Does anyone have any hints?
09-20-2011 12:51 PM
Can you share the switchport config from the switch, the show interfaces from teh WLC and teh WCS IP address?
09-21-2011 07:25 AM
I apologize, I should have posted that in the roiginal post...
On the port group on the Catalyst 6506:
interface Port-channel3
switchport
switchport trunk encapsulation dot1q
switchport trunk native vlan 160
switchport mode trunk
On the switch interfaces gi2/21 - 24 on the Catalyst 6506
switchport
channel-group 3 mode on
from the WCS
ifconfig
eth0 Link encap:Ethernet HWaddr 00:C0:9F:3E:F3:E1
inet addr:172.31.160.251 Bcast:172.31.160.255 Mask:255.255.255.0
inet6 addr: fe80::2c0:9fff:fe3e:f3e1/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:3568683 errors:0 dropped:0 overruns:0 frame:0
TX packets:1892997 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:1315869725 (1.2 GiB) TX bytes:560183509 (534.2 MiB)
Interrupt:177
from the WLC
show port summary
STP Admin Physical Physical Link Link Mcast
Pr Type Stat Mode Mode Status Status Trap Appliance POE
-- ------- ---- ------- ---------- ---------- ------ ------- --------- -------
1 Normal Forw Enable Auto 1000 Full Up Enable Enable N/A
2 Normal Forw Enable Auto 1000 Full Up Enable Enable N/A
3 Normal Forw Enable Auto 1000 Full Up Enable Enable N/A
4 Normal Forw Enable Auto 1000 Full Up Enable Enable N/A
Interface Name................................... management
MAC Address...................................... 00:23:5e:8a:e1:6b
IP Address....................................... 172.31.160.246
IP Netmask....................................... 255.255.255.0
IP Gateway....................................... 172.31.160.254
External NAT IP State............................ Disabled
External NAT IP Address.......................... 0.0.0.0
VLAN............................................. untagged
Quarantine-vlan.................................. 0
Active Physical Port............................. LAG (29)
Primary Physical Port............................ LAG (29)
Backup Physical Port............................. Unconfigured
Primary DHCP Server.............................. 172.31.4.190
Secondary DHCP Server............................ Unconfigured
DHCP Option 82................................... Disabled
ACL.............................................. Unconfigured
AP Manager....................................... No
Guest Interface.................................. No
L2 Multicast..................................... Disabled
09-20-2011 01:47 PM
Any other changes to the network .. ?
09-21-2011 07:25 AM
Not yet, we have 4 controllers that we are going to be putting as a LAG, this is just the first one.
09-27-2011 07:23 AM
Problem solved, took a call to TAC, but the issues was that we had assigned a native vlan on the Port channel, left the managment interface untagged on the WLC, but the AP-manager interface was still tagged on a specific vlan, so the WCS was trying to join the AP-Manager interface instead of the managment. so once we commanded: NO switchport trunk native vlan 160, and tagged the managment interface, everything started working and the WLC joined the WCS.
Thank you Viten Patel of Cisco. Very smart that one
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide