NetXMS Support Forum

Hi!

Currently it's not possible (beyond using print screen). I've added possibility to copy map content to clipboard as an image - it will be available in 1.2.15.

Best regards,
Victor

Hi!

There was a bug that prevents map status recalculation. I've just fixed it, next release will work as expected.

Best regards,
Victor

Hi!

Valid options are:

NF_DISABLE_DISCOVERY_POLL
NF_DISABLE_TOPOLOGY_POLL
NF_DISABLE_SNMP
NF_DISABLE_NXCP (to disable agent)
NF_DISABLE_ICMP
NF_FORCE_ENCRYPTION
NF_DISABLE_STATUS_POLL
NF_DISABLE_CONF_POLL
NF_DISABLE_ROUTE_POLL
NF_DISABLE_DATA_COLLECT

It's a bit mask, so you can combine multiple flags using bitwise OR operation, like this:


newFlags = node.getFlags() | Node.NF_DISABLE_SNMP | Node.NF_DISABLE_ICMP


Best regards,
Victor

Quote from: sperlm on July 07, 2014, 02:05:23 PM
3) yes, we have full backup of old DB with MySQL Admin which has very simple output which allows us to select parts to restore, there should not be problem with selecting and restoring parts of the DB
- the question is if we can get to migrate "just" hierarchy and network maps
- as these are dependent on IDs of discovered nodes this all boils down to - how to migrate discovered nodes
- everything else is nicely visible in the DB and can be "copy-pasted" many ways, there is no problem migrating scripts, events, rules, filters, templates...
- I would like to avoid migrating whole database for the purpose of "fresh" start as I think the old one might have too many unnecessary parts which caused troubles in the past

To migrate only nodes and containers you can try to import the following tables:

nodes
interfaces
network_services
vpn_connectors
vpn_connector_networks
containers
container_members
trusted_nodes
items
dc_tables
dc_table_columns
dct_column_names
dct_thresholds
dct_threshold_conditions
dci_schedules
raw_dci_values
thresholds
object_custom_attributes
object_properties

and all tables with names started with idata_ or tdata_.

Tricky part is object_properties and object_custom_attributes tables - you should delete any records with object_id not in nodes, interfaces, network_services, vpn_connectors, and containers tables.

Best regards,
Victor

Пакеты у нас есть, но они действительно не подписаны. Планируем решить эту проблему в недалеком будущем.

Hi!

Quote from: sperlm on July 04, 2014, 01:18:08 PM
1) how can I add options to apt-get install command to specify the configuration ? (is it needed ?)
--with-server --with-mysql (--with-agent) --prefix=/opt/netxms
(never added the --with-agent option, is it really needed ? always had the agent anyway)

It's not possible. Debian packages are pre-built binary packages. You select database option by installing appropriate package (netxms-server-mysql, netxms-server-pgsql, netxms-server-odbc, or netxms-server-oracle).

Quote from: sperlm on July 04, 2014, 01:18:08 PM
2) where can I get sample config files ? (I suppose these should be present in contrib directory, but there is no such)
- is copy from old installation safe option ? (without fear something was changed in newer versions)

It is not recommended to mix manually built binaries with pre-built binaries. It may work and may not work. But all necessary binaries should be included into debian packages. Samle configs seems to be missing from deb packages, it's just was forgotten. We will fix that.

Quote from: sperlm on July 04, 2014, 01:18:08 PM
3) is it safe to migrate only some DBs from old installation if we want to keep only list of found IPs with old IDs so that we can later import old network maps and hierarchy structure for example ?

You won't be able to do that without manually tweaking database or creating own migration tools. You can either migrate whole database and then clean it up or start from scratch. However, you can use Java API or nxshell to create a tool that will connect to old and new servers and migrate only data you need. Also, you can export event definitions, SNMP trap definitions, event processing rules, templates, and dashboards from old system and import into new system.

Quote from: sperlm on July 04, 2014, 01:18:08 PM
p.s. for testing purposes I need block all netxms comunication going outside, is it sufficient to block only outgoing ports 161 and 162 ?

For SNMP you have to block UDP port 161 (162 is for incoming traps, so server only listens on it), and TCP port 4700 for communications with agents. Also you might want to block outgoing ICMP echo requests.

Best regards,
Victor

Hi!

You have two options, and both requires script creation. One is to use nxshell script - there is an example of how to disable SNMP polling: http://wiki.netxms.org/wiki/Using_nxshell_to_automate_bulk_operations#Disable_SNMP_polling_for_node. Other option is to use NXSL script on server - you can use node enumeration example: http://wiki.netxms.org/wiki/Script_Example:_Enumerate_All_Nodes and add calls to methods enableAgent, enableConfigurationPolling, enableIcmp, enableSnmp, enableStatusPolling, enableTopologyPolling on node objects as needed. Each of these methods accepts true or false as parameter. For example, to disable agent for node you can call

n->enableAgent(false);

assuming that you have reference to node object in a variable n.

Best regards,
Victor

Исправил эту проблему, изменения войдут в релиз 1.2.15.

Hi!

Currently there are no other way to show dashboard without giving read access to nodes where data is collected, so your approach is absolutely right.

As for the script, it's actually a bug - in test mode $dci variable is not set. I'll fix it in the next release.

Best regards,
Victor

Actually it's an error in documentation. For server commands macros are expanded on server side, and you should use event processing macros (https://www.netxms.org/documentation/adminguide/event-processing.html#macros-for-event-processing).

It could be either condition object ID or name - if number is given server will interpret it as ID otherwise as name. If condition name is a number then you should use object ID

It's a bug that "Trusted nodes" is not shown for condition object. Just fixed it in development branch. As a workaround you can use legacy console to edit condition's trusted nodes list.

Best regards,
Victor

Hi!

It seems that rule named "Show alarm when node is down" has any event as a source (probably SYS_NODE_DOWN that was there originally was accidentally deleted) - that way it generates alarm on every event (including node status change events), thus triggering infinite loop of alarm creation. Add SYS_NODE_DOWN back and everything should be fine.

Best regards,
Victor

Hi!

Just test it, and it works as expected. Can you please show full script?

Best regards,
Victor

Можно, хотя и несколько нетривиальным методом. Команды, которую нужно выполнить, настроить как ExternalParameter. При наступлении нужного события запустить NXSL скрипт, в котором при помощи AgentReadParameter получить результат выполнения команды.

Lines 736 and 763 in file src/server/core/objtools.cpp should be


  DBBind(statment, 1, DB_SQLTYPE_INTEGER, dwToolId);


instead of


  DBBind(statment, bindID++, DB_SQLTYPE_INTEGER, dwToolId);


Best regards,
Victor