- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
06-02-2023 01:44 AM
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
Solved! Go to Solution.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
07-13-2023 09:09 AM - edited 07-13-2023 09:10 AM
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.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
02-06-2024 08:24 AM
I don't believe I've seen that error. I assume you followed the setup instructions in this post?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
01-16-2025 02:24 AM
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
02-22-2024 11:41 AM
You have to create a serverless execution pattern for each IP you want to discovery. The VIP won't work. For my configuration I chose 2 IPs per cluster.
Hoping SNOW addresses this in the future so that it will automatically discovery the cluster and know it has a VIP as well as statis IPs.
There is a similar issue with Juniper routers which have two routing engines. I have an open case with them atm.
