Good call anyway, Ryan. Master mode will have no affect in this scenario, AFAIK. Master will only cause this controller to take priority over any other controllers if several share the same group, forcing new APs to land on the Master (knowing where they'd land makes for easier configuration during initial deployment). In the era of WCS, this is less of an issue.
The only other things you can do are check firewalls between subnets (make sure both IPs are allowed, etc). You can try a few 'debug [...]' commands on the controller, but what you may really need is a ladder. -porkchop On 6/10/09 5:49 PM, "Shine Joseph" <[email protected]> wrote: > Yes it is in layer 3 mode > > ----- Original Message ----- > From: "Ryan West" <[email protected]> > To: "Shine Joseph" <[email protected]> > Cc: "Kaegler, Mike" <[email protected]>; <[email protected]> > Sent: Thursday, June 11, 2009 5:30 AM > Subject: Re: [c-nsp] WLC discovery > > > Are you in Layer 2 or Layer 3 AP mode. I forget if this is the actual > name, but you may need to switch to layer 3. > > Sent from handheld. > > On Jun 10, 2009, at 5:26 PM, "Shine Joseph" <[email protected]> > wrote: > >> Thanks Mike for the the quick response. >> >> That means I have to have physical access to the APs which are already >> mounted on the ceiling. >> I am in the process of moving this AP to another subnet and I have >> some 18 >> of them to be moved from a single subnet to different subnets. >> >> I can see this AP regsiters momentarily and de-registers. We are >> running >> code 5.1. >> >> When the AP regsiters I can go to its configuration page and I see >> Hardware >> reset and Reset to Factory defaults. >> >> Any help is appreciated. >> >> Thanks, >> Shine >> ----- Original Message ----- >> From: "Kaegler, Mike" <[email protected]> >> To: "Shine Joseph" <[email protected]>; <[email protected] >>> >> Sent: Thursday, June 11, 2009 4:50 AM >> Subject: Re: [c-nsp] WLC discovery >> >> >>> Boot the AP with the Mode button down to reset its parameter memory. >>> If that doesn't help, hook into console and watch the messages. >>> If that doesn't help, execute some 'debug [...]' statements on the >>> same >>> console. >>> -porkchop >>> >>> >>> On 6/10/09 4:42 PM, "Shine Joseph" <[email protected]> wrote: >>> >>>> Hi, >>>> >>>> A Cisco WLC4402 is configured and working alright. All of the APs >>>> currently >>>> are in the same subnet and hence the discovery do not require DHCP >>>> Option >>>> 43 >>>> or DNS. I want to add another AP that is in a different. When the AP >>>> tries to >>>> register with the WLC, it registers momentarily and un registers. >>>> This >>>> has >>>> happened for eithe DHCP option and DNS discovery. >>>> >>>> I am sure, there is something I have not done to get this working. >>>> Can >>>> anyone >>>> suggest somthing that I should try? >>>> >>>> Thanks in advance, >>>> >>>> Shine >>>> _______________________________________________ >>>> cisco-nsp mailing list [email protected] >>>> https://puck.nether.net/mailman/listinfo/cisco-nsp >>>> archive at http://puck.nether.net/pipermail/cisco-nsp/ >>>> >>> >>> -- >>> Michael Kaegler, TESSCO Technologies: Engineering, 410 229 1295 >>> Your wireless success, nothing less. http://www.tessco.com/ >>> >> >> _______________________________________________ >> cisco-nsp mailing list [email protected] >> https://puck.nether.net/mailman/listinfo/cisco-nsp >> archive at http://puck.nether.net/pipermail/cisco-nsp/ > -- Michael Kaegler, TESSCO Technologies: Engineering, 410 229 1295 Your wireless success, nothing less. http://www.tessco.com/ _______________________________________________ cisco-nsp mailing list [email protected] https://puck.nether.net/mailman/listinfo/cisco-nsp archive at http://puck.nether.net/pipermail/cisco-nsp/
