NetXMS Support Forum

Лучше писать сюда: https://www.radensolutions.com/chiliproject/login. Мы в процессе слияния Мантиса с внутренней Джирой. Как только все перенесем, останется наконец один issue tracker.

Поправил, спасибо.

В версии 1.2.3 можно будет, уже сделал.

А можно под gdb запустить и прислать backtrace?

Вроде сделал, можно пробовать: https://www.netxms.org/download/rc/netxms-1.2.3-rc1.tar.gz

Hi all!

Finally I've made some progress on this. Attached is an archive with latest message files. Please translate (in appropriate messages_lang.properties) and send back to me keeping same directory structure within archive. Archive includes existing translated files as well. Please note that there can be new entries in already translated files, so you have to compare existing translated files with English version for possible appearance of new messages!

Best regards,
Victor

Hi!

Do you set data type of DCI to unsigned integer?

Best regards,
Victor

D-Link использует portIdSubtype 7 (local) - в NetXMS'e нет поддержки такого типа. Я никогда до сих пор не встречал устройств, которые использовали бы этот тип идентификатора порта. Попробую сейчас добавить поддержку. Пришлите еще пожалуйста результат SNMP WALK по .1.0.8802.1.1.2.1.3 .

А можно прислать результат SNMP WALK для .1.0.8802.1.1.2.1.4.1.1? Например такой командой:

nxsnmpwalk -v 2c -c <community> <ip_address> .1.0.8802.1.1.2.1.4.1.1

Hi!

Yes, you are right. When I read GetTimeZoneInformation description, I had thought that Bias field contains current bias, calculated accordingly to DST. I have fixed it already, next build will contain correct code. Thank you for digging it out!

Best regards,
Victor

Quote from: xatteg on August 02, 2012, 09:59:58 AM
One thing I also would like to have is when you change alarm status to "Resolved" the alarm highlights should be removed from devices.

Yes, I agree. Will be done in next release.

Best regards,
Victor

Hi!

You can define external parameter in agent. Add the following line to your nxagentd.conf:

ExternalParameter = Exchange.MessageCount:powershell -Command "& {Get-Queue -Sort-Order:-MessageCount -Result:1 | fl -Property MessageCount}"

Part before : is a name for new parameter, you can set it whatever you want.

Restart agent, do configuration poll on a node, and you should see new parameter in parameters oist and be able to collect it as any other agent's parameter.

Best regards,
Victor

Попробуйте сделать Topology Poll вручную на коммутаторах - что он покажет? Если LLDP включен недавно, то возможно еще не собралась информация.

Da, dolzen byt' s lmsensors.

Quote from: Jmp_3f8h on August 01, 2012, 01:17:39 PM
I forgot to mention that in this scenario the event source for the alarm should be the container and not a specific node. But I don't know if promoting a container to source for alamr has other side effects.

This can cause some side effects. For example, now you have $node variable in filtering scripts in event processing policy. If container and/or cluster objects can be event sources as well, you will have to check with what object class you are dealing with before accessing object properties for example. It will be quite complicated change, mostly because lot of places in the code will need to be checked.

Best regards,
Victor