automatic discovery of devices from SpectrumGTW to SNMPCollector fails because of wrong auth protocol
search cancel

automatic discovery of devices from SpectrumGTW to SNMPCollector fails because of wrong auth protocol

book

Article ID: 421103

calendar_today

Updated On:

Products

DX Unified Infrastructure Management (Nimsoft / UIM)

Issue/Introduction

I am experiencing an issue with the automatic discovery of devices from SpectrumGTW to SNMPCollector.
I follow these steps:

  • In DX Spectrum → I add the devices to a Global Collection for integration with DX UIM.

  • In DX UIM            → In SpectrumGTW, I run Inventory Synchronization.
            → In OperatorConsole, the new elements are discovered.
            → In SNMPCollector, I add the devices to the discovery filters individually by IP address and then run Query discovery server

The devices are added to SNMPCollector, but all of them have bad credentials.

In reality, all of these devices use SHA256/AES256 (with the same password), but the devices are created in SNMPCollector with auth.protocol set to MD5 and priv.protocol left empty.
After manually changing the protocols, the devices start responding correctly.

Environment

  • UIM version is 23.4.4
  • Spectrum version is 24.3
  • spectrumgtw version is 20.41
  • snmpcollector 4.15

 

Cause

When importing devices from spectrumgtw to the UIM inventory the authentication protocol name is changing from SHA-256 to MD5.

It is discovered in DX Netops / Spectrum with SHA-256 but in inventory it shows as MD5 this causes the issue. 

The root cause is that the spectrumgtw probe is incorrectly converting the authentication protocol name, changing it from SHA-256 to MD5. This defect must be fixed on the spectrumgtw probe side. Once the protocol name is correctly converted, the SNMP Collector handles the privacy protocol conversion properly, and no code changes are required on the SNMP Collector side.

 

Resolution

The fix will be delivered in the next spectrumgtw probe release scheduled for the first week of January 2026.