[c-nsp] Replace a 2950 with a 3550.

[Siva Valliappan]

Hi Keith,

     are you going to enable L3 routing on the 3550?  if not, and the
3550 is going to be used as a drop in replacement to increase the
number of ports and switching capacity there should be no impact 
at least from a L2 infrastructure.

     now if you plan to enable L3 routing on the 3550 so as to handle
the redirect for your /24 it's going to be a different issue.
what is your topology like?

is it?

-- remote DHCP server -- 3550 -- CMTS #1
-- local DHCP server --       -- CMTS #2
                                -- CMTS #3

my suggestion would be to avoid routing in this scenario as you don't
need it.  just have CMTS #1, #2, and the link to the remote DHCP server
be in one VLAN.  and the local DHCP server and the CMTS#3 in a second 
VLAN.  This way your production and test traffic would be kept separate.

if you want to maintain remote access, you could possibly look into 
enabling IP Routing and RIPv2 (you need the EMI feature set) between
the 2 VLANs.

cheers
.siva

On Wed, 28 Feb 2007, Keith Woodworth wrote:

>
> Long time listener, first time poster.
>
> Have to replace a 2950 with a 3550.
>
> The 2950 has 3 CMTS's attached to it, 2 of them are announcing 10.0.0.0
> and 24.0.0.0 via Ripv2. DHCP service for the 2 CMTS units is located
> remotely. The 10 network being used is 10.60.0.0/20.
>
> I would like to add the 3rd CMTS but for testing purposes use a local DHCP
> server using 10.200.1.0/24 for testing.
>
> If I replace the 2950 with a 3550 how will the command ip routing affect
> RIP?
>
> I would like to route the /24 using a static route so the 3rd CMTS will be
> able to see the local DHCP server.
>
> As it stands now with the 2950 the 3rd CMTS can not get DHCP requests to
> the local DHCP server, hence why I would like to put in a 3550. The 3rd
> CMTS will be a replacement unit for one of the others and I need to test
> it out before going live with it.
>
> Thanks for any info.
> Keith
> _______________________________________________
> 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/
>