You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Feb 2, 2023. It is now read-only.
According to https://support.purestorage.com/Pure1/Pure1_Unplugged/001%3A_Pure1_Unplugged_Installation
I wonder why my flash array with purity version 5.1.1 with have api version {"version": ["1.0", "1.1", "1.2", "1.3", "1.4", "1.5", "1.6", "1.7", "1.8", "1.9", "1.10", "1.11", "1.12", "1.13", "1.14"]} does not support with Purity//FA 4.8.0 with REST API 1.7 and above.
I'm thinking about upgrading to purity version 5.3.x to get the rest API version 2.x, Is this going to fix the issue?
The text was updated successfully, but these errors were encountered:
@suphamit01 that upgrade probably won't fix the issue, there's no reason that model/version of array shouldn't work with Unplugged right now.
My guess as to the issue is that you probably left the pod CIDR as 192.168.0.0/16, which is the same IP range that your array is in, resulting in an IP routing conflict. Go ahead and change the pod CIDR to some IP range unused by all arrays you will be adding to Unplugged, and do puctl infra reset && puctl infra init && puctl pure1-unplugged install to reconfigure the networking, and give that a try.
I cannot add a new array into Pure1unplugged. It shows an error as below.
"Unable to connect. Error: Get https://192.168.122.14/api/api_version: dial tcp 192.168.122.14:443: getsockopt: connection timed out"
According to https://support.purestorage.com/Pure1/Pure1_Unplugged/001%3A_Pure1_Unplugged_Installation
I wonder why my flash array with purity version 5.1.1 with have api version {"version": ["1.0", "1.1", "1.2", "1.3", "1.4", "1.5", "1.6", "1.7", "1.8", "1.9", "1.10", "1.11", "1.12", "1.13", "1.14"]} does not support with Purity//FA 4.8.0 with REST API 1.7 and above.
I'm thinking about upgrading to purity version 5.3.x to get the rest API version 2.x, Is this going to fix the issue?
The text was updated successfully, but these errors were encountered: