DOCSLIB.ORG

How to Configure Ethernet Network Interface Backup on ~ Bladecenter JS20 with AIX 5L

Total Page：16

File Type：pdf, Size：1020Kb

Download full-text PDF Read full-text
How to Configure Ethernet Network Interface Backup on ~ Bladecenter JS20 with AIX 5L How to configure Ethernet Network Interface Backup on ~ BladeCenter JS20 with AIX 5L White Paper Trina Bunting pSeries Advanced Technical Support September 2005 Table of Contents Introduction.....................................................................................................................3 Prerequisites....................................................................................................................3 Network Interface Backup Overview...............................................................................3 BladeCenter JS20/NIB Configuration Limitations...........................................................4 Sample NIB Environment ...............................................................................................4 My BladeCenter JS20/NIB Environment.........................................................................5 Setting up the CIGESM...................................................................................................8 A. Installing Firmware on the CIGECSM...................................................................8 B. Change the Port Setting on CIGESM .....................................................................9 C. Configure Link State Tracking (Trunk Failover) ....................................................9 Troubleshooting NIB in AIX 5L....................................................................................10 How to Test Adapter Failover .......................................................................................10 A. Testing Adapter Failover from AIX 5L................................................................10 B. Testing Adapter Failover from the CIGESM........................................................11 C. Testing Adapter Failover from the Management Module......................................12 bctrjs20HA090805.doc Page 2 of 13 Introduction This document provides an overview of Network Interface Backup (NIB) feature of the AIX 5L™ operating system as well as how to configure and implement NIB style EtherChannel® on an IBM ~® BladeCenter® JS20 with Cisco Systems® Intelligent Gigabit Ethernet Switch Module (CIGESM). I also cover how to view and troubleshoot your NIB setup in the AIX 5L O/S, as well as, how to successfully test Adapter Failover from AIX 5L, CIGESM and the Management Module. Prerequisites The following hardware/software was used for my configuration and testing: • Two CIGESMs • CIGESM firmware level 12.1(22)AY1 or higher • AIX 5L V5.3 ML2 Although the CIGESM was used for my configuration, other Ethernet Switch Modules can be used as well (i.e. Nortel and DLink Switch Modules). Note: In the recommended version of firmware for the CIGESM, there is a potential problem with using a Management VLAN higher than 255. This problem is planned to be resolved in the next firmware level. Until a fix is available it is recommended to use a Management VLAN between 1 and 255. Also, the CIGESM must not be configured for EtherChannel on any of the downstream ports going to the BladeCenter JS20 blades. Network Interface Backup Overview NIB is designed to protect against a single point of network failure by providing failure detection and failover. In a NIB environment, only one adapter is active at any given time. Two key tests, link status and ping, protect against local link failure and network path failure, respectively. When a failure is detected, all traffic is sent and received on the backup adapter (backup adapter has the same MAC address as the primary adapter when NIB is configured, regardless of whether there’s a failover or not). It provides rapid detection/failover (in 2-4 seconds) with no disruption to currently active user connections. The AIX 5L NIB function is transparent to the network equipment therefore no special hardware or network equipment is needed. The overall effectiveness of this solution depends upon the implementer's knowledge of network design and AIX 5 L system attachments. The goal is to make sure that a single failure (at an adapter, node, or network component) doesn't impact all the AIX 5L links configured for the NIB group. bctrjs20HA090805.doc Page 3 of 13 BladeCenter JS20/NIB Configuration Limitations The BladeCenter JS20 Network Interface Cards (NICs) are hard-wired to two different switches (Bay 1 and Bay 2) in the BladeCenter chassis so only a NIB-style EtherChannel configuration can be implemented. The ent0 NIC is hard wired to Bay 1 and ent1 NIC is hard wired to Bay 2. In a NIB configuration ent0 should be configured as the primary adapter and ent1 should be configured as the backup adapter. Currently, if you configure ent1 as the primary adapter and ent0 as the secondary adapter, Serial Over LAN (SOL) will not function. Note: The SOL function will only work on the ent0 adapter so this function will not be available when the ent1 backup adapter is activated. During this time, the administrator would use telnet to access the BladeCenter JS20. Sample NIB Environment The following diagram is a sample NIB configuration where the Ethernet adapters (ent0 and ent1) are configured as EtherChannel pseudo-device ent2. The en2 interface should be configured to run TCP/IP therefore en0 or en1 will not be used. The ent0 (primary) adapter is active and ent1 is the backup adapter. 9.19.126.108 JS20 00:0d:60:1e:16:c0 Ethernet Switch ent2 Module Bay 1 ent0 en2 ent1 Ethernet Switch Module Bay 2 (backup) The link status test detects failures in the adapter link to the network. This includes adapter failure, cable break, switch or hub unplugged or failed. Link status tests for an electrical signal, meaning link-up or link-down state detection. When the electrical signal disappears, the switch to the backup is immediately triggered. The optional ping test checks the path through the network to the user-specified IP node. By default, the ping test sends a ping every second. If at least one response in three pings (default; can be modified by the user) is received, the network path is considered to be good. If three pings go without a response, failover is triggered. bctrjs20HA090805.doc Page 4 of 13 If the link or ping test on ent0 fails, the NIB software begins receiving traffic for the ent2 pseudo-device on the backup adapter ent1. Once the problem on ent0 has been resolved, all traffic is once again sent and received on the primary adapter. Note: Only if the link has failed will the traffic move back to the primary adapter. If the ping failed it will remain on the backup adapter until it itself fails. My BladeCenter JS20/NIB Environment It is important to consider how the CIGESM is managed before implementing NIB into your environment. In my test environment, the CIGESMs are managed using the Management Module’s (MM) uplink port. The Management Module and Data Traffic are in a common VLAN. The CIGESMs are on an internally different VLAN, but shares Management Module uplink VLAN for management. SOL is provided on a separate VLAN. The feature to manage the CIGESM over its uplink ports MUST be disabled (by setting “External management over all ports” to “Disabled” in the MM Advanced Management section for each CIGESM). For more detailed information on BladeCenter CIGESM Management, refer to the following Redpaper: Cisco Systems Intelligent Gigabit Ethernet Switch Module for IBM eServer™ BladeCenter (http://www.redbooks.ibm.com/abstracts/redp3869.html?Open). Note: Using a single VLAN to carry both user and management traffic is NOT recommended in a Production Environment. The following is a diagram of my test environment. In my environment, the VLANs bctrjs20HA090805.doc Page 5 of 13 are carried as follows: • On ports going to the JS20 Blades (g0/1 – g0/14): Data VLAN 1 SOL VLAN 4094 • On ports going to the MM (g0/15 – g0/16): MM/Switch VLAN 30 SOL VLAN 4094 • On ports going to the JS20 Production Network (g0/17 – g0/20): Data VLAN 1 Setting up NIB in AIX 5L Configuring NIB 1. This step should only be performed if the adapter interfaces are configured. To remove any pre-existing IP interface configurations type the following commands: Type “ifconfig en0 detach” and press “Enter” bctrjs20HA090805.doc Page 6 of 13 Type “rmdev –dl en0” and press “Enter” Type “ifconfig en1 detach” and press “Enter” Type “rmdev –dl en1” and press “Enter” Type “ifconfig et0 detach” and press “Enter” Type “rmdev –dl et0” and press “Enter” Type “ifconfig et1 detach” and press “Enter” Type “rmdev –dl et1” and press “Enter” Note: The above commands can also be executed in smit from the fast path “smitty tcpip”. 2. Verify the network interfaces have been removed: Type “netstat –in” and press “Enter” (You should only see the loopback interface) 3. Create the ent2 pseudo-device: a. Type the fast path “smitty etherchannel” and press “Enter” b. Select “Add an EtherChannel / Link Aggregation” and press “Enter” c. Select “ent0” as the primary adapter and “ent1” as the backup adapter and press “Enter” For more information on setting up Network Interface Backup style EtherChannel refer to the documentation at http://publib.boulder.ibm.com/infocenter/pseries/index.jsp?topic=/com.ibm.aix.doc/inf ocenter/base/aix53.htm. Note: If Jumbo Frames are enabled, the CIGESM is already enabled to support Jumbo Frames with firmware level 12.1(22)AY1. The max frame size on the CIGESM is 9216 bytes. bctrjs20HA090805.doc Page 7 of 13 4. Configure the IP Address for the pseudo-device ent2: a. Type the fast path “smitty chinet” and press “Enter” b. Select “en2” interface and press “Enter” 5. Enter the “IP/Address,
Load more

Recommended publications
  • Etherchannel & Highly Available Cluster Multiprocessing (HACMP) in AIX V5.2
    EtherChannel & Highly Available Cluster Multiprocessing (HACMP) in AIX V5.2 How-to and Test Experiences Abstract: This document gives tips and a working example of how to a Highly Available Cluster Multiprocessing (HACMP) user could implement EtherChannel with HACMP. Support for this combination was announced in May, 2004. Authors: Shawn Bodily (HACMP) and Cindy Young (EtherChannel) of IBM pSeries Advanced Technical Support and Michael Herrera (HACMP) of IBM pSeries AIX Support Introduction IBM AIX pSeries administrators have expressed interest in combining these components for several reasons. Those accustomed to other software availability solutions object to HACMP’s additional “standby” adapter. With EtherChannel, HACMP setups could mask the standby adapter giving an outward appearance familiar to these users. Other users like the aggregated bandwidth, load balancing, or high availability benefits of EtherChannel. The result is a lower cost, high performance network that is also popular as a high speed private (non-switch) interconnect between machines. In this test, we successfully implemented a “single adapter network” HACMP IP Address Takeover (IPAT) with the EtherChannel function included in AIX V 5.2. The EtherChannel was responsible for providing local adapter swapping – outside of HACMP. HACMP has no knowledge of EtherChannel and is completely independent. While a single adapter network is normally not ideal, EtherChannel makes this okay because there are multiple physical adapters within the single EtherChannel pseudo device. Thus, we could safely ignore the insufficient adapter warning messages posted during cluster synchronization. Our configuration consisted of a rotating resource group with a single adapter network using IP aliasing. Our testing proved to be beneficial in simplifying the HACMP setup.
    [Show full text]
  • Etherchannel Configuration Guide, Cisco IOS XE 17 (Cisco NCS 520 Series)
    EtherChannel Configuration Guide, Cisco IOS XE 17 (Cisco NCS 520 Series) First Published: 2019-11-26 Americas Headquarters Cisco Systems, Inc. 170 West Tasman Drive San Jose, CA 95134-1706 USA http://www.cisco.com Tel: 408 526-4000 800 553-NETS (6387) Fax: 408 527-0883 THE SPECIFICATIONS AND INFORMATION REGARDING THE PRODUCTS IN THIS MANUAL ARE SUBJECT TO CHANGE WITHOUT NOTICE. ALL STATEMENTS, INFORMATION, AND RECOMMENDATIONS IN THIS MANUAL ARE BELIEVED TO BE ACCURATE BUT ARE PRESENTED WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED. USERS MUST TAKE FULL RESPONSIBILITY FOR THEIR APPLICATION OF ANY PRODUCTS. THE SOFTWARE LICENSE AND LIMITED WARRANTY FOR THE ACCOMPANYING PRODUCT ARE SET FORTH IN THE INFORMATION PACKET THAT SHIPPED WITH THE PRODUCT AND ARE INCORPORATED HEREIN BY THIS REFERENCE. IF YOU ARE UNABLE TO LOCATE THE SOFTWARE LICENSE OR LIMITED WARRANTY, CONTACT YOUR CISCO REPRESENTATIVE FOR A COPY. The Cisco implementation of TCP header compression is an adaptation of a program developed by the University of California, Berkeley (UCB) as part of UCB's public domain version of the UNIX operating system. All rights reserved. Copyright © 1981, Regents of the University of California. NOTWITHSTANDING ANY OTHER WARRANTY HEREIN, ALL DOCUMENT FILES AND SOFTWARE OF THESE SUPPLIERS ARE PROVIDED “AS IS" WITH ALL FAULTS. CISCO AND THE ABOVE-NAMED SUPPLIERS DISCLAIM ALL WARRANTIES, EXPRESSED OR IMPLIED, INCLUDING, WITHOUT LIMITATION, THOSE OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT OR ARISING FROM A COURSE OF DEALING, USAGE, OR TRADE PRACTICE. IN NO EVENT SHALL CISCO OR ITS SUPPLIERS BE LIABLE FOR ANY INDIRECT, SPECIAL, CONSEQUENTIAL, OR INCIDENTAL DAMAGES, INCLUDING, WITHOUT LIMITATION, LOST PROFITS OR LOSS OR DAMAGE TO DATA ARISING OUT OF THE USE OR INABILITY TO USE THIS MANUAL, EVEN IF CISCO OR ITS SUPPLIERS HAVE BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES.
    [Show full text]
  • Symbols Numerics A
    I N D E X GLOP, 484–485 Symbols IP multicast, 480 limited-scope, 484 ! (exclamation point) character, 105 MAC address notification, 317–318 # (pound sign) character, 105 NAT, 649 reserved link local, 483–484 Numerics source-specific multicast, 484 virtual MAC, 573 10-Gigabit, 54 adjacencies, 393–394, 408 10-Mbps Ethernet, 48 ADSL (asymmetric digital subscriber line), 56 802.1D, compatibility with RSTP, 230 agents, relay (DHCP), 379 802.1Q, 156–158 aggregate policers, 448 802.1X Aggressive mode UDLD (A-UDLD), 336–338, 604 configuration exercise, 663–669 configuration exercises, 354 network access security, 639–641 versus Loop Guard, 272 AppleTalk Remote, 624 applications A Auto QoS, 463 Cisco AVVID, 16 AAA statistics, 291 accounting, 625, 629 voice, 596 authentication, 173, 623–626 Application-Specific Integrated Circuits. See ASICs authorization, 624, 627 applying RACLs, 643 configuration exercise, 663–669 Architecture for Voice, Video and integrated Data. configuring, 630–631 See Cisco AVVID aaa authentication login command, 626 ARP (Address Resolution Protocol), 12 aaa new-model command, 87, 626 DAI, 654–658 access as a security feature, 658–659 firewalls, 647–648 throttling, 396–398 hopping attacks (VLAN), 660–661 ASICs (Application-Specific Integrated Circuits), physical, 619 5–6, 275 unauthorized, 77 assured forwarding, 431–432 access control lists. See ACLs asymmetric digital subscriber line (ADSL), 56 access layer, 18 attacks, 655, 660–661 access-layer switches, 50 attenuation, 720 accounting, 625, 629 A-UDLD (Aggressive mode UDLD), ACLs (access control lists), 4, 618, 643 336–338, 604 PACLs, 646 configuration exercises, 354 RACLs, 643 versus Loop Guard, 272 security, 642 authentication, 173, 623–626 VACLs, 644 authorization, 624, 627 vty lines, 619 auth-proxy, 627 active keyword, 513 Auto QoS, 463 adding switches, 186 auto-negotiation, 53, 767 Address Resolution Protocol.
    [Show full text]
  • Cisco NX-OS Software Virtual Portchannel: Fundamental Concepts
    Chapter 3: Cisco NX-OS Software Virtual PortChannel: Fundamental Concepts © 2010 Cisco Systems, Inc. All rights reserved. This document is Cisco Public Information. Design Guide Contents Virtual PortChannel Technology ................................................................................................................................3 vPC Topologies.........................................................................................................................................................3 Virtual PortChannel Components..............................................................................................................................5 Traffic Flows..............................................................................................................................................................6 Dual-Control Plane with Single Layer 2 Node Behavior............................................................................................7 The Link Aggregation Group Identifier..................................................................................................................7 System ID in a vPC System .................................................................................................................................9 Primary and Secondary vPC Roles ......................................................................................................................9 Spanning Tree....................................................................................................................................................10
    [Show full text]
  • Application Notes
    A Sample Configuration with Design Guidelines for Link Aggregation Between Avaya™ P580/P882 Gigabit Ethernet Switch Hunt Groups and Cisco EtherChannel - Issue 1.0 Abstract These Application Notes describe a sample Hunt Group/EtherChannel Link Aggregation Group (LAG) configuration between an Avaya™ P882 Gigabit Ethernet switch and a Cisco Catalyst 6509 switch. Design guidelines for deploying LAG in a mixed Avaya/Cisco infrastructure are included as an aid for network designers. A sample configuration diagram has been included along with provisioning notes. These Application Notes were created as a result of field requests for information on interoperability between Avaya P580/P882 Hunt group trunks and Cisco EtherChannel. GAK; Reviewed: Solution & Interoperability Test Lab Application Notes 1 of 15 WCH 7/18/2003 ©2003 Avaya Inc. All Rights Reserved. cislaginterop.doc 1. Introduction The Avaya™ P580/P882 Gigabit Ethernet Switch Hunt Group feature aggregates multiple switch ports together, combining the bandwidth into a single connection. This feature is normally deployed between switches to provide added bandwidth and fault tolerance. If one segment in a hunt group fails, the remaining active members will service the traffic for that segment. The Hunt Group Load-Sharing feature (enabled by default) distributes traffic load among the hunt group members for improved throughput performance. Hunt group member ports can be configured using various trunk modes including IEEE 802.1Q, Multi-layer, 3Com and Clear. Hunt group ports may also be assigned a router IP interface for layer 3 forwarding. The Avaya™ Hunt Group feature is a manual (or static) implementation of link aggregation. This means the feature does not support dynamic LAG configuration or binding via some standard or proprietary protocol.
    [Show full text]
  • Chapter 2 Lab 2-2, Configuring Etherchannel
    CCNPv6 SWITCH Chapter 2 Lab 2-2, Configuring EtherChannel Topology Objective • Configure EtherChannel. Background Four switches have just been installed. The distribution layer switches are Catalyst 3560 switches, and the access layer switches are Catalyst 2960 switches. There are redundant uplinks between the access layer and distribution layer. Usually, only one of these links could be used; otherwise, a bridging loop might occur. However, using only one link utilizes only half of the available bandwidth. EtherChannel allows up to eight redundant links to be bundled together into one logical link. In this lab, you configure Port Aggregation Protocol (PAgP), a Cisco EtherChannel protocol, and Link Aggregation Control Protocol (LACP), an IEEE 802.3ad open standard version of EtherChannel. Note: This lab uses Cisco WS-C2960-24TT-L switches with the Cisco IOS image c2960-lanbasek9-mz.122- 46.SE.bin, and Catalyst 3560-24PS with the Cisco IOS image c3560-advipservicesk9-mz.122-46.SE.bin. You can use other switches (such as a 2950 or 3550) and Cisco IOS Software versions if they have comparable capabilities and features. Depending on the switch model and Cisco IOS Software version, the commands available and output produced might vary from what is shown in this lab. Required Resources • 2 switches (Cisco 2960 with the Cisco IOS Release 12.2(46)SE C2960-LANBASEK9-M image or comparable) • 2 switches (Cisco 3560 with the Cisco IOS Release 12.2(46)SE C3560- ADVIPSERVICESK9-M image or comparable) All contents are Copyright © 1992–2010 Cisco Systems, Inc. All rights reserved. This document is Cisco Public Information.
    [Show full text]
  • Chapter 4: Etherchannel and HSRP
    Chapter 4: EtherChannel and HSRP CCNA Routing and Switching Scaling Networks Chapter 4 - Sections & Objectives . 4.1 Link Aggregation Concepts • Explain link aggregation operation in a switched LAN environment. • Describe link aggregation. • Describe EtherChannel technology. 4.2 Link Aggregation Configuration • Implement link aggregation to improve performance on high-traffic switch links. • Configure link aggregation. • Troubleshoot a link aggregation implementation. 4.3 First Hop Redundancy Protocols • Implement HSRP • Explain the purpose and operation of first hop redundancy protocols. • Explain how HSRP operates. • Configure HSRP using Cisco IOS commands. • Troubleshoot HSRP. © 2016 Cisco and/or its affiliates. All rights reserved. Cisco Confidential 2 4.1 Link Aggregation Concepts © 2016 Cisco and/or its affiliates. All rights reserved. Cisco Confidential 3 Link Aggregation Introduction to Link Aggregation . It is possible to combine the number of physical links between switches to increase the overall speed of switch-to-switch communication. • STP will block redundant links to prevent routing loops. Redundant Links with STP (by default blocked) © 2016 Cisco and/or its affiliates. All rights reserved. Cisco Confidential 4 Link Aggregation Advantages of EtherChannel . Most configuration tasks can be done on the EtherChannel interface instead of on each individual port. EtherChannel relies on existing switch ports. Load balancing takes place between links that are part of the same EtherChannel. EtherChannel creates an aggregation that is seen as one logical link. EtherChannel provides redundancy because the overall link is seen as one logical connection. © 2016 Cisco and/or its affiliates. All rights reserved. Cisco Confidential 5 EtherChannel Operation Implementation Restrictions . EtherChannel groups multiple physical ports into one or more logical EtherChannel links.
    [Show full text]
  • Configuring Etherchannels
    Configuring EtherChannels This chapter describes how to configure EtherChannels and to apply and configure the Link Aggregation Control Protocol (LACP) for more efficient use of EtherChannels in Cisco NX-OS. It contains the following sections: • Information About EtherChannels, page 1 • Configuring EtherChannels, page 8 • Verifying EtherChannel Configuration, page 13 Information About EtherChannels An EtherChannel bundles up to 16 individual interfaces into a group to provide increased bandwidth and redundancy. Port channeling also load balances traffic across these physical interfaces. The EtherChannel stays operational as long as at least one physical interface within the EtherChannel is operational. You create an EtherChannel by bundling compatible interfaces. You can configure and run either static EtherChannels or EtherChannels running the Link Aggregation Control Protocol (LACP). Any configuration changes that you apply to the EtherChannel are applied to each member interface of that EtherChannel. For example, if you configure Spanning Tree Protocol (STP) parameters on the EtherChannel, the Cisco NX-OS applies those parameters to each interface in the EtherChannel. You can use static EtherChannels, with no associated protocol, for a simplified configuration. For more efficient use of the EtherChannel, you can use the Link Aggregation Control Protocol (LACP), which is defined in IEEE 802.3ad. When you use LACP, the link passes protocol packets. Related Topics • LACP Overview, page 5 Understanding EtherChannels Using EtherChannels, Cisco NX-OS provides wider bandwidth, redundancy, and load balancing across the channels. You can collect up to 16 ports into a static EtherChannel or you can enable the Link Aggregation Control Protocol (LACP). Configuring EtherChannels with LACP requires slightly different steps than configuring static EtherChannels.
    [Show full text]
  • Introduction to Scaling Networks
    CHAPTER 1 Introduction to Scaling Networks As a business grows, so does its networking requirements. To keep pace with a business’s expansion and new emerging technologies, a network must be designed to scale. A network that scales well is not only one that can handle growing traffic demands, but also one designed with the inevitable need to expand. This short chapter sets the stage for the rest of the course. This chapter covers the hierarchical network design model, the Cisco Enterprise Architecture modules, and appropriate device selections that you can use to systematically design a highly functional network. student.indb 1 3/19/14 3:09 PM 2 CCNA Routing and Switching Practice and Study Guide Implementing a Network Design An enterprise network must be designed to support the exchange of various types of network traffic, including data files, email, IP telephony, and video applications for multiple business units. Hierarchical Network Design Users expect enterprise networks to be up percent of the time. To provide this kind of reliability, enterprise class equipment uses power supplies and has failover capabilities. Describe what failover capability means for enterprise class equipment. Why should a network be organized so that traffic stays local and is not propagated unneces- sarily on to other portions of the network? Designing a network using the three-layer hierarchical design model helps optimize the net- work. In Figure 1-1, label the three layers of the hierarchical design model. Figure 1-1 Hierarchical Design Model Hierarchical Design Model Internet Internet student.indb 2 3/19/14 3:09 PM Chapter 1: Introduction to Scaling Networks 3 Briefly describe each layer of the hierarchical design model.
    [Show full text]
  • LAN Aggregation
    CHAPTER 3 LAN Aggregation Objectives Upon completion of this chapter, you will be able to answer the following questions: n What is link aggregation? n What are the commands to configure EtherChannel? n What is EtherChannel technology? n What are the methods to troubleshoot link aggregation with EtherChannel? Key Terms This chapter uses the following key terms. You can find the definitions in the Glossary. Port Aggregation Protocol (PAgP) page 122 PAgP auto page 127 Link Aggregation Control Protocol LACP active page 129 (LACP) page 122 LACP passive page 129 PAgP desirable page 127 03_SNCG_3282_r2a.indd 121 2/12/14 3:19 PM 122 Scaling Networks Companion Guide Introduction (3.0.1.1) Link aggregation is the ability to create one logical link using multiple physical links between two devices. This allows load sharing among the physical links, rather than having STP block one or more of the links. EtherChannel is a form of link aggrega­ tion used in switched networks. This chapter describes EtherChannel and the methods used to create an Ether­ Channel. An EtherChannel can be manually configured or can be negotiated by using the Cisco­proprietary protocol Port Aggregation Protocol (PAgP) or the IEEE 802.3ad–defined protocol Link Aggregation Control Protocol (LACP). The configuration, verification, and troubleshooting of EtherChannel are discussed. Class Activity 3.0.1.2: Imagine This It is the end of the work day. In your small­ to medium­sized business, you are try­ ing to explain to the network engineers about EtherChannel and how it looks when it is physically set up.
    [Show full text]
  • Etherchannel Between a Cisco Catalyst Switch That Runs Cisco IOS and a Workstation Or Server Configuration Example
    EtherChannel Between a Cisco Catalyst Switch That Runs Cisco IOS and a Workstation or Server Configuration Example Document ID: 98469 Contents Introduction Prerequisites Requirements Components Used Related Products Conventions Background Information Design Guidelines EtherChannel Negotiation Protocols Configure Network Diagram Switch Configuration Server Configuration Verify Troubleshoot Related Information Introduction This configuration example describes how to establish EtherChannel between a Cisco Catalyst Switch that runs Cisco IOS software and a workstation or server. For Cisco Catalyst switches that run the Catalyst OS, refer to Configuring EtherChannel Between a Catalyst Switch Running CatOS and a Workstation or Server. EtherChannel allows multiple physical Ethernet links to combine into one logical channel, which allows the links in the channel to share traffic load, as well as redundancy in the event that one or more links in the channel fail. You can use EtherChannel to interconnect LAN switches, routers, servers, and clients via unshielded twisted pair (UTP) wiring or single−mode and multimode fiber. This document refers to Fast EtherChannel, Gigabit EtherChannel, Port Channel, Channel Group, and Port Group with a single term, EtherChannel. The information in the document applies to all of these EtherChannels. This document covers the configuration of Layer 2 EtherChannel between a Catalyst switch and a server. Prerequisites Requirements Ensure that you meet these requirements before you attempt this configuration: • Cisco Catalyst switch that meets the system requirements to implement EtherChannel. For more information, refer to System Requirements to Implement EtherChannel on Catalyst Switches. Here is a simple command to determine if the switch/module supports EtherChannel: Switch#show interfaces Gi2/0/23 capabilities GigabitEthernet2/0/23 Model: WS−C3750G−24T Type: 10/100/1000BaseTX Speed: 10,100,1000,auto Duplex: half,full,auto Trunk encap.
    [Show full text]
  • Configuring Etherchannels
    Configuring EtherChannels This chapter describes how to configure EtherChannels and to apply and configure the Link Aggregation Control Protocol (LACP) for more efficient use of EtherChannels in Cisco NX-OS. It contains the following sections: • Information About EtherChannels, page 1 • Configuring EtherChannels, page 8 • Verifying EtherChannel Configuration, page 16 • Verifying the Load-Balancing Outgoing Port ID , page 16 Information About EtherChannels An EtherChannel bundles up to 16 individual interfaces into a group to provide increased bandwidth and redundancy. Port channeling also load balances traffic across these physical interfaces. The EtherChannel stays operational as long as at least one physical interface within the EtherChannel is operational. You create an EtherChannel by bundling compatible interfaces. You can configure and run either static EtherChannels or EtherChannels running the Link Aggregation Control Protocol (LACP). Any configuration changes that you apply to the EtherChannel are applied to each member interface of that EtherChannel. For example, if you configure Spanning Tree Protocol (STP) parameters on the EtherChannel, the Cisco NX-OS applies those parameters to each interface in the EtherChannel. You can use static EtherChannels, with no associated protocol, for a simplified configuration. For more efficient use of the EtherChannel, you can use the Link Aggregation Control Protocol (LACP), which is defined in IEEE 802.3ad. When you use LACP, the link passes protocol packets. Related Topics • LACP Overview, page 5 Understanding EtherChannels Using EtherChannels, Cisco NX-OS provides wider bandwidth, redundancy, and load balancing across the channels. Cisco Nexus 3000 Series NX-OS Layer 2 Switching Configuration Guide, Release 5.0(3)U1(1) 1 Configuring EtherChannels Compatibility Requirements An EtherChannel bundles individual links into a channel group to create a single logical link that provides the aggregate bandwidth of up to 16 physical links.
    [Show full text]