NetXMS Support Forum

Great I will work on stetting up a remote environment for you to access.


Thank you

we use a couple of different switches everthing works fine for these switches but it would be nice to have the port layout showing the ports status

https://www.siemens.com/global/en/products/automation/industrial-communication/ruggedcom.html

https://www.etherwan.com/us/products/ex78900x-series

What is generally needed to get new devices considered to be added as  driver ? 

It honestly just feels like the legacy interface with new icons and a sidebar. Aside from the navigation changing slightly I see no major benefit over the legacy interface at the moment. I often end up clicking on multiple icons to find what I am looking because I am used to just seeing "Templates" and not having to remember that "Templates" is now the icon that looks like three books.  Maybe its just me  getting old and not yet memorizing the icons   but I would be curious of what other are experiencing. 

After upgrading to 4.4.2 I noticed a new assets icon in the legacy interface but I cannot do anything with it. I am assuming this  new feature is only available for the new interface.  Are you going to phase out the old interface completely ?  I really don't prefer the new interface for several reasons but If  I have to switch I guess I can give it another try

It would be nice to be able to support SVG for maps and icons in order to have high resolution images that can scale. I think this would be good for dashboards as well instead of needing to have multiple colors of the same image to show status or errors the SVG can be directly edited to change the color or parameters

This feature would be awesome.. Thanks for all your hard work Victor.  Do we have the ability to sponsor this project on github ? If so I would gladly sponsor.


Thanks

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.