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. 

[shakarat]

Note: "Model number" is not populate in discovery job, as per product documentation this atrribute should be discovered and ServiceNow vendor confirmed its bug and documentation will be corrected soon from their end.

Thanks, 

Shakar AT 

[Rahul Priyadars]

Posting this on behalf of SHAKAR..

• Soltuion for Cohesity Discovery ... as follow

• • 👏
  • 👍
  • 👎
  • 😊
  • 😞

  ***************** The issues with Cohesity side, Our storage team using 6.X version as per Cohesity Vendor before version 7.x , the configuration file in the system is flaged = True [ it means,they have blocked this configuration file due to security reason, due to this our discovery pattern unable to read this file]. In Version 7.X they are allowed to read/discover. Our Storage team applied the fix in V6.x and now we are able to populate node and Chasis class table. Note: "Model number" will not populate in the discovery job. As per the Prodcution documentation this attribute needs to be discovery but ServiceNow vendor informed there is bug in documentation and it will be corrected soon from their end.

  Regards

  RP

[David Casper]

Just an update for anyone following this thread. The issue was related to the firmware on our Cohesity devices. We had to upgrade to 'patch 30 for 6.6.0d' as we were on patch 28. 

Hopefully this helps someone else!

[SiD2]

Hi @David Casper 

Yes, this seems to be some issue with Cohesity provider itself, as I also observed this from one customer we are working with.

I verified that specific API was working during pattern development and later suddenly it stopped responding to that API and comes null.

Request you to check from Cohesity side and see if same API from postman also has same behavior post cohesity upgrade.

[David Casper]

Thanks for the response @SiD2 . That other customer isn't me is it? 🙂 If not...how are their API tests going?