I built a new custom report to show the Top Cisco Nodes in my network by CPU utilization, and shared it with my Network Team.
One of them did some digging on nodes with unexpectedly high CPU utilization and came up with a Bug Tool entry that suggests any high CPU alarms MIGHT be false alarms. The information offers alternate methods of polling to compensate and correct for false high CPU alerts.
I thought some of you might be interested:
Linux kernel cache is leading to confusion over memory usage
Anything to save the SW Help Desk folks from getting useless tickets from us!
It's hard when any manufacturer's gear doesn't respond to standard polling OIDs the way it's supposed to.
Anytime you folks at Solarwinds want to buy out Cisco & redesign their IOS and hardware so it's all standard, that'd be OK by me . . .
SolarWinds solutions are rooted in our deep connection to our user base in the THWACK® online community. More than 150,000 members are here to solve problems, share technology and best practices, and directly contribute to our product development process.