08-28-2012 08:06 AM - edited 07-03-2021 10:35 PM
I have a Cisco Wireless LAN Controller WCL2112 model. It's currently plugged into an HP Procurve switch on a trunk port. That HP switch is plugged into my Cisco stack on a trunk port. I can reach the WCL just fine through the LAN. But when I plug the WCL directly into the Cisco stack on a trunk port(removing the HP switch), I can't reach the WCL at all, unless I connect to it over wireless. The interface shows it's conneccted and up/up. But no communications are sent across the line. I did a wireshark and can see only ARP request from the WCL.
The trunk port on the stack is set to:
interface GigabitEthernet1/0/1
switchport trunk encapsulation dot1q
switchport mode trunk
CiscoStack1#show interfaces GigabitEthernet 1/0/1 switchport
Name: Gi1/0/1
Switchport: Enabled
Administrative Mode: trunk
Operational Mode: trunk
Administrative Trunking Encapsulation: dot1q
Operational Trunking Encapsulation: dot1q
Negotiation of Trunking: On
Access Mode VLAN: 1 (default)
Trunking Native Mode VLAN: 1 (default)
Administrative Native VLAN tagging: enabled
Voice VLAN: none
Administrative private-vlan host-association: none
Administrative private-vlan mapping: none
Administrative private-vlan trunk native VLAN: none
Administrative private-vlan trunk Native VLAN tagging: enabled
Administrative private-vlan trunk encapsulation: dot1q
Administrative private-vlan trunk normal VLANs: none
Administrative private-vlan trunk associations: none
Administrative private-vlan trunk mappings: none
Operational private-vlan: none
Trunking VLANs Enabled: ALL
Pruning VLANs Enabled: 2-1001
Capture Mode Disabled
Capture VLANs Allowed: ALL
Protected: false
Unknown unicast blocked: disabled
Unknown multicast blocked: disabled
Appliance trust: none
CiscoStack1#
The WCL has 3 VLAN's on it and the SSID of VLAN 1 is our office wireless. VLAN's 1, 3, & 4.
The Cisco Stack is 4 switches. cisco WS-C3750X-48P
This is the first time I've dealt with a wireless lan controller, so it's new to me. I'm reading the docs and it sounds like I need to change the switch port to add the line "switchport trunk allowed vlan add 1,3,4" ? Is that the cause of my problems? I'm trying to get rid of the HP switch and plug the wireless controller directly into my cisco stack.
Solved! Go to Solution.
08-28-2012 09:15 AM
Yes that is what I was looking for. You are tagging the management interface.
What's, should be, happening is the switch is dropping the traffic, dot1q trunks drop traffic if it sees the native VLAN tagged in a packet.
Try this on the port the WLC is connected to
Switchport trunk native VLAN 999
Steve
Sent from Cisco Technical Support iPhone App
08-28-2012 08:12 AM
Is VLAN 1 your management interface? Are you tagging the management in the WLC?
Of you can get to the CLI can you lost the output from show interface summary?
Steve
Sent from Cisco Technical Support iPhone App
08-28-2012 09:11 AM
VLAN 1 is my management interface. I don't know how to tell if the tagging it on the management in the WLC?
(Cisco Controller) >show interface summary
Interface Name Port Vlan Id IP Address Type Ap Mgr Guest
-------------------------------- ---- -------- --------------- ------- ------ -----
ap-manager 1 1 192.168.10.166 Static Yes No
management 1 1 192.168.10.165 Static No No
shop 1 3 192.168.20.151 Dynamic No No
vendor 1 4 192.168.30.2 Dynamic No No
virtual N/A N/A 1.1.1.1 Static No No
Is that what you wanted?
08-28-2012 09:15 AM
Yes that is what I was looking for. You are tagging the management interface.
What's, should be, happening is the switch is dropping the traffic, dot1q trunks drop traffic if it sees the native VLAN tagged in a packet.
Try this on the port the WLC is connected to
Switchport trunk native VLAN 999
Steve
Sent from Cisco Technical Support iPhone App
08-28-2012 09:24 AM
Thanks! I'll try that in a couple hours and report back.
08-28-2012 09:30 AM
Or would it be better to untag the management interface?
08-28-2012 10:00 AM
No you want all interfaces tagged.
Steve
Sent from Cisco Technical Support iPhone App
08-28-2012 03:11 PM
That was it! Thanks Steve. Put the native VLAN to 999 and am able to connect just fine now.
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