Description

This article provides step-by-step procedure on how to troubleshoot authentication error for SNMPv3 protocol in Juniper EX-3400-VC setup.

Symptoms

Issue might be seen if the snmp engine-id is un-changed or SNMPv3 protocol is newly configured for the first time.

Solution

  1. Delete snmp_engine.db file from /var/db directory. Also, delete SNMPv3 configuration.

file delete /var/db/snmp_engine.db
 
user@switch# delete snmp
user@switch# commit
 

  1. Configure SNMP engine-id using the below command

 
user@switch# set snmp engine-id use-default-ip-address
user@switch# commit
 

  1. Further, check if the snmp engine-id has re-generated.

file show /var/db/snmp_engine.db
 

  1. Then, configure SNMPv3 configuration and commit the changes.

 
Verify the authentication and follow the below step if the issue is still persisting.
 

  1. Try changing the authentication-type & authentication-password and verify the status. If still the authentication is failing, then rollback the changes and verify the status.

 
 
If the issue is still persisting, then try to configure the engine id using local [or] mgmt interface mac-address and re-configure the SNMPv3 configuration.
 

  1. Delete snmp_engine.db file from /var/db directory. Also, delete SNMPv3 configuration.

file delete /var/db/snmp_engine.db
 
user@switch# delete snmp
user@switch# commit
 

  1. Configure snmp engine-id using local or mgmt interface mac address

 
user@switch# set snmp engine-id local xx:xx:xx:xx:xx
[or]
user@switch# set snmp engine-id use-mac-address             
 

  1. Further, check if the snmp engine-id has newly generated.

file show /var/db/snmp_engine.db
 

  1. Then, configure the SNMPv3 configuration and commit the changes.

 
Verify the authentication and follow the below step if the issue is still persisting.
 

  1. Try changing the authentication-type & authentication-password and verify the status. If still the authentication is failing, then rollback the changes and verify the status.

 Ideally, issue should have been resolved now.
 
If the issue is still persisting, please re-start the SNMP process and follow the provided action plan.
 
user@switch> restart snmp all-members gracefully
 
If restarting the SNMP process isn’t helping to fix the issue, please reboot the VC and follow the provided action plan.
 
user@switch> request system reboot all-members

 

Modification History

version 1