topic Re: Wireless LAN Controller in Wireless

Wireless LAN Controller

nickh2022 — Sun, 04 Jul 2021 00:14:07 GMT

Hello Everybody,

I have a WLC 4402 plugged into a Catalyst 4507R. My problem is I am unable to ping the WLC from a different VLAN. While reading the document about best practices, it mentions that the fiber port should be configured using dot1q encapsulation but when I try to configure that, I do not get encapsulation as an option. The wierd thing is, other ethernet ports on the switch do have encapsulation configured. Please advise!

Re: Wireless LAN Controller

jeff.kish — Wed, 25 Feb 2009 22:29:18 GMT

Some versions of IOS do not support ISL, so Dot1q is the only option for encapsulation. As such, it does not give you the option to configure encapsulation.

Rather than checking encapsulation, check to make sure the port is in trunk mode. Run the "switchport mode trunk" command on the switchport and see if that works for you.

I will say that this sounds more like a routing issue than anything. By saying that you can't ping it from other VLANs, are you implying that you can ping it from the same VLAN? If so, it sounds like your network isn't able to route to the controller.

A few questions - is this a new subnet? Can the 4507 ping the WLC? Can you ping it from the 4507 from different VLAN interfaces (will require an extended ping to test). Can you ping any other devices on the same subnet as the controller from different VLANs?

Also, make sure you're not trying to ping the AP Manager interface. This interface does not respond to pings.

Thanks,

Jeff

Re: Wireless LAN Controller

nickh2022 — Thu, 26 Feb 2009 13:26:18 GMT

The IOS version is 12.2 (25).

I do have â€œswitchport mode trunk" configured on the port already.

I can ping the WLC on the same VLAN. My computer for example is on a different VLAN and I can not ping the WLC, however from my PC I can ping other devices on the same VLAN as the WLC

It is not a new subnet. I can ping the WLC from the 4507

I am pinging the management interface and it is responding to pings.

Re: Wireless LAN Controller

tkhan — Thu, 26 Feb 2009 13:35:31 GMT

Check for proper mask and default gateway configured in the WLC.

Re: Wireless LAN Controller

nickh2022 — Thu, 26 Feb 2009 14:13:21 GMT

The SM and GW have the correct information. Some of my antonomus AP's have the exact same information as far as SM and GW and I can ping those devices.

Re: Wireless LAN Controller

tkhan — Thu, 26 Feb 2009 15:15:00 GMT

Check your switchport config for the proper "native vlan" assignment for the controller.

Re: Wireless LAN Controller

nickh2022 — Thu, 26 Feb 2009 15:42:22 GMT

I have set the "native vlan" to the appropriate vlan that the controller is located on...Still no communication.

Here is what I have configured on the Fiber port that the controller plugs in to

interface GigabitEthernet6/15

description ***Wirless Controller***

switchport trunk native vlan 20

switchport mode trunk

Now, when I set the native VLAN, I lose the ability to ping the WLC from the switch

Re: Wireless LAN Controller

tkhan — Thu, 26 Feb 2009 15:53:36 GMT

The ap-manager and management interfaces should both be, "untagged", for VLAN Identifier. You set this on initial setup of the WLC.

Re: Wireless LAN Controller

nickh2022 — Thu, 26 Feb 2009 15:55:40 GMT

Ok..right now I do have them "tagged" Do you believe that if I set the Native VLAN and change those two interfaces to "untagged" that it may resolve my issue?

Re: Wireless LAN Controller

jeff.kish — Thu, 26 Feb 2009 16:05:39 GMT

It sounds like a potential VLAN mismatch. Best practice is to have your management interface configured for untagged traffic, so I would advise that.

Is your management interface on VLAN 20? If so, your other option would be to remove the native VLAN statement from the switchport. But I would advise making the change on the controller itself.

Re: Wireless LAN Controller

nickh2022 — Thu, 26 Feb 2009 16:29:23 GMT

Ok...I changed the two interfaces mentioned above to untagged and added back the Native Vlan statement.

However, I still can not ping the WLC from outside its own VLAN.

I setup switchport trunk allowed for the two VLAN's, still no communication.

Re: Wireless LAN Controller

jeff.kish — Thu, 26 Feb 2009 19:18:50 GMT

Can you ping the controller's default gateway from the controller?

Re: Wireless LAN Controller

nickh2022 — Thu, 26 Feb 2009 19:42:57 GMT

Yes, I can.

Re: Wireless LAN Controller

tkhan — Thu, 26 Feb 2009 19:59:50 GMT

Either clear your arp tables in your router and/or reboot your controller.

Re: Wireless LAN Controller

nickh2022 — Thu, 26 Feb 2009 20:20:50 GMT

I've rebooted the controller several times.

Im just confused as to why I can not communicate.

Re: Wireless LAN Controller

tkhan — Thu, 26 Feb 2009 20:28:25 GMT

Ok, enough speculation. Please post the switchport config and controller config. At least the networking part of the controller config.

Re: Wireless LAN Controller

nickh2022 — Fri, 27 Feb 2009 15:11:37 GMT

I am only testing..So I can post my config. Here it is.

Cisco Controller) >show running-config

802.11a cac voice tspec-inactivity-timeout ignore

802.11a cac voice stream-size 84000 max-streams 2

802.11b cac voice tspec-inactivity-timeout ignore

802.11b cac voice stream-size 84000 max-streams 2

aaa auth mgmt local radius

Location Summary

Algorithm used: Average

Client

RSSI expiry timeout: 5 sec

Half life: 0 sec

Notify Threshold: 0 db

Calibrating Client

RSSI expiry timeout: 5 sec

Half life: 0 sec

Rogue AP

RSSI expiry timeout: 5 sec--More-- or (q)uit

Half life: 0 sec

Notify Threshold: 0 db

RFID Tag

RSSI expiry timeout: 5 sec

Half life: 0 sec

Notify Threshold: 0 db

location rssi-half-life tags 0

location rssi-half-life client 0

location rssi-half-life rogue-aps 0

location expiry tags 5

location expiry client 5

location expiry calibrating-client 5

location expiry rogue-aps 5

ap syslog host global 255.255.255.255

--More-- or (q)uit

auth-list add lbs-ssc 00:1b:24:df:f2:5c cbd944156e8248baf99fac0356770099d9dadf5

cdp advertise-v2 enable

dhcp create-scope Test

dhcp address-pool Test 10.1.220.50 10.1.220.60

dhcp default-router Test 10.1.220.237

dhcp enable Test

dhcp dns-servers Test 66.109.229.5 66.109.229.6

dhcp network Test 10.1.220.0 255.255.255.0

local-auth method fast server-key *****

interface create data 220

interface address ap-manager 10.1.120.251 255.255.255.0 10.1.120.237

interface address dynamic-interface data 10.1.220.237 255.255.255.0 10.1.220.237

interface address management 10.1.120.250 255.255.255.0 10.1.120.237

--More-- or (q)uit

interface address service-port 10.1.5.212 255.255.255.0

interface address virtual 1.1.1.1

interface dhcp ap-manager primary 10.1.5.45

interface dhcp dynamic-interface data primary 10.1.5.45

interface dhcp management primary 10.1.5.45

interface dhcp service-port disable

interface vlan data 220

interface port ap-manager 29

interface port data 29

interface port management 29

lag enable

load-balancing window 5

--More-- or (q)uit

memory monitor error disable

memory monitor leak thresholds 10000 30000

mesh security eap

mgmtuser add administrator **** read-write

mobility group domain MVE-WLAN

network telnet enable

network mgmt-via-wireless enable

network otap-mode disable

network rf-network-name MVE-WLAN

sessions timeout 160

snmp version v2c enable

--More-- or (q)uit

snmp version v3 enable

spanningtree port mode off 1

spanningtree port mode off 2

sysname MVE-WLC

time ntp interval 3600

time ntp server 1 192.168.1.253

wlan create 1 MVE MVE

wlan broadcast-ssid disable 1

wlan radio 1 802.11g

wlan session-timeout 1 1800

wlan wmm allow 1

wlan security static-wep-key encryption 1 104

--More-- or (q)uit

wlan security wpa akm 802.1x disable 1

wlan security wpa akm psk enable 1

wlan security wpa wpa1 enable 1

wlan security wpa wpa1 ciphers tkip enable 1

wlan dhcp_server 1 0.0.0.0 required required

(Cisco Controller) >

My switchport config is

interface GigabitEthernet6/15

description ***Wirless Controller***

switchport trunk native vlan 20

switchport trunk allowed vlan 2,20

switchport mode trunk

Re: Wireless LAN Controller

tkhan — Fri, 27 Feb 2009 15:51:26 GMT

Hmmm...you should have a "switchport trunk encapsulation dot1q" on your switch config. Your switch should support dot1q trunking. If that doesn't work, try upgrading the IOS on the switch.

Re: Wireless LAN Controller

nickh2022 — Fri, 27 Feb 2009 16:15:51 GMT

That's kind of my issue. For whatever reason when I go to setup Encapulation on that port, it is not an option. However, other ethernet ports and other fiber ports have it enabled. So I know that my IOS supports it. I have tried other fiber ports, but encapsulation is not an option on those other ports either.

Re: Wireless LAN Controller

tkhan — Fri, 27 Feb 2009 16:27:47 GMT

Try another switch that you know supports dot1q trunking.