Discovery-Request on an unsupported VLAN

Unanswered Question
May 22nd, 2007

I keep getting this error on the controller debug logs

"Received a Discovery-Request on an unsupported VLAN 7"

I have my APs tied to VLAN7 and i have option 43 defined on the DHCP VLAN 7 lan scope to point to the controller management interface.

all switch ports connecting to controller are trunked.

I'm guessing i should leave the management interface and the ap-manager interface on an untagged vlan (vlan 0).Right now, both these interfaces are on VLAN3 (user vlan)

Any ideas what i should be looking at to resolve this?

thanks for the assistance!

I have this problem too.
0 votes
  • 1
  • 2
  • 3
  • 4
  • 5
Overall Rating: 0 (0 ratings)
Loading.
ankbhasi Wed, 05/23/2007 - 08:15

Hi Friend,

Even if the management and ap-manager interfaces are tagged it should work. Can you confirm which APs are you having? Also what VCI string have you configured in option 43?

This message confirms that AP had not yet got the controller management interface ip address.

Regards,

Ankur

echelon360 Wed, 05/23/2007 - 16:42

Ankur,

thanks for replying to this post.

I am using the 1232 APs and the VCI string i'm using is "Cisco AP c1200".

It used to work fine before.All this problem started when i placed the management and ap-manager interface on a tagged vlan.

ankbhasi Thu, 05/24/2007 - 06:08

Hi Friend,

Just want to confirm when you changed your management interface to tagged vlan you are allowing that vlan on trunk port connected to switch and that vlan is not configured as a native vlan on your switch.

Regards,

Ankur

echelon360 Thu, 05/24/2007 - 16:11

Ankur,

Our native vlan here is VLAN1

I'm using the 2006 Controller model and i have ports 1-3 connected to my core switch.

On the switchports, this is what i've configured for each interface

switchport trunk encapsulation dot1q

switchport trunk allowed vlan 1-10,153

switchport mode trunk

echelon360 Tue, 06/05/2007 - 22:14

anyone facing these same issues?

Really frustrating trying to find out the exact cause...urgh!

echelon360 Mon, 06/11/2007 - 22:20

this is what i did to resolve this..

Used 12.3.11-JX1(ED) to revert back the APs to autonomous.(have it renamed to "c1200-k9w7-tar.default" before flash)

Once i was able to login to the AP,i started from scratch

-cleaned out previous lwapp configs

"clear lwapp private-config"

-manually added lwapp entries

lwapp ap ip address

lwapp ip ip default-gateway

lwapp ap controller ip address

lwapp ap hostname

APs joined the controller after that.

Hope it resolves for some of your guys

Actions

This Discussion