Help us improve your experience.

Let us know what you think.

Do you have time for a two-minute survey?

Navigation
 

Related Documentation

 

Configuring the SNMPv3 Authentication Type

By default, in a Junos OS configuration the SNMPv3 authentication type is set to none.

This topic includes the following sections:

Configuring MD5 Authentication

To configure the message digest algorithm (MD5) as the authentication type for an SNMPv3 user, include the authentication-md5 statement at the [edit snmp v3 usm local-engine user username] hierarchy level:

[edit snmp v3 usm local-engine user username]authentication-md5 {authentication-password authentication-password;}

authentication-password is the password used to generate the key used for authentication.

SNMPv3 has special requirements when you create plain-text passwords on a router or switch:

  • The password must be at least eight characters long.
  • The password can include alphabetic, numeric, and special characters, but it cannot include control characters.

Configuring SHA Authentication

To configure the secure hash algorithm (SHA) as the authentication type for an SNMPv3 user, include the authentication-sha statement at the [edit snmp v3 usm local-engine user username] hierarchy level:

[edit snmp v3 usm local-engine user username]authentication-sha {authentication-password authentication-password;}

authentication-password is the password used to generate the key used for authentication.

SNMPv3 has special requirements when you create plain-text passwords on a router or switch:

  • The password must be at least eight characters long.
  • The password can include alphabetic, numeric, and special characters, but it cannot include control characters.

Configuring No Authentication

To configure no authentication for an SNMPv3 user, include the authentication-none statement at the [edit snmp v3 usm local-engine user username] hierarchy level:

[edit snmp v3 usm local-engine user username]authentication-none;
 

Related Documentation

 

Published: 2012-12-08

 

Related Documentation

 

Published: 2012-12-08