NetXMS Support Forum

Hi,

proxy node should be part of the zone. Working setup should looks like following:

Nodes A and B are in site zone;
Site's public IP translated to node B;
Node B set as zone's proxy;
ZoneId in nxagentd.conf on node B set to ID of site's zone;
Primary IP for node A set to internal IP address reachable from node B.

Best regards,
Victor

Hi,

currently it is not possible. Feel free to fill feature request, it should not be hard to implement.

Best regards,
Victor

Hi,

if node is first in a subnet and does not have SNMP or agent, server expected to create new /24 subnet (it can be changed by setting parameter DefaultSubnetMaskIPv4). It is definitely a bug, but so far I was unable to reproduce it. I'll experiment a bit more with it.

Best regards,
Victor

Hi,

could you please provide log for such node for entire configuration poll as well as output from manual configuration poll in console?

Best regards,
Victor

Hi,

that probably means that you don't have startup script for netxmsd or it is not registered for auto start. You should consult manuals for your OS/distribution on how to enable autostart. IN NetXMS source code ynder contrib/startup you can find startup scripts for various platforms.

Best regards,
Victor

Hi,

I think it is good to have those rights separated. Added it as feature request: https://dev.raden.solutions/issues/1360.

Best regards,
Victor

Hi,

you put

SubAgent = ping.nsm

into wrong section. It should be in main section of config but it is in FILEMGR section.

Best regards,
Victor

Hi,

before 2.0.7/2.1-M2 NetXMS only supported PAP for RADIUS authentication. As we added support for other authentication methods default was set to CHAP, which is probably wrong because it breaks backward compatibility.

Best regards,
Victor

Yes, it's planned.

Best regards,
Victor

Hi,

I'll try to. I've added as feature request to our bug tracker so it should not be forgotten (splitted into two issues: https://dev.raden.solutions/issues/1358 and https://dev.raden.solutions/issues/1359).

Best regards,
Victor

Переделал на poll - изменения внесены как в ветку develop, так и в stable-2.0. Можно пробовать.

У субагента ограничение на размер буфера - 10МБ. Но вряд-ли документ больше 10МБ? Ече можно включить сохранение полученых страниц, добавив параметр FailedDirectory в секцию PortCheck в конфиге агента - тогда на каждый неудачный запрос будет сохранен html, можно будет проверить что в нем реально находилось.

Посмотрел дамп - единственно что вижу - много вызовов kevent. Похоже мы как-то неправильно его используем. Сегодня-завтра переделаю, можно будет попробовать.

Hi,

so weird, it was supposed to be there... Seems to be backport issue. I've fixed it in current 2.0 branch, it will be part of 2.0.8 release if it will happen.

Best regards,
Victor

Try to set server debug level to at least 5 and check what is going on during login.

Best regards,
Victor