Search the Community
- Global Forums
- ClearPass Recipe Review
- ClearPass Recipe Submission
- Admin Tool - Assign Role in Bulk
- Admin Tool - User Search
- CWNP Conf 2015
- Airheads Conference Vegas 2015
- Wlan Pro Conference 2015
- Airheads Conference Shanghai 2014
- WLAN Pro Conf EU 2014
- CWNP Conference 2014 (Sep 22 - 24)
- Airheads Local 2014
- Wireless Field Day 7 (Aug 6-8, 2014)
- Black Hat 2014 Contest
- Airheads EMEA Italy 2014 (June 9 - 13)
- Americas Airheads Conference 2014
- WLAN Professionals Summit 2014
- Airheads Roadshow 2013
- EMEA Airheads Conference 2013
- APJ Airheads Conference 2013
- Americas Airheads Conference 2013
- Americas Airheads Conference 2012
- APJ Airheads Conference 2012
- EMEA Airheads Conference 2012
- Airheads EMEA 2012 Contest: How to Enter - Contest Terms & Conditions
- Airheads EMEA 2012 Contest: Create your Entry to Win Here!
- Airheads Conferences Prior to 2012
- Americas Airheads Local Events 2012
- EMEA Airheads Local Events 2012
- Wireless Field Day 3 @ Aruba Networks
- Wireless Tech Field Day 2- Silicon Valley
- Wi-Fi Mobility Symposium- San Jose, CA USA
- SDN Apps
I think we may have solved this one. A little while back we migrated the VLANs for our dot...
I think we may have solved this one.
A little while back we migrated the VLANs for our dot1x environment off of our core switch to our Palo Alto 5050. It appears that in that transition we left the address for this particular VLAN on the core as well as putting it on the P.A. box. Once this was corrected, smart phones consistently began to work properly. So in essence it was an IP conflict which would explain its intermittent nature. Now why laptops still worked fine during all of this is still a mystery to me, but I'm not one to look a gift horse in the mouth so to speak.
So, so far so good!
On the plus side all of my actual wireless configurations have been vindicated! :-)
Thanks to Ryan for all the help, much appreciated!
Onboard is licensed based on the number of valid device credentials that have been provisioned. Tha...
Onboard is licensed based on the number of valid device credentials that have been provisioned. That is, as the crdentials expiry or are reovked they will be removed from the license count. We have seen some educational customers use expiry dates based on the final semester so the credentials are automatically released from the licensing count when the students leave.
Just a few thoughts 1) I agree that 5 GHz is becoming very widespread 2) However, 2.4 ...
Just a few thoughts
1) I agree that 5 GHz is becoming very widespread
2) However, 2.4 still needs to be treated appropriately
- Number of client drivers still do not behave well with band steering and do not necessarily select 5 GHz
- 2.4 should be deployed with the power set 5- 8 dB less than 5 GHz radio in the same chassis
- the extra chains make the link more robust due to diversity benefits
- If you get a DFS event the 2.4 needs to be properly tuned to preseve your customer experience.
- 2.4 should generally be left on to ensure anyone connected to 2.4 is on the nearest AP and getting a decent user experience
- Turn off your b rates and even a couple of the low gn rates. This reduces the beacon time consumption and improves 2.4 performance.
So even if the 2.4 band performance is less than 5 GHz it is still 60 MHz of spectrum that you have access to and, deployed properly, adds value to your end customers.
If PoE is a constraint, then as someone mentioned AP-215 is a great option outside of higher density areas.