NetXMS Forum

I use NXSL scripting to do a lot of custom event posting using PostEvent. I'd like to begin to add some more information to these alarms. Is there any way to use NXSL to add comments to an alarm?

So I did some further digging and discovered that the issue was of my own doing. I had a syntax error in the script. Correcting that resolved my own problem.

I'm using the nxevent binary to insert a custom alert onto the console. Everything looks like it really should be working. The event shows up in the Event Monitor but an alarm does not show up in the Alarm Browser. I'm running this command manually:

/usr/bin/nxevent -u admin -P adminPassword 10.42.1.31 '100002' 'clientName' 'businessUnit' 'ALERT' 'Alarm ID 1890000  Alarm goes here!' 'Critical' 'Custom.alarm.key'

All the information and command line arguments are correct. The event processing policy - id 100002 - calls a script named NXEvent::Raw.

I see these entries in the netxmsd.log file when I enter the command:

[13-Aug-2015 15:19:26.613] [DEBUG] [CLSN-1] RecvNXCPMessageEx failed (0)
[13-Aug-2015 15:19:26.613] [DEBUG] *actions* Executing action 3 (NXEVENT::Raw) of type NXSL SCRIPT
[13-Aug-2015 15:19:26.613] [DEBUG] *actions* Executing NXSL script "NXEVENT::Raw"
[13-Aug-2015 15:19:26.614] [DEBUG] ExecuteActionScript(): Cannot find script NXEVENT::Raw

NXEVENT::Raw is certainly there. Is there anything else I can do to troubleshoot?

I have a wireless device sending syslog to NetXMS. I see the syslogs coming in via tcpdump (I've cut and pasted a sample output below). However, the logs do not seem to be stored in the db.  The device itself - 'aruba-controller' - is added as a node in NetXMS. I've searched for this hostname and I've searched for all logs with a severity of 'debug' for the timeframe, and I cannot find the logs. Am I missing a configuration somewhere?

root@event-nmgt:/home/vwiebe# tcpdump -i em1 src 192.168.10.53 and port 514 -A -v
tcpdump: listening on em1, link-type EN10MB (Ethernet), capture size 65535 bytes
08:51:00.735117 IP (tos 0x0, ttl 64, id 0, offset 0, flags [DF], proto UDP (17), length 162)
    aruba-controller.wilm.sevone.com.syslog > event-nmgt.sevone.com.syslog: SYSLOG, length: 134
    Facility local1 (17), Severity debug (7)
    Msg: Apr  3 08:51:06 2015 aruba-controller lldp[3704]: <235002> <DBUG> <aruba-controller 192.168.10.53>  LLDP Recv PKT at ingress 8448
E.....@.@.....
5..
.......R_<143>Apr  3 08:51:06 2015 aruba-controller lldp[3704]: <235002> <DBUG> <aruba-controller 192.168.10.53>  LLDP Recv PKT at ingress 8448

Makes sense to me. Thanks!

I'll dig further with my sysadmin. Thanks!

Aha. Apologies. Here is the output:

(gdb) run
Starting program: /opt/netxms/bin/nxmibc --help
warning: Could not load shared library symbols for linux-vdso.so.1.
Do you need "set solib-search-path" or "set sysroot"?

Program received signal SIGSEGV, Segmentation fault.
0x00000000006612a0 in strcmp@@GLIBC_2.2.5 ()
(gdb) bt
#0  0x00000000006612a0 in strcmp@@GLIBC_2.2.5 ()
#1  0x00007ffff7de7356 in elf_machine_rela (sym=0x400af0, skip_ifunc=<optimized out>, reloc_addr_arg=0x7ffff6ef1950, version=<optimized out>, map=0x7ffff7fe0000, reloc=<optimized out>) at ../sysdeps/x86_64/dl-machine.h:302
#2  elf_dynamic_do_Rela (skip_ifunc=<optimized out>, lazy=<optimized out>, nrelative=<optimized out>, relsize=<optimized out>, reladdr=<optimized out>, map=0x7ffff7fe0000) at do-rel.h:146
#3  _dl_relocate_object (scope=0x7ffff7fe0358, reloc_mode=<optimized out>, consider_profiling=consider_profiling@entry=0) at dl-reloc.c:265
#4  0x00007ffff7dde3e0 in dl_main (phdr=<optimized out>, phnum=<optimized out>, user_entry=<optimized out>, auxv=0x7ffff7fdb740) at rtld.c:2282
#5  0x00007ffff7defb18 in _dl_sysdep_start (start_argptr=start_argptr@entry=0x7fffffffe1f0, dl_main=dl_main@entry=0x7ffff7ddcb60 <dl_main>) at ../elf/dl-sysdep.c:244
#6  0x00007ffff7ddfd45 in _dl_start_final (arg=0x7fffffffe1f0) at rtld.c:337
#7  _dl_start (arg=0x7fffffffe1f0) at rtld.c:563
#8  0x00007ffff7ddc598 in _start () from /lib64/ld-linux-x86-64.so.2
#9  0x0000000000000002 in ?? ()
#10 0x00007fffffffe470 in ?? ()
#11 0x00007fffffffe487 in ?? ()
#12 0x0000000000000000 in ?? ()
(gdb)

Hi Victor, sure thing. Here's the output:

[root@ITBox:/opt/netxms/bin] [S1V: 5.4.RC3.0] [16:38:18] $ gdb ./nxmibc
GNU gdb (Gentoo 7.4 p1) 7.4
Copyright (C) 2012 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later http://gnu.org/licenses/gpl.html
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.  Type "show copying"
and "show warranty" for details.
This GDB was configured as "x86_64-pc-linux-gnu".
For bug reporting instructions, please see:
http://bugs.gentoo.org/...
Reading symbols from /opt/netxms/bin/nxmibc...done.
(gdb) run
Starting program: /opt/netxms/bin/nxmibc
warning: Could not load shared library symbols for linux-vdso.so.1.
Do you need "set solib-search-path" or "set sysroot"?

Program received signal SIGSEGV, Segmentation fault.
0x00000000006612a0 in strcmp@@GLIBC_2.2.5 ()
(gdb)

I'm attempting to install version 1.2.16 on Gentoo from source. Almost everything works, with the exception of nxmibc, which segfaults whenever it is run. I've tried running a simple 'nxmibc --help' manually and still see a Segfault. Has anyone come across an issue like this?

Is it possible to run an external, shell script from an NXSL script and return the output as a variable?

Here is some more information as to what I'm trying to accomplish.

I am using NetXMS as an Event Management station. We're using it very well, in fact, and we're very happy with it. So far we are receiving events from our internal network via snmp trap and syslog, and I am also using nxevent to push custom events from other outside sources. When a trap is received from a node that netxms does not have in its configuration we even have automation to auto-create the node without snmp capabilities.

Now we are being asked to receive events from external networks that have overlapping/conflicting ip networks (it's all private networking in the 192.168.0.0 range). For right or wrong there are conflicts beyond my control.

I am thinking that using Zones might be the best way to do this (if there is a better method I'm not too proud to change my plans). So after going through the documentation it looks like I need to do a few things:

1. Install a remote nxagent to act as a proxy
2. Add the nxagent as a managed node in my primary netxms console
3. Create a zone with the nxagent as proxy

So I suppose my questions are thus:

1. Do I send the traps for the new conflicting network devices to the nxagent or the console?
2. Knowing that I will still need to create the node on the fly using CreateNode, is it possible to create the Node inside a specific zone?

Thanks for the help!

Is there anyway to use CreateNode to create a node inside a specific zone?

Interestingly, I would like to receive traps and show them as alarms for unmanaged nodes. Is there anyway to make this a toggle, such as "Allow Trap For Unmanaged Node"? Is there a way to stuff an Alarm in using an external script?

And I think I just found my own answer with the UnmanageObject function.

Thanks for the help Victor! Great product.

Booya! That did it. I now have a series of auto-created node's based on trap. Sweet!

After creating the node using CreateNode, is there a way to programatically disable polling? I won't have direct access from my netxms platform to the devices sending traps.

Thanks again! My event browser is looking awesome.

Hi Victor!

Yes, that fixed my immediate issue. The traps are certainly creating alarms now.

My trap sender is an NMS that will send traps on behalf of other devices; ultimately, it is the 'remote device' that I'd like to have referenced as "$node". I've been digging through the documentation and what I think I need to do is create a node on the fly upon trap reception based on one of the OID value's. I think the workflow would work like this:

1. Receive Trap
2. Identify Remote Node from MIB
3. Use FindNodeObject to see if the proper node exists
4. If yes, script a finagling and use PostEvent
5. If no, create a new object using CreateNode, and then modify the new alarm

Does this sound feasible to you? Would you be able to provide me with a one-liner as to how CreateNode works and the parameters it needs?

Thanks again!

Victor W

Hello everyone. I am in need of some help placing SNMP Traps onto the Alarm Browser. I've browsed through the documentation and the forums and am still struggling.

I have configured an external NMS system to send traps to NetXMS. The traps are being received: they appear in the SNMP Trap Log and the SNMP Trap Monitor.

I've followed the instructions at another post - https://www.netxms.org/forum/configuration/snmp-trap-configuration/msg13657/#msg13657 - but haven't had any luck with it. I have created five Event Configuration items:

TRAP_RAW
TRAP_INFO
TRAP_EMERGENCY
TRAP_CRITICAL
TRAP_CLOSE

The trap OID is .1.3.6.1.4.1.27207.2.2.1.0.1. I've configured the SNMP Trap Configuration to use event "TRAP_RAW" upon receiving an trap with this OID.

I have an Event Processing Policy which calls this script when a TRAP_RAW trap is received:

if ($event->parameters[3] == alert)
{
    switch($event->parameters[2])
    {
        case 1:
            evt = "TRAP_CRITICAL";
            break;
        case 2:
            evt = "TRAP_EMERGENCY";
            break;
        case 3:
            evt = "TRAP_EMERGENCY";
            break;
        case 4:
            evt = "TRAP_EMERGENCY";
            break;
        case 5:
            evt = "TRAP_EMERGENCY";
            break;
        case 6:
            evt = "TRAP_INFO";
            break;
        case 7:
            evt = "TRAP_INFO";
            break;
        case 8:
            evt = "TRAP_INFO";
            break;
    }

    PostEvent($node,evt,null,$event->parameters[7]);
}
else
{
    PostEvent($node, "TRAP_CLOSE");
}

I also have two additional Event Processing Policies for creating the alarm and clearing it. However, no alarms are ever created in the Alarm Browser.

In summary:

I see the traps coming in via tcpdump.
The traps appear in the SNMP Trap Log
The traps appear in the SNMP Trap Monitor
Nothing appears in the Event Monitor
Nothing appears in the Event Log
Alarms are not generated

I'm at a loss as to how to troubleshoot at this point. Would anyone be able to lend a hand?

Just to cover as many bases as I can think of, here is a copy of the incoming trap from tcpdump

09:44:53.154160 IP itbox.49128 > event.snmp-trap:  C= V2Trap(1134)  system.sysUpTime.0=3322126 S:1.1.4.1.0=E:27207.2.2.1.0.1 E:27207.2.1.1.1.1.2=0 E:27207.2.1.1.1.1.3="alert" E:27207.2.1.1.1.1.4=0 E:27207.2.1.1.1.1.5=1400852702 E:27207.2.1.1.1.1.6="" E:27207.2.1.1.1.1.7="Threshold triggered -- switch0.fl2-closet0.wilm's Gi2/0/1's Availability: 0.00 Percent < 100 Percent averaged over 10.00 minutes" E:27207.2.1.1.1.1.8="ITBOX" E:27207.2.1.1.1.1.9=1 E:27207.2.1.1.1.1.10=192.168.10.40 E:27207.2.1.1.1.1.11="switch0.fl2-closet0.wilm" E:27207.2.1.1.1.1.12=1453 E:27207.2.1.1.1.1.13=192.168.10.18 E:27207.2.1.1.2.1.1="Critical Uplinks Availability - switch0.fl2-closet0.wilm - Gi2/0/1" E:27207.2.1.1.2.1.2="" E:27207.2.1.1.2.1.3=0 E:27207.2.1.1.2.1.4="" E:27207.2.1.1.2.1.5=23 E:27207.2.1.1.2.1.6="Uplink ports" E:27207.2.1.1.2.1.7="" E:27207.2.1.1.1.1.14="SNMP" E:27207.2.1.1.1.1.15=1 E:27207.2.1.1.1.1.16="SNMP Poller" E:27207.2.1.1.1.1.17="Gi2/0/1" E:27207.2.1.1.1.1.18=17716 E:27207.2.1.1.1.1.19="core0.wilm gi6/1" E:27207.2.1.1.1.1.20="s1_interfaceavailability" E:27207.2.1.1.1.1.21=120537 E:27207.2.1.1.1.1.22="Availability" E:27207.2.1.1.2.1.8=213743 E:27207.2.1.1.2.1.9=0 E:27207.2.1.1.2.1.10="0.00" E:27207.2.1.1.2.1.11="100" E:27207.2.1.1.2.1.12="Percent" E:27207.2.1.1.2.1.13=2 E:27207.2.1.1.2.1.14="10.00"