Why, when I run a capacity management report, do some of my nodes show 'Not Calculated' across the 'Warning', 'Critical' and 'At Capacity' columns?

As the title says really, when running a capacity management report, about a third of the nodes show 'Not Calculated' in the relevant columns. Why is this? All the remaining nodes on the report have those columns populated with some useful info.

Any ideas anyone?

Thanks in advance for any help you can provide.

Simon

Find more posts tagged with

Accepted answers

All comments

adam.beedell

Thought one) - Are they added in the last 7 days?
Thought two) - Are they grey?

-SGregory-

No to thought 1....I assume by 'grey' you mean, are they in an 'Unknown' status? If so, thats a no too - most of the nodes have been on the system for a number of years.

adam.beedell

Do they perhaps not have volumes attached to them? Ping-only or simmilar?

Yeah unknown but either on the node or on the volumes or child items under it, perhaps obsolete interfaces or volumes

I'd focus in on what's different about those nodes in particular. I'd expect it'd be either "we couldnt run the math because X" or "we've not finished the math yet"

If neither though, not sure!

-SGregory-

No - all have volumes attached and all are Windows based servers. I'll keep looking, but its super frustrating as I really need this data for some reporting I have to produce for our senior management team. Might have to log a support ticket I guess...

cheryl1

Reading this thread, it may not be something easily identified. You may want to consider opening a ticket with support. They can then get details on your environment and the nodes involved to find a solution

-SGregory-

Thanks Cheryl. I actually did open a ticket with support. However, they say they cannot diagnose issues with custom scripts, so it looks like i'm back to square one at this point, with a script that produces output with missing data (for reasons still unknown).

adam.beedell

Nah push back to SW support on that one, if the value isn't populated in the DB and it should be that's a Them problem
(just make sure it's definitely not populated in the DB)