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 'invisible' configuration errors, that only raises its head months or years after the fact.
You could test with a new access point, or change your management IP address and bounce an AP. You can also watch LWAPP debug on the console while power cycling the access point, and/or span the port and verify. Thanks, Josh > -----Original Message----- > From: [EMAIL PROTECTED] > [mailto:[EMAIL PROTECTED] On Behalf Of > [EMAIL PROTECTED] > 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 ---------------------- > From: "Fred Reimer" <[EMAIL PROTECTED]> > > > _______________________________________________ cisco-nsp mailing list cisco-nsp@puck.nether.net https://puck.nether.net/mailman/listinfo/cisco-nsp archive at http://puck.nether.net/pipermail/cisco-nsp/
