[c-nsp] Sup720 -> Sup2T migration and CoPP

[Mack McBride]

Since the processor is faster you may want to open up policies a bit more as well.

Mack McBride | Network Architect | ViaWest, Inc.
O: 720.891.2502 | mack.mcbride at viawest.com | www.viawest.com | LinkedIn | Twitter | YouTube



-----Original Message-----
From: cisco-nsp [mailto:cisco-nsp-bounces at puck.nether.net] On Behalf Of Paul
Sent: Sunday, May 31, 2015 1:03 PM
To: Robert Hass; cisco-nsp at puck.nether.net
Subject: Re: [c-nsp] Sup720 -> Sup2T migration and CoPP

The 2T adds a lot more things that you can match with your CoPP , but it will work fine just copying your existing CoPP setup from the sup720 (you just won't be taking advantage of the new class maps for matching).


On 5/31/2015 7:20 AM, Robert Hass wrote:
> Hi
> I'll have of migration older Cat6500 boxes to new 6807 chassis plus
> Sup2T Supervisors.
>
> I'm only not sure about migration of CoPP configuration ? Anything
> changed between PFC3 (Sup720) and PFC4/DFC4 (Sup2T) regarding this or
> I can just re-apply my current CoPP configuration ?
>
> Any other hint regarding this kind of technology upgrade migration ?
>
> Rob
> _______________________________________________
> 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/
>

--
GloboTech Communications
Phone: 1-514-907-0050 x 215
Toll Free: 1-(888)-GTCOMM1
Fax: 1-(514)-907-0750
paul at gtcomm.net
http://www.gtcomm.net

_______________________________________________
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/
This message contains information that may be confidential, privileged or otherwise protected by law from disclosure. It is intended for the exclusive use of the addressee(s). Unless you are the addressee or authorized agent of the addressee, you may not review, copy, distribute or disclose to anyone the message or any information contained within. If you have received this message in error, please contact the sender by electronic reply and immediately delete all copies of the message.