Menu

Show posts

This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.

Show posts Menu

Topics - Victor Wiebe

#1
General Support / NXSL Script to add Alarm comment
September 25, 2015, 03:10:40 PM
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?
#2
General Support / Event Script issues
August 13, 2015, 10:24:00 PM
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?
#3
General Support / Not storing incoming syslogs
April 03, 2015, 03:53:45 PM
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
#4
General Support / nxmibc segfaulting
August 07, 2014, 06:31:26 PM
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?
#5
General Support / External Script from NXSL Script
August 07, 2014, 05:21:44 PM
Is it possible to run an external, shell script from an NXSL script and return the output as a variable?
#6
General Support / CreateNode and Zones
August 05, 2014, 07:47:38 PM
Is there anyway to use CreateNode to create a node inside a specific zone?
#7
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"