[c-nsp] 3550 layer 3 switch replacement for v6

Mark Price mprice at tqhosting.com
Sat Dec 11 22:45:43 EST 2010


I tested a 3560G-24 to replace 3550 switches doing layer 3 like you are
talking about.  Ran into TCAM overflow after switching to an ipv4+ipv6 SDM
template.  The limits advertised are under 'ideal' conditions and not real
world as you would suspect.  I think using OSPF for your routing greatly
reduces the routing resources that SDM templates advertise.

My only suggestion is to test yourself and not trust spec sheets, and
consider moving Layer3 to a bigger core switch and keeping your 3550s for
layer 2 only.


Regards,

Mark



On Thu, Dec 9, 2010 at 3:54 PM, Jon Lewis <jlewis at lewis.org> wrote:

> I need to start looking at replacing 3550-48 switches with something
> comparable that supports ipv6.  I tried using feature navigator, but the
> info it was giving me was so suspect I won't even bother repeating it.  My
> impression from past looks into this issue is that the 3560-48TS (which
> actually went end of sales earlier this year) is a comparable switch to the
> 3550, does ipv6 in hardware, but has far less flexible per port policing,
> which will require a total redesign of our customer port limits.
>
> I'm wondering if there are any major surprises with the 3560 when you
> enable ipv6 routing and ipv6 ospf?  I know doing so cuts the supported
> number of routes in half.  Also, we've kind of been abusing the 3550s, by
> running them with generally most of the ports in layer 3 mode.  The
> "recommended" number of routed interfaces on a 3550-48 is only 8!  Can we
> get away with running 48 dual-stack layer 3 ports on a 3560-48TS?
>
> Or is there a better switch I should be looking at?  Is the 3560 v2
> appreciably better than the original?  It looks like the only change we'd
> benefit from is lower power consumption.  They run the same software, so
> features should be the same.
>
> ----------------------------------------------------------------------
>  Jon Lewis, MCP :)           |  I route
>  Senior Network Engineer     |  therefore you are
>  Atlantic Net                |
> _________ http://www.lewis.org/~jlewis/pgp<http://www.lewis.org/%7Ejlewis/pgp>for PGP public key_________
> _______________________________________________
> 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/
>


More information about the cisco-nsp mailing list