Skip to content

This issue was moved to a discussion.

You can continue the conversation there. Go to discussion →

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

How to know what pool/srp device is bound to? #166

Closed
212850a opened this issue Apr 24, 2023 · 1 comment
Closed

How to know what pool/srp device is bound to? #166

212850a opened this issue Apr 24, 2023 · 1 comment

Comments

@212850a
Copy link

212850a commented Apr 24, 2023

Hello,
After spending some time I could not find the way to identify what pool/srp each device is bound to, get_volume() function does not provide these details.
May be I miss something or there is no way to do it via RestAPI?

From solutions enabler it's available from "symdev show" command output like:

symdev -sid 1111 show DEVICE
...
Bound Pool Name:   SRP_NAME
...
@rawstorage
Copy link
Collaborator

Hi, there is usually only a single SRP on the majority of PowerMax arrays, usually called SRP_1, this is reported at the storage group level. If you do a get_storage_group_details on the storage group you will find the bound SRP
{
"storageGroupId": "ansible_metro",
"slo": "Diamond",
"service_level": "Diamond",
"base_slo_name": "Diamond",
"srp": "SRP_1",
"slo_compliance": "STABLE",
"num_of_vols": 2,
"num_of_child_sgs": 0,
"num_of_parent_sgs": 0,
"num_of_masking_views": 0,
"num_of_snapshots": 0,
"cap_gb": 4,
"device_emulation": "FBA",
"type": "Standalone",
"unprotected": true,
"compression": true,
"compression_ratio_to_one": 0,
"vp_saved_percent": 100,
"unreducible_data_gb": 0
}

@dell dell locked and limited conversation to collaborators Apr 24, 2023
@rawstorage rawstorage converted this issue into discussion #167 Apr 24, 2023

This issue was moved to a discussion.

You can continue the conversation there. Go to discussion →

Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants