Configure SNMP
Use this topic to configure Routing Director to send SNMP traps received from Juniper devices.
Routing Director receives and stores SNMP traps (SNMPV2c and SNMPV3) and information messages from devices. Routing Director listens for SNMP traps on the default UDP port 162. These traps are then forwarded to external managers (applications) that are configured in Routing Director. Routing Director, by default, stores SNMP Traps for one month.
Routing Director logs all the activities related to SNMP processing if the SNMP trap
service (trapster) log level is configured as info. To view these logs, log
into a Routing Director cluster node and execute the following command:
root@controller:~# kubectl logs -f -n trapster svc/trapster
To configure Routing Director to accept SNMP traps and export them to external SNMP managers:
|
Field |
Description |
|---|---|
|
SNMP Forwarding Endpoints |
|
|
Name* |
Enter a name for the external SNMP manager (application) to which SNMP traps received from Juniper devices must be sent. The SNMP manager name can include any type of character but must not exceed the 128-character limit. |
|
Target Address* |
Enter an IPv4 address, an IPv6 address, or the fully qualified domain name of the external SNMP manager. The Target Address can include any type of character but must not the exceed 255 characters. |
|
Port |
Enter the port number on the external SNMP manager to which Routing Director must send SNMP traps received from Juniper devices. Range: 0 through 65,535 |
|
Description |
Enter a description of the external SNMP manager. |
|
SNMP Configuration V2 |
|
|
Timeout (in seconds)* |
Enter the maximum duration (in seconds) that Routing Director can take to forward SNMP traps received from Juniper devices to external SNMP managers. Range: 5 through 30 seconds |
|
Retry* |
Enter the number of times Routing Director can attempt forwarding an SNMP trap to external SNMP managers. Range: 0 through 5 |
|
Validate |
Click to enable (default) or disable Routing Director from validating the configured community string with the community string in the SNMP trap received from Juniper devices, for authentication. |
|
Community |
Enter a string that Routing Director can use to verify the SNMP traps received from Juniper devices. If the community string you enter here matches with the community string in the received SNMP traps, Routing Director forwards the SNMP traps to the configured external SNMP managers. The community string must not exceed 32 characters. |
|
SNMP Configuration V3 |
|
|
Timeout (in seconds)* |
Enter the maximum duration (in seconds) that Routing Director can take to forward SNMP traps received from Juniper devices, to external SNMP managers. Range: 5 through 30 seconds |
|
Retry* |
Enter the number of times Routing Director can attempt forwarding an SNMP trap to external SNMP managers. Range: 0 through 5 |
|
Authentication Type |
Select an algorithm (such as MD5 or SHA) that Routing Director can use to verify the identity of the SNMP user configured on Juniper devices sending the SNMP traps. The authentication type you select here must match the authentication type configured on the Juniper devices. If authentication fails, Routing Director will not forward the traps to external SNMP managers. |
|
Username |
Enter the SNMP username that Routing Director can use to verify the integrity of the SNMP traps received from Juniper devices. The username is used together with the authentication type and password to verify the SNMP user's identity configured on Juniper devices. The username you enter here must match the username configured on the Juniper devices. The username can contain any type of character but must not exceed 32 characters. |
|
Authentication Password |
Enter a secret key to be used together with the authentication type and username to verify the integrity of SNMP messages. The password is used together with the authentication type and username to verify the user’s identity. The password you enter here must match the password configured on the devices. The password can contain any type of character but must not exceed the 32-character limit. |
|
Encryption Type* |
Select an algorithm, such as DES or AES, that Routing Director can use to decrypt SNMP traps to validate them and then encrypt the SNMP traps back before sending them to external SNMP managers. |
|
Privacy Password |
Enter the password that Routing Director can use to decrypt and encrypt SNMP traps to validate them before forwarding to external SNMP managers. The privacy password can contain any type of character but must not exceed the 32-character limit. |