NetXMS Support Forum

I added a second device and it was placed in the wrong subnet container so now I have 2 10.168.0.0/21.  It is a Cisco router and a WatchGuard (ASA competitor).  I double checked the IPs/subnets on both and they are correct, any thoughts?  I deleted and added back both devices, still no luck.

One device is 10.168.0.1 and the other is 10.168.1.1.

When I right click a node Tools -> connect, it would be wonderful to be able to select RDP, Telnet or SSH.  Additionally, using fancy reverse-ssh tunneling or stunnel or something (in my mind, easier with a linux based server), having it launch the sessions FROM the management server would make my ACLs smaller and more concise (only opening things for the management server and requiring all access through the server).

An alternative, "user-defined" option (maybe configurable from the server's control panel) could be used to launch scripts (where I could define the reverse tunnels or to launch PuTTY from my windows laptop).

If any of this is do-able from the console already and I haven't RTFM'd enough let me know.  I haven't looked into NXSL at all and the I have used the manual to fill in gaps when something wasn't working as expected.

I've been using the development console (I guess it is now Console 1.1.0).  Under Layer-2 discovery I got the error that my device doesn't support it.  Checked it with Info LLDP poll, no output, but CDP does work.  (Some of my Cisco gear is EoL).

It would be great to have the layer 2 topology work from CDP as well as LLDP.

I am monitoring several nodes in my NetXMS install (on Ubuntu, ver. 1.0.10, sqlite).  I have been getting errors in the log DCI___ Internal: AverageDCPollerQueueSize, DBWriterQueueSize, QueueingTime, PollerQueue and ConfigPollerQueueSize all changing to unsupported (manually clearing buys me about 4 hours before they reappear).  Then a bunch of services go down.  Doing a status poll manually shows it is trying to be done with the wrong IP address (it seems to be using the management IP from a Cisco 6509 (130+ interfaces)).  So I looked at the 6509 node and it had the XMS interfaces only (different from when I initially added it) It had the XMS public IP, internal IP and the NAT Adapter.  So I deleted the 6509 node and all the alarms immediately cleared.  Readded the 6509, populated all the 130+ interfaces (I know because of my 136 emails received seconds after) and all the alams (DCI and servies) went down and unavailable again and the manual poll showed the 6509 address again.

Thoughts?