Arista

Arista EOS deliberately mirrors Cisco IOS command conventions for SNMP - if you already know IOS syntax, EOS will look immediately familiar.

SNMPv2c (community strings)

configure terminal
snmp-server community public ro
snmp-server community secretstring rw
snmp-server location "Rack 4, DC1"
snmp-server contact admin@example.com
end

SNMPv3

snmp-server group MYGROUP v3 priv
snmp-server user MYUSER MYGROUP v3 auth sha MYAUTHPASS priv aes 128 MYPRIVPASS

Same group-then-user pattern as IOS: the group carries the security level (priv requiring both authentication and encryption), the user is then attached to that group with its actual credentials.

Sending traps

snmp-server host 192.168.1.100 version 2c public
snmp-server host 192.168.1.100 version 3 priv MYUSER
snmp-server enable traps

As on IOS, snmp-server enable traps alone enables the default trap set; specific categories can be named instead if you want to be more selective (snmp-server enable traps bgp, for instance).

An EOS-specific option: exposing custom OIDs

EOS supports an extension mechanism for serving custom data over SNMP from an external script - conceptually similar to Net-SNMP's pass_persist (covered in the SNMP Service guide), but built into EOS itself rather than requiring a separate agent:

snmp-server extension .1.3.6.1.4.1.30065.99 /mnt/flash/my_custom_script.py

Since EOS runs on a Linux-based architecture, scripts like this run directly on the switch's own filesystem (commonly under /mnt/flash) rather than needing a separate management host.

Model/platform differences

This syntax is consistent across Arista's switch line. The more relevant difference on Arista isn't between models but between MIB sources: CPU and memory come from the standard HOST-RESOURCES-MIB rather than a proprietary Arista MIB - the SNMP configuration itself doesn't change based on this, but it's worth knowing when you go looking for a CPU OID and don't find an Arista-specific one.