News:

We really need your input in this questionnaire

Main Menu
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 - Nikk

#16
General Support / Re: Problem with SNMP
November 24, 2014, 04:05:43 PM
Thank you!
#17
General Support / Re: Problem with SNMP
November 24, 2014, 03:38:49 PM
Hi,

Here I got response from switch manufacturer:
QuoteCause
These OIDs are time-filtered, so per the RFCs (e.g. RFC3512, RFC4502) must return entries for all valid timeMarks.

The SNMP browser should understand the behavior of a timeFiltered MIB and move on after seeing the timeFilter index increment. However, not all browsers behave in this manner.

Solution/Workaround
Ensure you are using an appropriate SNMP tool - such as NetSight MIB tools - that behaves correctly.

Workaround:
DFE firmware 6.01.01.0020 introduced a new command which can accommodate SNMP browsers that are not timeFilter-aware.

Release notes state, in the "Software Changes and Enhancements" section:

A new SNMP control, "set snmp timefilter break", allows users to configure the
GET-NEXT behavior of MIBs indexed with timeMark. When this is set to 'enabled',
SNMP will not return incrementing index values. Many SNMP tools do not properly
support timefiltered MIBs and will benefit from this new setting. When disabled,
SNMP returns RFC conformant indexing.

Here is the command syntax, as seen in a sample cli session:
  NSeries(rw)->set snmp timefilter

  Command: set snmp Create SNMP agent entries

  Object: timefilter             SNMP timefilter configuration
  Usage:  set snmp timefilter break {disable | enable}

So maybe NetXMS doesn't support timeFiltered MIBs, or it could be something else?

Best Regards,
Nikk
#18
General Support / Re: Problem with SNMP
November 21, 2014, 11:54:32 AM
Yes, that walk is forming infinite loop, and is not stoping.

Regards,
Nikk
#19
General Support / Re: Problem with SNMP
November 19, 2014, 02:26:18 PM
So. here is the log:
Quote[19-Nov-2014 11:30:27.142] [DEBUG] StatusPoll(172.22.2.11): bAllDown=false, dynFlags=0x00001001
[19-Nov-2014 11:30:27.142] [DEBUG] [CLSN-0] Sending message CMD_OBJECT_UPDATE
[19-Nov-2014 11:30:27.142] [DEBUG] StatusPoll(172.22.2.11 [1338]): boot time set to 1402931335 from SNMP
[19-Nov-2014 11:30:27.142] [DEBUG] StatusPoll(172.22.2.11 [1338]): unable to get agent uptime
[19-Nov-2014 11:30:27.142] [DEBUG] Finished status poll for node 172.22.2.11 (ID: 1338)
[19-Nov-2014 11:30:28.392] [DEBUG] Node 1338 "172.22.2.11" queued for routing table poll
[19-Nov-2014 11:30:28.392] [DEBUG] Routing table updated for node 172.22.2.11 [1338]
[19-Nov-2014 11:31:28.408] [DEBUG] Node 1338 "172.22.2.11" queued for status poll
[19-Nov-2014 11:31:28.408] [DEBUG] Starting status poll for node 172.22.2.11 (ID: 1338)
[19-Nov-2014 11:31:28.408] [DEBUG] StatusPoll(172.22.2.11): check SNMP
[19-Nov-2014 11:31:28.408] [DEBUG] StatusPoll(172.22.2.11): SNMP check finished
[19-Nov-2014 11:31:28.916] [DEBUG] StatusPoll(172.22.2.11): bAllDown=false, dynFlags=0x00001001
[19-Nov-2014 11:31:28.918] [DEBUG] StatusPoll(172.22.2.11 [1338]): boot time set to 1402931334 from SNMP
[19-Nov-2014 11:31:28.918] [DEBUG] StatusPoll(172.22.2.11 [1338]): unable to get agent uptime
[19-Nov-2014 11:31:28.918] [DEBUG] Finished status poll for node 172.22.2.11 (ID: 1338)
[19-Nov-2014 11:32:33.491] [DEBUG] Node 1338 "172.22.2.11" queued for status poll
[19-Nov-2014 11:32:33.491] [DEBUG] Starting status poll for node 172.22.2.11 (ID: 1338)
[19-Nov-2014 11:32:33.491] [DEBUG] StatusPoll(172.22.2.11): check SNMP
[19-Nov-2014 11:32:33.491] [DEBUG] StatusPoll(172.22.2.11): SNMP check finished
[19-Nov-2014 11:32:33.979] [DEBUG] StatusPoll(172.22.2.11): bAllDown=false, dynFlags=0x00001001
[19-Nov-2014 11:32:33.979] [DEBUG] StatusPoll(172.22.2.11 [1338]): boot time set to 1402931334 from SNMP
[19-Nov-2014 11:32:33.979] [DEBUG] StatusPoll(172.22.2.11 [1338]): unable to get agent uptime
[19-Nov-2014 11:32:33.979] [DEBUG] Finished status poll for node 172.22.2.11 (ID: 1338)
[19-Nov-2014 11:33:38.495] [DEBUG] Node 1338 "172.22.2.11" queued for status poll
[19-Nov-2014 11:33:38.495] [DEBUG] Starting status poll for node 172.22.2.11 (ID: 1338)
[19-Nov-2014 11:33:38.495] [DEBUG] StatusPoll(172.22.2.11): check SNMP
[19-Nov-2014 11:33:38.495] [DEBUG] StatusPoll(172.22.2.11): SNMP check finished
[19-Nov-2014 11:33:39.026] [DEBUG] StatusPoll(172.22.2.11): bAllDown=false, dynFlags=0x00001001
[19-Nov-2014 11:33:39.026] [DEBUG] StatusPoll(172.22.2.11 [1338]): boot time set to 1402931335 from SNMP
[19-Nov-2014 11:33:39.026] [DEBUG] StatusPoll(172.22.2.11 [1338]): unable to get agent uptime
[19-Nov-2014 11:33:39.026] [DEBUG] Finished status poll for node 172.22.2.11 (ID: 1338)
[19-Nov-2014 11:34:43.496] [DEBUG] Node 1338 "172.22.2.11" queued for status poll
[19-Nov-2014 11:34:43.496] [DEBUG] Starting status poll for node 172.22.2.11 (ID: 1338)
[19-Nov-2014 11:34:43.496] [DEBUG] StatusPoll(172.22.2.11): check SNMP
[19-Nov-2014 11:34:43.496] [DEBUG] StatusPoll(172.22.2.11): SNMP check finished
[19-Nov-2014 11:34:44.012] [DEBUG] StatusPoll(172.22.2.11): bAllDown=false, dynFlags=0x00001001
[19-Nov-2014 11:34:44.012] [DEBUG] StatusPoll(172.22.2.11 [1338]): boot time set to 1402931335 from SNMP
[19-Nov-2014 11:34:44.012] [DEBUG] StatusPoll(172.22.2.11 [1338]): unable to get agent uptime
[19-Nov-2014 11:34:44.012] [DEBUG] Finished status poll for node 172.22.2.11 (ID: 1338)
[19-Nov-2014 11:35:33.497] [DEBUG] Node 1338 "172.22.2.11" queued for routing table poll
[19-Nov-2014 11:35:33.497] [DEBUG] Routing table updated for node 172.22.2.11 [1338]
[19-Nov-2014 11:35:48.497] [DEBUG] Node 1338 "172.22.2.11" queued for status poll
[19-Nov-2014 11:35:48.497] [DEBUG] Starting status poll for node 172.22.2.11 (ID: 1338)
[19-Nov-2014 11:35:48.497] [DEBUG] StatusPoll(172.22.2.11): check SNMP
[19-Nov-2014 11:35:48.497] [DEBUG] StatusPoll(172.22.2.11): SNMP check finished
[19-Nov-2014 11:35:48.981] [DEBUG] StatusPoll(172.22.2.11): bAllDown=false, dynFlags=0x00001001
[19-Nov-2014 11:35:48.981] [DEBUG] StatusPoll(172.22.2.11 [1338]): boot time set to 1402931334 from SNMP
[19-Nov-2014 11:35:48.981] [DEBUG] StatusPoll(172.22.2.11 [1338]): unable to get agent uptime
[19-Nov-2014 11:35:48.981] [DEBUG] Finished status poll for node 172.22.2.11 (ID: 1338)
[19-Nov-2014 11:36:53.497] [DEBUG] Node 1338 "172.22.2.11" queued for status poll
[19-Nov-2014 11:36:53.497] [DEBUG] Starting status poll for node 172.22.2.11 (ID: 1338)
[19-Nov-2014 11:36:53.497] [DEBUG] StatusPoll(172.22.2.11): check SNMP
[19-Nov-2014 11:36:53.497] [DEBUG] StatusPoll(172.22.2.11): SNMP check finished
[19-Nov-2014 11:36:53.903] [DEBUG] StatusPoll(172.22.2.11): bAllDown=false, dynFlags=0x00001001
[19-Nov-2014 11:36:53.919] [DEBUG] StatusPoll(172.22.2.11 [1338]): boot time set to 1402931334 from SNMP
[19-Nov-2014 11:36:53.919] [DEBUG] StatusPoll(172.22.2.11 [1338]): unable to get agent uptime
[19-Nov-2014 11:36:53.919] [DEBUG] Finished status poll for node 172.22.2.11 (ID: 1338)
[19-Nov-2014 11:37:18.498] [DEBUG] Node 1338 "172.22.2.11" queued for topology poll
[19-Nov-2014 11:37:18.498] [DEBUG] Started topology poll for node 172.22.2.11 [1338]
[19-Nov-2014 11:37:58.512] [DEBUG] Node 1338 "172.22.2.11" queued for status poll
[19-Nov-2014 11:40:38.589] [DEBUG] Node 1338 "172.22.2.11" queued for routing table poll
[19-Nov-2014 11:40:38.589] [DEBUG] Routing table updated for node 172.22.2.11 [1338]
[19-Nov-2014 11:45:43.607] [DEBUG] Node 1338 "172.22.2.11" queued for routing table poll
[19-Nov-2014 11:45:43.607] [DEBUG] Routing table updated for node 172.22.2.11 [1338]
[19-Nov-2014 11:50:24.953] [DEBUG] CorrelateEvent: event SYS_NODE_UNMANAGED id 4676 source 172.22.2.11 [1338]
[19-Nov-2014 11:50:24.953] [DEBUG] CorrelateEvent: finished, rootId=0
[19-Nov-2014 11:50:24.953] [DEBUG] [CLSN-0] Sending message CMD_OBJECT_UPDATE
[19-Nov-2014 11:50:24.953] [DEBUG] EVENT 12 (ID:4676 F:0x0001 S:0 TAG:"") FROM 172.22.2.11: Node status changed to UNMANAGED

At the end I changed status to unmanaged, but as I saw in Wireshark:
Quote4078950   3192.569851000   172.22.5.95   172.22.2.11   SNMP   93 get-next-request 1.3.6.1.2.1.17.7.1.4.2.1.4.56088.140
4078952   3192.571206000   172.22.2.11   172.22.5.95   SNMP   141   get-response 1.3.6.1.2.1.17.7.1.4.2.1.4.56088.153

It still keeps spamming this oid, but in server log nothing appears from that node (after unmanaging it).
#20
General Support / Re: Problem with SNMP
November 12, 2014, 11:58:20 AM
Yes, there is topology poll, and it just keeps requesting this  oid: 1.3.6.1.2.1.17.7.1.4.2.1.4. even if I disable topology polling.
#21
General Support / Re: Problem with SNMP
October 31, 2014, 11:21:47 AM
Upgraded from 1.2.16 to 1.2.17, but the problem still persists. The most annoying thing is, i can't stop the 'snmp get' from NetXMS.
#22
General Support / Problem with SNMP
October 29, 2014, 04:53:53 PM
Hi,

I recently placed a new Netxms server at remote site, and added a few core switches (Enterasys S3, S4) to the monitoring. I haven't set up yet any parameters to monitor (there are just the default ones). So there shouldn't be much load.
The problem is, these switches  get load of SNMP coming to them -> their processor jumps up to 90%. I tried unmanaging the nodes, disabling all pollings and even deleted the node at the end, but this SNMP kept going (as seen in Wireshark).
The SNMP mib was 1.3.6.1.2.1.17.7.1.4.2.1.4.X.X

It stops only, when I restart agent or server. In server log file, i didn't notice anything odd.

Is NetXMS generating this, or something else, as i haven't noticed this behavior on other servers.

Regards,
Nikk
#23
General Support / Re: Receive messages from Zabbix
July 24, 2014, 04:28:18 PM
Thank you, will give a try.
#24
General Support / Receive messages from Zabbix
July 24, 2014, 03:14:54 PM
Hi,

We have a situation where we are using NetXMS as main monitoring system, but our client is using Zabbix and they just can't change the systems at the moment. The goal is to see everything about servers and network devices on our main NetXMS server. Is there a chance to somehow send events or something like that to NetXMS agent or server which resides on their location, or it can just send straight to main server?

Regards,
Nikk
#26
General Support / HP mibs
June 05, 2014, 01:06:48 PM
Hi,

When adding these mibs - https://h10145.www1.hp.com/Downloads/ProductsList.aspx?lang=en&cc=us&prodSeriesId=3356808&lang=en&cc=us

I get many import symbol unresolved errors to netxms default mibs.  "MODULE-IDENTITY", "OBJECT-TYPE" and others. They all are from SNMPV2-SMI. Without them, everything is fine.

Same issues as here: https://www.netxms.org/forum/installation/hp-switch-mibs/msg7017/#msg7017
What should i change there?

Regards,
Nikk
#27
Yes, for instanced dcis.

I have checked history and snmpwalk, these values have never been more than 0, see attachment.
#28
General Support / Re: GetDCI
May 29, 2014, 08:50:11 PM
Sorry for late answer, been busy.

I checked with nxget and it returned non-zero value.
#29
General Support / Re: Distributed Monitoring
May 19, 2014, 04:40:46 PM
You should enable EnableISCListener and ReceiveForwardedEvents in server configuration and open port 4702. And on both sides events and nodes should match. This works localy only.
#30
Thanks for correcting me!

I tried your given script, but still getting 0 values.

I guess i'm doing something wrong, or i haven't given all the necessary information.