Cohesity discovery prerequisites

[Community Alums]

Hi Team,

I checked the servicenow documentation and found they have added cohesity operating system pattern in discovery pattern and service mapping plugin . i have upgraded the plugin and i can see in servicenow pattern cohesity pattern got added.

i checked the prerequisite and i am no clear how we can discover cohesity device in ServiceNow. if someone can please help me to provide the prerequisites and steps to perform for cohesity device end and ServiceNow side to discover.

Regards,

RK

[Ashok Sasidhara]

Have you checked the following URL for prerequisites?

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

[Community Alums]

Hi Ashok,

Yes i checked already but this is not helpful.  if possible can you suggest how can we implement this?

@CMDB @itam @Servicenow 

[David Casper · Accepted solution]

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.

[MBannis]

Wanted to add to David's response.. All that he said is absolutely correct.

To add, 

1. If your Cohesity system is already past version 6.6 (in our case we were already I think at 6.8), the patch referenced above would not work, you would have to open a ticket with Cohesity Support (although they did say they would release an update in their next patch cycle) for them to provide you a fix specific to the version of Cohesity you are running.

2. I too had to engage ServiceNow Support as even after applying the patches provided by Cohesity wasn't seeing my nodes / cluster resources populated. Now this one is a funny one, OOB the form view for the cluster shows some minimal cluster info then shows 2 tabs under related links - Cluster Node and Cluster Resources.

Keep in mind both these tabs DO NOT refer to the actual cohesity node or cohesity cluster tables hence why they show no data in them.

The fix for this is to using form designer to amend that form and add a new section to the form in between the top section (base cluster details) and the related links section, I call the section Related Items and in it add the CI Relations field reference. In doing so, you will see both upstream and downstream relationships for your cluster including it's nodes. 

3. One other thing ServiceNow Support noticed was that thru a verity of discovery attempts including ssh / snmp and finally utilizing this serverless pattern we had multiple copies of those nodes in our cmdb and in their investigation they noted that I had changed my IRE rules (starting from hardware down). They recommended I specifically revert cohesity node's IRE back to OOB. So I had to go to CI Class Manager, find Cohesity node, go into Identification Rules, choose to replace existing derived rule to independent and create an equivalent set of OOB rules for that branch (See screenshot for example).

Hope this helps some lucky chap.. 😃