NetXMS Support Forum

Hi!

No. It saves windows configuration, perspectives, etc. on local workstation. It's probably possible to store Eclipse workspace on the server, but I didn't dig so deep into it yet.

Best regards,
Victor

Hi!

Agent policies deploy additional configuration files into config include directory. Location of that directory determined by parameter ConfigIncludeDir in nxagentd.conf. Default value for this parameter on Windows is "C:\nxagentd.conf.d". I just checked it, and it looks like agent installer does not add correct ConfigIncludeDir to nxagentd.conf and does not create appropriate directory. Currently you should do it manually on all systems where you wish to deploy configs via policies. I'll fix it till next release.

Best regards,
Victor

Hi!

So you wish to get something like "4.05 GB" instead of "4348654387"? Then your transformation script should looks like following:


($1 / 1024 / 1024 / 1024) . " GB"


And don't forget to change DCI type to "string"!

Best regards,
Victor

Hi!

It's not implemented yet. Added to feature requests.

Best regards,
Victor

It's not implemented yet.

Best regards,
Victor

See explanation here: https://www.netxms.org/forum/configuration/vlan-list/. In short, you cannot do much - only wait for appropriate driver to be developed. What devices do you have?

Best regards,
Victor

Hi!

For most devices, getting VLAN list requires reading of proprietary MIBs. In NetXMS 1.1.x, we introduce concept of network device drivers - server modules which handle vendor-specific things for network devices. Currently we only have drivers for Avaya (former Nortel) Ethernet switches and some Cisco switches and routers. You can check what driver is selected for a device by looking at "Driver" line on overview page. If "GENERIC" driver is selected for device, that means that there are no vendor-specific support for it.

Best regards,
Victor

It's still not implemented in Java console. Currently, the following important functionality are missing in Java console:

1. Logs (there are some work done on event and audit logs, but not complete);
2. Cluster configuration;
3. Network discovery configuration (but you still can configure it by changing server configuration variables directly);
4. "command" type object tools not working very well
5. Configuration export

But these gaps should be closed soon.

Best regards,
Victor

Hopefully near end of year. I still have major changes pending which I wish to implement until next stable branch.

Best regards,
Victor

Hi!

Version 1.1.4 will have integration with Jasper reports. Most likely in 1.1.4 there will be only integration mechanisms, and actual reports will come later.

Best regards,
Victor

Hi!

The only purpose of MIB compiler is to provide information for MIB browser. Presence or absence of a MIB does not affect data collection or trap processing. You only need MIB files (and need to compile them) if you wish to select SNMP objects from the tree in MIB browser. You can just enter OIDs in numerical format by hand (or take them from external MIB browser) - in that case MIBs in NetXMS are not needed.

Best regards,
Victor

Hi!

Script for this cold looks like following:


if ($1 == 1)
   return "yes";
if ($1 == 2)
   return "no";
return "neither_yes_or_no";


or, using switch operator:


switch($1)
{
   case 1:
      return "yes";
   case 2:
      return "no";
   default:
      return "neither_yes_or_no";
}


Best regards,
Victor

Java console is quite big in size, so I was not sure that it need to be included into server installer.
Standard Windows console will be fully replaced by Java console in the nearest future - the old console are still there only because some functions are still not implemented in Java version. As soon as they all be implemented, old console will be removed.

Best regards,
Victor

Depends on how do you monitor service status. If it is done via set of DCIs, then you can create additional DCI and in transformation script, read values of all service checking DCIs, count number of services in "down" state, and return that value. Then you will be able to set threshold on this DCI as usual.

Best regards,
Victor

Quote from: lindeamon on August 17, 2011, 09:28:23 AM
another thing regarding this solution:
i have configured a dci to find uptime through snmp and in the autoapply it told it to apply it on node that have snmp and do not have an agent.what i want to know is,once a node was applyed with this dci and i install an agent on it,will the template be automatically unbind ? if not,what is the right way do unbind it automatically ?

It all depends on your auto apply script. Template is applied when script returns true, and removed when script return false. So, if you wish template to be applied only on nodes with SNMP, but without NetXMS agent, and remoed from SNMP-only node when NetXMS agent installed on it, your auto apply script should looks like following:


return $node->isSNMP && !$node->isAgent;


Best regards,
Victor