NetXMS Support Forum

Hello

What could cause this: I have Cisco C2960x-24TS-LL switch, snmp polling is enabled. But in interface tab only other Cisco switches are found (using CDP) and Mikrotik router (using LLDP). But for example servers/cameras are not discovered. Also Topology -> Switch forwarding database is empty.

NetXMS version: 4.3.3

.1.3.111.2.802.1.1.13.1.3.2.0 empty
.1.3.111.2.802.1.1.13.1.4.1.1 empty
.1.0.8802.1.1.2.1.4.1.1 contains info and mac addresses

Hello, is there fix in planning? Cisco switches dont show mac list and connected nodes.

Connection information for end nodes that does not support LLDP or CDP is obtained from FDB, so root cause is FDB not being retrieved from the switch.
What driver is selected for the switch? Also, what is walk output for .1.3.6.1.2.1.17.4.3.1?

Best regards,
Victor

Cisco switch: C9200L-24P-4X (17.3.4b)
Driver: CISCO-GENERIC

NetXMS version 4.3.5

Sorry for delay, just get back to issues that piled up.
Looks like switch returns FDB information, so problem is within server. Can you set debug level 6 for tag "topology.fdb", run topology poll on switch node, and show me server log?

Best regards,
Victor

2023.06.14 08:31:02.336 *I* [logger            ] Debug level for tag "topology.fdb" set to 6

2023.06.14 08:31:14.866 *D* [topology.fdb      ] GetSwitchForwardingDatabase([Sw] SWITCH [132981]): cannot read port table in context vlan-1
2023.06.14 08:31:14.881 *D* [topology.fdb      ] GetSwitchForwardingDatabase([Sw] SWITCH [132981]): cannot read port table in context vlan-3
2023.06.14 08:31:14.881 *D* [topology.fdb      ] GetSwitchForwardingDatabase([Sw] SWITCH [132981]): cannot read port table in context vlan-4
2023.06.14 08:31:14.881 *D* [topology.fdb      ] GetSwitchForwardingDatabase([Sw] SWITCH [132981]): cannot read port table in context vlan-1002
2023.06.14 08:31:14.881 *D* [topology.fdb      ] GetSwitchForwardingDatabase([Sw] SWITCH [132981]): cannot read port table in context vlan-1003
2023.06.14 08:31:14.881 *D* [topology.fdb      ] GetSwitchForwardingDatabase([Sw] SWITCH [132981]): cannot read port table in context vlan-1004
2023.06.14 08:31:14.881 *D* [topology.fdb      ] GetSwitchForwardingDatabase([Sw] SWITCH [132981]): cannot read port table in context vlan-1005
2023.06.14 08:31:14.881 *D* [topology.fdb      ] GetSwitchForwardingDatabase([Sw] SWITCH [132981]): 0 entries read from dot1qTpFdbTable
2023.06.14 08:31:14.897 *D* [topology.fdb      ] GetSwitchForwardingDatabase([Sw] SWITCH [132981]): 5 entries read from dot1dTpFdbTable
2023.06.14 08:31:14.897 *D* [topology.fdb      ] GetSwitchForwardingDatabase([Sw] SWITCH [132981]): cannot read  FDB in context vlan-1
2023.06.14 08:31:14.897 *D* [topology.fdb      ] GetSwitchForwardingDatabase([Sw] SWITCH [132981]): cannot read  FDB in context vlan-3
2023.06.14 08:31:14.897 *D* [topology.fdb      ] GetSwitchForwardingDatabase([Sw] SWITCH [132981]): cannot read  FDB in context vlan-4
2023.06.14 08:31:14.913 *D* [topology.fdb      ] GetSwitchForwardingDatabase([Sw] SWITCH [132981]): cannot read  FDB in context vlan-1002
2023.06.14 08:31:14.913 *D* [topology.fdb      ] GetSwitchForwardingDatabase([Sw] SWITCH [132981]): cannot read  FDB in context vlan-1003
2023.06.14 08:31:14.913 *D* [topology.fdb      ] GetSwitchForwardingDatabase([Sw] SWITCH [132981]): cannot read  FDB in context vlan-1004
2023.06.14 08:31:14.913 *D* [topology.fdb      ] GetSwitchForwardingDatabase([Sw] SWITCH [132981]): cannot read  FDB in context vlan-1005
2023
2023.06.14 08:31:20.710 *I* [logger            ] Debug level for tag "topology.fdb" set to 0

Log from management:
[14.06.2023 08:31:14] **** Poll request sent to server ****
[14.06.2023 08:31:14] Poll request accepted, waiting for outstanding polling requests to complete...
[14.06.2023 08:31:14] Starting topology poll of node [Sw] SWITCH
[14.06.2023 08:31:14] VLAN list successfully retrieved from node
[14.06.2023 08:31:14] Switch forwarding database retrieved
[14.06.2023 08:31:14] Link layer topology retrieved (7 connections found)
[14.06.2023 08:31:15] Updating peer information on interfaces
[14.06.2023 08:31:15]    Local interface Gi1/0/10 linked to remote interface [Sw] NAME1:Gi0/10
[14.06.2023 08:31:15]    Local interface Gi1/0/15 linked to remote interface [Sw] NAME2:Gi0/10
[14.06.2023 08:31:15]    Local interface Te1/1/1 linked to remote interface [Sw] NAME3:Ethernet1/1
[14.06.2023 08:31:15]    Local interface Te1/1/2 linked to remote interface [Sw] NAME4:Ethernet1/1
[14.06.2023 08:31:15] Link layer topology processed
[14.06.2023 08:31:15] Finished topology poll of node [Sw] SWITCH
[14.06.2023 08:31:15] **** Poll completed successfully ****

Thats the output i got. Hope it helps.

Am I understand correctly that this problem is on all Cisco switches? What SNMP version you are using? If you are using version 3, make sure that you have allowed access to vlan-* contexts. Command should be similar to this:

snmp-server group GroupName V3 priv context vlan- match prefix
Best regards,
Victor

Problem is present on all Cisco switches yes, snmp version is v3. I tested the context snmp command on one switch and now it shows other peer nodes aswell. il have to test other switches toobut i think the solution is found. Thank you for the helpfull tip!  

Egert