Can NetAppDocs be enhanced to include FabricPool ObjectStore data at the volume level?

[mpedigo_usda]

I can see that the ObjectStore is accounted for in NetAppDocs under AggregateDataStores, but I don't see volume foot-print data being captured on the volume side or at least fully.  This is important if you are trying to track where your FabricPool data is coming from and would be invaluable if you could add to NetAppDocs.

The command you would use at the CLI to get the data is:

volume show-footprint -aggregate <aggr>

The output is as follows:

Vserver : vs1
Volume : vol1

Feature                                  Used      Used%
-------------------------------- ---------- -----
Volume Data Footprint 2.24TB 2%  <----Need this for sure
Footprint in Performance Tier 486.4GB 21%   <----Need this for sure
Footprint in ObjectStore1 1.76TB 79%  <-----Need this for sure
Volume Guarantee 0B 0%
Flexible Volume Metadata 14.99GB 0%
Deduplication 15.54GB 0%
Cross Volume Deduplication 6.66GB 0%
Delayed Frees 1.78GB 0%

Total Footprint 2.27TB 2%

This would be a tremendous help to manage our environment and would help any NetApp SMC or other PS assisting a customer that is using FabricPool.

Please let me know if you have any questions or feedback on feasibility.

Thanks in advance!

[ttran]

Hello,

You can also run command "volume show-footprint" against a volume instead of an aggregate to get more specific detail, but the output against a volume is already what you provided. 

See my example below:

::> volume show-footprint -volume fabricpool_test

Vserver : vserver_test
Volume : fabricpool_test

Feature                          Used       Used%
-------------------------------- ---------- -----
Volume Data Footprint            5.03TB     36%
Footprint in Performance Tier    4.93TB     98%
Footprint in bucket_test         97.66GB    2%
Volume Guarantee                 0B         0%
Flexible Volume Metadata         29.08GB    0%
Delayed Frees                    12.39MB    0%

Total Footprint                  5.06TB     36%

Here are some other commands that might be helpful:

::> storage aggregate object-store show-space
::> aggr show -fields composite
::> df -A -composite
::> storage aggregate show-space -aggregate-name <aggrname>
::> volume show -fields tiering-policy
::> set diag; run local waflcomposite stats show <aggr name | vol name>

You can also add the "-instance" flag at the end of most "show" commands to get more information.

[mpedigo_usda]

TTRAN,

Thanks for responding.  I'm aware of how to pull it out of the CLI as you should have been able to see from my original post.  I use NetAppDocs for internal reporting, and this data is not presently in NetAppDocs that I can find.  I'm suggesting it would be helpful to the community to add this functionality, especially if they strip off and present in numbers based on GB.  That give me an easy way to keep trending data for reporting, planning, and troubleshooting purposes.

I'd really like to see that in OCUM someday, but right now there are limited ways to capture data related to FabricPool and from a management perspective that makes it difficult to identify where data is coming form easily when somebody starts filling it up quickly and you need to ask them to put on the brakes.  Hope that makes sense.

NetApp is coming up with some great stuff, but monitoring and reporting around those features is sorely lacking.  I hope NetApp will step it up one of these days.

[cole]

Yep, I can definitely add that. I have been somewhat ignoring that data since I thought it was covered by another property (like in the VolumeSpaceDetails table). But, I don't have a system set up with a Fabric Pool so I haven't seen real data. 

Would you want that in a separate table? Or, ideally, in an existing table? What would make the most sense when reviewing the data?

Jason

[mpedigo_usda]

Jason,

Thanks for responding!

In FlexVolConfiguration if you could add tiering-policy and tiering-minimum-cooling-days that would be great.

volume show -volume <vol> -fields tiering-policy,tiering-minimum-cooling-days

It might make sense to add it to FlexVolSpaceDetails if you already parse the volume-footprint output, but if it is simpler to do a new sheet or to not mess up other things people are doing, another sheet is fine and I can reconcile if necessary to another sheet if I'm adding to a report.     

volume show-footprint is the command.  You may already be reporting from this.  I'll give you an example of how the output looks when it is FabricPool vs not:

Feel free to reach out and I'm happy to do a working session to allow you to get what you need or be a beta tester once you have it figured out.

Thanks again!

Mike