NetXMS Support Forum

Actually, there is a flaw in the logic of status poll. When there are no SNMP or NetXMS agent ob the node, server relies only on ICMP pings of interfaces. If all interfaces are down, node is considered down. Problem is that status poller checks status of interfaces, so interfaces with expected state set to ignore are effectively excluded from status calculation. Probably most correct solution would be to use interface operational state instead of status for determining if all interfaces are down.

Best regards,
Victor

По поводу навигации по карте - сейчас такого нет, но можно сделать. Добавлю в наш список feature requests.

Попробуйте такой скрипт:

return int64($1) * 8L;

So the driver that is working is CATALYST-GENERIC? In that case, could you send me result of SNMP walk on .1.3.6.1.4.1.9.5.1.2 from this C4500 switch?

I've seen post on topology issues, will answer on it later.

Best regards,
Victor

Add interface speed and type description is quite easy, will do that in one of next releases.

Entity MIB support should be enough to show information in components. Can you send me result of SNMP walk on .1.3.6.1.2.1.47.1.1.1.1?

Best regards,
Victor

Hi,

event if connection is not closed properly connection limit is way bigger than 2. What is in server log (on debug level 6 or higher) when you try to connect for 3rd time?

Best regards,
Victor

Hi,

most likely it indicated that there are no server connection accepting traps. Can you share agent configuration file (nxagentd.conf)? Also, how this node is configured in NetXMS server and what is configuration poll output for it?

Best regards,
Victor

Hi,

you should set:

left red end at 150;
left yellow end at 200;
right yellow start at 250;
right red start at 250;

Best regards,
Victor

Hi,

seems to be a problem with installation - looks like nxevent compiled for older/newer version of libnxcl. Is it possible that you for example forgot to specify --with-client when building upgrade binaries? Anyway, I think best solution would be to recompile binaries on that server.

Best regards,
Victor

You can set responsible person's in container's custom attribute, and create universal action that will use script to extract recipient. For example, you can definie recipients in email action like this:

%[GetRecipients]

Then, create script in script library caled "GetRecipients" like this:


foreach(p : GetNodeParents($node))
{
rcpt = GetCustomAttribute(p, "recipients");
if (rcpt != null)
return rcpt;
}
return "default@email";  // fallback email if nothing was set in containers


It will return emails configured in parent container for node in custom attribute "recipients", or default email if nothing is configured. Script can be made more complicated to collect all recipients on all upper layers and combine them into single recipient list.

Best regards,
Victor

Hi,

configuration on agent side seems to be ok, and SendTrap record in log confirms that event is being generated. Check that you run agent with debug level 6 or higher and try to find record similar to "sending message CMD_TRAP" after SendTrap() record. If you'll find it, it mean that message was actually sent to server and problem is on server side. If not, problem is on agent side.

Best regards,
Victor

Hi,

first of all, I would recommend to change events for threshold to SYS_TABLE_THRESHOLD_ACTIVATED and SYS_TABLE_THRESHOLD_REARMED - you will get much more meaningful messages including service name. Other than that configuration seems fine (you can actually use == instead of like when you are not using metacharacters, but it should not make any difference in result).

Best regards,
Victor

I would recommend 8-16GB RAM and 4 CPU cores. For this number of nodes you'll have instant flow of INSERTs in database, so you may want to give most attention to I/O and MySQL tuning.

Best regards,
Victor

Этот параметр появился в 2.0-M1.

Hi,

you can force driver selection for a node by setting node's custom attribute snmp.driver to driver name. Try to use Catalyst driver and if it will work I'll correct supported device detection in the driver.

Best regards,
Victor