NetXMS Support Forum

Hi,

I still seem to be having a problem with moving nodes between zones.
I had described my problem before, but do not have a working solution yet other than deleting nodes and re-adding them (and I couldn't find my own, older post to reply to). Some of this is likely related to https://track.radensolutions.com/issue/NX-1148.
Except now I have issues where I am unable to move a node no matter how long I wait.
The error message used to be about IP address conflicts, now it just tells me "Invalid Zone ID".

And it seems to happen in other, more random, situations, so I am not sure if this is still the same issue.

--- EDIT --- The below part is indeed a different issue. --- EDIT ---
The previous issue generally happened when I wanted to change a setup like this:
- Node A sits in Zone Y. Node A is a server and NetXMS Proxy.
- Node B sits in Zone Z. Node B is a firewall/router.
- Both nodes are in the same private network and usually Node B is the default gateway for Node A.
- Node B is configured with it's public IP address in NetXMS for SNMP monitoring.
- Node A is configured with Node B's public IP address in NetXMS for Agent monitoring. Node B has a port forward for 4700 to Node A's private IP.
The above setup works fine, no issues.

Now I want both Node A and Node B to be in the same zone. The main reason being the ability to use Node A as syslog proxy for the entire private network, including the firewall.

Trying to move these into the same zone leads to (or used to lead to) an IP address conflict. The only way I can resolve this is to delete Node B, move Node A into zone Z, then re-add Node B in zone Z. After that everything works fine. Except at that point I usually hit https://track.radensolutions.com/issue/NX-1148, so it can take a while before I can move Node A.

That was my previous issue (although it still is an issue for me).

By now, I do not receive an IP address conflict message. I receive an "Invalid Zone ID" error instead.
That doesn't go away after a couple of hours either and it survives a NetXMS server reboot and nxdbmgr check run.
All I can do now is to delete Node A as well and then re-add it.

In addition, this errors has started appearing when trying to move random nodes which did and do not have IP address conflicts between zones. It also doesn't matter into which zone I want to move them - they always come back with "Invalid Zone ID".

Is this an issue in 2.1-M3?
Or do I have some database corruption somewhere which nxdbmgr check doesn't pick up?

Cheers

Hi,

Ok, I am pretty sure I stumbled into a bug in 2.1 with this issue.

When I move a node into the "Default" zone, which has Zone ID 0, it does not place the node into that zone.
Instead if places it into a different zone with Zone ID 4.
"4" happens to be the Object ID of the Default zone (not the Zone ID).

Looks like moving zones in 2.1 is linking up the wrong IDs?

That also explains the Invalid Zone ID errors we are seeing.
Our Object IDs are way higher than any Zone ID we ever assigned, so in almost all cases, it wouldn't be able to find a match at all - hence "Invalid Zone ID".

That's a bit of a problem for us right now, as we can't move nodes into the correct zones and nodes we previously tried to move into the Default zone for testing are stuck in a zone they don't belong in.

Cheers