Menu

Show posts

This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.

Show posts Menu

Topics - troffasky

#1
General Support / How are the intervals on graphs chosen?
November 21, 2023, 06:33:59 PM
How are these intervals chosen? Looks a bit random. 1323, 1421, 1520, etc.
Also would be great if there was a marker at 00:00.
ksnip_20231121-161702.png
#2
Tomcat 9.0.58
NetXMS server 4.4.3
WAR file 4.4.3
Firefox 119 on the client side.

I get various UI glitches when navigating around.

A popup with 'Cannot invoke "org.eclipse.swt.graphics.Color.getRGB()" because "color" is null' will appear at random.

The vertical divider that separates the navigation tree from the main pane of the interface will jump around when clicking in to different icons on the left. It also moves around when resizing the browser window.

There is no scrollbar so at Node level the right-most tabs will simply be off the screen with no way to get to them. Lack of scrollbars applies in other areas as well.
#3
I have a zone that contains:
1x Linux node which is NATed and reached through a port forward on below firewall.
1x firewall on edge
8x switches that use the Linux node as proxy for SNMP/ICMP/etc.

Linux node and switches are being monitored just fine.

I cannot add firewall by public IP because the IP conflicts with the Linux node and duplicate add is prevented.
I can add the firewall with its private IP, but then some hours later, NetXMS deletes it when it realises that the firewall's outside IP is detected as a duplicate of the Linux node.

I could have sworn I'd succeeded at this in the past. I would think it's a fairly common configuration. Do I need to do something "special" to the Linux node to prevent the duplicate detection?
#4
Since updating to 4.4, I no longer see the "Change interface expected state" option. This now has to be done at Properties > Polling, which is only one interface at a time.
Can I expect the old behaviour to come back at some point?
#5
General Support / Teltonika driver, node name
July 13, 2023, 01:41:09 PM
Teltonika SNMP implementation is a bit annoying in that it doesn't populate sysName with the actually configured name of the device. When you install the SNMP package the sysName defaults to 'name'.
I can see that the "Product Name" field detected by the Teltonika driver is actually a useful value, however.
So would it be possible to derive the node name for nodes using the Teltonika driver, from the Product Name?
#6
In address search results, the Switch node is given, if known. It would be nice if I could right-click on the result row and jump straight to the Object Details view of that node. Same for the Node column too, I guess.
#7
In the FDB/ARP cache poll output, a column with the MAC vendor in it would be very useful.
#8
Feature Requests / Vector map export
July 19, 2022, 04:29:55 PM
Bit of a big ask this one, probably, but....Vector map exports. Plain SVG would be good but what would be great would be drawio. Great diagram program and it's open-source.
#9
With some Cisco SB switches, if you put them in stack mode then every possible potential interface in a stack is enumerated with SNMP. For example  gi1/0/1 - gi8/0/52 [and the equivalent FastEthernet as well] even if this is a "stack" of just one switch. As an example, I am look at an SG500-28P that has nearly 1000 interfaces, of which only 28 are real physical interfaces, a few are VLANs and the rest are just "imaginary".

They all have an operation state of "notPresent" so should be straightforward enough to filter out, hide or disregard, but can I do this in NetXMS?
#10
Just looking at a server where the NodeDiscoveryPoller queue is over 600000. I can see in the logs that it is trying many many IP address starting with 172.
I found that I had added a discovery target of 172.28.15.0 with a netmask of /0. I don't actually know what this means to NetXMS, was it trying from 0.0.0.0 to 255.255.255.255 inclusive?
I think a warning that a netmask of /0 means way more IP addresses than you'd usually want would be a good idea here.
#11
I find the Object Details > Interfaces view a bit unwieldy due to how many columns there are [I am still scrolling with a 2560x1440 screen], but I appreciate the ability to just export all this info to CSV [useful when assembling a report on a switch].
It would be nice to have a customisable list of fields to choose.
Maybe even some task-focused presets, for example:
- All [obvious]
- Topology: Name, Alias, Description, the 5 Peer* columns, *State columns
- Other use cases I haven't thought of
#12
16:12:21.546 *D* [topology.cdp       ] CDP(sw1 [165174]): remote IP address 192.168.10.5
16:12:21.547 *D* [topology.cdp       ] CDP(sw1 [165174]): node object for remote IP 192.168.10.5 not found


It's found this from the CDP neighbours table, presumably, but there's no hint of this in the UI. It's good information to know about, although could be optional.
Maybe the interface list is not the place for this information, it's already eleventy columns wide and needs another column like I need a hole in the head :D
#13
Currently have debug level on 5.
Have a /24 subnet with multiple nodes that NetXMS has discovered previously. Two new hosts were added to this network but I just cannot get NetXMS to discover them automatically.
"Active discovery - node 172.22.141.37 responded to ICMP probe via proxy" is logged but that's it, it doesn't log that it took any further action on that specific IP.
If I add the node manually it works instantly, ie, the host is configured with the correct SNMP community.
"Starting SNMP check on range" is logged for the IP range that covers that host, but that's it.
It also mentions that it knows this host from another node's ARP cache.
#14
General Support / Cisco CBS switches driver
May 31, 2022, 07:43:02 PM
Cisco CBS series switches are the successor to the Cisco Small Business series switches.
I think it would probably make sense to use CISCO-SB driver for these switches.
Do you want some snmpwalk output or similar to help add support for these switches to the CISCO-SB driver?
#15
General Support / What are "end nodes" in maps?
May 17, 2022, 12:45:32 PM
If I check "include end nodes" in an L2 map, I get printers and APs.
In my opinion, printers are definitely end nodes and switches are definitely not.
What about APs? I reckon in the context of an L2 map that an AP is not an end node - it provides a L2 connectivity to wireless clients.
How does NetXMS determine what an end node is?
#16
Feature Requests / Improvements for Address Map
May 13, 2022, 06:27:06 PM
Address Map is a useful tool but I think a few things could enhance it:

  • Some way of representing DHCP scopes. I guess this would just be a parameter on the "Subnet" Object class rather than a dummy host that has 50 IP addresses
  • Populate it from ARP cache as well
  • Colour the above two things with different colours or symbols to distinguish how "true" they might be
  • Tooltip when hovering over an IP if it's a known node, click on it to jump to it, etc
  • Right click on a "free" IP with option to ping from an agent if there is one in that network with ICMP subagent, and report back if IP was free and no ARP response seen
#17
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
#18
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].
#19
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?
#20
General Support / Zone proxy inside zone conundrum
September 17, 2021, 03:03:32 PM
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.