Cannot save a new SNMP manager in SNMP Forwarding (Save button stays disabled)

34 viewsFORA
2
0 Comments

Hi all,

We're trying to configure a new SNMP manager under System Center > SNMP Forwarding in DataMiner Cube, but the Save button remains disabled no matter what we do.

DataMiner version: 10.6.2543.13924

What we're trying to achieve:
Forward DataMiner alarm notifications (SNMP traps) to a third-party device (a PATLITE network signal tower) whenever a Critical alarm occurs.

Steps taken so far:

  1. Created a new SNMP manager (New button), filled in Name, IP address, and Get community string on the general tab.
  2. Configured the notification tab (tried both Default OID and custom bindings OID).
  3. Configured the resend tab (left at default).
  4. Configured a filter on the filter tab (Severity Equal to Critical), confirmed and closed the filter editor with OK.
  5. Configured the alarm storm tab (also tried with "Enable alarm storm prevention" both checked and unchecked, with valid time span values filled in).

Despite completing every tab, the Save button at the bottom stays greyed out.

Troubleshooting we already did:

  • Recreated the SNMP manager from scratch with only the minimal required fields filled in (Name, IP address, Get community string on the general tab, everything else left at default) — Save is still disabled.
  • Checked the DataMiner license list in SLNet.txt — all relevant licenses (including RESOURCEMANAGER, SERVICEMANAGER, etc.) are present and the license is not expired.
  • Verified that SLSNMPAgent.exe and SLSNMPManager.exe are both running as processes (confirmed via Task Manager and via SLNet.txt authentication logs).
  • Checked SLNet.txt and could not find any Set DataMiner Info (EditSNMPManager) log entry, suggesting the Save action is never actually being submitted to the server (it seems to be blocked purely on the Cube client side).

Question:
Is there a known issue with the Save button on the SNMP Forwarding page being disabled in this version, or a required field/validation that isn't obvious from the UI? Are there any Cube client logs (beyond SLNet.txt) we should check to see exactly which validation is failing?

Any guidance would be greatly appreciated.

Thanks,

Hiroaysu Nakajima Asked question