Hi,
I use great NetXMS to monitor lot of Windows Server nodes, but only on one I have constantly a new alert generated (few times a day) :
Node capabilities changed (Old: 0x090C0002; New: 0x09040002)
Can somebody explain in more detail what were old and what are new capabilities, so I will try to figure out what is causing it, and stop necessary alerting.
(I do not want to turn of this alerting, just to solve problem causing it)
Thank you
I found something in NetXMS source, nxclapi.h
/**
* Node flags
*/
#define NF_SYSTEM_FLAGS 0x003FFF7F
#define NF_USER_FLAGS 0xFFC00080
#define NF_IS_SNMP 0x00000001
#define NF_IS_NATIVE_AGENT 0x00000002
#define NF_IS_BRIDGE 0x00000004
#define NF_IS_ROUTER 0x00000008
#define NF_IS_LOCAL_MGMT 0x00000010
#define NF_IS_PRINTER 0x00000020
#define NF_IS_OSPF 0x00000040
#define NF_REMOTE_AGENT 0x00000080
#define NF_IS_CPSNMP 0x00000100 /* CheckPoint SNMP agent on port 260 */
#define NF_IS_CDP 0x00000200
#define NF_IS_NDP 0x00000400 /* Supports Nortel (Synoptics/Bay Networks) topology discovery */
#define NF_IS_SONMP 0x00000400 /* SONMP is an old name for NDP */
#define NF_IS_LLDP 0x00000800 /* Supports Link Layer Discovery Protocol */
#define NF_IS_VRRP 0x00001000 /* VRRP support */
#define NF_HAS_VLANS 0x00002000 /* VLAN information available */
#define NF_IS_8021X 0x00004000 /* 802.1x support enabled on node */
#define NF_IS_STP 0x00008000 /* Spanning Tree (IEEE 802.1d) enabled on node */
#define NF_HAS_ENTITY_MIB 0x00010000 /* Supports ENTITY-MIB */
#define NF_HAS_IFXTABLE 0x00020000 /* Supports ifXTable */
#define NF_HAS_AGENT_IFXCOUNTERS 0x00040000 /* Agent supports 64-bit interface counters */
#define NF_HAS_WINPDH 0x00080000 /* Node supports Windows PDH parameters */
#define NF_IS_WIFI_CONTROLLER 0x00100000 /* Node is wireless network controller */
#define NF_IS_SMCLP 0x00200000 /* Node supports SMCLP protocol */
#define NF_DISABLE_DISCOVERY_POLL 0x00400000
#define NF_DISABLE_TOPOLOGY_POLL 0x00800000
#define NF_DISABLE_SNMP 0x01000000
#define NF_DISABLE_NXCP 0x02000000
#define NF_DISABLE_ICMP 0x04000000
#define NF_FORCE_ENCRYPTION 0x08000000
#define NF_DISABLE_STATUS_POLL 0x10000000
#define NF_DISABLE_CONF_POLL 0x20000000
#define NF_DISABLE_ROUTE_POLL 0x40000000
#define NF_DISABLE_DATA_COLLECT 0x80000000
and it seems in my case, that regular Pool configuration sometimes pick-ups that ICMP should not be monitored for this Windows Server node.
Can somebody confirm me that I am on correct track to solve the issue ?
Thank you
Hi!
That means that flag NF_HAS_WINPDH (Node supports Windows PDH parameters) set and cleared periodically. Node considered to support PDH if it has NetXMS agent and agent responds correctly to PDH requests (PDH.Objects list and others). You can check server debug log (running with debug level 5 or higher) for error messages started with WinPerfObject::getWinPerfObjectsFromNode prefix.
Best regards,
Victor
Quote from: Victor Kirhenshtein on May 05, 2014, 03:56:01 PM
Hi!
That means that flag NF_HAS_WINPDH (Node supports Windows PDH parameters) set and cleared periodically. Node considered to support PDH if it has NetXMS agent and agent responds correctly to PDH requests (PDH.Objects list and others). You can check server debug log (running with debug level 5 or higher) for error messages started with WinPerfObject::getWinPerfObjectsFromNode prefix.
Best regards,
Victor
Great, thank you for correcting me !
I Windows Event Log , from NetXMS Agent I have:
H_PdhCounterValue: PDH Error 00000102 in call to PdhOpenQuery (The wait operation timed out.)
Please explain what to check futher ?
I understand that it has something with disk / RAID ?
Server is operating normally.