Dsicovery : IP Switch and IP routers relation fail

hreddy
Tera Expert

‎10-16-2023 06:53 AM

Hi,

  • I have run quick discovery and the devices are discovered but it failed to create relation ship(IP Switch -- IP routers relation ship). 
  • I checked discovery Pattern log , all steps are executed with no errors.
  • I have checked both patters (Network Router, Network Switch) and there is no step involved to make relationship between IP switch and Router.
  • I have checked suggested relation ships but there is no relation exists between IP switch and IP router.
  • Could anyone tell me is it possible to make relationship between IP switch and IP router ?

 

0 Helpfuls
  • 1,039 Views
5 REPLIES 5

VivekSattanatha
Mega Sage
Mega Sage

‎10-16-2023 07:36 AM

@hreddy I am not sure whether you had a look already this doc.

https://docs.servicenow.com/bundle/vancouver-it-operations-management/page/product/discovery/concept...

 

The relationship getting created based on a business rule not by discovery pattern. The business rule logic explained on that article above

Also if you face any issue in that this kb article also would help

https://support.servicenow.com/kb?id=kb_article_view&sysparm_article=KB0683837

 

hreddy
Tera Expert

‎10-16-2023 07:56 AM

Hi @VivekSattanatha 

Thankyou for your response, much appreciated 😀
I will go through the article . BR "Service Discovery - Device Complete" is active, what else should i check to find why the relation ships are not establishing between IP Switch and Routers. any logs etc ... ?

0 Helpfuls

VivekSattanatha
Mega Sage
Mega Sage
In response to hreddy

‎10-16-2023 09:21 AM

That KB article which I pasted above shows how to debug

0 Helpfuls

hreddy
Tera Expert
In response to VivekSattanatha

‎10-16-2023 12:18 PM - edited ‎10-16-2023 01:01 PM

Hi @VivekSattanatha 

The KB article does not explain IP switch -- > Ip router  relationship debug 😞.

Debugging procedure

  • Set the ’sa.discolog.sys_log’ system property to true.
  • Run the following script in scripts-background: ​
    • var npm = new SNC.NetworkPathManager();
    • npm.createPhysicalConnections(ciId);
  • In case of layer 2 connection between a server and switch, the ciId should be the sys id of the server.​
  • In case of layer 2 connection between 2 switches, the ciId should be the sys id of one of the switches.
  • Look at the debug messages to understand why the connection was not created.
  • Note: The actual relation in the CMDB is created between the ports of the devices or between port of one device directly to another device (in case the target port was not found).
  • The algorithm is not creating a direct relation between the server and the network device or between 2 network devices.

 

Also servicenow doc does not provide relation ship between IP Switch ---> IP Router.

 

How Layer 2 Discovery works

When device discovery is complete, the system runs the Service Discovery - Device Complete business rule on the Device [discovery_device_history] table. This business rule uses several strategies, together with information from various tables to create Connects to:Connected by relationships in the CMDB. Relationships can be created between:
  • A server and a switch
  • Two switches
  • A device and the port of another device
  • The ports of two devices
0 Helpfuls