NetXMS Support Forum

We are getting close, I see there is a NIC Vendor column now in the Object Details > Interfaces tab, so feature must be nearly ready....

Plus one, subnet-level would be a great place to be able to define a proxy.

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.

How about a banner at the top of every wiki page saying they're historical?

In the FDB/ARP cache poll output, a column with the MAC vendor in it would be very useful.

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.

Great stuff!

To be precise, this is when deployed in Tomcat, not with a standalone management console.

Not sure if this is a bug or the intended behaviour, but if you update the server to 4.1.404 and leave NXMC on 4.1.333, then "Rename" is greyed out on nodes.  Not a fluke, I've seen this happen on two different installs.

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?

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.

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

I don't have an answer for you but I can say that this doesn't happen to me with 4.1.333.

Address filter is empty, just filtering on SNMP/SSH/agent protocol.
Following hints in this thread
https://www.netxms.org/forum/general-support/discovery-through-proxy/15/
I increased ThreadPool.Discovery.BaseSize from 1 to 4 and enabled parallel processing, then restarted the service.
The expected node was then discovered by the next day [as with the other system, log level is such that they were rotated away so I don't know exactly when].

I am going to assume that other things I wasn't specifically looking for have been discovered as well.

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