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

#1
Hi All
First: Thank's for the new V3 Release. We would like to migrate the current installation to a new server.
Old:openSUSE (old version)NetXMS 2.2.17 (from sources)PostgreSQL
New:openSUSE Leap 15.1NetXMS 3.0.x (compiled from sources)
Timescale DB
What would be the best migration path? On the old server we cannot update to NetXMS V3 because of missing libprce32. It's important that we can migrate the existing DB to the new one.
best regardsDani

#2
Hi
I just set up a new 'normal' local user (read only rights) in NetXMS 2.2.13. Logon in Webinterface is ok, but logon in management console gives error:'Open user databse' has encountered a problemCannot lock user database: Access denied
Any ideas?
thanks
Dani
#3
General Support / npi files in the new download area?
October 25, 2018, 05:17:07 PM
Hi
Where can I get the npi files for windows agents on the new download site (https://www.netxms.org/download/)?
thanksDani
#4
Hi

Since update from 2.2.2 to 2.2.3 we have a problem in events generated from syslog parser on NetXMS server. The source node information is missing. The syslog messages in NetXMS has source node information. It only lacks in events. No change in syslog parser config since update.
Is it a known error? What can we do?

best regards
Dani
#5
Hi

I get the following error compiling UBNT-UniFi-MIB.txt:
UBNT-UniFi-MIB: ERROR 001: Import symbol "ubntUniFiGroups" unresolved
The MIB from where this should be imported (UBNT-MID.txt) is also in MIB directory. I attached both MIBs to this thread.

In UBNT-MIB.txt I see this definition:
   ubntUniFi OBJECT IDENTIFIER ::= { ubntMIB 6 }

Can someone help?

thanks
Dani

edit: replaced UBNT-MIB.txt
#6
General Support / NetXMS 3.x?
January 08, 2018, 06:52:55 PM
Hi

I heard a rumor about a major release NetXMS 3.x. Is there any information about?

best regards
Dani
#7
Hi

We have updated from NetXMS 2.1.2 to 2.2.1. After that PING subagent makes problems. We have nodes with NetXMS agents (linux and windows) which are pinging some targets. Other nodes get the results from these 'pinging'-agent nodes. Everything went fine with V2.1.2.

Now with V2.2.1 I get in debug log (level=9) of the pinging-agents the error 404 (unknown_parameter), but not for all targets.

edit1: it's for all targets, I checked the DCIs.



2017.12.08 16:27:47.063 *D* [VCS-3996] Requesting parameter "Icmp.PacketLoss(gw2.domain.intern)"
2017.12.08 16:27:47.063 *D* [VCS-3996] GetParameterValue(): result is 404 (UNKNOWN_PARAMETER)
2017.12.08 16:27:47.063 *D* [VCS-3997] Requesting parameter "Icmp.AvgPingTime(gw2.domain.intern)"
2017.12.08 16:27:47.063 *D* [VCS-3997] GetParameterValue(): result is 404 (UNKNOWN_PARAMETER)
2017.12.08 16:27:47.063 *D* [VCS-3998] Requesting parameter "Icmp.PacketLoss(gw1.domain2.intern)"
2017.12.08 16:27:47.063 *D* [VCS-3998] GetParameterValue(): result is 404 (UNKNOWN_PARAMETER)
2017.12.08 16:27:47.063 *D* [VCS-3999] Requesting parameter "Icmp.AvgPingTime(gw1.domain2.intern)"
2017.12.08 16:27:47.063 *D* [VCS-3994] GetParameterValue(): result is 0 (SUCCESS)


The ping section of the agent config has no difference between working and not working targets:

[ping]
DefaultPacketSize = 46
Timeout = 2000
PacketRate = 24
Target = 172.16.10.1:gw1.domain.intern
Target = 172.16.50.1:gw2.domain.intern
Target = 172.16.20.1:gw1.domain2.intern


I didn't changed anything in config after update.

thanks
Dani

edit2: server is linux compiled from sources, agents on Windows are binary packages.
#8
Hi

We see frequent critical events like this:


Database query failed (Query: INSERT INTO ap_common (policy_type,version,id) VALUES (?,?,?); Error: 23505 ERROR: duplicate key value violates unique constraint "ap_common_pkey"DETAIL: Key (id)=(1816) already exists.)

where ids are different. I checked all affected ids are really existing in db table.

Install is NetXMS 2.1.2 on linux, db is PostgreSQL

thanks for any help
Dani
#9
Hi

We set up a few nodes in one subnet /16 nad integrated them in NetXMS. So we got there also one subnet /16.
Now for production they have the same IP addresses as in test but are all in separated different /30 subnets.
Now we get a lot of events in NetXMS 'invalif network mask 30 on interface xy, should be 16.
How we can change this in NetXMS without deleting all these nodes?

best regards
Dani
#10
General Support / V2.1-M3 ready?
March 28, 2017, 12:11:34 PM
Hi

V2.1-M3 with changelog is in the beta download section. But there was no announcement in the forum. Is it ready for update?

thanks
Dani
#11
General Support / After Update to V2.1-M2 No Alarms
January 20, 2017, 06:53:20 PM
Since update from V2.1-M1 to V2.1-M2 I see troubles with alarms.

I have nodes which has status 'warning' since before update, after update they have still status 'warning' but I can't see any alarms on these nodes anymore. Before update there were not answered alarms on these nodes.

I tested on another node the following:
I switched of the device, the status of this node changed to Critical, but also no alarm on alarm-tab.

I see no alarms anymore in general. Alarm browser is completely empty.

But we get the alarm emails.

There is something broken with alarms. Which additional information do you need for further troubleshooting?

thanks
Dani
#12
Hi

I have an installation of NetXMS V2.1-M1 on Linux.
I'm not 100% sure, but I think the problem appeared with the update from V2.0.6. There is a local Postfix installation on the NetXMS server itself for relaying outgoing mails to mail server of Microsoft Exchange Online by TLS. In NetXMS server 'SMTPServer = localhost'. That worked fine in V2.0.6. But now no mails arrive at the Postfix server. I set DebugLevel of the NetXMS server to 6 and I see in the log:

"...EVENT SYS_SMTP_FAILURE [22]... Unable to resolve SMTP server name"

What I tried yet:

       
  • send mail on command line on the NetXMS server (by nc or telnet) to the local Postfix server (same receipient, same sender) -> works
  • searched for ingoing mails in Postfix logs -> no mails
  • changed server conf value SMTPServer to '127.0.0.1' (so no name resolution necessairy) -> not working
  • changed server conf value SMTPServer to FQDN of server -> not working
What can I do to further troubleshoot this? As we cannot get any mails from NetXMS now.

Thanks
Dani

edit: typos and precision

#13
I have a ICMP DCI (Icmp.Packetloss)on a node with another node as source node. When I change the polling intervall of this DCI, the change is not applied. I need to restart the NetXMS agent on the proxy node to get the change applied. What's the reason? bug or by design?

Installation  is NetXMS V2.0.5 on linux x64 build from sources. Agents V2.0.5 on Windows.

thanks
Dani
#14
We have one subnet twice under 'entire network'. Both the same network and the same netmask, different object IDs in NetXMS and all nodes are listed under both network objects.

NetXMS version is V2.0.4 on linux x64 built from sources. How can I fix that?

thanks
Dani
#15
Hi

I observe the following problem for some time:
We have some sites connected by VPN connections.
When a VPN connection goes down and up again, the NetXMS server reports the remote VPN-gateway as 'snmp agent unreachable'. When I manually do a status Poll on a remote node I get 'node is connected' but also 'snmp agent unreachable'.

My findings so far:

  • SNMP to all other nodes in the same remote sites is ok
  • RuntimeFlags is 0x1010 on the remote VPN-gateway node
  • snmpwalk for remote VPN-gateway on command line of NetXMS server is ok
  • nxsnmpwalk for remote VPN-gateway on command line of NetXMS server is ok too
  • restart of netxmsd fix the problem for the moment
  • remote VPN-gateway and local VPN-gateways has VPN connectors in NetXMS configured
  • in server debug log I found the following

[19-May-2016 18:28:50.789] [DEBUG] Node(vpn-gateway.domain.intern)->GetItemFromSNMP(.1.3.6.1.2.1.1.3.0): dwResult=17
[19-May-2016 18:28:50.789] [DEBUG] StatusPoll(vpn-gateway.domain.intern [951]): unable to get system uptime
[19-May-2016 18:28:50.789] [DEBUG] StatusPoll(vpn-gateway.domain.intern [951]): unable to get agent uptime
[19-May-2016 18:28:50.789] [DEBUG] StatusPoll(vpn-gateway.domain.intern [951]): unable to get system location
[19-May-2016 18:28:50.789] [DEBUG] Finished status poll for node vpn-gateway.domain.intern (ID: 951)
[19-May-2016 18:28:50.789] [DEBUG] ConfigReadStr: (cached) name=DeleteUnreachableNodesPeriod value="0"
...
[19-May-2016 18:30:07.540] [DEBUG] Node(vpn-gateway.domain.intern)->GetItemFromSNMP(.1.3.6.1.4.1.890.1.6.22.1.6.0): dwResult=4


What could be the best next steps for troubleshooting?

NetXMS server is V2.0.3 on Linux x64 built from sources.

thanks
Dani
#16
We see from time to time this error in server log:

[ERROR] SQL query failed (Query = "INSERT INTO tdata_1466 (item_id,tdata_timestamp,record_id) VALUES (?,?,?)"): 23505 ERROR:  duplicate key value violates unique constraint "tdata_1466_record_id_key "
DETAIL:  Key (record_id)=(1558995887784001536) already exists.


We are on NetXMS V2.0 on PostgreSQL.

How can we fix this?
#17
We are using NetXMS V2.0-RC2. We configured the NetXMS agents by policies (Windows and Linux). I just wanted to change something in an existing policy. Now all but one node assignments are disappeared in the console!

Is something in the agent configuration policy feature broken in V2.0-RC2?

edit:
I can reinstall the policies on the nodes, then they appear again in the console under the policy. Maybe an upgrade or database problem?

Thanks
Dani
#18
We have the following situation on a Cisco Switch ('switch1', LLDP enabled):

switch1 Port1:
Connected to a second switch ('switch2') by a VLAN trunk port.
In Object Details of switch1 I can see on interface tab for Port1 peer node 'switch2.domain.com', peer discovery protocol is LLDP.
In Tools - Info - Topology Table (LLDP) on switch1 I can see as system name of the peer 'switch2'.
So everything is fine here

switch1 Port2:
Connected to an WLAN AP ('ap1') by a VLAN trunk port.
In Object Details of switch1 I can see no peer node on interface tab for Port2.
In Tools - Info - Topology Table (LLDP) on switch1 I can see as system name of the peer 'ap1.domain.com'.
Is it possible that NetXMS cannot recognition the peer if it sends FQDN instead of pure hostname?
What is the standard for LLDP system name?
#19
General Support / Object Filter in Layer3-Maps
July 06, 2015, 05:31:20 PM
I have a Layer3 map where I only want nodes from container 'London'.

I tried with the following filter script but got always all nodes instead of only those in container 'London':

parents = GetNodeParents((FindObject($1));
if (parents == null) return false;
foreach(p : parents)
{
   if (p->type == 5 && p->name == "London") return true;
}
return false;



  • Do I have a typo or an error in reasoning?
  • What is the input of the filtering script? An object? An ID? (didn't found it in documentation)
  • When you temporarily disable the filter, the filtering script will be deleted (bug or feature?)

Thanks for any input!
#20
Hi

In VPN-Connector it's not possible to set the peer gateway anymore . You can choose one and exit with 'ok'. But if you open the VPN connector configuration again the field 'Peer gateway' ist '<none>' again. I use the java console on Win-x64. The server is V2.0-M5 on linux-x64 compiled from sources.
Is this a known bug? If yes, is there a workaround?

Edit:
I narrowed down the problem.
When you create a new VPN connector, than edit this connector filling in the peer gateway, the local and the remote networks, everything is ok.
But when you create a new VPN connector, than edit this connector filling in only the local and the remote networks (missing the peer gateway) and finish with 'ok'. Than you edit the VPN connection again filling in the missing peer gateway, this field will not be saved!

thanks
Dani