Understanding Etherchannel Load Balancing and Redundancy on Catalyst Switch...Page 1 of 10
Total Page:16
File Type:pdf, Size:1020Kb
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. -
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. -
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. -
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 -
SRD Configuration Guide October 21, 2008
Cisco Persistent Storage Device for Cisco IOS Release 12.2(33)SRD Configuration Guide October 21, 2008 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 following information is for FCC compliance of Class A devices: This equipment has been tested and found to comply with the limits for a Class A digital device, pursuant to part 15 of the FCC rules. These limits are designed to provide reasonable protection against harmful interference when the equipment is operated in a commercial environment. This equipment generates, uses, and can radiate radio-frequency energy and, if not installed and used in accordance with the instruction manual, may cause harmful interference to radio communications. Operation of this equipment in a residential area is likely to cause harmful interference, in which case users will be required to correct the interference at their own expense. -
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. -
Cisco Enterprise Networks Catalog Volume 5: Europe, Middle East, Africa and Russia #Networkintuitive 02 Switches Wireless Routing
Constantly learning, constantly adapting, constantly protecting Built on Cisco DNA Cisco Enterprise Networks Catalog Volume 5: www.cisco.com/go/DNA Europe, Middle East, Africa and Russia #networkintuitive 02 Switches Wireless Routing Cisco Catalog - EMEAR Switches No SDA/SDA Switches P20 Vol.5 Cisco Catalyst 2960-CX Series P26 Cisco Catalyst 3560-CX Series P26 Security Cisco Catalyst 2960-L Series Switches P27 Cisco Catalyst 2960-X Series P28 Cisco Catalyst 3650 Series P28 Cisco Catalyst 3850 Series P31 Index Cisco Catalyst 4500E Series P33 Cisco Catalyst 4500-X Series P35 Cisco Catalyst 6800 Series P36 Cisco Nexus 7700 Switches P37 Cisco Meraki Cisco Catalyst 9300 Series Switches P40 Cisco Catalyst 9400 Series Switches P41 Cisco Catalyst 9500 Series Switches P42 Modules & Accessories P45 What's New Subscription-based software P46 Wireless Switches Cisco Virtual Beacon P54 DNA-Center Revolutionary Cisco Aironet Access Points P57 ■ Indoor Access Points P57 Catalyst 9000 Series ■ Outdoor Access Points P59 P16 ■ Cisco Aironet Antennas and Accessories P60 Cisco Wireless Controllers P62 Subscription-based software P64 Cisco DNA for Access Routing Wireless and Switching Subscription Cisco ISR 800 Series P69 Introducing New Software Cisco ISR 1000 Series P70 Subscription Licensing Cisco ISR 4000 Series P71 SMB Modules & Accessories P17 P72 Cisco Enterprise Network Functions Virtualization (ENVF) P74 Cisco 5000 Series Enterprise Network Compute System P75 Cisco SD WAN Wireless P76 Cisco Wide Area Application Services (WAAS) P78 Cisco® Aironet® -
In the United States Bankruptcy Court for the District of Delaware
Case 21-10457-LSS Doc 237 Filed 05/13/21 Page 1 of 2 IN THE UNITED STATES BANKRUPTCY COURT FOR THE DISTRICT OF DELAWARE Chapter 11 In re: Case No. 21-10457 (LSS) MOBITV, INC., et al., Jointly Administered Debtors.1 Related Docket Nos. 73 and 164 NOTICE OF FILING OF SUCCESSFUL BIDDER ASSET PURCHASE AGREEMENT PLEASE TAKE NOTICE that, on April 7, 2021, the United States Bankruptcy Court for the District of Delaware (the “Bankruptcy Court”) entered the Order (A) Approving Bidding Procedures for the Sale of Substantially All Assets of the Debtors; (B) Approving Procedures for the Assumption and Assignment of Executory Contracts and Unexpired Leases; (C) Scheduling the Auction and Sale Hearing; and (D) Granting Related Relief [Docket No. 164] (the “Bidding Procedures Order”).2 PLEASE TAKE FURTHER NOTICE that, pursuant to the Bidding Procedures Order, the Debtors conducted an auction on May 11-12, 2021 for substantially all of the Debtors’ assets (the “Assets”). At the conclusion of the auction, the Debtors, in consultation with their advisors and the Consultation Parties, selected the bid submitted by TiVo Corporation (the “Successful Bidder”) as the Successful Bid. PLEASE TAKE FURTHER NOTICE that, on May 12, 2021, the Debtors filed the Notice of Auction Results [Docket No. 234] with the Bankruptcy Court. PLEASE TAKE FURTHER NOTICE that attached hereto as Exhibit A is the Asset Purchase Agreement dated May 12, 2021 (the “Successful Bidder APA”) between the Debtors and the Successful Bidder. PLEASE TAKE FURTHER NOTICE that a hearing is scheduled for May 21, 2021 at 2:00 p.m. -
Cisco Catalyst 6500 Series Virtual Switching System White Paper
White Paper Cisco Catalyst 6500 Series Virtual Switching System White Paper December, 2012 © 2012 Cisco and/or its affiliates. All rights reserved. This document is Cisco Public Information. Page 1 of 55 Contents Introduction .............................................................................................................................................................. 3 Cisco Catalyst 6500 Series Virtual Switching System: An Overview .................................................................. 3 Cisco Catalyst 6500 Series Virtual Switching System Architecture .................................................................... 3 Virtual Switch Link ................................................................................................................................................... 7 Virtual Switch Link Initialization ............................................................................................................................. 8 Hardware and Software Requirements ................................................................................................................ 10 Virtual Switch Link Redundancy .......................................................................................................................... 13 Multiple Cisco Virtual Switching System Domains ............................................................................................. 15 Cisco EtherChannel Concepts ............................................................................................................................ -
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. -
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. -
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.