NetXMS Support Forum

Quote from: SKYnv on March 14, 2012, 08:11:50 AM
столкнулся с проблемой что выпадают некорректные значения при сборе и обработке значение.

скрипты примерно такие

Code Select Expand


sub main()
{
return int64((($1*8)/1024)/1024);
}

выпадают отрицательные значения там где их не может быть, собирается параметр .1.3.6.1.2.1.2.2.1.16.1

Poskol'ku original'noe znachenie 32 bit, to pri pervom umnozenii na 8 mi mozem vijti za predeli vozmoznih znacenij dlja 32 bitnogo celogo, i poluchit' perepolnenie. Ja bi predlozil delat' snachala privedenie znachenija k 64 bitam, chtobi interpretator vse dal'nejshie matematicheskie operacii delal kak s 64 bit znacheniem. Vot malen'kij skript, kotorij pokazivaet raznicu:


println int64((($1 * 8) / 1024) / 1024);
println int64(((int64($1) * 8) / 1024) / 1024);


Rezul'tat:


C:\Source\NetXMS\debug>nxscript math.nxsl 100000000
NetXMS Scripting Host  Version 1.1.10
Copyright (c) 2005-2012 Victor Kirhenshtein

762
762

C:\Source\NetXMS\debug>nxscript math.nxsl 1000000000
NetXMS Scripting Host  Version 1.1.10
Copyright (c) 2005-2012 Victor Kirhenshtein

-562
7629


Quote from: SKYnv on March 14, 2012, 02:55:59 PM
ну наиболее стабильная работа идет на стандартных настройках.
то есть тип определяется как unsigned integer,никак не интерпретируется больше, ясно что это недостаточно, потому как на больших значениях данные ожидаемо падают в 0 и нужно использовать unsigned integer64, у этого же наоборот данные падают в нереальный плюс, если тип ансигнед, если сигнед то еще и в минус могут.
Отдаваемый тип явно int64

Code Select Expand

The total number of octets received on the
            interface, including framing characters.

Esli rech' idet o standartnih OIDah dlja trafika na interfeisah (.1.3.6.1.2.1.2.2.1.16 naprimer), to oni imejut SNMP tip Counter, t.e. unsigned 32bit integer. Zaschet togo chto znachenie unsigned, vichislenie delta budet prohodit' pravil'no daze pri perehode cherez 0.

Quote from: SKYnv on March 15, 2012, 05:55:17 AM
в script library опечатка в названии скрипта Resolve IfName

A chto eto za skript takoj? V default installjacii takogo vrode kak net.

Quote from: SKYnv on March 15, 2012, 10:12:27 AM
И еще вопрос в догонку я подозреваю что использовать сдвиги выгоднее деления или не принципиально?

Dlja interpretiruemogo skripta eto ne principial'no

From the error it seems that connection between NetXMS server and MySQL server is broken for some reason. There are many possible reasons for that. The fact that problem occurs on exact hours may point to some scheduled task, which broke communication with MySQL server in some way. Do you have MySQL server on same machine or on remote host?

Best regards,
Victor

A kak opredelen tip dannih v samom DCI (na zakladke General)? Kakoe original'noe znachenie, poluchaemoe s hosta?

Ogranichenij na kolichestvo DCI net.

Hi!

I suspect that NetXMS server incorrectly process some information obtained from device. Could you please send me more information about this object(s)? I'm mostly interested in information shown on summary page (capabilities, OID, system description), list of interfaces with IP addresses, and IP address selected as primary. I don't need to know exact IP addresses, but very important is to check that address selected as primary IP is presented on one of interface objects.

Best regards,
Victor

Vpechatljajuschij spisok Ja pozavozu eto kak otdel'nie bagi v nash bugtracker. Chto kasaetsja imen ob'ektov, to v nih nel'zja ispol'zovat' simvoli s kodom men'she 32 i sledujuschie special'nie simvoli:

|\"'*%#\\`;?<>=

Vo mnogom eto uze perezitok proshlogo, sejchas vrode kak nichego na eto ne zavjazano. Navernoe edinstvennaja potencial'naja problema - ispol'zovanie imen ob'ektov v komandah - posle podstanovki mogut poluchitsja neozidannie rezul'tati, esli tam skazem kavichki ili vertikal'naja cherta.

Viktor

Ja dumaju takoe opisanie budet poleznim.

Viktor

This topic intended for posting MIB files which are validated to work with NetXMS but not (yet) included in distribution.

Da, podderzivaju. Ja sdelaju novij sticky topik v razdele Configuration.

Viktor

Hi!

Thank you! I'll take a look at it in a few days.

Best regards,
Victor

Hi!

The correct syntax will be


return $node->ipAddr == "10.0.0.18" ||
$node->ipAddr == "10.0.0.92" ||
$node->ipAddr == "10.0.0.93" ||
$node->ipAddr == "10.0.0.94" ||
$node->ipAddr == "10.0.0.96" ||
$node->ipAddr == "10.0.0.97";


Best regards,
Victor

Hi!

I'm interested in walk results for the following OIDs:

.1.3.6.1.2.1.1
.1.3.6.1.2.1.2
.1.3.6.1.2.1.17.1
.1.3.6.1.2.1.4.20.1
.1.3.6.1.4.1.9.9.401.1
.1.3.6.1.4.1.9.9.134.1
.1.3.6.1.4.1.9.9.276.1
.1.3.6.1.4.1.9.9.173.1
.1.3.6.1.4.1.9.9.128
.1.3.6.1.4.1.9.9.68

Output can contain sensitive information like IP addresses. You can obfuscate them if it is a problem, just let me know what places in the output was changed.

Best regards,
Victor

Technically it's possible, but there are lot of licensing limitations, especially for using Google maps in desktop applications. My initial implementations was based on Google maps, but then I read terms of use and switched to OSM. Limitations that I can remember so far are:

1. You cannot access tiles directly - you have to issue rendering request each time you have to display map. For example, if you resize map window, you have to do new request to server with new map size.
2. Caching is forbidden
3. Map size is limited to something around 600 pixels
4. You cannot glue pieces of the map together to create a bigger map - that means that you cannot create large full screen view with geo map
5. You have limits on rendering requests per day
6. Google requires that application which uses Google maps should be publicly available - it's not clear if it's enough that source code can be downloaded, or monitoring service itself should be publicly available.

Of course, if you purchase commercial access to Googe maps, you will not have those limitations. If somebody wishes to integrate access for commercial Google map services, we can do it.

Best regards,
Victor