I have attached the logs. I think i know whats going on and it seems to be on the switch side but not 100% sure. For each node that has been fully polled the interfaces all show as
ETHERNET PORT 1
.
.
ETHERNET PORT 10
However the lldptables from the switch show completely different port names
PORT1
.
.
PORT8
SFP-1GLXLC-T
SFP-1GLXLC-T
I can only get the topology to work if I uses alias's and SNMP SET the alias to match the lldp port name. So setting port 9 and 10 to SFP-1GLXLC-T on both switches will allow the connections to be found. But I really don't want to script this up just to get things working and if the SFP is changed it could end up being a different port name. I would think Netxms would be able to just use the port index and FDB but maybe since LLDP is enabled that is not being used. One other thing is the switched is a L3/L2 but is only on layer2 mode but is still discovered by netxms as being a router so the dot1qtpfdbtable does not return any entries only dot1dfdtable returns. Hope this helps and thank you for your time.
Gary
ETHERNET PORT 1
.
.
ETHERNET PORT 10
However the lldptables from the switch show completely different port names
PORT1
.
.
PORT8
SFP-1GLXLC-T
SFP-1GLXLC-T
I can only get the topology to work if I uses alias's and SNMP SET the alias to match the lldp port name. So setting port 9 and 10 to SFP-1GLXLC-T on both switches will allow the connections to be found. But I really don't want to script this up just to get things working and if the SFP is changed it could end up being a different port name. I would think Netxms would be able to just use the port index and FDB but maybe since LLDP is enabled that is not being used. One other thing is the switched is a L3/L2 but is only on layer2 mode but is still discovered by netxms as being a router so the dot1qtpfdbtable does not return any entries only dot1dfdtable returns. Hope this helps and thank you for your time.
Gary
Thanks for the info
I always thought timeseries databases where better suited for NMS's