04-08-2025 04:01 PM - edited 04-08-2025 04:03 PM
Hello
I want to configure this code in Cisco 3850 but when i do the past to cli in the 3850, i get an error:
track 1 ip sla 1 reachability
!
!
ip route 10.8.254.73 255.255.255.255 10.8.254.58 track 1
!
!
ip sla 1
icmp-echo 10.8.254.73 source-ip 10.8.254.57
threshold 20
timeout 1000
frequency 20
ip sla schedule 1 life forever start-time now
!
!
event manager applet noshutInterface2
event track 1 state down
action 10 cli command "enable"
action 11 cli command "conf t"
action 12 cli command "interface Te1/0/1"
action 13 cli command "no shut"
action 14 cli command "interface Te1/0/2"
action 15 cli command "no shut"
action 28 cli command "exit"
event manager applet shutInterface2
event track 1 state up
action 10 cli command "enable"
action 11 cli command "conf t"
action 12 cli command "interface Te1/0/1"
action 13 cli command "shut"
action 14 cli command "interface Te1/0/2"
action 15 cli command "shut"
action 28 cli command "exit"
The error is i cant configure this line:
"event track 1 state down"
Only "event " command is allowed, after that i cant write "track" :
Only options:
sw1-ed(config-applet)# event ?
application Application specific event
cli CLI event
config Configuration policy event
counter Counter event
env Environmental event
gold GOLD event
identity Identity event
interface Interface event
ioswdsysmon IOS WDSysMon event
mat MAC address table event
neighbor-discovery Neighbor Discovery event
none Manually run policy event
oir OIR event
rf Redundancy Facility event
routing Routing event
rpc Remote Procedure Call event
snmp SNMP event
snmp-notification SNMP Notification Event
snmp-object SNMP object event
syslog Syslog event
tag event tag identifier
timer Timer event
So i cant configure all the SLA...
Any help?
Best regards,
Solved! Go to Solution.
04-09-2025 01:42 AM
Your're welcome @rpalmeida
No, the number of hops between your device and the target IP address does not prevent syslog messages from being generated. IP SLA feature is designed to monitor the reachability of remote IP addresses, regardless of their distance in term of hops. When an IP sla operation detect a change in the state of the tracked IP—such as transitioning from reachable to unreachable—it can trigger a syslog message on the local device where the IP SLA is configured...
04-08-2025 09:33 PM - edited 04-08-2025 09:33 PM
Hello @rpalmeida
Use a syslog event instead:
event syslog pattern "%TRACK-6-STATE: 1 ip sla 1 reachability Up -> Down"
--ensure on your log that is the good message...but I think it should work this way.
04-09-2025 01:02 AM
Hello M02@rt37
Thanks for your fast answer.
Tell me something, the IP that i´m tracking is 2 hops for distance, i have other switch in the middle, i think i won´t receive syslog because isnt directly connect...is that true?
Best Regards.
04-09-2025 01:42 AM
Your're welcome @rpalmeida
No, the number of hops between your device and the target IP address does not prevent syslog messages from being generated. IP SLA feature is designed to monitor the reachability of remote IP addresses, regardless of their distance in term of hops. When an IP sla operation detect a change in the state of the tracked IP—such as transitioning from reachable to unreachable—it can trigger a syslog message on the local device where the IP SLA is configured...
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide