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 - brettmilfos

#1
General Support / Re: openssl
June 14, 2023, 02:22:26 AM
Thanks, and yes I was asking about the windows version.
#2
General Support / openssl
June 06, 2023, 02:52:16 AM
Hi,

Is there a timeframe for a release of NetXMS that has the latest openssl to address the recent CVEs?

Thanks, Brett.
#3
Quote from: Victor Kirhenshtein on November 22, 2019, 01:28:19 PM
Where exactly it is not saved? In node properties? Or in global settings?

Node properties.
#4
Quote from: vasnam23 on November 07, 2019, 08:30:42 PM
I just noticed SNMP community is not being updated/saved. it only saves it if it is no longer than 3 characters long... Anyone else has such problem?

Yes.. I have had this problem. Along with the commiinty string being ignored and either publkic or a blank string being used.
#5
Quote from: Victor Kirhenshtein on September 27, 2019, 06:54:34 PM
Hi,

we don't have other reports for such behavior, even for quite large deployments. Please turn on debug logging on proxy and server to level 6 and send part of the logs for period when one such issue experienced.

Best regards,
Victor

Hi Victor,

Sorry for the delay.

Have had a close look and the issue seems to be with the SNMP Community string. I use custom community strings for each device type.

Nodes that are being proxied by the agent seem to randomly forget the manually configured string and default to using public as well as resting the SNMP Version to 1.

Any attempt to manually enter the correct string in the GUI results in a blank field and continued use of public string and version 1 protocol.

Oddly, doing a full configuration poll will restore the correct version and string in the GUI and normal SNMP polling continues until it "glitches" again.

When the polling "glitches" the node reports SYS_SNMP_UNREACHABLE.

When the polling "glitches" it also reports all configured SNMP DCI as unsupported as the SNMP version has been reset.

This seems to cycle with the configured polling interval of 60 seconds.

All nodes use SNMP V2c.

All nodes that are not proxied are not affected.

Network discovery is disabled and I do have all custom SNMP Community Strings defined.

Have logs, but would prefer to not post publicly.

Thanks, Brett.


#6
Hi,

Have noticed some odd behaviour with SNMP proxying since V3

Nodes that are polled via a server with the agent acting as a proxy are exhibiting the following odd behaviour:

  • SNMP Version randomly resets to V1 from configured value
  • SNMP Community string will go blank if you set the Prevent automatic SNMP configuration changes, and any attempt to add a string fails.
  • Nodes with SNMP enabled will frequently report SYS_SNMP_UNREACHABLE and then next poll interval will go back to normal.

From observations, the issue is worse for switches.

Cheers, Brett.
#7
Announcements / Re: NetXMS 3.0 released
September 23, 2019, 03:59:40 AM
Quote from: Tatjana Dubrovica on September 16, 2019, 12:52:36 PM
Quote from: brettmilfos on September 13, 2019, 06:49:59 AM

Hi,

That fixed the issue of not finding the DriverName.

Checking the logs the generic driver finds the device OK, but when I try to send a notification it says it cannot send the notification as there is no such channel name.

Cheers, Brett.

Can you please provide screenshot of Cannel configuration for GenericDriver. It is under "Configuration"->"Notification Channels"

Hi Victor,

Attached is the screenshot.

P.S. Issue is with using Tools > Send notification

Thanks, Brett.
#8
Announcements / Re: NetXMS 3.0 released
September 13, 2019, 06:49:59 AM
Quote from: Victor Kirhenshtein on September 13, 2019, 12:51:16 AM
Hi,

I've found bug in Windows installer. Try to rename directory C:\NetXMS\lib\ncd to C:\NetXMS\lib\ncdrv and restart NetXMS Core service.

Best regards,
Victor

Hi,

That fixed the issue of not finding the DriverName.

Checking the logs the generic driver finds the device OK, but when I try to send a notification it says it cannot send the notification as there is no such channel name.

Cheers, Brett.
#9
Announcements / Re: NetXMS 3.0 released
September 12, 2019, 11:46:05 PM
Quote from: Victor Kirhenshtein on September 12, 2019, 10:58:03 AM
Quote from: brettmilfos on September 12, 2019, 06:59:17 AM
Just upgraded and have found an issue with SMS.

It created the migrated notification channel but did not work.

I tried to create a new notification channel, but there is nothing to select in the Driver name drop down.

Thanks, Brett.

How did you install server? On what platform?

Best regards,
Victor

Hi Victor,

Updated from 2.2.17 server 2k8r2 with existing generic SMS.

Cheers, Brett.
#10
Announcements / Re: NetXMS 3.0 released
September 12, 2019, 06:59:17 AM
Just upgraded and have found an issue with SMS.

It created the migrated notification channel but did not work.

I tried to create a new notification channel, but there is nothing to select in the Driver name drop down.

Thanks, Brett.
#11
A few suggestions:

When viewing interfaces it would be nice to be able to pull up the full list of MAC addresses on an interface. This will be really useful for interfaces with unmanaged devices connected.

Where supported, it would be nice to have an event that can be configured when there is more than one MAC address detected on an interface. This will be really useful to detect when users connect unmanaged switch devices.

Thanks, Brett.
#12
Announcements / Re: NetXMS 2.2.3 released
February 13, 2018, 05:51:59 AM
Installed OK and is running OK on a server with no NetXMS server.

Thanks, Brett.

Quote from: Victor Kirhenshtein on February 12, 2018, 10:41:49 PM
Hi,

please try to upgrade agent to this version: https://cloud.netxms.org/index.php/s/6AhhFsSt8hKTXbW

Best regards,
Victor
#13
Announcements / Re: NetXMS 2.2.3 released
February 12, 2018, 10:24:02 PM
Hi,

Upgraded from 2.2.2 and have problem.

If using the logwatch agent the agent process stops. No obvious error logged.

Disable logwatch agent and the agent process is stable.

Have attached debug 9 of agent with logwatch enabled.
#14
Announcements / Re: NetXMS 2.0-RC1 released
September 04, 2015, 07:55:41 AM
Hi,

Just noticed that this problem has come back again for the agent:

DB Library: Unable to load database driver module "sqlite.ddr": The specified module could not be found.

Odd thing, the file is in the bin folder.

Cheers, Brett.
#15
Announcements / Re: NetXMS 2.0-RC1 released
August 12, 2015, 12:43:53 AM
Quote from: Victor Kirhenshtein on August 11, 2015, 08:52:14 AM
Quote from: brettmilfos on August 11, 2015, 12:53:50 AM
I have encountered one issue. While upgrading from 2.0M5 all the mibs from var/mibs dis-appeared. This is on win2k8r2.

Restored mibs from a backup and re-built. But now when I run the 32bit console on win7 I get the following error after logging in:
"Cannot load MIB file from server: File I/O operation failed"

MIB locations was changed in 2.0-RC1. Source MIBs now are in <install_path>\share\mibs and compiled MIB file in <install_path>\var. Installer was supposed to move any non-standard MIBs from var\mibs to share\mibs. If you compile MIBs manually, you should set output file to be <install_path>\var\netxms.mib.

Quote from: brettmilfos on August 11, 2015, 12:53:50 AM
Also, do not know if this is related to the upgrade, before upgrading I stopped the Core, Agent & WebGUI services, but there was still a lock on the MySQL DB which prevented DB upgrade.

That means that core service didn't stop normally and was forcibly terminated by service manager. It's not related to upgrade, but rather indicates some problem with previous version.

Best regards,
Victor

Many thanks, I had seen the new folder for the mibs, but could not see where the compiled file was meant to go.

Also, in my attempts to sort this out I may have noticed an issue with one of the mibs, that I suspect prevented the installer from generating the compiled output?
HH3C-LICENSE-MIB: ERROR 001: Import symbol "PhysicalIndexOrZero" unresolved

Searching does not find a definition for the symbol.

Sadly, I have made a big mess of things now and was wondering where I could find all the "deafault" mibs?

Thanks, Brett.