My company is an authorized reseller of AKCP. We lent our old Securityprobe 5E demo unit to our prospective client. They will try to test if they can add the base unit as a node of their SolarWinds Observability using SNMPv3 to receive SNMP traps from the base unit. After configuring all the needed information and credentials on both the Securityprobe and SolarWinds, they encountered this error during adding/testing the node on the SolarWinds side: Test Failed. Error Code ‘31216’, Message: /SNMPv3 Error. The specified username is not recognized by the SNMP service on remote machine. Verify that the username is correctly configured on the device. Despite of double checking all the credentials to be correct and matches on both the Securityprobe and SolarWinds, this error persists. Are we missing something here? Does anyone tried doing this kind of setup and succeeded?
- teddyty888 asked 4 weeks ago
- You must login to post comments
Dear valued dealer,
Thank you for reaching out. We have definitely seen this kind of setup before, and we can help you get this resolved.
The error message “The specified username is not recognized by the SNMP service on remote machine” typically indicates a mismatch in the SNMPv3 cryptographic settings between SolarWinds and the SecurityProbe. This mismatch prevents them from authenticating the user.
Because the SecurityProbe 5E is an older generation unit, it has specific limitations regarding the SNMPv3 protocols it supports. SolarWinds might be defaulting to newer, stronger encryption standards that the SEC5E cannot process.
Please ask your client to verify the following details within their SolarWinds configuration for this node:
- Authentication (Auth) Protocol: The SEC5E only supports MD5 or SHA (SHA-1). Ensure SolarWinds is not set to SHA-256, SHA-512, or other newer protocols.
- Privacy/Encryption (Priv) Protocol: The SEC5E only supports DES or AES (AES-128). Ensure SolarWinds is not set to AES-192 or AES-256.
- Password Length: Both the Authentication and Privacy passwords must be at least 8 characters long. This is a strict requirement for SNMPv3.
- Trap Configuration vs. Polling: You mentioned they want to receive SNMP traps. Please note that receiving traps and adding the node for polling are two entirely separate configurations.
Configuration Steps:
- For Polling: To add the node, the SolarWinds SNMPv3 credentials must exactly match the SEC5E using the specific protocols listed above.
- For Traps: To receive SNMPv3 Traps, ensure the SNMPv3 user is also correctly mapped in the trap destination settings. This is located under the SEC5E’s Virtual Sensor SNMP Trap Receiver settings.
Please have the client double-check the Auth and Priv algorithm drop-down menus in SolarWinds to guarantee they are strictly using SHA1/MD5 and AES128/DES.
Let us know how the testing goes or if you need any further assistance via a direct email to our support team (support@akcp.com) including all of the details included in this posting.
Best regards,
AKCP Support Team
- AKCP Support Team answered 3 weeks ago
- last edited 3 weeks ago
- Thank you! We got it running.
- You must login to post comments
Hello Teddy,
Great to hear and thanks for the update on this.
Best regards,
AKCP Support Team
- AKCP Support Team answered 3 weeks ago
- You must login to post comments
Please login first to submit.