Wireless Access

last person joined: yesterday 

Access network design for branch, remote, outdoor, and campus locations with HPE Aruba Networking access points and mobility controllers.
Back to discussions
Expand all | Collapse all

Our SNMP Trap server IP changed but controller is still sending logs to old IP

This thread has been viewed 0 times

  • 1.  Our SNMP Trap server IP changed but controller is still sending logs to old IP

    Posted Aug 01, 2014 02:39 PM

    We have an account that had SNMP trap servers change.  The New IPs were added to the controller (old ones removed) but the controller is still sending logs to the old IP address.  Any suggestions?  Controller code is 6.1.3.1



  • 2.  RE: Our SNMP Trap server IP changed but controller is still sending logs to old IP

    EMPLOYEE
    Posted Aug 01, 2014 03:24 PM

    Sending SNMP traps with an Aruba Controller is confiugured by using "snmp trap-host...".  Sending syslog from an Aruba controller is configured by using "logging <ip address".  Which one did you change? (traps or syslog)



  • 3.  RE: Our SNMP Trap server IP changed but controller is still sending logs to old IP

    Posted Aug 01, 2014 03:45 PM

    New Trap Receiver Hosts(currently show up in configuration)
    1xx.xxx.xx.211
    1xx.xxx.xx.211

    Old Trap Receiver Hosts(were removed from configuration couple weeks ago)
    1xx.xxx.xx.201
    1xx.xxx.xx.201



  • 4.  RE: Our SNMP Trap server IP changed but controller is still sending logs to old IP
    Best Answer

    EMPLOYEE
    Posted Aug 01, 2014 03:47 PM

    Look in the Audit trail and see what commands were executed for both "show audit-trail".  Each controller has a local configuration for traps and syslog, so it must be done for each individually.

     

    If you checked those and you cannot find the issue, please open a support case.