NetXMS Forum

Thank you very much for your quick reply. Our use case is: based on historical IP addresses (for example, IPs logged when users access critical systems), we want to look up the MAC address associated with that IP at that point in time, so we can identify the specific endpoint. We look forward to this new feature. Many thanks!

Got it, thank you very much for your reply!

Thank you very much.

Thanks very much!

Thanks a lot for your help. I'll give it a try.

We suspect it might be a switch configuration problem, yet it functions normally occasionally. We’ll keep an eye on it. Thanks for your help.

Make sure you have --enable-auto-tool-choice set as well. If won't help, try --tool-call-parser=pythonic

That's wonderful! I'm looking forward to the next version update, and thank you so much for your tremendous help!

[color=#1f1f1f][size=5][font=Verdana, Arial, Helvetica, sans-serif]OK。。 thank you very much![/font][/size][/color]

Tested version 4.4.4 and the problem remains... Looking forward to it, thanks a lot!

@victor said in Help: H3C port security policy causes the switch to fail to learn the interface: I've added processing of FDB record status 6 - next patch release should process them in a same way as status 3 (dynamic). Best regards, Victor The problem has been solved in the just released version 4.3.6, thank you very much!

@victor said in How to discover all peer nodes completely?: I have made some changes in reading LLDP information in upcoming release 4.4.1. FIrst of all there were few bugs left in reading LLDP-V2 MIB. Also, now server will use both LLDP-MIB and LLDP-V2-MIB if supported by device, and LLDP-MIB takes precedence. This should solve discovery issues. Best regards, Victor We've updated to version 4.4.1 and it looks like H3C's Neighborhood Discovery feature should be working fine, fantastic, thanks so much!

Why are the epel and fedora sources not updated to the latest 4.3.2 version, thank you very much! Also, there seems to be a peer node recognition problem in 4.3.1, for example, aggregated devices can only recognize individual downlinked devices, while in the previous version 4.3.0 they could be fully recognized.

try running yum update yum install jansson

 Thanks very much,  I will try again！

Thank you very much for the pointers!

Thank you very much for your advice! This is really the most powerful network manager I have ever tried!

ok,thank you very much!!