[c-nsp] Wr mem causes massive delay...

Jon Lewis jlewis at lewis.org
Mon Jan 25 08:50:21 EST 2010


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 affected by things that use a lot of CPU.

On Mon, 25 Jan 2010, Jonathan Charles wrote:

> 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 Serial interfaces
> 6 Channelized/Clear T1/PRI ports
> 1 Virtual Private Network (VPN) Module
> 4 Voice FXS interfaces
> DRAM configuration is 64 bits wide with parity enabled.
> 239K bytes of non-volatile configuration memory.
> 126000K bytes of ATA CompactFlash (Read/Write)
>
>
>
>
> Reply from 172.16.2.11: bytes=32 time=32ms TTL=60
> Reply from 172.16.2.11: bytes=32 time=34ms TTL=60
> Reply from 172.16.2.11: bytes=32 time=133ms TTL=60
> Reply from 172.16.2.11: bytes=32 time=30ms TTL=60
> Reply from 172.16.2.11: bytes=32 time=25ms TTL=60
>
> So, is this normal?
>
>
>
> Jonathan
> _______________________________________________
> cisco-nsp mailing list  cisco-nsp at puck.nether.net
> https://puck.nether.net/mailman/listinfo/cisco-nsp
> archive at http://puck.nether.net/pipermail/cisco-nsp/
>

----------------------------------------------------------------------
  Jon Lewis                   |  I route
  Senior Network Engineer     |  therefore you are
  Atlantic Net                |
_________ http://www.lewis.org/~jlewis/pgp for PGP public key_________


More information about the cisco-nsp mailing list