RE: what is wrong with SLA

From: Antonio Soares (amsoares@netcabo.pt)
Date: Sat Sep 29 2007 - 15:20:11 ART


You need to disable control packets:

!
ip sla monitor 1
 type udpEcho dest-ipaddr 1.1.16.22 dest-port 2000 source-ipaddr 1.1.16.6
source-port 2000 control disable
 timeout 6
 frequency 2
ip sla monitor schedule 1 life forever start-time now
!

Rack1R4#
IP: tableid=0, s=1.1.16.6 (local), d=1.1.16.22 (Ethernet1/0), routed via RIB
IP: s=1.1.16.6 (local), d=1.1.16.22 (Ethernet1/0), len 44, sending
    UDP src=2000, dst=2000
Rack1R4#

Regards,

Antonio Soares
CCIE #18473, CCNP, CCIP

-----Original Message-----
From: nobody@groupstudy.com [mailto:nobody@groupstudy.com] On Behalf Of
Joseph Brunner
Sent: sabado, 29 de Setembro de 2007 18:27
To: ccielab@groupstudy.com
Subject: what is wrong with SLA

Does anyone else think IP SLA is a turd? (look at what's wrong with this
picture)

 

ip sla monitor 1

 type udpEcho dest-ipaddr 1.1.16.22 dest-port 2000 source-ipaddr 1.1.16.6
source-port 2000

 timeout 6

 frequency 2

ip sla monitor schedule 1 life forever start-time now

 

*Sep 29 08:56:08.959: IP: tableid=0, s=1.1.16.6 (local), d=1.1.16.22
(GigabitEthernet0/0), routed via RIB

*Sep 29 08:56:08.959: IP: s=1.1.16.6 (local), d=1.1.16.22
(GigabitEthernet0/0), len 80, sending

*Sep 29 08:56:08.959: UDP src=2000, dst=1967

*Sep 29 08:56:08.959: IP: tableid=0, s=1.1.16.6 (GigabitEthernet0/0),
d=1.1.16.22 (GigabitEthernet0/0), routed via RIB

*Sep 29 08:56:08.959: IP: s=1.1.16.6 (GigabitEthernet0/0), d=1.1.16.22
(GigabitEthernet0/0), len 80, rcvd 3

*Sep 29 08:56:08.959: UDP src=2000, dst=1967

 

 

I think Cisco's R&D is choking on Watermelon seeds in the Watermelon juice
in San Jose.



This archive was generated by hypermail 2.1.4 : Sat Oct 06 2007 - 12:01:16 ART