Configuration Ethernet Avaya Advanced Gateway 2330 AG NN , 01.01

Transcription

1 Configuration Ethernet Avaya Advanced Gateway 2330 AG NN , August 2010

2 2010 Avaya Inc. All Rights Reserved. Notice While reasonable efforts have been made to ensure that the information in this document is complete and accurate at the time of printing, Avaya assumes no liability for any errors. Avaya reserves the right to make changes and corrections to the information in this document without the obligation to notify any person or organization of such changes. Documentation disclaimer Avaya shall not be responsible for any modifications, additions, or deletions to the original published version of this documentation unless such modifications, additions, or deletions were performed by Avaya. End User agree to indemnify and hold harmless Avaya, Avaya's agents, servants and employees against all claims, lawsuits, demands and judgments arising out of, or in connection with, subsequent modifications, additions or deletions to this documentation, to the extent made by End User. Link disclaimer Avaya is not responsible for the contents or reliability of any linked Web sites referenced within this site or documentation(s) provided by Avaya. Avaya is not responsible for the accuracy of any information, statement or content provided on these sites and does not necessarily endorse the products, services, or information described or offered within them. Avaya does not guarantee that these links will work all the time and has no control over the availability of the linked pages. Warranty Avaya provides a limited warranty on this product. Refer to your sales agreement to establish the terms of the limited warranty. In addition, Avaya s standard warranty language, as well as information regarding support for this product, while under warranty, is available to Avaya customers and other parties through the Avaya Support Web site: Please note that if you acquired the product from an authorized Avaya reseller outside of the United States and Canada, the warranty is provided to you by said Avaya reseller and not by Avaya. Licenses THE SOFTWARE LICENSE TERMS AVAILABLE ON THE AVAYA WEBSITE, ARE APPLICABLE TO ANYONE WHO DOWNLOADS, USES AND/OR INSTALLS AVAYA SOFTWARE, PURCHASED FROM AVAYA INC., ANY AVAYA AFFILIATE, OR AN AUTHORIZED AVAYA RESELLER (AS APPLICABLE) UNDER A COMMERCIAL AGREEMENT WITH AVAYA OR AN AUTHORIZED AVAYA RESELLER. UNLESS OTHERWISE AGREED TO BY AVAYA IN WRITING, AVAYA DOES NOT EXTEND THIS LICENSE IF THE SOFTWARE WAS OBTAINED FROM ANYONE OTHER THAN AVAYA, AN AVAYA AFFILIATE OR AN AVAYA AUTHORIZED RESELLER, AND AVAYA RESERVES THE RIGHT TO TAKE LEGAL ACTION AGAINST YOU AND ANYONE ELSE USING OR SELLING THE SOFTWARE WITHOUT A LICENSE. BY INSTALLING, DOWNLOADING OR USING THE SOFTWARE, OR AUTHORIZING OTHERS TO DO SO, YOU, ON BEHALF OF YOURSELF AND THE ENTITY FOR WHOM YOU ARE INSTALLING, DOWNLOADING OR USING THE SOFTWARE (HEREINAFTER REFERRED TO INTERCHANGEABLY AS YOU AND END USER ), AGREE TO THESE TERMS AND CONDITIONS AND CREATE A BINDING CONTRACT BETWEEN YOU AND AVAYA INC. OR THE APPLICABLE AVAYA AFFILIATE ( AVAYA ). protected by copyright and other intellectual property laws including the sui generis rights relating to the protection of databases. You may not modify, copy, reproduce, republish, upload, post, transmit or distribute in any way any content, in whole or in part, including any code and software. Unauthorized reproduction, transmission, dissemination, storage, and or use without the express written consent of Avaya can be a criminal, as well as a civil, offense under the applicable law. Third-party components Certain software programs or portions thereof included in the Product may contain software distributed under third party agreements ( Third Party Components ), which may contain terms that expand or limit rights to use certain portions of the Product ( Third Party Terms ). Information regarding distributed Linux OS source code (for those Products that have distributed the Linux OS source code), and identifying the copyright holders of the Third Party Components and the Third Party Terms that apply to them is available on the Avaya Support Web site: Trademarks The trademarks, logos and service marks ( Marks ) displayed in this site, the documentation(s) and product(s) provided by Avaya are the registered or unregistered Marks of Avaya, its affiliates, or other third parties. Users are not permitted to use such Marks without prior written consent from Avaya or such third party which may own the Mark. Nothing contained in this site, the documentation(s) and product(s) should be construed as granting, by implication, estoppel, or otherwise, any license or right in and to the Marks without the express written permission of Avaya or the applicable third party. Avaya is a registered trademark of Avaya Inc. All other trademarks are the property of their respective owners. Downloading documents For the most current versions of documentation, see the Avaya Support Web site: Contact Avaya Support Avaya provides a telephone number for you to use to report problems or to ask questions about your product. The support telephone number is in the United States. For additional support telephone numbers, see the Avaya Web site: support Copyright Except where expressly stated otherwise, no use should be made of materials on this site, the Documentation(s) and Product(s) provided by Avaya. All content on this site, the documentation(s) and the product(s) provided by Avaya including the selection, arrangement and design of the content is owned either by Avaya or its licensors and is 2 Configuration Ethernet August 2010

3 Contents Chapter 1: New in this release...9 Chapter 2: Introduction...11 Navigation...11 Chapter 3: Layer 2 fundamentals...13 Navigation...13 Ethernet interface fundamentals...13 Layer 2 switching and bridging...14 MAC bridging...14 VLANs...14 Independent VLAN learning...16 VLAN classification...16 VLAN stacking...17 Spanning Tree Protocol...18 Multiple Spanning Tree Protocol...18 MSTP regions...18 Common Spanning Tree...20 MSTP instance...20 Rapid transitions...21 Port mirroring...23 Selectable range of ports...23 Chapter 4: Configuring Advanced Gateway 2330 Ethernet interfaces...25 Configuring Maximum Transmission Unit size...25 Configuring jumbo frames...26 Adding comments to an interface...26 Adding comments at the beginning of a configuration file...26 Adding comments at the end of a configuration file...27 Adding a description to an interface...28 Configuring the speed of an interface...28 Configuring the traffic class table...29 Configuring user priority...30 Chapter 5: Layer 2 configuration...31 Prerequisites to Layer 2 configuration...31 Layer 2 configuration procedures...31 Layer 2 configuration navigation...32 Chapter 6: Configuring interface modes...35 Configuring trunking on Ethernet interfaces...35 Enabling trunking on an Ethernet port...35 Specifying VLANs to trunk...35 Disabling trunking...37 Verifying trunks...37 Example of configuring trunking on a chassis Ethernet interface...38 Configuring a hybrid link on an Ethernet interface...38 Associating VLANs with hybrid links...39 Disabling a hybrid link...41 Configuration Ethernet August

4 Verifying a hybrid link...41 Example of configuring a hybrid link on a chassis Ethernet interface...41 Configuring an access port on an Ethernet interface...42 Enabling an access link on an Ethernet port...42 Associating VLANs with access links...42 Disabling an access port...43 Verifying an access port...43 Chapter 7: Configuring VLANs...45 Creating a VLAN...45 Removing a VLAN...45 Verifying VLANs...46 Shutting down a VLAN interface...46 Example of creating VLANs and binding each VLAN to an interface...46 Example of creating VLANs...47 Example of binding an access interface to a VLAN...47 Example of binding a trunk port to multiple VLANs...48 Example of binding an Ethernet hybrid port to VLANs...48 Chapter 8: Configuring VLAN classification...49 Creating VLAN classification rules...49 Configuring an IPv4 subnet-based VLAN classification rule...49 Configuring a protocol-based VLAN classification rule...50 Deleting VLAN classification rules...51 Verifying VLAN classification rules...51 Creating VLAN classification rules on an interface...51 Creating protocol VLAN classification rules...52 Creating IPv4 VLAN classification rules...52 Deleting VLAN classification rules from an interface...52 Deleting protocol rules from an interface...52 Deleting IPv4 rules from an interface...53 Example of configuring VLAN classification rules...53 Chapter 9: Configuring VLAN stacking...55 Enabling VLAN stacking...55 Disabling VLAN stacking...55 Verifying VLAN stacking configuration...56 Chapter 10: Configuring port mirroring...57 Enabling port mirroring...57 Disabling port mirroring...58 Verifying port mirroring configuration...58 Example of configuring port mirroring...58 Chapter 11: Configuring MAC entries...59 Adding static MAC address entries to the MAC address table...59 Deleting a static MAC address entry...59 Verifying static MAC address entries...60 Example of configuring static MAC address entries...60 Configuring MAC address aging time...60 Restoring the default MAC address aging time...61 Verifying the MAC address aging time Configuration Ethernet August 2010

5 Example of configuring MAC address aging time...62 Chapter 12: Configuring Multiple Spanning Tree Protocol...63 Configuring the region name and revision number...63 Resetting the revision number...63 Configuring Common Spanning Tree...64 Configuring bridge priority...64 Configuring hop count...65 Configuring link path cost and priority...67 Configuring PortFast...70 Configuring PortFast BPDU Guard...72 Configuring PortFast BPDU Filter...73 Configuring MSTP timers...74 Configuring forward delay...76 Configuring maximum age time...78 Configuring link types...79 Configuring an MSTP instance...81 Creating an MSTP instance...81 Associating a VLAN with an instance...82 Configuring priority for an instance...83 Configuring link path cost and priority for an instance...85 Configuring the Spanning Tree version on a port...88 Restoring the default Spanning Tree version...88 Verifying MSTP operation...89 Viewing information for MSTP Common Spanning Tree...89 Viewing information for MSTP instances...89 Viewing bridge information for an instance...90 Viewing interface information...90 Viewing VLAN information for all instances...90 Viewing VLAN information for a specified instance...91 Chapter 13: IP routing concepts...93 IP addressing...93 Subnet addressing...94 Static routes...95 Black hole static routes...96 Equal Cost Multipath (ECMP)...96 Loopback IP...96 Routing over VLAN interfaces...97 Chapter 14: Configuring IP routing...99 IP routing commands...99 Configuring load balancing for equal cost routes...99 Configuring a static route...99 Configuring an access list Show commands Displaying IP access lists Displaying interface information Displaying the IP routing table Configuring routing for interfaces Configuring the IP address and mask for an interface Enabling proxy arp Configuration Ethernet August

6 Configuring ICMP redirect messages on an interface Configuring ICMP destination unreachable messages on an interface Chapter 15: IPv6 routing fundamentals IPv6 routing fundamentals navigation The IPv6 header IPv6 addresses Anycast Address Multicast Address IPv4-Compatible Address Address formats IPv6 extension headers Comparison of IPv4 and IPv ICMPv Neighbor discovery ND messages ND cache Router discovery Multicast IPv6 and the Avaya Advanced Gateway Management access Path MTU discovery Routing Static routes IPv6 Routing over VLAN Chapter 16: IPv6 routing procedures Enabling unicast routing globally Enabling IPv6 on an Ethernet interface Configuring the IPv6 address for an interface Configuring Neighbor Discovery parameters Configuring IPv6 redirects Configuring an IPv6 general-prefix Configuring the IPv6 hop-limit Configuring IPv6 icmp rate limit Configuring IPv6 load balancing Configuring an IPv6 neighbor Configuring IPv6 next-hop address Establishing static routes Creating an access list entry Creating a prefix list Displaying IPv6 access lists Displaying general prefix information Displaying IPv6 interface information Displaying learned pmtu information Displaying Neighbor Discovery cache information Displaying IPv6 prefix list information Displaying the IPv6 routing table Displaying IPv6 Router Advertisement information Removing dynamically learned neighbor entries Clearing a prefix list Configuration Ethernet August 2010

7 Index Configuration Ethernet August

8 8 Configuration Ethernet August 2010

9 Chapter 1: New in this release Avaya Advanced Gateway 2330 Configuration Ethernet (NN ) is a new document for Release of the Avaya Advanced Gateway 2330 (AG2330). Configuration Ethernet August

10 New in this release 10 Configuration Ethernet August 2010

11 Chapter 2: Introduction This document provides information you need to configure Ethernet interfaces, Layer 2 features, IPv4 routing, and IPv6 routing. Navigation Layer 2 fundamentals on page 13 Configuring Advanced Gateway 2330 Ethernet interfaces on page 25 Layer 2 configuration on page 31 Configuring interface modes on page 35 Configuring VLANs on page 45 Configuring VLAN classification on page 49 Configuring VLAN stacking on page 55 Configuring port mirroring on page 57 Configuring MAC entries on page 59 Configuring Multiple Spanning Tree Protocol on page 63 Configuration Ethernet August

12 Introduction 12 Configuration Ethernet August 2010

13 Chapter 3: Layer 2 fundamentals Ethernet is one of the most widely deployed Layer 2 Local Area Network (LAN) transport technologies today. A LAN is a data communications network connecting terminals, computers, and printers within a building or other geographically limited area. Advantages of Ethernet include: Ability to scale in bandwidth and speed Ethernet switches support high port densities and forwarding rates in the millions of packets per second Support of Class of Service (CoS) that allows up to eight classes of service to be defined Ease of deploying multipoint communications The Avaya Advanced Gateway 2330 (AG2330) Ethernet Layer 2 features support VLAN MAC bridging of traffic within the LAN. The AG2330 platform uses both the hardware network processor and software forwarding logic for Ethernet Layer 2 switching. The network processor handles LAN switching. Software forwarding works with the network processor to achieve VLAN data switching. The AG2330 also supports termination of Layer 3 traffic on a VLAN to achieve routing using the Layer 3 engine. Navigation Ethernet interface fundamentals on page 13 Layer 2 switching and bridging on page 14 MAC bridging on page 14 VLANs on page 14 Spanning Tree Protocol on page 18 Port mirroring on page 23 Ethernet interface fundamentals The Avaya Advanced Gateway 2330 (AG2330) supports the following Ethernet interfaces: FE 0/1 through FE 0/4 10/100 Base-T ports GE 0/5 and GE 0/6 10/100/1000 BaseT ports GE 0/7 and GE0/8 SFP ports, for plug-in SFP modules All Ethernet ports on the AG2330 support MDI and MDI-X. Configuration Ethernet August

14 Layer 2 fundamentals By default, Ethernet interfaces on the AG2330 are routed interfaces. To configure them as Layer 2 interfaces, use the switchport command. Layer 2 switching and bridging Local Area Network (LAN) is a data communications network connecting terminals, computers and printers within a building or other geographically limited areas. These devices could be connected through wired cables or wireless links. Ethernet and Token Ring are examples of standard LAN technologies. LAN switching involves examining physical network addresses that uniquely identify a device in the network. LAN bridging offers an extension of the LAN by supporting the connection of multiple LAN segments. MAC addresses of the datagram that flow through bridges are examined to build a table of known destinations. If the destination of a datagram is on the same segment as the source of the datagram, the bridge drops the datagram because forwarding is not required. However, if the destination is on another segment, the bridge transmits the datagram on that segment only. If the bridge does not know the destination segment, it transmits the datagram on all segments except the source segment (a technique known as flooding). MAC bridging MAC Bridging allows multiple LANs to be connected together. Transparent bridging involves the creation of MAC address tables, and limits the Ethernet collision domain by filtering data sent between LAN segments. This reduces network congestion and allows networks to be partitioned for administrative purposes. VLANs A Virtual LAN (VLAN) is a switched network that is logically segmented on an organizational basis, by functions, project teams, or applications rather than on a physical or geographical basis. VLAN segments the physical local-area network (LAN) infrastructure into different subnets so that packets are switched only between ports within the same VLAN. Devices on a VLAN are configured so that they can communicate as if they were attached to the same physical wire, when in fact they are located on a number of different LAN segments. With VLAN partitioning, traffic stays within the appropriate groups, minimizing wasteful broadcasts. A VLAN is made up of a group of ports that define a logical broadcast domain. These ports can belong to a single device, or they can be spread across multiple devices. In a VLANaware device, every frame received on a port is classified as belonging to one and only one VLAN. Whenever a broadcast, multicast, or unknown destination frame must be flooded by a 14 Configuration Ethernet August 2010

15 VLANs VLAN-aware device, the frame is sent out only through all the other active ports that are members of this VLAN. The default device configuration groups all ports into the port-based default VLAN 1. This VLAN cannot be deleted from the system. The AG2330 supports port-based and protocol-based VLANs. A port-based VLAN is a VLAN whose ports are explicitly configured as members. In portbased VLANs, all ports are always static members. When creating a port-based VLAN, you assign a VLAN identification number (VID) and specify which ports belong to the VLAN. The VID is used to coordinate VLANs across multiple devices. Protocol-based VLANs are an effective way to segment your network into broadcast domains according to the network protocols in use. Traffic generated by any network protocol can be automatically confined to its own VLAN. VLAN tagging is a MAC option. A VLAN-tagged frame is a basic MAC data frame that has had a 4-byte VLAN header inserted between the SA and Length/Type fields. The VLAN header consists of the following fields: A reserved 2-byte type value, indicating that the frame is a VLAN frame Tag Protocol Identifier (TPID) - defined value of 8100 in hex. When a frame has the EtherType equal to 8100, this frame carries the tag IEEE 802.1Q/802.1P. TCI - Tag Control Information field including user priority, Canonical format indicator and VLAN ID. VLAN tagging can be enabled or disabled on each interface. The AG2330 uses IEEE 802.1Q tagging of frames and coordinates VLANs across multiple devices. The following figure shows the additional 4-octet (tag) header that is inserted into a frame after the source address and before the frame type. The tag contains the VLAN ID associated with the frame. Figure 1: VLAN tagging In the AG2330, your port level configuration determines whether tagged frames are sent and received. Tagging is set as true or false for the port and is applied to all VLANs on that port. The AG2330 associates a frame with a VLAN based on the data content of the frame and the configuration of the destination port. Whether the frame is tagged or untagged dictates how that frame is treated. A AG2330 port with tagging enabled sends frames explicitly tagged with a VLAN ID. Tagged ports are typically used to multiplex traffic belonging to multiple VLANs to other IEEE-802.1Qcompliant devices. If tagging is disabled on a AG2330 port, it does not send tagged frames. An untagged port connects a AG2330 to devices that do not support IEEE 802.1Q tagging. Configuration Ethernet August

16 Layer 2 fundamentals If a tagged frame is forwarded out a port on which tagging is set to false, the device removes the tag from the frame before sending it out the port. If a tagged frame is received on a tagged port, with a VLAN ID specified in the tag, the AG2330 directs it to that VLAN, if it is present. For untagged frames, VLAN membership is implied from the content of the frame itself. For untagged frames received on a tagged port, you can configure the port to either discard or accept the frame. If you configure a tagged port to accept untagged frames, the port must be assigned to a port-based VLAN. Independent VLAN learning In the AG2330, each VLAN has its own, independent, forwarding database. That is, the same MAC address can be learned in different VLANs; and, based on the VLAN receiving traffic for this address, the device is able to forward to this MAC address without any confusion. This means that before the device can look up the source or destination MAC address in a received frame, or before it can decide whether to bridge or to route a frame, it must first determine to which VLAN the frame belongs. Independent VLAN learning mode is used to learn MAC addresses in the context of the VLAN to which they belong. VLAN classification Each frame received by a VLAN bridge is classified as belonging to exactly one VLAN by associating a VID value with the received frame. The classification is achieved as follows: 1. If the vlan_identifier parameter carried in a received data indication is the null VLAN ID (VID), and no VLAN classification rules are configured, then the VID for the frame is the unique Port VLAN ID (PVID) associated with the port through which the frame was received. Otherwise: 2. If the vlan_identifier parameter carried in a received data indication is the null VLAN ID and there are VLAN classification rules configured, then the VID for the frame is selected from the VID set of the port through which the frame was received. The VID selected is the member of the VID set for which the associated Protocol Group Identifier (PGI) is equal to the PGI of the frame. If no matches are found, then the VID for the frame is the PVID associated with the port. Otherwise: 3. The VID for the frame is the vlan_identifier parameter value. Important: The vlan_identifier parameter carries the null VLAN ID if the frame was not VLAN tagged. There are two cases: either the frame was untagged, or the frame was tagged and the tag header carried a VID value equal to the null VLAN ID (that is, a priority-tagged frame). 16 Configuration Ethernet August 2010

17 VLANs Supported protocols for protocol-based VLAN classification rules The following table lists the protocols that the AG2330 supports for VLAN classification rules. Table 1: Supported protocols for VLAN classification rules Classification rule parameter ipv4 ipv6 mpls arp rarp vlan-tagged appletalk ipx pppoe-disc pppoe-session Description IPv4 IPv6 MPLS ARP Reverse ARP 802.1q VLAN tag Appletalk IPX PPPoE discovery PPPoE session The supported encapsulations for protocol-based VLAN classification rules are: Ethernet Type II LLC SNAP LLC only VLAN stacking VLAN stacking refers to the encapsulation of one VLAN within another VLAN. A stacked VLAN transparently tunnels packets through the stacked VLAN domain by adding an additional 4- byte header to each packet. Stacked VLANs offer the following features: VLAN transparency for IEEE 802.1Q tagged or untagged traffic through a service provider core network A solution to VLAN scalability issues you can summarize customer VLANs into core stacked VLANs Uses a layered architecture to improve scalability Configuration Ethernet August

18 Layer 2 fundamentals Spanning Tree Protocol The operation of the Spanning Tree Protocol (STP) is defined in the IEEE Standard 802.1D. The STP detects and eliminates logical loops in a bridged or switched network. When multiple paths exist, the spanning tree algorithm configures the network so that a bridge or switch uses only the most efficient path. If that path fails, the protocol automatically reconfigures the network to make another path active. The process maintains network operations. You can control path redundancy for VLANs by implementing STP. Multiple Spanning Tree Protocol The AG2330 supports Multiple Spanning Tree Protocol (MSTP), and it is enabled by default. MSTP on the AG2330 is backward-compatible with STP and Rapid Spanning Tree Protocol (RSTP). STP and RSTP can be implemented on a per-port basis on the AG2330. MSTP defines an extension to RSTP that further develops the usefulness of VLANs. This "per- VLAN" MSTP configures a separate Spanning Tree for each VLAN group and blocks the links that are redundant within each Spanning Tree. If there is only one VLAN in the network, single (traditional) STP works appropriately. If the network contains more than one VLAN, the logical network configured by single STP would work, but it is possible to make better use of the redundant links available by using an alternate spanning tree for different (groups of) VLANs. MSTP allows the formation of MST regions that can run multiple MST instances (MSTI). Multiple regions and other STP bridges are interconnected using one single common spanning tree (CST). MSTP on the AG2330 interoperates with Cisco s implementation of MSTP. The Cisco equipment must have IOS v12.2 (25), or newer, installed. MSTP regions All devices are said to be in the same region if the following three elements are the same on all the devices: region name (32 bytes) revision number (2 bytes) configuration digest (the numerical value derived from VLAN to instance mapping) The following figure shows a single MSTP region. 18 Configuration Ethernet August 2010

19 Spanning Tree Protocol Figure 2: Single MSTP region Within a region, there can be multiple spanning trees running for an instance. All the bridges within a region appear as a single bridge to other regions. Bridges that are outside the region always have a single point of contact to the region. The following figure shows the relationship amongst multiple MSTP regions. Figure 3: Multiple MSTP regions Configuration Ethernet August

20 Layer 2 fundamentals Common Spanning Tree With Common Spanning Tree (CST) there is only one instance of spanning tree for all VLANs. As shown in the following figure, the traffic for all VLANs (2 100) must travel from Switch B to Switch A, while the path between Switch C and Switch A is unused. Figure 4: Common Spanning Tree MSTP instance With MSTP instances, traffic can be load-balanced between all the links. Within a region, each instance has its own independent spanning tree. It can have its own root bridge. Each bridge can have a different priority for each instance, so that the bridge can be selected as root in one instance and non-root in another instance. In the following figure, Switch B is root in Instance #1. Switch C is the root bridge in Instance #2. In CST, Switch A is the root. 20 Configuration Ethernet August 2010

21 Spanning Tree Protocol Figure 5: Network with multiple instances configured VLANs can be assigned arbitrarily to any instance. Any VLAN can be part of one and only one instance. The VLAN traffic inside the MSTP region takes the path determined by the Spanning Tree associated with that particular instance. For example, if VLANs 2 50 are associated with Instance #1 and VLANs are associated with Instance #2, the VLAN traffic (VLAN ID 2 50) never takes the link AC path until and unless the link AB or BC fails. Similarly, the VLAN traffic (VLAN ID ) never takes the link AB path until and unless link CB or CA fails. Rapid transitions On a port connected to no other bridge, Spanning Tree PortFast brings the port up more quickly following device initialization or a spanning tree change. For example, in the following figure, ports A1, B1, B2 are connected to end stations. These ports do not participate in the Spanning Tree port selection. These ports can, therefore, go directly to the spanning tree forwarding state (skipping the listening and learning states). Configuration Ethernet August

22 Layer 2 fundamentals Figure 6: Enabling rapid transitions in a network Important: Enabling PortFast does not disable spanning tree on an interface. See PortFast BPDU Filter on page 23 for more information. PortFast is intended for access ports where only one device is connected to the gateway or switch (as in workstations with no other spanning tree devices). If you configure PortFast on a port that is connected to another bridge, there is the possibility of forming a loop. This can be prevented with the help of the Bridge Protocol Data Unit (BPDU) Guard feature. PortFast BPDU Guard The PortFast BPDU Guard feature prevents loops by moving a port into an "error disable" state when that port receives a BPDU. When you enable the BPDU guard feature on the port, Spanning Tree shuts down PortFast-configured interfaces that receive BPDUs, rather than putting them into the Spanning Tree blocking state. In a valid configuration, PortFast-configured interfaces do not receive BPDUs. If a PortFastconfigured interface receives a BPDU, an invalid configuration exists, such as the connection of an unauthorized device. 22 Configuration Ethernet August 2010

23 Port mirroring PortFast BPDU Filter By default, MSTP sends BPDU packets on all ports regardless of whether or not you have enabled PortFast. Enabling PortFast BPDU filter on a port results in the following: stops sending BPDU packets stops processing of incoming BPDU packets sets the port to forwarding always The purpose of the PortFast BPDU Filter command is to filter all incoming BPDUs on an interface, which effectively disables spanning tree on an interface. You can apply the feature on ports that connect to an end station or to routers. Although spanning tree is disabled, all Layer 2 forwarding rules remain the same (in terms of packet flooding within a VLAN domain, or in terms of supporting VLAN termination) to allow routing of Layer 2 packets. Port mirroring The AG2330 has a port mirroring feature that helps you to monitor and analyze network traffic. The monitoring (destination) port can be connected to a network analyzer or RMON probe for packet analysis. Unlike other methods that are used to analyze packet traffic, the packet traffic is uninterrupted and packets flow normally through the mirrored port. The port mirroring feature supports both ingress (incoming traffic) and egress (outgoing traffic) port mirroring. When port mirroring is enabled, the ingress or egress packets of the mirrored (source) port are forwarded normally and a copy of the packets is sent out of the mirrored port to the mirroring (destination) port. To avoid seeing unintended traffic, remove mirroring (destination) ports from all virtual local area networks (VLAN) and multiple spanning tree instances (MSTIs). When mirroring ports where VLAN tagging is enabled, the VLAN tags are not included in the packets received at the mirroring (destination) port. The port mirroring feature is supported only on the module Ethernet ports. You can configure a maximum of one analyzer (destination) port for each module. Selectable range of ports With Release 10.2 and later, you can specify a range of Ethernet ports to configure at the same time. To do so, you must use the interface range ethernet command. Configuration Ethernet August

24 Layer 2 fundamentals 24 Configuration Ethernet August 2010

25 Chapter 4: Configuring Advanced Gateway 2330 Ethernet interfaces Use the procedures in this section for your basic Ethernet interface configuration. Configuring Maximum Transmission Unit size Use the procedure in this section to configure the MTU size for an Ethernet interface. Important: The Advanced Gateway 2330 (AG2330) management Ethernet interface (FE 0/0) on the rear panel does not support jumbo frames. Therefore, the management port Maximum Transmission Unit (MTU) can be configured with a value in the range of 64 to 1500 bytes. Important: The AG2330 management Ethernet interface (FE 0/0) is automatically disabled when you install a Digital Signal Processor (DSP). 2. To select an interface, enter: interface ethernet <slot/port> 3. To configure the MTU size, enter: mtu <size> Table 2: definitions <size> Specifies the MTU size. Valid values are 64 to The default value is <slot/port> Specifies the slot and port numbers that identify the port for configuration. For example, 6/1. Configuration Ethernet August

26 Configuring Advanced Gateway 2330 Ethernet interfaces Configuring jumbo frames The AG2330 supports jumbo frames. Important: The AG2330 management Ethernet interface (FE 0/0) on the rear panel does not support jumbo frames. Therefore, the management port Maximum Transmission Unit (MTU) can be configured with a value in the range of 64 to 1500 bytes. Use the procedure in this section to configure the AG2330 system settings to support jumbo frames. 2. To configure the system settings to support jumbo frames, enter: system jumbo-mtu-limit <value> 3. Reboot the system. Table 3: definitions <value> Valid values for the jumbo MTU limit are 1500 and 9216 bytes. The default value is 1500 bytes. Adding comments to an interface Use the procedures in this section to add comments to an interface. Adding comments at the beginning of a configuration file Use the procedure in this section to add comments at the beginning of the Ethernet area of a configuration file. 26 Configuration Ethernet August 2010

27 Adding comments to an interface 2. To select an interface, enter: interface ethernet <slot/port> 3. To enter a comment: REM <string> Table 4: definitions <string> <slot/port> Specifies the comments. The string length for comments is 80 characters. You must enclose comments in quotation marks. For example, REM "Configured on July 30". Specifies the slot and port numbers that identify the port for configuration. For example, 6/1. Adding comments at the end of a configuration file Use the procedures in this section to add comments to an interface. The comments appear at the end of the Ethernet area of a configuration file. 2. To select an interface, enter: interface ethernet <slot/port> 3. To enter a comment: REM_ <string> Table 5: definitions <string> Specifies the comments. The string length for comments is 80 characters. You must enclose comments in quotation marks. For example, REM_ "Configured on July 30". Configuration Ethernet August

28 Configuring Advanced Gateway 2330 Ethernet interfaces <slot/port> Specifies the slot and port numbers that identify the port for configuration. For example, 6/1. Adding a description to an interface Use the procedure in this section to configure a description for an Ethernet interface. The description string can be up to 76 characters. 2. To select an interface, enter: interface ethernet <slot/port> 3. To configure a description, enter: description <string> Table 6: definitions <string> <slot/port> Specifies the description. The string length for a description is 76 characters. You must enclose the description in quotation marks. For example, description "Main LAN". Specifies the slot and port numbers that identify the port for configuration. For example, 6/1. Configuring the speed of an interface Use the procedure in this section to configure the speed of an Ethernet interface. 28 Configuration Ethernet August 2010

29 Configuring the traffic class table 2. To select an interface, enter: interface ethernet <slot/port> 3. To configure the speed, enter: speed { auto} mode {half_duplex full_duplex} Table 7: definitions { auto} Specifies the speed of the port. The default value is auto. {half_duplex full_duplex} <slot/port> Specifies the operating mode for the port. The default value is half_duplex. Specifies the slot and port numbers that identify the port for configuration. For example, 6/1. Configuring the traffic class table Use the procedure in this section to set the traffic class tables values, specifically, the user priority and number of supported traffic classes. 2. To select an interface, enter: interface ethernet <slot/port> 3. To configure the traffic class table, enter: traffic-class-table user-priority <user priority> numtraffic-classes <traffic classes> value <value> Table 8: definitions <slot/port> <traffic classes> Specifies the slot and port numbers that identify the port for configuration. For example, 0/0. Specifies the number of traffic classes supported. Valid values are 1 to 8. Configuration Ethernet August

30 Configuring Advanced Gateway 2330 Ethernet interfaces <user priority> <value> Specifies the user priority value. Valid values are 0 to 7. Specifies the value to be used for the given user priority and number of traffic classes. Configuring user priority Use the procedure in this section to configure the default user priority associated with a Layer 2 interface. 2. To select an interface, enter: interface ethernet <slot/port> 3. To set the user priority, enter: user-priority <value> Table 9: definitions <slot/port> <value> Specifies the slot and port numbers that identify the port for configuration. For example, 0/0. Specifies the user priority value for the interface. Valid values are 0 to Configuration Ethernet August 2010

31 Chapter 5: Layer 2 configuration You configure Layer 2 (data link layer) features to allow traffic to pass between between devices on the same LAN segment. On the Avaya Advanced Gateway 2330 (AG2330), you can specify a range of Ethernet ports to configure at the same time. To do so, you must use the interface range ethernet command. Prerequisites to Layer 2 configuration The Avaya Advanced Gateway 2330 (AG2330) must be securely installed in an equipment rack, and properly grounded. You must have commissioned your AG2330 so it is ready for software feature configuration. Layer 2 configuration procedures This task flow shows you the sequence of procedures you perform to configure Layer 2 features on the AG2330. To link to any procedure, go to Layer 2 configuration navigation on page 32. Configuration Ethernet August

32 Layer 2 configuration Figure 7: Layer 2 configuration procedures Layer 2 configuration navigation Configuring interface modes on page 35 Configuring VLANs on page Configuration Ethernet August 2010

33 Layer 2 configuration navigation Configuring VLAN classification on page 49 Configuring VLAN stacking on page 55 Configuring port mirroring on page 57 Configuring MAC entries on page 59 Configuring Multiple Spanning Tree Protocol on page 63 Configuration Ethernet August

34 Layer 2 configuration 34 Configuration Ethernet August 2010

35 Chapter 6: Configuring interface modes You can configure a port on a Avaya Advanced Gateway 2330 (AG2330) as an access port, a trunk port, or a hybrid port. You can enable Layer 2 switching on all Ethernet interfaces. This section describes the supported interface modes and how to configure each mode on LAN interfaces. Configuring trunking on Ethernet interfaces Trunk links are required to pass VLAN information between devices. You can configure a trunk port to be a member of all the VLANs that exist on the device. That port then carries traffic for all the VLANs between the devices. To distinguish between the traffic flows, a trunk port must mark the frames with special tags as they pass between the devices. You must enable trunking on both sides of a link. If two devices are connected together, for example, you must configure both device ports for trunking. Enabling trunking on an Ethernet port Use the procedure in this section to enable trunking between the devices. 2. To select an Ethernet interface, enter: interface [range] ethernet <slot/port> 3. To configure the interface as a trunk port, enter: switchportswitchport mode trunk Specifying VLANs to trunk You can configure a trunk link to carry all the VLANs that exist on the device. You can also selectively add VLANs to and remove VLANs from a trunk link. Use the procedures in this section to specify the VLANs to add or remove from a trunk link. Configuration Ethernet August

36 Configuring interface modes Adding all VLANs to a trunk link Use the procedure in this section to add all VLANs to a trunk link. 2. To select an interface, enter: interface [range] ethernet <slot/port> 3. To add all VLANs to the selected trunk link, enter: switchport trunk allowed vlan all Removing all VLANs from a trunk link Use the procedure in this section to remove all VLANs from a trunk link. 2. To select an interface, enter: interface [range] ethernet <slot/port> 3. To remove all VLANs from the selected trunk link, enter: switchport trunk remove vlan all Adding a specified VLAN to a trunk link Use the procedure in this section to selectively add VLANs to a trunk link. 2. To select an interface, enter: interface [range] ethernet <slot/port> 3. To add a specific VLAN to the selected trunk link, enter: switchport trunk allowed vlan <vid> 36 Configuration Ethernet August 2010

37 Configuring trunking on Ethernet interfaces Removing a specified VLAN from a trunk link Use the procedure in this section to selectively remove VLANs from a trunk link. 2. To select an interface, enter: interface [range] ethernet <slot/port> 3. To remove a specific VLAN from the selected trunk link, enter: switchport trunk remove vlan <vid> Disabling trunking Use the procedure in this section to disable trunking on an interface. 2. To select an interface, enter: interface [range] ethernet <slot/port> 3. To disable trunking on the interface, enter: no switchport Verifying trunks Use the procedure in this section to verify the successful configuration of trunks. The show interface ethernet command displays the highest supported capability for each interface: FE for Fast Ethernet and GE for Gigabit Ethernet. 1. To view information related to the interface mode, enter: show bridge port 2. To view information related to the operation of the trunk port, enter: show interface ethernet <slot/port> Configuration Ethernet August

38 Configuring interface modes Example of configuring trunking on a chassis Ethernet interface 2. To select the chassis Ethernet interface (in this example, interface 0/1), enter: interface ethernet 0/1 3. To configure the interface as a Layer 2 interface, enter: switchport 4. To configure the interface as a trunk, enter: switchport mode trunk Configuring a hybrid link on an Ethernet interface A hybrid link is a LAN segment that contains both VLAN-aware and VLAN-unaware devices. Consequently, a hybrid link can carry both VLAN tagged frames and other (untagged or prioritytagged) frames. Use the procedure in this section to enable a hybrid link between devices. 2. To select an Ethernet interface, enter: interface [range] ethernet <slot/port> 3. To configure the interface as a Layer 2 interface, enter: switchport 4. To configure the interface as a hybrid port, enter: switchport mode hybrid 38 Configuration Ethernet August 2010

39 Configuring a hybrid link on an Ethernet interface Associating VLANs with hybrid links When configuring hybrid links, ensure that all frames transmitted by a bridge on a hybrid link are tagged in the same way on that link. The frames must be either all tagged, or all tagged and carrying the same VLAN ID. A bridge can transmit a mix of VLAN-tagged frames and untagged frames, but the frames must be for different VLANs. In the following figure, all the frames for VLAN A and VLAN B are tagged on the hybrid link. All frames for VLAN C on the hybrid link are untagged. Figure 8: Hybrid link network scenario Adding all VLANs to a hybrid link Use the procedure in this section to add all VLANs to a hybrid link. 2. To select an interface, enter: interface [range] ethernet <slot/port> 3. To add all VLANs to the selected hybrid link, enter: Configuration Ethernet August

40 Configuring interface modes switchport hybrid allowed vlan all egress {tagged untagged} Removing all VLANs from a hybrid link Use the procedure in this section to remove all VLANs from a hybrid link. 2. To select an interface, enter: interface [range] ethernet <slot/port> 3. To remove all VLANs from the selected hybrid link, enter: switchport hybrid remove vlan all egress {tagged untagged} Adding a specified VLAN to a hybrid link Use the procedure in this section to selectively add VLANs to a hybrid link. 2. To select an interface, enter: interface [range] ethernet <slot/port> 3. To add a specific VLAN to the selected hybrid link, enter: switchport hybrid allowed vlan <vid> egress {tagged untagged} Removing a specified VLAN from a link Use the procedure in this section to selectively remove VLANs from a hybrid link. 2. To select an interface, enter: interface [range] ethernet <slot/port> 3. To remove a specific VLAN from the selected hybrid link, enter: 40 Configuration Ethernet August 2010

41 Configuring a hybrid link on an Ethernet interface switchport hybrid remove vlan <vid> egress {tagged untagged} Disabling a hybrid link Use the procedure in this section to disable a hybrid link. 2. To select an interface, enter: interface [range] ethernet <slot/port> 3. To disable the hybrid link on the interface, enter: no switchport Verifying a hybrid link Use the procedure in this section to verify the successful configuration of a hybrid link. The show interface ethernet command displays the highest supported capability for each interface: FE for Fast Ethernet and GE for Gigabit Ethernet. 1. To view information related to the interface mode, enter: show bridge port 2. To view information related to the operation of the hybrid interface, enter: show interface ethernet <slot/port> Example of configuring a hybrid link on a chassis Ethernet interface 2. To select an Ethernet interface (in this example, Ethernet interface 0/1), enter: interface ethernet 0/1 3. To configure the interface as a Layer 2 interface, enter: Configuration Ethernet August

42 Configuring interface modes switchport 4. To configure the interface as a hybrid link, enter: switchport mode hybrid Configuring an access port on an Ethernet interface Access ports belong to a single VLAN and do not provide any identifying marks on the frames that are passed between devices. Access ports carry traffic that comes only from the VLAN assigned to the port. For an example network scenario that shows the use of trunking, see Example of configuring VLAN stacking. Enabling an access link on an Ethernet port Use the procedure in this section to enable an access link between the devices. 2. To select an interface, enter: interface [range] ethernet <slot/port> 3. To configure the interface as an access port, enter: switchport Associating VLANs with access links There can be only one VLAN assigned to an access port. VLAN ID 1 is the default VLAN assigned to each port. Use the procedures in this section to specify the VLANs to add to or remove from an access link. Changing the VLAN on an access port Use the procedure in this section to change the VLAN assigned to an access link. 42 Configuration Ethernet August 2010

43 Configuring an access port on an Ethernet interface 2. To select an interface, enter: interface [range] ethernet <slot/port> 3. To assign a VLAN to the selected access port, enter: switchport pvid <vid> Disabling an access port Use the procedure in this section to disable an access port. 2. To select an interface, enter: interface [range] ethernet <slot/port> 3. To disable the selected access port, enter: no switchport Verifying an access port Use the procedure in this section to verify the successful configuration of an access port. The show interface ethernet command displays the highest supported capability for each interface: FE for Fast Ethernet and GE for Gigabit Ethernet. 1. To view information related to the interface mode, enter: show bridge port 2. To view information related to the operation of the access port, enter: show interface ethernet <slot/port> Configuration Ethernet August

44 Configuring interface modes 44 Configuration Ethernet August 2010

45 Chapter 7: Configuring VLANs Use the procedures in this section to create or remove VLANs from the system. Creating a VLAN Use the procedure in this section to create VLANs in the bridge global database. 2. To access the VLAN database, enter: vlan database 3. To create a VLAN, enter: vlan <vid> [name <WORD>] Table 10: definitions name <WORD> <vid> The name that you assign to the VLAN. This parameter is optional. The VLAN identification number that you assign. Valid values are 2 to Removing a VLAN Use the procedure in this section to remove a VLAN from the database. 2. To access the VLAN database, enter: Configuration Ethernet August

46 Configuring VLANs vlan database 3. To remove a VLAN, enter: no vlan <vid> [name <WORD>] Verifying VLANs After configuring a VLAN, use the procedure in this section to verify successful operation of a VLAN and to verify the interfaces to which the VLAN is assigned. To verify the successful configuration of a VLAN, enter: show bridge vlan Shutting down a VLAN interface Use the procedure in this section to shut down a VLAN interface. 2. To select a VLAN interface, enter: interface vlan vlan<id> 3. To shut down the interface, enter: shutdown Example of creating VLANs and binding each VLAN to an interface The example in this section shows how to create VLANs and bind different interface types to the VLANs. 46 Configuration Ethernet August 2010

47 Example of creating VLANs and binding each VLAN to an interface Example of creating VLANs In this example, you create VLANs 2 to To access the VLAN database, enter: vlan database 3. To create a VLAN with ID 2, enter: vlan 2 4. To create a VLAN with ID 3, enter: vlan 3 5. To create a VLAN with ID 4, enter: vlan 4 Example of binding an access interface to a VLAN 2. To select an Ethernet interface (in this example, FE 0/2), enter: interface ethernet 0/2 3. To configure the interface as an access port, enter: switchport 4. To bind the access interface to VLAN 2, enter: switchport pvid 2 This changes the default PVID from 1 to 2. Configuration Ethernet August

48 Configuring VLANs Example of binding a trunk port to multiple VLANs 2. To select an Ethernet port (in this case, GE port 0/5), enter: interface ethernet 0/5 3. To configure the interface as a trunk port, enter: switchport switchport mode trunk 4. To bind the trunk port to VLANs 2, 3, and 4, enter: switchport trunk allow vlan 2,3,4 Example of binding an Ethernet hybrid port to VLANs 2. To select the previously configured channel group number 1, enter: interface lag lag1 3. To configure the LAG interface as a hybrid link, enter: switchportswitchport mode hybrid 4. To bind the Ethernet hybrid port to VLANs 2, 3, and 4, enter: switch hybrid allow vlan all egress tagged 48 Configuration Ethernet August 2010

49 Chapter 8: Configuring VLAN classification Creating VLAN classification rules There are two types of VLAN classification rules that you can create: IPv4 subnet-based VLAN classification rule (if the source IP address matches the IP subnet specified in the VLAN classification rule, the received packets are mapped to the specified VLAN) protocol-based VLAN classification rule (If the protocol type matches the protocol specified in the VLAN classification rule, the received packets are mapped to the specified VLAN) Configuring an IPv4 subnet-based VLAN classification rule 2. Enter the configuration context: vlan classification 3. To create a subnet-based VLAN classification rule, enter: rule <id> ipv4 <ipaddr/netmask> vlan <vid> Table 11: definitions <id> <ipaddr/netmask> The VLAN classifier rule ID. Valid values are 1 to 12. IPv4 address. Specify an IP address and subnet. For example, /24. Configuration Ethernet August

50 Configuring VLAN classification Configuring a protocol-based VLAN classification rule 2. Enter the configuration context: vlan classification 3. To create a protocol-based VLAN classification rule, enter: rule <id> protocol <protocol> encap <encapsulation> Table 12: definitions <id> <protocol> <encapsulation> The VLAN classifier rule ID. Valid values are 1 to 12. The protocol parameter is either a number (from 0 to 65535), or one of the following: ipv4 ipv6 mpls arp rarp vlan-tagged appletalk ipx pppoe-disc pppoe-session The encapsulation type. Enter one of the following: ethv2 llcsnap llc 50 Configuration Ethernet August 2010

51 Deleting VLAN classification rules Deleting VLAN classification rules Use the procedure in this section to delete VLAN classification rules. 2. Enter the configuration context: vlan classification 3. To delete a subnet-based classification rule, enter: no rule <id> ipv4 <ipaddr/netmask> vlan <vid> 4. To delete a protocol-based classification rule, enter: no rule <id> protocol <protocol> encap <encapsulation> Verifying VLAN classification rules Use the procedure in this section to verify the successful operation of configured VLAN classification rules. To verify the successful operation of VLAN classification rules, enter: show running-config Creating VLAN classification rules on an interface Use the procedures in this section to create VLAN classification rules on an interface. Important: You can apply VLAN classification rules only on hybrid ports. Configuration Ethernet August

52 Configuring VLAN classification Creating protocol VLAN classification rules After you have defined protocol rules, you can apply those rules to an interface. 2. To select an interface, enter: interface ethernet <slot/port> 3. To apply a protocol-based classification rule to the selected interface, enter: vlan classification protocol rule <id> vlan <vid> Creating IPv4 VLAN classification rules In the case of an IPv4 subnet-based classification rule, the rule can be assigned to an interface prior to the creation of the rule definition. 2. To select an interface, enter: interface ethernet <slot/port> 3. To apply a subnet-based classification rule to the selected interface, enter: vlan classification ipv4 Deleting VLAN classification rules from an interface Use the procedures in this section to remove VLAN classification rules from an interface. Deleting protocol rules from an interface Use the procedure in this section to delete a protocol-based VLAN classification rule from an interface. 52 Configuration Ethernet August 2010

53 Example of configuring VLAN classification rules 2. To select an interface, enter: interface ethernet <slot/port> 3. To delete a protocol-based classification rule from the selected interface, enter: no vlan classification protocol rule <id> vlan <vid> Deleting IPv4 rules from an interface Use the procedure in this section to delete an IPv4-based VLAN classification rule from an interface. 2. To select an interface, enter: interface ethernet <slot/port> 3. To delete a subnet-based classification rule from the selected interface, enter: no vlan classification ipv4 Example of configuring VLAN classification rules In this example, you define both IPv4 VLAN classification rules and apply the rules to Ethernet interfaces. 2. Enter the configuration context: vlan classification 3. To define rule 1 (subnet-based rule), enter: rule 1 ipv /16 vlan 3 4. To define rule 2 (subnet-based rule), enter: Configuration Ethernet August

54 Configuring VLAN classification rule 2 ipv /32 vlan 2 5. To exit the VLAN classification configuration context, enter: exit 6. To select an Ethernet interface (in this example, interface 0/3), enter: interface ethernet 0/3 7. To apply a classification rule to the selected interface, enter: vlan classification protocol rule 1 vlan To deselect the Ethernet interface, enter: exit 9. To select another Ethernet interface (in this example, interface 0/4), enter: interface ethernet 0/4 10. To apply a classification rule to the selected interface, enter: vlan classification protocol rule 2 vlan To deselect the interface, enter: exit 54 Configuration Ethernet August 2010

55 Chapter 9: Configuring VLAN stacking Use the procedures in this section to configure VLAN stacking. Enabling VLAN stacking You can configure VLAN stacking on access, trunk, and hybrid interfaces. Use the procedure in this section to enable VLAN stacking on an interface. Prerequisites Before you enable VLAN stacking you must ensure that you have configured both ends of the link as access, trunk, or hybrid. 2. To select an interface, enter: interface [range] ethernet <slot/port> 3. To configure the interface as a Layer 2 interface, enter: switchport [trunk hybrid] 4. To enable VLAN stacking, enter: switchport mode access vlan-stacking Disabling VLAN stacking Use the procedure in this section to disable VLAN stacking. Note that the "no" command option is unavailable for VLAN stacking. 2. To select an interface, enter: Configuration Ethernet August

56 Configuring VLAN stacking interface [range] ethernet <slot/port> 3. To disable VLAN stacking, enter: switchport mode [access trunk hybrid] Verifying VLAN stacking configuration Use the procedure in this section to verify the successful operation of your VLAN stacking configuration. To verify the successful operation of VLAN stacking configuration, enter: show bridge port 56 Configuration Ethernet August 2010

57 Chapter 10: Configuring port mirroring The port mirroring feature is supported only on the interface module Ethernet ports. You can configure a maximum of one analyzer (destination) port for each module. There is no limitation on the number of ports that can be monitored for "receive" packets. However, each analyzer port can monitor up to eight ports for both transmit and receive (both) packets. Enabling port mirroring Use the procedure in this section to configure one mirroring port (destination port) for each mirrored port (source port). The analyzer and monitor ports can reside either on the same slot or on different slots. 2. To enable port mirroring, enter: mirror source <interface id> destination <interface id> direction {both receive} Table 13: definitions destination <interface id> direction {both receive} source <interface id> The interface ID that identifies the mirroring port. For example, ethernet5/1. The direction of packets that you want to mirror. Use a value of both to mirror both transmit and receive packets. Use a value of receive to mirror receive packets only. The interface ID that identifies the mirrored port. For example, ethernet6/1. Configuration Ethernet August

58 Configuring port mirroring Disabling port mirroring Use the procedure in this section to disable port mirroring. 1. To access configuration mode, enable: 2. To disable port mirroring, enter: no mirror source <interface id> destination <interface id> direction {both receive} Verifying port mirroring configuration Use the procedure in this section to view summary information about mirrored ports on the Avaya Advanced Gateway 2330 (AG2330). To view port mirroring information and status, enter: show mirror Example of configuring port mirroring 2. To configure port 6/1 as the analyzer port for ports 5/1, 5/2, and 5/3, enter: mirror source ethernet5/1 destination ethernet6/1 direction both mirror source ethernet5/2 destination ethernet6/1 direction receive mirror source ethernet6/2 destination ethernet6/1 direction both 58 Configuration Ethernet August 2010

59 Chapter 11: Configuring MAC entries Use the procedures in this section to configure static MAC entries. Adding static MAC address entries to the MAC address table Use the procedure in this section to add a list of interfaces and associated MAC addresses to the Layer 2 forwarding table. 2. To add entries to the MAC address table, enter: mac address <mac addr> {forward discard} <interface> vlan <vid> Table 14: definitions {forward discard} <interface> <vid> Specify whether frames received with the configured MAC address are to be discarded or forwarded. Specifies the interface on which the frame enters the Avaya Advanced Gateway 2330 (AG2330). For example, ethernet6/1. Specifies the VLAN ID of the received frames. Deleting a static MAC address entry Use the procedure in this section to remove a static MAC address entry from the MAC address table. Configuration Ethernet August

60 Configuring MAC entries 2. To add entries to the MAC address table, enter: no mac address <mac addr> {forward discard} <interface> vlan <vid> Verifying static MAC address entries After you have configured static MAC Address entries, use the procedure in this section to verify operation. To verify static MAC address configuration, enter: show bridge mac static Example of configuring static MAC address entries In this example, VLANs 10 and 11 and interfaces 6/1 and 6/2 have been previously configured. 1. To create a static MAC address entry for interface 6/1, enter: mac address forward ethernet6/1 vlan To create a static MAC address entry for interface 6/2, enter: mac address discard ethernet6/2 vlan To remove the MAC entry for interface 6/1, enter: no mac address forward ethernet6/1 vlan 10 Configuring MAC address aging time Use the procedure in this section to specify an age-out time for a learned MAC address. The learned MAC address will persist until the configured age-out time is expired. 60 Configuration Ethernet August 2010

61 Restoring the default MAC address aging time 2. To access the bridge command context, enter: bridge 3. To configure the MAC address age-out time, enter: mac aging-time <age-out value> Table 15: definitions <age-out value> The number of seconds that a learned MAC address persists. The default age-out time value is 300 seconds. Valid values are 10 to 630 seconds. Restoring the default MAC address aging time Use the procedure in this section to restore the default age-out time for a learned MAC address. 2. To access the bridge command context, enter: bridge 3. To restore the default MAC address age-out time, enter: no mac aging-time <age-out value> Verifying the MAC address aging time After you have configured MAC Address entries, use the procedure in this section to verify successful operation. 1. To view summary information of bridge configuration, enter: Configuration Ethernet August

62 Configuring MAC entries show bridge config 2. To view detailed bridge information, enter: show bridge detail Example of configuring MAC address aging time 2. To access the bridge command context, enter: bridge 3. To configure the MAC address aging time to 100 seconds, enter: mac aging-time To restore the default MAC address aging time, enter: no mac aging-time Configuration Ethernet August 2010

63 Chapter 12: Configuring Multiple Spanning Tree Protocol Use the procedures in this section to configure MSTP on the Avaya Advanced Gateway 2330 (AG2330). Configuring the region name and revision number Use the procedure in this section to configure the MSTP region name and revision number. 2. To access the bridge command context, enter: bridge 3. To access the MSTP command context, enter: mstp 4. To configure the region name, enter: region <region-name> 5. To configure the revision number, enter: revision <revision-number> Table 16: definitions <region-name> <revision-number> The name you specify for the MSTP region. The revision number that you assign. The default value is 0. Valid values are 0 to 255. Resetting the revision number Use the procedure in this section to restore the default revision number (0). Configuration Ethernet August

64 Configuring Multiple Spanning Tree Protocol 2. To access the bridge command context, enter: bridge 3. To access the MSTP command context, enter: mstp 4. To configure the revision number, enter: no revision <revision-number> Table 17: definitions <revision-number> Specifies the revision number that is currently configured. The default value is 0. Valid values are 0 to 255. Configuring Common Spanning Tree Use the procedures in this section to configure CST elements. Configuring bridge priority You can assign a priority to the bridge. The lower the priority, the greater the chance that the bridge becomes root for the CST. 2. To access the bridge command context, enter: bridge 3. To configure the priority value, enter: priority <value> 64 Configuration Ethernet August 2010

65 Configuring Common Spanning Tree Table 18: definitions <value> Specifies the bridge priority. The default value is (or hex 0x8000). Valid values are 0 to 61440, and are increments of Restoring the default bridge priority value Use the procedure in this section to restore the bridge priority value to the default setting. 2. To access the bridge command context, enter: bridge 3. To restore the bridge priority value to the default setting, enter: no priority <value> Table 19: definitions <value> Specifies the bridge priority that is currently configured. Valid values are 0 to 61440, and are increments of The default value is Configuring hop count Hop count in the packet gets decremented on every node that it traverses. Once the hop count reaches zero, the packet becomes stale. Use the procedure in this section to configure the maximum hops for a BPDU. 2. To access the bridge command context, enter: bridge 3. To access the MSTP command context, enter: Configuration Ethernet August

66 Configuring Multiple Spanning Tree Protocol mstp 4. To specify the maximum hops, enter: max-hops <value> Table 20: definitions <value> The maximum hops for which a BPDU is valid. Valid values are 1 to 40. The default value is 20. Restoring the default maximum hops value Use the procedure in this section to restore the default maximum hops value for a BPDU. 2. To access the bridge command context, enter: bridge 3. To access the MSTP command context, enter: mstp 4. To restore the default maximum hops value, enter: no max-hops <value> Table 21: definitions <value> Specifies the maximum hop value that is currently configured. Valid values are 1 to 40. The default value is Configuration Ethernet August 2010

67 Configuring Common Spanning Tree Procedure job aid Figure 9: Hop count of a packet Configuring link path cost and priority Use the procedures in this section to configure the path cost and priority for a port. The port with the least path cost is selected as the preferred port for traffic transmission. Similarly, the lower the port priority, the greater the chance that the port is selected for traffic transmission. Configuring link path cost Use the procedure in this section to configure the link path cost. 2. To select an interface, enter: interface [range] ethernet <slot/port> 3. To access the Spanning Tree command context, enter: spanning-tree 4. To configure the path cost, enter: Configuration Ethernet August

68 Configuring Multiple Spanning Tree Protocol path-cost <value> Table 22: definitions <slot/port> path-cost <value> The slot and port numbers that identify the port for which you configure the path cost. For example, 7/1. Specifies the path cost. The default value is auto-detect. Valid values are 1 to Restoring the default path cost Use the procedure in this section to restore the default path cost (auto-detect). 2. To select an interface, enter: interface [range] ethernet <slot/port> 3. To access the Spanning Tree command context, enter: spanning-tree 4. To restore the default path cost, enter: no path-cost <value> Table 23: definitions <slot/port> path-cost <value> The slot and port numbers that identify the port for which you configure the path cost. For example, 7/1. Specifies the path cost that is currently configured. The default value is autodetect. Valid values are 1 to Configuring link priority Use the procedure in this section to configure the link priority for an interface. 68 Configuration Ethernet August 2010

69 Configuring Common Spanning Tree 2. To select an interface, enter: interface [range] ethernet <slot/port> 3. To access the Spanning Tree command context, enter: spanning-tree 4. To configure the link priority, enter: priority <value> Table 24: definitions <slot/port> priority <value> The slot and port numbers that identify the port for which you configure the link priority. For example, 7/1. Specifies the link priority. The default value is 128. Valid values are 0 to 240. Restoring the default link priority Use the procedure in this section to restore the default link priority (128). 2. To select an interface, enter: interface [range] ethernet <slot/port> 3. To access the Spanning Tree command context, enter: spanning-tree 4. To restore the default link priority, enter: no priority <value> Configuration Ethernet August

70 Configuring Multiple Spanning Tree Protocol Table 25: definitions <slot/port> priority <value> The slot and port numbers that identify the port for which you configure the link priority. For example, 7/1. Specifies the link priority that is currently configured. The default value is 128. Valid values are 0 to 240. Procedure job aid Path cost on a port is dependent on the bandwidth of the link. In the following figure, Link A has more bandwidth than Link B. Consequently, Link A is the preferred path. The greater the bandwidth, the lower the path cost on the port. The port with the least path cost is selected as the preferred port for traffic transmission. Similarly, a port can be selected as the preferred path for traffic transmission by changing the priority on the port to a lower value. The lower the port priority, the greater the chance that the port is selected for traffic transmission. You can configure both path cost and priority parameters on a port. Figure 10: Link bandwidth and priority Configuring PortFast Use the procedure in this section to enable and disable rapid transitions. Enabling rapid transitions with PortFast Use the procedure in this section to enable rapid transitions. 70 Configuration Ethernet August 2010

71 Configuring Common Spanning Tree 2. To select an Ethernet interface, enter: interface [range] ethernet <slot/port> 3. To access the Spanning Tree command context, enter: spanning-tree 4. To enable rapid transitions, enter: portfast Table 26: definitions <slot/port> The slot and port numbers that identify the port on which you enable rapid transitions. For example, 7/1. Disabling rapid transitions Use the procedure in this section to disable rapid transitions. 2. To select an Ethernet interface, enter: interface [range] ethernet <slot/port> 3. To access the Spanning Tree command context, enter: spanning-tree 4. To disable rapid transitions, enter: no portfast Table 27: definitions <slot/port> The slot and port numbers that identify the port on which you disable rapid transitions. For example, 7/1. Configuration Ethernet August

72 Configuring Multiple Spanning Tree Protocol Configuring PortFast BPDU Guard Use the procedures in this section to enable and disable BPDU Guard on a PortFastenabled port. Enabling PortFast BPDU Guard Use the procedure in this section to enable BPDU Guard on a port. 2. To select an Ethernet interface, enter: interface [range] ethernet <slot/port> 3. To access the Spanning Tree command context, enter: spanning-tree 4. To enable PortFast BPDU Guard, enter: portfast bpdu-guard Table 28: definitions <slot/port> The slot and port numbers that identify the port on which you enable BPDU guard. For example, 7/1. Disabling PortFast BPDU Guard Use the procedure in this section to disable BPDU Guard on a port. 2. To select an Ethernet interface, enter: interface [range] ethernet <slot/port> 3. To access the Spanning Tree command context, enter: 72 Configuration Ethernet August 2010

73 Configuring Common Spanning Tree spanning-tree 4. To disable BPDU Guard, enter: no portfast bpdu-guard Table 29: definitions <slot/port> The slot and port numbers that identify the port on which you disable BPDU guard. For example, 7/1. Configuring PortFast BPDU Filter Use the procedure in this section to enable and disable PortFast BPDU Filter on a port. The Spanning Tree Protocol sends BPDUs from all ports. Enabling the BPDU Filter feature ensures that PortFast-enabled ports do not transmit or receive any BPDUs. Enabling PortFast BPDU Filter Use the procedure in this section to enable PortFast BPDU filter for a port. 2. To select an Ethernet interface, enter: interface [range] ethernet <slot/port> 3. To access the Spanning Tree command context, enter: spanning-tree 4. To enable PortFast BPDU Filter, enter: portfast bpdu-filter Table 30: definitions <slot/port> The slot and port numbers that identify the port on which you enable the Portfast BPDU Filter. For example, 7/1. Configuration Ethernet August

74 Configuring Multiple Spanning Tree Protocol Disabling PortFast BPDU Filter Use the procedure in this section to disable PortFast BPDU filter for a port. 2. To select an Ethernet interface, enter: interface [range] ethernet <slot/port> 3. To access the Spanning Tree command context, enter: spanning-tree 4. To disable PortFast BPDU Filter on the port, enter: no portfast bpdu-filter Table 31: definitions <slot/port> The slot and port numbers that identify the port on which you disable the Portfast BPDU Filter. For example, 7/1. Configuring MSTP timers The AG2330 transmits a BPDU at every hello time. Use the procedures in this section to configure the timer value. Configuring hello time The hello time is the time, in seconds, after which (if the bridge is the root bridge) all the bridges in a bridged LAN exchange BPDUs. A very low hello time value results in excessive traffic on the network, while a higher value delays the detection of topology change. 2. To access the bridge command context, enter: 74 Configuration Ethernet August 2010

75 Configuring Common Spanning Tree bridge 3. To configure the hello time interval, enter: hello-time <time value> Table 32: definitions <time value> The interval, expressed in seconds, between BPDU exchanges. The default value is 2 seconds. Valid values are 1 to 10 seconds. Restoring the default hello time value Use the procedure in this section to restore the hello time value to the default setting (2 seconds). 2. To access the bridge command context, enter: bridge 3. To restore the default hello time interval, enter: no hello-time <time value> Table 33: definitions <time value> The hello time interval currently configured. The default value is 2 seconds. Valid values are 1 to 10 seconds. Configuration Ethernet August

76 Configuring Multiple Spanning Tree Protocol Procedure job aid Figure 11: Transmission of BPDU at hello time Configuring forward delay Forward delay is the time interval that bridges use to transition root and designated ports to the forwarding state. When the AG2330 powers up, or when a device is connected to a port, the port normally enters the Spanning Tree listening state. When the forward delay timer expires, the port enters the learning state. When the forward delay timer expires a second time, the port transitions to the forwarding state. 2. To access the bridge command context, enter: bridge 3. To set the forward delay value, enter: forward-delay <time value> 76 Configuration Ethernet August 2010

77 Configuring Common Spanning Tree Table 34: definitions <time value> Specifies the forward time delay, expressed in seconds. The default value is 15 seconds. Valid values are 4 to 30 seconds. Restoring the default forward delay value Use the procedure in this section to restore the forward delay value to the default setting (15 seconds). 2. To access the bridge command context, enter: bridge 3. To restore the forward value to the default setting, enter: no forward-delay <time value> Table 35: definitions <time value> Specifies the currently configured forward time delay, expressed in seconds. The default value is 15 seconds. Valid values are 4 to 30 seconds. Configuration Ethernet August

78 Configuring Multiple Spanning Tree Protocol Procedure job aid Figure 12: Forward delay representation Configuring maximum age time The maximum age time represents the maximum age of the information after which the information becomes stale. Use the procedures in this section to configure the maximum age time. 2. To access the bridge command context, enter: bridge 3. To configure the maximum age time value, enter: max-age <time value> Table 36: definitions <time value> The maximum age time, expressed in seconds. The default value is 20 seconds. Valid values are 6 to 40 seconds. Restoring the default maximum age time Use the procedure in this section to restore the maximum age time to the default setting (20 seconds). 78 Configuration Ethernet August 2010

79 Configuring Common Spanning Tree 2. To access the bridge command context, enter: bridge 3. To restore the default maximum age time, enter: no max-age <time value> Table 37: definitions <time value> The maximum age time that is currently configured. The default value is 20 seconds. Valid values are 6 to 40 seconds. Configuring link types Use the procedures in this section to configure the link type. 2. To select an Ethernet interface, enter: interface ethernet <slot/port> 3. To access the Spanning Tree command context, enter: spanning-tree 4. To specify the link type, enter: link-type <type> Table 38: definitions <slot/port> <type> The slot and port numbers that identify the port on which you configure the link type. For example, 7/1. Specifies the link type. Valid values are pointto-point and shared. The default value is point-to-point. Configuration Ethernet August

80 Configuring Multiple Spanning Tree Protocol Restoring the default link type Use the procedure in this section to restore the default link type (point-to-point) for an interface. 2. To select an Ethernet interface, enter: interface [range] ethernet <slot/port> 3. To access the Spanning Tree command context, enter: spanning-tree 4. To restore the default link type, enter: no link-type <type> Table 39: definitions <slot/port> <type> The slot and port numbers that identify the port on which you configure the link type. For example, 7/1. Specifies the link type. Valid values are pointto-point and shared. The default value is point-to-point. Procedure job aid When devices are connected back-to-back, the link is a point-to-point link. The following figure shows a point-to-point link. 80 Configuration Ethernet August 2010

81 Configuring an MSTP instance Figure 13: Point-to-point link When devices are connected through a hub (or any broadcasting device), the link is a shared link. MSTP requires more time for convergence over a shared link (that is, compared to a pointto-point link). The following figure shows a shared link. Figure 14: Shared link Configuring an MSTP instance Use the procedures in this section to configure MSTP instances. Creating an MSTP instance Use the procedure in this section to create an MSTP instance. Configuration Ethernet August

82 Configuring Multiple Spanning Tree Protocol 2. To access the bridge command context, enter: bridge 3. To access the MSTP command context, enter: mstp 4. To create an instance, enter: instance <instance id> Table 40: definitions <instance id> Specifies the MSTP instance ID. Valid values are 1 to 15. Associating a VLAN with an instance Use the procedure in this section to associate a VLAN with an MSTP instance. Prerequisites You must have created the VLAN. 2. To access the bridge command context, enter: bridge 3. To access the MSTP command context, enter: mstp 4. To select the MSTP instance, enter: instance <instance id> 5. To associate a VLAN with the MSTP instance, enter: vlan <vid> 82 Configuration Ethernet August 2010

83 Configuring an MSTP instance Table 41: definitions <instance id> <vid> Specifies the MSTP instance ID. Valid values are 1 to 15. Specifies the VLAN ID to associate with the MSTP instance. Valid values are 1 to Removing a VLAN from an MSTP instance Use the procedure in this section to remove a VLAN from an MSTP instance. 2. To access the bridge command context, enter: bridge 3. To access the MSTP command context, enter: mstp 4. To select the MSTP instance, enter: instance <instance id> 5. To remove a VLAN from the MSTP instance, enter: no vlan <vid> Table 42: definitions <instance id> <vid> Specifies the MSTP instance ID. Valid values are 1 to 15. Specifies the VLAN ID to remove from the MSTP instance. Valid values are 1 to Configuring priority for an instance You can assign a priority value for a bridge associated with an instance. The lower the priority, the greater the chance the bridge becomes root for that instance. Use the procedure in this section to configure priority for an instance. Configuration Ethernet August

84 Configuring Multiple Spanning Tree Protocol 2. To access the bridge command context, enter: bridge 3. To access the MSTP command context, enter: mstp 4. To select an MSTP instance, enter: instance <instance id> 5. To configure the priority for the instance, enter: priority <value> Table 43: definitions <instance id> <value> Specifies the MSTP instance ID. Valid values are 1 to 15. Specifies the priority that you assign to the instance. The default value for priority is Bridge priority values are in increments of Valid values are 0 to Restoring the default priority for an instance Use the procedure in this section to restore the default priority value for an instance. 2. To access the bridge command context, enter: bridge 3. To access the MSTP command context, enter: mstp 4. To select an MSTP instance, enter: instance <instance id> 5. To restore the default priority for the instance, enter: 84 Configuration Ethernet August 2010

85 Configuring an MSTP instance no priority <value> Table 44: definitions <instance id> <value> Specifies the MSTP instance ID. Valid values are 1 to 15. Specifies the priority that you assign to the instance. The default value for priority is Bridge priority values are in increments of Valid values are 0 to Configuring link path cost and priority for an instance Use the procedures in this section to configure the link path cost and priority for an instance. Assigning port path cost in an instance (Internal Spanning Tree) Use the procedure in this section to set the cost of a path for an MSTP instance. 2. To select an Ethernet interface, enter: interface ethernet <slot/port> 3. To access the Spanning Tree command context, enter: spanning-tree 4. To select an MSTP instance, enter: instance <instance id> 5. To configure the path cost for the instance, enter: path-cost <value> Table 45: definitions <instance id> Specifies the MSTP instance ID. Valid values are 1 to 15. Configuration Ethernet August

86 Configuring Multiple Spanning Tree Protocol <value> Specifies the path cost that you assign to the MSTP instance. Valid values are 1 to The default value is auto-detect. Restoring the default path cost for an instance Use the procedure in this section to restore the default path cost value for an MSTP instance. 2. To select an Ethernet interface, enter: interface [range] ethernet <slot/port> 3. To access the Spanning Tree command context, enter: spanning-tree 4. To select an MSTP instance, enter: instance <instance id> 5. To restore the default path cost for the instance, enter: no path-cost <value> Table 46: definitions <instance id> <value> Specifies the MSTP instance ID. Valid values are 1 to 15. Specifies the currently configured path cost for the MSTP instance. Valid values are 1 to The default value is auto-detect. Assigning port priority in an instance (Internal Spanning Tree) Use the procedure in this section to set the port priority for an MSTP instance. 2. To select an Ethernet interface, enter: 86 Configuration Ethernet August 2010

87 Configuring an MSTP instance interface [range] ethernet <slot/port> 3. To access the Spanning Tree command context, enter: spanning-tree 4. To select an MSTP instance, enter: instance <instance id> 5. To configure the port priority for the instance, enter: priority <value> Table 47: definitions <instance id> <value> Specifies the MSTP instance ID. Valid values are 1 to 15. Specifies the port priority that you assign to the MSTP instance. The default value for priority is Bridge priority values are in increments of Valid values are 0 to Restoring the default port priority for an instance Use the procedure in this section to restore the default port priority value for an MSTP instance. 2. To select an Ethernet interface, enter: interface [range] ethernet <slot/port> 3. To access the Spanning Tree command context, enter: spanning-tree 4. To select an MSTP instance, enter: instance <instance id> 5. To restore the default port priority for the instance, enter: no priority <value> Configuration Ethernet August

88 Configuring Multiple Spanning Tree Protocol Table 48: definitions <instance id> <value> Specifies the MSTP instance ID. Valid values are 1 to 15. Specifies the currently configured port priority for the MSTP instance. The default value for priority is Bridge priority values are in increments of Valid values are 0 to Configuring the Spanning Tree version on a port You can configure MSTP, RSTP, or STP on a port of a bridge. If STP is configured on the port, only STP packets flow through that port. MSTP is enabled on every port, by default. Use the procedure in this section to set the Spanning Tree version on a port. 2. To select an Ethernet interface, enter: interface [range] ethernet <slot/port> 3. To access the Spanning Tree command context, enter: spanning-tree 4. To configure the Spanning Tree version for the port, enter: force-version <WORD> Table 49: definitions <WORD> Specifies the STP version for the port. Valid values for <WORD> are STP, RSTP, and MSTP. The default value is MSTP. Restoring the default Spanning Tree version Use the procedure in this section to restore the default Spanning Tree version (MSTP) on a port. 88 Configuration Ethernet August 2010

89 Verifying MSTP operation 2. To select an Ethernet interface, enter: interface [range] ethernet <slot/port> 3. To access the Spanning Tree command context, enter: spanning-tree 4. To restore the default setting for the Spanning Tree version, enter: no force-version <WORD> Table 50: definitions <WORD> Specifies the STP version that is currently configured on the port. Valid values for <WORD> are STP, RSTP, and MSTP. The default value is MSTP. Verifying MSTP operation Use the procedures in this section to view information related to the configuration and operation of MSTP. Viewing information for MSTP Common Spanning Tree Use the procedure in this section to view information about the state and role of all ports in Common Spanning Tree. To view information about the ports in Common Spanning Tree, enter: show spanning-tree Viewing information for MSTP instances Use the procedure in this section to view information about the state and role of all ports in Common Spanning Tree and in all instances. Configuration Ethernet August

90 Configuring Multiple Spanning Tree Protocol To view information about the ports in Common Spanning Tree and in all instances, enter: show spanning-tree detail Viewing bridge information for an instance Use the procedure in this section to view information about bridge priority, root ID, and the root port for an instance. To view bridge information for an instance, enter: show spanning-tree mstp instance <instance id> Table 51: definitions <instance id> Specifies the instance for which you want to view information. Valid values are 1 to 15. Viewing interface information Use the procedure in this section to view information about port priority, port IDs, port path cost, and so on for common spanning tree. To view interface information, enter: show spanning-tree interface <interface name> Table 52: definitions <interface name> Specifies the interface for which you want to view information. For example, ethernet7/1. Viewing VLAN information for all instances Use the procedure in this section to view information about the association between VLANs and instances. 90 Configuration Ethernet August 2010

91 Verifying MSTP operation To view information about VLANs and all instances, enter: show spanning-tree mstp instance vlan Viewing VLAN information for a specified instance Use the procedure in this section to view information about the VLANs in a specified instance. To view information about VLANs in an instance, enter: show spanning-tree mstp instance <instance id> vlan Configuration Ethernet August

92 Configuring Multiple Spanning Tree Protocol 92 Configuration Ethernet August 2010

93 Chapter 13: IP routing concepts The gateway management features covered in this documentation apply regardless of which routing protocols are used and include gateway Internet Protocol (IP) configuration, IP route table management, Address Routing Protocol (ARP) configuration, and ARP table management. You must be familiar with the basics of routing and IP addresses. This section includes the following topics: IP addressing on page 93 Static routes on page 95 Black hole static routes on page 96 Loopback IP on page 96 IP addressing An IP version 4 address consists of 32 bits expressed in a dotted-decimal format (x.x.x.x). The IP version 4 address space is divided into classes, with classes A, B, and C reserved for unicast addresses and accounting for 87.5 percent of the 32-bit IP address space. Class D is reserved for multicast addressing. Table 53: IP addresses on page 93 lists the breakdown of IP address space by address range and mask. Table 53: IP addresses Class Address range Mask Number of addresses A B * 255 C * 255 * 255 D To express an IP address in dotted-decimal notation, you convert each octet of the IP address to a decimal number and separate the numbers by decimal points. For example, you specify the 32-bit IP address in dotted-decimal notation as Each IP address class, when expressed in binary, has a different boundary point between the network and host portions of the address as illustrated in Figure 15: Network and host boundaries in IP address classes on page 94. The network portion is a network number field from 8 through 24 bits. The remaining 8 through 24 bits identify a specific host on the network. Configuration Ethernet August

94 IP routing concepts Figure 15: Network and host boundaries in IP address classes Subnet addressing Subnetworks (or subnets) extend the IP addressing scheme used by an organization to one with an IP address range for multiple networks. Subnets are two or more physical networks that share a common network-identification field (the network portion of the 32-bit IP address). You create a subnet address by increasing the network portion to include a subnet address, thus decreasing the host portion of the IP address. For example, in the address , the network portion is , while the subnet is found in the first octet of the host portion (10). A subnet mask is applied to the IP address and identifies the network and host portions of the address. Table 54: Subnet masks for class B and class C IP addresses on page 94 illustrates how subnet masks used with class B and class C addresses can create differing numbers of subnets and hosts. This example includes using the zero subnet, which is permitted on an Avaya Advanced Gateway 2330 (AG2330). Table 54: Subnet masks for class B and class C IP addresses Number of bits Subnet mask Number of subnets (recommended) Class B Number of hosts per subnet Configuration Ethernet August 2010

95 Static routes Number of bits Subnet mask Number of subnets (recommended) Number of hosts per subnet Class C Static routes Static routes allow you to create routes to a destination IP address manually (see also Black hole static routes on page 96). You can use a static default route to specify a route to all networks for which there are no explicit routes in the Forwarding Information Base or the routing table. This route is by definition a route with the prefix length of zero (RFC 1812). You can configure the AG2330 with any route through the IP static routing table. Static routes can also be configured with a next hop that is not directly connected, but that hop must be reachable. Otherwise, the static route is not enabled. The configured gateway can be either a specific IP address or router interface. Configuration Ethernet August

96 IP routing concepts Black hole static routes A black hole static route is a route with an invalid next hop, such that the data packets destined for this network are dropped by the gateway (see also Static routes on page 95). While aggregating or injecting routes to other routers, the gateway itself may not have a path to the aggregated destination. In such cases, the result is a black hole and a routing loop. To avoid such loops, configure a black hole static route to the destination the gateway is advertising. You can configure a preference value for a black hole route. However, you must configure that preference value appropriately, so that when you wish the black hole route to be used, it gets elected as the best route. Before adding a black hole static route, perform a check to ensure that there is no other static route to that identical destination in an enabled state. If such a route exists, you cannot add the black hole route and an error message is displayed. Equal Cost Multipath (ECMP) With Equal Cost Multipath (ECMP) the AG2330 can determine up to eight equal-cost paths to the same destination prefix. You can use multiple paths for load sharing of traffic. These multiple paths allow faster convergence to other active paths in case of network failure. By maximizing load sharing among equal-cost paths, you can use your links between routers more efficiently when sending IP traffic. Equal Cost Multipath is formed using routes from same source or protocol. The AG2330 supports per-packet or flow-based ECMP. Loopback IP Loopback IP (also known as circuitless IP or CLIP) is a virtual interface that is not associated with any physical port. You can use the loopback interface to provide uninterrupted connectivity to your gateway as long as there is an actual path to reach the device. The loopback interface is treated as any other IP interface. The network associated with the loopback is treated as a local network attached to the device. This route always exists and the circuit is always up because there is no physical attachment. Routes are advertised to routers in the domain as external routes using the routeredistribution process. 96 Configuration Ethernet August 2010

97 Routing over VLAN interfaces When you create a loopback interface, the system software programs a local route with the CPU as destid. The CPU processes all packets that are destined to the loopback interface address. Any other packets with destination addresses associated with this network (but not to the interface address) are treated as if they are from an unknown host. A loopback address can be used as source IP address in the IP header when sending remote monitoring (RMON) traps. Routing over VLAN interfaces On the AG2330, you can enable static routing on VLAN interfaces. Configuration Ethernet August

98 IP routing concepts 98 Configuration Ethernet August 2010

99 Chapter 14: Configuring IP routing This section describes CLI commands that you use to configure Layer 3 (routing) functions in your Avaya Advanced Gateway 2330 (AG2330). For conceptual information about Layer 3 routing functions, see IP routing concepts. This section includes the following topics: IP routing commands on page 99 Show commands on page 100 Configuring routing for interfaces on page 103 IP routing commands The IP routing commands configure general characteristics of the gateway. Configuring load balancing for equal cost routes This procedure describes how to specify a load balancing policy for equal cost routes. 1. Enter configuration mode. 2. To specify the policy, enter: ip load-balancing policy [per-flow per-packet] Configuring a static route This procedure describes how to configure a static IP route. Use the no form of this command to disable the distance for static routes of a subnet mask. 1. Enter configuration mode. Configuration Ethernet August

100 Configuring IP routing 2. To configure the IP route, enter: [no] ip route <destprefix> <ipaddressmask> <gatewayip interface> <distvalue> Table 55: definition <address> <mask> <gatewayip> <interface> The IP destination prefix for the route to be added. The IP destination prefix mask for the route to be added. The IP gateway address of the route to be added. The name of the interface. <distvalue> The distance value for the route, in the range 1 to 255. Configuring an access list This procedure describes how to configure an access list. 1. Enter configuration mode. 2. To configure the access list, enter: [no] access-list <listname> {permit {<prefix> [exact-match] any} deny {<prefix> [exact-match] any} remark <comment>} Table 56: definition <listname> <prefix> <comment> [no] A name for the access list. The IP prefix (network/length) to match. Description of the access list, up to 100 characters. Removes the access list configuration. Show commands The show IP commands display the general IP characteristics of the gateway. 100 Configuration Ethernet August 2010

101 Show commands Displaying IP access lists This procedure describes how to display IP access lists. To display IP access lists, enter: show ip access-list <name> Table 57: definition <name> The name of the access list you want to display. Displaying interface information This procedure describes how to display interface information. The interface display includes the highest supported capability for each interface: FE for Fast Ethernet and GE for Gigabit Ethernet. 1. To display interface information, enter: show ip interfaces 2. To display information only about a specific interface, enter: show ip interfaces interface <ifname> 3. To display a summary of the interface information, enter: show ip interfaces brief [interface <ifname>] 4. To display information for a specific Ethernet interface, enter: show interface ethernet <slot/port> 5. To display information for all Ethernet interfaces, enter: show interface ethernets Table 58: definition <ifname> The interface name for which you want to display information. Configuration Ethernet August

102 Configuring IP routing Figure 16: show ip interface command output Figure 17: show ip interface ethernet command output Displaying the IP routing table This procedure describes how to display the IP routing table. To display the IP routing table, enter: 102 Configuration Ethernet August 2010

103 Configuring routing for interfaces show ip route [routetype] Table 59: definition <routetype> Optional route-type information to display. Possible options are: A.B.C.D - The network in the IP routing table to display. connected - Display connected route information. database - The IP routing table database to display. static - Display static information. summary - Display a summary of all routes. Configuring routing for interfaces This section describes some of the generic port-related IP routing commands. Other port commands are included in sections of this manual that describe commands that are used with a specific protocol or feature. These commands apply to Ethernet interfaces. Configuring the IP address and mask for an interface This procedure describes how to configure the IP address and subnet mask for an interface. 1. Enter configuration mode. 2. Enter interface mode. interface <interface> 3. To configure the IP address and subnet mask, enter: ip address <address> <mask> Table 60: definition <address> <mask> The IP address for the interface. The subnet mask for the interface. Configuration Ethernet August

104 Configuring IP routing Enabling proxy arp This procedure describes how to enable proxy arp. 1. Enter configuration mode. 2. Enter interface mode. interface <interface> 3. To enable proxy arp, enter: ip proxy_arp Configuring ICMP redirect messages on an interface This procedure describes how to configure ICMP redirect messages on an interface. Use the no form of this command to disable. 1. Enter configuration mode. 2. Enter interface mode. interface <interface> 3. To enable ICMP redirect messages, enter: [no] ip redirects Configuring ICMP destination unreachable messages on an interface This procedure describes how to enable ICMP destination unreachable messages on an interface. Use the no form of this command to disable. 1. Enter configuration mode. 2. Enter interface mode. 104 Configuration Ethernet August 2010

105 Configuring routing for interfaces interface <interface> 3. To enable ICMP destination unreachable messages, enter: [no] ip unreachables Configuration Ethernet August

106 Configuring IP routing 106 Configuration Ethernet August 2010

107 Chapter 15: IPv6 routing fundamentals The gateway-management features apply regardless of which routing protocols you use and include gateway Internet Protocol version 6 (IPv6) configuration and IPv6 route table management. IPv6 routing fundamentals navigation The IPv6 header on page 107 ICMPv6 on page 112 Neighbor discovery on page 112 Multicast on page 117 IPv6 and the Avaya Advanced Gateway 2330 on page 117 Management access on page 118 Path MTU discovery on page 118 Routing on page 118 IPv6 Routing over VLAN on page 121 The IPv6 header The IPv6 header contains the following fields: a 4-bit Internet Protocol version number, with a value of 6 an 8-bit traffic class field, similar to Type of Service in IPv4 a 20-bit flow label that identifies traffic flow for additional quality of service a 16-bit unsigned integer, the length of the IPv6 payload an 8-bit next header selector, that identifies the following header an 8-bit hop limit unsigned integer that decrements by 1 each time a node forwards the packet. Nodes discard packets with hop limit values of 0. a 128-bit source address a 128-bit destination address Figure 18: IPv6 header on page 108 illustrates the IPv6 header. Configuration Ethernet August

108 IPv6 routing fundamentals Figure 18: IPv6 header IPv6 addresses IPv6 addresses are 128 bits in length. The address identifies a single interface or multiple interfaces. IPv4 addresses, in comparison, are 32 bits in length. The increased number of possible addresses in IPv6 solves the inevitable IP Address exhaustion inherent to IPv4. The IPv6 address contains two parts: an address prefix and an IPv6 interface ID. The first 3 bits indicate the type of address that follows. Figure 19: 128-Bit IPv6 address format on page 108 shows the IPv6 address format. Figure 19: 128-Bit IPv6 address format An example of a unicast IPv6 address is 1080:0:0:0:8:8000:200C:417A Interface ID The interface ID is a unique number that identifies an IPv6 node (a host or a router). For stateless autoconfiguration the ID is 64 bits in length. 108 Configuration Ethernet August 2010

109 The IPv6 header In IPv6 stateless autoconfiguration, the interface ID is derived by a formula that uses the link layer 48-bit MAC address. (In most cases, the interface ID is a 64-bit interface ID that contains the 48-bit MAC address.) The IPv6 interface ID is as unique as the MAC address. If you manually configure interface IDs or MAC addresses (or both), no relationship between the MAC address and the interface ID is necessary. A manually configured interface ID can be longer or shorter than 64 bits. Anycast Address An IPv6 anycast address is a unicast address identifying a group of IPv6 nodes that share a common variable-length address prefix. A packet bearing an anycast address is delivered to one node in the group. There is no visual way of distinguishing an anycast address from an unicast address. Multicast Address An IPv6 multicast address identifies a group of nodes. A packet bearing a multicast address is delivered to all members of the group. (The function of IPv4 broadcast addresses has been superseded by IPv6 multicast addresses.) Figure 20: Multicast Address Format on page 109 shows the format of an IPv6 multicast address. Figure 20: Multicast Address Format A value of FF ( ) in the 8 high-order bits of an IPv6 address indicates that the address specifies a multicast group. The 4-bit flags field indicates whether the group is permanent or transient. The 4-bit scope field indicates the scope of the group specified in the 112-bit group ID field. The scope options are: 1 - node local 2 - link-local 3 - subnet local 4 - admin local 5 - site-local 8 - organization-local Configuration Ethernet August

110 IPv6 routing fundamentals B - community-local E - global An example of a multicast address is: FF01:0:0:0:0:0:0:101 IPv4-Compatible Address The IPv4-compatible address, which includes an IPv4 address in the low-order 32 bits, is intended for IPv6 nodes that need to inter operate with IPv4 nodes. Figure 21: IPv4- Compatible Unicast Address Format on page 110 shows the format of an IPv4-compatible address. Figure 21: IPv4-Compatible Unicast Address Format Address formats The format for representing an IPv6 address is n:n:n:n:n:n:n:n n is the hexadecimal representation of 16 bits in the address. For example: FF01:0:0:0:0:0:0:43 Each non zero field must contain at least one numeral. Within a given hexadecimal field however, leading zeros are not required. Certain classes of IPv6 addresses commonly include multiple contiguous fields containing hexadecimal 0. The following sample address includes five contiguous fields containing 0 represents contiguous fields containing zeroes with a double colon (::): FF01::43 You can use a double colon to compress the leading zero fields in a hexadecimal address. A double colon can appear once in an address. An IPv4-compatible address combines hexadecimal and decimal values as follows: x:x:x:x:x:x:d.d.d.d x:x:x:x:x:x is a hexadecimal representation of the six high-order 16-bit pieces of the address, and d.d.d.d is a decimal representation of the four 8-bit pieces of the address. For example: 0:0:0:0:0:0: Configuration Ethernet August 2010

111 The IPv6 header or :: IPv6 extension headers IPv6 extension headers describe processing options. Each extension header contains a separate category of options. A packet can include zero or more extension headers, see Figure 22: IPv6 Header and Extension Headers on page 111. Figure 22: IPv6 Header and Extension Headers IPv6 examines the destination address in the main header of each packet it receives: this examination determines whether the gateway is the packet destination or an intermediate node in the packet data path. If the gaeway is the destination of the packet, IPv6 examines the header extensions that contain options for destination processing. If the gateway is an intermediate node, IPv6 examines the header extensions that contain forwarding options. By examining only the extension headers that apply to the operations it performs, IPv6 reduces the amount of time and processing resources required to process a packet. IPv6 defines the following extension headers: The hop-by-hop extension header contains optional information that all intermediate IPv6 routers examine between the source and the destination. The end-to-end extension header contains optional information for the destination node. The source routing extension header contains a list of one or more intermediate nodes that define a path for the packet to follow through the network, to its destination. The packet source creates this list. This function is similar to the IPv4 source routing options. The fragmentation extension header uses by an IPv6 source to send packets larger than the size specified for the path MTU. The authentication extension header and the security encapsulation extension header, used singly or jointly, provide security services for IPv6 datagrams. Comparison of IPv4 and IPv6 Table 61: IPv4 and IPv6 differences on page 112 compares key differences between IPv4 and IPv6. Configuration Ethernet August

112 IPv6 routing fundamentals Table 61: IPv4 and IPv6 differences Feature IPv4 IPv6 Address length 32 bits 128 bits IPSec support Optional Required QoS support Limited Improved Fragmentation Hosts and routers Hosts only MTU Packet size 576 bytes 1280 bytes Checksum in header Yes No Options in header Yes No Link-layer address resolution ARP (broadcast) Multicast Neighbor Discovery Messages Multicast membership IGMP Multicast Listener Discovery (MLD) Router Discovery Optional Required Uses broadcasts Yes No Configuration Manual, DHCP Automatic, DHCP ICMPv6 Internet Control Message Protocol (ICMP) version 6 maintains and improves upon features from ICMP for IPv4. ICMPv6 reports the delivery of forwarding errors, such as Destination Unreachable, Packet Too Big, Time Exceeded, and Parameter Problem. ICMPv6 also delivers information messages such as echo request and echo reply. Important: ICMPv6 plays an important role in IPv6 features such as Neighbor Discovery, Multicast Listener Discovery and Path MTU Discovery. Neighbor discovery Neighbor discovery (ND) allows IPv6 nodes (routers and hosts) on the same link to discover link layer addresses and to obtain and advertise various network parameters and reachability information. ND combines the services provided for IPv4 with the Address Resolution Protocol (ARP) and router discovery. ND replaces ARP in IPv6. Hosts use ND to discover the routers in the network that you can use as the default routers, and to determine the link layer address of their neighbors attached on their local links. Routers 112 Configuration Ethernet August 2010

113 Neighbor discovery also use ND to discover their neighbors and their link layer information. ND also updates the neighbor database with valid entries, invalid entries, and entries migrated to different locations. ND protocol provides you with the following: Address and prefix Discovery: hosts determine the set of addresses that are on-link for the given link. Nodes determine which addresses or prefixes are locally reachable and are remote with address and prefix discovery. Router Discovery: hosts discover neighboring routers with router discovery. Hosts then establish neighbors as default packet-forwarding routers. Parameter Discovery: host and routers discover link parameters such as the link MTU or the hop limit value placed in outgoing packets. Duplicate address detection: hosts and nodes determine if an address is assigned to another router or a host. Address Resolution: hosts determine link layer addresses (MAC for Ethernet) of the local neighbors (attached on the local net), provided the IP address is known. Next-Hop determination: hosts determine how to forward local or remote traffic with nexthop determination. The next-hop can be a local or remote router. Neighbor unreachability detection: hosts determine if the neighbor is reachable, and address resolution must be performed again to update the database. For neighbors you use as routers, hosts attempt to forward traffic through alternate default routers. Redirect: routers inform the host of more efficient routes with redirect messages. Neighbor discovery is categorized into three components: Host-Router discovery Host-Host communication component Redirect See Figure 23: Neighbor Discovery components on page 113 for the ND components. Figure 23: Neighbor Discovery components Configuration Ethernet August