NetXMS Support Forum

I've noticed that the same trap has been thrown at extreme devices. Analyzing the logs of this device the following message appears:

Login failed through SNMPv3 - not in life time

According to extreme documentation this seems to be a problem on the NMS server, as per the following link:

https://extremeportal.force.com/ExtrArticleDetail?an=000077945

Any hints on what could be done?

Thanks,

Hi Victor,

Thanks for uploading files. I realized however that maybe there are some terms where there are no matching keys in the files. Probably from the latest updates. Wouldn't there be a way to include the missing keys with standard text to add them to the translation?

As for the changes, could they be adopted in the legacy version and also in the new UI in the future?

Hello,

Analyzing the packages I got the error as shown in the attached image:
The SNMP credentials are correct, on the devices the SNMP server address was pointed to an SNMP proxy.


Thanks,

Hi,

I would like to help with the Portuguese translation, since I see there are many terms that no longer have translation in the tool.

If someone sends the current version of the files that haven't been completely translated I can start this work.

Hello,
I only managed to make the errors stop on the device by checking the option to disable the use of SNMP for all polls. However, this makes it difficult to poll the device and look up status.
The option to prevent SNMP configuration change is also checked.

Could anyone help? thanks

Hey guys,

On a Huawei switch we configure snmpv3 for polling and sending traps, the polling and sending traps normally occurs except that the switch sends from time to time a series of traps related to authentication failure, approximately every 10 min.

SNMP_AUTH_FAILURE .1.3.6.1.6.3.1.1.5.5
The switch is in a zone and the snmp trap configuration on the equipment points to the proxy.

I believe some of the switc polls are causing this issue, probably with some invalid credential.

Thank you for your help,

A great improvement will make it easy. Thanks for the answer.

How to initialize subgent for mongodb? Documentation is unclear.
The agent was installed via the repository, but the subagent does not appear to be present. Is it necessary to compile it manually?

Thanks,

Hi!
Would you like to know how to apply settings to send messages via google chat? thanks in advance.

I am unable to operate UPS monitoring with the netxms agent. Through the device software I use the megatec protocol and it works but I can't get it via an agent
Here is my setup:

ConfigIncludeDir = C:\NetXMS\etc\nxagentd.conf.d
LogFile = {syslog}
# DebugLevel = 6
FileStore = C:\NetXMS\var
SubAgent = winperf.nsm
SubAgent = ups.nsm

[UPS]
Device = 0:"COM1:":MEGATEC

This is the error message:
Cannot establish communication with device #0 "MEGATEC-COM1:"

thanks for the help

I'm using NetXMS 3.2.400

Quote from: Victor Kirhenshtein on February 06, 2020, 02:47:32 PM
Hi,

what exact console version you are using? Is it desktop or web based?

Best regards,
Victor

Hi Victor,
I am using version 3.1.300, the error is both Web and desktop. The program freezes and I have to close and restart it.


Thank you for your attention,

Good morning everyone,

The NetXMS console since it was changed to version 3, has been freezing and the program crashes when I place a specific dashboard for display.
I realized that it always takes time to load values from the VMGR subagent that I implanted to get values from ESXi hosts.

I find this error message in the logs:

!ENTRY org.netxms.ui.eclipse.console 4 0 2020-02-03 09:47:20.868
!MESSAGE Exception in ConsoleJob
!STACK 0
org.netxms.client.NXCException: Invalid DCI ID
   at org.netxms.client.NXCSession.waitForRCC(NXCSession.java:1762)
   at org.netxms.client.NXCSession.waitForRCC(NXCSession.java:1731)
   at org.netxms.client.NXCSession.getCollectedDataInternal(NXCSession.java:4608)
   at org.netxms.client.NXCSession.getCollectedData(NXCSession.java:4656)
   at org.netxms.ui.eclipse.dashboard.widgets.ComparisonChartElement$3.runInternal(ComparisonChartElement.java:116)
   at org.netxms.ui.eclipse.jobs.ConsoleJob.run(ConsoleJob.java:98)
   at org.eclipse.core.internal.jobs.Worker.run(Worker.java:63)

Thanks,

The issue was resolved by simply updating the configuration pool.
New Issue:
On an ESXi host via esx, the agent can connect and collect data. On a host VCenter, connection through Active Directory user credentials with connection type VPX fails.
The same parameters entered work with the virsh tool.

Thank you for your help,

I would like to receive parameters from ESXi hosts. From the parameters given in the NetXMS documentation I thought it was possible to receive this data from an agent installed on another machine, so I did it as follows:
1 - I installed libvirt on netxms server with ESX driver support
2 - I installed the netxms-agent-vmgr subagent
3 - I set up with the correct sections in agent [vmgr],
SubAgent = vmgr.nsm
[vmgr]
host = myhost
[vmgr: myhost]
Url = esx: // some_user @ ip_server /?no_verify = 1
User = some_user
Password = somepassword
4 - I can access esx host from netxms server from virsh tool.
5 - The agent shows no errors and successfully loads the configuration.

The problem is: When I create a DCI with some of the VMGR.xxxxxx metrics, the result is always an error.
Example: VMGR.Host.FreeMemory (myhost) always returns <<ERROR>>

Thank you for your help,

Quote from: Victor Kirhenshtein on July 29, 2019, 10:00:50 AM
What version you are using?

I'm using 2.2.16 version