NetXMS Support Forum

What are you using to import  is it  https://github.com/tomaskir/NetXMS-csv-importer  if so im not sure it works with newer versions of Netxms

I noticed UBNT devices do not provide acess to SNMP dot1Q briding information so topology polls always fail.  Is it possibel for us to hook into Topolgy poll to create our own custom poll ?  UBNT devices use bridge-utils  so all info can be displayed using brctl  I would like to be able port 1 is ath0 and port 2 is eth0 so I can figure out what devices are connected remotely but i would love to have it displayed in netxms topology.   Thanks

WA# brctl showmacs br1
port no mac addr                is local?       ageing timer
  1     00:04:81:02:b8:62       no                 0.23
  2     00:0c:42:6f:63:17       no                32.17
  2     00:0c:42:6f:63:1a       no                35.92
  2     00:0c:42:95:ec:03       no                17.08
  2     00:0c:42:9d:d9:44       no                50.58
  2     00:0c:42:9f:a6:e1       no                32.11
  2     00:0c:42:9f:d0:31       no                56.66
  2     00:0c:42:b5:b8:6b       no                31.38
  2     00:0c:42:b6:2e:0d       no                17.76
  2     00:0c:42:ba:f4:df       no                15.84
  2     00:15:6d:65:54:27       no                 0.20
  2     00:15:6d:67:34:ff       no                10.74
  2     00:15:6d:69:67:ee       no                38.89
  2     00:15:6d:69:67:fd       no                 2.65
  2     00:15:6d:69:68:06       no                50.58
  2     00:15:6d:69:68:83       no                17.76
  2     00:15:6d:69:68:89       no                32.11
  2     00:15:6d:69:68:8e       no                33.64
  2     00:15:6d:6b:4b:93       no                51.55
  2     00:15:6d:6b:4c:8a       no                17.55
  2     00:15:6d:6b:4c:c9       no                32.17
  2     00:15:6d:6b:4c:cc       no                15.84
  2     00:15:6d:6b:4d:2d       no                 3.66
  2     00:15:6d:6b:4d:51       no                33.60
  2     00:15:6d:6b:56:2f       no                58.58
  2     00:15:6d:6b:8c:e3       no                56.66
  2     00:15:6d:6b:ff:21       no                 2.71
  2     00:15:6d:6b:ff:29       no                13.69
  2     00:15:6d:6b:ff:2a       no                47.96
  2     00:15:6d:6b:ff:39       no                 7.23
  2     00:15:6d:6c:22:cc       no                 7.01
  2     00:15:6d:6c:22:cd       no                 7.05
  2     00:15:6d:6c:22:ce       no                29.67
  2     00:15:6d:6c:22:d5       no                15.25
  2     00:15:6d:6c:22:db       no                35.93
  2     00:15:6d:6c:b1:e0       no                 7.00
  2     00:15:6d:6c:b1:f2       no                 0.81
  2     00:15:6d:6c:b1:fd       no                 1.95
  2     00:15:6d:6c:b1:fe       no                47.49
  2     4c:5e:0c:7f:cf:36       no                 1.95
  2     4c:5e:0c:84:70:e5       no                35.93
  2     4c:5e:0c:84:cd:3a       no                10.74
  2     4c:5e:0c:85:05:43       no                 7.01
  2     4c:5e:0c:85:67:1d       no                26.69
  2     4c:5e:0c:86:7e:f6       no                47.49
  2     4c:5e:0c:87:07:12       no                 0.81
  2     4c:5e:0c:8e:6a:62       no                 7.00
  1     70:a7:41:48:9e:f5       yes                0.00
  1     70:a7:41:48:a7:f5       no                 0.80
  2     70:a7:41:49:9e:f5       yes                0.00
  3     72:a7:41:49:9e:f5       yes                0.00
  2     d4:ca:6d:9c:f0:1e       no                 2.71
  2     d4:ca:6d:a1:3d:de       no                17.94
  2     fc:96:43:6e:56:01       no                 0.01

recently moved my netxms install to a new server and received the following when initializing the db 

WARNING:  column type "character varying" used for "idata_value" does not follow best practices
HINT:  Use datatype TEXT instead.
WARNING:  column type "character varying" used for "raw_value" does not follow best practices
HINT:  Use datatype TEXT instead.
WARNING:  column type "character varying" used for "idata_value" does not follow best practices
HINT:  Use datatype TEXT instead.
WARNING:  column type "character varying" used for "raw_value" does not follow best practices
HINT:  Use datatype TEXT instead.
WARNING:  column type "character varying" used for "idata_value" does not follow best practices
HINT:  Use datatype TEXT instead.
WARNING:  column type "character varying" used for "raw_value" does not follow best practices
HINT:  Use datatype TEXT instead.
WARNING:  column type "character varying" used for "idata_value" does not follow best practices
HINT:  Use datatype TEXT instead.
WARNING:  column type "character varying" used for "raw_value" does not follow best practices
HINT:  Use datatype TEXT instead.
WARNING:  column type "character varying" used for "idata_value" does not follow best practices
HINT:  Use datatype TEXT instead.
WARNING:  column type "character varying" used for "raw_value" does not follow best practices
HINT:  Use datatype TEXT instead.
WARNING:  column type "character varying" used for "idata_value" does not follow best practices
HINT:  Use datatype TEXT instead.
WARNING:  column type "character varying" used for "raw_value" does not follow best practices
HINT:  Use datatype TEXT instead.
WARNING:  column type "character varying" used for "event_message" does not follow best practices
HINT:  Use datatype TEXT instead.
WARNING:  column type "character varying" used for "event_tags" does not follow best practices
HINT:  Use datatype TEXT instead.
WARNING:  column type "character varying" used for "notification_channel" does not follow best practices
HINT:  Use datatype TEXT instead.
WARNING:  column type "character varying" used for "recipient" does not follow best practices
HINT:  Use datatype TEXT instead.
WARNING:  column type "character varying" used for "subject" does not follow best practices
HINT:  Use datatype TEXT instead.
WARNING:  column type "character varying" used for "message" does not follow best practices
HINT:  Use datatype TEXT instead.
WARNING:  column type "character varying" used for "action_name" does not follow best practices
HINT:  Use datatype TEXT instead.
WARNING:  column type "character varying" used for "channel_name" does not follow best practices
HINT:  Use datatype TEXT instead.
WARNING:  column type "character varying" used for "recipient" does not follow best practices
HINT:  Use datatype TEXT instead.
WARNING:  column type "character varying" used for "subject" does not follow best practices
HINT:  Use datatype TEXT instead.
WARNING:  column type "character varying" used for "action_data" does not follow best practices
HINT:  Use datatype TEXT instead.
WARNING:  column type "character varying" used for "hostname" does not follow best practices
HINT:  Use datatype TEXT instead.
WARNING:  column type "character varying" used for "msg_tag" does not follow best practices
HINT:  Use datatype TEXT instead.
WARNING:  column type "character varying" used for "ip_addr" does not follow best practices
HINT:  Use datatype TEXT instead.
WARNING:  column type "character varying" used for "trap_oid" does not follow best practices
HINT:  Use datatype TEXT instead.
WARNING:  column type "character varying" used for "log_name" does not follow best practices
HINT:  Use datatype TEXT instead.
WARNING:  column type "character varying" used for "event_source" does not follow best practices
HINT:  Use datatype TEXT instead.
WARNING:  column type "character varying" used for "message" does not follow best practices
HINT:  Use datatype TEXT instead.

Everything initialized ok but just thought this was strange.  

ok so I was able to to achieve what I wanted with the following its hacky  but if works. How do I go about terminating this alarm ? I want to terminate the alarm as soon as the time expires.


ts = ReadPersistentStorage("ts_".$node->name);

if(ts == NULL){
/* create initial timestamp and event*/
WritePersistentStorage("ts_".$node->name,$event->timestamp);
WritePersistentStorage($node->name,1);
return;
}
/* if within time range of 10min check storage */
if (time() - ts <=600){
 
events = ReadPersistentStorage($node->name);
WritePersistentStorage($node->name,events+1);
if (events!=NULL ){


if (events >=5){
return true;
}
}

}else{


/* if time is over 10min reset storage values for timestamp and event*/
WritePersistentStorage($node->name, NULL);
WritePersistentStorage("ts_".$node->name, NULL);



}

I will give it a try myself and if I can not figure it out I will circle back and ask for assistance.  Thank you for pointing me in the right direction.

 Is there any way to set a threshold for received traps or alarms ? We have a few switches where the connected devices sometimes will have a faulty power supply and will randomly cause the device to constantly reboot causing the port to go up and down generating  SNMP_LINK_UP  SNMP_LINK_DOWN  traps.  I would like to generate an alarm/notification if there are say 10 or more back to back up down events received within 5min to notify me that the port is flapping. I think this would be useful to be able to do the same for certain alarms due to some alarms can trigger then rearm on the next check and can sometimes be easily missed.

Thanks.. 

the following worked for me  all published messages did go to the recipient as a topic 
Hostname = x.x.x.x
Port = 1883
Login = ""
Password = ""

Looked in the docs and did not see any information on setting up the driver. Is there any other documentation on setting this up ?  I am assuming we can now publish to a mqtt topic which is somthing I have been waiting for. 

What os are you using ?  Looks like the database is postgres.  Are you able to login via psql 

It it possible to get  access to Netxms raw data for Grafana queries ? I am currently using timescale and I would like to show metrics on total number of devices total number of critical alarms and so forth.  This more of a dummy board for the higher ups so at  a glance they can gauge an over all health status. It does not look like custom queries can be performed.  But it would be a nice addition if we can query data we are interested in assuming we know the schema of the netxms database 


Thanks 

I have had the issue with several different versions of Netxms.  Its frustrating after spending larges amounts to time creating a map layout then to save and when you open it back up at a later time about half of the items are clumped up and all pushed to the up left corner 

Yes,  That's correct I was trying to get the hierarchy from a single core switch interface.  I was trying to see if that was possible but it looks like I would have to do  some sort of recursive function and step through each peer and its interfaces.  Any pointers would be much apperciated.


Thanks

Is it possible to filter by interface on topology map ?  We have 48 Port core switch that has around 20 devices connected to each port so a topology map is pretty much a big blob of devices that span out from the core.  I would like to be able just include say interface Gi1/0/1 and whatever devices that span out from that particular interface.



Thanks

Got it makes sense... Thank you so much   I have been using netxms for over 4 years and I am still amazed how flexible this software is.

Is it possible to show critical status only when the node is actually down and not responding to ICMP or SNMP  ?  I have several switches that I have listed on maps and status maps that show critical only because a single port is down I would much rather show Minor or Major when a port goes down since for me  a port down is really not critical  if the switch still has connectivity. I have tried setting the status calculation on all ports to fixed major thinking that  would help but when the switch does go down it now will only show major and not critical


Thanks