Hi,

Another odd thing I have noticed.

I have some win2k3 servers and ......

Why? In 3 months support will end completely.. No more security updates for you and no more support for anything you encounter on them.
You should worry about upgrading them.

@d-ray said in NetXMS 2.0-M3 released:

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.

did you upgrade agent on proxy node?

Best regards,
Victor

@djex81 said in NetXMS 2.0-M3 released:

Hi Victor, in this new update you fixed the broken SNMP in agents and that works great but now I am unable to use SNMP from the server netxms is installed on. It was working in version 2.0-M2. What happens is this:

1. I do a configuration poll on the netxms server node. SNMP is connected to and values read.
2. I try to do a SNMP walk from netxms on the local netxms server node and it fails or gives no results back.
3. If I then do another configuration poll on the netxms server node SNMP fails and isn't found.

I know SNMP works as I can SNMP walk with a separate program without any issues. I tried deleting the netxms server node and having it recreate it self but that did not help. Could it be something to do with the new IPv6 interfaces in this new version?

Basically, SNMP is working for all other nodes except the node netxms server is installed on.

To add to my previous post quoted above when I do a status poll on the netxms server node SNMP errors with:

[13.04.2015 11:50:24] Checking SNMP agent connectivity
[13.04.2015 11:50:32] SNMP agent unreachable

The SNMP agent is local so I'm not sure why it's unreachable. I can sometimes get it to connect to SNMP but most of the time it will not. I find if I am able to connect and I try to do a SNMP walk from netxms it will loose SNMP connection and return no results. I have had it return results successfully but only a few times. What debug level should I use so I can check the logs? I tried debug 7 but I couldn't see much in the way of SNMP errors.

UPDATE: I believe I've found the cause of the problem. It turned out to be the agent for our APC UPS causing SNMP to hang randomly. I updated the APC agent and so far it's working well. It's strange that it was working just fine in 2.0-M2 though. Oh well it's working now.

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

Hi!

@brettmilfos said in NetXMS 2.0-M3 released:

I have found a couple of problems with ping after the upgrade from 2.0-M2 to 2.0-M3.

One is the ping agent not working, but have got around that by reversing the IP addresses in the conf file.

The second is the ICMP proxy is not working. I would assume it is related to the same issue as the ping agent?

yes, both are related to same problem (also discussed in another post). You can apply patch posted earlier if you are building from sources, or I can provide compiled ping subagent for Windows. Also, we likely to publish patch release soon which will fix issues found so far.

Best regards,
Victor

Thanks, I can live with the work around until patch release.

Hi Victor,

when do you plan to publish the new installation packages with all the fixes ?
up until now i was under the impression that all the new releases are stable ones, what happened ? why does 1.2.17 is considered stable ? we are losing a lot of new and cool features if do not use the latest version.
when will the next stable release is due ?

Best Regards,
Lindeamon

Hi,

we do lot of internal changes (mostly targeted at IPv6 support), so few next M releases could have problems. It can be used in production, although you always should test it on test system if possible. We plan to rerlease M4 very soon which will fix most important issues found so far in M3. I think that stability will improve with next releases as major internal changes are already made and we will focus on fixing bugs and adding features that do not require so big changes in system core.

Best regards,
Victor

when do you plan to publish the new installation packages with all the fixes ?
up until now i was under the impression that all the new releases are stable ones, what happened ? why does 1.2.17 is considered stable ? we are losing a lot of new and cool features if do not use the latest version.
when will the next stable release is due ?

Best Regards,
Lindeamon

What operating system and SNMP version used? If you are using SNMP v3, do you use authentication and encryption, and what algorithms?

Best regards,
Victor

I am using Windows Server 2008 R2 Standard with SNMP version 2c. There is no authentication or encryption at the moment.

Attached are screen shots of the properties pages for the server node.

@victor said in NetXMS 2.0-M3 released:

What address you have set as primary host name for management server node? Can you do nxsnmpwall on that address?

Best regards,
Victor

For the server node I am using the local address 10.0.0.2 . Yes, I can nxsnmpwalk on 10.0.0.2 without any issues.

What operating system and SNMP version used? If you are using SNMP v3, do you use authentication and encryption, and what algorithms?

Best regards,
Victor

@brettmilfos said in NetXMS 2.0-M3 released:

I have found a couple of problems with ping after the upgrade from 2.0-M2 to 2.0-M3.

One is the ping agent not working, but have got around that by reversing the IP addresses in the conf file.

The second is the ICMP proxy is not working. I would assume it is related to the same issue as the ping agent?

yes, both are related to same problem (also discussed in another post). You can apply patch posted earlier if you are building from sources, or I can provide compiled ping subagent for Windows. Also, we likely to publish patch release soon which will fix issues found so far.

Best regards,
Victor

What address you have set as primary host name for management server node? Can you do nxsnmpwall on that address?

Best regards,
Victor

For the server node I am using the local address 10.0.0.2 . Yes, I can nxsnmpwalk on 10.0.0.2 without any issues.

@djex81 said in NetXMS 2.0-M3 released:

Hi Victor, in this new update you fixed the broken SNMP in agents and that works great but now I am unable to use SNMP from the server netxms is installed on. It was working in version 2.0-M2. What happens is this:

1. I do a configuration poll on the netxms server node. SNMP is connected to and values read.
2. I try to do a SNMP walk from netxms on the local netxms server node and it fails or gives no results back.
3. If I then do another configuration poll on the netxms server node SNMP fails and isn't found.

I know SNMP works as I can SNMP walk with a separate program without any issues. I tried deleting the netxms server node and having it recreate it self but that did not help. Could it be something to do with the new IPv6 interfaces in this new version?

Basically, SNMP is working for all other nodes except the node netxms server is installed on.

To add to my previous post quoted above when I do a status poll on the netxms server node SNMP errors with:

[13.04.2015 11:50:24] Checking SNMP agent connectivity
[13.04.2015 11:50:32] SNMP agent unreachable

The SNMP agent is local so I'm not sure why it's unreachable. I can sometimes get it to connect to SNMP but most of the time it will not. I find if I am able to connect and I try to do a SNMP walk from netxms it will loose SNMP connection and return no results. I have had it return results successfully but only a few times. What debug level should I use so I can check the logs? I tried debug 7 but I couldn't see much in the way of SNMP errors.

What address you have set as primary host name for management server node? Can you do nxsnmpwall on that address?

Best regards,
Victor

Hi Victor, in this new update you fixed the broken SNMP in agents and that works great but now I am unable to use SNMP from the server netxms is installed on. It was working in version 2.0-M2. What happens is this:

1. I do a configuration poll on the netxms server node. SNMP is connected to and values read.
2. I try to do a SNMP walk from netxms on the local netxms server node and it fails or gives no results back.
3. If I then do another configuration poll on the netxms server node SNMP fails and isn't found.

I know SNMP works as I can SNMP walk with a separate program without any issues. I tried deleting the netxms server node and having it recreate it self but that did not help. Could it be something to do with the new IPv6 interfaces in this new version?

Basically, SNMP is working for all other nodes except the node netxms server is installed on.

To add to my previous post quoted above when I do a status poll on the netxms server node SNMP errors with:

[13.04.2015 11:50:24] Checking SNMP agent connectivity
[13.04.2015 11:50:32] SNMP agent unreachable

The SNMP agent is local so I'm not sure why it's unreachable. I can sometimes get it to connect to SNMP but most of the time it will not. I find if I am able to connect and I try to do a SNMP walk from netxms it will loose SNMP connection and return no results. I have had it return results successfully but only a few times. What debug level should I use so I can check the logs? I tried debug 7 but I couldn't see much in the way of SNMP errors.

Another odd thing I have noticed.

I have some win2k3 servers and they are reporting the wrong netmask for interfaces. They have a /23 netmask but NetXMS is reporting /24 and I am getting warnings about the incorrect netmask. Polled with agent.

Also I have two APC UPS units polled via SNMP proxy that are reporting /0 netmask when they have a /24 netmask. Again am getting netmask warnings logged. All other SNMP devices polled via the proxy are reporting correct netmask.

Have done a check on the DB and there are no issues detected.

Netmask was correct in 2.0-M2, and I have tried doing a full configuration poll since upgrade.

Thanks, Brett.

I have found a couple of problems with ping after the upgrade from 2.0-M2 to 2.0-M3.

One is the ping agent not working, but have got around that by reversing the IP addresses in the conf file.

The second is the ICMP proxy is not working. I would assume it is related to the same issue as the ping agent?

Thanks, Brett.

I fixed ping subagent. You can try to replace ping.cpp and ping.h in src/agent/subagents/ping with attached ones and recompile agent. As side effect, it should also work correctly with IPv6 targets (IPv6 addresses in config should be enclosed in square brackets).

Best regards,
Victor

ping.cpp

ping.h

To the "PING subagent" issue:
I made a network dump and saw the IP addresses the subagent uses are in reverse order:
set in agent config: 172.16.50.1
used from PING subagent: 1.50.16.172

I hope you have a short solution, I can fix in the source code.

1. I do a configuration poll on the netxms server node. SNMP is connected to and values read.
2. I try to do a SNMP walk from netxms on the local netxms server node and it fails or gives no results back.
3. If I then do another configuration poll on the netxms server node SNMP fails and isn't found.

I know SNMP works as I can SNMP walk with a separate program without any issues. I tried deleting the netxms server node and having it recreate it self but that did not help. Could it be something to do with the new IPv6 interfaces in this new version?

Basically, SNMP is working for all other nodes except the node netxms server is installed on.

         UINT32 destAddr = htonl(addr.getAddressV4() | ~(0xFFFFFFFF << addr.getMaskBits()));

to

         UINT32 destAddr = htonl(addr.getAddressV4() | ~(0xFFFFFFFF << (32 - addr.getMaskBits())));

and recompile server.

Best regards,
Victor

[ping]
DefaultPacketSize = 46
PacketRate = 4
Target = 172.16.50.1:host.doamin.intern