So, noticed something weird...
Got a 2851 with 512MB or RAM... if I have a constant ping going thru the
router and I write mem, the ping goes up by a factor of 5
Cisco 2851 (revision 53.50) with 507904K/16384K bytes of memory.
Processor board ID FTX1345A0EY
2 Gigabit Ethernet interfaces
51
So, is this normal?
Ours does it. I wouldn't worry about it - it does not mean packet
forwarding will be adversely affected.
___
cisco-nsp mailing list cisco-nsp@puck.nether.net
https://puck.nether.net/mailman/listinfo/cisco-nsp
archive at
It is an IP address past the router, on the other side of the WAN...
Jonathan
On Mon, Jan 25, 2010 at 7:47 AM, Byrd, William w...@collier-byrd.netwrote:
Is that IP address on an interface in the router or something behind it?
William Collier-Byrd / w...@collier-byrd.net
Make note, my
Are you pinging through (i.e. from one device on one side of the router
through to another device on the other side of the router) or are you
pinging an interface on the router? Packets forwarded through the router
really shouldn't be affected. Pinging the router itself will definitely
be
On 25/01/10 13:55, Joe Maimon wrote:
Phil Mayers wrote:
So, is this normal?
Ours does it. I wouldn't worry about it - it does not mean packet
forwarding will be adversely affected.
___
Depends if he is pinging the router or pinging through it,
On (2010-01-25 09:34 -0600), Tony Varriale wrote:
If you are pinging through the router, no that is not normal. There
will always be some delay while it writes to media. But, it should
not affect the forwarding path.
It does, but only slightly, 'write' and 'dir' will both do that, as they
@puck.nether.net
Sent: Monday, January 25, 2010 7:27 AM
Subject: [c-nsp] Wr mem causes massive delay...
So, noticed something weird...
Got a 2851 with 512MB or RAM... if I have a constant ping going thru the
router and I write mem, the ping goes up by a factor of 5
Cisco 2851 (revision 53.50
On 1/25/10 8:07 AM, Church, Charles wrote:
This is a software based router, and 'wri mem' is very CPU intensive. What
does the CPU look like before the wri mem is done? I don't think this is
abnormal.
Very large config on an already busy router with compress-config turned on?
~Seth
It is a big config... cuz of all the voipy stuff.
J
On Mon, Jan 25, 2010 at 11:14 AM, Seth Mattinen se...@rollernet.us wrote:
On 1/25/10 8:07 AM, Church, Charles wrote:
This is a software based router, and 'wri mem' is very CPU intensive.
What does the CPU look like before the wri mem is
Assuming the config isn't huge and your router is already oversubbed you
shouldn't be able to tell.
tv
- Original Message -
From: Saku Ytti s...@ytti.fi
To: cisco-nsp@puck.nether.net
Sent: Monday, January 25, 2010 10:06 AM
Subject: Re: [c-nsp] Wr mem causes massive delay
On 1/25/2010 11:53, Tony Varriale wrote:
Assuming the config isn't huge and your router is already oversubbed you
shouldn't be able to tell.
Well, he does have 64 interfaces, so it's probably large-ish.
~Seth
___
cisco-nsp mailing list
@puck.nether.net
Sent: Monday, January 25, 2010 11:40 AM
Subject: Re: [c-nsp] Wr mem causes massive delay...
It is a big config... cuz of all the voipy stuff.
J
On Mon, Jan 25, 2010 at 11:14 AM, Seth Mattinen se...@rollernet.us
wrote:
On 1/25/10 8:07 AM, Church, Charles wrote
- Original Message -
From: Tony Varriale tvarri...@comcast.net
To: cisco-nsp@puck.nether.net
Sent: Monday, January 25, 2010 1:53 PM
Subject: Re: [c-nsp] Wr mem causes massive delay...
Assuming the config isn't huge and your router is already oversubbed you
shouldn't be able to tell
On (2010-01-25 14:00 -0600), Tony Varriale wrote:
Assuming the config isn't huge and your router isn't already
oversubbed you shouldn't be able to tell.
It doesn't really matter, interrupt is interrupt, while compiling the
config is what you can do, when you don't have packets to push, but
14 matches
Mail list logo
