NetXMS Forum

Issue was fixed by 3.1. Not really much help here. 

Templates are matched on guid.

And here I was thinking my excessively complicated PowerShell to create a service desk ticket was just me (which it still largely probably is). Switch management in remote networks is potentially on my horizon, so good to hear that a) somebody else got it working and b) they used PowerShell. My only hard requirements were SSH (Securecrt or Putty) and Utilization / Packet loss at a Node level and at an interface level. This functionality should deliver the first and I assume that Utilisation and Packet Loss could / should probably be added to the Network template to give me the second. (add .13 .14 .19 and .20 from iftable) Once v3 is out, will check out what options are now available.

Any client OS. I gave up on  Ubuntu 18.04. Installed server on Windows, worked on first try.

What is the proper way to setup proxy agent for remote network? I followed documentation and enabled zones. I have port 4700 open on agent machine. I added agent node manually with external IP address to default zone. I added other nodes to different zone and first node as proxy. Remote network subnet object appeared twice in both default zone and remote network zone. There are other remote networks that will be added later and they will overlap.

Hi. I am using 2.0-M5 and still getting the alert. Has not been fixed yet? [image: 2015-08-07_20-23-44.png]