Hi all!
NetXMS version 2.0-M3 is out. This release contains significant internal changes mostly related to IPv6 support. Full change log is following:
- IPv6 support: communications, address information, topology
- New NXSL functions: gethostbyaddr, gethostbyname, md5, sha1, AgentReadList
- Added posibility to wakeup unmanaged node
- Instance discovery separated from configuration polls
- Instance discovery type "SNMP Walk - OIDs" sets instance name to OID value by default
- GPIO.PinState parameter in Raspberry Pi subagent
- Server housekeeping process runs once per day at fixed configurable time
- Server housekeeping process performance optimization
- Added driver for Qtech OLT switches
- New agent parameter FileSystem.Type(*)
- New agent parameters Net.Resolver.AddressByName(*) and Net.Resolver.NameByAddress(*)
- Fixed broken SNMP proxy functionality in agent
- Management console:
- Fixed broken popup menu actions on "Interfaces" tab
- Macro %USERNAME% can be used in object tools
- VLAN highlight on port selection in VLAN view
- "Use multipliers" option in DCI summary tables
- "Zoom to fit" action in network maps
- "Always fit layout to screen" option in network maps
- Last selected zoom level preserved on network map close
- Invisible dashboards and charts do not refresh itself automatically
- "Current" column in extended line chart legend
- Option to clone network maps
- Android console:
- Implemented feature #776 (WoL)
- Fixed issues: #690, #693, #702, #722, #725, #745, #750, #752, #755, #756, #757, #758, #759, #760, #763, #764, #765, #766, #767, #768, #769, #770, #771, #776, #778, #779, #782, #785, #787, #788, #789, #790, #792, #793
Best regards,
Victor
A problem with the upgrade from earlier versions (in Windows). The NetXMS Server installer (full, not minimal) doesn't upgrade the Management Console (although the Administration Console component is marked in the installer window). As a result, after installation I have 2.0-M3 Server and 2.0-M1 Console which are incompatible with each other.
Yes, there was a bug in installer. I just uploaded updated installer to the web site.
Best regards,
Victor
PING subagent:
Since upgrade from V2.0-M2 to V2.0-M3 I have a problem with PING subagent, with no change in the existing configuration I get now always Latency=10k (=timeout) (Icmp.AvgPingTime).
We use NetXMS on Linux x64 compiled from sources. PING subagent is on the NetXMS server.
Is there any known problem?
VPN-connector Subnets tab:
Since V2.0-M3 I can't open the Subnets tab of an existing VPN-connector anymore, I get the following error:
"The currently displayed page contains invalid values." in the Windows x64 Java Console.
Wake-on-LAN:
Now Wake-on-LAN is not working anymore (managed or unmanaged node).
Hi,
seems that all of those related to changes in IP address handling. Are you using IP addresses or DNS names in PING subagent?
Best regards,
Victor
We use IP addresses in PING subagent config:
[ping]
DefaultPacketSize = 46
PacketRate = 4
Target = 172.16.50.1:host.doamin.intern
I've fixed broken WoL. If you are building from sources you can replace line 993 in file src/server/core/interface.cpp from
UINT32 destAddr = htonl(addr.getAddressV4() | ~(0xFFFFFFFF << addr.getMaskBits()));
to
UINT32 destAddr = htonl(addr.getAddressV4() | ~(0xFFFFFFFF << (32 - addr.getMaskBits())));
and recompile server.
Best regards,
Victor
Thanks Victor, I can confirm that fixed the one with Wake-on-LAN (for managed and unmanaged nodes).
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.
Victor
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.
Hi,
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
Hi Victor. Thanks for the quick fix. PING subagent is working again! Thanks, Dani
Hi,
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.
Hi,
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.
We also see /0 netmasks instead of /24 on HP printers since upgrade from M2 to M3 (server on Linux x64 built from sources).
Quote from: djex81 on April 11, 2015, 02:20:22 AM
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.
Quote from: djex81 on April 13, 2015, 06:57:32 PM
Quote from: djex81 on April 11, 2015, 02:20:22 AM
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
Quote from: Victor Kirhenshtein on April 13, 2015, 09:14:15 PM
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.
Hi!
Quote from: brettmilfos on April 13, 2015, 12:36:19 AM
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
Quote from: djex81 on April 14, 2015, 03:04:57 AM
Quote from: Victor Kirhenshtein on April 13, 2015, 09:14:15 PM
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
Quote from: Victor Kirhenshtein on April 14, 2015, 09:39:27 AM
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.
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
Quote from: lindeamon on April 15, 2015, 02:00:51 PM
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
Quote from: Victor Kirhenshtein on April 14, 2015, 09:38:31 AM
Hi!
Quote from: brettmilfos on April 13, 2015, 12:36:19 AM
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,
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
Quote from: djex81 on April 13, 2015, 06:57:32 PM
Quote from: djex81 on April 11, 2015, 02:20:22 AM
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.
Hi!
Quote from: d-ray on April 16, 2015, 05:52:03 PM
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
Quote from: brettmilfos on April 13, 2015, 07:30:02 AM
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.
Thank you for IPv6!!
You have no idea how happy you made me with this :) :) :)