DaveStraley

Yes just Sflow data. Other link information within Orion is reporting properly. For instance NPM is reporting the link currently at 10Mbps while Netflow shows the traffic at 800kbps.

This is for Clustered On Tap running 8.3. Its a table value that gives you the CPU busy times for each node in the cluster. I havent got around to getting one going for our 7-mode nodes.

I would like to second this. In large Netapp deployments you will run out of CPU power before you run out of anything else. Many times high Latency is caused by the controllers being too overloaded on CPU (higher than 90%). For Netapp CPU is critical.

Does this release correct the Netflow issue with vCenter/esx 5.1? Also, can I get the RC enabled in my customer portal? Cheers, Dave

I have gone through that article and it did not correct the issue. Any other ideas?

Is there any way around this or will it be updated to accept decimal points (.35)? Only our most expensive SSD tier is over $1/gb, the rest of our disk is charged below this. Makes it very hard to sell this product to my company when we cant charge the proper price for disk.

Has the option to go below $1/GB been added with the latest update? Cheers, Dave

Amazing to see DataDomain finally make it into SRM! Cant wait to try it out!

This works from the report writer but not from the web interface. We updated to v9.5... maybe that has something to do with it.

I was really hoping DataDomain was going to be on this release since its the #1 most requested array on the SRM site. This was a major point for us purchasing Solarwinds. It will be much harder to justify without it....

We are using these on Liebert UPS that use the Intellislot Web Card. We have not tested this on anything else.

Looks like its out. Virtualization Manager 8.0 release notes - SolarWinds Worldwide, LLC. Help and Support

You could always create a custom SNMP poller. This OID should give you the CPU busy % across the cluster. OID: 1.3.6.1.4.1.789.1.2.1.14.1.4 Cheers, Dave

On the one that is not populating there are 8 Nodes, 21 Aggregates, Aprox 260 Volumes. We have very few direct NFS exports left. Here is the CPU chart for the polling server. The memory is only about 32% utitlized and the DB server is even less. I have also tried removing everything and only adding the large cluster and…

Will do. I just wanted to make sure it wasnt a known issue. Thanks for your time.

It turns out that the install on the polling engine did not finish properly and that was causing the high CPU issue. After running the installer again the CPU has dropped back down to normal levels.

Ticket submitted. Ticket #377979 One thing to add is that the CPU usage is higher on our dedicated polling engine, not our main app/polling server. This polling engine does the vast majority of our SAM polling.