[c-nsp] Appletalk in C6500 sup720

Tim Stevenson tstevens at cisco.com
Thu Sep 29 13:00:43 EDT 2005


Enterprise FS is only required if you want to route AT. To do 
fallback bridging of AT, you can configure bridge-groups under your 
vlan interfaces (SVIs) using the vlan-bridge protocol. This is, of 
course, totally in software (well, so is AT routing). You can get 
about 150Kpps max doing FBB of AT in Sup720, with 100% CPU.

Tim

At 09:12 AM 9/29/2005, Voll, Scott pronounced:
>I haven't had to bridge Appletalk since we upgraded to a sup 720 but
>with the sup1a/msfc2 you had to have the enterprise IOS (not cheap) and
>under each vlan configure:
>
>Appletalk cable-range <range>
>Appletalk zone <name>
>
>And of course global command:
>
>appletalk routing
>
>Scott
>
>
>
>-----Original Message-----
>From: cisco-nsp-bounces at puck.nether.net
>[mailto:cisco-nsp-bounces at puck.nether.net] On Behalf Of Ruben Montes
>Sent: Thursday, September 29, 2005 8:55 AM
>To: cisco-nsp at puck.nether.net
>Subject: [c-nsp] Appletalk in C6500 sup720
>
>Hello,
>
>We are implementing vlans in a customer's existing network and we have
>found that there are some machines running Appletalk. I need to bridge
>this protocol because some Appletalk machines are in different vlans...
>The backbone is composed of two cat6500 sup720 running 12.2SX
>
>Any help would be appreciated,
>
>Ruben
>
>
>_______________________________________________
>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/
>
>_______________________________________________
>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/



Tim Stevenson, tstevens at cisco.com
Routing & Switching CCIE #5561
Technical Marketing Engineer, Catalyst 6500
Cisco Systems, http://www.cisco.com
IP Phone: 408-526-6759
********************************************************
The contents of this message may be *Cisco Confidential*
and are intended for the specified recipients only.


More information about the cisco-nsp mailing list