Cohesity Discovery Issues
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
02-23-2023 01:16 PM
I've been working on discovery our Cohesity clusters for a while now and recently noticed an issue. I'm currently using Tokyo.
A while back the discovery was working as intended, in spite of the odd configuration requirements. I was discovering the cluster, node and chassis. Then I noticed the nodes and chassis CIs were no longer being created.
I'm using the Cohesity Storage System pattern with serverless discovery jobs scheduled for each cluster. Each job has two Execution Patterns. Each one has a different IP since there is apparently no way to input the VIPs hostname. As previously mentioned, this had been working.
Working with SNOW support we found in the pattern one of the API calls was returning 'null' for proto.
My thought was to run some test API calls via postman, but so far I've not had success. Looking to see if anyone else has ran into this issue.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
07-13-2023 11:09 AM
Here's the full solution which I put in another thread a few hours ago. Wanted to make sure it was available here as well.
SNOW's docs on this are worthless. I even told them while I was working a case I opened with them for this issue.
To start, make sure you are on Cohesity patch 30 for 6.6.0d users or later. There was an issue introduced sometime before that which changed the API path for Cohesity that prevented SNOW from seeing the chassis and node details.
Then you do have to create a serverless discovery, as their doc states (but was only updated after I mentioned it) except they don't list all the specific details.
1) Create a credential alias, type 'credential'
2) Cred is basic auth
3) In the serverless discovery schedule you have to create at least one 'Serverless Execution Pattern'
- Select 'Cohesity Storage System' for the Pattern
4) Create two Discovery Pattern Launcher Parameters
*** I created two of these since they won't work with Cohesity's VIP. I just chose 2 of the IPs contained within the VIP***
- credentialAlias - Value = the alias you previously created
- cluster_ip - Value = one of the IPs within the Cohesity VIP
Hopefully this helps. Lmk if you have any questions.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
07-13-2023 10:38 PM - edited 07-30-2023 07:20 AM
Hi All & @David Casper
Here's the snow doc mentioning all the prerequisites as well...
Let me know if anything is still missed we can fix that.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
07-24-2023 07:42 AM
Was there supposed to be a link?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
07-30-2023 07:21 AM
My bad, yes missed it, updated my comments with the link in the original post.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
11-17-2023 11:29 AM - edited 11-17-2023 11:31 AM
Hi David, What kind of permission is required on the Cohesity Cluster to run this pattern, I have a account with Viewer rights (its a local account) which is throwing error when running the patter. but when i am trying with API explorer to get cluster details it does provide output. Any suggestions here?
