NetXMS Support Forum

Hi,

I'm sorry.
Thank you for pointing out.

Windows teaming + NLB unicast mode was the cause.

Because the NLB's unicast mode shares the same MAC address, packets arrive on each interface, so packets received by each interface were duplicated.

Since the connection destination switch was compatible with IGMP snooping, solving it by enabling IGMP snooping and making NLB from unicast mode to IGMP multicast.

Thanks for the advice.
Thank you very much.

Hi,

Thank you for your reply.

Captured using Wireshark, I tried SNMP trap test.
In the previous environment (teaming with two NIC, creating teams with each NIC, creating an interface), we received one, which is not duplicated.
In this environment (two teams using teaming, creating one team to create an interface), we received two cases and were duplicated.
What does "vcase" mean specifically?

Is such an environment assumed for NetXMS?
Is there any example in which there is no duplication in such an environment and it works normally?
Is there a solution?

Best regards,

Hi,

The server that runs NetXMS this time uses NIC teaming on Windows to create two interfaces with two NIC as one team.
The settings of the team are as follows.

Teening mode: Switch independent.
Load balancing mode: Address hash
Standby adapter: None (All adapters are active)

In this environment I found that SNMP traps are received in duplicate.
Disabling one side NIC in team properties in this environment will not duplicate.

Is there a solution?

Best regards,

Hi,

Thank you very much for your quick response any time.

Best regards,

Hi,

If you set the snmp trap destination to the IP added by TCP / IP property instead of the NetXMS server physical IP, the Event Moniter and SNMP Trap Monitor of the NetXMS server are displayed in duplicate.
Is this a specification?
Is there a solution?

OS: Windows 2012
NetXMS: Version 2.2.9

[Constitution]
192.168.0.11: Physical IP
192.168.0.1: added IP
* Set the SNMP trap destination to 192.168.0.1

Best regards,

Hi,

We upgraded to 2.2.9 and confirmed that the event configuration problem has been resolved.
Thank you very much.

Although it is set to replace the snmp trap value with% n in the event message, there is still a problem that garbage is added after the replaced string if the value contains a multibyte character string.

Example)

snmp trap parameter:
%2 -> The second value of snmp trap is a multibyte character string

Event message definition:
Error:%2

Event monitor messages:
"Error: multibyte character stringxx"
xx -> garbage

Best regards,

Hi,

When notifying with V2c and Inform, we confirmed with the manufacturer that it is notified with OID different from V1.

Sorry.
Thank you very much for pointing out.

Hi,

Thank you very much for your quick response.

Best regards,

Hi,

Thank you for the immediate reply.
Attach the setting and the log when actually generating the trap.

DiChangeValue.xml: Corresponding Event and SnmpTrap Configuration.
EventLog.csv: Event log when tasting in execution.
SnmpTrapLog.csv: Event log when tasting in execution.

I tested in the following order.
V1Trap -> DiChangeValue1 * OK *
V1Trap -> DiChangeValue 0 * OK *
V2Trap -> DiChangeValue1 * NG *
V2Trap -> DiChangeValue 0 * NG *
Inform -> DiChangeValue 1 * NG *
Inform -> DiChangeValue 0 * NG *

Thank you.

Hi,

Thank you for the immediate reply.
I am using MySQL 5.6.15.

Garbage was not added to the relevant data in the database.
I tried organizing the occurrence situation, so please refer to the attached PDF file.

Thank you.

Hello,

I am currently using version 2.2.6, but it is the same situation.
Currently multi-byte character strings are used in the event of snmptrap.

Although I do not know the effect of this case, if you use multibyte character string in event presentation of snmptrap, an unknown character string will be displayed after the value in the event monitor message of the management console.

Thank you.

Hello!

There is a device that can send traps of version v1 or v2c or Inform of snmp in the monitoring target and it is set to trap in the trap of the current v1, so it can receive without problems and an event has occurred.
If you trap this setting with v2c trap or Infom, you can receive but it will be SNMP_UNMATCH_TRAP.
Do I need to change the setting of NetXMS?

OS Version: Windows2012 (64bit)
NetXMS Version: 2.2.6

Thank you.

Hello,

If you register a message containing multibyte characters in the message in Event Configuration, a character string that is not registered at the end of the Message will be appended.
It is not added immediately after registration, but when Event Configuration is redisplayed, it can be confirmed that it is added with Event Configuration List or Edit Event Template.
This occurred from the previous version, but is there a workaround?

OS Version: Windows2012 (64bit)
NetXMS Version: 2.2.3

Thank you.

Hello!

I saw examines various, but not been able to find the cause.
Although has been added "_" at the beginning in the example of MSDN, or will become the same meaning?
We want your professor.

https://msdn.microsoft.com/library/z0kc8e3z.aspx

Best regards,
Med

Hi, Victor

Thank immediately reply.

I feel bad.
It is similarly occur in the following of the OS.
Windows Server 2003 R2
Windows Server 2008 R2
Windows Server 2012

Thank you.