NetXMS Support Forum

Hi,

looks like you have older version of NetXMS (3.4.178) somewhere in the path as well. Make sure that you don't have old version installed from sources for example.

Best regards,
Victor

Hi,

looks like call to Cipher.getInstance("AES/CBC/PKCS5Padding") sometimes is very slow. To test it, please create the following Java file:


import javax.crypto.Cipher;

class CipherTest
{
   public static final void main(String[] args)
   {
      long start = System.currentTimeMillis();
      try
      {
         Cipher.getInstance("AES/CBC/PKCS5Padding");
      }
      catch(Exception e)
      {
         e.printStackTrace();
      }
      long elapsed = System.currentTimeMillis() - start;
      System.out.println("Elapsed time " + elapsed + " milliseconds");
   }
}


call it CipherTest.java, then compile as

javac CipherTest.java


and run as

java CipherTest


It should print elapsed time for cipher initialization. On my machine it is around 60 milliseconds. If it will take many seconds during some run then this is problem with local JVM (likely with entropy collection, maybe with /dev/random or /dev/urandom).

Best regards,
Victor

Там где агент падает - поставьте пожалуйста еще -dbg пакеты (netxms-agent-dbg, netxms-dbdrv-sqlite-dbg, и т.д.) - тогда дамп будет сильно более полезным.

По поводу дескрипторов - пришлите пожалуйста вывод lsof -p для процесса агента.

Hi,

are those nodes in default zone or in remote zones? If yes and zone proxy cannot resolve host name then server will not attempt to resolve it directly unless server configuration parameter Objects.Nodes.FallbackToLocalResolver set to true. This change was introduced in version 3.5.

Best regards,
Victor

Hi!

Looks like Java side issue. Could you please try to do the following:

1. Download nxshell-3.8.250.jar and the following files:
https://repo1.maven.org/maven2/ch/qos/logback/logback-core/1.2.3/logback-core-1.2.3.jar
https://repo1.maven.org/maven2/ch/qos/logback/logback-classic/1.2.3/logback-classic-1.2.3.jar
into same directory.
2. Create file logback.xml in the same directory with the following content:

<configuration>
   <appender name="Console" class="ch.qos.logback.core.ConsoleAppender">
      <layout class="ch.qos.logback.classic.PatternLayout">
         <Pattern>%d{HH:mm:ss.SSS} [%t] %-5level %logger{36} - %msg%n</Pattern>
      </layout>
   </appender>
   <root level="debug">
      <appender-ref ref="Console"/>
   </root>
</configuration>

3. Run nxshell as following:

java -Dnetxms.server=127.0.0.1 -Dnetxms.login=admin -Dnetxms.password=your_password -cp logback-classic-1.2.3.jar:logback-core-1.2.3.jar:.:nxshell-3.8.250.jar org.netxms.Shell

until it hangs and send me console output.

Best regards,
Victor

Hi,

when you do search for IP address, server will find node with that IP address, and show you MAC address of interface where this IP address is configured. You get specific MAC because you are looking for specific IP. When looking for a node by it's ID you have to somehow decide what interface to use. You can use primary IP address for example to determine what interface and MAC address to show.

Best regards,
Victor

Hi,

please verify with command show flags in server debug console if flag AF_RESOLVE_IP_FOR_EACH_STATUS_POLL is actually set.

Best regards,
Victor

Hi all!

We just published next patch release for NetXMS 3.8 - version 3.8.350 (3.8.251 for Linux agents). Changes since previous patch release:

- Added notification channel driver for SNMP traps
- Event processing macro %K (alarm key) also works in rules following one that triggered alarm
- Improved Data Collection Editor and Policy Editor usability
- DCI instance used for custom attribute lookup when expanding %{} macro
- Fixed sorting for "Object query" dashboard element
- Fixed memory leak in server related to "Object query" dashboard element
- Fixed issues:
        NX-2022 (Rack with custom height is incorrectly displayed)
        NX-2028 (Use instance name for custom attribute search when expanding %{} macro)
        NX-2029 (Line Chart General Time Period keeps reverting to "Back from now" when trying to use "Fixed time frame" option)
        NX-2031 (HTTP proxy parameter configured in nxmc properties has no effect)

Best regards,
Victor

Hi,

it does, but very limited. You can configure cluster object and register virtual IPs - NetXMS will then monitor if virtual IP address is moved from one node to another and if it is present. It cannot monitor resources without associated virtual IPs.

Best regards,
Victor

Hi,

are you running server on Windows?

Best regards,
Victor

You can actually try upgrade to 3.8 - we did change framework version 3.7, so that may help. And 3.2 is quite old anyway, lot of other fixes and improvements were made since its release.

Best regards,
Victor

Hi,

you can use any database present on that server then, probably "master" could be a good choice as it always exists.

Best regards,
Victor

It is considered down, but status for the interface is set to "Minor" instead of "Critical" if operational state is DORMANT and expected state is UP. If expected state is DOWN and interface is in DORMANT state, then status will be "Normal" because interface is down in a sense that it does not pass operational packets. I don't think there should be expected state DORMANT (as far as I understand it it is more of an exception state that expected to be solved, so it is kind of pointless to expect interface to be in that state normally).

Best regards,
Victor

Hi all!

New patch release for NetXMS 3.8 (version 3.8.226) is just published. Changed since previous release:

- Lower memory footprint of NXSL scripts
- Correct handling of agent policies by external subagents
- Added attribute "tunnel" to NXSL class "Node"
- Server runs configuration poll on node after agent upgrade
- File manager subagent does not register same root multiple times
- Fixed refresh issues in Object Details view
- Fixed visualization issues in switch port view
- Fixed incorrect root object filtering in dashboard elements "Event Monitor", "SNMP Trap Monitor", and "Syslog Monitor"
- Fixed issues:
        NX-2014 (Create NXSL property on node object that gives reference to each type of proxy)
        NX-2024 (Add "Max Wait Time" to Server.EventProcessors Internal Parameter Table)

Best regards,
Victor

Hi,

you could choose OID right before doing actual SNMP request in script DCI - so no extra SNMP requests will be done. Like this:

switch($node->vendor)
{
   case "Mikrotik":
      switch($node->productName)
      {
         case "60ghz": oid = ".1.3.6.1.4.1.14988.1.1.1.8.1.6.1";
      }
      break;
   case "Ubiquity":
      switch($node->productName)
      {
         case "AirMAX": oid = ".1.3.6.1.4.1.41112.1.4.1.1.4.1";
         case "AirFiber": oid = ".1.3.6.1.4.1.41112.1.3.1.1.5.1";
      }
      break;
}

if (oid == null)
   return null;  // OID was not selected, null will mark DCI as unsupported

snmp = $node->createSNMPTransport();
if (snmp == null)
   abort;
return SNMPGetValue(snmp, oid);


This of course relies on correctly set vendor and product name values. This should be the case for Mikrotik devices, but may not be for Ubiquity - you should double check.

Alternative approach could be probing for different OIDs in configuration poll hook andd setting correct OID as node's custom attribute, and then use it in script DCI. For example:

HOOK::ConfigurationPoll:

oids = %( ".1.3.6.1.4.1.41112.1.4.1.1.4.1", ".1.3.6.1.4.1.41112.1.3.1.1.5.1", ".1.3.6.1.4.1.14988.1.1.1.8.1.6.1" );
snmp = $node->createSNMPTransport();
if (snmp != null)
{
   for(oid : oids)
   {
      if (SNMPGetValue(snmp, oid) != null)  // You may use more sophisticated checks here if needed
      {
          selectedOID = oid;
          break;
      }
   }
}
SetCustomAttribute($node, "WirelessCenterFrequencyOID", selectedOID);


and script DCI:

oid = GetCustomAttribute($node, "WirelessCenterFrequencyOID");
if (oid == null)
   return null;  // No OID selected, mark as unsupported
snmp = $node->createSNMPTransport();
if (snmp == null)
   abort;
return SNMPGetValue(snmp, oid);


Best regards,
Victor