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

Topics - Dani@M3T

#21
We use NetXMS V2.0-M3 and see a very strange but critical problem.

All "SYS_NODE_DOWN" events are not processed anymore in Event Process Policies. I checked the EPPs double and triple. Everything still like it worked before (same config). I also tested with the EPP-policy for "SYS_NODE_DOWN" as first rule. "SYS_NODE_UP" and all other events are processed fine. The events "SYS_NODE_DOWN" are generated, that part is ok. It occures on all tested nodes.
I turned on server debug logging (level=9). There I see for every generated event a line like this:
[25-Apr-2015 17:50:04.531] [DEBUG] EPP: processing event 1857868
But no such line for the "SYS_NODE_DOWN" events. I have the debug log but would not like attach to forum posts.

It could be since upgrade to V2.0-M3, but not for sure.
At the moment I don't know where the problem can be. Any help is appreciated.
#22
We have a lot of events "SYS_THREAD_HANG" (Thread "Item Poller" is not responding).
Most of time only for a few seconds, then "SYS_THREAD_RUNNING" again.

What is the best way to analyse this and find the root cause?
(maybe a good point for the troubleshooting paragraph of the administrator guide)

In server log we get:
[14-Apr-2015 15:30:51.580] [ERROR] Thread "Item Poller" does not respond to watchdog thread

Server debug log is attached.

We use NetXMS V2.0-M3 (linux x64, PostgreSQL).

Thanks!
#23
Especially with MAC addresses we see situations in SNMP values like this:

ARP-Table:
.1.3.6.1.2.1.3.1.1.2.8.1.192.168.30.3 [Hex-STRING] = 4C 9E FF 6F E0 17
.1.3.6.1.2.1.3.1.1.2.8.1.192.168.30.4 [Hex-STRING] = 4C 9E FF 6F E2 15
.1.3.6.1.2.1.3.1.1.2.8.1.192.168.30.10 [Hex-STRING] = 00 08 9B DA 8B C5
.1.3.6.1.2.1.3.1.1.2.8.1.192.168.30.100 [STRING] = x~a?G
.1.3.6.1.2.1.3.1.1.2.8.1.192.168.30.103 [STRING] = Tä:?ön
.1.3.6.1.2.1.3.1.1.2.8.1.192.168.30.109 [Hex-STRING] = 28 6A BA 90 1B 77
.1.3.6.1.2.1.3.1.1.2.8.1.192.168.30.111 [STRING] = ô·âw_


Some values are of type STRING instead of Hex-STRING (in the same SNMP table!). We see this especially with ZyXEL devices, but other vendors too. Is this a problem of the monitored devices or in NetXMS? (NetXMS is V2.0-M3 on Linux x64, built from sources). If you need more information, no problem. Thanks.
#24
General Support / Cluster Monitoring Questions
January 14, 2015, 12:25:16 PM
We just built up a new storage cluster which we want to monitor by NetXMS. So I created a cluster object and 2 nodes. Unfortunately the Section 'Monitoring Clusters' is still not available in the administration guide. So I have a few questions:


  • Where can I see the 'Last Values' of cluster object DCIs (associated to cluster ressources or not)? In 'Object Details' of the cluster object 'Last Values' is empty.
  • There is no 'Performance' tab in Object Details of cluster objects
  • Will the Admin Guide section for Cluster be published soon?
  • in 'Data Collection Configuration' of cluster objects it would be good to have a column 'Cluster Ressource' in the table
  • DCIs on Cluster Object with no associated cluster ressource will be polled to which IP address?
  • How can we use templates for cluster objects? The problem is the name of the cluster ressource to associate. Assign templates to cluster nodes directly, thats clear.
  • What is the meaning of 'Cluster Networks' in cluster object properties?

Thansk for any help.
#25
General Support / SNMP configuration lost
January 10, 2015, 11:15:32 PM
we have a strange phenomena:
We have a node in NetXMS which losts his SNMP conficuration. I set the SNMP settings in 'Communications' to SNMPv3 with authentication and encryption in the java console. Then I finish with 'ok'. When I just reopen the node properties the settings are still there. A few minutes later I open the properties again and the SNMP settings are reseted to SNMP version 2c community string 'public'.
Very strange, I never saw that on other nodes before. How is this possible? and how can I fix this. Please help.

thanks
Dani

(NetXMS 2.0M1 installed from sources on linux 64bit, but also saw this on V1.2.17)
#26
Hi

If a node has more than one interface. You should be able to choose the interface for each DCI. Maybe if nothing is choosen, NetXMS uses the interface of the Primary IP address. At the moment we need to create a second node for that and use proxy node. But that's not very elegant.

That could be used for baseboard management interfaces and also for nodes with interfaces in different vLANs.

Or how far are the plans for the object class "Management Board", as Alex said in this post?:
https://www.netxms.org/forum/configuration/server-with-bmc-board-as-one-node/msg12473/#msg12473

#27
General Support / User Permission Problems
November 16, 2014, 05:43:43 PM
We want to give some supporters rights limited to there sites in NetXMS. So we assign rights only to the 'site'-container in 'Infrastructure Services'. There I see these problems:


  • The System Right 'View event log' also includes Syslog. Please add this to the admin guide.
  • You cannot block access to Event-Monitor, Syslog-Monitor and SNMP Trap Monitor (the System Rights are only for the corresponding Logs in Menu 'View')
  • In Alarm-, Event-, SNMP Trap-Log and Syslog the limited supporter can see all events, syslog-entries... of all nodes, not only the ones from the containers he has permission for. NetXMS should filter the log entries and only show entries of sources he has permission for. In the fiield 'source' he only sees the node-id for such entries but he sees all other fields like 'Host Name' and 'Message'. We cannot allow this.
  • Would it be possible and reasonable to remove all menu items a user don't have permisison for? To get everytime this error message is not very user friendly: 'Open log ,,syslog" has encountered a problem. Cannot open server log ,,syslog": Access denied
#28
Feature Requests / Clusters on Status Map
October 30, 2014, 09:34:40 AM
On Status Maps are only nodes. It would be great to have clusters on this map too. For us Status Maps are a good feature for fast overview.
#29
General Support / Error in Tools - Wakeup node
October 21, 2014, 09:32:18 PM
When I try to start a physical linux node by 'Tools - Wakeup node' I get this error in NetXMS Management Console (on Windows 64bit):

'Wake node' has encountered a problem
Cannot send wake-on-LAN packet to node: No MAC address on interface

But there is a MAC address on interface eth0 in NetXMS and other Wake-on-LAN tools can start the same target machine.
(NetXMS 1.2.17)
#30
Copy/Paste (CTRL+C, CTRL+V) is not working at a lot of places in Java console (V1.2.16 on Windows-x64).
For example:
- Script Editor
- Agent Config Manager

That's very painful. Does others see this too?
#31
General Support / node for an unmanaged switch
August 18, 2014, 10:59:54 PM
I'm looking for a possibility to have unmanaged switches as managed nodes in NetXMS.

Example:
NetXMS --- SwitchA --- SwitchB --- DeviceX
(NetXMS = Monitoring-Server, SwitchA = managed Switch, SwitchB = unmanaged Switch, DeviceX = some NetXMS node)

So I could use the Status of the switch port on SwitchA (on which SwitchB is connected) to determine the status of SwitchB. I defined for SwitchB a node in NetXMS with a DCI which reads the interface status from SwitchA. But so I only have a normal DCI on SwitchB and no 'Status' (with SYS_NODE-DOWN and UP).
I made some experiments with the 'This is address of remote management node' switch. But no luck.
Has anybody a good solution for such a situation? Thanks in advance for all suggestions.
#32
I saw the command line of the NetXMS-windows-service is like:
"C:\Program Files\NetXMS\bin\nxagentd.exe" -d -c "C:\Program Files\NetXMS\etc\nxagentd.conf" -n "NetXMSAgentdW32" -e "NetXMS Win32 Agent" -D 0

So the DebugLevel is already defined in the command line ("-D 0") and "DebugLevel = 9" in agent configuration file is useless. When I delete the "-D 0" in the windows registry (value "ImagePath") the "DebugLevel"-setting in the configuration file works.

(tested with NetXMS-Agent V1.2.16 on Win2012R2)
#33
Till now we have all agent configs locally on each node. For better management I want to transfer them to a server based approach. In Admin guide I see two possibilities:

  • Agent Policies
  • Agent Configuration Files on Server (Agent Config manager)

Now my questions:

  • what are the advantages and disadvantages of both functions?
  • Which is the better way for the future?
#34
In the script library editor of the java console I miss Copy/Paste (neither CTRL-C nor context menu)
#35
I inserted this filtering script in an existing event processing policy and saved the policies.
/* no alarm when node is down */
sub main()
{
   s = FindSituation("NodeDown", %n);
   if (s != NULL)
   {
   if (s->status == 1)
   return false; //don't match rule
   }
   return true; //match rule
}


Then the NetXMS server (netxmsd) crashed.
Server is V1.2.14 on Linux x64. I send the debuglog (LogLevel=9) to [email protected]

Update:
When I write the filtering script without "sub main () {" and "}" the server does not crash. Maybe a bug? Or my fault?
#36
General Support / Syslog from source <unknown>
July 07, 2014, 07:47:04 PM
We just changed our internet gateway (same manufacturer but a bigger device model). In NetXMS I left the existing node, changed the node name and started configuration-, interface-name- and topology poll. All DCIs are still ok.
But the syslog messages from the new gateway arrive at the NetXMS-syslog-server with source <unknown>. The new gateway has the same IP address as the old. Maybe the gateway uses a wrong source interface to send the syslog messages. Is there an easy way to see the source IP address of the syslog messages in NetXMS server? As long as I know NetXMS is mapping incoming syslog messages by source IP adress to existing nodes. Right? On the other side SNMP Traps are working, source node is ok there. Or does anybody has an idea what could be wrong? Thank's in advance!

Addition:
I checked the source IP address of the syslog packets with wireshark. All syslog packets arrives with the primary IP address of this node. So the cause must be something else.
#37
General Support / ConditionStatus()
June 26, 2014, 10:08:40 AM
I tried to use the internal DCI ConditionStatus() on a node to read the status of a condition. As I read in the forum the node must be in the trusted node list of the condition. But there is no trusted node list in condition (V1.2.14).
And what is the argument of ConditionStatus()? The condition "name" or the "Object ID"?
#38
When we want to change object tools in our NetXMS installation (V1.2.14) we get database errors like:

[ERROR] SQL query failed (Query = "DELETE FROM object_tools_acl WHERE tool_id=?"): 08P01 ERROR:  bind message supplies 9 parameters, but prepared statement "netxms_stmt_0x7f51d4056c40_1403626097" requires 1


What can we do to fix it? Thanks in advance
#39
We have nodes (HPserver) with DCIs only on the node itself but with Proxy nodes (iLO). Now Instance discovery is not working in DCIs (SNMP) on nodes (HPserver) with Proxy nodes (iLO). No instances are generated (I started configuration polls). The DCI is a simple SNMP one and the discovery is simple SNMP-Walk-OID on the same OID with no filtering script.
Is instance discovery not possible with Proxy nodes on the DCI?
#40
When I delete DCIs from templates (not from nodes) I always get errors like this:

Critical SYS_DB_QUERY_FAILED Database query failed (Query: DELETE FROM idata_1174 WHERE item_id=1354; Error: 42P01 ERROR:  relation "idata_1174" does not exist
LINE 1: DELETE FROM idata_1174 WHERE item_id=1354
Critical SYS_DB_QUERY_FAILED Database query failed (Query: DELETE FROM idata_384 WHERE item_id=526; Error: 42P01 ERROR:  relation "idata_384" does not exist
LINE 1: DELETE FROM idata_384 WHERE item_id=526
Critical SYS_DB_QUERY_FAILED Database query failed (Query: DELETE FROM idata_1139 WHERE item_id=825; Error: 42P01 ERROR:  relation "idata_1139" does not exist
LINE 1: DELETE FROM idata_1139 WHERE item_id=825


It's for older and for newly created DCIs in templates. NetXMS is V1.2.14.