Controller Based WLANs

When do we see the error message "Cannot bind SNMP Trap transport" in controller logs?

Aruba Employee
Q:

Why is my SNMP server not receiving the trap messages from the controller?

Why do I see the error message "Cannot bind SNMP Trap transport" in the controller logs?



A:

We can configure a trap source on the controller to send SNMP traps:

(Master) # config t
(Master) (config) #snmp-server trap source 10.2.1.1

With the above configuration, the controller will start using given IP address on the controller as source IP address for TRAP messages. However, if the IP address is not configured or if the vlan is not UP, the controller will be unable to send the traps. Also, We might start seeing the following error messages on the controller logs:

Jan 21 16:32:35 snmp[3661]: <301249> <WARN> |snmp| Cannot bind SNMP Trap transport
Jan 21 16:32:35 snmp[3661]: <301249> <WARN> |snmp| Cannot bind SNMP Trap transport
Jan 21 16:32:35 snmp[3661]: <301249> <WARN> |snmp| Cannot bind SNMP Trap transport
Jan 21 16:32:35 snmp[3661]: <301249> <WARN> |snmp| Cannot bind SNMP Trap transport

 

To fix this, we need to make sure that the IP address is correctly configured.

(Master) (config) #show ip interface brief

Interface                   IP Address / IP Netmask        Admin   Protocol
vlan 1                     10.17.171.3 / 255.255.255.224   up      up
vlan 2                      10.150.2.3 / 255.255.255.0     up      up
vlan 3                      10.150.3.3 / 255.255.255.0     up      up

 

Here we see that configured trap source is not available on the controller. We wil correct this by:

(Master) # config t

(Master) (config) #snmp-server trap source 10.17.171.3

 

Version history
Revision #:
2 of 2
Last update:
‎03-24-2017 05:03 PM
Updated by:
 
Labels (1)
Contributors
Search Airheads
cancel
Showing results for 
Search instead for 
Did you mean: 
Is this a frequent problem?

Request an official Aruba knowledge base article to be written by our experts.