Menu

Show posts

This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.

Show posts Menu

Messages - Victor Kirhenshtein

#6391
General Support / Re: skip modem from monitoring
March 02, 2010, 07:26:01 PM
If you need to compare two values in NXSL, you should use == operator. Operator = is an assignment. So, if your script really uses = instead of ==, it's one mistake. Also, don't forget that any event passes all rules, except if matching rule contains "stop processing" option. You have to add it to your rule. Also, interface name always passed as parameter number 2 with SYS_IF_DOWN and SYS_IF_UP events, so you can compare just it's value to {5757FA85-B187-42A4-981C-7443B4ECFC90} instead of comparing full message text. So, I suggest the following rule:

event:
SYS_IF_DOWN
SYS_IF_UP

source:
any

severity:
any

script:
$2 == "{5757FA85-B187-42A4-981C-7443B4ECFC90}"

alarm:
none

actions:
none

options:
stop processing


Should work :)

Best regards,
Victor
#6392
Poprobujte zapustit' configure kak:

#LDFLAGS=-lmysqlclient ./configure --with-server --with-mysql --prefix=/usr/local --mandir=/usr/local/man --infodir=/usr/local/info/ --build=i386-portbld-freebsd8.0

Pohoze chto eto bug v configure.
#6393
A prishlite pozalujsta config.log
#6394
General Support / Re: Action to return value
February 26, 2010, 10:06:47 AM
Hi!

DCI object has the following attributes:


AttributeDescription
dataTypeDCI data type (string, integer, etc.) represented as internal numeric code
descriptionDCI description
idDCI identifier
lastPollTimeDCI last successful poll time as UNIX timestamp (number of seconds since 01.01.1970 00:00:00 UTC)
nameParameter's name
originDCI origin (NetXMS agent, SNMP, etc.) represented as internal numeric code
statusDCI status (0 = active, 1 = disabled, 2 = not supported)
systemTagDCI system tag (not available in 1.0.x versions)

So, you need lastPollTime attribute.

Please also note that there are new function called "trace", which can be very useful in debugging scripts. It takes two arguments - debug level (0 .. 9) and text, like this:

trace(1, "some message");

Text passed as second argument will appear in server's log, if given debug level less or equal current server's debug level (set by -D command line option). If debug level in trace() call set to 0, message will always be logged with INFO severity.

Best regards,
Victor
#6395
General Support / Re: Action to return value
February 25, 2010, 06:40:53 PM
In 1.0.0-rc1 I have added new NXSL function FindNodeObject. It takes two arguments: current node object and ID or name of node of interest. It can be used as following:


sub main()
{
   // Search for node named "gateway"
   gw_node = FindNodeObject($node, "gateway");
   
   if (gw_node == null)
      return 0;   // No such node or access denied

   // from here, gw_node can be used in a same way as $node, for example:
   status = GetDCIValue(gw_node, FindDCIByDescription(gw_node, "Status"));

   return 1;
}


Best regards,
Victor
#6396
Announcements / NetXMS 1.0.0-rc1 released
February 25, 2010, 06:34:56 PM
Hi all!

Version 1.0.0-rc1 is out. It's a release candidate for stable 1.0.0 branch. If it works fine, we release 1.0.0 and focus on active development of 1.1.0 branch, where lot of changes are planned. Also, preview of new Eclipse-based management console from 1.1.0 branch, compatible with current 1.0.0 branch, will be released soon.

Changes in 1.0.0-rc1 compared to 0.2.23:

- System configuration (events, SNMP traps, templates, event processing rules) can be exported and imported in XML format - this solves various problems with old NXMP files
- NXSL improvements:
   - New functions: GetDCIObject, GetInterfaceName, FindNodeObject, trace
   - Added built-in constants TRUE and FALSE
- Added support for encrypted DB passwords in netxmsd.conf
- Improved SNMPv3 support
- Fixed issues: #62, #278

Best regards,
Victor
#6397
По умолчанию на событие SNMP_LINK_DOWN аларм не создается. Надо добавить в event processing policy правило для генерации аларма по этому событию.
#6398
There are two parameters for disk space on UNIX: Disk.Free (or Disk.FreePerc) and Disk.Avail (or Disk.AvailPerc). First shows total amount of free space, including reserved blocks. Second shows free space available to non-root users - free space without reserved blocks. You should compare Disk.Avail results with df output.

Best regards,
Victor
#6399
Esli pri obrabotke sobitija, to dolzno rabotat' tak:

GetDCIValue($node, FindDCIByName($node, "Disk.Total(" . $6 . ")"));
#6400
General Support / Re: Pocket PC binary installer
February 23, 2010, 11:09:19 PM
Unfortunately, PocketPC version is long forgotten. Probably I could rebuild it to work with current server version, but it has very limited functionality. You can:
- Browse object tree
- Work with alarms: see list, acknowledge and terminate
- View last collected values for DCIs
- View graphs for DCIs

If such functionality is interesting for you, I could try to rebuild PocketPC client.

Best regards,
Victor
#6401
It's I/O error on server - most likely server cannot access MIB file (netxms.mib). Did you compile MIBs?

Best regards,
Victor
#6402
General Support / Re: Data collection - Graph/history
February 23, 2010, 11:05:09 PM
Very strange. I can create a graph for a one year for example. Is there anything in server logs? Also, could you please run server with -D 9 for a moment, try to create graph for long period, and send logs to me (at [email protected])?

Best regards,
Victor
#6403
He probably mean menu in SQLite Database Browser, not in NetXMS console.

Best regards,
Victor
#6404
General Support / Re: How to add a script to the template
February 23, 2010, 10:59:48 PM
What do you mean by that? There are various places where scripts could be used - autobinding, data transformation, event processing, etc. What do you want to achieve?

Best regards,
Victor
#6405
General Support / Re: How to create a Event
February 23, 2010, 10:58:19 PM
Hi!

You should create separate events (for example, DISK_SPACE_WARNING, DISK_SPACE_CRITICAL) for each level you wish to have. Then add appropriate thresholds and set your custom events as activation events. For example, for threshold "> 50" set  DISK_SPACE_WARNING as event, and for threshold "> 90" set DISK_SPACE_CRITICAL as event. Don't forget to order thresholds properly - in case with disk space, you should start with "> 90", then "> 75", then "> 50". See data collection section in manual for explanation. Add appropriate processing to event processing policy.

Best regards,
Victor