We have one specific link that USED to be connected to two switches, SWaa and SWab, port 1:2 on both sides. The link was detected in NetSight via LLDP and EDP and showed up just fine on the OneView map. Then a new link was established between the switches (LACP port group using ports 1:3 and 1:4 on both sides, 1:3 to 1:3, 1:4 to 1:4) and the port 1:2 link was disconnected. Port 1:2 on each switch was then "re-used" and connected to a FortiGate firewall that has LLDP disabled (due to limitations in the Forti LLDP implementation). The problem is that the link still shows as connected between SWaa and SWab.
There is no LLDP or EDP neighbor on port 1:2 on any of the switches any more (since the links were re-routed to the FortiGate).
The top switches are the ones with the incorrect link. If the FortiGate has been visible, it would have been on top of those and connected to swirches aa and ab to their ports 1:2.
Is NetSight confused since the link was discovered using LLDP and EDP and now, the links are still up, it's just that there are no more LLDP/EDP packets seen over the link? Can I have NS rediscover the link without removing the switches from the map? In my opinion this should be automatic, and I should have a choice to remove the link that has changed.
There is no LLDP or EDP neighbor on port 1:2 on any of the switches any more (since the links were re-routed to the FortiGate).
The top switches are the ones with the incorrect link. If the FortiGate has been visible, it would have been on top of those and connected to swirches aa and ab to their ports 1:2.
Is NetSight confused since the link was discovered using LLDP and EDP and now, the links are still up, it's just that there are no more LLDP/EDP packets seen over the link? Can I have NS rediscover the link without removing the switches from the map? In my opinion this should be automatic, and I should have a choice to remove the link that has changed.
You should be able to right click each switch and do a rediscover on the map.
If that doesn't work and running 6.3/7.0 EA you can remove the switches from the cache and then do a rediscover. This will cause the cache to pull all the info from the switches again [which shouldn't have that link again]
If that doesn't work and running 6.3/7.0 EA you can remove the switches from the cache and then do a rediscover. This will cause the cache to pull all the info from the switches again [which shouldn't have that link again]
