Recent Discussions
- 66Views0likes14Comments
good morning, codyhosterman I used the PureStorage.Pure1
good morning, codyhosterman I used the PureStorage.Pure1 module to get load metrics from Pure1, which worked fine yesterday. But when I run the same script with same cert, etc, I get the message JWT expired. How can I make this authentication process work so if I run it once every hour, I can get authenticated properly? ```$mypwd = "xxxx" $CertObj = Get-PfxCertificate -FilePath C:\Stash\PowerShell-Projects\Pure1\mypfx.pfx -Password $mypwd $pure1_appid = "pure1OSWa2R7FOwejvETD" $PureOneConn = New-PureOneRestConnection -certificate $CertObj -pureAppID $pure1_appid``` reply: `Exception: The Pure1 Organization with ID 1001 is already connected.` ```$PureOneArrays = Get-PureOneArray -arrayProduct FlashArray Invoke-RestMethod: {"message":"JWT is expired"}```36Views0likes11CommentsWe have had a major outage
We have had a major outage because of a combination of network outage and the way we designed our environment. Working with Cisco and Pure support to get to the exact details, but main issue is: Our design has ESXi hosts only connected to Pure array in DC1 and we have pods that replicate SYNC to DC2. During network maintenance there was a planned core switch failover that caused a longer outage then expected, which made the mediator unavailable and the latency for the preferred site too high. This all caused the pods to become unavailable on our preferred site and "switch" over the non-preferred site. We're still looking into the details, but I'm also searching for a possible work around during future core maintenance. For that, the question I have is if it is possible to automate (RestAPI / Powershell) the sync of pod's to pause, to prevent failovers during network maintenance and of course enable it again later on.Solved26Views0likes4CommentsI have started the process to migrate between arrays
I have started the process to migrate between arrays - I'm using ActiveCluster (again - it kicks hiney!) and have set the PreferredArray for a batch of volumes (just before I cut them over) I moved over. I have another batch of volumes that I will migrate in the next week. Both arrays are in the same DC, a rack apart. As I read the documentation I think it won't be an issue to leave that set - it only comes into play with ActiveCluster; and then only when the volume is online on both arrays. Am I correct thinking that I should I blank it out?Solved16Views0likes3Comments