Start a Conversation

Unsolved

This post is more than 5 years old

489

January 28th, 2008 11:00

StorageScope 5.2 SP5 dropping LUN masking information

We have a situation where STS doesn't always report valid Lun masking info, one day there will be two thousand entries and the next day STS will report 6. Wondering if anyone else has seen this?

2 Intern

 • 

5.7K Posts

January 29th, 2008 03:00

I have seen similar outputs, but tis time with ... what's it called ? ... available storage and accessible storage. These two values aren't always the same. And this is too bad, since StS reports the lower value of the two and customers get the wrong bills and we're getting not as much paid as we should be.....

8 Posts

January 29th, 2008 14:00

The report I'm looking at is 'Array - LUN Masking', filtered on a particular Symmetirx. One day shows 2264 luns and the next 6! We got a ticket opened, see what happens.

2 Intern

 • 

5.7K Posts

January 30th, 2008 00:00

That's very extreme.... A service request is perhaps better indeed. Please let us know what the outcome is.
In my case the inconsistency between what the host actually "sees / uses" and what StS reports is consistent (does this line of text make any sence ?).

41 Posts

January 30th, 2008 09:00

If you are referring to the canned column "Available" in the Drill-Down View of STS, Available is the amount of Capacity that can be reclaimed in an array either because the devices are Masked but not mapped or because the host is accessing the storage device and not using it.. Accessible is the amount of storage device capacity that is accessed by the host either by direct attach or through a switch. These two columns have different purposes.

41 Posts

January 30th, 2008 09:00

Also the "Available" column is only found in ECC6.0. It is not in any of the STS sp5 reports.

6 Posts

March 13th, 2008 10:00

Accessible or Available is only accurate if the host agent is reporting correctly.
Masking info is from the allocation table retrieved during discovery.
The masking table can be parsed incorrectly or have invalid data if the storage agent discovery doesn't complete under the set dcp . Check dcp's and agent logs for abnormalities.
No Events found!

Top