Autodiscovery looping on a device

Products

• Network Observability

Issue/Introduction

Autodiscovery looping on a device

Staging switches are attached to core switch which are  neither discovered, nor modeled., they have a dummy address of XXX.XXX.1.1.

Discovery looks for all devices in spectrum with this address and tries to connect them to the device where we ran discover connections.

XXX.XXX.1.1 and XXX.XXX.0.0/16 have been added as excluded ip's in the autodiscovery control, modeling and protocol options in the VNM. still trying to match these in the discovery

AutoDiscovery is looping with below entries

Nov 20 09:27:19   Switch1/0x0  found 637 matched neighbor devices at IP XXX.XXX.1.1:

Line 4006638: Nov 20 08:43:01   Switch2 no neighbour device is resolved with  remote IP XXX.XXX.1.1, going for device model search

Line 4006639: Nov 20 08:43:01    no neighbour device is resolved with  remote IP XXX.XXX.1.1 and remote device ID Switch, going for device model search

Line 4011471: Nov 20 08:57:11   Switch1 no neighbour device is resolved with  remote IP XXX.XXX.1.1, going for device model search

Line 4011472: Nov 20 08:57:11    no neighbour device is resolved with  remote IP XXX.XXX.1.1 and remote device ID Switch, going for device model search

Line 4013380: Nov 20 09:10:04   Switch1 no neighbour device is resolved with  remote IP XXX.XXX.1.1, going for device model search

Line 4013381: Nov 20 09:10:04    no neighbour device is resolved with  remote IP XXX.XXX.1.1 and remote device ID Switch, going for device model search

Line 4015630: Nov 20 09:27:19   Switch1 no neighbour device is resolved with  remote IP XXX.XXX.1.1, going for device model search

Line 4015631: Nov 20 09:27:19    no neighbour device is resolved with  remote IP XXX.XXX.1.1 and remote device ID Switch, going for device model search

Environment

24.3.x

Cause

Spectrum creates a Cisco Discovery Protocol (CDP) connection based on the IP model search method if the devID and IPAddr entries do not exist in the CDP table. Due to this IP model search, wrong CDP connections are observed if multiple models exist for the IP

Resolution

Add  "match_ipaddr_devid=true" entry to the $SPECROOT/SS/.vnmrc file

With this setting, you can change the default behavior

This setting creates a CDP connection with the remote device only for the matched devID and IPAddr entries that exist in the CDP table