NetXMS Support Forum

Hi Filipp,

Thanks for feedback.

I think one thing that could be implemented would be permissions to view the list of backups performed and another to export or view the backup content.

Regarding the XML error, is there a way to find out which section the error originates from? This makes it difficult to view the server logs over time.

Regarding the MIB error, yes, the date changes and when I compile via the GUI a new file is created, but it remains invalid, although no error is reported.

I've had to manually edit some MIB files before uploading them to the interface due to inconsistencies in their definitions, but I don't remember exactly which ones.

Another question: can the password be entered using `nxencpasswd`?

Thank you!

Thank you for your reply, Tatjana.

My mistake was because I had the following definition:

Module = webapi,Y
[WEBAPI]
...

Module = oxidized.nxm
[OXIZIDIZED]
...
The module declarations need to come before the configuration:

Module = webapi,Y
Module = oxidized.nxm

[WEBAPI]
...
[OXIDIZED]
...

This way, it works!

Thank you!

The Portuguese translation is much better now.
Congratulations to everyone!

Hi,

I'm trying to integrate NetXMS with Oxidized, but it seems the module isn't loading completely.

Adding the settings to the netxmsd.conf file results in the following message during system initialization:

[backup] Network device backup interface is not available
The URL and credential settings are all correct.

Thank you for your attention.

Server Initialization Errors

I'm encountering some errors during initialization. In principle, they don't prevent the system from functioning.

[snmp.mib] Failed to load MIB tree from /var/lib/netxms/netxms.cmib: Invalid or corrupted file data
The MIB compiles successfully on the frontend, but the MIB Explorer doesn't work. This message appears in the server logs during the MIB file compilation.

The second error is this:

[config] Configuration loading error: XML parser error in file ":memory:" at line 1 (no element found)
I can't identify the cause of this message, but it appears constantly.

Could someone offer some guidance on how to fix this?

Quote from: Victor Kirhenshtein on May 16, 2026, 05:23:24 PMJust closed issue 3023 (former NX-2821) - will be part of release 6.2.0.

Thank you, Victor!

Hi,

Sent an example

Hi, Victor.

First of all, thanks for the information, it's been a great help.

In a test, extreme returns values 1 and 7 separately for the respective OIDs, on all interfaces. However, in the NetXMS GUI, only UNKNOWN appears.

For Huawei, the OID mentioned does not return a MIB for the corresponding value. Apparently, there is no support for the standard 1.0.8802.1.1.1.1. Maybe with some specific Huawei MIB?
Here is the link that I believe has the supported MIBs:
https://support.huawei.com/hedex/hdx.do?docid=EDOC1100333029&id=EN-US_CONCEPT_0177099878

Hello Everyone,

Extreme
The scenario of a switch that responds "Yes" to the 802.1x NetXMS capability and the interfaces is activated is the option. Should the status of your ports not show anything other than "UNKNOWN" in the PAE State and Backend State columns, when a device is connected?

Huawei
Another problem with this capacity is that it seems to me that Huawei switches that also work with 802.1x enabled do not have this capacity detected in NetXMS.


I appreciate that you can inform me how to make this function work correctly in NetXMS.

Hi,

If you need to specify colors for each item, the hashmap can be used for this:
values.append(%{"name":"Item X", "value":10, "color": "#f5f5f5"});
return values;


Hi,

I would like to thank the NetXMS team for this update, several changes that are very good for the community.

Hi,
I think it would also be nice to have a configuration in the agent file that would allow the implementation of policies similar to "EnableActions".

+1 upvote for this vendor driver