@d-ray said in node staus = 5 not updated:
Still the same issu in version (2.0-RC2)
When the wan connection goes down from a remote host (proxy) the host gets status 4.
When the wan is back online the host stays on status 4 until you manually do a "poll configuration (full)"
A status poll or configuration poll manually doesn't work.
Is there a fix for the issue?
Still the same issu in version (2.0-RC2)
When the wan connection goes down from a remote host (proxy) the host gets status 4.
When the wan is back online the host stays on status 4 until you manually do a "poll configuration (full)"
A status poll or configuration poll manually doesn't work.
Victor,
we have the same issue in 2.0-M4
Regard
Denis
version 2.0-M4
Regards
Denis
Hi Victor,
Yes it is an dynamic host. (wan connection) and also a proxy host for other clients.
If the netxms server lost the connection with the host. And the ip is changed when he goes back online, the host stays offline in unknown status.
ResolveDNSToIPOnStatusPoll is set to 1
Regards,
Denis
is it possible to use the zonename in text?
HI,
When a node goes down, and gets status 5 (node unknown) it will never come back online.
I have to do a manually to poll -> configuration(full) to get back the online status of the node.
It looks once the node gets status 5 it will no longer updated in netxms.
Is that a normal behavior? or bad configuration?
Regards
Denis
Thanks for the help
Hi,
Can anyone help the for the syntax of a filter script
I want to filter all nodes with the same zoneID in one container.
sub main()
{
if ($node->zoneID == 106)
{
return 1;
}
}
Regards
Denis
I have the same issue... I post the issue already
@brettmilfos said in NetXMS 2.0-M4 released:
Hi,
Thanks for the new release, the ping bug has gone and all is good.
One problem so far, the ICMP proxy does not seem to be working. It was not working in M3, but I thought that was due to the IP being reversed, maybe not. It did seem to be working in M2.
Thanks, Brett.
I can confirm the issue is still there with a proxy server.
Regards Denis
Hi,
Thanks
The problem is now compiling the windows client ???
is there a downloadable version available ?
I was just thinking that i have some proxy servers with the old version 1.7 on it. And the ping agent isn't working after upgrading the server
Regards
Hi,
Only server.
Thanks
Hi,
I installed the patch
Only copy the 2 files in the source folder en then
sudo make
sudo make install
restart the server.
The ping is working for my local clients but not for the clients in the remote sites over proxy.
regards
Hi,
I have upgraded my netxms server to Version 2.0-M3.
I have some devices in the network that only can monitor with a ping.
The devices are in a remote network (zone & proxy server)
It isn't possible to do a status poll. the device looks offline
Devices that are in the network of the netxms server will work.
Anyone that has the same issue?
Regards
Denis
Regards
So it looks there is something wrong in the proxy agent
Hi,
I upgraded my server today and fixed the ping agent.
It looks it is working when the client is in the same network.
but when the client is contacted over a proxy server (using zones) it doesn't work.
Regards
@victor said in Primary hostname will not resolved to Primary IP Address:
I've register a change request to use agent for DNS resolution for remote zones: https://dev.raden.solutions/issues/778. Should not be hard to implement.
Best regards,
Victor
Thanks
I'm using zones.
Regards
The network discovery is working well over the proxy connection. (but without dns hostname)
Yes I confirm that the server isn't possible to resolve the Host name from the DNS.
It is the proxy agent that needs to resolve the host name. He is the only one that has access to the local LAN.
The only communication between the LAN with the netxms server in and the LAN with the DHCP agents in is the netxms Proxy agent.
There is no VPN or whatever between the different LAN'S. All the communication is over the netxms proxy (port 4700)
If you need more info let me know. Then I will make a design of the network setup.
