NetXMS Support Forum

The dreaded "Status of DCI nnnnn (SNMP oid) changed to UNSUPPORTED" has been one of the items we have always struggled with on this excellent product and once again this is the case.  Really want to get to the root of this so we can monitor and move forward.  The specific issues that we are having this time is monitoring Cambium ePMP LAN / WAN TX / RX byte counters.  We are monitoring 100's of these devices and the issue only shows up on about 15-20 of them.

To help narrow this down I have picked a single radio where these are not working which is located at a site that has one working perfectly.  I have compared configurations for these two devices, they are running the same firmware release and besides IP address information are identical (including hardware model of course).  All four of the counters are not working for this device as well and we get messages like:

Status of DCI 28941 (SNMP: .1.3.6.1.4.1.17713.21.2.1.65.0) changed to UNSUPPORTED

If I use the built in MIB explorer on the working device and WALK starting at .1.3.6.1.4.1.17713.21.2.1 this value is part of the list retrieved.  On the "broken" device it is not displayed in the MIB explorer.  HOWEVER, if I simply go to the command line of the server running NetXMS and run some SNMP commands against the failing device they respond just fine:

# snmpwalk -v 2c -c NOTIT 10.0.XXX.XXX .1.3.6.1.4.1.17713.21.2.1.65.0
iso.3.6.1.4.1.17713.21.2.1.65.0 = Counter64: 106460802368
# snmpget -v 2c -c NOTIT 10.0.XXX.XXX .1.3.6.1.4.1.17713.21.2.1.65.0
iso.3.6.1.4.1.17713.21.2.1.65.0 = Counter64: 106460803992

Hoping to finally be able to resolve this "random" issue that we have always faced.

OK, I rescind the not working I had just not ever saw the option under the "Other options" section which I am guessing was added.  Changing it on the Last Values for me still changes ALL of them to either using multipliers or not. 

Thanks for pointing this out!

An update to my last post, decided to live on the edge and run nxdbmgr -X upgrade which resulted in:

# nxdbmgr -X upgrade
NetXMS Database Manager Version 3.8.382 Build 3.8-382-gc0100d1389 (UNICODE)

Upgrading database...
Upgrading from version 38.16 to 38.17
SQL query failed (Duplicate column name 'rule_description'):
ALTER TABLE alarms ADD rule_description varchar(255)
SQL query failed (Data too long for column 'rule_description' at row 75):
UPDATE alarms SET rule_description=(SELECT REPLACE(REPLACE(REPLACE(REPLACE(comments, ?, ' '), ?, ' '), ?, ' '), '  ', ' ') FROM event_policy WHERE event_policy.rule_guid=alarms.rule_guid)
Database upgrade succeeded

Server now starts, but concerned what the long term impact of this might be...

Received this when upgrading Ubuntu server to 3.8-382:

SQL query failed (Data too long for column 'rule_description' at row 75):
UPDATE alarms SET rule_description=(SELECT REPLACE(REPLACE(REPLACE(REPLACE(comments, ?, ' '), ?, ' '), ?, ' '), '  ', ' ') FROM event_policy WHERE event_policy.rule_guid=alarms.rule_guid)
Rolling back last stage due to upgrade errors...

After I tried to use nxdbmgr upgrade and get:

NetXMS Database Manager Version 3.8.382 Build 3.8-382-gc0100d1389 (UNICODE)

Upgrading database...
Upgrading from version 38.16 to 38.17
SQL query failed (Duplicate column name 'rule_description'):
ALTER TABLE alarms ADD rule_description varchar(255)
Rolling back last stage due to upgrade errors...
Database upgrade failed


The netxmsd service will not start now.  This was coming from 3.8-314.

This is marked fixed as of 3.7 in the tracker, but it definitely is not working.  It still seems multipliers are an all or nothing situation.

It would be nice if you could expand the size of the Edit Script window anywhere it shows up.  Currently, the pain point is in the Edit Threshold section of the application, but if there are other areas it would probably be helpful as well.  If you have any significant amount of code it is difficult to write within the small window which only allows about 50 characters before scrolling.

Victor,

I actually believe that instance discovery will work much better, just had not really looked into this much previously.  So, seeing the power that provides where would a table be a better solution?  Just trying to figure out the best use cases for all of the power of this wonderful tool!  Thanks as always.

Wondering if it would be possible to allow scripts to be processed in thresholds like you can for a single value collection on tables.  Our specific case is that we have a device that has a fan speed table (simply index / fan speed in RPM's) and devices may have anywhere from 1-5 fans depending on model.  We have another polled value which represents a temperature.  If the temperature exceeds a threshold the fans should start.  If they have 0 RPMs when that temperature is exceeded this triggers to us the fan has failed and we need to look at replacing it.  Looking for an elegant solution to trigger these events.  Suppose I could put it into the processing for the board temperature but logically it seems to be better placed with the fan table.

Hoping this makes sense, thanks in advance for any suggestions.

Totally agree with lindaemon that this has and continues to be an excellent product!

It does not appear the Ubuntu repositories (maybe others) have not bee updated, any ETA?

It would be nice on a per item basis to be able to turn on / off the Use Multiplier function and of course have a default setting for this in the Server Configuration options.  In most instances it is great and works as you would hope, but for things like Ethernet speed or Frequency that an access point is using it becomes odd.  Gigabit Ethernet shows as 1K and an access point using 2412 for its frequency show 2.41K which is not helpful at all in that case.

Thanks!

Stan:

I would completely agree with you if what you were describing was the problem, but it is NOT!  We use many different templates as well to fine tune what is being collected.

The issue is that it is changing items to UNSUPPORTED that are 100% legitimate!  In one of our cases it is the polling of a SNMP value to show GPS sync state of a device.  Have verified many times the OID is correct and the console has no issues polling that OID withing the MIB Explorer.  We have also looked to make sure that more than one template does not have the OID and that we are looking at the wrong one. 

It is simply broken!

Yes, we have not seen it resolved either and each release seems to actually grow.

This issue still exists in 2.2.15.

That was the fix, thanks! 

Victor any ideas how to correct this?  The line of code is pretty much the one in the page referred to.  Thanks!