s.toofanian

The core layer doing its job at its best, filled with correct mac address, ip addresses, and DC is polling fine. Overall service health is correct, the issue persist. You lucky!

The ARP table filled with the all mac addresses, seems that the core layer is doing its job and we should look into other matters. After hours of troubleshooting I concluded my perceiving from the Cisco IOS side rather UDT issue, To what extend do you agree? Have you experience the same?

Same here! Layer-3 port collection from UDT does not resolve the issue. Any idea?

Nope, still nothing! The issue is not related to core layer monitoring from UDT perspective.

My assumption is that the core layer is being monitored from the NPM module and sends logs and traps to Log analyzer (LA), so in this respect the information already provided. The core layer switch is actively monitors vlan and interfaces. Also, the trap and syslog is active on the switch. I would add the backbone…

Fantastic that you are here! I found it strange to add core layer switch to UDT, as you suggest I would give it a shot and wait for the result. Many thanks.

Again thanks for the prompt respond. My assumption is that something hinder the path to find the correct devices. The switch configuration on all devices are the same but the ios versions and backbone connectivity differs. In my environment about the half of the node ports are just discovered as active endpoint and UDT is…

Many thanks for the reply. That's the odd, although the user inventory data functioning as expected in the user inventory page, the information is missing in the switch port pages. The missing information is the IP address in the UDT panels. I have tried every method you could guess to catch the ip address from the cisco…