Hector, Our guys followed a similar process to what Dennis posted and the migration went fine. We went from 12.2(33)SXH8a to 12.2(33)SXJ2 on our 6500's. The way in which you configure the WiSM's/port channels is different. You don't actually configure the channels manually any more, you run specific WiSM commands. That really is the only "gotcha" that I can think of. Everything else is very similar, easier to manage even.
We have been fighting issues with WiSM2 code/HA though. We had to upgrade to 7.4 in order to do N+1, but the 7.4 code that we were running at the time (7.4.100.0) had 1142 AP related bugs, so we were forced to downgrade to 7.3 and hence lost N+1 HA. We have since acquired two more WISM2-HA SKU controllers in order to do AP SSO HA, but then we found our controllers failing back and forth between the HA and the primaries continuously, this would eventually cause the APs to lock up. The guys are working with TAC right now on this and just upgraded things to 7.4.100.60, so we will see how that goes. So far this a.m. the only issue is that our service ports aren't working. We are running about 2100 APs across three WiSM2's. Just keep an eye on your HA setup, ours has been difficult so far, hopefully you have a better experience with it. --Joe On Wed, Jul 31, 2013 at 4:57 PM, Hector J Rios <[email protected]> wrote: > The only thing that I can add of value is that our VLAN subnet sizes will > not change. They will remain at /22's. but now that we are on the 7.4 code, > we will leverage "interface groups" to provide enough IP space to our main > SSID. > > We are not using VSS. We bought HA controllers because they were so > affordable and in the 7.4 code they can function in N+1 mode (haven't > tested yet; just drank the koolaid). > > Regarding v6, there is nothing new, but we have seen issues with multicast > that we've been able to replicate on both WiSM1s and WiSM2s, and also on > the 7.0.116.0 and 7.4.100.60 codes. Basically, a user will obtain an IPv6 > address. When the user moves to another AP in the same controller, that > user no longer receiver RAs. We've tested this with the WiSM in > multicast-multicast mode. Our only solution that we've found at the moment > is to disable multicast on the controller, and surprisingly, that works. > But if we do that, we can take advantage of the new Bonjour gateway > feature. I won't go into that cause it just gives me headaches. > > Thanks, > > Hector Rios, CCNA, CCA > Assistant Director, Network Engineering > Dept. of Networking and Infrastructure > Information Technology Services > Louisiana State University > Phone: (225) 578-1333 > Email: [email protected] > > > -- Joe Roth Networking Group Binghamton University Ph. 607-777-7528 Fax 607-777-4009 ********** Participation and subscription information for this EDUCAUSE Constituent Group discussion list can be found at http://www.educause.edu/groups/.
