Re: [c-nsp] LWAPP Problems

2008-05-22 Thread Rupert Finnigan
Hi, Thanks to all who offered advise - It was the IP address in the end. I'd setup DHCP Option 43 to the ap-manager interface address, and not the management one. Now that's corrected all is fine. I'm still confused as to how this particular network has worked in the past though! Thanks again,

Re: [c-nsp] LWAPP Problems

2008-05-22 Thread jason . plank
I have always used the ap-manager interface in my DHCP option 43 configuration. My understanding is that the Management interface is used for controller to controller traffic to terminate EOIP tunnels. I would call your configuration correct now :) -- Regards, Jason Plank CCIE #16560 e:

Re: [c-nsp] LWAPP Problems

2008-05-22 Thread Fred Reimer
Coleman Technologies, Inc. 954-298-1697 -Original Message- From: [EMAIL PROTECTED] [mailto:cisco-nsp- [EMAIL PROTECTED] On Behalf Of [EMAIL PROTECTED] Sent: Thursday, May 22, 2008 9:28 AM To: Rupert Finnigan; cisco-nsp@puck.nether.net Subject: Re: [c-nsp] LWAPP Problems I have

Re: [c-nsp] LWAPP Problems

2008-05-22 Thread jason . plank
] [mailto:cisco-nsp- [EMAIL PROTECTED] On Behalf Of [EMAIL PROTECTED] Sent: Thursday, May 22, 2008 9:28 AM To: Rupert Finnigan; cisco-nsp@puck.nether.net Subject: Re: [c-nsp] LWAPP Problems I have always used the ap-manager interface in my DHCP option 43 configuration. My understanding

Re: [c-nsp] LWAPP Problems

2008-05-22 Thread Joerg Mayer
On Thu, May 22, 2008 at 02:36:32PM +, [EMAIL PROTECTED] wrote: Interesting. Why does it work? speculate If management and ap-manager addresses are in the same VLAN on the controller then perhaps that particular controller model with that particular software will forward the packet to the

Re: [c-nsp] LWAPP Problems

2008-05-22 Thread Higham, Josh
] Sent: Thursday, May 22, 2008 7:37 AM To: Fred Reimer; Rupert Finnigan; cisco-nsp@puck.nether.net Subject: Re: [c-nsp] LWAPP Problems Interesting. Why does it work? -- Regards, Jason Plank CCIE #16560 e: [EMAIL PROTECTED] -- Original message

Re: [c-nsp] LWAPP Problems

2008-05-22 Thread Fred Reimer
] On Behalf Of Higham, Josh Sent: Thursday, May 22, 2008 12:45 PM To: cisco-nsp@puck.nether.net Subject: Re: [c-nsp] LWAPP Problems If an access point has connected to a controller, I believe that it attempts to connect to that controller as part of the discovery process. It is another of those

Re: [c-nsp] LWAPP Problems

2008-05-22 Thread Oliver Gorwits
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Fred Reimer wrote: | When an AP initially connects to a controller it will save the | list of controllers in the same mobility group to NVRAM, and | attempt to connect to those controller (management addresses) | upon reboot. On this point I *think*

Re: [c-nsp] LWAPP Problems

2008-05-21 Thread Joerg Mayer
On Wed, May 21, 2008 at 08:55:39PM +0100, Rupert Finnigan wrote: the setup, and am really stumped as to what's going on. The AP's are assigned their IP's via DHCP with Option 43 configured, and are all in VLAN 3, with the ap-manager interface configured appropriately. I'm wandering if IIRC,

Re: [c-nsp] LWAPP Problems

2008-05-21 Thread Oliver Gorwits
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hi Rupert, Rupert Finnigan wrote: | The controller's been power cycled during a outage, and now none | of the AP's will join back up. The controller is logging these | two messages: | | May 21 20:50:47.987 | spam_lrad.c:1209 LWAPP-3-DISC_INTF_ERR2: