NetXMS Support Forum

Hi,

version 4.1 attempts to detect SSH availability during configuration poll. Most likely other switches just don't report failed SSH login attempts, or they have valid credentials. If you don't need SSH access to problematic switches you can disable SSH polling in node properties on "Polling" page.

Best regards,
Victor

Hi,

it's possible to some degree. Few options here:

1. Create circular status map - you can define root object, and status map will show sub-objects and their statuses as sunburst diagram. However, drilldown action is hardcoded and will open list of active alarms for selected object.

2. Create network map - you can place any object on a map, and as drilldown you can set other map or dashboard. This will not be sunburst diagram however - although you can represent objects in some logical layout.

Best regards,
Victor

Not each output of powershell begins with empty line, only this specific command does. You can filter output further, probably from powershell itself as well, but I don't know how (not using it). However, command line pipe should work as well (I assume you are interested in line with version number):


ExternalParameterShellExec = ExchangePatchNumber:pwsh -Command { Get-Command Exsetup.exe | ForEach {$_.FileVersionInfo} } | find "ExSetup.exe"


Best regards,
Victor

Hi,

I just fixed this issue, fix will be included into next patch release. Current workaround is to press refresh if overview is not shown for too long.

Best regards,
Victor

Hi,

can you check log on proxy agent around time when SYS_SSH_UNREACHABLE generated? Make sure you have debug level 6 or more for tag "ssh".

Best regards,
Victor

Yes, only first line is taken as value of external parameter. You have to format output in your script so it return required value in first line.

Best regards,
Victor

Hi,

you can try to manually add column tt_row_number to table dct_threshold_instances (integer not null, set it to 0 if you have any records in dct_threshold_instances table), then you can try to run upgrade with -X option (it will ignore upgrade errors and continue). One of next upgrade procedures will try to rename row_number to tt_row_number, so you should end up with correct schema.
Make sure you have database snapshot or backup before trying this, and watch for possible other errors, because with -X DB manager would not stop at them anymore.

Best regards,
Victor

Hi,

you should use $$ to insert $ into command, as it is start of command argument ($1, $2, etc.).

Best regards,
Victor

Hi all!

We just published patch release for version 4.1 - 4.1.333. Changes since previous release:

- Added support for package type "zip"
- Fixed incorrect label colors on dashboards after migration from 4.0
- Minimum number of bytes required for MAC address search reduced to two
- Reading of ipAddrTable and/or ipAddressTable during configuration poll can be disabled via custom attributes
- Fixed server crash caused by incorrect value of configuration parameter ICMP.PingSize
- Multiple fixes and improvements in new UI
- Fixed issues:
        NX-2089 (Bundle prunmgr.exe with web-ui installer)
        NX-2250 (Show VLAN information on interface overview page)
        NX-2258 (No context menu on area of interactive dashboard graphs)

Best regards,
Victor

Is it mean for authenticating NetXMS users, or for use with SSH connections from NetXMS to devices? Because latter is already implemented for some time.

Hi,

yes, it can be done, but it will take some time to move all strings to message files. I will update on progress.

Best regards,
Victor

For L2 maps server consider any node without bridge capability to be end node. Bridge capability determined by attempting to access BRIDGE-MIB during configuration poll (specifically OIDs .1.3.6.1.2.1.17.1.1.0 and .1.3.6.1.2.1.17.1.2.0).

Best regards,
Victor

I've made changes to disable usage of ipAddrTable and ipAddressTable by setting to true attributes snmp.ignore.ipAddrTable and snmp.ignore.ipAddressTable. Those changes will be included into upcoming patch release.

Best regards,
Victor

Hi,

if data in IP-MIB is incorrect that it definitely can cause strange results. Do those devices provide correct address information under .1.3.6.1.2.1.4.20.1.1 (ipAddrTable)? If yes, I can made small change that will allow to disable usage of .1.3.6.1.2.1.4.20.1.1 (ipAddressTable) for specific devices.

Best regards,
Victor

Hello!

This is download link for current message files: https://cloud.radensolutions.com/s/zrYw4jDxcfTbKFG.
However, we are currently in process of moving to new UI, so it could be more productive to work on new UI when most of functions will be transferred. I expect most work to be done during May and early June. We will try to re-use translations from legacy UI as much as possible though.
Also, please note that some texts in UI are not moved to language files yet and are hard-coded as English texts. This is also work in progress.

Best regards,
Victor