Hello Martin,

Thanks for asking.  You have given me a good reason to take a closer look at PowerShell 3.  Because we use CAS authentication, you'll first need to authenticate with ProSphere using the invoke-webrequest cmdlet.  Once you do that, you can use the web session with the invoke-restmethod cmdlet to retrieve the data of interest to you.

Here's a quick function I put together that will authenticate with ProSphere and return the session variable.

function Get-ProSphereSession {

    param(  

    ## ProSphere virtual machine FQDN

    [string] $psfqdn = "",

    ## ProSphere username

    [string] $username = "appadmin",

    ## ProSphere username

    [string] $password = "Changeme1!"

    )

    #Get a web session variable for the ProSphere instance

    [string] $loginuri = "https://" + $psfqdn + "/cas-server/login"

    $request = Invoke-WebRequest -Uri $loginuri -SessionVariable ps

    #Login to the CAS server

    $form = $request.Forms[0]

    $form.Fields["username"] = $username

    $form.Fields["password"] = $password

    $request = Invoke-WebRequest -Uri $loginuri -WebSession $ps -Method POST -Body $form.Fields

    #Return the authenticated web session variable

    $ps

}

What I did next was dot source the function so I could use it from the PowerShell prompt.  Here's how to get an authenticated session (no need to provide the username and password if you are still using the default).

$session = Get-ProSphereSession pstest.lss.emc.com -username appadmin -password Changeme1!

Next, you can run the invoke-restmethod cmdlet using $session.

$request = Invoke-RestMethod -uri https://pstest.lss.emc.com/srm/topology/msa/types/Host/instances -WebSession $session

Sending $request to get-member you can see it is an XmlElement:

$request | get-member

   TypeName: System.Xml.XmlElement#http://www.w3.org/2005/Atom#entry

Which you can then do with as you please:

$request.content.Host | Where-Object {$_.Displayname -match "2950prem"} | format-list DisplayName,ipaddress,fqdn,createdby

DisplayName : 2950prem2-ecc

IPAddress   : 10.192.165.133

FQDN        : 2950prem2-ecc.workgroup

CreatedBy   : Discovery

DisplayName : 2950prem4-ecc

IPAddress   : 10.192.164.27

FQDN        : 2950prem4-ecc.emc.pri

CreatedBy   : Discovery

DisplayName : 2950prem5-ecc

IPAddress   : 10.192.164.28

FQDN        : 2950prem5-ecc.emc.pri

CreatedBy   : Discovery

I hope this is enough to get you started!

Ryan H.