Insert manual CI in service mapping through pattern

rimvydas_v · ‎02-19-2018

I am trying to crease service map, however after load balancer we have TMG servers to which discovery does not have access (and probably will not have in nearest future). During mapping procedure connections from load balancer to TMGs are created, but these devices cannot be identified. Error message:

Failed to detect the operating system on host: x.x.x.x. Unable to discover host by IP address x.x.x.x.

Quick discovery Shazzam returns closed ports.

What would be the best course of action add these devices into the map and continue with the rest of service mapping?

robertgeen · ‎02-20-2018

Unfortunately unless you are on Kingston release this isn't possible. You can create manual connections but you still have to have the ability to discover them (unless you are on Kingston release). In Kingston they added the ability to add manual CIs to service maps which is exactly what you need so unless you plan on going to Kingston this probably won't be possible.

I feel your pain as I've hit moments many times over where it would be of been so nice to just add a manual CI to the service map.

View solution in original post

Paul Ciarfella · ‎03-02-2018

Agreed. Its got to be dynamic.

I'm going to cry foul at the next ServiceNow service mapping demo showing how easy it is to use!

robertgeen · ‎03-02-2018

One thing you can do is just try to add the ARP cache SNMP probe to your SNMP discoveries for those devices. If they return ARP cache data you can actually get a connection from the infrastructure to it (I did this with firewalls before) however because it doesn't show up in the tracert it does between the 2 endpoints I can't guarantee it will show up. Worth a try though :).

johnnyjava · ‎11-15-2018

Wait, so how do you even do this in Kingston / London? I'm having an error saying "one or more host properties should not be empty"

robertgeen · ‎11-16-2018

So there are a few ways to do this. The first is that you have to have an entry point that works in Kingston (London is different as you can actually add manual CIs and just build the map one by one) and you can right click the discovered CI and add a manual connection or manual CI. The second way is if you have a failing entry point you can Skip and Resume and at that time you can give it a CI to replace it with.

In London you actually tell it a CI and then you can build it out from there or you can keep adding CIs at the top level. Those are basically the options.

johnnyjava · ‎11-17-2018

I've been trying to use the Manual Endpoint type within a pattern, leveraging a pre_task_script to have the sys_id handy, but the system isn't happy about it. I have the developers reviewing it with a HI ticket.

I try to avoid doing manual connections manually as those aren't portable from instance to instance and in some cases we are not mapping in Production.