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]

Hi David, 

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. 

Thanks, 

Shakar AT 

[shakarat]

Hi @David Casper 

This issue is with Cohesity side,  We are using version 6.x for Cohesity. From Cohesity side the configurtaion file is blocked (they have flagged this file to TRUE, that means our discovery job will not be able to read/discovery this file). Thats why we are unable to populate those record via discovery.

Solution: your internal cohesity team should get a fix from Cohesity Vendor and apply to the system. we have did the same steps. once applying the fix now we are able to discovery thoses records. 

Note: Still you not be able to discovery "Model Number". As per  product documentation this field should discover but ServiceNow vendor confirmed its Bug in the documentation and it will be corrected soon from their end. 

Hope this info helps you to move forward. 

Thanks, 

Shakar AT 

[David Casper]

@shakarat thanks for the details. Can you specify a couple things?
1) Cohesity fix. Is there a specific name, file name, type name for this fix to help ensure Cohesity knows what I'm referring to?

2) Model Number bug: what documentation are you referring to and is it SNOW that confirmed this is a bug or Cohesity?

[shakarat]

Hi @David Casper 

1) Cohesity fix. Is there a specific name, file name, type name for this fix to help ensure Cohesity knows what I'm referring to?

   ---> Just inform them the error "proto type = null" and they will understanding when i talk to them they mentioned "configuration file" so specific name.

2) Model Number bug: what documentation are you referring to and is it SNOW that confirmed this is a bug or Cohesity?

   ---> for every Discovery module, we do have section "Data collected by Discovery during horizontal discovery" when you configure/implement the discover...  we need to make sure all the fields are getting populated as per the product documentation. When i checked model number was missing. 

URL : https://docs.servicenow.com/en-US/bundle/utah-it-operations-management/page/product/service-mapping/...

Thanks, 

Shakar AT 

[David Casper]

It does. I'll pass this info along and cross my fingers.