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
03-01-2023 04:47 AM
🙂 So which company are you from so I can confirm if it was the same with whom I experienced.
We communicated the same that issue could be with cohesity end and the customer didn't get back and the conv was closed now, so not sure if their API started working or not.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
03-01-2023 07:26 AM
QTS. My case is still open though.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
03-01-2023 07:30 AM
Then it's a NO, it was a different customer when I worked with.
Probably there might be someone else working on your case and I moved to a diff team so I'm unaware.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
04-24-2023 06:40 PM
Hello. I know this is a little outdated but was wondering if you got this resolved? I'm experiencing the same issue and it appears that the pattern step 16 - parsing chassis information is coming back with no results. The steps before that gather the information work but this parsing step fails. There's another similar step # 25 - parsing node information works properly. I've been trying to compare the commands but not helping. Also, I'm working with the Storage SME and we're working on the Roles within Cohesity to make sure we have all the privileges we need. I'm thinking of opening a case but wanted to check with you first. Thank you.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
05-04-2023 05:22 AM - edited 05-04-2023 05:25 AM
Thanks for reaching out. Unfortunately I'm still struggling with this and SNOW support just pushed me to Cohesity. The really weird thing is this worked a while back, but due to bouncing back and forth I'm not sure when it stopped working.
The one thing SNOW support pointed out that in this call '/irisservices/api/v1/nexus/cluster/status' the following is being returned
"clusterConfig": {
"proto": null,
"version": -1
}
They say the needed data should be contained within the proto object, but unfortunately I don't have an example of what that should look like.
I'm trying to work with Cohesity, but that is through another team at my company and they have their priorities as well.
The one thing I did find out from Cohesity is that they are moving away from v1/nexus to v1/public for their API calls. Not sure if that is the cause of this or not. I did some testing with public and was not able to find the proto object. @SiD2 any updates on your end?
