NetXMS Support Forum

See responses below.  I forgot to mention this is a timescaledb so im not sure if that is what is causing my issues




\d alarms;

Table "public.alarms"
       Column       |          Type           | Collation | Nullable | Default
--------------------+-------------------------+-----------+----------+---------
alarm_id           | integer                 |           | not null |
parent_alarm_id    | integer                 |           | not null |
alarm_state        | integer                 |           | not null |
hd_state           | integer                 |           | not null |
hd_ref             | character varying(63)   |           |          |
creation_time      | integer                 |           | not null |
last_change_time   | integer                 |           | not null |
rule_guid          | character varying(36)   |           |          |
source_object_id   | integer                 |           | not null |
zone_uin           | integer                 |           | not null |
source_event_code  | integer                 |           | not null |
source_event_id    | bigint                  |           | not null |
dci_id             | integer                 |           | not null |
message            | character varying(2000) |           |          |
original_severity  | integer                 |           | not null |
current_severity   | integer                 |           | not null |
repeat_count       | integer                 |           | not null |
alarm_key          | character varying(255)  |           |          |
ack_by             | integer                 |           | not null |
resolved_by        | integer                 |           | not null |
term_by            | integer                 |           | not null |
timeout            | integer                 |           | not null |
timeout_event      | integer                 |           | not null |
ack_timeout        | integer                 |           | not null |
alarm_category_ids | character varying(255)  |           |          |
event_tags         | character varying(2000) |           |          |
rca_script_name    | character varying(255)  |           |          |
impact             | character varying(1000) |           |          |
Indexes:
    "alarms_pkey" PRIMARY KEY, btree (alarm_id, source_object_id, creation_time)
    "alarms_creation_time_idx" btree (creation_time DESC)
    "alarms_source_object_id_creation_time_idx" btree (source_object_id, creation_time DESC)
Number of child tables: 1989 (Use \d+ to list them.)




select count(*) from alarms;
count
-------
     0
(1 row)


Did not find any relation named "old_alarms".
netxms_db=#


netxms_db-# \d event_log;
                          Table "public.event_log"
      Column      |          Type           | Collation | Nullable | Default
------------------+-------------------------+-----------+----------+---------
event_id         | bigint                  |           | not null |
event_code       | integer                 |           | not null |
event_timestamp  | integer                 |           | not null |
origin           | integer                 |           | not null |
origin_timestamp | integer                 |           | not null |
event_source     | integer                 |           | not null |
zone_uin         | integer                 |           | not null |
dci_id           | integer                 |           | not null |
event_severity   | integer                 |           | not null |
event_message    | character varying(2000) |           |          |
event_tags       | character varying(2000) |           |          |
root_event_id    | bigint                  |           | not null |
raw_data         | text                    |           |          |
Indexes:
    "event_log_pkey" PRIMARY KEY, btree (event_id, event_source, event_timestamp)
    "event_log_event_source_event_timestamp_idx" btree (event_source, event_timestamp DESC)
    "idx_event_log_event_timestamp" btree (event_timestamp)
    "idx_event_log_root_id" btree (root_event_id) WHERE root_event_id > 0
    "idx_event_log_source" btree (event_source)
Number of child tables: 17943 (Use \d+ to list them.)


netxms_db=# \d  event_log_v35_2;
Did not find any relation named "event_log_v35_2".

Currently we have 3.3.323  and I am getting the following error when trying to upgrade

Upgrading database...
Upgrading from version 35.1 to 35.2
SQL query failed (25P02 ERROR:  current transaction is aborted, commands ignored until end of transaction block):
DROP INDEX IF EXISTS idx_event_log_event_timestamp
Rolling back last stage due to upgrade errors...

I normally build from source and install.  Do I need to install a previous version in order to upgrade to 3.6 or should this process still work jumping that many versions

Thanks,

Gary

Just an update I downloaded CentOS 7 and was able to successfully build and install using the latest netxms source and postgres 12.    However i did run into  an initial issues when trying to nxdb init

Unable to connect to database netxms_db@localhost as netxms (FATAL:  Ident authentication failed for user "netxms") i believe this is because the pg_hba.conf does not have an entry for netxms after changing to the following i was able to initialize via nxbmgr init

local   all             postgres                                trust
# IPv4 local connections:
host    netxms_db   netxms         127.0.0.1/32             md5
# IPv6 local connections:
host    netxms_db   netxms         ::1/128                  md5



using pqsql i created a db of netxms_db and  user netxms with password of netxms for testing   


hope this helps

Are you able to connect to either database using the cli tools such as mysql  or psql for postgres ?   Did you make sure to add the correct db driver username and credentials in the netxms config?  You also would have to have configured netxms to build those drivers   --with-pgsql  --with-mysql --with-sqlite in orderian to initialize the databases.  Hope any of that helps. I have never had any issues as long as every thing builds correctly and I am able to connect to the DB with my configured username and password from the cli tools then i'm usually good to go.

Looking for a function the will enable the check box   "Use ICMP ping on primary IP address to determine node status"  I searched in the docs an could not find anything.



Thanks,

Gary

Has any one done any comparison of the two ?   When would one be recommend over the other.  I have noticed at times with Timescale I often get disconnects from nxmc  when im doing a lot at once.  I have never had these issues with mysql or postgres.


Thanks,

Gary

Would be nice to be able to edit multiple objects in gui.  I know this can be done via scripting but it would be so nice to be able to multi select multiple nodes right click and change any of those attributes such as polling, map appearance, proxy .. etc    Or be able to add nodes to a container and make global changes to each node in the container. 


Thanks for an awesome product.

Please see  attached image.  I have tried two different NMS solutions that seem to have no problems finding the associations.  Maybe this should be a feature suggestion but is there a way to force netxms to use the FDB when building topology  for those switches that may not fully be compatiable with lldp.  I have seen several switch that in some way do not fully implement lldp  and this is just enough to prevent a topology in netxms.  But  those switches show all connections no problem in the FDB database. 


The attached is a topology map from opennms.  Netxms will never show the Desktop connection and only show switch connections between netxms-test and moxa pos switch  if I rename interfaces to match lldplocal port.

Not sure netxms would monitor all you need.  Have you tried https://www.elastichq.org/features.html   it does have an api that you could probly incorporate into netxms if really needed

if you are using deployment tools then you should already have everything you need to deploy.  It shouldn't take to much to copy a folder to the machine and create a shortcute to nxmc.exe to the users desktop. I have used PDQDeploy to do the exact same thing without issues

Victor,

I have been going back and forth with them trying to have them fix the inconsistencies to no avail see their response below.

We have looked into the SNMP frames to find which OID NetXMS is polling from EDR-810 during auto-topology. We found out that modifying the subtype in LLDP does not fix the topology issue of NetXMS in our test. However, after discussing with PM, making EDR-810 compatible of NetXMS would be not in the specs and would be a CV request. In addition, we found that NetXMS polls dot1dBasePortIfIndex from EDR-810. However, the EDR-810 does not support dot1dBase-MIB. We have confirmed the auto topology can be done for EDR-810 with FW v5.6 in MXView

Is the fact that the switch does not support dot1dbaseportindex really matter.  Looking at the trial version of MXView  it doesnt seem to do anything more than what Netxms does and pretty much queries the same mibs except dot1dbase.  But it is able to find the topology no problem.   If this is somthing im just going to have to deal with. Is it possible to provide me with an example of a HOOK i can use to try and change the names of the interfaces after a poll. I have renamed the interfaces manually and the topology does seem to be found but it is very inconsistant every other poll will not find connections and it will never find a netxms agent that is connected to any port on the switch. However it does list the connections via info -> lldp but the port number is always off by one.  For example the agent will be connected in port 4 but lldp lists it as port 3.  So i do think there is some netxms lldp related issues going on.


Thanks

Victor,

Is there anything I can do to provide a workaround to this on the netxms side of things? can I force the naming of these interfaces to match what is being sent by lldp.  I was given a newer firmware that was supposed to fix a known issues but I am still not seeing the topology in Netxms .  However The trial version of the vendors NMS works just fine.  But would rather not pay for an inferior product that doesnt have half the features of Netxms.

Victor,

I attached the ifxtables in the previous message. Another thing I noticed is the FDB table does not list an interface. Is this also a result of the behavior of the switch. 

"MAC Address","Port","Interface","VLAN","Node","Type"
"CC:4E:24:BC:D1:2C","9","

• ","1","TMC-ICX-CORE","dynamic"
  "AC:CC:8E:AC:01:80","2","
• ","1","172.27.x.x","dynamic"
  "00:40:8C:E6:D6:37","9","
• ","1","172.27.x.x","dynamic"
  "00:04:81:02:1E:EB","10","
• ","1","","dynamic"
  "00:04:81:02:1F:9B","10","
• ","1","","dynamic"
  "00:04:81:04:1B:DB","1","
• ","1","","dynamic"
  "00:04:81:04:1D:AF","10","
• ","1","","dynamic"
  "00:04:81:04:4F:19","10","
• ","1","","dynamic"
  "00:14:7B:20:20:8C","9","
• ","1","","dynamic"

Here you go. At this point I dont think this has anything to do with Netxms but any help would be much appreciated.  I have also emailed the switch support since the switch is clearly  advertising values that are not even configured in the tables.  I have a feeling this maybe on purpose since this particular vendor has a paid version of their own NMS
.


Thanks,

Gary 

I have attached the logs.  I think i know whats going on and it seems to be on the switch side but not 100% sure.  For each node that has been fully polled the interfaces all show as

ETHERNET PORT 1
.
.
ETHERNET PORT 10

However the lldptables from the switch show completely different port names

PORT1
.
.
PORT8
SFP-1GLXLC-T
SFP-1GLXLC-T

I can only get the topology to work if I uses alias's and SNMP SET the alias to match the lldp port name.  So setting port 9 and 10 to SFP-1GLXLC-T  on both switches will allow the connections to be found.  But I really don't want to script this up just to get things working and  if the SFP is changed it could end up being a different port name.  I would think Netxms would be able to just use the port index and FDB but maybe since LLDP is enabled that is not being used.   One other thing is the switched is a L3/L2 but is only on layer2 mode but is still discovered by netxms as being a router so the dot1qtpfdbtable does not return any entries only dot1dfdtable returns. Hope this helps and thank you for your time.

Gary