NetXMS Support Forum

Attempting to update NetXMS from version 5.1.3 to version 5.2.
The legacy client seemed to work, but the (modern) client closes without errors immediately after logging in.
The client was tested on different computers.
System environment: Server on Windows Server 2016, client on Windows Server 2016 or Windows 10.
How do i determine what the problem is?

Regards
Peter

Hi.
I'm trying to use getValue on Octet-String within scripting, but it returns an empty string.

transport = $node->createSNMPTransport();
if (transport != null)
{
  testStr = transport->getValue(".1.3.6.1.4.1.4196.1.1.5.2.100.2.1.4.0");
  if (testStr == "") println "huh ?";
}

The MIB-Browser shows Type Hex-String with Value "00 00 02 00 00"
The DCI with DataType String and no conversion collects the same value.
The code from above returns an empty string   

NetXMS version 3.9.156

Any hints?

Thanks in advance.

In general I like this Feature. 

Since every source can theoretically generate events with ID 0-65535, it should be possible to include/exclude a combination of source, level and ID (similar to Logwatch).
For example: A search for ID 1 on www.eventid.net shows a list of many different sources with different level.

I tried some keywords, but with version 3.8.266 level or severity is not supported?

My first and most important step would be to exclude level 4 (information).
That would greatly relieve the database.

I'm looking forward to new filter options. 

Thanks in advance.

Hello.
While DCI-status is propagated to parent objects with the original status (warning, minor, major, critical),
the status for 'unexpected interface up' (major) or 'interface down' (minor) is always propagated with severity critical.

As the the interface in object tree shows the status critical, it may be intentionally.
But I would like to have the original interface severity propagated.

Status calculation is set to default.
Is there a setting to change this behavior?

Thanks in advance.

I set up an DCI with: origin-script, data type-string, polling intervall-300
The script returns possible node problems as string - amongst other things using the function GetDCIValueByDescription.
While NetXMS is constantly running, I get the last value (not empty as expected).
If the Core Server has been restarted, the function GetDCIValueByDescription returns (once) an empty string. 
I checked in the history that the last value was not empty.

I would call it a bug , observed in version 2.0-RC1 and 2.0-RC2.

Best Regards.

Hi @all.
Up to now we use 'The Dude' from Mikrotik - but development is stopped for years.
I am testing NetXMS from version 1.2.12 up to 2.0-RC1.
It is a nice software with great potential - functions like autodiscover, automatic map layout, usage of scripts, templates etc. are very welcome.
But I have also some ideas for improvements - here is my first

Automatic cyclic reconnect-attempt of the Management Console, if the connection is lost.
In an multi-user-environment all users have to reconnect manually if one user decides to restart the core server (ex: Windows Updates).
It would be also helpful when a short network problem occurs or if the server temporarily is too busy.

Best Regards.