NetXMS Support Forum

Hello!
I just checked MIB compiler source, and it actually should handle DISPLAY-HINT clause. Could you please provide full MIB file trhat cause error? Also, what NetXMS version you are using?

Best regards,
Victor

Quote from: gdodd on October 05, 2021, 04:10:21 AM
- Fixed bug in centralized agent upgrade on Windows

Does that mean once server and agent are on 3.9.298, future centralized agent upgrades should work? Or should it work with just server on 3.9.298?

I am trying to upgrade Windows agents 3.9.280 from Linux server 3.9.298 and get the "Agent's version doesn't match..." error message.

Unfortunately most issues with file transfer and upgrade in 3.9 were agent related, so you have to upgrade agent somehow. Once both server and agent are on 3.9.298, further upgrades should work fine. We will discuss internally if we can do something server-side to allow upgrade of previous versions.

Best regards,
Victor

Hi all!

We just published new patch release for version 3.9 - 3.9.298. Changes since previous patch release:

- Improved file delivery policy editor
- Fixed bug in centralized agent upgrade on Windows
- New endpoint /events in web API for sending events
- Filtering by primary host name in web API endpoint /objects
- Fixed session agent crash on 32 bit Windows systems
- Fixed issues:
        NX-2129 (File delivery policy on Windows Agent causing .part0 to be added to the filename)
        NX-2130 (If file in file delivery policy is updated new version is appended to the old one instead of replacing it)
        NX-2133 (Set subagent column as instance on table Agent.SubAgents)
        NX-2134 (Agent crashes if invalid owner or group set in file delivery policy)

Best regards,
Victor

Hi all!

We just published new patch release for version 3.9 - 3.9.280. Changes since previous patch release:

- External audit logging via LEEF protocol
- Improved process table in Windows agent
- Windows service manager in GUI
- Process manager in GUI
- Optimized working with ICMP
- Object alias shown in geo map tooltips
- Geo map tooltips work in web UI
- Added option to hide other objects in object geolocation view
- Object names can be shown on geo maps
- Fixed issues with Chassis/Rack placement properties page save
- Fixed bug in standard deviation calculation in ping subagent
- Fixed incorrect limit on dashboard element span in UI property page
- Fixed file transfer issue when upgrading agents from Package Manager
- Fixed issues:
        NX-2115 (Allow adding image in chassis properties without selecting a rack)
        NX-2118 (Changes in ICMP statistic collection period are not applied until server restart)
        NX-2119 (Agent table "ICMP.Targets" should have "Standard deviation" column)
        NX-2121 (Status map view should show node aliases)
        NX-2124 (Log parser hangs on lines longer than 4095 characters)
        NX-2125 (Server incorrectly reads IP network mask from VMWare ESXi and vCenter)

Best regards,
Victor

Hi,

few notes here. First, you don't need both session agent and user agent - use agent has all the functionality of session agent.
And you can select "Install user support application" in unattended installer by adding to installer command line option

/MERGETASKS="useragent"

Best regards,
Victor

Try to set debug level to 7 for tag ncd.msteams - you should see more detailed diagnostic in the log then.

Best regards,
Victor

Hi,

\ is an escape character in NXSL string, so for actually passing \ to regex processor, you can escape it, like this: "^\\.1\\.3\\.6".

In simple cases you can use like instead of regexp matching. For example, to match all OIDs starting with .1.3.6.1.2.1 you can use condition

if (oid like ".1.3.6.1.2.1.*")
{
   /* match, dio something */
}


Best regards,
Victor

Hi!

So initially zone is without proxy? Try to set this node as proxy for the zone, then run full configuration poll on it. Also please try to set debug level 6 on server for tag poll.*, and check server log after running status and configuration poll.

Best regards,
Victor

Hi,

most likely you'll have to look at NXSL extensions, data collection related functions are in src/server/core/dc_nxsl.cpp. Look for F_GetDCIValues - it is implementation of getting history for single value DCIs, and GetDCIValueImpl - it will give you idea how to return table value as NXSL object. Then you will need code to unpack table values. You can take a look at src/server/core/session.cpp, method ClientSession::getCollectedDataFromDB - you will be interested in code part around call Table::createFromPackedXML.

Best regards,
Victor

Hi!

There are few bugs that contribute to this problem. First is incorrect data reported by vCenter in ipAddressTable:

.1.3.6.1.2.1.4.34.1.5.1.4.172.17.128.20 [OBJECT IDENTIFIER] = .1.3

It should be either .0.0 or valid OID from ipAddressPrefixTable (.1.3.6.1.2.1.4.32). Combined with bug in NetXMS server that does not check for validity of this OID and just using last element (it should have done scan of ipAddressPrefixTable instead, as in .0.0 OID case) it produced /3 network mask (because in valid OID from ipAddressPrefixTable last element is prefix length).

Unfortunately just fixing this issue in NetXMS server is not enough, because ipAddressPrefixTable reported by vCenter is incorrect as well. OID

.1.3.6.1.2.1.4.32.1.6.2.1.4.255.255.127.0.24 [INTEGER] = 2

should have been

.1.3.6.1.2.1.4.32.1.6.2.1.4.172.17.128.0.24 [INTEGER] = 2

(with correct prefix as part of OID). I've checked on my vCenter - it returns exactly this incorrect value (255.255.127.0) no matter what actual subnet is.

I was able to add a workaround in server code for such situation - now server also attempts to scan inetCidrRouteTable for local routes and deduce correct prefix from there. It seems to work on my vCenter. This change will be included into next patch release.

Best regards,
Victor

Hi,

this supposed to be fixed in 3.9.235. Could you please provide screenshot of "Interfaces" tab for such device and event details for "duplicate MAC" event?

Best regards,
Victor

Тогда можно оставить использование transformation, просто скрипт заменить на вызов библиотечного скрипта в форме

return script_name::function();

В вызванном скрипте будет доступна переменная $dci.

$node - объект ноды с которой происходит сбор данных (https://www.netxms.org/documentation/nxsl-latest/#class-node)
$targetObject - объект ноды для которой происходит сбор данных (будет то-же что и $node если у DCI не выставлен source node)

В $ARGS (и в $1, $2, ...) будут параметры если в DCI скрипт указан со скобками.

Hi,

does NetXMS server has SNMP access to this Cisco device? Because normally it should read all configured addresses via SNMP and not attempt to create separate nodes for each known IP address.

If for some reason device is not accessible via SNMP, you can block secondary address in discovery filter. You can set discovery filter to script, and use script like this:

if ($node->ipAddr == "1.2.3.4")
   return false;
return true;


you can also use hook script Hook::AcceptNewNode for this, just add the following line to it:


return $ipAddr != "1.2.3.4";


(of course replace 1.2.3.4 with actual IP address).

Best regards,
Victor

Hi,

it depends on resources available. Developer that was working on it left the company, and currently we do not have any iOS developer onboard (and they are quite expensive as well). Ultimate goal is to have iOS client though.

Best regards,
Victor