NetXMS Support Forum

Hi,

assigning cluster resources with a script will definitely allow more possibilities for cluster monitoring. I'll try to add it in one of next versions.

Best regards,
Victor

Hi,

it seems that I just have to change base OID for SNMP walk. I've added issue to pur bug tracker: https://dev.raden.solutions/issues/878.

Best regards,
Victor

Hi,

I was able to reproduce this problem on my test system. I'll provide fix soon.

Best regards,
Victor

Quote from: brettmilfos on August 11, 2015, 12:53:50 AM
I have encountered one issue. While upgrading from 2.0M5 all the mibs from var/mibs dis-appeared. This is on win2k8r2.

Restored mibs from a backup and re-built. But now when I run the 32bit console on win7 I get the following error after logging in:
"Cannot load MIB file from server: File I/O operation failed"

MIB locations was changed in 2.0-RC1. Source MIBs now are in <install_path>\share\mibs and compiled MIB file in <install_path>\var. Installer was supposed to move any non-standard MIBs from var\mibs to share\mibs. If you compile MIBs manually, you should set output file to be <install_path>\var\netxms.mib.

Quote from: brettmilfos on August 11, 2015, 12:53:50 AM
Also, do not know if this is related to the upgrade, before upgrading I stopped the Core, Agent & WebGUI services, but there was still a lock on the MySQL DB which prevented DB upgrade.

That means that core service didn't stop normally and was forcibly terminated by service manager. It's not related to upgrade, but rather indicates some problem with previous version.

Best regards,
Victor

Hi,

instead of processing SYS_AGENT_UNREACHABLE event you can collect internal parameter AgentStatus. It returns 0 if agent is connected and 1 if unreachable. Then you can use thresholds as usual to generate alarm only if agent is unreachable for more then specific time period.

Best regards,
Victor

Can you provide more detailed information how exactly false positive looks like (service name, etc.). I tested it on my machine and everything works as expected.

Best regards,
Victor

Hi all!

NetXMS 2.0-RC1 is out! Changes since previous release:

- Fixed LDAP authentication issues with Active Directory
- Fixed character encoding issues in LDAP user data
- Java subagent improved
- Fixed multiple issues with agent side data caching
- Hash maps implemented in NXSL
- Improved array implementation in NXSL
- New NXSL function ArrayToString
- New OS parameters and tables: System.HandleCount, System.OpenFiles, Process.Handles
- Unified macros in all types of object tools
- Server can be switched to case-insensitive login names mode
- Implemented support of "command generates output" option for server commands
- Network device driver for TelcoBridges gateways
- Fixed memory leak in Qtech OLT driver
- Java subagent plugin for Ubiquity/LigoWave device monitoring
- Management console:
   - Default object display mode can be set in map properties
   - Map drill-down can be enabled in dashboard map elements
   - Input fields in object tools
   - Improved script editor for script library
   - Interface speed displayed in interface object details and in "Interfaces" tab
   - Symbolic name of interface type displayed when known
- Fixed issues: #38, #55, #741, #818, #829, #830, #836, #838, #840, #843, #844, #845, #846, #848, #850, #853, #855, #856, #857, #862, #866

Best regards,
Victor

It is not possible now, but I think it could be quite useful to have template graphs (and possibly dashboards) preconfigured and accessible for node in a way similar to object tools. So far I see easiest way to implement it is to add option "save as template" for graph - it will save all settings except actual node name, and when called for node will show same parameters for selected node. It should not be too complicated to implement. For those who wants to track progress: https://dev.raden.solutions/issues/876.

Best regards,
Victor

Hi,

no it's not possible. However, you can generate new event from NXSL using PostEvent function, and execute action on this event as usual.

Best regards,
Victor

So, there are two problems. First, you should add 127.0.0.1 to list of MasterServers for agent running on NetXMS server. Second, you should check that primary host name for node is not set to 127.0.0.1, but to real IP address.

Best regards,
Victor

Попробуйте прописать в конфиге агента как ConfigurableQuery - должен появится новый параметр checksensor к которому можно будет обратится как checksensor(1)

Логично на самом деле. Тип тоже можно ведь достать из объекта интерфейса - поле ifType.

Из фильтра можно возвращать измененый instance и instance name. Можно попробовать такой скрипт:


transport = CreateSNMPTransport($node);
if (transport == null)
return false;
type = SNMPGet(transport, ".1.3.6.1.2.1.2.2.1.3." . $1);
if (type == null)
return false;
if (type->value != 129)
return false;

name = SNMPGetValue(transport, ".1.3.6.1.2.1.2.2.1.2." . $1);  // ifDescr
if (name == null)
        name = $1; // use interface index as fallback

return %(true, $1, name);


и в параметре использовать {instance-name} там где надо подставить имя интерфейса.

Can you post agent config for verification please?

Best regards,
Victor

Hi,

your agent version (2.0-M2) has a bug that can cause incorrect server access if server address listed in multiple categories (Servers, ControlServers, MasterServers). Try to comment out Servers and ControlServers options in nxagentd.conf leaving only MasterServers.

Best regards,
Victor