- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎02-08-2016 12:13 AM
Hello All,
We are doing having issue for port level discovery, where SNOW should discover all the devices which are open in particular port which should be given some where.
Is there any way to achieve to this?
********Urgent**********
Regards,
AJ
Solved! Go to Solution.
- Labels:
-
Service Mapping
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎02-17-2016 08:40 AM
Robert,
Even simpler he can just use a behavior that defines exactly what ports should be checked during a discovery!
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎02-17-2016 12:07 PM
Doug,
This makes sense the part I am struggling with on this question is how to properly implement the scenario where a client only wants devices discovered that have XYZ ports open. The purpose of using Behaviors and limiting port probes is to tell it which port to trigger discovery on (e.g. if port 22 is open then run SSH) but it seems like the purpose of what AJ is trying to do is "If it has any of these ports open then try to discover using technologies that are known". It's a bit of a different workflow then ServiceNow Discovery uses no?
AJ just to confirm you mentioned port 135, 80, 443, and 22 but really only 2 of those could actually be used to fully discover the server (as they are standard ports for WMI and SSH). Let's take the case where your client says I want to discover any servers running those ports plus 8183 as an example. If it detects port 8183 you will still need either WMI, SSH, or SNMP open on the device to properly discover it and that port will have to be assigned within ServiceNow to the appropriate Port Probe (this scenario is for a typical full end to end discovery not an IP only discovery). I hope I haven't confused you too much AJ .
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎02-17-2016 12:17 PM
I dont think so, in fact the way Im reading this is that its exactly what we are doing, when said ports (22, 135, 161) are open then discover away.. if you are talking about multiple ports being open then trigger a discovery, then no..
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎02-17-2016 12:21 PM
Ah okay. AJ if this is what you were going for then I think you are good to go pretty much out of the box and you can just tailor discovery behavior using behaviors or by adding additional IP services/Port Probes. Hope we were able to help.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎02-17-2016 09:44 PM
Hello robertgeen / doug.schulze,
Great!
Thanks Guys for help, even i found same 'behavior' part can do this for me, i am in full swing with testing and so far looks good.
My only concern about vCenter/VM's, Not sure if i can able to do that via this process?
-AJ
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎02-18-2016 10:34 AM
You can create your own functionalities based on any combination of port probes you choose! So yes, you can create a vCenter appliance discovery but if its windows based, you would want to create a specific schedule that just targets the vCenter host IPs..