Notifications

94 views

Description

"Network Router" Pattern creates invalid discovery_device_neighbors records towards 192.168.0.1 default gateway which results in creating incorrect L2 Mapping -"Connects To::Connected By" relationships between one router interface towards another router- between non-neighbour devices.


Steps to Reproduce

1. Run Horizontal Discovery against two Cisco routers which are not neighbours but have a device neighbour record to 192.168.0.1 in their CDP.
2. "Network Router" or "Network Switch" Pattern will create discovery_device_neighbors between the routers interfaces and 192.168.0.1 default gateway.
3. L2 Mapping logic may create "Connects To::Connected By" relationship between the one router interface towards another router which will be shown in Dependency View Map as "Depends On::Used By" virtual links between the 2 routers when "Physical Connection" Dependency type is selected.

Workaround

As a workaround, you could import the attached update set XML which includes modified steps in both "SNMP - CDP and LLDP" and "SNMP - Routing" shared pattern libraries.

Please after importing and committing the update set, navigate to the modified shared pattern libraries , "Network Switch" and "Network Router" pattern and click "Synchronize with MID Servers" UI action to assure the up and running MID servers received the recent modifications applied on the shared libraries. 


This issue is under review. To receive notifications when more information is available, subscribe to this Known Error article by clicking the Subscribe button at the top right of the article. If you are able to upgrade, review the Fixed In or Intended Fix Version fields to determine whether any versions have a planned or permanent fix.


Note: 

After upgrading to a ServiceNow release or patch that include a fix for PRB1406348, please revert the modified shared pattern libraries to the latest out of box version. 



Related Problem: PRB1406348

Seen In

There is no data to report.

Intended Fix Version

Quebec

Safe Harbor Statement

This "Intended Fix Version" information is meant to outline ServiceNow's general product direction and should not be relied upon in making a purchasing decision. The information provided here is for information purposes only and may not be incorporated into any contract. It is not a commitment, promise, or legal obligation to deliver any material, code, or functionality. The development, release, and timing of any features or functionality described for our products remains at ServiceNow's sole discretion.

Associated Community Threads

There is no data to report.

Article Information

Last Updated:2020-07-09 02:53:54
Published:2020-07-09
PRB1406348 Workaround.xml[View]