NetXMS Support Forum

Hi!

Most likely you will need Solaris agent, but for x86 architecture (Solaris 10 agent binaries on our site is for Sparc, and Solaris 11 for x86). I'll check what happens with Solaris 11 agent download - it should be what you need.

Best regards,
Victor

Hi,

this message format dows not conform neither to BSD syslog format (RFC 3164) nor RFC 5424. The main problem is that 2014 as host name is a valid IP address (it's not widely known nor used, but it is valid to write IP addresses not only as n.n.n.n, but also as n, n.n, and n.n.n) so it resolves to 0.0.7.222, which of course is not found. I change node binding logic so that if server cannot find node by hostname/IP address provided in syslog message itself it still try source IP address of the message. This should solve your problem.

Best regards,
Victor

Hi,

if you see threshold triggered, that mean that event was generated. Most likely problem is in event processing policy. Double check the rule that is supposed to show alarm from threshold violation event.

Best regards,
Victor

I hope to made it available in a week or so.

Best regards,
Victor

It could be. Can you provide full syslog packet dump (with original text)? Probably I can tweak syslog parser so it will understand Zyxel variant correctly (we already done that for Cisco for example).

Best regards,
Victor

Hi!

Bug with repeated threshold violation events was fixed in 1.2.14. I had to read our own change log first

Issue 564 is relatively easy to implement, I think I can made it before 1.2.15 release. 563 is more complicated, and most likely it will not be before 1.2.16 release.

Best regards,
Victor

Hi!

Can you show me few examples of syslog packets? Server try to find source object using "host" part of syslog message first - maybe this is the problem.

Best regards,
Victor

I would say it's a bug. There was similar problem with SNMP traps. Now server do not create events from SNMP traps from unmanaged nodes unless you set ProcessTrapsFromUnmanagedNodes parameter to 1. I'll do the same for syslog.

Best regards,
Victor

Hi,

default map image size is 48x48.

Best regards,
Victor

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