*Here is the official Cisco info on this:*
**
http://www.cisco.com/en/US/technologies/tk648/tk362/tk920/technologies_qas090
0aecd8017bd5a.html
*Q.* To what extent does Cisco IOS IP SLAs impact CPU utilization or
memory?
*A.* As Cisco IOS IP SLAs is a software-based measurement, it does consume
CPU usage and memory.
Table 2 illustrates the CPU usage based on 2,000 active operations,
activated sequentially. The data generated per operation is 10 packets of 64
byte sizing, with 20ms spacing using the IP SLAs jitter operation. The data
represents four destinations, activated per one second versus percentage of
CPU usage in a 12.4 Cisco IOS release.
*Table 2.* Cisco IOS IP SLAs CPU Usage
Operations/ Second
Operations/ Minute
2620XM
3725
7200VXR
NPE-G1
4
240
7
2
0
The memory used per Cisco IOS IP SLAs operation does vary with different
Cisco IOS Software releases.
*Table 3.* Cisco IOS IP SLAs Memory Usage
Cisco IOS Software 12.2 and above
UDP Jitter
< 12KB
UDP Echo
< 3.5KB
ICMP Echo
< 3.2 KB
Larry Hadrava
CCIE #12203 CCNP CCNA
Sr. Support Engineer IPexpert, Inc.
URL: http://www.IPexpert.com
On Tue, Apr 21, 2009 at 4:34 PM, David Prall <dcp_at_dcptech.com> wrote:
> I'd say minimal. I have 10 tracked objects, using 6 ip sla's, with 4 EEM
> Applet's, and 1 static route using EOT.
>
> #sh proc cpu | i SLA
> 221 17320 2227937 7 0.00% 0.00% 0.00% 0 IP SLAs Event
> Pr
>
> #sh proc 221
> Process ID 221 [IP SLAs Event Processor], TTY 0
> Memory usage [in bytes]
> Holding: 17208, Maximum: 48332, Allocated: 42236, Freed: 6328
> Getbufs: 0, Retbufs: 0, Stack: 2668/6000
> CPU usage
> PC: 8148B528, Invoked: 2227938, Giveups: 1993513, uSec: 7
> 5Sec: 0.00%, 1Min: 0.00%, 5Min: 0.00%, Average: 0.00%
> Age: 7864535564 msec, Runtime: 17320 msec
> State: Waiting for Event, Priority: Normal
>
> #sh proc cpu | i Track
> 92 0 2 0 0.00% 0.00% 0.00% 0 IP Host Track
> Pr
> 174 0 3 0 0.00% 0.00% 0.00% 0 EEM ED Track
> 206 5880 9934593 0 0.00% 0.00% 0.00% 0 Track
>
> #sh proc 92
> Process ID 92 [IP Host Track Process], TTY 0
> Memory usage [in bytes]
> Holding: 10244, Maximum: 10496, Allocated: 252, Freed: 252
> Getbufs: 0, Retbufs: 0, Stack: 8576/9000
> CPU usage
> PC: 818FC84C, Invoked: 2, Giveups: 0, uSec: 0
> 5Sec: 0.00%, 1Min: 0.00%, 5Min: 0.00%, Average: 0.00%
> Age: 7864659936 msec, Runtime: 0 msec
> State: Waiting for Event, Priority: Normal
>
> #sh proc 174
> Process ID 174 [EEM ED Track], TTY 0
> Memory usage [in bytes]
> Holding: 13976, Maximum: 13976, Allocated: 3732, Freed: 0
> Getbufs: 0, Retbufs: 0, Stack: 8332/9000
> CPU usage
> PC: 80A85968, Invoked: 3, Giveups: 1, uSec: 0
> 5Sec: 0.00%, 1Min: 0.00%, 5Min: 0.00%, Average: 0.00%
> Age: 7864632804 msec, Runtime: 0 msec
> State: Waiting for Event, Priority: Normal
>
> #sh proc 206
> Process ID 206 [Track], TTY 0
> Memory usage [in bytes]
> Holding: 7696, Maximum: 42784, Allocated: 690736, Freed: 61972
> Getbufs: 0, Retbufs: 0, Stack: 3216/6000
> CPU usage
> PC: 816C8614, Invoked: 9934668, Giveups: 0, uSec: 0
> 5Sec: 0.00%, 1Min: 0.00%, 5Min: 0.00%, Average: 0.00%
> Age: 7864634104 msec, Runtime: 5880 msec
> State: Waiting for Event, Priority: Normal
>
> --
> http://dcp.dcptech.com
>
>
> > -----Original Message-----
> > From: nobody_at_groupstudy.com [mailto:nobody_at_groupstudy.com] On Behalf Of
> > S Malik
> > Sent: Tuesday, April 21, 2009 4:01 PM
> > To: Cisco certification
> > Subject: IP SLA Monitor
> >
> > Is there any impact of "ip sla monitor" on CPU?
> >
> > I need to configure some static routes across an EVPL circuit,
> > therefore I
> > like to verify end-to-end connectivity.
> >
> >
> > Blogs and organic groups at http://www.ccie.net
> >
> > _______________________________________________________________________
> > Subscription information may be found at:
> > http://www.groupstudy.com/list/CCIELab.html
>
>
> Blogs and organic groups at http://www.ccie.net
>
> _______________________________________________________________________
> Subscription information may be found at:
> http://www.groupstudy.com/list/CCIELab.html
Blogs and organic groups at http://www.ccie.net
Received on Tue Apr 21 2009 - 16:53:41 ART
This archive was generated by hypermail 2.2.0 : Mon May 04 2009 - 07:39:12 ART