NetXMS Support Forum

For reference, the above is all about Sonicwall Gen 6 devices. I have added a Gen 7 device to NetXMS, this does not have IP-MIB::ipAddressIfIndex entries and interface table in NetXMS appears as it should do.
Gen 6 is end of sale and nearing end of life, so this defect will never be fixed by Sonicwall.

Just occurred to me that I didn't see 127.0.0.1 in any of that, so I looked over the snmpwalk again and this is probably the cause here - the IP-MIB:


IP-MIB::ipAddressIfIndex.ipv4."88.xx.xx.142" = INTEGER: 4
IP-MIB::ipAddressIfIndex.ipv4."94.xx.xx.34" = INTEGER: 3
IP-MIB::ipAddressIfIndex.ipv4."94.xx.xx.35" = INTEGER: 3
IP-MIB::ipAddressIfIndex.ipv4."127.0.0.1" = INTEGER: 1
IP-MIB::ipAddressIfIndex.ipv4."172.22.40.1" = INTEGER: 10
IP-MIB::ipAddressIfIndex.ipv4."172.22.140.1" = INTEGER: 2
IP-MIB::ipAddressIfIndex.ipv4."172.22.240.1" = INTEGER: 11
IP-MIB::ipAddressIfIndex.ipv6."00:00:00:00:00:00:00:00:00:00:00:00:00:00:00:01" = INTEGER: 1


The IP-MIB entries look a bit random, there is no interface index 10 or 11!
Not an SNMP expert but I think the above explains this? Ie, it's a Sonicwall issue, not an NetXMS one.

In the attached, IPs in green are correct, IPs in red are incorrect. For whatever reason, NetXMS thinks the same IPs are on multiple interfaces. This is not something that just appeared in 4.1.283, I think it's been there a while. It seems to affect Sonicwalls particularly, didn't notice it anywhere else.

It's not obvious from an snmpwalk how this would arise:


RFC1213-MIB::ifIndex.1 = INTEGER: 1
RFC1213-MIB::ifIndex.2 = INTEGER: 2
RFC1213-MIB::ifIndex.3 = INTEGER: 3
RFC1213-MIB::ifIndex.4 = INTEGER: 4
RFC1213-MIB::ifIndex.5 = INTEGER: 5
RFC1213-MIB::ifIndex.6 = INTEGER: 6
RFC1213-MIB::ifIndex.7 = INTEGER: 7
RFC1213-MIB::ifIndex.8 = INTEGER: 8
RFC1213-MIB::ifIndex.268484097 = INTEGER: 268484097
RFC1213-MIB::ifIndex.268486657 = INTEGER: 268486657
RFC1213-MIB::ifDescr.1 = STRING: "X0 (Portshield Host)"
RFC1213-MIB::ifDescr.2 = STRING: "X1 (WAN)"
RFC1213-MIB::ifDescr.3 = STRING: "X2 (WAN)"
RFC1213-MIB::ifDescr.4 = STRING: "X3 (Portshielded To X0)"
RFC1213-MIB::ifDescr.5 = STRING: "X4 (Portshielded To X0)"
RFC1213-MIB::ifDescr.6 = STRING: "X5 (Portshielded To X0)"
RFC1213-MIB::ifDescr.7 = STRING: "X6 (Portshielded To X0)"
RFC1213-MIB::ifDescr.8 = STRING: "U0 (Unassigned)"
RFC1213-MIB::ifDescr.268484097 = STRING: "X0:V190 (Guest Wireless)"
RFC1213-MIB::ifDescr.268486657 = STRING: "X0:V200 (LAN)"
RFC1213-MIB::ipAdEntAddr.88.xx.xx.142 = IpAddress: 88.xx.xx.142
RFC1213-MIB::ipAdEntAddr.94.xx.xx.34 = IpAddress: 94.xx.xx.34
RFC1213-MIB::ipAdEntAddr.172.22.40.1 = IpAddress: 172.22.40.1
RFC1213-MIB::ipAdEntAddr.172.22.140.1 = IpAddress: 172.22.140.1
RFC1213-MIB::ipAdEntAddr.172.22.240.1 = IpAddress: 172.22.240.1
RFC1213-MIB::ipAdEntIfIndex.88.xx.xx.142 = INTEGER: 3
RFC1213-MIB::ipAdEntIfIndex.94.xx.xx.34 = INTEGER: 2
RFC1213-MIB::ipAdEntIfIndex.172.22.40.1 = INTEGER: 268484097
RFC1213-MIB::ipAdEntIfIndex.172.22.140.1 = INTEGER: 1
RFC1213-MIB::ipAdEntIfIndex.172.22.240.1 = INTEGER: 268486657
RFC1213-MIB::ipAdEntNetMask.88.xx.xx.142 = IpAddress: 255.255.255.252
RFC1213-MIB::ipAdEntNetMask.94.xx.xx.34 = IpAddress: 255.255.255.252
RFC1213-MIB::ipAdEntNetMask.172.22.40.1 = IpAddress: 255.255.255.0
RFC1213-MIB::ipAdEntNetMask.172.22.140.1 = IpAddress: 255.255.255.0
RFC1213-MIB::ipAdEntNetMask.172.22.240.1 = IpAddress: 255.255.255.0


Don't know if you've fixed this but in NXMC legacy 4.1.283, the MAC address search results title is "Searh" not "Search".

Just to be clear, I wasn't questioning the value of reporting bugs about NetXMS at all, it was more whether I should be doing so against the preview. And the answer seems to be yes 

Updated server. Using nxmc-legacy-4.1.283.war.
When I do a "Find switchport", I get a result in a popup, but it won't populate the results table and I get an error popup.
[Can't copy the error, screenshot attached].

Is it worth bringing these up here?

Can't load maps, every map I load gives me this:

Error: Error: Operation "set" on target "w138" of type "rwt.widgets.Slider" failed:
Scrollbar thumb must be positive
Properties:
bounds = 0,-16,0,16
visibility = true
thumb = 0


[yes they load fine with nxmc-legacy-4.1.283].

Yes, set to AUTO was the fix. Removed/readded a switch, behaves as expected.

Objects.Interfaces.DefaultExpectedState is set to UP.
Documentation says default is "1".  https://www.netxms.org/documentation/adminguide/appendix.html
I guess it should be AUTO? I swear I didn't change this.

I just added a new CiscoSB switch, this has the CISCO-SB driver and does the same.

Ubiquiti Unifi Switch USW-Pro-Aggregation, 5.76.7.13442.
Driver is GENERIC and the Unifi Switch template has been applied automatically.

Server is 4.0.2157.

First new device I have added since upgrading to 4.0.
The default interface expected state is UP for every interface, leading to the node immediately going Critical due to many of the ports being down.
This device is definitely completely new, nothing has had this hostname or IP before.
I could have sworn that previously, the expected state when adding a device is the current state, ie when you add it, it is assumed to be all OK. Then any deviation from this in future causes an alarm.
Is this new behaviour in 4.x compared to 3.x?

It seems like upgrading to 4.0 got this working without me having to do anything else.

More to the point, the Debian packages ship with a config file that says mysql.ddr.

Server: 3.9.235-1
Agent: 3.9.235-1
Agent config:

MasterServers=192.168.253.0/24
SubAgent = ping.nsm
# Allow server to proxy requests through here
EnableSNMPProxy=yes
EnableProxy=yes



Zone contains the agent + other devices.
The agent is 100% reachable from the server. I can ping it from the server, I can telnet to port 4700 on the agent from the server. If I packet capture on port 4700 on the agent, I can see dialogue between agent and server happening regularly.
I want this zone configured with this one agent as the proxy.
If I make this agent the proxy for the zone, it becomes unreachable.

Poll agent status. Note how quick it is. Doing a packet capture on agent and server I see no ICMP at all between them whilst the poll is running, and ICMP being down seems to preclude any further checks. Nothing logged on agent when poll is run even at debug level 5.

[2021.09.17 12:49:59] **** Poll request sent to server ****
[2021.09.17 12:49:59] Poll request accepted, waiting for outstanding polling requests to complete...
[2021.09.17 12:49:59] Starting status poll for node zabbixproxy
[2021.09.17 12:49:59]    Starting status poll on interface lo
[2021.09.17 12:49:59]       Current interface status is UNKNOWN
[2021.09.17 12:49:59]       Interface status cannot be determined
[2021.09.17 12:49:59]       Interface is UNKNOWN for 9417 polls (1 poll required for status change)
[2021.09.17 12:49:59]       Interface status after poll is UNKNOWN
[2021.09.17 12:49:59]    Finished status poll on interface lo
[2021.09.17 12:49:59]    Starting status poll on interface ens160
[2021.09.17 12:49:59]       Current interface status is UNKNOWN
[2021.09.17 12:49:59]       Starting ICMP ping via proxy
[2021.09.17 12:49:59]       ICMP proxy not available
[2021.09.17 12:49:59]       Interface is UNKNOWN for 1 poll (1 poll required for status change)
[2021.09.17 12:49:59]       Interface status after poll is UNKNOWN
[2021.09.17 12:49:59]    Finished status poll on interface ens160
[2021.09.17 12:49:59] Node is still unreachable
[2021.09.17 12:49:59] Finished status poll for node zabbixproxy
[2021.09.17 12:49:59] Node status after poll is CRITICAL
[2021.09.17 12:49:59] **** Poll completed successfully ****



Remove this agent as the proxy for the zone, re-poll:

[2021.09.17 12:50:31] **** Poll request sent to server ****
[2021.09.17 12:50:31] Poll request accepted, waiting for outstanding polling requests to complete...
[2021.09.17 12:50:31] Starting status poll for node zabbixproxy
[2021.09.17 12:50:31]    Starting status poll on interface lo
[2021.09.17 12:50:31]       Current interface status is UNKNOWN
[2021.09.17 12:50:31]       Interface status cannot be determined
[2021.09.17 12:50:31]       Interface is UNKNOWN for 9418 polls (1 poll required for status change)
[2021.09.17 12:50:31]       Interface status after poll is UNKNOWN
[2021.09.17 12:50:31]    Finished status poll on interface lo
[2021.09.17 12:50:31]    Starting status poll on interface ens160
[2021.09.17 12:50:31]       Current interface status is UNKNOWN
[2021.09.17 12:50:31]       Starting ICMP ping
[2021.09.17 12:50:31]       Interface is NORMAL for 1 poll (1 poll required for status change)
[2021.09.17 12:50:31]       Interface status changed to NORMAL
[2021.09.17 12:50:31]       Interface status after poll is NORMAL
[2021.09.17 12:50:31]    Finished status poll on interface ens160
[2021.09.17 12:50:31] Node recovered from unreachable state
[2021.09.17 12:50:31]    Starting status poll on interface lo
[2021.09.17 12:50:31]       Current interface status is UNKNOWN
[2021.09.17 12:50:31]       Interface status cannot be determined
[2021.09.17 12:50:31]       Interface is UNKNOWN for 9419 polls (1 poll required for status change)
[2021.09.17 12:50:31]       Interface status after poll is UNKNOWN
[2021.09.17 12:50:31]    Finished status poll on interface lo
[2021.09.17 12:50:31]    Starting status poll on interface ens160
[2021.09.17 12:50:31]       Current interface status is NORMAL
[2021.09.17 12:50:31]       Starting ICMP ping
[2021.09.17 12:50:31]       Interface is NORMAL for 1 poll (1 poll required for status change)
[2021.09.17 12:50:31]       Interface status after poll is NORMAL
[2021.09.17 12:50:31]    Finished status poll on interface ens160
[2021.09.17 12:50:31] Node is connected
[2021.09.17 12:50:37] Finished status poll for node zabbixproxy
[2021.09.17 12:50:37] Node status after poll is MAJOR
[2021.09.17 12:50:37] **** Poll completed successfully ****



I feel like I'm missing something here.