cool, thanks for all the advise guys. I think i'm getting a better grip on how to tackle the project.
one tower has 12 x PMP450s covering about 200* so lots of overlap. The other tower has 6 x PMP450s covering 160* on the 12 AP tower i think i'm going to leave the 2 outer APs on the current color code and one other in the center of the cluster (the SMs connected to the edge APs can't really see the other APs better than a -75 to -80 anyway). if I leave those three then I only have to monkey with 9 APs instead of all 12 lol. I wish the canopy SM was better at selecting the "best" AP but we often end up with one AP with 70-80 clients and the AP next door has 10 clients. once we drop all sessions they seem to migrate back to a more balance load per AP but after a couple days everything is out of balance again and we have to drop all session etc. with color code priority we will have more control over the balancing act. :-) -Sean On Mon, Mar 21, 2016 at 2:23 PM, Darren Shea <[email protected]> wrote: > It’s been a while, but I remember my steps (going from one omni to > multiple sectors) being like this: > > > > 1. Put up new sectors, but don’t turn on transmit > > 2. Set all new APs to the same color code as the omni. Grab a > snapshot of all connected SMs from the omni > > 3. Reboot all SM’s (Perl script using SNMP and proxy IP), while at > the same time turning on the transmit on the new sectors, and off on the > omni > > 4. Make sure (after a reasonable time) that each SM has registered > (with a good signal level, of course), if so… > > 5. Under the assumption that each SM has chosen the best AP > available, program the appropriate new color code into each of the SMs > connected to each sector (another perl script using SNMP and the proxy IP). > > 6. After double-checking everything, set the new sector color codes > and reboot all simultaneously > > 7. Verify all SMs are registered, and you’re done! > > > > *From:* Af [mailto:[email protected]] *On Behalf Of *Sterling Jacobson > *Sent:* Saturday, March 19, 2016 2:14 PM > *To:* [email protected] > *Subject:* Re: [AFMUG] Canopy moving from 1 color code per tower to 1 > color code per AP > > > > I think you could add secondary and tertiary color codes to the AP’s, then > just go through the SM’s and change their CC to whatever works best for > them. > > > > I seem to recall doing that often years ago, but not sure if there is an > easier way other than manually. > > > > I know JAB had written a very nice platform to do something like this with > Canopy, again, years ago. > > > > *From:* Af [mailto:[email protected] <[email protected]>] *On > Behalf Of *Sean Heskett > *Sent:* Saturday, March 19, 2016 1:05 PM > *To:* [email protected]; [email protected] > *Subject:* [AFMUG] Canopy moving from 1 color code per tower to 1 color > code per AP > > > > Hi Gang, > > > > due to historical reasons that are no longer valid we currently have 1 > color code assigned to all APs per tower. I'd like to move to 1 color code > per AP. However, this would require first gathering all the data from the > SMs as to which AP is their best, which is second best and which is third > best (we often have multiple APs aimed in almost the same direction). We > have hundreds of APs and thousands of SMs so having a monkey log into each > SM and log this data would probably take a couple lifetimes haha. > > > > Before I go hire someone to write some scripts and create a database to > get this project going, I was wondering if any of you have already done > this and if you have any software tools you'd be willing to share/sell. > > > > Also if anyone else is thinking of doing this would you want to go in on > the development together? (if no one else has accomplished this) > > > > thanks, > > > > -Sean >
