Configuracion de etherchannel

Solo disponible en BuenasTareas
  • Páginas : 8 (1935 palabras )
  • Descarga(s) : 0
  • Publicado : 4 de noviembre de 2011
Leer documento completo
Vista previa del texto
Configuring EtherChannel Between Catalyst Switches Running Cisco IOS System Software and a Cisco Router
Document ID: 21066
Introduction Prerequisites Requirements Components Used Conventions Important Notes Configure Network Diagram Configurations Verify show Commands Sample show Command Output Troubleshoot NetPro Discussion Forums − Featured Conversations Related Information

IntroductionThis sample configuration demonstrates how to set up a Layer 3 (L3) EtherChannel, without VLAN trunking, between a Cisco router and a Cisco Catalyst 6500 switch running Cisco IOS® System Software. EtherChannel can be called Fast EtherChannel (FEC) or Gigabit EtherChannel (GEC); the term depends on the speed of the interfaces or ports you use to form the EtherChannel. In this example, two FastEthernet ports from a Cisco router and a Catalyst 6500 switch have been bundled into a FEC. Throughout this document, the terms FEC, GEC, port channel, channel, and port group all refer to EtherChannel. This document includes only the configuration files from the switch and router, and the output from the related sample show commands.

Prerequisites
Requirements
Before you attempt thisconfiguration, ensure that you meet these requirements: • Catalyst 6500/6000 and 4500/4000 series switches running Cisco IOS Software: ♦ Catalyst 6500/6000 and 4500/4000 series switches running Cisco IOS Software support both Layer 2 (L2) and L3 EtherChannel, with up to eight compatibly configured Ethernet interfaces on any module. All interfaces in each EtherChannel must be the same speed. All must beconfigured as either L2 or L3 interfaces. ♦ EtherChannel load balancing can use either MAC addresses, IP addresses, or the TCP port numbers. Note: The selected mode applies to all EtherChannels configured on the switch.

♦ Catalyst 6500/6000 Cisco IOS Software Release 12.1E or later and Catalyst 4500/4000 Cisco IOS Software Release 12.1(8a)EW or later. • Cisco routers: ♦ IP traffic distributes overthe port channel interface while traffic from other routing protocols sends over a single link. Bridged traffic distributes on the basis of the L3 information in the packet. If the L3 information does not exist in the packet, the traffic sends over the first link. • A wide variety of Cisco routers support EtherChannel. To find a platform or version of code that supports EtherChannel on a Ciscorouter, use the Cisco Feature Navigator II ( registered customers only) . A list of routers and Cisco IOS Software releases that support EtherChannel is found under the FEC feature. For hardware and software requirements for EtherChannel on other Cisco products, refer to System Requirements to Implement EtherChannel on Catalyst Switches.

Components Used
The information in this document is based onthese software and hardware versions: • Catalyst 6500 switch running Cisco IOS Software Release 12.1(8b)E10 • Cisco 7500 router running Cisco IOS Software Release 12.1(21) The switch configuration in this document applies to any Catalyst 6500/6000 and any Catalyst 4500/4000 series switch running Cisco IOS Software. The information in this document was created from the devices in a specific labenvironment. All of the devices used in this document started with a cleared (default) configuration. If your network is live, make sure that you understand the potential impact of any command. Note: Use of the write erase command cleared the configurations on all devices to ensure that they had a default configuration. Make sure to reload the devices after you issue the write erase command to flushall the nondefault configurations.

Conventions
Refer to Cisco Technical Tips Conventions for more information on document conventions.

Important Notes
If you initially issue the channel−group command under the physical interface, it automatically creates the port−channel interface. If you configured the port−channel interface before you channeled physical interfaces, remove the...
tracking img