Managing SNMP

This chapter describes how to manage SNMP services on a DANZ Monitoring Fabric (DMF) Controller.

SNMP Overview

SNMP provides a method for communication between an NMS or other client and agents (servers) on network devices, which send reports, called traps, regarding their operation and configuration. An SNMP agent manages and organizes the information as a collection of objects called MIBs.

In SNMPv3, an engineID identifies the agent (SNMP server), which helps prevent unauthorized SNMPv3 messages, such as traps, from being accepted or intercepted by unauthorized receivers. The engineID of the SNMP agent is required when configuring an SNMPv3 trap receiver to receive messages from an agent, including a DMF Controller or fabric switch.

In DMF, the engineID is auto-generated for the Controller and fabric switches. The engineID of the DMF Controller is configured for the local node. This configuration must be entered separately on the active and standby Controllers. The acceptable practice recommends configuring a different engineID for each Controller.

Using the DMF GUI to Configure SNMP

Complete the following steps to manage or view the DANZ Monitoring fabric (DMF) Controller SNMP configuration. SNMP configuration tabs and features include:
  1. Select Maintenance > SNMP from the DMF main menu.
    Figure 1. Configuring SNMP
    Note: By default, SNMP access is disabled.
  2. To enable access to SNMP for the Controller, click the link and enter the required fields, ID, Source, and Action (permit), in the Edit Access Control section.
    Figure 2. Edit Access Control
  3. Click Submit to continue.
    Figure 3. SNMP Enabled
  4. Under Local Configuration, click Edit and enter an Engine ID value, as required.
    Figure 4. Edit SNMP Local Configuration
  5. Click Submit to continue.
    Tip: Use the Reset button to clear the Engine ID value, if required.
    Figure 5. Local Configuration
  6. To enable SNMP traps, select Global Configuration.
    Figure 6. Global Configuration
  7. Click Edit and enter the Contact and Location details. Enable Trap Enabled by moving the selector switch to the right.
    Figure 7. Edit SNMP Global Configuration
  8. Click Next to continue.
  9. Enter the Trap Host details for the Server and UDP Port (162 by default) using the Provision control (+) button.
    Figure 8. SNMP Trap Host
  10. Click Submit. The dashboard displays the information and confirms Trap Enabled.
    Figure 9. Global Configuration Trap Enabled
  11. To create a new Community, select the Actions button under Communities and click + Add Community.
    Figure 10. Add Community
  12. Select the Permission type (read-only) from the drop-down and enter the Secret.
    Figure 11. Add Community Details
  13. Click Submit—the dashboard updates with the Community details.
    Figure 12. Communities
  14. To create an SNMPv3 user, select the Actions button under Users and click + Add User.
    Figure 13. Add Users
  15. Enter the required information, such as the Name of the user, the Authentication Passphrase for the user, and the Privacy Passphrase. Use the Privacy Protocol drop-down to select Advanced Encryption Standard (AES) or Data Encryption Standard (DES) encryption to encrypt the SNMP messages between the SNMP agent and the manager.
    Figure 14. User Details and Encryption
  16. Click Submit to continue—the dashboard updates with the User details.
    Figure 15. Users

Configuring SNMP Traps

Complete the following steps to configure the SNMP traps sent to the trap host. SNMP Traps configurations include:
  1. Select Controller Traps on the SNMP landing page.
    Figure 16. Controller Traps
  2. Click Edit and enter the Disk Percent value.
    Figure 17. Edit SNMP Controller Traps
  3. Click Submit. The dashboard displays the Disk Percent value.
    Figure 18. Disk Percent
  4. Select Switch Traps on the SNMP landing page.
    Figure 19. Switch Traps
  5. Click Edit and enter the Events values:
    • PSU Status Change in seconds(s).
    • Fan Status Changein seconds(s).
    • Link Status Change in seconds(s).

    Enable Authentication Failure by moving the selector switch to the right.

    Figure 20. Edit SNMP Switch Traps - Events
  6. Click Next to continue.
  7. Enter the Thresholds values:
    • 1-Minute CPU Load Threshold in percentage.
    • 5-Minute CPU Load Threshold in percentage.
    • 15-Minute CPU Load Threshold in percentage.
    • Percent Idle in percentage.
    • Percent Utilization in percentage.
    • Memory Free in bytes.
    • Full-Match Flow Table in percentage.
    Figure 21. Edit SNMP Switch Traps - Thresholds
  8. Click Next to continue.
  9. Enter the Thermal values:
    • Min in degrees Celsius.
    • Max in degrees Celsius.
    • Interval in seconds(s). It must be equal to or greater than 10.
    • Status from the drop-down list (None, All, Failed, Good, Missing).
    Figure 22. Switch Traps - Thermal
  10. Click Submit. The dashboard displays the Switch Traps values.
    Figure 23. Switch Traps Values

Configuring the System Name

Complete the following steps to configure the SNMP system name in the local configuration to a desired value such as a fully qualified domain name (FQDN).
  1. Select Local Configuration on the SNMP landing page.
    Figure 24. Local Configuration
  2. Click Edit and enter the chosen System Name string.
  3. Click Submit. The dashboard displays the new System Name string.

Using the CLI to Configure SNMP

This section describes using the CLI to configure and manage SNMP settings for the DMF Controller cluster.

Note: To configure a separate SNMP server for switches or Service Nodes, configure an access list to permit access from required clients.

Configuring SNMP Access to the Controller

By default, SNMP access to the Controller is disabled. The default SNMP access list is empty, meaning access is not permitted unless specifically enabled.

The following commands enable access to the Controller by remote SNMP clients on the specified subnetwork: 
controller-1(config)# controller
controller-1(config-controller)# access-control
controller-1(config-controller-access)# access-list snmp
controller-1(config-controller-access-list)# 10 permit from 10.8.67.0/24/0
Note: The permit command enables access to the Controller from an SNMP client in the subnetwork 10.8.67.0.
To enable access from any subnet, use the access list entry 0.0.0.0/0 (IP v4) and ::/0(IPv6), as in the following example: 
controller-1(config)# controller
controller-1(config-controller)# access-control
controller-1(config-controller-access)# access-list snmp
controller-1(config-controller-access-list)# 10 permit from 0.0.0 .0/0
controller-1(config-controller-access-list)# 20 permit from ::/0

Identifying the SNMP Trap Receiver

To identify a host to receive SNMP traps while in the config mode, enter the snmp-server host command, which has the following syntax: 
controller-1(config)# snmp-server host <ipaddress> [udp-port <udp-port>]
Replace ipaddress with the IP address of the host. Replace udp-port with the port number used by the SNMP traps. For example, the following command identifies a management system at 192.168.17.150 using UDP port 162. 
controller-1(config)# snmp-server host 192.168.17.150 udp-port 162

UDP port 162 is the default for SNMP trap messages; UPD port 161 is the default port for general SNMP messages.

The following are the SNMP traps generated by the Controller running on a VM or the hardware appliance: 
Name OID Trap generation
--------------------------------------------------------------------------
cpuload .1.3.6.2.4.1.2021.10.1.5.1 when load (average over 1 minute) > %90
memtotalfree .1.3.6.2.4.1.2021.4.11.0 when freemen (of entire Linux OS) < 50K
The following are the SNMP traps generated only by the hardware appliance: 
cputemp .1.3.6.2.2.1.99.1.1.1.4.1001 when CPU core temp > vendor
specified threshold value
ambienttemp .1.3.6.2.2.1.99.1.1.1.4.2001 when chassis inlet temp >
vendor specified threshold value
powersupply .1.3.6.2.2.1.99.1.1.1.4.3001 when power consumption >
vendor specified threshold value
fan**speed .1.3.6.2.2.1.99.1.1.1.4.40** when fan speed < vendor
specified threshold
Configuring disk-percent trap will monitor the root partition and the /var/log partition. To configure the trap: 
controller-1(config)# snmp-server trap
disk-percent set logging partition space use percentage at which to send trap
<disk-percent> Percent disk utilization (1..100)
controller-1(config)# snmp-server trap disk-percent 75
The following is the entry created in the /etc/snmp/snmpd.conf file when you configure the trap on the DMF controller: 
monitor -r 30 -I dskPercent .1.3.6.2.4.1.2021.9.1.9.1 > 75

Configuring SNMP Settings

To set the SNMP community string, which is a password used by a management application for accessing SNMP information, enter the snmp-server community command from config mode, as in the following example:
Note: Even though the CLI has options for ro or read-only and rw or read-write types of community strings, DANZ Monitoring Fabric supports only the ro option.
controller-1(config)# snmp-server community ro <string>
This command sets the community string for read-only access to the SNMP trap server.
Note: To push the SNMP trap host configuration to the monitoring switches, configure the community string to access the MIBs on the controller and switches. The SNMP trap server uses the same community string to receive and process the traps.
To set the SNMP location, enter the snmp-server location command from config mode, as in the following example: 
controller-1(config)# snmp-server location <location>
To set the SNMP contact, enter the snmp-server contact command from config mode, as in the following example: 
controller-1(config)# snmp-server contact <contact>
To view the current SNMP configuration, enter the show running-config snmp command.
Note: The community string appears as a Type 7 encoded value in the running-config.

To monitor the Controller’s /var/log and root partitions, configure the following trap:

  • disk-percent percent: Replace percent with the percentage that triggers a trap when exceeded.
    Note: Configuring the disk-percent trap on the Analytics Node will monitor the /var/lib/analytics/data folder, the /var/log folder, and the root partition.

To set the SNMP system name string to a desired value such as a fully qualified domain name (FQDN), the Controller configuration must be updated in the local node mode and hence must be done individually for each Controller node in the cluster.

Note: The same configuration applies also to Service Nodes, Recorder Nodes, and Analytics Nodes.

You can enter a chosen string as shown in the example below:


controller-2# conf 
controller-2(config)# local node 
controller-2(config-local)# snmp-server 
engine-id Value for the SNMP engine ID, a text string up to 27 characters long 
system-name SNMP system name to expose (sysName) 
DMF-MACSEC-2(config-local)# snmp-server system-name 
<System-name><String> 
controller-2(config-local)# snmp-server system-name DMF-C2.aristanetworks.com
controller-2(config-local)# end 
controller-2# show run local 

! local 
local node
hostname controller-2 
snmp-server system-name DMF-C2.aristanetworks.com 
interface management 
! 
ipv4 
ip 10.240.189.233/27 gateway 10.240.189.225 
method manual 
dns search qa.bsn.sjc.aristanetworks.com 
dns server 10.240.48.6 
! 
ipv6 
method manual

host ~ % snmpwalk -v2c -c bigswitch 10.240.189.233 sysName.0 
SNMPv2-MIB::sysName.0 = STRING: DMF-C2.aristanetworks.com

Without the above configuration, an snmpwalk command would return the hostname in the sysName parameter, as shown in the following:


controller-2# conf 
controller-2(config)# local node 
controller-2(config-local)# no snmp-server system-name DMF-C2.aristanetworks.com
controller-2(config-local)# end 
controller-2#

host ~ % snmpwalk -v2c -c bigswitch 10.240.189.233 sysName.0 
SNMPv2-MIB::sysName.0 = STRING: controller-2

Configuring SNMP Switch Trap Thresholds

To configure the thresholds for the SNMP traps generated by fabric switches, use the following command:

[no] snmp-server switch trap {cpu-load <cpu-load>| cpu-load 5min <cpu-load5>| cpu-load 15min <cpu-load15>| fm-flow-table-util <util>| mem-free <mem-free>| percent-idle <percent> | percent-utilization <percent>| psu-status <psu-status>| fan-status <fan-status> | link- status <link-status> | auth-fail | thermal [all | failed | good | missing | <interval> <min-temp> <max- temp>]

Use the following keywords with the snmp-server switch trap command as required.
  • auth-fail: Sends a trap when an authentication attempt fails.
  • cpu-load cpu-load: Replace cpu-load with the threshold for CPU utilization.
  • fan-status: Sends a trap when the fan status changes. Set the interval for monitoring between 10 and 100,000 seconds.
  • fm-flow-table-util util: Replace util with the percentage that triggers a trap when exceeded.
  • link-status: Sends a trap when the status of a link changes. Set the interval for monitoring between 1 and 100,000 seconds.
  • mem-free mem-free: Replace mem-free with the threshold (in bytes) for memory utilization.
  • percent-idle percent: Replace percent with the percentage of CPU idle utilization that triggers a trap when exceeded.
  • percent-utilization percent: Replace percent with the with the percentage of CPU utilization that triggers a trap when exceeded.
  • psu-status: Generate a trap when PSU status changes. Set the interval for monitoring between 10 and 100,000 seconds.
  • thermal: Sends a trap when the thermal sensor status changes as specified using the following options.
    • all: Includes failed, good, and missing.
    • failed: Sends a trap when the thermal sensor fails.
    • good: Sends a trap when the thermal environment is normal.
    • missing: Sends a trip when the thermal sensor is not present.
    • interval: Sends the trip after the expiry of the specified interval. The range is 10 to 100,000 seconds.
    • [ min-temp | max-temp ]: A trap is generated when the temperature in degrees Celsius is less than min-temp or greater than max-temp.
      Note: It is highly recommended to use percent-idle or percent-utilization instead of cpu-load trap.

SNMP Traps for DMF Service Node Appliance

The following are the SNMP traps supported by the DANZ Monitoring Fabric (DMF) Service Node appliance.
  • PSU failed/recovered
  • Fan failed/recovered
  • Temp exceeded some threshold or came back to normal
  • Interfaces up/down
  • SN inaccessible by the Controller
  • SN NetFlow GW is inaccessible
  • Percent (%) packet drop exceeded some threshold

Managing the SNMPv3 Engine ID for Trap Receivers

SNMPv3 adds authentication and encryption to the features provided by earlier versions of SNMP (v1 and v2). DANZ Monitoring Fabric (DMF) supports the SNMPv3 user-based security model (USM) for message security through authentication and encryption.

In SNMPv3, an engineID identifies the agent (SNMP server), which helps prevent unauthorized SNMPv3 messages, such as traps, from being accepted or intercepted by unauthorized receivers. The engineID of the SNMP agent is required when configuring an SNMPv3 trap receiver to receive messages from an agent, including a DMF Controller or fabric switch.

In DMF, the engineID is auto-generated for the fabric switches. To view the engineID for a specific fabric switch, enter the following command: 
controller-1> show switch <switch-name> running-config
For the DMF Controller, specify an engine-ID keyword that is used to generate the Controller engine-ID. The engine-ID keyword is a text string, up to 27 characters. To configure the engine-id, use the snmp-server engine-id string command from the config-local-node submode, as in the following example: 
controller-1(config)# local node
controller-1(config-local)# snmp-server engine-id controller-1_EngineID
The engineID of the DMF Controller is configured for the local node. This configuration must be entered separately on the active and standby Controllers. The acceptable practice recommends configuring a different engineID for each Controller.
Note: The engine-id configuration is not included when applying a saved running-config to the Controller. The engine-id configuration must be reapplied using snmp-server engine-id command.
The snmp-server engine-id command sets the engine-ID for the Controller using the following format: 
0x80001f8804 + <hex string>
where hex string is the ASCII hex version of the user-supplied string, which can be found using a tool like xxd: 
$ echo "abcdef--g" | xxd -ps
6162636465662d2d670a
This command lets you calculate the engine ID, as in the following example. 
snmp-server engine-id Controller2_Engine_ID
workstation$ echo "Controller2_Engine_ID" | xxd -ps
436f6e74726f6c6c6572325f456e67696e655f49440a
workstation$
The following is the output from the above with the trailing 0a removed. 
0x80001f8804
workstation:~$ sudo cat /var/lib/snmp/snmpd.conf | grep old
oldEngineID 0x80001f8804436f6e74726f6c6c6572325f456e67696e655f4944 <--------

Configuring SNMPv3 Users

Use the snmp-server user command in config mode to create a user account for SNMP v3 access. When running an snmpwalk (snmpget, snmpgetnext, snmpbulkget) from a shell, passphrases should be enclosed in single quotes. Entering the passphrase with double quotes (” “), may result in an error. This command has the following syntax:

[no] snmp-server user <name> {auth [0] <cleartext passphrase> | 7 <auth-passphrase>} [ priv {aes | des}{[0] <cleartext passphrase> | 7 <priv-passphrase>}]

The following is the meaning of each keyword:

  • auth | auth 0 | auth 7: Use a plaintext passphrase or a type 7 encoded passphrase.
  • cleartext-passphrase: A cleartext passphrase from 8 to 64 alphanumeric characters including dash (“-” and space). A dash or whitespace is not allowed at the beginning or end of the passphrase. Other special characters are not allowed.
  • private-passphrase: A type 0 encoded passphrase from 8 to 64 alphanumeric characters including dash (“-”) and space. A dash or whitespace is not allowed at the beginning or end of the passphrase. Other special characters are not allowed.
  • type-7-passphrase: A type 7 encoded passphrase from 8 to 128 alphanumeric characters including dash (“-”) and space. The maximum text string length that can be used with a Type 7 encoder, which can be found online, is 64. A dash or whitespace is not allowed at the beginning or end of the passphrase. Other special characters are not allowed.
  • priv {aes | des}: Optional keyword to perform Advanced Encryption Standard (AES) or Data Encryption Standard (DES) encryption of the following passphrase, which is used as an encryption key to encrypt the SNMP messages between the SNMP agent and the manager.
  • user username: Up to 32 alphanumeric characters including dash (“-“) and underscore (“_”) Spaces are not permitted. After you configure the username with a plaintext passphrase, the output from the show snmp-server command displays the passphrases in Type7 encoded strings. The Controller's configuration gets pushed through zero touch networking (ZTN) to the connected fabric switches.
    Note: DANZ Monitoring Fabric (DMF) only supports the ro or read-only type of community string option.

SNMPv3 Command Examples

Example 1. The snmp_1 user is configured for authentication (authNoPriv) with the plaintext password authauth1. 
controller-1(config)# snmp-server user snmp_1 auth authauth1
Example 2. The snmp-2 user is configured for authentication (authNoPriv) with the plaintext password authauth1. 
controller-1(config)# snmp-server user snmp-2 auth 0 authauth2
Example 3. The snmp11 user is configured for authentication and DES encryption (authpriv) with the auth password authauth11 and the encryption key privpriv11. 
controller-1(config)# snmp-server user snmp11 auth 0 authauth11 priv des 0 privpriv11
Example 4. The snmp21 user is configured for authentication and AES encryption (authpriv) with the auth password authauth21 and the encryption key privpriv21. 
controller-1(config)# snmp-server user snmp21 auth 0 authauth21 priv aes 0 privpriv21
The following are examples of Type7 encoded passphrases: 
controller-1(config)# snmp-server user snmp1 auth 7 0207114f03071a35441f
controller-1(config)# snmp-server user snmp20 auth 7 0207114f03071a35441c59 priv des 7 021616521d161d285a1c59
controller-1(config)# snmp-server user snmp30 auth 7 0207114f03071a35441d59 priv aes 7 021616521d161d285a1d59

Configuring SNMP on a Specific Switch

Configuring SNMP for a specific switch does not affect the Controller or other switches. Otherwise, the configuration is similar to configuring SNMP at the Controller level, using the Maintenance > SNMP option.
Note: Before configuring SNMP for a specific switch, enable SNMP access to the Controller.

Using the GUI to Configure SNMP on a Specific Switch

To use the GUI to merge/override the default SNMP configuration with switch-specific SNMP configuration, complete the following steps:
  1. Select Fabric > Switches and click the link for a specific switch.
    Figure 25. Fabric Switches
  2. On the Switches page, click the Actions control followed by Configure Switch.
    Figure 26. Configure Switch Dialog
    This page allows merging and overriding the default configuration pushed from the DANZ Monitoring Fabric (DMF) Controller with switch-specific SNMP configuration.
  3. To merge or override the SNMP configuration, click the SNMP link. Choose from the SNMP Settings drop-down to Merge with Global Config or Override Global Config.
  4. Make any changes required to the specific switch configuration, click Next to customize the SNMP traps, or click Submit.
  5. To merge or override the configuration for SNMP traps, click the SNMP Traps link and choose from the SNMP Switch Trap Settings drop-down to either Merge with Global Config or Override Global Config.
    Figure 27. SNMP Traps
  6. Make any changes required to the specific switch configuration and click Submit.

Using the CLI to Configure SNMP on a Specific Switch

Note: Before entering SNMP commands from the config-switch submode, enable SNMP access to the Controller.
  • When using the config-switch submode for a specific switch, configuration changes, including SNMP, do not affect the Controller or other switches. Otherwise, the configuration is similar to configuring SNMP in config mode at the Controller level.
  • Entering the snmp-server enable traps command in config mode pushes snmp-server enable configuration to each connected fabric switch. Verify the switch configuration by entering the show effective-config switch switch-name snmp from the CLI, as in the following example. 
    controller-1(config)# snmp-server enable traps
  • From the switch CLI: 
    controller-1(config)# show effective-config switch switch-btsw-1 snmp
! switch
switch switch-btsw-1
snmp-server enable traps

Like the GUI, use the CLI to merge or override the default SNMP configuration with switch-specific SNMP configuration. To do so, complete the following steps:

  1. Add the SNMP configuration at the Controller. This is the default SNMP configuration pushed to all the switches. The following is an example configuration: 
    controller-1(config)# show running-config snmp
! snmp-server
snmp-server host 10.1.1.1
snmp-server enable traps
snmp-server community ro 7 02161159070f0c
snmp-server contact Alice
snmp-server location 'San Francisco'
snmp-server user user1 auth 7 0217135e191216344541
  2. Configure switch-specific-parameters at the config-switch submode. 
    controller-1(config)# switch-btsw-1
controller-1(config-switch)# snmp-server host 10.1.1.2
controller-1(config-switch)# snmp-server contact Bob
controller-1(config-switch)# snmp-server location 'San Jose'
controller-1(config-switch)# snmp-server user user2 auth 0 qwertyuiop
  3. In the config-switch submode, type either merge-global to merge the global config with the switch-specific config or override-global to override the global config with the switch config. When choosing neither, the switch inherits the global config, and any configuration added under the config-switch submode will be redundant. 
    controller-1(config-switch)# snmp-server merge-global
  4. Check the SNMP configuration running on the switch using the CLI command show effective-config switch switch-name snmp: 
    controller-1(config-switch)# show effective-config switch switch-btsw-1 snmp
! switch
switch switch-btsw-1
snmp-server host 10.1.1.1
snmp-server host 10.1.1.2
snmp-server enable traps
snmp-server community ro 7 02161159070f0c
snmp-server contact Bob
snmp-server location 'San Jose'
snmp-server user user1 auth 7 0217135e191216344541
snmp-server user user2 auth 7 0207175f0d01072b4742
    When using merge-global, the effective configuration on the switch is a merge of the global configuration and the switch-specific configuration.
    Note: SNMP community, user, and host are of list-type. In merge-mode these list-type configurations append to potentially existing global config.
    Below is an example with override-global: 
    controller-1(config-switch)# snmp-server override-global
controller-1(config-switch)# show effective-config switch switch-btsw-1 snmp
! switch
switch switch-btsw-1
snmp-server host 10.1.1.2
snmp-server contact Bob
snmp-server location 'San Jose'
snmp-server user user2 auth 7 0207175f0d01072b4742

    When using override-global, the effective configuration on the switch is only the switch-specific configuration and completely overrides the default configuration inherited from the Controller.

  5. Configuring SNMP traps using merge and override global commands is similar. See examples below: 
    controller-1(config)# snmp-server switch trap thermal all
controller-1(config)# snmp-server switch trap link-status 5
controller-1(config)# snmp-server switch trap percent-utilization 80
controller-1(config)# switch-btsw-1
controller-1(config-switch)# snmp-server switch trap thermal failed
controller-1(config-switch)# snmp-server switch trap link-status 1
controller-1(config-switch)# snmp-server switch trap percent-utilization 90
    Example 1. merge-global 
    controller-1(config-switch)# snmp-server trap merge-global
controller-1(config-switch)# show effective-config switch switch-btsw-1 snmp-trap
! switch
switch switch-btsw-1
snmp-server switch trap thermal failed
snmp-server switch trap link-status 1
snmp-server switch trap percent-utilization 90
    Example 2. override-global 
    controller-1(config-switch)# snmp-server trap override-global
controller-1(config-switch)# show effective-config switch switch-btsw-1 snmp-trap
! switch
switch switch-btsw-1
snmp-server switch trap thermal failed
snmp-server switch trap link-status 1
snmp-server switch trap percent-utilization 90
    To limit SNMP access to clients in specific IP subnetworks, enter the snmp-server community command from the config-switch submode on the DMF Controller. This command has the following syntax: 
    snmp-server community {rw | ro} {<cleartext secret> | 0 <cleartext secret> | 7 <obfuscated secret>}
    When using the merge-global and override-global commands at the config-switch submode, the SNMP community for the switch can be changed as shown in the following example:
    SNMP configuration on the controller: 
    controller-1(config)# show running-config snmp
! snmp-server
snmp-server host 10.1.1.1
snmp-server community ro 7 02161159070f0c
snmp-server contact Alice
snmp-server location 'San Francisco'
snmp-server user user1 auth 7 0217135e191216344541
    SNMP configuration on the switch: 
    controller-1(config-switch)# show run switch switch-btsw-1
! switch
switch switch-btsw-1
snmp-server override-global
snmp-server enable traps
snmp-server host 10.1.1.2
snmp-server community ro 7 021616521d071b24
snmp-server contact Bob
snmp-server location 'San Jose'
snmp-server user user2 auth 7 0207175f0d01072b4742

SNMP Clear Trap

SNMP trap messages are sent whenever a threshold is reached, or an HW failure happens, like PSU failure/removal. An SNMP clear trap message is sent whenever a threshold is less than the specified range or the HW failure is fixed, such as when the PSU starts working.

There is no command to enable this feature. This feature is automatically enabled when configuring the SNMP trap on the Controller.

SNMP traps that do not have associated clear traps have other ways of notifying state change. For example, link up and link down traps are sent when the link goes up and down. The /etc/snmp/snmpd.conf file lists all SNMP traps and clear trap settings.
Note: SNMP clear traps will be sent without any prior associated SNMP traps when the system comes up or there is any SNMP configuration change. Ignore these SNMP clear traps.

SNMP clear trap messages are not supported on DMF switches running EOS.

The following are switch traps for which clear traps will be sent:
  • switch trap cpu-load
  • switch trap fm-flow-table-util
  • switch trap mem-free
  • switch trap percent-idle
  • switch trap percent-utilization

These are the appliance (Controller, Service Node, Recorder Node, Analytic Node) traps for which clear traps will be sent.

Note: Upgrade the appliance IDRAC Firmware to the recommended version of 5.10.50.00 or later.
  • disk-percent
  
  • memtotalfree
  
  • lowmemavailable
  
  • cpuload
  
  • cputemp
  
  • cpu1temp
  
  • ambienttemp
  
  • exhausttemp
  
  • powersupply
  
  • fanspeed
 The number of fans on an appliance varies. Depending on the number of fans on the appliance, fanspeed clear traps are sent.

Fan speed traps are named fan1Aspeed, fan1Bspeed, etc.
  • psuCount
  
  • fanCount