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

Messages - Marco Incalcaterra

#166
General Support / Re: Possible Bug 1.2.7 (SNMP)
June 20, 2013, 10:39:21 PM
It works properly for me. Did you change anything in your configuration?

Best regards,
Marco
#167
Hi,

I'm sorry but this is out of my knowledge, I don't know! I have only static IPs on my networks, this is why I did not encounter that kind of problem (and I did not dig to solve it  :P )

Marco
#168
Yes, I forgot the "-D 9" :)

I have a very similar output (at least the initial part, then it starts to collect the requests from the proxy).
Here the log from my REMOTEPC:

C:\Users\marco>"C:\Program Files\NetXMS\bin\nxagentd.exe" -D 9 -c "C:\Program Files\NetXMS\etc\nxagentd.conf"
[19-Jun-2013 19:33:47.870] Additional configs was loaded from C:\Program Files\NetXMS\etc\nxagentd.conf.d
[19-Jun-2013 19:33:47.870] Debug level set to 9
[19-Jun-2013 19:33:47.870] Subagent API initialized
[19-Jun-2013 19:33:47.870] Subagent "WINNT.NSM" loaded successfully
[19-Jun-2013 19:33:47.870] Debug callback set for DB library
[19-Jun-2013 19:33:47.995] WINPERF: CollectorThread_A waiting for set change
[19-Jun-2013 19:33:47.995] WINPERF: CollectorThread_B waiting for set change
[19-Jun-2013 19:33:47.995] Subagent "winperf.nsm" loaded successfully
[19-Jun-2013 19:33:47.995] WINPERF: CollectorThread_C waiting for set change
[19-Jun-2013 19:33:47.995] WINPERF: CollectorThread_A: set changed
[19-Jun-2013 19:33:47.995] WINPERF: CollectorThread_A entered data collection loop
[19-Jun-2013 19:33:48.995] External parameters providers poller thread will notstart
[19-Jun-2013 19:33:48.995] StorageDiscoveryConnector: named pipe created, waiting for connection
[19-Jun-2013 19:33:48.995] PushConnector: named pipe created, waiting for connection
[19-Jun-2013 19:33:48.995] Trying to bind on 0.0.0.0:4700
[19-Jun-2013 19:33:48.995] Listening on socket 0.0.0.0:4700
[19-Jun-2013 19:33:49.994] NetXMS Agent started
Agent running. Press ESC to shutdown.
[19-Jun-2013 19:34:13.301] Incoming connection from 192.168.10.3
[19-Jun-2013 19:34:13.301] Connection from 192.168.10.3 accepted
[19-Jun-2013 19:34:13.426] [session:0] Received message CMD_KEEPALIVE
[19-Jun-2013 19:34:13.426] [session:0] Sending message CMD_REQUEST_COMPLETED (size 32)
[19-Jun-2013 19:34:13.458] [session:0] Received message CMD_ENABLE_AGENT_TRAPS
[19-Jun-2013 19:34:13.458] [session:0] Sending message CMD_REQUEST_COMPLETED (size 32)
[19-Jun-2013 19:34:13.598] [session:0] Received message CMD_GET_PARAMETER
[19-Jun-2013 19:34:13.598] [session:0] Requesting parameter "Net.Interface.AdminStatus(11)"
[19-Jun-2013 19:34:13.598] [session:0] GetParameterValue(): result is 0 (SUCCESS)
[19-Jun-2013 19:34:13.598] [session:0] Sending message CMD_REQUEST_COMPLETED (size 48)
[19-Jun-2013 19:34:13.629] [session:0] Received message CMD_GET_PARAMETER
[19-Jun-2013 19:34:13.629] [session:0] Requesting parameter "Net.Interface.Link(11)"
[19-Jun-2013 19:34:13.629] [session:0] GetParameterValue(): result is 0 (SUCCESS)
[19-Jun-2013 19:34:13.629] [session:0] Sending message CMD_REQUEST_COMPLETED (size 48)
[19-Jun-2013 19:34:19.534] [session:0] Received message CMD_GET_PARAMETER
[19-Jun-2013 19:34:19.534] [session:0] Requesting parameter "Net.Interface.BytesIn("Local Area Connection")"
[19-Jun-2013 19:34:19.534] [session:0] GetParameterValue(): result is 0 (SUCCESS)
[19-Jun-2013 19:34:19.534] [session:0] Sending message CMD_REQUEST_COMPLETED (size 64)
Agent shutting down...
[19-Jun-2013 19:34:21.190] Shutdown() called
[19-Jun-2013 19:34:21.190] Trap sender thread terminated
[19-Jun-2013 19:34:21.987] [session:0] CommSession::disconnect()
[19-Jun-2013 19:34:21.987] [session:0] Session with 192.168.10.3 closed
[19-Jun-2013 19:34:22.987] Session Watchdog thread terminated
[19-Jun-2013 19:34:22.987] Listener thread terminated
[19-Jun-2013 19:34:22.987] WINPERF: Collector thread for counter set B terminated
[19-Jun-2013 19:34:22.987] WINPERF: Collector thread for counter set A terminated
[19-Jun-2013 19:34:22.987] WINPERF: Collector thread for counter set C terminated
[19-Jun-2013 19:34:23.486] NetXMS Agent stopped


192.168.10.3 is the internal network IP of my proxy.
Did you try to put the IP address directly instead of the DNS name in the REMOTEPC name?
Do the AGENTPROXY and REMOTEPC belongs to the same subnet?

Best regards,
Marco
#169
Hi,

I have exactly the same configuration of you. No other port needs to be opened than tcp/4700.
Could you please try to dump the poll status from the manual execution of the agent on both AGENTPROXY and REMOTEPC: run the agent in dump mode on both nodes and run a poll status from NetXMS console. Here an example on how I run it on my node:

"C:\Program Files\NetXMS\bin\nxagentd.exe" -c "C:\Program Files\NetXMS\etc\nxagentd.conf" -n "NetXMSAgentdW32" -e "NetXMS Win32 Agent")

Best regards,
Marco
#170
The only point I did not understand in your configuration is if the AGENTPROXY is assigned to a zone. In my configuration AGENTPROXY is not assigned to a zone and REMOTEPC is assigned to a zone.

I have two proxies for two different zones in my NetXMS and everything works fine.

Best regards,
Marco
#171
Hi,

If current user is not an administrator installer should ask to run with elevated privileges, did it ask?

If user is not an administrator you can try to:

1) Force installer to run as administrator (right mouse button on program e chose "Run as administrator"
2) Temporary promote current user to belong to administrator group (ad then demote it after install/config is finished)
3) Disable (temporary) the UAC (User Access Control), from "Control Panel"|"User Accounts"|"User Accounts"|"Change User Account Control settings"|"Never notify"

Hope this help.

Best regards,
Marco
#172
General Support / Re: DCI Alarms not raised!
March 28, 2013, 08:20:42 PM
Quote from: tivanni on March 28, 2013, 07:48:15 PM
Hi,

first, thank you the answer.

In your example, you configure the event configuration policy and the action to obtain netxms sent an email every time the threshold is exceeded, and this is ok.
But, in this time, i'm not interested in get the mail.
Normally, when you use DCI, it's not required to configure a customized event, but you can use the standard event for Threshold "SYS_THRESHOLD_REACHED".
And if you configure a Threshold for a DCI, when the event occour a popup with the allarm message appear on the console and you can see the alarm in the alarm menu of this object.
In my case is like netxms don't see the actual value is greater than the threshold.

I'm sorry but I have exactly the same behaviour using the default event (SYS_THRESHOLD_REACHED) either with values collected by agent or by SNMP. The threshold status is properly updated in the threshold column (Last values tab) as soon as the threshold is reached but nothing else is popped up and/or notified. Maybe I'm not understanding your problem!

Best regards,
Marco
#173
General Support / Re: DCI Alarms not raised!
March 28, 2013, 05:44:57 PM
Quote from: tivanni on March 28, 2013, 05:26:24 PM
Hi!

i have a IBM server and i want to monitor his temperature, voltage etc... So i get this data through snmp, and for each data i create a data collection item.
For each data collection item, i create a threshold: if last  polled value is greater than x, an event is raised!... But, didn't work!
The actual value of the DCI is greater than the threshold but no alarms appear! I test this with 2 different DCI, but the result is the same.
I try to use all the different choice of Data Input for the DCI (Integer, Unsigned Integer, etc) but nothing change.
I have configured several type of alarms with other DCI and all of this works, the unique difference is the value of this DCI are collected by Netxms Agent and not by SNMP.
How can I fix this?
I'm running netxms 1.2.5 on Debian 32 bit.
Thank you!

You should define your event and how it should be processed (such as send an email or wathever else). Have a look to the example here attached. I defined a threshold to send me an alarm when HDD space free is less that 5%. Hope it helps.

Best regards,
Marco
#174
Quote from: Victor Kirhenshtein on March 18, 2013, 09:44:57 PM

2. Try to build a logical-to-physical hierarchy, like this:

Node
  +-- IP interface 1 (IP address)
     +-- Physical Interface 1 (MAC address)
  +-- IP interface 2 (IP address)
     +-- Physical Interface 1 (MAC address)
  +-- IPv6 interface 1 (IPv6 address)
     +-- Physical Interface 1 (MAC address)
  +-- IP interface 3 (IP address)
     +-- Team 1
        +-- Physical Interface 2 (MAC address)
        +-- Physical Interface 3 (MAC address)

What do you think?

Best regards,
Victor

I personally like more the second option but I don't think that will solve the Peter's problem. In Hyper-V a NIC dedicated to a virtual switch doesn't have an IP, so I guess that it cannot be shown in that hierarchy.

Best regards,
Marco.
#175
Quote from: peterjn on March 18, 2013, 06:40:37 PM
Example a linux box has 2 NIC, NIC 1 has IP address A and NIC 2 is has IP address B. I have PC connect to NIC 2 and NIC 1 is not connected (down). When I ping IP address A from the PC I wil get a reply. So a ping to IP address A says nothing about the status of NIC 1. It only tells that IP address A is configured on the box.
Windows is a little more complex. When a NIC driver report that the link is down the IP address is removed.
But when a NIC is broken (reports false UP) windows wil do the same as linux.

I don't have experience on linux, only on Windows, that was the reason of my trouble to follow you.

Regarding Windows I have a different experience. With disconnected cable the IP is not removed, loopback is still available and pingable from within the PC - where the NIC is installed - if the link was up at least one time in the current session (i.e. up to the next reboot of the PC). No loopback if you rebooted the PC and link had never been up.

Best regards,
Marco
#176
Quote from: peterjn on March 18, 2013, 11:54:27 AMA NIC can be down or broken and the system will still response to the IP address linked that NIC (using a other NIC).

Hera I'm a bit in trouble to follow you, maybe depends on definition of "down" and "broken" :)

Quote from: peterjn on March 18, 2013, 11:54:27 AM
One of the reason for my original posting was that we have problems with a NIC linked to the software Hyper-V switch and I want to monitor this. Currently this is not possible.

Best regards,
Peter

In my Hyper-V I have agents running in the VMs, if there is a communication problem with the NIC of the server I'm unable to communicate with the VMs. I use that as first indicator, may be that could be useful for a basic diagnosis even in your case.

Best regards,
Marco
#177
Quote from: Victor Kirhenshtein on March 11, 2013, 08:44:29 PM
NetXMS counts each logical interface as separate object. I'm thinking about changing this to have multiple IP addresses on one interface, but decision is not made yet.

Best regards,
Victor

In my opinion, since the MAC address is unique, each interface should be identified by the MAC address and all the IPs associated to that interface should be reported as a list, possibily with corresponding net mask and gateway (if present).

Best regards,
Marco
#178
Quote from: peterjn on March 06, 2013, 11:04:26 PM
I have 2 problems

Windows 2008 R2 Hyper-V host (nsagent 1.2.6 installed)
If a nic is used by the Hyper-V network switch (only bound to Microsoft Virtual Network Switch Protocol). It is not showing up in the console.

You'll be able to see it only selecting "Allow management operating system to share this network adapter" (see attachment). Otherwise Windows will hide from the list of adapters so NetXMS will not be able to enumerate it.

Quote from: peterjn on March 06, 2013, 11:04:26 PM
Linux firewall (snmpd)
If a nic has multple IP addresses I get the same nic multiple times.

Is there a fix for this or workaround?

Same story in Windows if you have multiple IPs on the same NIC for a PC. I'm not aware of workaround.

Best regards,
Marco
#179
General Support / Re: Android console app question
February 15, 2013, 12:18:02 PM
Quote from: DanG on February 14, 2013, 10:38:35 PM
Hi Marco,

Thanks for replying!

I do indeed get the connection failed message - my bad. I guess I expected it to be more prominent while setting things up (maybe a popup error?). BTW, as I was testing things to reply I discovered that if I change the server name (I use an IP address) the new value is not being used. I need to "disconnect & exit" and restart the app to make the new value take effect (changing the name or password does work immediately).

Looking forward to the next version ;-)
Dan

Issue #239 solved, regarding the notification of the connection error you have also info in the status bar if you enable it.

Regarding the changing of server address, I guess that the behaviour is due because there is no force disconnect of current session after changing the parameters. I've added the issue to the bugratcker:

https://www.radensolutions.com/chiliproject/issues/241

Best regards,
Marco
#180
General Support / Re: Android console app question
February 13, 2013, 03:57:26 PM
Quote from: DanG on February 12, 2013, 01:33:34 PM
- No error message with wrong password
You should get a "Connection failed: Access denied" message, in red color, under the "Home" title. You should get also the same error message in the status bar and as "toast" if those notifications are enabled.

Quote from: DanG on February 12, 2013, 01:33:34 PM
- missing refresh button at dashboards and other screens. I guess screeb auto-update, but sometimes they don't.
Dashboard should autorefresh, graphs not yet.

Quote from: DanG on February 12, 2013, 01:33:34 PM
- graph containing a lot of data do no appear, as there's no progress indication I can't say if it takes (too) long or just doesn't.
Issue added to bugtracker:
https://www.radensolutions.com/chiliproject/issues/239

Quote from: DanG on February 12, 2013, 01:33:34 PM
- missing the ability to scale graphs (text too small to read)
Space on smartphone is limited, I'll try to elaborate a solution. Issue added to bugtracker:
https://www.radensolutions.com/chiliproject/issues/240

Best regards,
Marco