High Memory Utilization on WAE Standby Central Manager
Need to help / suggestion on this one. We have 1 primary Central Manager and 2 Standby Central Manager. No issues since deployment ( 2 years ) . Lately ( since 1 month ago ) , the 1 of the stanby central manager's memory is being over utilized by multiple java processes. It goes up to around 85% and stays there until it is rebooted. After reboot , memory utilization returns to normal but slowy builds up again until we hit the 85 - 90% before going for another round of reboot.
Checked for bugs but could not find any. Software version is 4.2.1. Since its a standby central manager , I find it weird that the memory is being overutilized. I have read in this same CISCO forum that monitoring memory utilization for WAE is not really a good way to determine performance , but this is the Stanby Central Manager. Does the statement above apply to the Central Managers as well.
Introduction This article will help you understand the steps on how to
download the UCS licenses from the Cisco Systems website and then
installing it on the UCS. The redacted (blue lines) just covers up
certain numbers for privacy please do not take them...
Introduction This article will help you understand and educate the
customer on how to clear their "expired licenses"
(license-graceperiod-expired) from their UCS-M. If a customer just
purchased a license and needs a step by step guide on how to download
==================== VIC FNIC driver does not support Virtual Volumes (
second level LUN ID ) An enhancement request has been created to track
this feature - CSCux64473 UPDATE - 12-14-2016 We made some traction on
the enhancement request - The Fix is in t...