I'm trying to pull a report that lists the various profiles currently in use via PowerRools and UCS Central. I've taken a look at the Get-UcsCentralServiceProfile cmdlet and at the Get-UcsCentralComputeInstance, but I'm not sure what individual property for either will indicate if the profile is global or local.
Any ideas?
EDIT:
I think I may have a solution for finding some of the data that I require:
Get-UcsCentralComputeInstance | ?{$_.PolicyOwner -match "local"} # Local Service Profile Get-UcsCentralServiceProfile | ?{$_.type -match 'instance'} # Global Service Profile Get-UcsCentralServiceProfile | ?{$_.type -match 'template'} # Global Service Profile Templates
But I'm still working on determining the Local Service Profile Templates.
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Get-UcsCentralServiceProfile -name <"sp-name"> | fl *
I don't have a UCS Central environment set up right now, but the above command will return all available fields for the service profile whose name is sp-name. I use variations on this on lots of cmdlets to see what is available to me. On a UCS environment, some of the fields that I would most likely be using to satisfy a request similar to yours would include Name, Type, AssignState, and PnDn. You just need to determine the name of the field that specifies the local/global nature of the service profile.
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Thanks for the quick reply Timothy. I'm relatively new with the PowerTools plugin, but have a pretty deep knowledge of PowerShell in general - do you happen to know of any resources/documentation for the various PowerTools cmdlets that may be publicly available?
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Best source of information is from our communities site where you download from - https://communities.cisco.com/docs/DOC-37154
And, just like for UCS PowerTool, one of the most helpful commands is ConvertTo-UcsCentralCmdlet. Perform something in the GUI and get the PowerShell output in the associated PowerShell window.
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Comments
0 comments
Please sign in to leave a comment.