Cohesity Discovery Issues

[David Casper]

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. 

[Rahul Priyadars]

Is Something is also Changed at Cohesity level?

Since API is returning NULL Values ---> Is REST Resource is Not Available or some permission Issue.

As rightly said TRY same REST endpoint using POSTMAN and see what is the return?

Regards

RP

[David Casper]

Morning Rahul. We did do a Cohesity software upgrade, but I'm not 100% that is when the issue started. It's definitely a possibility. 

I've not had success connecting with Postman yet. Continuing to work on it. The simple calls I've tried so far have failed with cookie and/or token errors.

[shakarat]

Hi David, 

Currently myself doing this deployment, Same error and i have requested my internal Storage team to check with Cohesity vendor, since API call is returning null for proto. 

Will keep you updated, 

Thanks, 
Shakar AT 

[Rahul Priyadars]

thanks keep us posted here