NetXMS Support Forum

Hi!

File iostat.h was missing from source package. I put updated package on web site, now it should compiles without problems.

Best regards,
Victor

Hello!

Looks like some Cisco switches need special handling for interface names. NetXMS server reads interface description from .1.3.6.1.2.1.2.2.1.2, which is standard interface MIB supported by all SNMP devices. As I see Catalyst 6500 returns description of the interface here, not the name as most devices do. In the next version I will add check for extended information under ifXTable (.1.3.6.1.2.1.31.1.1) and NetXMS server will use it when available. This should solve Cat 6500 problem (and possible for some other devices too).

Best regards,
Victor

Hello all!

NetXMS version 0.2.21 released. Changes from previous release:

- Multiple network maps implemented
- Added parameter ListenAddress to all services (server, web server, agent)
- New possible value for UseInterfaceAliases - concatenate name with alias
- Added possibility to create custom message in event matching script and
  use it in alarms and actions
- WMI subagent added
- SNMP sysDescr and agent's uname now polled and displayed
- New features in Windows console:
   - Possibility to use non-local timezone in Windows console
   - Default graph settings can be changed
- AIX subagent: implemented System.CPU.LoadAvg* and System.Uptime parameters
- Fixed issues: #193, #194, #198, #204, #209, #211, #212, #213, #214, #215

Best regards,
Victor

Change log:

- Multiple network maps implemented
- Added parameter ListenAddress to all services (server, web server, agent)
- New possible value for UseInterfaceAliases - concatenate name with alias
- Added possibility to create custom message in event matching script and
  use it in alarms and actions
- WMI subagent added
- SNMP sysDescr and agent's uname now polled and displayed
- New features in Windows console:
        - Possibility to use non-local timezone in Windows console
        - Default graph settings can be changed
- AIX subagent: implemented System.CPU.LoadAvg* and System.Uptime parameters
- Fixed issues: #193, #194, #198, #204, #209, #211, #212, #213, #214, #215

Best regards,
Victor

Hi!

First, you should create DCI for ifSpeed. Let's assume that it's description will be "Interface speed" (without quotes). After that, create DCI for ifInOctets, and create transformation script for it:


(($1 * 8) / GetDCIValue($node, FindDCIByDescription($node, "Interface speed"))) * 100


If you will use different DCI description for ifSpeed parameter, change call to FindDCIByDescription accordingly.

You can also take a look at the following topic:

https://www.netxms.org/forum/index.php/topic,292.msg1495.html#msg1495

Best regards,
Victor

Hello!

Please try to upgrade to 0.2.21 - it's available already at https://www.netxms.org/download/netxms-0.2.21.exe but not announced yet - we do some final testing. You problem looks very similar to one solved in 0.2.21, related to SNMP data collection.

Best regards,
Victor

List of available parameters populated by server during configuration polls, which is every 1 hour by default. You can start configuration poll manually by right-clicking on node object and selecting Poll -> Configuration.

Best regards,
Victor

You mean to notify when new updates are available for Windows but not installed yet? Why not to use WSUS for it - as far as I know it's free.

Hello!

It's intended for centrally stored configs. If you start agent with option -M management_server_address, then agent tries to connect to management server and get configuration file from there. In agent configuration manager you can define these configs and filters to decide which agent takes which config.

Best regards,
Victor

I agree, it can be useful feature.

For now, it potentially could be done on UNIX with combination of procmail and nxevent (or nxpush). Maybe it is also possible to run procmail on Windows under cygwin.

Best regards,
Victor

Yes, screenshots will be helpful

Похоже что сервер не может прочитать файл netxms.mib. Он должен быть в каталоге <install_prefix>/share/netxms/mibs.

Node status calculated based on two sources - active alarms for that node and status of child objects (usually interfaces). If you wish that node remains in NORMAL status event if some or all interfaces goes down, you should change status propagation algorithm for child objects of that node. You can select "fixed value" propagation algorithm for interface objects and set value to NORMAL.

Best regards,
Victor

It can be a problem for NetXMS, because if during status poll it determines that node is down, data collection will not be scheduled for that node. But, if there are no status polls, NetXMS will try to establish TCP connection for each parameter to be collected. With connection timeout about 1 minute, it can easily cause long data collection queues.

What is the reason for disabling status polls? If you don't want alarms, mails, etc. for SYS_NODE_DOWN events, you can just block them in the first rule of event processing policy.

Best regards,
Victor

Hello!

It's fixed in 0.2.21.

Best regards,
Victor