07-29-2013 11:36 PM - edited 07-04-2021 12:32 AM
I have my native vlan on my 2504 set on vlan 100 port #1. This is connected to a trunk port # 9 on my 3560. It is setup to allow vlan 100 and use switchport trunk native vlan 100. I am trunking because I have two other wireless vlan's setup as dynamic interfaces on different subnets. I have the same subnets on the 2504 port # 1 and port #9 on 3560. I can put a PC on the port #8 that has switchport access vlan 100. I can ping the switch but I cannot ping the WLC. My switch cannot ping the WLC either. The WLC cannot ping the PC nor the switch?
I am using firmware 7.0.220.0.
Can anyone shed some light on the situation?
Thank you Carlos
Solved! Go to Solution.
08-01-2013 05:38 PM
I think your management interface vlan assignment is wrong. Since you make native vlan 30 on your trunk managment traffic is un-tagged.Therefore you have to set vlan to zero (0) on WLC in order to get this working.
But best practice is to make management vlan traffic tagged in order to have QoS on all wireless traffic. So if you could think about change the native vlan from 30 to something else. In that situation you can keep vlan 30 on WLC side, but native vlan won't be 30
wlc code upgrade is not required
Test this & let me know if it still not working.
HTH
Rasika
07-30-2013 12:39 AM
Hi Carlos,
Please check:
Example:
Switch 3560 Config:
interface FastEthernet1/0/9 ...or ...check your port where WLC is connected
description *** XXXWLAN1 ***
switchport trunk encapsulation dot1q
switchport trunk allowed vlan 100,101.....and others
switchport mode trunk
speed 100
duplex full
Create a VLAN 100 and assign a ip address(Add in vlan database in swicth)...that should be management interface of the WLC
interface Vlan100
description WLAN_Management
ip address 10.xx.100.241 255.255.255.0
Regards
08-01-2013 05:32 PM
I've been away on family matters. Sorry for the late reply.
My switch is configured per your example. I'm just wondering if if may be a firmware issue. I've been reading that an upgrade to the firmware may fix the problem. I will upgrade my firmware in the coming days and see how it goes. Thank you for your input.
Carlos
07-30-2013 12:39 AM
Check the management interface configuration of WLC. Either VLAN setting or Primary interface configuration may be wrong.
If you could post WLC's "show interface detailed management" output, that would help us to find what's missing.
Rasika
08-01-2013 05:39 PM
I've been away on family matters. Sorry for the late reply.
Here is my WLC 2504 Configuration:
Interface Name Management
IP Address 10.13.1.254
IP Netmask: 255.255.255.0
IP Gateway: 10.13.1.1
External NAT IP State: Disabled
External NAT IP Address: 0.0.0.0
VLAN: 30
Active Port: 1
Primary Port: 1
Primary DHCP Server: 10.13.1.254
ACL: unconfigured
AP Manager: Yes
Guest Interface: No
L2 Multicast: Disabled
VLAN 10 Dynamic Interface used for wireless a
VLAN 20 Dynamic Interface used for wireless b
Any suggestions would be greatly appreciated it.
Thank you
Carlos
07-30-2013 07:32 AM
Can you post your running config? WLC & Switch
08-01-2013 05:28 PM
I've been away on family matters, sorry for the late reply. Any help I would appreciate.
WLC 2504:
Interface Name: Management
IP Address: 10.13.1.254
IP Netmask: 255.255.255.0
IP Netmask: 10.13.1.1
External NAT IP State: Disabled
External NAT IP Address: 0.0.0.0
VLAN: 30
Quarantine VLAN: 30
Active Physical Port: 1
Primary Physical Port: 1
Primary DHCP Server 10.13.1.254
ACL: unconfigured
AP Manager: Yes
Guest Interface: No
L2 Multicast: Disabled.
Vlan 10 Dynamic Interface used for wireless a
Vlan 20 Dynamic Interface used for wireless b
====================================
Cisco 3560 Switch
Interface GigabitEthernet 0/1-8
Description Connected to the LAP
switchport access vlan 30
switchport mode access
power inline never
Interface GigabitEthernet 0/9
Description Trunk Port Connected to WLC
switchport trunk encapsulation dot1q
switchport trunk native vlan 30
switchport trunk allowed vlan 10,20,30
switchport mode trunk
Interface GigabitEthernet 0/10
Description Trunk Port Connected to ASA5520
switchport trunk encapsulation dot1q
switchport trunk native vlan 30
switchport trunk allowed vlan 10,20,30
switchport mode trunk
interface Vlan1
no ip address
shutdown
interface vlan30
ip address 10.13.11.253 255.255.255.0
ip default-gateway 10.13.1.1
08-01-2013 05:38 PM
I think your management interface vlan assignment is wrong. Since you make native vlan 30 on your trunk managment traffic is un-tagged.Therefore you have to set vlan to zero (0) on WLC in order to get this working.
But best practice is to make management vlan traffic tagged in order to have QoS on all wireless traffic. So if you could think about change the native vlan from 30 to something else. In that situation you can keep vlan 30 on WLC side, but native vlan won't be 30
wlc code upgrade is not required
Test this & let me know if it still not working.
HTH
Rasika
08-02-2013 03:37 PM
Hello Rasika
Thank you for the feedback.
I adjusted my switch and changed the switchport trunk native vlan to 40 and added vlan 40 to the allowed on the trunk.
I can now communicate properly on VLAN 30 with no issues.
Appreciate your help
Carlos
08-02-2013 04:25 PM
Hi Carlos,
Glad to hear that works for you....
Also thanks for giving me rating on that...
Rasika
07-30-2013 02:23 PM
Hello Carlos,
As per your query i can suggest you the following solution-
Please check the management console or interface of the WLC.
Hope this will help you.
08-01-2013 05:34 PM
I have been away on family matters. Sorry for the late reply. I have checked per your suggestion. I have been doing some research and a recommended path is to upgrade the firmware. I shall try this next. Thank you for your input.
Carlos
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