So the value is set to 63 (The default).
.
We can't run nxmc on the Netxms server, or remote Unless we disable FIPs. We are using java-11.0.9-openjdk, which works fine on previous versions of netxms.
The error in the logfile is:
UnsatisfieLinkError:
no swt-pi4-gtk-4940r23 in java.library.path
Could not Open SWP library.
The term 'acknowledged' comes from the Legacy HP OpenView Operations Manager product. When an alarm is 'acknowledged' it is moved to 'history' (a table i the database). Alarms within the 'alarm history table' can be deleted or archived.
Terminating an alarm in NetXMS deletes the alarm from the active alarm browser. We have a requirement to retrieve a list of historical alarms for any and all nodes. If the alarm is 'terminated' within NetXMS it appears that the alarm is permanently removed from NetXMS.
The ability to retrieve historical alarms provides for anomaly analysis. It would be great if a 'Node_up" alarm was recived; acknowledged the "Node_down" alarm, and both were then moved to history; keeping the active alarm browser 'state based'. State based mean that only valid alarms (needing attention) are in the active alarm browser.
After acknowledgement of an alarm the alarm should move from the alarm browser to an event history table (in the database).
Moving the acknowledged alarm to an alarm history table creates a 'state based browser' where the only events that are 'real and actionable' are left in the alarm browser.
Event correlation can also move events to the event history table.
Search and query should be available for the event history table, into a 'alarm history browser'.
Running a RHEL 8.3 workstation / client in FIPS mode.
After upgrading to nxmc 3.8.250 (and 3.8.314) the nxmc Java GUI fails to connect to the remote NetXMS Server (also FIPS enabled).
Once the RHEL 8.3 workstation is booted without FIPS enabled, the Java GUI (nxmc) connects without issue.
Does one need the Java Crypto Extensions (JCE) in order for nxmc to run on a system with FIPS enabled?
