NetXMS Support Forum

Насколько я понимаю это другое - этот параметр задает, как Juniper будет идентифицировать свои порты в отсылаемых LLDP пакетах.

Hi!

You cannot cancel timer directly from NXSL. However, you can generate special event to cancel timer. For example, in your script you can have something like

PostEvent($object, "CANCEL_TIMER", null, timer);   // Variable "timer" contains timer key

and in EPP you create separate rule that handles event CANCEL_TIMER and the only action is "cancel timer" with %1 as key.

Of course you also have to create event CANCEL_TIMER.

Also, if you need macro string expanded within NXSL, you can use function ExpandString. In your example you can do

timer = ExpandString("nodetimer_%i", $node);

That way you are guaranteed to have exactly same string in NXSL as in other EPP places.

Best regards,
Victor

Hi,

try to use ExternalParameterShellExec instead. Also, how long it take to execute this command? There could have been changes in handling execution timeouts. Agent log on debug level 6 could be helpful as well.

And what version you are using currently?

Best regards,
Victor

Hi,

it could be access control issue - maybe account you are using don't have access to those nodes. Discovered nodes will appear in "Entire Network" tree under appropriate subnet. You can try to login with user "system" and check - this user always has access to all objects, so you should see them or be able to find.

Best regards,
Victor

Hi all!

We just published new patch release for version 4.1 - 4.1.420, with some fixes and improvements on top of release 4.1.404. Full change log is following:

- Optimized alarm resolve/terminate using regular expressions
- Improved topology detection on Juniper switches
- Fixed communication protocol compatibility issues in C++ client library and command line client tools
- Fixed issues:
        NX-627 (Gauge rendered incorrectly)
        NX-846 (Ability to copy to clipboard in Routing Table and FDB views)
        NX-1077 (Option to copy MAC address to clipboard in FDB view)
        NX-2283 (Show version in debug console)

Best regards,
Victor

Похоже что Juniper использует индекс интерфейса вместо bridge port number в таблице lldpRemTable. Я добавил в драйвер Juniper индикатор для принудительного использования ifIndex - по идее должно помочь. Мы вскоре выпустим новый патч релиз для 4.1 - можно будет проверить.

Hi,

most texts in UI are located in so called language files. For translation we create new language file which initially contains all texts in English, so they can be translated. We also add new language menu to UI.

Currently there are two issues:
1. Not all texts moved to language files, some are hard-coded as English.
2. We are in process of migrating to new UI, which will have different localization mechanism.

I can prepare and provide you language files for old UI, so you'll be able to translate most of the texts. However, it could be more effective to do new translation on new UI. I hope we will have localization mechanism in new UI ready with release 4.2.

Best regards,
Victor

А какая версия сервера?

Пришлите пожалуйста результат SNMP walk по следующим веткам:
.1.0.8802.1.1.2.1.4.1.1
.1.0.8802.1.1.2.1.3
.1.3.6.1.2.1.17.1.4.1
.1.3.6.1.2.1.2.2.1.2

So agent is built for older MySQL client library. What Linux distribution you are using? If it is Debian or Ubuntu, I highly recommend using deb packages for installation. For RedHat we also provide separate binary package. If none of the above, then you either have to install required libmysqlclient or build agent from sources.

Best regards,
Victor

I was unable to reproduce this issue, neither with 4.1.333 nor with 4.1.404. Try to redeploy webapp, maybe also make sure that work directory is deleted.

Best regards,
Victor

Looks like you are missing MySQL client library. Make sure it is installed. Also, how did you install agent?

Best regards,
Victor

Например так:


bs = new ByteStream();
bs->writeByte(0xC0);
bs->writeByte(0xA8);
bs->writeByte(0x05);
bs->writeByte(0x5D);

snmp = $node->createSNMPTransport();
snmp->set(".1.3.6.1.4.1.171.14.14.1.2.1.6.1", bs);


Definitely not an intended behavior. We will check if it can be reproduced on our test systems.

Best regards,
Victor

Hi,

looks like I forgot to update change log with this fix. However, it was fixed as part of this commit: https://github.com/netxms/netxms/commit/80c79d73d7e4b358769b35bd034cbe921f6b39a1 and included into 4.1.377.

Best regards,
Victor

Сейчас nxsnmpset не поддерживает задание OCTET STRING в шестнадцатеричном виде. Я добавил feature request: https://track.radensolutions.com/issue/NX-2278.

В текущей версии это можно делать из NXSL скрипта - при помощи ByteStream собрать нужную последовательность байтов и передать в SNMP SET.