topic Re: IP SLA Configuration on S6 Chasssis in ExtremeSwitching (EOS)

IP SLA Configuration on S6 Chasssis

Alexander_Bauer — Thu, 01 Oct 2020 17:50:47 GMT

Hi,

does anyone have any idea how this Cisco configuration works on an S6 chassis?ip sla 1 http raw http://<IP> timeout 5000 threshold 500 http-raw-request  GET http://gateway.<Cloud Name>.net/vpntest HTTP/1.0\r\n  User-Agent: Cisco IP SLA\r\n  end\r\n  \r\n  \r\n  \r\n  exit

Thansk for your help.

Re: IP SLA Configuration on S6 Chasssis

SamPirok — Fri, 02 Oct 2020 21:58:20 GMT

Hi Alexander, I reviewed your question with our top EOS engineers but we would need to know more about the Cisco implementation before we can answer your question. In general, it looks like that command tracks response times to various queries, but if you’re using ICMP you shouldn’t need to do anything for that with EOS devices. I think we’d need to open a support case to dig in to this request a bit further.

Re: IP SLA Configuration on S6 Chasssis

Alexander_Bauer — Tue, 06 Oct 2020 14:10:52 GMT

Hi,

we have tried this configuration at the EOS Switch:

This sould be a L7 Check. Open a connection to 172.21.58.146 via GRE Tunnel and then checks the http request.

But if i map the probe to the tunnel interface the tunnel goes immediately down.

probe ZscalerGRE1 tcp
acv request "GET http://gateway.zscloud.net/vpntest HTTP/1.0\\r\\nUser-Agent: Cisco IP SLA\\r\\nend\\r\\n\\r\\n\\r\\n\\r\\n"
faildetect interval 120
passdetect interval 180
inservice
exit
!
ip slb serverfarm ZscalerGRE-FFM
real 172.21.58.146 port 80
   faildetect probe one ZscalerGRE1
   inservice
   exit
exit