EFA acts as the SNMP Manager for all the SLX devices and agents and receives the traps from all the devices in its inventory.
Simple Network Management Protocol (SNMP) traps are alert messages sent from a remote SNMP-enabled device to a central collector, the SNMP Manager. Trap messages are the main form of communication between SNMP monitoring tools – an SNMP Agent and an SNMP Manager.
EFA acts as the SNMP Manager for all the SLX devices and agents and receives the traps from all the devices in its inventory. Once you register an SLX device with EFA, EFA automatically configures the SLX device to send v3 traps to EFA.
EFA acts as an SNMP proxy for all the SNMP v2 and v3 traps received from the SLX devices, forwarding them onto an external trap receiver, if there is one.
During an update operation, EFA verifies that it is still registered to receive traps from the SLX devices. If a device is unregistered from EFA, the SNMP configuration on the device is updated to no longer send traps to the EFA IP address.
SNMP-COMMUNITY-MIB::snmpTrapAddress.0
. It is not the EFA IP address.For more information about SLX-OS MIBs, see the Extreme SLX-OS MIB Reference for your version of SLX-OS.
The gosnmp-service is responsible for persisting the trap subscribers, receiving the SNMP traps, and forwarding them to the subscribers.
The service is stateless, so no historical data (that is, previously received traps) will be persisted.
For high availability deployment, the service will be running in active/active mode, however since the VIP is bound to one host at a time, the pod running on the active node will be the one receiving the traps. On failover, the standby node takes over and the SNMP service running on that node will forward the traps.
You may have multiple IP subnets configured to access EFA. In such a case, EFA creates multiple subinterfaces under the management interface to which EFA is bound. EFA does not determine which interface sends out the trap, syslog or webhook. The administrator is responsible for configuring a route to the recipient. If one is found, the server will send out the trap. For more information, see Multiple Management IP Network.