relationship between clusters and host groups
Yeah, that makes perfect sense, gear can definitely throw things off once WWPNs and hostnames start drifting. What you’re seeing happens a lot when teams rebuild vCenters and clusters instead of upgrading in place. The Pure plugin really depends on consistent naming and WWN alignment, so once that’s gone, it’s smart to be careful about using it for host group changes.
If you can, get the VMware team to standardize names again and use same cluster and host naming across vCenter and the array. It’ll make the plugin usable and predictable. In the meantime, I’d pull a current WWPN list from both sides and clean it up manually. Once you’ve got that alignment back, it’ll save a ton of confusion later.
Purity 6.5 doesn’t like cluster names with spaces. Stick to clean alphanumeric names if you can. Until things are standardized, I’d handle host group edits directly from the array CLI or REST rather than through the plugin.
Try to push for naming consistency. Once that’s fixed, everything else (plugin ops, automation, reporting) falls back into place. Also push for change management and CMDB changes - that will make your life easier....
Last advise, if people do not know how to use plugins, do not allow access...
