How to discover Pure FlashArray storage devices
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎02-16-2024 06:34 AM - edited ‎02-26-2024 11:27 PM
Hello All,
I am new to Storage discovery. We are trying to discover Pure Flash Array storage devices. Storage team has provided a Management IP and test account with read-only access. I have configured credentials as Basic Auth Credential. We are getting authentication failed error in discovery logs.
Please help me to understand which type of credentials are required?
Which ports should be open for Pure FlashArray discovery?
@Rahul Priyadars @Maik Skoddow
#discovery #itom
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎12-05-2024 02:50 AM
Flash Array Storage Discovery needs devices to be configured via SMI-S and CIM type credentials.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎12-05-2024 03:34 AM
Hi @ajaykumar_r ,
According to ServiceNow doc Pure Storage Flash Array discovery asks to use Basic Auth and we have a OOB pattern in place... Kindly let me know whether you used SMI in your environment and did you used any custom patterns.
Thanks
Denisa
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎12-05-2024 11:04 AM
We only have Basic Auth credential in place (per the SN doc), but the issue are having right now is that the HTTP classifier does not return any info. We see it issues that URL ending with /api/api_version, but it does not get any results. When we try the URL in a browser from the MID server, we get a "invalid certificate" message. We have a case open with SN.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎01-13-2025 10:04 PM
Yes , we have the same issues
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎01-14-2025 06:29 AM
We opened a case with SN Support and they provided update set with fix to HTTP classifier. Case notes:
The issue is related to a defect . We have a PRB opened for the issue . I have attached the PRB to the case. As a workaround, can you please apply the attached update set attached.