squelchtone

Thanks John, this makes a lot of sense. I just went to Home > Security > Certificate Usage > clicked RADIUS EAP > and changed the cert drop down box for Authentication To The Peer to be: Dummy RADIUS Server Certificate, and down below that I went to Peer Authentication drop down and changed it to Dummy RADIUS Authority and clicked Save. Then I went one tab back to Certificates Store, saw that the expiring ones no longer had anything used them, and clicked the trashcan (bin for my UK friends :-) icon and now all my icons are green and no more annoying warning. I just disconnected a wireless client from the network, made sure the controller no longer saw it as connected, turned wifi back on, connected to wifi and everything is working great, so for anyone reading this down the road, you can rest easy that this shouldn't affect your end users, unless of course you actually are using RADIUS 802.1x authentication from client to AP/controller. Thank you everyone, Squelchtone

Ok, Bradford Networks does not believe that these default certs are used in the process of my controller sending mac addresses over to the Bradford appliance, but they do have concerns that my wireless users may encounter problems as they connect to the access point. I told the Bradford tech that we use WPA2 for authentication, not RADIUS so I think my next step is to open a case with HP and see where that leads. Worst case fumbling around and getting/generating new CA certs and importing them into the wireless controller, right? =)

Hi, I found this forum by googling why my MSM765zl suddenly had this certificate message as everyone else here does. I updated firmware from 6.6.00 to 6.6.5.0-23187 but the cert messages came back again. I use the Radius feature for my wireless clients to use mac based authentication in the VSC against Bradford Networks NAC which keeps track of users macs and puts them on the correct vlan or puts them in the Registration vlan where they get a you must register with your AD credentials web portal. I'm worried that the certs running out will break this mechanism, but I'm not sure if the MSM is the Radius server in my particular setup or if the Bradford appliance is acting as the Radius server. (EDIT: in MSM Authenticaion > Radius Profiles > Primary Radius Server has the IP of my Bradford appliance as the primary Radius server so perhaps I shouldnt worry) I will open a ticket with Bradford, hopefully not their only MSM controller customer. Will follow up if I hear anything, Squelchtone PS and probably it's own question, but does anyone here ever update their controller and then lose visibility of all APs and you have to remote in or go reboot each AP for them to rediscover the controller so they show up in the Detected list? (controller LAN IP and AP IP's are on same vlan, no firewalls or acls to block them from talking, users connect to AP and dump out to the network, they dont tunnel back to controller for their internet access.)