![]() ![]() It started after ClearPass reinstallation. Before this disk expansion, we´ve never seen this issue. The disks on this server are all new now. Last week we expanded the disk capacity of this server and to do this we redeployed ClearPass OVF file, updated to 6.5.6 and restored the databases. ![]() We have beem using this server for a long time to run ClearPass VM. Our ClearPass VM is running on a dedicated server. however the messages come from the ClearPass kernel (which is the component closest to the hardware) and indicate issues/delays with the hardware it is installed on. might any of your harddisks be bad (resulting in hughe disk io delays)? After you validated that the hardware does meet the ClearPass system requirements, can you replace hardware components? Like harddisk, power supply, whole server?Īnd yes, open a TAC case as well in parallel. Or this: (I don't agree with the workaround as if you see these soft lockups performance of your ClearPass will be very poor)įrom the information that I have now, I would thoroughly check the hardware and the VMWare ESXi information. It may be that you are running other VMs on the same hardware.Ĭheck this: (solution was replacing the power supply of the computer) These soft lockups indicate that the hardware cannot handle the load. You pretty sure have issues with your underlying hardware. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |