Totally agree, DHCP + option 43? I think it's 43. I forget :) -- Regards,
Jason Plank CCIE #16560 e: [EMAIL PROTECTED] -------------- Original message ---------------------- From: Mike Louis <[EMAIL PROTECTED]> > You should be assigning the WLC controller names in the LWAPP AP > configuration > using their system name. You can use DNS entries to make the transition > easier. > Do not use IP addresses though. As long as the AP can join one controller, > and > that controller is in the same mobility group as all the other controllers, > the > AP will be able to download the controller list during its first join. I > normally prefer to use DHCP + Options for LWAPP assignment and controller > configuratios. Makes setup and changes much easier. YMMV > > mike > > > > -----Original Message----- > From: [EMAIL PROTECTED] > [mailto:[EMAIL PROTECTED] On Behalf Of Jeff Cartier > Sent: Wednesday, April 16, 2008 11:06 AM > To: [email protected] > Subject: [c-nsp] Cisco LWAPP - statically assigned controller...Controller IP > has since changed. > > Greetings! > > > > So I'm running into a issue where I've configured a bunch of Cisco > LWAPPs. The idea was to statically assign the IP address and to which > Controller (Primary/Secondary) the LWAPP would join. > > > > Everything worked fine. No issues. > > > > A couple days later I found out that the WLC Management + AP Manager > subnets would have to change. Since the LWAPPs are configured > statically to look for and join on a specific subnet that doesn't exist, > whats the simplest way to tell these LWAPPs (that are statically > configured) to find the new WLC IP address? > > > > Thanks!!! > > _______________________________________________ > cisco-nsp mailing list [email protected] > https://puck.nether.net/mailman/listinfo/cisco-nsp > archive at http://puck.nether.net/pipermail/cisco-nsp/ > > > Note: This message and any attachments is intended solely for the use of the > individual or entity to which it is addressed and may contain information > that > is non-public, proprietary, legally privileged, confidential, and/or exempt > from > disclosure. If you are not the intended recipient, you are hereby notified > that > any use, dissemination, distribution, or copying of this communication is > strictly prohibited. If you have received this communication in error, > please > notify the original sender immediately by telephone or return email and > destroy > or delete this message along with any attachments immediately. > > _______________________________________________ > cisco-nsp mailing list [email protected] > https://puck.nether.net/mailman/listinfo/cisco-nsp > archive at http://puck.nether.net/pipermail/cisco-nsp/ _______________________________________________ cisco-nsp mailing list [email protected] https://puck.nether.net/mailman/listinfo/cisco-nsp archive at http://puck.nether.net/pipermail/cisco-nsp/
