[nsp] RE: cisco-nsp Digest, Vol 11, Issue 17

Fri Oct 10 13:28:49 EDT 2003

The 4700M can go up to 80 MB total, Main and Shared. The Shared is a single
module, the Main must be installed in pairs.

MEM-4700M-32D= 129017A 32 MB DRAM Upgrade (main)
MEM-NP32M-P= 129017A 32 MB Kit
MEM-4700M-16U32D 129017A 32 MB Kit
MEM-4700M-64D= 129121A 64 MB DRAM Upgrade (main)
MEM-NP64M-P= 129121A 64 MB DRAM Upgrade (main)
MEM-4700M-16S= 129020A 16 MB DRAM Upgrade (shared)
MEM-NP16S-P= 129020A 16 MB Module
MEM-4700M-4U16S 129020A 16 MB Module
MEM-4700M-16F= 129032A 16 MB Flash SIMM Upgrade - (2) 8MB Modules
MEM-NP16F-R4-P= 129032A 16 MB Flash SIMM Upgrade - (2) 8MB Modules
MEM-4700M-4U16F 129032A 16 MB Kit

-----Original Message-----
From: cisco-nsp-bounces at puck.nether.net
[mailto:cisco-nsp-bounces at puck.nether.net]On Behalf Of
cisco-nsp-request at puck.nether.net
Sent: Friday, October 10, 2003 12:00 PM
To: cisco-nsp at puck.nether.net
Subject: cisco-nsp Digest, Vol 11, Issue 17

Send cisco-nsp mailing list submissions to
	cisco-nsp at puck.nether.net

To subscribe or unsubscribe via the World Wide Web, visit
	https://puck.nether.net/mailman/listinfo/cisco-nsp
or, via email, send a message with subject or body 'help' to
	cisco-nsp-request at puck.nether.net

You can reach the person managing the list at
	cisco-nsp-owner at puck.nether.net

When replying, please edit your Subject line so it is more specific
than "Re: Contents of cisco-nsp digest..."

Today's Topics:

   1. Determining Memory Layouts on different platforms (Kevin Gannon)
   2. Re: Maximum Flash supported in the CISCO 4700M+ (Gert Doering)
   3. Re: Maximum Flash supported in the CISCO 4700M+ (Gert Doering)
   4. WCCP v2 problem (morph)
   5. Re: rate-limiting (Steve Lim)

----------------------------------------------------------------------

Message: 1
Date: Fri, 10 Oct 2003 09:22:03 +0100
From: Kevin Gannon <kgannon at lancomms.ie>
Subject: [nsp] Determining Memory Layouts on different platforms
To: cisco-nsp at puck.nether.net
Message-ID:
	<4159668C5AA7D4118A40001083FD704201D56527 at ccgate.lancomms.ie>
Content-Type: text/plain;	charset="iso-8859-1"

I found a very useful URL to find the occupied memory banks in a
3600:

http://www.cisco.com/en/US/products/hw/routers/ps274/products_tech_note09186
a0080104555.shtml

Does anyone know how to do this for 7200's and other platforms ?

Thanks & Regards,
Kevin

----------------------------------------------------------------------------
---------
Kevin Gannon                        Phone: +353-1-4093030
NOC Manager
LAN Comms

**********************************************************************
 This email and any files transmitted with it are confidential and
 intended solely for the use of the individual or entity to whom they
 are addressed. If you have received this email in error please notify
 the system manager.

 This footnote also confirms that this email message has been swept for
 the
 presence of computer viruses.

 For more information contact postmaster at lancomms.ie

 phone + 353 1 4093000

 fax + 353 1 4093001
**********************************************************************

------------------------------

Message: 2
Date: Fri, 10 Oct 2003 10:32:03 +0200
From: Gert Doering <gert at greenie.muc.de>
Subject: Re: [nsp] Maximum Flash supported in the CISCO 4700M+
To: Fast Track Technologies <fast_track at vsnl.com>
Cc: cisco-nsp at puck.nether.net
Message-ID: <20031010103203.Y26276 at greenie.muc.de>
Content-Type: text/plain; charset=us-ascii

Hi,

On Fri, Oct 10, 2003 at 01:37:42PM +0530, Fast Track Technologies wrote:
> What is the maximum Flash supported in the CISCO 4700M+?

Searching on www.cisco.com for "flash SIMM 4700" yields the following URL:

http://www.cisco.com/univercd/cc/td/doc/product/access/acs_mod/cis4000/4000m
/4000sig/memory.htm

which claims 16 Mb is the maximum (2 x 8Mb SIMMs).

The funny thing is that this page explicitely mentions a "4800 M" router,
which I've never seen advertised before.  I've seen a reference to the
4800 M on another (memory-upgrade) page, but that could have been a typo -
this page here is very explicit about the differences.

The interesting thing about the 4800 M is that it officially supports
128 Mb of DRAM (!!).

Can anybody shed some light on this?  Is the 4800 M "just" a more recent
board version of the 4700 M?  (I know a colleague that has box that was
purchased as 4700 M but runs fine with 128 Mb of DRAM!)

How can you determine whether a box is a 4700 M or 4800 M?

*wondering*

gert
--
USENET is *not* the non-clickable part of WWW!

//www.muc.de/~gert/
Gert Doering - Munich, Germany
gert at greenie.muc.de
fax: +49-89-35655025
gert at net.informatik.tu-muenchen.de

------------------------------

Message: 3
Date: Fri, 10 Oct 2003 11:46:52 +0200
From: Gert Doering <gert at greenie.muc.de>
Subject: Re: [nsp] Maximum Flash supported in the CISCO 4700M+
To: Fast Track Technologies <fast_track at vsnl.com>
Cc: cisco-nsp at puck.nether.net
Message-ID: <20031010114652.A26276 at greenie.muc.de>
Content-Type: text/plain; charset=us-ascii

Hi,

On Fri, Oct 10, 2003 at 03:15:01PM +0530, Fast Track Technologies wrote:
> My customer insists that the 4700M+ supports 64 MB Flash..and the CISCO
> document supporting this is attached.

Interesting reading indeed.

The document is clearly outdated in a few places (it misses the 4700M
which can go to 64 Mb DRAM).  So I'd tend to believe the CCO document
more.

On the other hand, this is one of the scenarios where it might make sense
to just try it.  4700s are always good for a surprise...

gert

--
USENET is *not* the non-clickable part of WWW!

//www.muc.de/~gert/
Gert Doering - Munich, Germany
gert at greenie.muc.de
fax: +49-89-35655025
gert at net.informatik.tu-muenchen.de

------------------------------

Message: 4
Date: Fri, 10 Oct 2003 14:08:28 +0200
From: morph <morph at 0z0ne.com>
Subject: [nsp] WCCP v2 problem
To: cisco-nsp at puck.nether.net
Message-ID: <3F86A13C.2030407 at 0z0ne.com>
Content-Type: text/plain; charset=us-ascii; format=flowed

Hi all

Any experience with High CPU utilisation with WCCP v2 enabled. Platform
is CISCO 7507 with dCEF.

Even with the wccp disabled but the config still in the running config i
have around 70-80% of CPU load. The load only gets normal values (6%)
when i delete ALL the configuration of wccp in the interfaces where it
was applied.

Regards and greetings (this is my first post in the list :)

JJ

------------------------------

Message: 5
Date: Fri, 10 Oct 2003 10:54:48 -0400
From: Steve Lim <limmer at execpc.com>
Subject: Re: [nsp] rate-limiting
To: cisco-nsp at puck.nether.net
Message-ID: <3F86C838.5000006 at execpc.com>
Content-Type: text/plain; charset=us-ascii; format=flowed

This link explains the Token Bucket concept:
http://www.cisco.com/en/US/products/sw/iosswrel/ps1828/products_configuratio
n_guide_chapter09186a00800ca59f.html

This link takes you the Rate Limits specifically:
http://www.cisco.com/en/US/products/sw/iosswrel/ps1828/products_configuratio
n_guide_chapter09186a00800ca59f.html#32499

Page down a couple of times for the Recomended Burst Values:
http://www.cisco.com/en/US/products/sw/iosswrel/ps1835/products_configuratio
n_guide_chapter09186a00800bd8ed.html#1000977

Based on Cisco recomendation to avoid Tail Drops (and also approximate
the configured rate), you would still configure as follows (of course
you can tweak it if you want :)

interface fe0/0/0
rate-limit input 50000000 9375000 18750000 conform-action transmit
exceed-action drop
rate-limit output 50000000 9375000 18750000 conform-action transmit
exceed-action drop

This follows the following formula:

	normal burst = configured rate * (1 byte)/(8 bits) * 1.5 seconds
	extended burst = 2 * normal burst

Tweaking the replenish rate makes for some interesting times, especially
   if you forget to tell the customer. :}

CAR or class map. Hrmm. How would this work out administratively, say if
one where to apply said strategies if you grow to 20 customers on that
router? Just absent-mindedly wondering.

Taa,

SL

Raymond, Steven wrote:

>>Hi Christopher,
>>
>>I know that when using traditional CAR, your policer
>>bucketsize values
>>are incorrect.  I assume the policer is implemented similarly
>>with the
>>modular QoS on the same platforms.
>
>
> Can anyone point to a CCO link that usefully describes the meaning and use
> of the bucketsize parameters?  In my trial & error testing with a
smartbits,
> I found that the closest approximation to limit a FE circuit to say,
50Mb/s,
> would be something like this:
>
> interface fe0/0/0
> rate-limit input 50000000 12500000 12500000 conform-action transmit
> exceed-action drop
> rate-limit output 50000000 12500000 12500000 conform-action transmit
> exceed-action drop
>
> Where the 12500000s are the actual signalling rate of the media in terms
of
> bytes/second.  With much smaller numbers, smartbits showed that achieved
> throughput was much lower than 50,000,000 bits/second at layer 2 (similar
to
> the original poster's results).  These numbers usually let a little more
> than 50,000,000 bits/sec at layer 2 through, but I'd rather be over than
> under.
>
> Furthermore, is there a difference in the configuration when doing
straight
> interface rate limiting (CAR?) vs the modular QOS style?
>
> Thanks
>
> _______________________________________________
> 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/
>
>

--
<><><><><><><><><><><><><><><><><><><><>
Steve Lim - Network Engineer (Michigan)
Corecomm -An ATX Communications Company
On God's keyboard, he has a "Smite" button
-limmer

------------------------------

_______________________________________________
cisco-nsp mailing list
cisco-nsp at puck.nether.net
https://puck.nether.net/mailman/listinfo/cisco-nsp

End of cisco-nsp Digest, Vol 11, Issue 17
*****************************************