On Thu, 2019-01-03 at 11:30 +0100, Robert Hass wrote:
> event manager applet blah2 authorization bypass
> event syslog pattern "%CLEAR-5-COUNTERS: .*"
> action 0.01 syslog msg "blah2 script"
> action 0.02 cli command "enable"
> action 0.03 cli command "term exec prompt timestamp"
> action 0.04
On 3 Jan 2019, at 16:58, Robert Hass wrote:
> How I can check which IP is trying constantly connect via IKEv2 to my
> router ?
Use flow telemetry to look for incoming traffic directed to your router
on UDP/4500?
You could also use a classification ACL. Or if your circumstances
permit, just u
Hi
I have below EEM script running at CSR1K:
event manager applet blah2 authorization bypass
event syslog pattern "%CLEAR-5-COUNTERS: .*"
action 0.01 syslog msg "blah2 script"
action 0.02 cli command "enable"
action 0.03 cli command "term exec prompt timestamp"
action 0.04 cli command "term
> Robert Hass
> Sent: Thursday, January 3, 2019 9:59 AM
>
> Hi
>
> I see a lot syslog messages related to IKEv2:
> Jan 3 10:47:55.537: %IKEV2-5-RECV_CONNECTION_REQUEST: Received a
> IKE_INIT_SA request Jan 3 10:47:55.795: %IKEV2-3-NEG_ABORT: Negotiation
> aborted due to ERROR:
> Failed to loc
Hi
I see a lot syslog messages related to IKEv2:
Jan 3 10:47:55.537: %IKEV2-5-RECV_CONNECTION_REQUEST: Received a
IKE_INIT_SA request
Jan 3 10:47:55.795: %IKEV2-3-NEG_ABORT: Negotiation aborted due to ERROR:
Failed to locate an item in the database
Jan 3 10:48:25.536: %IKEV2-5-RECV_CONNECTION_R