NetXMS Support Forum

It would be nice to be able to have checks that would show or alert on duplex mismatches on links between devices. Like wise it would also be beneficial to have indicators on the map the shows differences between interfaces that are 10-100M or 1-10GB etc  or a difference in line width if the links are 100m vs 10GB 

Why does netxms continually try snmp communities when the community is already known ?  I have a few different community strings and netxms will still try all others even though the correct string is already configured  in the node settings. This causes issues with switches that have security measures to block snmp if failed snmp attemps are reached. As well as causing bloated logs with auth failed attempts.

I usually build from source and have no problems but for some reason my server is now dead after installing 4.5.4 from source

Details
Debian 11
Postgres 13 with timescale db extension 2.10

database was upgraded via nxdbmgr successfully

running with -D 9  gives nothing of value last lines are 

Network device driver JUNIPER loaded successfully 
Network device driver NETSCREEN loaded successfully 
Segmentation fault

What are the limits for PS ?  are there in guidelines of how many entries you can store and is this stored in a flat file on the local file system or do these also get put into the same database. 

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

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

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.  

 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.. 

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. 

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 

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

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

Is it possible to graph the ICMP packet loss and Response times shown in Object Details -> Overview      I have tried adding the internal ICMP ping to{instance}:packet loss  and last response time to my Data Collection Configuration but they both just error out.



Thanks

current version is 4.1.377   We have a layer2 redundant loop in our network and needed to break the loop by shutting down one of the switch interfaces temporarily. However netxms never updates the topology to reflect the broken loop even after two days its still shows the link connected between the two switches when interface details on both switches shows the interface as down.  I would expect the link to be removed after a topology poll was completed showing the loop broken in the middle where the interfaces are down. Is this normal or do I have to do something to force an update.


Thanks

Does netxms now support netflow ?   looking at the build options for  4.1.377 i see   --with-flow-collector  is this just experimental ?


Thanks

Trying to build from source fails with the following

OS: Debian Buster
here is my config     ./configure --with-server --with-client --with-snmp --with-pgsql --with-agent --with-client-proxy --with-vmgr




Making all in nxcproxy
make[3]: Entering directory '/home/gmonk/netxms-4.1.333/src/nxcproxy'
/usr/bin/perl ../../tools/mc.pl messages.mc
  CXX      nxcproxy-listener.o
  CXX      nxcproxy-nxcproxy.o
nxcproxy.cpp: In function 'int main(int, char**)':
nxcproxy.cpp:372:25: error: 'CP_ACP' was not declared in this scope
     MultiByteToWideChar(CP_ACP, MB_PRECOMPOSED, optarg, -1, g_configFile, MAX_PATH);
                         ^~~~~~
nxcproxy.cpp:372:25: note: suggested alternative: 'P_ALL'
     MultiByteToWideChar(CP_ACP, MB_PRECOMPOSED, optarg, -1, g_configFile, MAX_PATH);
                         ^~~~~~
                         P_ALL
nxcproxy.cpp:372:33: error: 'MB_PRECOMPOSED' was not declared in this scope
     MultiByteToWideChar(CP_ACP, MB_PRECOMPOSED, optarg, -1, g_configFile, MAX_PATH);
                                 ^~~~~~~~~~~~~~
nxcproxy.cpp:372:33: note: suggested alternative: 'MSGRECV_CLOSED'
     MultiByteToWideChar(CP_ACP, MB_PRECOMPOSED, optarg, -1, g_configFile, MAX_PATH);
                                 ^~~~~~~~~~~~~~
                                 MSGRECV_CLOSED
nxcproxy.cpp:372:5: error: 'MultiByteToWideChar' was not declared in this scope
     MultiByteToWideChar(CP_ACP, MB_PRECOMPOSED, optarg, -1, g_configFile, MAX_PATH);
     ^~~~~~~~~~~~~~~~~~~
nxcproxy.cpp:372:5: note: suggested alternative: 'MultiByteToWideCharSysLocale'
     MultiByteToWideChar(CP_ACP, MB_PRECOMPOSED, optarg, -1, g_configFile, MAX_PATH);
     ^~~~~~~~~~~~~~~~~~~
     MultiByteToWideCharSysLocale
make[3]: *** [Makefile:627: nxcproxy-nxcproxy.o] Error 1
make[3]: *** Waiting for unfinished jobs....
make[3]: Leaving directory '/home/gmonk/netxms-4.1.333/src/nxcproxy'
make[2]: *** [Makefile:467: all-recursive] Error 1
make[2]: Leaving directory '/home/gmonk/netxms-4.1.333/src'
make[1]: *** [Makefile:520: all-recursive] Error 1
make[1]: Leaving directory '/home/gmonk/netxms-4.1.333'
make: *** [Makefile:452: all] Error 2

I'm wondering if the back up process differs when using the Timescale extension ?  will nxdbmgr export capture the database + data or is there a better method.


Thanks

When trying to set the map background using Geographic Map the coordinates are way off.  I have even taken the coordinates listed in the World map and tried to use those but they are still  of compared to the world map.  The world map does match exactly what google maps shows so I know that is working.  Does the map background use a different coordinate system ?


Thanks