"Interfaces" tab

[lindeamon]

hi victor,

you have added "peer..." options to the "interfaces" tab and when i look at the info i see doubles and i will explain.
i have a printer which is connected to port 2 and i see it on the peer name and it is correct but i see it also on port 20 and the difference between them is that the "admin state" and "oper state" are "down" and the "status" is "disabled".
i have seen this on other entities and i also see a desktop connected to one of this ports where in fact it is physically connected to another switch.
what is the problem ?

Best Regards,
Lindeamon

[victor]

Can it be that said printer was connected to port 20 before? Or it was always in port 2?

Best regards,
Victor

[lindeamon]

hi victor,

i can not say for sure but there is a chance that it was connected.
if this is the case, where does this info saved ? arp table ?

Best Regards,
Lindeamon

[victor]

Hi!

No, it's actually is/was a bug in NetXMS. Information about connected peer node is stored in interface object itself, and supposed to be cleared when same node found on another interface. This bug should be fixed in 1.2.2, but if node move to another port was discovered before upgrade, peer information on old interface might not be updated. Keep looking if new stalled peer information will appear. If possible, try to do some tests - connect node to one port for few hours, ensure that it is shown on correct port, then reconnect to another port, and check again after few hours - it should corrrectly show node on new interface and nothing on old interface.

Best regards,
Victor

[lindeamon]

hi victor,

this is from 1.2.2 if this feature was presented in 1.2.1 then i have not seen it.
i found it after installing 1.2.2.
i will keep track of things.isn't there a way to clear this ?

Best Regards,
Lindeamon

[victor]

Hi!

"Interfaces" tab is a new feature in 1.2.2, but interface peer tracking is there since some version in 1.1.x branch. This information was shown previously in object overview tab for interface objects. You can clear that by deleting interface object with wrong peer information and running configuration poll - server will rediscover interface and create new interface object without peer information.

Best regards,
Victor

[lindeamon]

hi victor,

sorry for being a nag, but shouldn't it be automatically ?

Best Regards,
Lindeamon

[victor]

Yes, it should, but due to a bug existed before 1.2.2, some interfaces have stalled peer information. It should be cleared when you connect new devices to ports with wrong information, or when device incorrectly pointed as peer will be moved to yet another port. I'll also consider possibility to add background peer validation in 1.2.3 to clear incorrect peer information.

Best regards,
Victor

[lindeamon]

hi victor,

good to hear, when are you planning to issue the next release ?
you are suppose to be on vacation for three weeks, aren't you ?

Best Regards,
Lindeamon

[victor]

Hi!

I'm already back from vacation I don't know exact release date for 1.2.3 yet. Most likely it will be somewhere in the end of August.

Best regards,
Victor