NN46220 511 (MERS8600 R6.0 Configuration VLANs Spanning Tree and Link Aggregation) Rev04.01

Ciena® Confidential and Proprietary

Configuration — VLANs, Spanning Tree, and Link AggregationSoftware Release 6.0

NN46220-511 - Revision 04.01June 26, 2009Copyright Ciena® Corporation

MERS 8600®Metro Ethernet Routing Switch 8600

MERS 8600 Metro Ethernet Routing Switch 8600 NN46220-511 - Revision 04.01Copyright Ciena® Corporation June 26, 2009

LEGAL NOTICES

THIS DOCUMENT CONTAINS CONFIDENTIAL AND TRADE SECRET INFORMATION OF CIENA CORPORATIONAND ITS RECEIPT OR POSSESSION DOES NOT CONVEY ANY RIGHTS TO REPRODUCE OR DISCLOSE ITSCONTENTS, OR TO MANUFACTURE, USE, OR SELL ANYTHING THAT IT MAY DESCRIBE. REPRODUCTION,DISCLOSURE, OR USE IN WHOLE OR IN PART WITHOUT THE SPECIFIC WRITTEN AUTHORIZATION OF CIENACORPORATION IS STRICTLY FORBIDDEN.

EVERY EFFORT HAS BEEN MADE TO ENSURE THAT THE INFORMATION IN THIS DOCUMENT IS COMPLETEAND ACCURATE AT THE TIME OF PRINTING; HOWEVER, THE INFORMATION CONTAINED IN THIS DOCUMENTIS SUBJECT TO CHANGE.

Copyright 2010 Ciena Corporation

Unpublished All Rights Reserved

The material contained in this document is also protected by copyright laws of the United States of America and othercountries. It may not be reproduced or distributed in any form by any means, altered in any fashion, or stored in a database or retrieval system, without express written permission of the Ciena Corporation.

Security

Ciena® cannot be responsible for unauthorized use of equipment and will not make allowance or credit forunauthorized use or access.

Contacting Ciena

For additional office locations and phone numbers, please visit the Ciena web site at www.ciena.com.

Corporate Headquarters 410-694-5700 or 800-921-1144 www.ciena.com

Customer Technical Support/Warranty

In North America 1-800-CIENA24 (243-6224) 410-865-4961 E-mail: [email protected]

In Europe, Middle East, and Africa

800-CIENA-24-7 (800-243-6224-7) +44-207-012-5508 E-mail: [email protected]

In Asia-Pacific 800-CIENA-24-7 (800-243-6224-7) +81-3-3248-4743 E-mail: [email protected]

Sales and General Information 410-694-5700 E-mail: [email protected]

In North America 410-694-5700 or 800-207-3714 E-mail: [email protected]

In Europe +44-207-012-5500 (UK) E-mail: [email protected]

In Asia +81-3-3248-4680 (Japan) E-mail: [email protected]

In India +91-124-434-0500 E-mail: [email protected]

In Latin America 011-5255-1719-0220 (Mexico City) E-mail: [email protected]

Training and Documentation

Training877-CIENA-TD (243-6283) or 410-865-8996 E-mail: [email protected]

Documentation 877-CIENA-TD (243-6283) or 410-694-8125 E-mail: [email protected]


IMPORTANT: PLEASE READ THIS LICENSE AGREEMENT ("AGREEMENT") CAREFULLY BEFOREINSTALLING OR USING CIENA CORPORATION ("Ciena") SOFTWARE, HARDWARE OR DOCUMENTATION(COLLECTIVELY, THE "EQUIPMENT").

BY INSTALLING OR USING THE EQUIPMENT, YOU ACKNOWLEDGE THAT YOU HAVE READ THISAGREEMENT AND AGREE TO BE BOUND BY ITS TERMS AND CONDITIONS.

1. Right to Use License; Restrictions. Subject to these terms, and the payment of all applicable license fees, Cienagrants to you, as end user, a non-exclusive license to use the Ciena software (the "Software") in object code formsolely in connection with, and as embedded within, the Equipment,. You shall have the right to use the Software solelyfor your own internal use and benefit. You may make one copy of the Software and documentation solely for backupand archival purpose, however you must reproduce and affix all copyright and other proprietary rights notices thatappear in or on the original. You may not, without Ciena's prior written consent, (i) sublicense, assign, sell, rent, lend,lease, transfer or otherwise distribute the Software; (ii) grant any rights in the Software or documentation not expresslyauthorized herein; (iii) modify the Software nor provide any third person the means to do the same; (iv) createderivative works, translate, disassemble, recompile, reverse engineer or attempt to obtain the source code of theSoftware in any way; or (v) alter, destroy, or otherwise remove any proprietary notices or labels on or embedded withinthe Software or documentation. You acknowledge that this license is subject to Section 365 of the U.S. BankruptcyCode and requires Ciena's consent to any assignment related to a bankruptcy proceeding. Sole title to the Softwareand documentation, to any derivative works, and to any associated patents and copyrights, remains with Ciena or itslicensors. Ciena reserves to itself and its licensors all rights in the Software and documentation not expressly grantedto you. You shall preserve intact any notice of copyright, trademark, logo, legend or other notice of ownership from anyoriginal or copies of the Software or documentation.

2. Audit: Upon Ciena's reasonable request, but not more frequently than annually without reasonable cause, youshall permit Ciena to audit the use of the Software at such times as may be mutually agreed upon to ensurecompliance with this Agreement.

3. Confidentiality. You agree that you will receive confidential or proprietary information ("Confidential Information")in connection with the purchase, deployment and use of the Equipment. You will not disclose Confidential Informationto any third party without prior written consent of Ciena, will use it only for purposes for which it was disclosed, use yourbest efforts to prevent and protect the contents of the Software from unauthorized disclosure or use, and must treat itwith the same degree of care as you do your own similar information, but with no less than reasonable care. Youacknowledge that the design and structure of the Software constitute trade secrets and/or copyrighted materials ofCiena and agree that the Equipment is Confidential Information for purposes of this Agreement.

4. U.S. Government Use. The Software is provided to the Government only with restricted rights and limited rights.Use, duplication, or disclosure by the Government is subject to restrictions set forth in FAR Sections 52-227-14 and52-227-19 or DFARS Section 52.227-7013(C)(1)(ii), as applicable. The Equipment and any accompanying technicaldata (collectively "Materials") are commercial within the meaning of applicable Federal acquisition regulations. TheseMaterials were developed fully at private expense. U.S. Government use of the Materials is restricted by thisAgreement, and all other U.S. Government use is prohibited. In accordance with FAR 12.212 and DFAR Supplement227.7202, software delivered to you is commercial computer software and the use of that software is further restrictedby this Agreement.

5. Term of License. This license is effective until terminated. Customer may terminate this license at any time bygiving written notice to Ciena [or] and destroying or erasing all copies of Software including any documentation. Cienamay terminate this Agreement and your license to the Software immediately by giving you written notice of terminationin the event that either (i) you breach any term or condition of this Agreement or (ii) you are wound up other thanvoluntarily for the purposes of amalgamation or reorganization, have a receiver appointed or enter into liquidation orbankruptcy or analogous process in your home country. Termination shall be without prejudice to any other rights orremedies Ciena may have. In the event of any termination you will have no right to keep or use the Software or anycopy of the Software for any purpose and you shall destroy and erase all copies of such Software in its possession orcontrol, and forward written certification to Ciena that all such copies of Software have been destroyed or erased.


6. Compliance with laws. You agree to comply with all applicable laws, including all import regulations, and to obtainall required licenses and permits related to installation and use of Equipment. Software, including technical data, issubject to U.S. export control laws, including the U.S. Export Administration Act and its associated regulations, andmay be subject to export or import regulations in other countries. Customer agrees to comply strictly with all suchregulations and acknowledges that it has the responsibility to obtain licenses to export, re-export, or import Software.

7. Limitation of Liability. ANY LIABILITY OF Ciena SHALL BE LIMITED IN THE AGGREGATE TO THE AMOUNTSPAID BY YOU FOR THE SOFTWARE. THIS LIMITATION APPLIES TO ALL CAUSES OF ACTION, INCLUDINGWITHOUT LIMITATION BREACH OF CONTRACT, BREACH OF WARRANTY, NEGLIGENCE, STRICT LIABILITY,MISREPRESENTATION AND OTHER TORTS. THE LIMITATIONS OF LIABILITY DESCRIBED IN THIS SECTIONALSO APPLY TO ANY THIRD-PARTY SUPPLIER OF Ciena. NEITHER Ciena NOR ANY OF ITS THIRD-PARTYSUPPLIERS SHALL BE LIABLE FOR ANY INJURY, LOSS OR DAMAGE, WHETHER INDIRECT, SPECIAL,INCIDENTAL OR CONSEQUENTIAL INCLUDING WITHOUT LIMITATION ANY LOST PROFITS, CONTRACTS,DATA OR PROGRAMS, AND THE COST OF RECOVERING SUCH DATA OR PROGRAMS, EVEN IF INFORMEDOF THE POSSIBILITY OF SUCH DAMAGES IN ADVANCE

8. General. Ciena may assign this Agreement to any Ciena affiliate or to a purchaser of the intellectual property rightsin the Software, but otherwise neither this Agreement nor any rights hereunder may be assigned nor duties delegatedby either party, and any attempt to do so will be void. This Agreement shall be governed by the laws of the State ofMaryland (without regard to the conflict of laws provisions) and shall be enforceable in the courts of Maryland. TheU.N. Convention on Contracts for the International Sale of Goods shall not apply hereto. This Agreement constitutesthe complete and exclusive statement of agreement between the parties relating to the license for the Software andsupersedes all proposals, communications, purchase orders, and prior agreements, verbal or written, between theparties. If any portion hereof is found to be void or unenforceable, the remaining provisions shall remain in full forceand effect.

3.

ContentsSoftware license 9

New in this release 13Features 14Co-existence of PLSB with LACP 14Other changes 16clear ports mstpstats command 16PLSB-MSTI 16

Introduction 17Acronyms 18

Layer 2 operational concepts 21VLANs 21

Port-based VLANs 22Policy-based VLANs 24Multihoming support 30Port types 30VLAN tagging and port types 31VLAN virtual router interfaces 35IP routing and VLANs 35Prevention of IP spoofing within a VLAN 35VLAN Loop Detection 36Multiple MAC Registration Protocol 37

Spanning tree protocols 37Spanning Tree Protocol 37Spanning Tree Protocol with PLSB 42Spanning Tree Protocol with PBT 43Multiple Spanning Tree Protocol 43

Link aggregation (MLT, SMLT, LACP) 47MultiLink Trunking (MLT) 48IEEE 802.3ad-based link aggregation 60Split MultiLink Trunking (SMLT) 69

Simple Loop Prevention Protocol 90SLPP and UNI Ports 92

Nortel Metro Ethernet Routing Switch 8600Configuration — VLANs, Spanning Tree, and Link Aggregation

NN46220-511 04.01 26 June 2009

Copyright © 2007-2009 Nortel Networks. All Rights Reserved.

.

4

SLPP general notes 93Considerations and limitations 94

VLAN implementation on the Metro Ethernet Routing Switch 8600 94VLAN rules 95MultiLink trunking and VLAN scalability 96

Configuring VLANs using Device Manager 99Displaying defined VLANs 99Configuring port-based VLANs 101

Creating a port-based VLAN 102Configuring an IP address for a VLAN 106

Configuring policy-based VLANs 107Creating a source IP subnet-based VLAN 108Creating a protocol-based VLAN 109Configuring user-defined protocol-based VLANs 111Creating a source MAC address-based VLAN 114

Managing a VLAN 119Changing VLAN port membership 120Configuring advanced VLAN features 120Configuring VLAN forwarding 123Configuring a VLAN to accept tagged or untagged frames 125Configuring Untagging Default VLAN on a Tagged Port 128Configuring MAC address auto-learning on a VLAN 129Modifying auto-learned MAC addresses 131Configuring VLAN Loop Detection 133Configuring directed broadcast on a VLAN 135

Managing VLAN bridging 137Configuring the forwarding database timeout 137Viewing the forwarding database for a specific VLAN 138Clearing learned MAC addresses from the forwarding database 140Configuring static forwarding 142MAC-layer bridge packet filtering 145Configuring static multicast 146Configuring a MAC-layer bridge filter 146Configuring the Global MAC filter 150

Configuring Enhanced Operation mode 151

Configuring spanning tree using Device Manager 155Choosing the spanning tree mode 155Configuring Spanning Tree Protocol 156

Creating a STG 157Editing an STG 161Adding ports to an STG 161Viewing the STG status 162Viewing STG ports 165


NN46220-511 04.01 26 June 2009


.

5

Enabling STP on a port 167Deleting an STG 168Configuring STG topology change detection 168

Configuring Multiple Spanning Tree Protocol 169Configuring MSTP globally 169Configuring CIST ports for MSTP 172Viewing statistics for the CIST ports 175Configuring MSTI bridges for MSTP 177Configuring MSTI ports for MSTP 178Viewing MSTI port statistics 180Viewing MSTI port notification 181

Configuring link aggregation using Device Manager 183Configuring link aggregation 183

Configuring LACP globally 184Adding a MultiLink/LACP trunk 185Adding ports to a multilink trunk 192Viewing multilink trunk interface statistics 193Viewing multilink trunk Ethernet error statistics 195Managing LACP information 198Configuring a port for LACP 201Viewing LACP statistics 206

Configuring Split Multilink Trunking 208Adding a MLT-based SMLT 208Viewing MLT-based SMLTs 210Adding ports to an MLT-based SMLT 211Configuring an IST multilink trunk 212Editing an IST 213Viewing IST statistics 214Configuring a single port split multilink trunk 216Viewing Single Port SMLTs 218Deleting a Single Port SMLT 219

Configuring Simple Loop Prevention Protocol 220Configuring SLPP globally 220Configuring the SLPP by VLAN 222Configuring the SLPP by port 223

Setting the sVLAN Ethertype using Device Manager 227SVLAN, Ether Type tab 228

Setting the sVLAN switch level using Device Manager 229

Configuring Simple Loop Prevention Protocol with DeviceManager 231SLPP, Ports tab fields 232


NN46220-511 04.01 26 June 2009


.

6

Configuring and managing VLANs using the CLI 233Roadmap of VLAN commands 233Configuring and managing a VLAN 237

Creating a VLAN 238Performing general VLAN operations 243Configuring VLAN parameters in the forwarding database 245Limiting MAC learning 250Adding or removing VLAN ports 251Adding or removing VLAN source MAC addresses 252Configuring Untagging Default VLAN on a Tagged Port 252Configuring Enhanced Operation mode 253Configuring VLAN Loop Detection 254Configuring spoof detection for a VLAN 258

Using the VLAN show commands 258Displaying general VLAN information 259Displaying forwarding database information 270Displaying forwarding database filters 271Displaying database status, MAC address, and QoS levels 272Displaying additional parameters 273Displaying ARP configurations 274Displaying VLAN information 275Displaying brouter port information 276Displaying IGMP switch operation information 277Displaying VLAN routing (IP) configuration 278Displaying port member status 278Displaying source MAC addresses 280

Using the show ports commands for VLANs 280Displaying port tagging information 281Displaying all port VLAN information 282

Using the VLAN IP commands 283Assigning an IP address to a VLAN 284

Configuring STGs using the CLI 287Roadmap of spanning tree commands 287Configuring the spanning tree protocol mode 290Configuring Spanning Tree Protocol 290

Configuring spanning tree group parameters 291Configuring STG port parameters 293Configuring topology change detection 295Using the show STG commands 297

Configuring Multiple Spanning Tree Protocol 306Configuring Multiple Spanning Tree Protocol 307Configuring MSTP region 308


NN46220-511 04.01 26 June 2009


.

7

Configuring MSTP CIST 309Configuring MSTP MSTI 310Mapping an MSTI to a VLAN 310Showing MSTP configurations 311Showing MSTP instance information 313Showing MSTP bridge statistics information 314Showing MSTP status 315Showing MSTP port information 316Configuring Ethernet MSTP CIST 318Configuring Ethernet MSTP MSTI 319

Configuring link aggregation using the CLI 321Roadmap of link aggregation commands 321Configuring link aggregation 325

Link aggregation commands 326Adding ports to a link aggregation group 327Removing ports from a link aggregation group 327Global LACP commands 328Aggregator configuration commands 329Port configuration commands 331LACP show commands 333Creating a split multilink trunk from an existing multilink trunk 338Creating an interswitch trunk 339Creating a single port split multilink trunk 343Configuring SMLT-on-Single-CPU 344

Using the MLT and SMLT show commands 344Displaying all multilink trunk information 345Displaying information about collision errors 348Displaying information about Ethernet errors 349Displaying multilink trunk status 350Displaying interswitch trunk status 350Displaying split multilink trunk status 351Displaying all ports configured for single port split multilink trunk 352Displaying a port configured for Single Port SMLT 353Displaying MLT statistics 353

Troubleshooting SMLT problems 354Troubleshooting IST problems 354Troubleshooting problems with a single user 357

Global MAC filtering 358

Configuring Simple Loop Prevention Protocol 361Configuring SLPP on a port 362Showing SLPP information 363Showing SLPP port information 364


NN46220-511 04.01 26 June 2009


.

8

Device Manager configuration examples 367SMLT and LACP configuration example 367Single Port SMLT and LACP configuration example 371

CLI configuration examples 375MultiLink Trunking configuration example 376Single Port SMLT with SLPP configuration example 377SMLT triangle with loop detection configuration example 379Square SMLT configuration example 386Full mesh SMLT configuration example 390SMLT and VRRP configuration example 394SMLT and multicast configuration example 397Triangle SMLT and LACP configuration example 398Single Port SMLT and LACP configuration example 401LACP-based MLT for UNI configuration example 404LACP-based MLT for NNI configuration example 405Multiple Spanning Tree Protocol configuration example 406Dual home UNI and MSTP configuration example 413

Tap and OctaPID assignment (Release 3.x feature set) 419


NN46220-511 04.01 26 June 2009


.

9.

Software licenseThis section contains the Nortel Networks software license.

Nortel Networks Inc. software license agreementThis Software License Agreement ("License Agreement") is betweenyou, the end-user ("Customer") and Nortel Networks Corporation andits subsidiaries and affiliates ("Nortel Networks"). PLEASE READ THEFOLLOWING CAREFULLY. YOU MUST ACCEPT THESE LICENSETERMS IN ORDER TO DOWNLOAD AND/OR USE THE SOFTWARE.USE OF THE SOFTWARE CONSTITUTES YOUR ACCEPTANCE OFTHIS LICENSE AGREEMENT. If you do not accept these terms andconditions, return the Software, unused and in the original shippingcontainer, within 30 days of purchase to obtain a credit for the fullpurchase price.

"Software" is owned or licensed by Nortel Networks, its parent or one ofits subsidiaries or affiliates, and is copyrighted and licensed, not sold.Software consists of machine-readable instructions, its components, data,audio-visual content (such as images, text, recordings or pictures) andrelated licensed materials including all whole or partial copies. NortelNetworks grants you a license to use the Software only in the countrywhere you acquired the Software. You obtain no rights other than thosegranted to you under this License Agreement. You are responsible for theselection of the Software and for the installation of, use of, and resultsobtained from the Software.

1. Licensed Use of Software. Nortel Networks grants Customer anonexclusive license to use a copy of the Software on only one machineat any one time or to the extent of the activation or authorized usage level,whichever is applicable. To the extent Software is furnished for use withdesignated hardware or Customer furnished equipment ("CFE"), Customeris granted a nonexclusive license to use Software only on such hardwareor CFE, as applicable. Software contains trade secrets and Customeragrees to treat Software as confidential information using the same careand discretion Customer uses with its own similar information that it doesnot wish to disclose, publish or disseminate. Customer will ensure thatanyone who uses the Software does so only in compliance with the terms


NN46220-511 04.01 26 June 2009


.

10 Software license

of this Agreement. Customer shall not a) use, copy, modify, transferor distribute the Software except as expressly authorized; b) reverseassemble, reverse compile, reverse engineer or otherwise translate theSoftware; c) create derivative works or modifications unless expresslyauthorized; or d) sublicense, rent or lease the Software. Licensors ofintellectual property to Nortel Networks are beneficiaries of this provision.Upon termination or breach of the license by Customer or in the eventdesignated hardware or CFE is no longer in use, Customer will promptlyreturn the Software to Nortel Networks or certify its destruction. NortelNetworks may audit by remote polling or other reasonable means todetermine Customer’s Software activation or usage levels. If suppliers ofthird party software included in Software require Nortel Networks to includeadditional or different terms, Customer agrees to abide by such termsprovided by Nortel Networks with respect to such third party software.

2. Warranty. Except as may be otherwise expressly agreed to inwriting between Nortel Networks and Customer, Software is provided"AS IS" without any warranties (conditions) of any kind. NORTELNETWORKS DISCLAIMS ALL WARRANTIES (CONDITIONS) FOR THESOFTWARE, EITHER EXPRESS OR IMPLIED, INCLUDING, BUT NOTLIMITED TO THE IMPLIED WARRANTIES OF MERCHANTABILITY ANDFITNESS FOR A PARTICULAR PURPOSE AND ANY WARRANTY OFNON-INFRINGEMENT. Nortel Networks is not obligated to provide supportof any kind for the Software. Some jurisdictions do not allow exclusionof implied warranties, and, in such event, the above exclusions may notapply.

3. Limitation of Remedies. IN NO EVENT SHALL NORTELNETWORKS OR ITS AGENTS OR SUPPLIERS BE LIABLE FOR ANYOF THE FOLLOWING: a) DAMAGES BASED ON ANY THIRD PARTYCLAIM; b) LOSS OF, OR DAMAGE TO, CUSTOMER’S RECORDS,FILES OR DATA; OR c) DIRECT, INDIRECT, SPECIAL, INCIDENTAL,PUNITIVE, OR CONSEQUENTIAL DAMAGES (INCLUDING LOSTPROFITS OR SAVINGS), WHETHER IN CONTRACT, TORT OROTHERWISE (INCLUDING NEGLIGENCE) ARISING OUT OFYOUR USE OF THE SOFTWARE, EVEN IF NORTEL NETWORKS,ITS AGENTS OR SUPPLIERS HAVE BEEN ADVISED OF THEIRPOSSIBILITY. The forgoing limitations of remedies also apply to anydeveloper and/or supplier of the Software. Such developer and/or supplieris an intended beneficiary of this Section. Some jurisdictions do not allowthese limitations or exclusions and, in such event, they may not apply.

4. General

1. If Customer is the United States Government, the following paragraphshall apply: All Nortel Networks Software available under this LicenseAgreement is commercial computer software and commercial computer


NN46220-511 04.01 26 June 2009


.

Nortel Networks Inc. software license agreement 11

software documentation and, in the event Software is licensed foror on behalf of the United States Government, the respective rightsto the software and software documentation are governed by NortelNetworks standard commercial license in accordance with U.S. FederalRegulations at 48 C.F.R. Sections 12.212 (for non-DoD entities) and48 C.F.R. 227.7202 (for DoD entities).

2. Customer may terminate the license at any time. Nortel Networksmay terminate the license if Customer fails to comply with the termsand conditions of this license. In either event, upon termination,Customer must either return the Software to Nortel Networks or certifyits destruction.

3. Customer is responsible for payment of any taxes, including personalproperty taxes, resulting from Customer’s use of the Software.Customer agrees to comply with all applicable laws including allapplicable export and import laws and regulations.

4. Neither party may bring an action, regardless of form, more than twoyears after the cause of the action arose.

5. The terms and conditions of this License Agreement form the completeand exclusive agreement between Customer and Nortel Networks.

6. This License Agreement is governed by the laws of the country inwhich Customer acquires the Software. If the Software is acquired inthe United States, then this License Agreement is governed by thelaws of the state of New York.


NN46220-511 04.01 26 June 2009


.

12 Software license


NN46220-511 04.01 26 June 2009


.

13.

New in this releaseThe following sections detail what’s new in Nortel Metro EthernetRouting Switch 8600 Configuration — VLANs, Spanning Tree, and LinkAggregation (NN46220-511) for release 6.0.

• “Features” (page 14)

• “Other changes” (page 16)


NN46220-511 04.01 26 June 2009


.

14 New in this release

Features

See the following sections for information about feature changes:

• “LACP enhancements” (page 14)

• “SLPP enhancements” (page 14)

• “Co-existence of PLSB with LACP” (page 14)

LACP enhancementsThe DFO feature includes Link Aggregation Control Protocol (LACP)enhancements. The behavior of LACP-enabled MLTs is changed so thatyou can:

• add and remove ports from an LACP-enabled MLT statically

• add and remove B-VLAN/ACL filters

This feature is applicable on both UNI and NNI MLT/LAG, on R and RCmodules.

The current LACP behavior is not changed; the ports can still be addedand removed dynamically.

If communication of the Link Aggregation Control Protocol data unit(LACPDU) on the port with peer node does not agree, traffic is nottransmitted and accepted on this port. In this condition, the port is in anSTG-disabled state.

For more information, see “LACP and MLT” (page 64) and “LACP keys”(page 66).

SLPP enhancementsYou can specify the UNI ports added under the SLPP global configurationand view the total number of SLPP packets received on the port. Thisrelease includes additional enhancements to show packet rx counts andclear commands for the packet rx. For more information, see “Simple LoopPrevention Protocol” (page 90), “Configuring SLPP globally” (page 220),and “Configuring the SLPP by port” (page 223).

Co-existence of PLSB with LACPThis release supports PLSB for LACP-based MLT-UNI, or co-existence ofPLSB with LACP. However, it does not support PLSB over LACP-basedMLT-NNI or LACP-based RCT-MLT with PLSB VLAN. PLSB can co-existon the same node as LACP-based non-PLSB MLT-NNIs.


NN46220-511 04.01 26 June 2009


.

Co-existence of PLSB with LACP 15

For more information, see “Link aggregation (MLT, SMLT, LACP)” (page47)


NN46220-511 04.01 26 June 2009


.

16 New in this release

Other changes

See the following section for details and locations of the changes madeto this document.

clear ports mstpstats command• Added "clear ports mstpstats" command information. See “Roadmap

of spanning tree commands” (page 287) and Attention Box that followsthe Table in “Showing MSTP port information” (page 316).

ConfiguredMembers• Updated “MultiLink/LACP Trunks tab fields” (page 188) to include

ConfiguredMembers details.

MLT display• Updated paragraph in “LACP and MLT” (page 64) and show mlt info

sample output in “Displaying multilink trunk status” (page 350).

PLSB-MSTI• Updated the screen capture in “Configuring MSTP globally” (page 169).

• Updated Table 27 "MSTP, Globals fields" (page 171).


NN46220-511 04.01 26 June 2009


.

17.

IntroductionThis guide describes how to configure VLANs, spanning tree, and linkaggregation on the Nortel Metro Ethernet Routing Switch 8600 (MERS8600).

PrerequisitesThis guide is intended for network administrators with the followingbackground:

• Basic knowledge of networks, Ethernet bridging, and IP routing

• Familiarity with networking concepts and terminology

• Experience with graphical user interfaces (GUI)

• Basic knowledge of network topologies

• Basic knowledge of Provider Backbone Bridging (PBB) concepts.

For more information, see Nortel Metro Ethernet Routing Switch 8600Fundamentals (NN46220-100).

Ensure that you are running the latest version of the Metro EthernetRouting Switch 8600 Software Release 6.0 and Device Manager software.For information about upgrading the Metro Ethernet Routing Switch8600 Software Release 6.0 and Device Manager, see Nortel MetroEthernet Services Routing Switch 8600 Upgrades — Software Release 6.0(NN46220-402) for your version of the Metro Ethernet Routing Switch.

Navigation• “Layer 2 operational concepts” (page 21)

• “Configuring VLANs using Device Manager” (page 99)

• “Configuring spanning tree using Device Manager” (page 155)

• “Configuring link aggregation using Device Manager” (page 183)

• “Setting the sVLAN Ethertype using Device Manager” (page 227)

• “Setting the sVLAN switch level using Device Manager” (page 229)


NN46220-511 04.01 26 June 2009


.

18 Introduction

• “Configuring and managing VLANs using the CLI” (page 233)

• “Configuring link aggregation using the CLI” (page 321)

• “Device Manager configuration examples” (page 367)

• “CLI configuration examples” (page 375)

AcronymsThis guide uses the following acronyms:

ARP Address Resolution Protocol

ATM Asynchronous Transfer Mode

BGP Border Gateway Protocol

BPDU bridge protocol data unit

CIST Common and Internal Spanning Tree

CLI command line interface

CPU Central Processing Unit

DF designated forwarding

DMLT Distributed MultiLink Trunking

DSAP Destination Service Access Point

ES Extranet Switch

FCS Frame Check Sequence

FDB forwarding database

GbE Gigabit Ethernet

ICMP Internet Control Message Protocol

I/O input/output

IEEE Institute of Electrical and Electronics Engineers

IGMP Internet Group Management Protocol

IGP interior gateway protocol

IP Internet Protocol

IPX Internetwork Packet Exchange

ISP Internet Service Provider

IST Internal Spanning Tree

IST InterSwitch Trunking

LACP Link Aggregation Control Protocol

LACPDU Link Aggregation Control Protocol data unit

LAG link aggregation group


NN46220-511 04.01 26 June 2009


.

Acronyms 19

LLC Logical Link Control

MAC Media Access Control

MIB management information base

MLT MultiLink Trunking

MSTI Multiple Spanning Tree Instance

MSTP Multiple Spanning Tree Protocol

NIC network interface card

NLB Network Load Balancer

NNI network-to-network interface

OSI Open Systems Interconnect

OSPF Open Shortest Path First

PCAP Packet Capture Tool

PID protocol identifier

PDU protocol data unit

POS Packet over SONET

PPP Point-to-Point Protocol

PPPoE Point-to-Point Protocol over Ethernet

PVST Per-VLAN Spanning Tree

QoS Quality of Service

RARP Reverse Address Resolution Protocol

RIP Routing Information Protocol

RF root forwarding

RSMLT Routed Split MultiLink Trunking

SLPP Simple Loop Prevention Protocol

SMLT Split MultiLink Trunking

SNA Systems Network Architecture

SNAP Sub-Network Access Protocol

SNMP Simple Network Management Protocol

SSAP Source Service Access Point

SST single spanning tree

STG spanning tree group

STP Spanning Tree Protocol

sVLAN stacked virtual local area network

TCN topology change notification

UNI user-to-network interface


NN46220-511 04.01 26 June 2009


.

20 Introduction

VLACP Virtual Link Aggregation Control Protocol

VLAN virtual local area network

XOR exclusive OR


NN46220-511 04.01 26 June 2009


.

21.

Layer 2 operational conceptsThis section describes Layer 2 operational concepts and featuressupported on your Metro Ethernet Routing Switch.

See “Device Manager configuration examples” (page 367) and “CLIconfiguration examples” (page 375) for configuration examples, includingcommand line interface (CLI) commands, for concepts described in thissection.

This section covers the following topics:

• “VLANs” (page 21)

• “Spanning tree protocols” (page 37)

• “Link aggregation (MLT, SMLT, LACP)” (page 47)

• “Simple Loop Prevention Protocol” (page 90)

VLANsUsing a virtual LAN (VLAN), you can divide your LAN into smaller groupswithout interfering with the physical network. VLAN practical applicationsinclude the following:

• You can create VLANs, or workgroups, for common interest groups.

• You can create VLANs, or workgroups, for specific types of networktraffic.

• You can add, move, or delete members from these workgroups withoutmaking any physical changes to the network.

By dividing the network into separate VLANs, you can create separatebroadcast domains. This arrangement conserves bandwidth, especiallyin networks supporting broadcast and multicast applications that floodthe network with traffic. A VLAN workgroup can include members from anumber of dispersed physical segments on the network, improving trafficflow between them.


NN46220-511 04.01 26 June 2009


.

22 Layer 2 operational concepts

The Metro Ethernet Routing Switch 8600 Software Release 6.0 performsthe Layer 2 switching functions necessary to transmit information withinVLANs, as well as the Layer 3 routing functions necessary for VLANsto communicate with one another. A VLAN can be defined for a singleswitch or it can span multiple switches. A port can be a member of multipleVLANs.

A port-based VLAN is the only type of VLAN provisioning supported forProvider Backbone Bridging (PBB) and Provider Backbone Transport(PBT) service. Port-based VLANs are known as B-VLANs or PBT VLANs.

For information about configuring VLANs, see “Configuring VLANs usingDevice Manager” (page 99) and “Configuring and managing VLANs usingthe CLI” (page 233).

This section includes the following topics:

• “Port-based VLANs” (page 22)

• “Policy-based VLANs” (page 24)

• “Multihoming support” (page 30)

• “Port types” (page 30)

• “VLAN tagging and port types” (page 31)

• “VLAN virtual router interfaces” (page 35)

• “IP routing and VLANs” (page 35)

• “VLAN rules” (page 95)

• “MultiLink trunking and VLAN scalability” (page 96)

• “Prevention of IP spoofing within a VLAN” (page 35)

• “VLAN Loop Detection” (page 36)

• “Multiple MAC Registration Protocol” (page 37)

Port-based VLANsA port-based VLAN is a VLAN in which the ports are explicitly configuredto be in the VLAN. When creating a port-based VLAN on a switch, youassign a VLAN identification number (VLAN ID) and specify the ports thatbelong to the VLAN. The VLAN ID is used to coordinate VLANs acrossmultiple switches.

A port-based VLAN is the only type of VLAN provisioning supported forProvider Backbone Bridging (PBB) services running on B-VLANs, PBTVLANs, or PLSB VLANs. Port-based VLANs are known as B-VLANs, PBTVLANs, or PLSB VLANs.


NN46220-511 04.01 26 June 2009


.

VLANs 23

A port interface can be set to either UNI, NNI or silent. Silent is thedefault and, as a security feature, does not allow any VLANs or UNI tobe assigned to the port until it is changed to UNI or NNI. When a port isset to UNI, the Encapsulated Virtual Private Network (EVPN) conceptapplies; the port is tied to an end-point, which is tied to an I-SID, whichis either tied to a B-VLAN, PLSB-VLAN or PBT-VLAN, depending on thetransport method selected for that I-SID. The B-VLAN, PLSB-VLAN andPBT-VLAN can only be port-based VLANs. When a port is set to NNI, itcan be assigned to any VLAN type.

NNI trunk ports must be assigned as needed. Rings must be added to allB-VLANs that the UNIs are assigned to after the ring ID is created andports are added to the ring. B-VLANs are assigned to TDIs and I-SIDs;UNIs are assigned to TDIs or I-SIDs.

EVPN applies to a PBB encapsulation of Layer 2 frames entering the port.These encapsulated frames are then transported across the network andthe encapsulation is removed to form a Virtual Private Network (VPN).When encapsulated, EVPN traffic is transported over normal ports throughthe network.

The example in Figure 1 "Port-based VLAN" (page 24) shows twoport-based VLANs: one for the marketing department, and one for thesales department. Ports are assigned to each port-based VLAN. A changein the sales area can move the sales representative at port 3/1 (the firstport in the input/output (I/O) module in chassis slot 3) to the marketingdepartment without moving cables. With a port-based VLAN, you onlyneed to indicate in Device Manager or the CLI that port 3/1 in the salesVLAN now is a member of the marketing VLAN.


NN46220-511 04.01 26 June 2009


.


Figure 1Port-based VLAN

Policy-based VLANsA policy-based VLAN consists of ports that are dynamically added to theVLAN on the basis of the traffic coming into the port.

ATTENTIONThe policy-based VLANs are only supported for non EVPN service that is,B-VLAN, PBT-VLAN, PLSB-VLAN and MMRP-VLANs cannot belong to thesetypes of VLANs and can only be port-based VLANs.


• “Port membership types” (page 24)

• “Protocol-based VLANs” (page 26)

• “User-defined protocol-based VLANs” (page 27)

• “MAC address-based VLANs” (page 28)

• “IP subnet-based VLANs” (page 29)

Port membership typesIn a policy-based VLAN, a port can be designated as always a member ornever a member of the VLAN describing the port membership types.

In addition, you can designate a port as a potential member of the VLANon the Metro Ethernet Routing Switch 8600. When a port is designatedas a potential member of the VLAN, and the incoming traffic matches


NN46220-511 04.01 26 June 2009


.

VLANs 25

the policy, the port is dynamically added to the VLAN. Potential memberports that join the VLAN are removed, timed out from the VLAN when thetimeout (aging time) period of that VLAN expires.

Port membership in a VLAN is determined by the traffic coming into theport. Nortel recommends that you designate at least some ports as alwaysa member of the VLAN. If a server or router connects to a port, thendesignate that port as always a member of a VLAN. If a server connectsto a port that is only a potential member and the server sends very littletraffic, a client fails to reach the server if the server port has timed out ofthe VLAN.

A port can belong to one port-based VLAN and many policy-based VLANs.

Table 1 "Port membership types for policy-based VLANs" (page25) describes port membership types for policy-based VLANs.

Table 1Port membership types for policy-based VLANs

Membership type Description

Static

(always a member)

Static members are always active members of theVLAN after they are configured as belonging to thatVLAN. This membership type is used in policy-basedand port-based VLANs.

• In policy-based VLANs, the tagged ports are usuallyconfigured as static members.

• In port-based VLANs, all ports are always staticmembers.

Not allowed to join

(never a member)

Ports of this type are not allowed to join the VLAN.

Table 2 "Supported VLAN types for NNI and Layer 2 ports" (page 25) listssupported policy-based VLANs.

Table 2Supported VLAN types for NNI and Layer 2 ports

VLAN type Metro Ethernet Routing Switch 8600

Protocol-based supported

User-defined protocol-based supported

MAC address-based supported

IP subnet-based supported


NN46220-511 04.01 26 June 2009


.


Protocol-based VLANsProtocol-based VLANs are an effective way to segment your networkinto broadcast domains according to the network protocols in use. Trafficgenerated by any network protocol—Appletalk, Point-to-Point Protocol overEthernet (PPPoE)—can be automatically confined to its own VLAN.

All ports within a protocol-based VLAN must be in the same port-basedVLAN. However, the same port within a port-based VLAN can belong tomultiple protocol-based VLANs. Port tagging is not required for a port tobe a member of multiple protocol-based VLANs.

The Metro Ethernet Routing Switch 8600 supports the followingprotocol-based VLANs:

• IP version 4 (ip)

• AppleTalk on Ethernet Type 2 and Ethernet SNAP frames (AppleTalk)

• DEC LAT Protocol (decLat)

• Other DEC protocols (decOther)

• IBM SNA on IEEE 802.2 frames (sna802dot2)

• IBM SNA on Ethernet Type 2 frames (snaEthernet2)

• NetBIOS Protocol (netBIOS)

• Xerox XNS (xns)

• Banyan VINES (vines)

• IP version 6 (ipv6)

• Reverse Address Resolution Protocol (RARP)

• Point-to-Point Protocol over Ethernet (PPPoE)

• User-defined protocols

Example: PPPoE protocol-based VLAN

With PPPoE, you can connect multiple computers on Ethernet to aremote site through a device, such as a modem, so that multiple userscan share a common line connection to the Internet. PPPoE combinesthe Point-to-Point Protocol (PPP), commonly used in dial-up connections,with the Ethernet protocol, which supports multiple users in a local areanetwork (LAN) by encapsulating the PPP frame within an Ethernet frame.

PPPoE occurs in two stages—a discovery stage and a PPP session stage.The Ether_Type field in the Ethernet frame identifies the stage:


NN46220-511 04.01 26 June 2009


.

VLANs 27

• The discovery stage uses 0x8863 Ether_Type

• The session stage uses 0x8864 Ether_Type

In Figure 2 "PPPoE and IP configuration" (page 27), VLAN 2 is aprotocol-based VLAN that transports PPPoE traffic to the Internet ServiceProvider (ISP) network. The traffic to the ISP is bridged.

IP traffic can also be routed to the LAN using port-based VLANs, IPprotocol-based VLANs, or IP subnet-based VLANs.

Figure 2PPPoE and IP configuration

User-defined protocol-based VLANsYou can create user-defined protocol-based VLANs to support networkswith non-standard protocols. For user-defined protocol-based VLANs, youcan specify the Protocol Identifier (PID) for the VLAN. Frames that matchthe specified PID for the following are assigned to that user-defined VLAN:

• The ethertype for Ethernet type 2 frames

• The PID in Ethernet Sub-Network Access Protocol (SNAP) frames


NN46220-511 04.01 26 June 2009


.


Table 3 "PIDs that cannot be used for user-defined protocol-based VLANs"(page 28) lists reserved, predefined policy-based PIDs that cannot be usedas user-defined PIDs.

Table 3PIDs that cannot be used for user-defined protocol-based VLANs

PID (hex) Description

04xx, xx04 sna802.2

F0xx, xxF0 netBIOS

0000-05DC Overlaps with 802.3 frame length

0600, 0807 xns

0BAD VINES

4242 IEEE 802.1d BPDUs

6000-6003, 6005-6009 decOther

6004 decLat

0800, 0806 ip

8035 RARP

809B, 80F3 AppleTalk

8100 Reserved by IEEE 802.1Q for tagged frames

80D5 snaEthernet2

86DD ipv6

8808 IEEE 802.3x pause frames

9000 Used by diagnostic loopback frames

8863, 8864 PPPoE

MAC address-based VLANsAs with all policy-based VLANs, using source media access control (MAC)address VLANs allows Metro Ethernet Routing Switch 8600 modules toassociate frames with a VLAN based on the frame content. With sourceMAC-based VLANs, a frame is associated with a VLAN if the sourceMAC address is one of the MAC addresses explicitly associated with theVLAN. To create a source MAC-based VLAN, you add the MAC addressto a list of MAC addresses that constitutes the VLAN. However, becauseit is necessary to explicitly associate MAC addresses with a sourceMAC-based VLAN, the administrative overhead can be quite high.

Use source MAC-based VLANs when you want to enforce a MAC levelsecurity scheme to differentiate groups of users. For example, in auniversity environment, the students are part of a student VLAN withcertain services and access privileges, and the faculty are part of a sourceMAC-based VLAN with faculty services and access privileges. Therefore,


NN46220-511 04.01 26 June 2009


.

VLANs 29

a student and a faculty member can plug into the same port, but haveaccess to a different range of services. To provide the correct servicesthroughout the campus, the source MAC-based VLAN must be definedon Metro Ethernet Routing Switch 8600 devices throughout the campus,which entails administrative overhead.

When a source MAC VLAN is created, not all of the port members of thespanning tree group (STG) are automatically made potential members ofthe VLAN by default.

The source MAC VLAN must have static port members on either theaccess or trunk switch for source MAC VLANS to explicitly associate theMAC address with the source MAC VLAN. If the static port members arenot set, then any source MAC address gains access to the network.

IP subnet-based VLANsMetro Ethernet Routing Switch 8600 modules support policy-basedVLANs based on IP subnets. You can assign access ports to multiplesubnet-based VLANs. A frame’s membership in a subnet-based VLAN isbased on the IP source address associated with a mask. Subnet-basedVLANs are optionally routable. Using source IP subnet-based VLANs,multiple workstations on a single port can belong to different subnets,similar to multinetting.

You cannot use IP subnet-based VLANs on segments that act as a transitnetwork.

Figure 3 "Incorrect use of an IP subnet-based VLAN" (page 30) shows twoexamples of the incorrect use of IP subnet-based VLANs that result intraffic loss. In the IP unicast routing example, the host on 172.100.10.2sends traffic to switch 2 (172.100.10.1) destined for the router in switch 1(192.168.1.1). Switch 2 attempts to route the IP traffic, but that traffic doesnot arrive at the router in switch 1. Switch 1 will not assign this frame to IPsubnet-based VLAN 2 because the IP address of the traffic source doesnot match the IP subnet assigned to VLAN 2. If the access link in VLAN 2which connects switches 1 and 2 is a tagged link, the traffic is associatedwith the VLAN tag, not the IP address, and is forwarded correctly to switch1.

In the IP multicast routing example, the multicast stream is on an accesslink that is part of IP subnet-based VLAN 2. If the source IP address inthe multicast data packets received on the access port is not within thesubnet of VLAN 2 (a likely scenario), the multicast stream will not reachthe multicast router (MR).


NN46220-511 04.01 26 June 2009


.


Figure 3Incorrect use of an IP subnet-based VLAN

Multihoming supportUsing the multihoming feature, the Metro Ethernet Routing Switch 8600can support clients or servers that have multiple IPs addresses associatedwith a single MAC address. Multihomed hosts can be connected toport-based VLANs. All other types of VLANs are not supported.

The IP addresses associated with a single MAC address on a host mustbe in the same IP subnet. Multihomed hosts with up to 16 IP addresses foreach MAC address are supported on the Metro Ethernet Routing Switch8600.

Port typesA port interface type can be set to either UNI, Normal or Silent. Silent isthe default and, as a security feature, does not allow any VLANs or UNI tobe assigned to the port until it is changed to UNI or normal.

When a port interface type is set to UNI, the EVPN concept applies. Theport must be tied to an end-point to transport traffic. This is a port thatnormally faces the customer equipment.


NN46220-511 04.01 26 June 2009


.

VLANs 31

When a port interface type is set to normal, it can be used for regular L2traffic (no EVPN) and use any VLAN type, or it can be used as an NNIinterface that has B-VLAN, PLSB-VLAN or PBT-VLAN, which can only beport-based VLANs. This is a port that normally faces the service providernetwork.

When a switch boots with the factory default configuration, the ports donot belong to a VLAN (they belong to NULL VLAN) and the port type isset to "silent" (it will be part of NULL VLAN and will not process BPDUand topology packets). The interface-type value must be set to "UNI" forthe port before configuring a UNI, I-SID endpoint, MLT endpoint, andCUST-IP-VLAN. For a non-UNI port, the interface-type must be set to"normal" before adding a port to a VLAN. Change the interface-type for theport using the following command.

config ethernet<slot/port>interface-type<normal:silent:uni>

IP VLAN management of the Ethernet Services Units (ESU) issupported. IP VLAN traffic flow from and to all Ethernet Services Units issingle-direction, towards the primary ring port. Virtual Router RedundancyProtocol (VRRP) is enabled on the service provider (SP) VLAN that theDual Home Ring port is part of. This provides a mechanism to have thesame IP gateway for Ethernet Services Unit access ports.

VLAN tagging and port typesThe Metro Ethernet Routing Switch 8600 supports the IEEE 802.1Qspecification for tagging frames and coordinating VLANs across multipleswitches.

VLAN tagging is required for NNI and UNI ports when using the portsfor EVPN services. Port types can be of three types: UNI, normal, andsilent. By default, port type is untagged and silent to prevent traffic fromforwarding.

Figure 4 "VLAN tag insertion" (page 32) shows how an additional fouroctet (tag) header is inserted in a frame after the source address andbefore the frame type. The tag contains the VLAN ID associated with theframe.


NN46220-511 04.01 26 June 2009


.


Figure 4VLAN tag insertion

802.1Q tagged portsTagging a frame adds four octets to a frame, making it bigger than thetraditional maximum frame size. These frames are sometimes referred toas baby giant frames. If a device does not support IEEE 802.1Q tagging,it can have problems interpreting tagged frames and receiving baby giantframes.

On the Metro Ethernet Routing Switch 8600, whether or not tagged framesare sent or received depends on what you configure at the port level.Tagging is set as true or false for the port and is applied to all VLANs onthat port.

When you enable tagging on an untagged port, the previous portconfiguration of VLANs, STGs, and multilink trunking (MLT) is lost. Inaddition, the port resets and runs Spanning Tree Protocol. This processbreaks connectivity while the protocol proceeds through the normalblocking and learning stages before the port enters the forwarding state.

A port with tagging enabled sends frames explicitly tagged with a VLAN ID.Tagged ports are typically used to multiplex traffic belonging to multipleVLANs to other IEEE 802.1Q-compliant devices.


NN46220-511 04.01 26 June 2009


.

VLANs 33

If you disable tagging on a port, it does not send tagged frames. Anon-tagged port connects an Metro Ethernet Routing Switch to devicesthat do not support IEEE 802.1Q tagging. If a tagged frame is forwardedto a port with tagging set to false, the Metro Ethernet Routing Switchremoves the tag from the frame before sending it to the port.

Treatment of tagged and untagged framesThe Metro Ethernet Routing Switch 8600 associates a frame with aVLAN based on the data content of the frame and the configuration ofthe destination port. The treatment of the frame depends on whether it istagged or untagged.

If a tagged frame is received on a tagged port with a VLAN ID specified inthe tag, the Metro Ethernet Routing Switch 8600 directs it to that VLAN ifthe VLAN is present. For tagged frames received on an untagged port,you can configure that port to either discard the frame or accept it. Thediscarding of tagged frames on an untagged port is not applicable for theport-based VLAN. If you choose not to discard tagged frames, the MetroEthernet Routing Switch 8600 sends the frame to the VLAN identified inthe frame tag.

For untagged frames, VLAN membership is implied from the content ofthe frame itself. For untagged frames received on a tagged port, you canconfigure the port to either discard or accept the frame. If you configure atagged port to accept untagged frames, the port must be assigned to aport-based VLAN in spanning tree group 1 (STG1).

The frame is forwarded based on the VLAN on which the frame isreceived, and on the forwarding options available for that VLAN. The MetroEthernet Routing Switch 8600 tries to associate untagged frames with aVLAN. If a port is not tagged, it receives the default tagging.

If the frame meets none of the criteria listed, it is discarded.

Untagging Default VLAN on a Tagged Port featureThis feature provides the ability to connect both an IP phone and a PC to asingle port of a Metro Ethernet Routing Switch 8600.

The default VLAN feature is only applicable to NNI ports when the NNI isnot associated with any PBB or PBT interfaces; it is not applicable to UNIports on PBB and PBT.

Most IP phones ship with an embedded three port switch, and trafficcoming from the phone is generally tagged (VLAN ID configured staticallyor remotely). However, the traffic originating from a PC is usually untaggedtraffic and must be separated from the IP phone traffic. This separationensures that broadcast traffic from the PC does not impact voice quality.


NN46220-511 04.01 26 June 2009


.


In the case of the Metro Ethernet Routing Switch, when an IP phone isattached to an untagged port and configured into an IP subnet-basedVLAN, it can fail to register with a remote Internet Telephony Gateway (orequivalent device) dependent on the netmask of the destination IP address(Call Server subnet).

Figure 5Network with IP phone and PC

In Figure 5 "Network with IP phone and PC" (page 34), IP phones and PCscoexist on the same port due to the use of an embedded IP Phone Layer2 switch. In this scenario, the port is configured to be untagged and isa member of two IP subnet-based VLANs. In this network configuration,under certain conditions, packets from the IP phone are not routed andtherefore are unable to reach their designated Call Server to register.

The Untagging Default VLAN on a Tagged Port feature separatesuntagged packets originating from a PC from the tagged packetsoriginating from the IP phone.

You can configure the switch to send untagged packets for the defaultVLAN on a tagged port. After you configure this option, all the packetssent on a tagged port for the default VLAN are untagged packets.

When a port belongs to multiple VLANs, and the port is removed fromthe current default VLAN, the lowest VLAN by index (among the VLANsof which the port is a member) is made the default VLAN. In this case,packets for new default VLAN are sent untagged.

To configure this feature using the CLI, see “Configuring VLAN LoopDetection” (page 254). To configure this feature using Device Manager,see “Configuring Untagging Default VLAN on a Tagged Port” (page 128).


NN46220-511 04.01 26 June 2009


.

VLANs 35

VLAN virtual router interfacesVirtual router interfaces correspond to routing on a virtual port that isassociated with a VLAN. This type of routing is the routing of IP traffic toand from a VLAN. Because a given port can belong to multiple VLANs(some of which are configured for routing on the switch and some ofwhich are not), there is no longer a one-to-one correspondence betweenthe physical port and the router interface. For VLAN routing, the routerinterface for the VLAN is called a virtual router interface because the IPaddress is assigned to an interface on the routing entity in the switch. Thisinitial interface has a one-to-one correspondence with a VLAN on anygiven switch.

VLAN routing is applicable to customer IP_VLAN UNIs and is used tomanage devices attached to UNIs or rings, including Ethernet ServicesUnits within the ring. It is not applicable to PBB and PBT B-VLANs.

IP routing and VLANsMetro Ethernet Routing Switch 8600 modules support IP routing onport-based VLANs only. IP routing can be applied to a UNI for IPmanagement.

IP routing is not supported on VLANs based on other protocols, includinguser-defined protocol-based VLANs.

Prevention of IP spoofing within a VLANYou can prevent VLAN logical IP spoofing by blocking the external useof the switch IP address. A configurable option is provided, on a per-portbasis, which detects a duplicate IP address (that is, an address that is thesame as the switch VLAN IP address) and blocks all packets with a sourceor destination address equal to that address.

IP Spoofing VLAN is supported on Customer IP VLAN UNIs and NNI ports.It does not apply to PBB or PBT interfaces.

If an ARP packet is received that has the same source IP address as thelogical VLAN IP address, all traffic coming to any port of the switch in thatVLAN (with this MAC address as source/destination address) is silentlydiscarded by the hardware. After detecting a duplicate IP address, theswitch sends a gratuitous ARP packet to inform devices on the VLANabout the correct MAC address for that IP address. You can specify atime on a configurable global timer after which the MAC discard record isdeleted and the switch resumes accepting packets from that MAC address.

For information about configuring this option using the CLI, see“Configuring spoof detection for a VLAN” (page 258).


NN46220-511 04.01 26 June 2009


.


If you use Split MultiLink Trunking (SMLT), configure this option on bothSMLT aggregation switches to avoid connectivity issues.

ATTENTIONEnabling the IP spoofing feature requires you to reboot the switch.

For information about implementing at the UNI level, see Metro EthernetRouting Switch 8600 Configuration—UNI & Endpoints for non-PBT VPN(NN46220-506).

VLAN Loop Detection

ATTENTIONThe Loop Detection feature is applicable to NNI and SMLT ports; it is notapplicable to UNI ports. PBT trunks and B-VLANs can be associated with NNIports that have VLAN loop detection enabled.

On a per-port basis, the Loop Detection feature detects MAC addressesthat are looping from one port to other ports. After a loop is detected, theport on which the MAC addresses were learned is disabled. Additionally,if a MAC address is found to loop, the MAC address is disabled for thatVLAN.

The Loop Detection feature is used at the edge of a network to preventloops. It detects whether the same MAC address appears on differentports. This feature can disable a VLAN or a port. The Loop Detectionfeature can also disable a group of ports if it detects the same MACaddress on two different ports five times in a configurable amount of time.

The Loop Detection feature must only be enabled on SMLT ports, andnever used on IST ports or core SMLT square or full mesh ports.

The Loop Detection feature is configured per-switch. If a loop detectionevent takes place, peer switches are not notified.

You can also use Simple Loop Prevention Protocol to detect VLAN loops(see “Simple Loop Prevention Protocol” (page 90)).

The Loop Detection feature has the following traits:

• If a source MAC address is found to loop, and the specified loop detectaction is mac-discard, the MAC address is disabled. Any incomingpackets with this source or destination MAC address will be discardedfor that VLAN.

• Ports, VLANs, and MAC addresses that have been disabled by theLoop Detection feature are reenabled for automatic recovery.


NN46220-511 04.01 26 June 2009


.

Spanning tree protocols 37

• The link flap feature sets ports to operational down rather than admindown.

• Loop detection cannot be enabled on interswitch trunk ports.

For information about configuring Loop Detection with Device Manager,see “Configuring VLAN Loop Detection” (page 133). For information aboutconfiguring Loop Detection with the CLI, see “Configuring VLAN LoopDetection” (page 254). For a CLI loop detection configuration example,see “SMLT triangle with loop detection configuration example” (page 379).

Multiple MAC Registration ProtocolStarting in release 5.1, Multiple MAC Registration Protocol (MMRP) can beenabled on individual B-LANs. MMRPs interwork with protocols like MSTP,802.1ag, Y.1731, PBT, and LAG. MMRP and PLSB cannot coexist. Formore information see, Configuration — IP Multicast (NN46220-519).

Spanning tree protocolsThe Metro Ethernet Routing Switch 8600 can use one of two spanning treeprotocols: the Spanning Tree Protocol and the Multiple Spanning TreeProtocol.

For information about configuring spanning tree, see “Configuring spanningtree using Device Manager” (page 155) and “Configuring STGs using theCLI” (page 287).


• “Spanning Tree Protocol” (page 37)

• “Spanning Tree Protocol with PLSB” (page 42)

• “Spanning Tree Protocol with PBT” (page 43)

Spanning Tree ProtocolThe operation of the Spanning Tree Protocol (STP) is defined in theIEEE 802.1d standard. The STP detects and eliminates logical loops ina bridged or switched network. When multiple paths exist, the spanningtree algorithm configures the network so that a bridge or switch usesonly the most efficient path. If that path fails, the protocol automaticallyreconfigures the network and makes another path active, which sustainsnetwork operations. You can control path redundancy for VLANs byimplementing the STP.

A network can include multiple instances of STP. The collection of portsin one spanning tree instance is called a spanning tree group (STG).Metro Ethernet Routing Switch 8600 modules support STP and up to 64spanning tree groups.


NN46220-511 04.01 26 June 2009


.



• “Spanning tree groups” (page 38)

• “Spanning Tree FastStart” (page 39)

• “Understanding STGs and VLANs” (page 40)

• “Spanning Tree Protocol topology change detection” (page 40)

• “Per-VLAN spanning tree” (page 41)

Spanning tree groupsEach STG consists of a collection of ports that belong to the sameinstance of the STP protocol. These STP instances are completelyindependent from each other. For example, they send their own BPDUs,and they have their own timers.

For Metro Ethernet Routing Switch 8600s, multiple STGs are possiblewithin the same switch; that is, the routing switch can participate in thenegotiation for multiple spanning trees.

Figure 6 "Multiple spanning tree groups" (page 38) shows multiplespanning tree groups.

Figure 6Multiple spanning tree groups


NN46220-511 04.01 26 June 2009


.


Spanning Tree Protocol controlsThe ports associated with a VLAN must be contained within a singlespanning tree group. If you do not allow a VLAN to span multiple STGs,you avoid problems with spanning tree blocking ports (which causes a lossof connectivity within the VLAN).

Each untagged port can belong to only one STG, while tagged portscan belong to more than one STG. When a tagged port belongs to morethan one STG, the spanning tree BPDUs are tagged to distinguish theBPDUs of one STG from those of another STG. BPDUs from STG 1 arenot tagged. The tagged BPDUs are transmitted using a multicast MACaddress as tagged frames with a VLAN ID, and you specify the multicastMAC address and the VLAN ID. Because tagged BPDUs are not part ofthe IEEE 802.1d standard, not all devices can interpret tagged BPDUs.

You can enable or disable the Spanning Tree Protocol at the port or at thespanning tree group level. If you disable the protocol at the group level,received BPDUs are handled like a MAC-level multicast and flooded outof the other ports of the STG. Note that an STG can contain one or moreVLANs. Remember that MAC broadcasts are flooded out on all ports of aVLAN; a BPDU is a MAC-level message, but the BPDU is flooded out ofall ports on the STG, which can encompass many VLANs.

When STP is globally enabled on the STG, BPDU handling depends onthe STP setting of the port:

• When STP is enabled on the port, received BPDUs are processed inaccordance with STP.

• When STP is disabled on the port, the port stays in a forwarding state,received BPDUs are dropped and not processed, and no BPDU isgenerated.

An alternative to disabling the Spanning Tree Protocol is to enableSpanning Tree FastStart.

Spanning Tree FastStartSpanning Tree FastStart is an enhanced port mode supported by theMetro Ethernet Routing Switch 8600. If you enable Spanning TreeFastStart on a port with no other bridges, Spanning Tree FastStart bringsthe port up more quickly following switch initialization or a spanningtree change. The port goes through the usual blocking and learningstates before the forwarding state, but the hold times for these states isdetermined by the bridge hello timer (2 seconds by default) instead of thebridge forward delay timer (15 seconds by default). If the port receives aBPDU, it reverts to regular behavior.


NN46220-511 04.01 26 June 2009


.


FastStart is intended for access ports in which only one device isconnected to the switch (as in workstations with no other spanning treedevices). It may not be desirable to wait the usual 30 to 35 seconds forspanning tree initialization and bridge learning.

Use Spanning Tree FastStart with caution. This procedure is contrary tothat specified in the IEEE 802.1d standard for Spanning Tree Protocol(STP), in which a port enters the blocking state following the initializationof the bridging device or from the disabled state when the port is enabledthrough configuration.

Understanding STGs and VLANsFor the purposes of Spanning Tree Protocol negotiation, the ports on aMetro Ethernet Routing Switch 8600 can be divided into groups of portswhere each group of ports performs its own spanning tree negotiation withneighboring devices. In a Metro Ethernet Routing Switch 8600, thesegroups of ports are called spanning tree groups (STG). The Metro EthernetRouting Switch 8600 supports up to 64 STGs.

The ports in a VLAN are always a subset of the ports in an STG. A VLANcan include all the ports in a given STG, and there can be multiple VLANsin an STG, but a VLAN cannot have more ports than exist in the STG.Because VLANs are always subsets of STGs, the recommended practiceis to plan STGs and then create VLANs.

In the Metro Ethernet Routing Switch 8600 default configuration, a singleSTG encompasses all the ports in the switch. For most applications, thisconfiguration is sufficient. The default STG is assigned ID 1 (STG1).

If a VLAN spans multiple switches, it must be within the same STG acrossall switches; that is, the ID of the STG in which it is defined must be thesame across all devices.

Spanning Tree Protocol topology change detectionChange detection enables the detection of topology changes and sends atopology change notification (TCN) to the root on a per-port basis. Changedetection is enabled by default. When change detection is enabled and atopology change occurs, a trap is sent with the following information sothat you can identify the device:

• the MAC address of the STG sending the TCN

• the port number

• the STG ID

You can disable change detection on ports on which a single end station isconnected, and where powering that end station on and off will trigger theTCN. Change detection is referenced in IEEE 802.1d.


NN46220-511 04.01 26 June 2009


.


Topology change detection configuration rules

When you work with change detection settings:

• You can configure change detection only on access ports. This alsoapplies to link aggregation ports.

• If you disable change detection and then change the port from accessto tagging-enabled, the switch automatically sets change detection toenabled for the port. This also applies to link aggregation ports.

• In a link aggregation group with access ports, modifications to changedetection for a member port are automatically applied to the remainingmember ports.

To configure change detection using Device Manager, see “ConfiguringSTG topology change detection” (page 168).

To configure change detection using the CLI, see “Configuring topologychange detection” (page 295).

Per-VLAN spanning treeThe Metro Ethernet Routing Switch supports standards-based IEEE802.1d STP in addition to supporting proprietary mechanisms for multipleinstances of spanning tree.

Unfortunately, the IEEE 802.1d spanning tree provides only one instanceof the STP that can lead to incomplete connectivity for certain VLANs,depending on the network topology.

For example, Figure 7 "802.1d spanning tree" (page 41) shows a networkin which one or more VLANs span only some switches. In this example,the STP can block a VLAN path if that VLAN does not span across allswitches.

Figure 7802.1d spanning tree

You can avoid this issue by configuring multiple spanning tree instances,as shown in Figure 8 "Multiple instances of spanning tree" (page 42).


NN46220-511 04.01 26 June 2009


.


The Metro Ethernet Routing Switch 8600 uses a tagged BPDU addressthat is associated with a VLAN tag ID. The VLAN tag ID is applied to oneor more VLANs, and is used among switches to prevent loops. The sametagged BPDU address must be configured on all switches in the network.

The Cisco Systems proprietary implementation of multiple spanning tree(pre-IEEE 802.1s) is called PVST/PVST+ (Per VLAN Spanning Tree),which uses a spanning tree instance per VLAN.

Figure 8Multiple instances of spanning tree

With software release 3.7 or greater, you can configure your MetroEthernet Routing Switch using either of two methods: Metro EthernetRouting Switch 8600 tagged BPDU or PVST+.

Similar to the Metro Ethernet Routing Switch 8600 implementation ofmultiple STP instances, PVST+ uses the standard IEEE 802.1d STP forVLAN 1; all other VLANs use PVST+ BPDUs.

You can use IEEE 802.1Q VLAN tagging to tunnel the multicastPVST+ BPDUs within a IEEE 802.1Q region. The standard BPDUs forVLAN 1 are all addressed to the well-known STP multicast address01-80-C2-00-00-00, while PVST+ BPDUs in other VLANs are addressed tothe multicast address of 01-00-0C-CC-CC-CD.

You can use PVST+ to load balance the VLANs by changing the VLANbridge priority.

Spanning Tree Protocol with PLSBProvider Link State Bridging (PLSB) does not support xSTP. When PLSBis enabled at the chassis level, only the regular STP mode is supported;MSTP is not supported. In order to create a PLSB-VLAN, a PLSB-STGmust be created.

PLSB is a simple, robust networking solution that displaces conventionalEthernet networking solutions for E-LAN services achieved through theuse of a Link State Routing Protocol as the control plane rather thanconventional spanning tree protocols. PBT and PLSB are complementary


NN46220-511 04.01 26 June 2009


.


as they address different problems (for example, E-Line versus E-LANservices) while leveraging a common data plane approach (that isMAC-in-MAC, PBT style configuration in a VLAN partition). PLSB andexisting Ethernet control protocols (for example, spanning tree) canoperate side-by-side in the same network infrastructure ensuring smoothnetwork evolution.

Spanning Tree Protocol with PBTPBT disables MAC address learning and Spanning Tree Protocol (STP).It also disables broadcast-on-unknown. Therefore, PBT does not allowbroadcast and dropped frames that do not have a forwarding record.In order to create a PBT-VLAN, a PBT-STG must be created with STPautomatically turned off.

Multiple Spanning Tree ProtocolThe operation of the Multiple Spanning Tree Protocol (MSTP or IEEE802.1s) is similar to the current Nortel proprietary MSTP.

Use MSTP in addition to the current proprietary Spanning Tree Protocol(STP) implementation to enable the Metro Ethernet Routing Switch 8600 toachieve the following:

• reduced convergence time from 30 seconds to less than one secondfor most scenarios when there is a topology change in the network(that is, a port going up or down)

• elimination of unnecessary flushing of the Media Access Control (MAC)database and flooding of traffic to the network, using a new topologychange mechanism

• backward compatibility with legacy 802.1d switches

• support for 64 instances of spanning tree in MSTP mode

For MSTP configuration examples, see “Multiple Spanning Tree Protocolconfiguration example” (page 406).

Interoperability with legacy STPMSTP provides a new parameter called ForceVersion to provide backwardcompatibility with legacy STP. A user can configure a port in eitherSTP-compatible mode or MSTP mode.

• An STP-compatible port transmits and receives only STP BPDUs. AnyMSTP BPDU that the port receives in this mode is discarded.

• An MSTP-compatible port transmits and receives only MSTP BPDUs.If an MSTP port receives a STP BPDU, it becomes an STP port. Userintervention is required to change this port back to MSTP mode. Thisprocess is called Port Protocol Migration.


NN46220-511 04.01 26 June 2009


.


Differences in port roles

MSTP is an enhanced version of STP. These two protocols have almostthe same set of parameters.

The following table lists the differences in port roles for STP and MSTP.STP supports two port roles while MSTP supports four port roles.

Table 4Differences in port roles for STP and MSTP

Port Role STP MSTP Description

Root Yes Yes This port receivesa better BPDU thanits own and has thebest path to reach theRoot. The root port isin Forwarding state.The root port anddesignated ports canbe in the Discardingstate before they go toroot forwarding.

Designated Yes Yes This port has thebest BPDU onthe segment. Thedesignated port is inthe Forwarding state.

Alternate No Yes This port receives abetter BPDU than itsown BPDU, and thereis a Root port withinthe same switch. Thealternate port is in theDiscarding state.

Backup No Yes This port receivesa better BPDU thanits own BPDU, andthis BPDU is fromanother port withinthe same switch. Thebackup port is in theDiscarding state.

Port roles—root forwarding role

MSTP root forwarding roles are as follows:


NN46220-511 04.01 26 June 2009


.


• The port that receives the best path BPDU on a switch is the root port,and is referred to as a Root Forwarding (RF) port. This is the port thatis the closest to the root bridge in terms of path cost.

• The spanning tree algorithm elects a single root bridge in a bridgednetwork per spanning tree instance.

• The root bridge is the only bridge in a network that does not have rootports; all ports on a root bridge are Designated Forwarding (DF).

• There can only be one path towards a root bridge on a given segment,otherwise there will be loops.

Port roles—designated forwarding role

MSTP designated forwarding roles are as follows:

• All bridges connected on a given segment monitor each other’sBPDUs. The bridge that sends the best BPDU is, by mutualagreement, the root bridge for the segment.

• The corresponding port on the bridge is referred to as a DesignatedForwarding Port.

Port roles—alternate blocking role

MSTP alternate blocking roles are as follows:

• A blocked port is defined as a port not designated by a root port.

• An Alternate Blocked port is a port that is blocked because it receivedbetter path cost BPDUs from another bridge.

Edge port

MSTP uses a new parameter called the edge port. When a port connectsto a non-switch device, such as a PC or a workstation, it must beconfigured as an edge port. An active edge port enters forwarding statewithout delay. An edge port becomes a non-edge port if it receives aBPDU.

Path cost values

MSTP recommends new path cost values that support a wide range of linkspeeds. The following table lists the recommended path cost values.


NN46220-511 04.01 26 June 2009


.


Table 5Recommended path cost values

Link Speed Recommended Value

Less than or equal to 100 Kb/s1 Mb/s10 Mb/s100 Mb/s

200 000 00020 000 0002 000 000200 000

1 Gb/s10 Gb/s100 Gb/s

20 0002 000200

1 Tb/s10 Tb/s

202

Negotiation process

The following section describes the negotiation process between switchesthat takes place before PCs can exchange data (see Figure 9 "Negotiationprocess" (page 46)).

Figure 9Negotiation process

After power-up, all ports assume the role of designated ports. All portsare in the discarding state except edge ports. Edge ports go directly intoforwarding state without delay.


NN46220-511 04.01 26 June 2009


.

Link aggregation (MLT, SMLT, LACP) 47

Switch A port 1 and switch B port 1 exchange BPDUs. Switch A knowsthat it is the root and that switch A port 1 is the designated port. Switch Blearns that switch A has higher priority. Switch B port 1 becomes the rootport. Both switch A port 1 and switch B port 1 are still in discarding state.

Switch A starts the negotiation process by sending a BPDU with theproposal bit set.

Switch B receives the proposal BPDU and sets its non-edge ports todiscarding state. This operation occurs during the synchronization process.

Switch B sends a BPDU to switch A with the agreement bit set.

Switch A sets port 1 to forwarding state and switch B sets port 1 toforwarding state. PC 1 and PC 2 can now communicate. The negotiationprocess now moves on to switch B port 3 and its partner port. PC 3 cannotexchange data with either PC 1 or PC 2 until the negotiation processbetween switch B and switch C finishes.

The MSTP convergence time depends on how quickly the switch canexchange BPDUs during the negotiation process, and on the number ofswitches in the network.

Link aggregation (MLT, SMLT, LACP)Link aggregation allows you to bundle a set of ports into a port group,which is represented as one logical interface to upper layer protocols.

Metro Ethernet Routing Switch 8600 supports multiple types of linkaggregation:

• MultiLink Trunking (MLT) is a statically configured link bundlingmethod.

• IEEE 802.3ad-based link aggregation, through the Link AggregationControl Protocol (LACP), supports a dynamic link aggregation function,which can add links dynamically, as they become available, to a trunkgroup.

• If Provider Link State Bridging (PLSB) MLT ISIS interface and LACPare configured on the same MLT, when a port configured on the LAGcomes up, the port is added dynamically to MLT, and LACP informsPLSB ISIS to bring up the ISIS circuit. When a port configured on theLAG goes down, the port is removed dynamically from MLT, and ifthe port is the last port on the MLT, LACP informs PLSB ISIS to bringdown ISIS circuit.

• Both MLT and IEEE 802.3ad-based link aggregation are defined aspoint-to-point functions, although Split MultiLink Trunking (SMLT)allows you to connect a multilink trunk point to two SMLT endpoints.


NN46220-511 04.01 26 June 2009


.


SMLT can connect two SMLT end points to two other SMLT endpointsas well.

• SMLT allows not only module redundancy, but also allows systemredundancy while allowing bandwidth aggregation at the same time.In addition, SMLT functionality was extended to include LACP fordynamic link aggregation.

For information about configuring link aggregation, see “Configuring linkaggregation using Device Manager” (page 183) and “Configuring linkaggregation using the CLI” (page 321).

See “Device Manager configuration examples” (page 367) and “CLIconfiguration examples” (page 375) for configuration examples, includingCLI commands, for concepts described in this section.


• “MultiLink Trunking (MLT)” (page 48)

• “IEEE 802.3ad-based link aggregation” (page 60)

• “Split MultiLink Trunking (SMLT)” (page 69)

MultiLink Trunking (MLT)MultiLink Trunking (MLT) is a point-to-point connection that aggregatesmultiple ports so that they logically act like a single port, but with theaggregated bandwidth. Grouping multiple ports into a logical link provideshigher aggregate throughput on a switch-to-switch or switch-to-serverapplication.

MultiLink Trunking provides media and module redundancy. Moduleredundancy is provided in the form of Distributed MLT (DMLT), which youcan use to aggregate similar ports from different modules.

MLT links must be statically configured to be trunk group members.


• “MLT UNI” (page 49)

• “MLT load distribution options” (page 49)

• “Metro Ethernet Routing Switch 8600 MLT hash algorithms” (page 51)

• “Multicast/Broadcast Hashing” (page 52)

• “MultiLink Trunking rules” (page 53)

• “Multicast flow distribution over MLT” (page 53)

• “Multicast distribution algorithm” (page 54)


NN46220-511 04.01 26 June 2009


.


• “Multicast traffic redistribution” (page 55)

• “MLT examples” (page 56)

MLT UNIMLT is based on 802.3ad link aggregation (LAG), which allows multipleEthernet links to be grouped into one bundle. MLT UNI is supported on Rand RC modules, and on ESM ports. MLT links can be on the same cardor across different physical cards to provide card redundancy, referredto as Distributed MLT (DMLT). A single MLT cannot span different cardtypes.

MLT UNI is not supported on Ethernet Services Unit access ports whenthe Ethernet Services Unit is used in ring or standalone mode.

MLT UNI is supported for both OEL2 (ESM and R module), and 802.1ah(PBB) UNI types (on R and RC modules only).

ESM ports only support OEL2 encapsulation service.

The MAC address used by an MLT UNI is a separate MAC address,known as an "aggregator MAC address”. This aggregator MACaddress is used as the source and destination MAC for OEL2 and PBBencapsulation.

ISID endpoint and TDI endpoint traffic statistics are displayed as anaggregation of statistics from each MLT member port used by a givenentity.

For more information on using and configuring MLT UNI, see EngineeringGuidelines (NN46220-200).

MLT load distribution optionsLoad distribution algorithms on Metro Ethernet Routing Switch for trafficdistribution across an MLT are supported for on both MLT UNI and NNIMLT. The actual distribution and forwarding is performed in the hardware.

The following distinct hardware MLT distribution types are supported onMetro Ethernet Routing Switch:

C-MAC Hash

The MLT link is chosen based on a hash of the associated source anddestination customer MAC address (C-MAC SA and DA), if the ingress linkis an R or RC module NNI, or R or RC module UNI.


NN46220-511 04.01 26 June 2009


.


If the ingress UNI is on an ESM card, the hash is based on the sourcecustomer MAC and destination B-MAC/UNI MAC (C-MAC SA and B-MACDA).

If the CPE is a router or the VPN type is point-to-point, this option resultsin unicast frames between two Metro Ethernet Routing Switch UNIs takingthe same egress MLT link. A typical router deployment has a single IP linkbetween two routers and each is identified by a single MAC address.

B-MAC Hash

The egress MLT link is chosen based on a hash of the associated sourceand destination UNI MAC or source and destination I-SID MAC (UNIMAC/BMAC SA and DA). If the traffic type is OEL2 and the ingress MLTport is a legacy NNI port or ESM local TLS/Ring/Standalone, this traffic ishashed based on the OEL2 UNI ID.

For R and RC modules, and ESM MLT-UNI, OEL2, traffic is hashed basedon the UNI MAC/BMAC.

For E-LINE (point to point) service, this option results in all VPN traffic toegress a single link of an MLT UNI.

B-MAC Hash is the default option for MLT-UNI. It is also used if theconfigured option is not supported by the ingress hardware. For moreinformation on using and configuring MLT UNI, see Engineering Guidelines(NN46220-200).

1+1 SP B-VID

The egress MLT link is chosen based on a configured, ordered prioritylist for VPNs that use different SPVLANs/BVLANs within the core ofthe network. For a given VPN, because a VPN must be in a singleSPVLAN/BVID, traffic always chooses the same link (highest priority). Thiscan effectively distribute traffic over an MLT UNI only if there are severalSPVLANs/BVLANs in use in the core of the Metro Ethernet Routing Switchnetwork.

This option is likely to be deployed for interconnection between networks,where different VPNs can be put into different core VLANs. This optioncan allow greater than 1G throughput for an MLT (independent of MACaddresses) under nonfailure conditions.


NN46220-511 04.01 26 June 2009


.


Packets in the same flow are guaranteed to be placed on the same linkin the MLT group, therefore guaranteeing frame ordering. Each VID isgiven a primary and secondary link. A primary failure causes switchover tosecondary; upon recovery traffic is reverted. Ingress traffic from the CPEcan use any link of the MLT.

ISID/TDI (R and RC module only)

This option is only supported if the ingress port for the node is an Ror RC module. If the ingress card is ESM or Legacy NNI, the defaultB-MAC Hash is used instead. If the packet received is not a PBB or OEL2encapsulated packet, the default B-MAC hash is used.

The egress MLT link is chosen based on a hash of the associated ISID orTDI number. Frames are hashed such that all frames that are a memberof a single TDI or ISID are sent over the same link. In order for this optionto effectively distribute traffic, several TDI or ISIDs must be present on theMLT UNI.

For more details on MLT load distribution, see Engineering Guidelines(NN46220-200).

Metro Ethernet Routing Switch 8600 MLT hash algorithmsThe Metro Ethernet Routing Switch distributes traffic across MLT linkmembers based on several criteria. Regardless of which load distributionoption is chosen, the actual algorithm varies based on the Ingresshardware to the node and the protocol or service being used. Differentcard types and vintages have different capabilities to distribute traffic.

Legacy NNI

The original 8000 series Legacy I/O modules are used only for NNI portsor trunks. The Legacy I/O module performs the hash algorithm based onthe following formula. The formula uses a 6 bit LSB XOR calculation:

{(A XOR B) MOD x},

where A and B are the 6 least-most significant bits in either

1. the source and destination UNI ID addresses in the case of OEL2

2. the source and destination B-MAC addresses in the case of PBB

3. the source and destination IP Address in the case of non EVPN IProuted or IP bridged traffic and x is the number of active links in the MLT.


NN46220-511 04.01 26 June 2009


.


IP traffic is always hashed on the SA/DA IP address using the 6 bit LSBXOR function.

ESM8668 UNI

ESM cards use the same hash algorithm as described for Legacy cards.For ESM UNI, the hash is based on the UNI ID fields when the BMACoption is chosen. This is referred to as 6 bit LSB XOR calculation.

IP VLAN traffic is always hashed on the SA/DA IP address using the 6 bitLSB XOR function.

ESM8668 MLT UNI

MLT-UNI on ESM cards perform the same algorithm as described forLegacy cards. However the hash is based on the UNI MAC fields whenthe BMAC option is chosen.

R and RC module UNI/NNI (including MLT)

The R and RC module hash algorithm uses 32 bit polynomial functionroutine to determine the distribution. The formula uses 32 bits from thesource and 32 bits from the destination address, and uses the polynomialfunction to determine an MLT link index for a particular flow.

The 32 bit polynomial function inputs are always SA/DA UNI MAC/B-MACfor EVPN traffic, or IP SA/DA for IP routed or bridged non EVPN traffic.

Metro Ethernet Routing Switch 8600 provides a CLI command to generatethe hash results for selected source and destination addresses. Thiscommand can be used to verify what MLT links are used for a selectcombination. The following is an example CLI command for ISID:

config sys set hash-calc getmltindex traffic-type non-ipdest-val 1:0:0:0:0:0 src-val 0:0:0:0:0:24 mltID 25]

There is one calculation exception for Load Distribution TDI/ISID. Becausethere is only one field used to hash with, a fixed value for dest-val equal to1:0:0:0:0:0:0 is used when TDI/ISID (in hex format) is used as the src-val.

Multicast/Broadcast HashingFor broadcast and multicast traffic (including EVPN traffic that fails CMAClookup, for example multicast in the BVID), the traffic sent across the MLTdiffers based on the Ingress hardware type.

Legacy modules send the broadcast or multicast traffic to a single linkdefined by the first link in the MGID table on the switch fabric. This link isnot deterministic.


NN46220-511 04.01 26 June 2009


.


R modules send the broadcast or multicast traffic to a single link definedby the first link in the MLT itself (lowest slot and port).

If the links fail, the traffic is sent to the next link in the list.

The above behavior imposes an overall limit on the amount of broadcastor multicast traffic (including flooding unknown EVPN traffic) that cantraverse an MLT. Also, the first link, as defined above, can be different foreach direction between two nodes. The result is that forward and reversemulticast traffic take different links in an MLT group based on the directionbetween two nodes.

MultiLink Trunking rulesAll Metro Ethernet Routing Switch 8600 multilink trunks operate under thefollowing set of rules:

• MLT is supported on 10BaseT, 100BaseTX, 100BaseFX, GigabitEthernet, and 10 Gigabit Ethernet module ports.

• All ports in an multilink trunk must be of the same media type (copperor fiber) and have the same speed and duplex settings.

• All ports in a multilink trunk must be in the same STG, unless the portis tagged; tagging allows ports to belong to multiple STGs.

• MLT is compatible with the Spanning Tree Protocol.

• IEEE 802.1Q tagging is supported on a multilink trunk.

• The uni-aggr-idx and perform-tagging enabled commandsmust be included in the MLT UNI before the MLT can be used for aUNI endpoint.

Metro Ethernet Routing Switch 8600 multilink trunks have the followinggeneral features and requirements:

• Up to 128 MLT groups (using R modules and R mode) are supportedwith as many as 8 same-type ports belonging to a single multilinktrunk.

• The ports in a multilink trunk can span modules, providing moduleredundancy.

• Apply filters individually to each port in a multilink trunk.

Multicast flow distribution over MLTMultiLink Trunking (MLT) provides a mechanism for distributing multicaststreams over a multilink trunk. The mechanism is based on source-subnetand group addresses, and you can use it to choose the address and thebytes in the address for the distribution algorithm.


NN46220-511 04.01 26 June 2009


.


This algorithm is the same multicast flow distribution algorithm used forIEEE 802.3ad-based link aggregation.

As a result, you can distribute the load on different ports of the multilinktrunk and achieve an even distribution of the streams. In applications suchas TV distribution, multicast traffic distribution is particularly important,because bandwidth requirements can be substantial when a large numberof TV streams are employed.

The Multicast Distribution over MLT feature is supported only on MetroEthernet Routing Switch 8600 E, M, and R modules. As a result, all themodules that have ports in a multilink trunk must be Metro EthernetRouting Switch 8600 E, M, or R modules to enable multicast flowdistribution over MLT.

Multicast distribution algorithmTo determine the port for a particular source, group (S, G) pair, use thenumber of active MLT ports to MOD the number generated by the XOR(exclusive OR operation) for each byte of the masked group address, withthe masked source address.

By default, the group mask and source mask is 255.255.255.255. A bytewith a value of 255 in the mask means that the corresponding byte inthe group or source address is taken into account when the algorithm isapplied.

For example, given:

group address G[0].G[1].G[2].G[3]

group mask GM[0].GM[1].GM[2].GM[3]

source subnet address S[0].S[1].S[2].S[3]

source mask SM[0].SM[1].SM[2].SM[3]

The port is calculated using:

( ( ( (( G[0] AND GM[0] ) XOR ( S[0] AND SM[0] ) ) XOR ( (G[1] ANDGM[0] ) XOR ( S[1] AND SM[1] )) ) XOR ( (G[2] AND GM[2] ) XOR ( S[2]AND SM[2] )) ) XOR ( ( G[3] AND GM[3] ) XOR ( S[3] AND SM[3] )) )MOD (active ports of the MLT)

Algorithm example

The algorithm used for traffic distribution causes the distribution to besequential if the streams are similar to those in this example.


NN46220-511 04.01 26 June 2009


.


For this example, assume that the MLT ports are 1/1 to 1/4, that the maskconfiguration is 0.0.0.0 for the source mask and 0.0.0.255 for the groupmask, and that source A.B.C.D sends to groups:

X.Y.Z.1

X.Y.Z.2

X.Y.Z.3 to X.Y.Z.10

The algorithm chooses link 1/1 for group X.Y.Z.1, and then X.Y.Z.2 goeson port 1/2, X.Y.Z.3 goes on port 1/3, X.Y.Z.4 goes on port 1/4, X.Y.Z.5goes on port 1/1, and so on.

Configuration example

In this configuration example, only the first byte of the group mask, and thefirst two bytes of the source subnet mask are considered when distributingthe streams.

config sys mcast-mlt-distribution grp-mask 255.0.0.0config sys mcast-mlt-distribution src-mask 255.255.0.0config sys mcast-mlt-distribution enableconfig sys mcast-mlt-distribution redistribution enable

When you configure flow distribution over MLT, Nortel recommendsthat you choose source and group masks that result in the most eventraffic distribution over the multilink trunk links. For example, if you findthat group addresses change incrementally, while there are few sourcessending to different groups, use a source mask of 0.0.0.0 and a groupmask of 255.255.255.255. In most cases, this provides a sequentialdistribution of traffic on the multilink trunk links.

For a detailed description of commands used to configure multicast flowdistribution over MLT, see Configuration — IP Multicast (NN46220-519).

Multicast traffic redistributionThe overall goal of traffic redistribution is to achieve a distribution of thestreams on the multilink trunk links in the event of an MLT configurationchange. Traffic distribution is based on the IP multicast MLT distributionalgorithm (see “Multicast distribution algorithm” (page 54)) and thealgorithm behavior is the same for R and non-R modules.


NN46220-511 04.01 26 June 2009


.


By default, redistribution is disabled. When you add or remove a link fromthe multilink trunk, the active streams continue flowing on their originallinks if redistribution is disabled. If redistribution is enabled, however, theactive streams are redistributed according to the distribution algorithm onthe links of the multilink trunk.

Traffic redistribution can cause minor traffic interruptions.

To minimize the effect of redistribution of multicast traffic on the multilinktrunks, the implementation does not move the streams to the appropriatelinks all at once. Instead, it redistributes a few streams at every time tickof the system. To that end, when an MLT port becomes inactive andredistribution is disabled, only the affected streams are redistributed onthe remaining active ports.

If redistribution is enabled, all the streams are redistributed on the MLTports based on the assignment provided by the distribution algorithm. Formore information, see “Multicast distribution algorithm” (page 54).

When a new port becomes active in a multilink trunk and redistribution isdisabled, existing streams remain on their original links. If you need toredistribute the streams dynamically to split the load on all the links of themultilink trunk, you can enable redistribution. This results in a few streamsbeing redistributed every system time tick.

For a detailed description of the commands used to configuremulticast flow distribution over MLT, see Configuration — IP Multicast(NN46220-519).

MLT examplesThis section provides three MLT examples and includes the followingtopics:

• Switch-to-switch MLT example

• Client/server MLT example

Switch-to-switch MLT example

The following figure shows two multilink trunks (T1 and T2) connectingswitch S1 to switches S2 and S3.


NN46220-511 04.01 26 June 2009


.


Figure 10Switch-to-switch multilink trunk configuration

Each of the trunks shown in Figure 10 "Switch-to-switch multilinktrunk configuration" (page 57) can be configured with multiple switchports to increase bandwidth and redundancy. When traffic betweenswitch-to-switch connections approaches single port bandwidth limitations,you can create a multilink trunk to supply the additional bandwidth requiredto improve performance.

Switch-to-server MLT example

This example applies to MLT UNIs where the servers are attached to MLTUNIs.

Figure 11 "Switch-to-server multilink trunk configuration" (page 58) showsa typical switch-to-server trunk configuration. In this example, file serverFS1 utilizes dual MAC addresses, using one MAC address for eachnetwork interface card (NIC). No multilink trunk is configured on FS1. FS2is a single MAC server (with a four port NIC) and is configured as multilinktrunk configuration T1.


NN46220-511 04.01 26 June 2009


.


Figure 11Switch-to-server multilink trunk configuration

As shown in this example, one port on FS1 is blocked, thus is unused,whereas FS2 benefits from having aggregated bandwidth on multilink trunkT1.

Client/server MLT example

Figure 12 "Client/server multilink trunk configuration" (page 59) showsan example of how multilink trunks can be used in a client/serverconfiguration. In this example, both servers are connected directly toswitch S1. FS2 is connected through a multilink trunk configuration (T1).The switch-to-switch connections are through multilink trunk T2, T3, andT4. Clients accessing data from the servers (FS1 and FS2) are providedwith maximized bandwidth through T1, T2, T3, and T4. On the MetroEthernet Routing Switch 8600, trunk members (the ports that compriseeach multilink trunk) do not have to be consecutive switch ports; they canbe selected across different modules for module redundancy.


NN46220-511 04.01 26 June 2009


.


Figure 12Client/server multilink trunk configuration

With spanning tree enabled, ports that belong to the same MultiLink Trunkoperate as follows:

• All ports in the multilink trunk must belong to the same spanning treegroup if spanning tree is enabled.

• Identical bridge protocol data units (BPDU) are sent from each port.

• The multilink trunk port ID is the ID of the lowest numbered port.

• If identical BPDUs are received on all ports, the multilink trunk mode isforwarding.

You can disable the Nortel Spanning Tree Protocol (ntstg<enable|disable>) if you do not want to receive BPDUs on allports.


NN46220-511 04.01 26 June 2009


.


• If no BPDU is received on a port or if BPDU tagging and port taggingdo not match, the individual port is taken offline.

• Path cost is inversely proportional to the active multilink trunkbandwidth.

IEEE 802.3ad-based link aggregationIEEE 802.3ad-based (IEEE 802.3 2002 clause 43) link aggregation allowsyou to aggregate one or more links together to form a link aggregationgroup (LAG), such that a MAC client can treat the LAG as if it were asingle link.

Although IEEE 802.3ad-based link aggregation and MLT provide similarservices, MLT is statically defined, whereas IEEE 802.3ad-based linkaggregation is dynamic and provides more functionality through the LinkAggregation Control Protocol (LACP). LACP dynamically detects whetherlinks can be aggregated into a link aggregation group and does so whenlinks become available.

IEEE 802.3ad was designed for point-to-point link aggregation only.However, the Metro Ethernet Routing Switch 8600 provides extensions tosupport IEEE 802.3ad in SMLT configurations, thereby allowing any IEEE802.3ad-capable device to be connected to an SMLT aggregation pair.


• “IEEE 802.3ad overview” (page 61)

• “LACP” (page 61)

• “Link aggregation operations” (page 62)

• “Principles of link aggregation” (page 63)

• “LACP and MLT” (page 64)

• “LACP and SMLT” (page 65)

• “LACP priority” (page 66)

• “LACP keys” (page 66)

• “LACP timers” (page 67)

• “LACP modes” (page 68)

• “LACP and spanning tree interaction” (page 68)


NN46220-511 04.01 26 June 2009


.


IEEE 802.3ad overviewThe IEEE 802.3ad standard comprises of service interfaces, the LinkAggregation Control Protocol, the Marker Protocol, link aggregationselection logic, parser/multiplexer, frame distribution, and frame collectionfunctions.

Figure 13 "Link aggregation sublayer (according to IEEE 802.3ad)" (page61) shows the major functions of IEEE 802.3ad defined as multiple linkaggregation.

Figure 13Link aggregation sublayer (according to IEEE 802.3ad)

LACPThe main purpose of LACP is to manage switch ports and their portmemberships to form link aggregation groups (LAG). LACP candynamically add or remove LAG ports, depending on their availability andstates.

Aside from automatic link aggregation, a side benefit of LACP is its abilityto detect link layer failure within a service provider network. LACP packetsare exchanged end to end, thus if a link in the middle fails, but the localports do not register the failure, LACP times out and disables the port fortraffic.


NN46220-511 04.01 26 June 2009


.


The interfaces between the LACP module and the other modules is shownin Figure 13 "Link aggregation sublayer (according to IEEE 802.3ad)"(page 61).

Link aggregation operationsAs shown in Figure 13 "Link aggregation sublayer (according to IEEE802.3ad)" (page 61), the link aggregation sublayer comprises the followingfunctions:

• Frame distribution:

This block takes frames submitted by the MAC client and submits themfor transmission on the appropriate port, based on a frame distributionalgorithm employed by the Frame Distributor.

Frame distribution also includes an optional Marker Generator/Receiverused for the Marker Protocol. For the Metro Ethernet Routing Switch8600, only the Marker Receiver function is implemented. Refer to“MultiLink Trunking (MLT)” (page 48) for details about the framedistribution function.

• Frame collection:

This block passes frames received from the various ports to the MACclient. Frame collection also includes a Marker Responder, used forthe Marker Protocol.

• Aggregator Parser/Multiplexers:

— During transmission operations, these blocks pass frametransmission requests from the Distributor, Marker Generator, andMarker Responder to the appropriate port.

— During receive operations, these blocks distinguish among MarkerRequest, Marker Response, and MAC Client PDUs, and pass eachto the appropriate entity (Marker Responder, Marker Receiver, andCollector, respectively).

• Aggregator:

The combination of frame distribution and collection, along withAggregator Parser/Multiplexers, is referred to as the Aggregator.

• Aggregation Control:

This block configures and controls link aggregation. It incorporatesLACP, which can be used for automatic communication of aggregationcapabilities between systems. and automatic configuration of linkaggregation.

• Control Parser/Multiplexers:


NN46220-511 04.01 26 June 2009


.


— During transmission operations, these blocks pass frametransmission requests from the Aggregator and Control entities tothe appropriate port.

— During receive operations, these blocks distinguish LinkAggregation Control PDUs (LACPDU) from other frames, passingthe LACPDUs to the appropriate sublayer entity, and all otherframes to the aggregator.

Principles of link aggregationLink aggregation allows you to group switch ports together to form a linkgroup to another switch or server, thus increasing aggregate throughput ofthe interconnection between the devices while providing link redundancy.

Link aggregation employs the following principles and concepts:

• A MAC client communicates with a set of ports through an aggregator,which presents a standard IEEE 802.3 service interface to the MACclient. The Aggregator binds to one or more ports within a system.

• The aggregator distributes frame transmissions from the MAC clientto the various ports, and collects received frames from the ports andpasses them to the MAC client transparently.

• A system can contain multiple aggregators serving multiple MACclients. A given port binds to (at most) a single aggregator at any time.A MAC client is served by a single aggregator at a time.

• The binding of ports to aggregators within a system is managed by theLink Aggregation Control function for that system. The control functiondetermines which links can be aggregated, aggregates them, bindsthe ports within the system to an appropriate aggregator, and monitorsconditions to determine when a change in aggregation is needed. Suchdetermination and binding can be under manual control through directmanipulation of the state variables of link aggregation (for example,keys) by a network manager. In addition, automatic determination,configuration, binding, and monitoring can occur through the use ofa LACP.

• The LACP uses peer exchanges across the links to determine, onan ongoing basis, the aggregation capability of the various links, andcontinuously provides the maximum level of aggregation capabilityachievable between a given pair of systems.

• Frame ordering is maintained for certain sequences of frameexchanges between MAC Clients. The distributor ensures that allframes of a given conversation are passed to a single port. For anygiven port, the collector is required to pass frames to the MAC clientin the order that they are received from that port. The collector is


NN46220-511 04.01 26 June 2009


.


otherwise free to select frames received from the aggregated ports inany order. Because there are no means for frames to be mis-orderedon a single link, this guarantees that frame ordering is maintained forany conversation.

• Conversations can be moved among ports within an aggregation, bothfor load balancing and for maintaining availability in the event of linkfailures.

• The standard does not impose any particular distribution algorithm onthe distributor. Use an algorithm that is appropriate for the supportedMAC client.

For frame distribution function details, see “MultiLink Trunking (MLT)”(page 48).

• Each port is assigned a unique, globally administered MAC address.

The MAC address is used as the source address for frame exchangesthat are initiated by entities within the link aggregation sublayer itself(for example, LACP and Marker Protocol exchanges).

• Each aggregator is assigned a unique, globally administered MACaddress, which is used as the MAC address of the aggregation fromthe perspective of the MAC Client, both as a source address fortransmitted frames and as the destination address for received frames.

The MAC address of the aggregator can be one of the MAC addressesof a port in the associated LAG.

LACP and MLTWhen you configure standards-based link aggregation, you must enablethe aggregatable field. After you enable the aggregatable field, the LACPaggregator is one-to-one mapped to the specified multilink trunk.

For example, when you configure a link aggregation group (LAG), youmust do the following:

• Assign a numeric key to the ports you want to include in the LAG.

• Configure the LAG to be aggregatable.

• Enable LACP on the port.

• Create a multilink trunk and assign the same key to that multilink trunk.

The multilink trunk/LAG only aggregates those ports whose keymatches its own.

The newly created multilink trunk/LAG adopts the VLAN membership of itsmember ports when the first port is attached to the aggregator associatedwith this LAG. When a port is detached from an aggregator, the port is


NN46220-511 04.01 26 June 2009


.


deleted from the associated LAG port member list. When the last portmember is deleted from the LAG, the LAG is deleted from all VLANs andSTGs.

When LACP is enabled on any MLT containing ports, MLT LACP attributesoverride all the port level LACP attributes for the statically added ports.

To enable tagging on ports belonging to LAG, first disable LACP on theport, and then enable tagging on the port and enable LACP.

In release 6.0, the behavior of LACP-enabled MLTs is changed so thatports can be added and removed from an LACP-enabled MLT statically,as well as dynamically. This change is applicable on both UNI and NNIMLT/LAG, on R and RC modules.

If communication of the Link Aggregation Control Protocol data unit(LACPDU) on the port with peer node does not agree, traffic is nottransmitted and accepted on this port. In this condition, the port is in anSTG-disabled state.

Because ports can now be added and removed from an LACP-enabledMLT statically, the following points are also supported:

• configuration of 1 + 1 B-VID load distribution with LACP enabled

• dynamic addition and removal of B-VLANs and ACLs on anLACP-enabled MLT

• endpoint maintenance (for example, adding an I-SID endpoint) whenports of LACP-enabled LAG UNI are in a down state

LACP and SMLTLACP is supported on single port split multilink trunks and split multilinktrunks. The following are some guidelines to follow when using LACP andSMLT:

• When you sets the LACP system ID for split multilink trunks, youmust configure the same LACP SMLT system ID on both aggregationswitches to avoid loss of data. Nortel recommends that the SmltSysIdbe configured such that it matches the base MAC address of one ofthe chassis.

• If you use LACP in an SMLT square configuration, the LACPports must have the same keys for that SMLT LAG; otherwise, theaggregation can fail if a switch failure occurs.

• If an SMLT aggregation switch has LACP enabled on some of itsmultilink trunks, do not change LACP system priority after LACP isenabled on ports. If some ports do not enter the desired multilink trunk


NN46220-511 04.01 26 June 2009


.


after a dynamic configuration change, use the CLI command (assumeMLT 10): conf mlt 10 lacp clear-link-aggrgate

• Nortel recommends that LACP not be enabled on interswitch trunks toavoid unnecessary processing and to maintain simplicity.

Using the smlt-sys-id enables the use of any third-party switch asa wiring closet switch in an SMLT configuration. This enhancementprovides an option for the administrator to configure the system id onthe aggregation switch. The actor system priority of actor system id(LACP_DEFAULT_SYS_PRIO), configured by the user, and an actor keyequal to the SMLT-ID or SLT-ID, is sent to the wiring closet switch. Theadministrator must ensure that the same value of system id is configuredon the both the aggregation switches.

LACP priorityLACP priority is configured at the system level and at the port level.

• Port priority—determines which ports are aggregated into LAG ifmore than eight ports are configured for the LAG, as in a standby-portconfiguration.

• System priority—generates the switch ID when communicating withother switches. For SMLT applications, this is used to determine amaster/slave relationship between the SMLT switches. Nortel recommendsthat this value remain at its default value. If it must be changed, Nortelrecommends that you disable LACP first, and then reenable it after thevalue is changed.

LACP keysLACP keys are used to determine which ports are eligible to beaggregated into a LAG. The LACP keys are defined under the ports whenthe multilink trunk is configured. The ports whose keys match the multilinktrunk’s key can be aggregated into that multilink trunk.

• Keys need not match between two LACP peers.

• Keys must match on SMLT core switches when using LACP withSMLT.

You cannot change the LACP key of a port which is part of anLACP-enabled MLT. Consistency checks are added to ensure thefollowing:

• The LACP key and state cannot be altered on a statically added port.

• A dynamically added port cannot be removed from MLT.

• Only static ports can be added as primary or secondary ports for aMLT.


NN46220-511 04.01 26 June 2009


.


• Only ports with a matching key and VLAN can be added to anLACP-enabled MLT.

• You cannot change the LACP state of MLT with static ports.

LACP timersYou can customize failover times by changing the LACP timer attributes(fast periodic time; slow periodic time; aggregate wait time). These valuesare set by default to match the IEEE 802.3ad values. If they are changed,these values must match on the ports participating in aggregation betweentwo devices.

Any changes to these values at the global level are reflected on all ports.However, these values can be changed on a per-port level. When youchange a LACP timer globally, this value is set on all ports. The globaltimer value overwrites the local port value irrespective of the LACP state.You must reconfigure any port values that differ from the global values.

The user can use either the fast or slow timer, and this is set on theport level. By default, the Metro Ethernet Routing Switch 8600 uses thelong timer. LACP uses the following timers, which have the parametersindicated:

• fast periodic timer—200 to 20 000 ms; default 1000 ms

• slow periodic timer—10 000 to 30 000 ms; default 30 000 ms

• aggregation wait timer—200 to 2000; default 2000

Timer changes must be made to all ports participating in link aggregation,as well as to the ports on the partnering node.

Configuration changes to the LACP timers are not reflected immediately.LACP timers are not reset until the next time LACP is restarted globally oron a port. This action ensures consistency with peer switches.

When you enable LACP on a port, the timer values used are those set atthe port level. Toggling of the LACP status is required when timer valueschange. Existing ports are not impacted by this change unless you togglethe LACP status on the port.


NN46220-511 04.01 26 June 2009


.


LACP modesLACP uses two mode types, active and passive.

• Active mode—ports initiate the aggregation process. Active mode portsaggregate with other active mode ports or passive mode ports.

• Passive mode—ports participate in LACP but do not initiate theaggregation process. Passive mode ports must be partnered withactive mode ports for aggregation to occur.

LACP and spanning tree interactionLACP module operation is only affected by the physical link state or itsLACP peer status. When a link is enabled or disabled, the LACP module isnotified. The STP forwarding state does not affect the operation of LACPmodule. LACPDUs can be sent even if the port is in the STP blockingstate.

Unlike legacy multilink trunks, configuration changes (such as speed andduplex mode) to a LAG member port are not applied to all the memberports in the multilink trunk. Instead, the changed port is removed from theLAG and the corresponding aggregator, and the user is alerted when theconfiguration is created.

In contrast to MLT, IEEE 802.3ad-based link aggregation does not expectBPDUs to be replicated over all ports in the trunk group. Therefore, youmust enter the ntstg disable command to disable the parameter onthe spanning tree group for LACP-based link aggregation. For moreinformation about this command, see “Configuring Spanning Tree Protocol”(page 156) .

Be aware that this parameter is applicable to all trunk groups thatare members of the spanning tree group. This is necessary wheninternetworking with devices that only send BPDUs out of one port of theLAG.

Link aggregation rulesMetro Ethernet Routing Switch 8600 link aggregation groups operateunder the following rules:

• All ports in a LAG must operate in full-duplex mode.

• All ports in a LAG must operate at the same data rate.

• All ports in a LAG must be in the same VLAN.

• Link aggregation is compatible with Spanning Tree Protocol (STP) andMultiple Spanning Tree Protocol (MSTP).

• Link aggregation groups must be in the same STP groups.


NN46220-511 04.01 26 June 2009


.


• Ports in a link aggregation group can exist on different modules.

• A maximum of 32 link aggregation groups (128 for R modules in Rmode) are supported.

• A maximum of eight active links are supported per LAG.

• A maximum of eight standby links are supported per LAG.

• You can configure up to eight ports (mixture of active and standbyports) in an 802.3ad group.

Split MultiLink Trunking (SMLT)Routed SMLT, or RSMLT, is a Layer 3 protocol whereas SMLT is a Layer2 protocol. SMLT is described in this document, and RSMLT is describedin the document Configuring IP Routing Operations.

SMLT only applies to port type NNI; UNI does not have SMLT support.PBT trunks are supported over SMLT.

This section describes the Split MultiLink Trunking (SMLT) feature andincludes the following topics. For help with common terms and acronymsused with SMLT, refer to the “Glossary” (page 425).

• “Overview” (page 69)

• “Advantages of SMLT” (page 70)

• “SMLT operations” (page 72)

• “SMLT-on-Single-CPU feature” (page 78)

• “Single Port SMLT” (page 79)

• “Using MLT-based SMLT with Single Port SMLT” (page 84)

• “SMLT network design considerations” (page 87)

OverviewLink aggregation technologies are popular for improving link bandwidthefficiency and preventing link failures. IEEE 802.3ad is the standardizedlink aggregation protocol, although various vendors have developedtheir own proprietary implementations. IEEE 802.3ad is defined forpoint-to-point applications, however; it was not designed to recover arounda nodal failure.

Split MultiLink Trunking (SMLT) is an extension to IEEE 802.3ad thatimproves Layer 2 and Layer 3 resiliency by providing nodal protection, inaddition to link failure protection, and flexible bandwidth scaling. SMLT


NN46220-511 04.01 26 June 2009


.


achieves this by allowing edge switches using IEEE 802.3ad to dual-hometo two SMLT aggregation switches. SMLT is transparent to attacheddevices supporting IEEE 802.3ad.

Because SMLT inherently avoids loops due to its superior enhanced linkaggregation protocol, SMLT networks do not need to use the IEEE 802.1dSpanning Tree Protocol to enable loop-free triangle topologies. This isaccomplished by implementing a method that allows two aggregationswitches to appear as a single device to edge switches, which aredual-homed to the aggregation switches. The aggregation switches areinterconnected using an interswitch trunk, which allows them to exchangeaddressing and state information (permitting rapid fault detection andforwarding path modification). Although SMLT is primarily designed forLayer 2, it also provides benefits for Layer 3 networks as well.

Layer 2 edge switches must support some form of link aggregation (suchas MLT) to allow communications with an SMLT aggregation switch.

Advantages of SMLTSMLT improves the reliability of Layer 2 networks that operate betweenuser access switches and the network center aggregation switch byproviding:

• Load sharing among all links

• Fast failover in case of link failures

• Elimination of single point of failure

• Fast recovery, in case of nodal failure

• Transparent and interoperable solutions

• Removes STP convergence issues

These advantages are described in more detail in the sections that follow.

R modules support SMLT over 10 Gigabit Ethernet. This is available onlyon the 8683XLR/XZR modules.

Single point of failure elimination

SMLT helps eliminate all single points of failure and creates multiple pathsfrom all user access switches to the core of the network. In case of failure,SMLT recovers as quickly as possible so that no capacity is unused.SMLT provides a transparent and interoperable solution that requires nomodification on the part of the majority of existing user access devices.

SMLT compared to Spanning Tree Protocol


NN46220-511 04.01 26 June 2009


.


Networks that are designed to have user access switches dual-homed totwo aggregation switches, and have VLANs spanning two or more useraccess switches, experience the following design constraints:

• Spanning tree must be used to detect loops

• No load sharing exists over redundant links

• Network convergence is slow in case of failure

Figure 14 "Resilient networks with Spanning Tree Protocol" (page71) shows a typical aggregator switch configuration that is dependent uponSTP for loop detection.

Figure 14Resilient networks with Spanning Tree Protocol

As shown in Figure 15 "Resilient networks with SMLT" (page 72), withthe introduction of SMLT, all dual-homed Layer 2 frame-switched networkdevices are no longer dependent upon Spanning Tree Protocol for loopdetection, because a properly designed SMLT network inherently does nothave any logical loops. Similarly, Layer 3 networks can benefit from SMLTas well.


NN46220-511 04.01 26 June 2009


.


Resilient networks with SMLT is supported for IP routing and for servicesassociated with customer IP VLAN UNIs.

Figure 15Resilient networks with SMLT

SMLT operationsFigure 16 "Metro Ethernet Routing Switch 8600 as SMLT aggregationswitches" (page 73) illustrates an SMLT configuration with a pair of MetroEthernet Routing Switch 8600 devices (E and F) as aggregation switches.Also included are four separate user access switches (A, B, C, and D).Refer to the following sections for a description of the components shownin this SMLT example.

• Interswitch trunking

• CP Limit and SMLT interswitch trunking

• Other SMLT aggregation switch connections


NN46220-511 04.01 26 June 2009


.


Figure 16Metro Ethernet Routing Switch 8600 as SMLT aggregation switches

Interswitch trunking

SMLT aggregation switches must be connected through an interswitchtrunk. For example, user access switches B and C are connected to theaggregation switches via multilink trunks split between the two aggregationswitches. As shown in Figure 16 "Metro Ethernet Routing Switch 8600 asSMLT aggregation switches" (page 73), the implementation of SMLT onlyrequires two SMLT-capable aggregation switches. These switches mustbe connected through an interswitch trunk.

Aggregation switches use the interswitch trunk to:

• Confirm that they are alive and exchange MAC address forwardingtables.

• Send traffic between single switches attached to the aggregationswitches.

• Serve as a backup if one SMLT link fails.


NN46220-511 04.01 26 June 2009


.


Because the interswitch trunk is required for SMLT, for proper operationNortel recommends that you use multiple links on the interswitch trunkto ensure reliability and high availability. Nortel recommends usingGigabit Ethernet links for interswitch trunk connectivity to provide enoughbandwidth for potential cross traffic.

Asynchronous Transfer Mode (ATM) and Packet over SONET (PoS) linksare not supported for use as interswitch trunk links.

CP Limit and SMLT interswitch trunking

Control packet rate limit (CP Limit) is a feature that controls the amount ofmulticast and broadcast traffic that can be sent to the CPU from a physicalport. It protects the CPU from being flooded by traffic from a single,unstable port. The CP-Limit default settings are:

• default state = enabled

• default multicast packets-per-second (pps) value = 15 000

• default broadcast pps value = 10 000

When you configure SMLT links, Nortel recommends setting themulticast packets-per-second value to 6000 pps.

Note that for SMLT ports, CP Limit is enabled by default. Packets thatare destined for the control plane (that is, packets that have a QoS levelof 7 such as BPDU, OSPF hello) trigger this feature. When the thresholdis reached, CP Limit disables the port from which the offending traffic isreceived.

You can enable CP Limit for all ports so that the Metro Ethernet RoutingSwitch 8600 can disable any port that receives excess control traffic.SMLT is an exception because of the importance of the interswitch trunk.Nortel recommends that you disable the CP Limit feature on all interswitchtrunk ports so that these ports are not disabled, which can compromisethe stability of SMLT.

Do not confuse CP Limit with port rate limiting. Port rate limiting and CPLimit serve different purposes. Port level rate limiting, if enabled, limits allpackets with broadcast and multicast addresses to control the amount ofuser traffic. CP Limit is a protection mechanism for the control plane thatonly counts packets that are destined for the control plane, or packets thatare processed by the CPU with a QoS=7.

The CPU can count packets which are not counted by the CP Limitfeature. Such packet types can include auto-topology or NetBIOS. TheQoS level ensures that control plane traffic (with QoS=7) is processed firstin the case of congestion in the CPU buffer.


NN46220-511 04.01 26 June 2009


.


If the actual packets-per-second rate sent from a port exceeds the definedrate, then the port is administratively shut down to protect the CPU fromcontinued bombardment. Disabling interswitch trunk ports in this way canimpair network traffic flow, as this is a critical port for SMLT configurations.

Nortel recommends that an interswitch multilink trunk contain at least twophysical ports. Nortel also recommends that you disable CP-Limit on allphysical ports that are members of an interswitch trunk multilink trunk.

Disabling CP Limit on interswitch trunk multilink trunk ports forces another,less-critical port to be disabled if the defined CP Limits are exceeded.In doing so, you preserve network stability if a protection condition (CPLimit) arises. Note that, although it is likely that one of the multilink trunkports (risers) will be disabled in such a condition, traffic continues to flowuninterrupted through the remaining SMLT ports.

CP Limit can only be configured through the CLI.

The command syntax to enable or disable CP Limit is:

config ethernet <slot/port> cp-limit <enable|disable>

The Metro Ethernet Routing Switch 8600 also supports the ExtendedCP Limit feature. For more information about Extended CP Limit, seeConfiguring Network Management.

Other SMLT aggregation switch connections

The example shown in Figure 16 "Metro Ethernet Routing Switch 8600as SMLT aggregation switches" (page 73) includes end stations whichconnect to each of the switches. In this example, a, b1, b2, c1, c2, and dare clients and printers, while e and f are servers or routers.

User access switches B and C can use any method to determine whichlink of their multilink trunk connections to use to forward a packet, as longas the same link is used for a given source/destination address (SA/DA)pair. This is true regardless of whether the DA is known by B or C. SMLTaggregation switches always send traffic directly to a user access switch,and only use the interswitch trunk for traffic that they cannot forward inanother, more direct way.

The examples that follow explain the process in more detail.

Example 1: Traffic flow from a to b1 or b2

Assuming a and b1/b2 are communicating through Layer 2, traffic flowsfrom A to switch E and is forwarded over its direct link to B. Traffic comingfrom b1 or b2 to a is sent by B on one of its multilink trunk ports.


NN46220-511 04.01 26 June 2009


.


B can send traffic from b1 to a on the link to switch E, and traffic fromb2 to a on the link to F. In the case of traffic from b1, switch E forwardsthe traffic directly to switch A, while traffic from b2, which arrived at F, isforwarded across the interswitch trunk to E and then on to A.

Example 2: Traffic flow from b1/b2 to c1/c2

Traffic from b1/b2 to c1/c2 is always sent by switch B through its multilinktrunk to the core. No matter which switch (E or F) it arrives at, it will besent directly to C through the local link.

Example 3: Traffic flow from a to d

Traffic from a to d (and d to a) is forwarded across the interswitch trunkbecause it is the shortest path. This is treated as a standard link; SMLTand interswitch trunk parameters are not considered.

Example 4: Traffic flow from f to c1/c2

Traffic from f to c1/c2 is sent out directly from F. Return traffic from c1/c2allows you to have one active VRRP Master per IP subnet. It is passedacross the interswitch trunk if switch C sends it to E.

Traffic flow in an SMLT environmentTraffic flow in an SMLT environment follows these rules:

• If a packet is received from an interswitch trunk port, it is not forwardedto any active SMLT groups. This is key in preventing network loops.

• When a packet is received, a look-up is performed on the forwardingdatabase. If an entry exists, and if the entry was learned locally fromthe split multilink trunk or through the interswitch trunk as a remote splitmultilink trunk, it is forwarded out the local port (the packet should notbe sent to the interswitch trunk for forwarding unless there is no localconnection). Unknown and Broadcast packets are flooded out all portsthat are members of this VLAN.

• For loadsharing purposes in an SMLT scenario, the Metro EthernetRouting Switch 8600 obeys the MLT traffic distribution algorithm.

Traffic flow example

In an SMLT environment, the two aggregation switches share the sameforwarding database by exchanging forwarding entries using the IST. InFigure 17 "Output of the command show vlan info fdb-e 10" (page 77), theforwarding databases are shown for a pair of IST nodes (B and C). Notethat the entry for 00:E0:7B:B3:04:00 is shown on node C as being learnedon MLT-1, but because SMLT REMOTE is true, this entry was actually


NN46220-511 04.01 26 June 2009


.


learned from node B. On B, that same entry is shown as being directlylearned through MLT-1 because SMLT REMOTE is false. Figure 18"Network topology for traffic flow example" (page 78) shows the networktopology.

When a packet arrives at node C destined for 00:E0:7B:B3:04:00, if theSMLT REMOTE status is true, then the switch tries to send the packetout MLT-1 first, rather than through the interswitch trunk. Traffic rarelytraverses the interswitch trunk unless there is a failure. If this same packetarrives at B, then it will be forwarded to MLT-1 on the local ports.

Figure 17Output of the command show vlan info fdb-e 10


NN46220-511 04.01 26 June 2009


.


Figure 18Network topology for traffic flow example

SMLT-on-Single-CPU featureBeginning with Metro Ethernet Routing Switch 8600 Software Release 3.5and continuing through the latest hardware revisions, an enhancementwas added to improve SMLT failover behaviors for single CPU/SFconfigurations.

Prior to release 5.2, Nortel required that two switch fabric modules beinstalled in a chassis running SMLT. This was a requirement becauseSMLT clients did not reroute traffic around SMLT aggregation switcheswith a single failed CPU. Thus, packet loss can occur in this rare failurecase.

The SMLT-on-Single-CPU feature establishes a polling mechanismbetween the CPU and the interface modules. Because single CPU/SFconfigurations do not benefit from standard CPU/SF redundancy, in therare event that a CPU failure occurs on the aggregation switch, thisenhancement forces the interface modules offline and allows networkredundancy configurations to activate more quickly.

You can configure this feature using the CLI. For instructions, see“Configuring SMLT-on-Single-CPU” (page 344).


NN46220-511 04.01 26 June 2009


.


This feature is applicable to all I/O modules capable of supporting thenew Single CPU/Switch Fabric reliability enhancement. By default, theSMLT-on-Single-CPU feature is disabled.

The SMLT-on-Single-CPU feature can also be implemented on dualSSF/CPU chassis, and is independent of SMLT design. In dual SSF/CPUsystems, Nortel recommends that you consider enabling this feature. Itsuse provides for faster High-Availability-like failover for dual SSF/CPUsystems in terms of proper link status. This feature is fully supportedon R modules; R modules always operate in this mode independent ofconfiguration settings. R modules have been designed for faster failoverwithout software control.

Note that not all versions of Classic modules can support this feature. Ifnonsupported modules are in a chassis which has this feature enabled,you cannot enable the parameter, and the following error messageappears: Chassis configuration inappropriate for this feature. Forinformation about module version support, consult the Metro EthernetRouting Switch 8600 6.0 Release Notes. The 8608SX/8608SXE modulesare an example of nonsupported module types.

Single Port SMLTSingle Port SMLT lets you configure a split multilink trunk using a singleport. The Single Port SMLT behaves like an MLT-based SMLT, and cancoexist with SMLTs in the same system. Single Port SMLT lets you scalethe number of split multilink trunks on a switch to the maximum number ofavailable ports.

Split multilink trunk links can exist in the following combinations on theSMLT-aggregation switch pair:

• MLT-based SMLT + MLT-based SMLT

• MLT-based SMLT + single link SMLT

• single link SMLT + single link SMLT

Rules for configuring Single Port SMLT include:

• The dual-homed device that connects to the aggregation switches mustsupport MLT.

• Single Port SMLT is supported on Ethernet, PoS, and ATM ports.

Single Port SMLT is not supported on the 8681 module 10 GigabitEthernet ports with Software Release 3.5.


NN46220-511 04.01 26 June 2009


.


• Each Single Port SMLT is assigned an SMLT ID from 1 to 512.

• Single Port SMLT ports can be designated as Access or Trunk (that is,IEEE 802.1Q tagged or not); changing the type does not affect theirbehavior.

• You cannot change a single port split multilink trunk to an MLT-basedSMLT by adding more ports. You must delete the single port splitmultilink trunk, and then reconfigure the port as SMLT/MLT.

• You cannot change an MLT-based split multilink trunk into a single portsplit multilink trunk by deleting all ports but one. You must first removethe SMLT/MLT, then reconfigure the port as Single Port SMLT.

• A port cannot be configured as a MLT-based split multilink trunk and asa single port split multilink trunk at the same time.

• Two or more aggregation switches can have single port split multilinktrunks with the same IDs. You can have as many single port splitmultilink trunks as there are available ports on the switch.

• LACP is supported on single port split multilink trunks.

Split multilink trunk topologiesThere are four generic topologies in which SMLT can be deployed. Theuser can choose either a Single Port SMLT configuration, a triangleconfiguration, a square configuration, or a full mesh configuration,depending on the resiliency and redundancy required.

Single Port SMLT topology

Sometimes you need to exceed the Metro Ethernet Routing Switch 8600multilink trunk Group ID limit for server farm applications. In this case, youcan use Single Port SMLT (see Figure 19 "Single Port SMLT topology"(page 81)). This topology allows scaling up to the maximum number ofports on a switch. Any Layer 2 switch capable of link aggregation can beused as the client in this case.


NN46220-511 04.01 26 June 2009


.


Figure 19Single Port SMLT topology

SMLT triangle topology

The most often used configuration, the triangle configuration, connectsmultiple access switches to a pair of Metro Ethernet Routing Switch 8600devices. In many cases, dual-NIC servers capable of link aggregation areconnected directly to the Metro Ethernet Routing Switch 8600 devices ina similar fashion. Figure 20 "SMLT triangle topology" (page 82) depictsExtranet Switches (ES) as the SMLT Clients. In real-world applications,any Layer 2 device capable of link aggregation can become the SMLTclient.


NN46220-511 04.01 26 June 2009


.


Figure 20SMLT triangle topology

SMLT square topology

Often used in an enterprise core, the square SMLT configuration providesnetwork resiliency. Figure 21 "SMLT square topology" (page 83) showsthis topology.


NN46220-511 04.01 26 June 2009


.


Figure 21SMLT square topology

SMLT full mesh topology

For maximum reliability and resiliency, all SMLT nodes can be fullymeshed. This may not be an economical solution for many cases, but iftraffic loss cannot be tolerated, this design can route traffic around anyfailure. Figure 22 "SMLT full mesh topology" (page 84) shows the fullmesh topology.


NN46220-511 04.01 26 June 2009


.


Figure 22SMLT full mesh topology

Using MLT-based SMLT with Single Port SMLTYou can configure a split multilink trunk with a single port split multilinktrunk on one side and an MLT-based split multilink trunk on the other.Both must have the same SMLT ID. In addition to general use, Figure 23"Changing a split trunk from MLT-based SMLT to Single Port SMLT" (page85) shows how this configuration can be used for upgrading an MLT-basedsplit multilink trunk to a single port split multilink trunk without taking downthe split trunk.


NN46220-511 04.01 26 June 2009


.


Figure 23Changing a split trunk from MLT-based SMLT to Single Port SMLT

To configure Single Port SMLT using Device Manager, see “Configuring asingle port split multilink trunk” (page 216).

To configure Single Port SMLT using the CLI, see “Creating a single portsplit multilink trunk” (page 343).

Interaction between SMLT and LACPThe Metro Ethernet Routing Switch 8600 fully supports the IEEE 802.3adLink Aggregation Control Protocol (LACP); this is supported not only onmultilink trunks, but also on a pair of SMLT switches.


NN46220-511 04.01 26 June 2009


.


With this protocol, the Metro Ethernet Routing Switch 8600 provides astandardized external link aggregation interface to third-party vendor IEEE802.3ad implementations. This protocol extension provides dynamic linkaggregation mechanisms. Advantages of this protocol extension include:

• MLT peers and SMLT client devices can be network switches, andcan also be any type of server/workstation that supports link bundlingthrough IEEE 802.3ad.

• Single-link and multilink trunk solutions support dual-homedconnectivity for more than 350 attached devices, so that you can builddual-homed server farm solutions.

• Nortel tightly coupled the IEEE link aggregation standard with theSMLT solution to provide seamless configuration integration, while alsodetecting failure scenarios during network setup or operations.

Supported scenarios

SMLT/IEEE link aggregation interaction supports all known SMLTscenarios in which an IEEE 802.3ad SMLT pair can be connected to SMLTclients, or in which two IEEE 802.3ad SMLT pairs can be connected toeach other in a square or full mesh topology.

Non-supported scenarios

Some factors leading to failure are:

• Wrong ports connected

• Mismatched SMLT IDs assigned to SMLT client: SMLT switches candetect if SMLT IDs are not consistent. The SMLT aggregation switch,which has the lower IP address, does not allow the SMLT port tobecome a member of the aggregation, thus avoiding misconfigurations.

• SMLT client switch does not have automatic aggregation enabled(LACP disabled): SMLT aggregation switches can detect thataggregation is not enabled on the SMLT client, thus no automatic linkaggregation is established until the configuration is resolved.

• Single CPU failures: In the case of a CPU failure in a system with onlyone switch fabric, the LACP on the other switch (or switches) detectsthe remote failure and triggers all links connected to the failed systemto be removed from the link aggregation group. This process allowsfailure recovery for the network along a different network path.

Only dual-homed devices will benefit from this enhancement.


NN46220-511 04.01 26 June 2009


.


SMLT network design considerationsIf you use LACP in a square SMLT topology, LACP must have the samekeys for that SMLT LAG; otherwise, the aggregation can fail if a switchfailure occurs.

Use the following procedure when designing and configuring a SMLTnetwork (for more information, see Network Design Guidelines).

Step Action

1 Define a separate VLAN for the IST protocol:

config mlt 1 ist create ip <value> vlan-id <value>

2 Disable CP-Limit on the IST ports:

config ethernet <slot|port> cp-limit disable

3 Keep CP-Limit enabled on the split multilink trunk ports andchange multicast-limit value to 6000:

config ethernet <slot|port> cp-limit enablemulticast-limit 6000

4 Disable loop detect on split multilink trunk ports:

config ethernet <slot|port> loop-detect disable

5 Enable tagging on split multilink trunk links:

config ethernet <slot/port> perform-tagging enable

6 Enable dropping of untagged frames on split multilink trunk links:

config ethernet <slot/port> untagged-frames-discardenable

--End--

SMLT and SLPPDo not enable Simple Loop Prevention Protocol (SLPP) on all the portsof a square, partial, or full mesh split multilink trunk core. SLPP can beenabled on other non-SMLT ports of the core. For more information aboutSLPP, see “Simple Loop Prevention Protocol” (page 90).

SMLT and IP routingThis section describes SMLT and IP routing interactions and includes thefollowing topics:

• SMLT and Virtual Router Redundancy Protocol (VRRP)

• VRRP BackupMaster

• Routed SMLT (RSMLT)


NN46220-511 04.01 26 June 2009


.


SMLT and VRRP

ATTENTIONVRRP is supported for IP routing and for services associated with Customer IPVLAN UNIs.

Using VRRP, you can have one active primary router per IP subnet, withall other network VRRP interfaces operating in backup mode.

VRRP, when used with SMLT, becomes less efficient. Users that accessswitches aggregated into two Split-MLT switches send their shared trafficload (based on source and destination MAC or IP addresses) on all uplinkstowards the SMLT aggregation switches.

VRRP, however, has only one active routing interface enabled. Allother interfaces are in backup (standby) mode. In this case, all traffic isforwarded over the IST link towards the primary VRRP switch. Potentially,all traffic that arrives at the VRRP backup interface is forwarded, so thereis not enough bandwidth on the IST link to carry all the aggregated risertraffic. However, an enhancement to VRRP overcomes this issue byensuring that the IST trunk is not used in such a case for primary dataforwarding.

VRRP BackupMaster

ATTENTIONVRRP is supported for IP routing and for services associated with Customer IPVLAN UNIs.

If enabled, the VRRP BackupMaster acts as an IP router for packetsdestined for the logical VRRP IP address. Thus, all traffic is directly routedto the subnetwork it is destined for, and not Layer 2 switched to the VRRPmaster. This eliminates a potential limitation in the available interswitchtrunk bandwidth.

To avoid potential frame duplication problems, the VRRP BackupMasterfeature for SMLT can only be used on interfaces that are definedfor SMLT. It cannot be used in conjunction with hubs to avoid frameduplication. Also, it cannot be used on brouter or VLAN interfaces.

When using SMLT with routing on SMLT aggregation switches, Nortelrecommends that you use VRRP for default gateway redundancy. In aVRRP environment, usually one switch is active and the other is backup.For SMLT, an active-active concept can be used by enabling VRRPBackupMaster. The VRRP BackupMaster router will route traffic thatis received on the SMLT VLAN, thus avoiding traffic flow across theinterswitch trunk. This provides true load sharing abilities.


NN46220-511 04.01 26 June 2009


.


The BackupMaster feature provides an additional benefit. Under normalVRRP operation, a hello packet is sent every second. When three hellosare not received, all switches automatically revert to master mode. Thisresults in a 3 second outage. When you are using VRRP in an SMLTenvironment, and a link goes down, traffic is automatically forwarded tothe remaining ports configured for SMLT VRRP BackupMaster. Becauseboth switches are processing traffic, the node immediately recognizesthe VRRP state change, so there is faster failure recovery (less than 1second).

The following sections describe a few guidelines to follow when usingVRRP BackupMaster with SMLT:

• The VRRP virtual IP address and the VLAN IP address cannot be thesame.

• Configure the hold-down timer for VRRP to a value that isapproximately 150 percent of the IGP (Interior Gateway Protocol, suchas RIP or OSPF) convergence time to allow the IGP enough time toreconverge following a failure. That is, if OSPF takes 40 seconds toreconverge, set the holddown timer to 60 seconds.

• Stagger the hold-down timers with ARP requests. This means thatthe Ethernet Routing Switch 8600 will not have to run ARP at thesame time, causing excess CPU load. For example, if one node hasthe hold-down timer set for 60 seconds, you can set the other to 65seconds.

• Enable hold-down times on both VRRP sides (Master andBackupMaster).

Routed SMLT (RSMLT)

ATTENTIONRSMLT is supported for IP routing and for services associated with Customer IPVLAN UNIs.

SMLT subsecond failover benefits are only supported in Layer 2 networks.When routing is involved, depending on the specific routing protocol, thisconvergence time can cause network interruptions ranging from secondsto minutes.

The Nortel RSMLT feature extends the subsecond failover benefit to coretopologies by providing an active-active router concept to core SMLTnetworks.

Supported scenarios are split multilink trunk triangle, square, and full meshtopologies, with routing enabled on the core VLANs.


NN46220-511 04.01 26 June 2009


.


Routing protocols can be any of the following protocol types: IP UnicastStatic Routes, RIP1, RIP2, OSPF, BGP and IPX RIP.

In the case of core router failures, RSMLT provides packet forwarding,thus eliminating dropped packets during the routing protocol convergence.

For detailed information about RSMLT, see Configuring IP RoutingOperations.

Simple Loop Prevention ProtocolSimple Loop Prevention Protocol (SLPP) is used at the edge of anetwork to prevent loops in a SMLT network if Spanning Tree is not used.SLPP is focused on SMLT networks; however, it also works with otherconfigurations.

SLPP is supported for MERS End-Point UNIs.

SLPP is rate Limited by the L2CP Aggregate control traffic rate limiter.

Logical loops can occur in SMLT networks because of the following:

• misconfigurations (for example, when SMLT client devices areerroneously directly connected together)

• MLT is not operating correctly (for example, when a switch isconnected to the network using the default configuration without anyMLT settings)

• problems with the edge switch (for example, when MLT or some otherform of link aggregation is not working)

You can detect loops with SLPP. You can also use the Metro EthernetRouting Switch 8600 Loop Detection feature (see “Configuring VLAN LoopDetection” (page 133)).

Loop detection is achieved by detecting if a SLPP test packet—calleda SLPP-packet data unit (SLPP-PDU)— is received on a peering splitmultilink trunk switch port or on the same switch from which it originated. Ifthe packet is received by the originating switch, or by a peer aggregationswitch on the same VLAN, the port is disabled.

When you configure and enable SLPP, the switch control processor (CP)sends a SLPP-PDU to the VLAN. If there is a loop on the VLAN, theSLPP-PDU eventually returns to the originating port and is received by theCP. The CP disables that port, and a message appears on the consoleto describe the reason. After a port is disabled, it remains disabled, andmanual intervention is required to reenable the port. The port auto-enablefeature can be used to reenable the port after a predefined interval.


NN46220-511 04.01 26 June 2009


.

Simple Loop Prevention Protocol 91

Figure 24 "SLPP frame" (page 91) shows the fields of an SLPP-PDU. Thedestination address (DA) is the switch MAC address with the multicast bitset; the source address (SA) is the switch MAC address; the protocol ID(PID) default is 0x8104 and is user configurable; and the payload containsthree fields: (1) SLPP protocol version (one byte), (2) reserved (one byte),(3) VLAN ID (two bytes).

Figure 24SLPP frame

There are several factors to keep in mind when you use SLPP:

• SLPP-PDUs are forwarded on a per VLAN basis.

• Received SLPP frames on UNI/NNI ports are processed only if SLPPreception is enabled on the port. Otherwise if the port is a UNI port,these frames undergo normal OE encapsulation processing and areforwarded to the destination remote UNI.

• SLPP Ethertype check is done in addition to dest-mac lookup, toensure it is really an SLPP frame. For UNI ports, the SLPP Ethertypeis checked at the correct offset based on whether a frame is taggedor untagged.

• SLPP-PDUs are automatically forwarded on all ports of the VLANs thatare configured for SLPP.

• The SLPP-PDU destination MAC address is the switch MAC address(with the multicast bit set) while the source MAC address is the switchMAC address.

• If btag-ether-type is enabled on the B-VLAN, the SLPP-PDUs sent outon the NNI ports has the VLAN Ethertype set to 0x88A8. Otherwise theIEEE VLAN Ethertype of 0x8100 is used.

• The SLPP-PDU is sent out as a multicast packet and is constrainedto the VLAN on which it is sent.

• The SLPP-PDU payload contains the VLAN ID; a separate SLPP-PDUis sent for each VLAN.

• The SLPP-PDU packet transmission interval default is 500 millisecondsand is configurable from 500 to 5000 milliseconds.

• If an MLT port receives an SLPP PDU that it sent, the port goes down.If MLT UNI ports are configured at SLPP global level, the SLPP-PDUsare sent out only on the active MLT UNI port.


NN46220-511 04.01 26 June 2009


.


• The SLPP-PDU can be received by the originating CP or the peerSMLT CP. All other switches treat the SLPP-PDU as a normalmulticast packet, ignore it, and forward it to the VLAN.

• SLPP-PDU transmission and reception only operates on ports forwhich STP is in forwarding state (if STP is enabled on one switch inthe path).

• If you admin disable and re-enable the port on which SLPP packets arereceived, or if the port shuts down because the packet-rx-threshold isreached, then the packet-rx counter is cleared.

• You must enable SLPP packet receive on a per-port basis to detecta loop:

— Enable SLPP packet reception only on UNI Ports and SMLTaccess ports. Never enable it on SMLT IST ports, nor on any NNIports within an SMLT square or full mesh core ports.

— By default, the SLPP packet receive threshold is set to one second.It is configurable from 1 to 20 seconds.

— Vary the SLPP packet receive threshold between the two coreSMLT switches so that if a loop is detected, the access portson both switches does not go down, which avoids SMLT clientisolation.

SLPP and UNI PortsWhen you add a VLAN under global SLPP config, SLPP PDUs aretransmitted at a configured interval, on all ports with type NNI of thatVLAN. For port types UNI, if a UNI port is part of a VLAN, and that VLANis added to the SLPP configuration, SLPP PDUs are not sent out on thatUNI port. SLPP PDUs are only sent out of UNI ports when those ports areadded as part of “add-uni-port” config under global SLPP configuration.

SLPP-PDUs are sent out periodically from the UNI ports that areconfigured at the SLPP global level. The periodicity is also configurable atthe global level.

SLPP-PDUs sent out of UNI ports are always untagged. Tagged SLPPframes can be received on the UNI port if SLPP is enabled and part of theadd-uni-port list, but are processed only as long as:

• the dest-MAC of the received SLPP frame matches the chassis-Mac

• the Ethertype of the frame matches the configured SLPP Ethertype


NN46220-511 04.01 26 June 2009


.

SLPP general notes 93

If UNI ports configured at the SLPP global level are part of an MLT, theSLPP-PDUs are sent out only on the active MLT UNI port. Only the UNIMLT port that receives an incorrect SLPP PDU is taken down when the rxthreshold is reached.

SLPP general notesBecause SLPP is port-based, a port and all associated I-SID/UNIs on theeffected port if a UNI port, will be disabled if it receives SLPP-BDUs onone or more VLANs on a tagged port. For example, if the SLPP packetreceive threshold is set to five, a port is shut down if it receives fiveSLPP-PDUs from one or more VLANs on a tagged port.

SLPP does not have any hardware requirements or dependencies.

SLPP does not replace the functionality of Spanning Tree Protocol, but isa supplement to help detect and prevent loops in the SMLT environment.Nortel recommends that you use this feature in a SMLT environment only.

If you set the SLPP Rx-threshold to a high value (for example, more than50 SLPP frames) on a heavily-loaded Metro Ethernet Routing Switch 8600,the switch experiences high CPU utilization if a loop occurs. Becauseof the high Rx-threshold, the switch can become unstable during, andsometimes after, loop clearing.

For example, in a network containing an edge switch connected with32 SLTs to two Metro Ethernet Routing Switch 8600s, the followingparameters can cause 100% CPU utilization:

• SLPP is enabled with Rx-threshold of 100 SLPP frames on all SLTs

• Each SLT is in a different VLAN; routing protocol enabled on all VLANs

• The edge switch fails

Although the Metro Ethernet Routing Switch 8600 supports portrx-threshold values of up to 500 SLPP frames, high values should onlybe used on lightly-loaded switches.

The total number of SLPP sessions (UNI ports + NNI (VLANS)) supportedby the MERS-8600 is 60 sessions per chassis. However, there will be noconsistency to limit this to 60.

To prevent overloading of the CPU and COP, release 6.0 supports thecontrol of aggregate traffic from different ports to the CPU and COP. TheMetro Ethernet Routing Switch supports a packet per second rate limitwhere it discards control frames and CFM frames that are directed to theCPU and COP. SLPP is therefore rate limited.


NN46220-511 04.01 26 June 2009


.


For information about configuring SLPP with the CLI, see . For informationabout configuring SLPP with Device Manager, see “Configuring SimpleLoop Prevention Protocol” (page 220).

Considerations and limitationsThis section describes considerations and limitations of configuring VLANs,spanning tree, and link aggregation on the Metro Ethernet Routing Switch8600.

Navigation

• “VLAN implementation on the Metro Ethernet Routing Switch 8600”(page 94)

• “VLAN rules” (page 95)

• “MultiLink trunking and VLAN scalability” (page 96)

VLAN implementation on the Metro Ethernet Routing Switch 8600This section describes how to implement VLANs on the Metro EthernetRouting Switch 8600 and describes default VLANs, unassigned VLANs,and brouter ports. It also summarizes the defaults and rules regardingVLAN creation on the Metro Ethernet Routing Switch 8600.


• “Default VLAN” (page 94)

• “Unassigned VLAN” (page 94)

• “Brouter ports” (page 95)

Default VLANMetro Ethernet Routing Switch 8600 devices are factory configured sothat all ports are in a port-based VLAN called the default VLAN. Becauseall ports are in the default VLAN, the switch behaves like a Layer 2switch. The VLAN ID of this default VLAN is always 1, and it is always aport-based VLAN. The default VLAN cannot be deleted.

The default VLAN feature is only applicable to NNI ports when the NNI isnot associated with any PBB or PBT interfaces.

Unassigned VLANInternally, an Metro Ethernet Routing Switch 8600 supports a placeholderfor ports that is called an unassigned port-based VLAN. This conceptis used for ports that are removed from all port-based VLANs. Portscan belong to policy-based VLANs as well as to the unassigned VLAN.If a frame does not meet any policy criteria and there is no underlying


NN46220-511 04.01 26 June 2009


.

Considerations and limitations 95

port-based VLAN, the port belongs to the unassigned VLAN and the frameis dropped. Only ports in the unassigned VLAN have no spanning treegroup association, so these ports do not participate in Spanning TreeProtocol negotiation; that is, no Bridge Protocol Data Units (BPDU) aresent out of ports in the unassigned VLAN.

Because it is an internal construct, the unassigned VLAN cannot bedeleted. If a user-defined spanning tree group is deleted, the ports aremoved to the unassigned VLAN and can later be assigned to anotherspanning tree group. Moving the ports to the unassigned VLAN avoidscreating unwanted loops and duplicate connections. If routing is disabledin these ports, the port is completely isolated and no Layer 2 or Layer 3functionality is provided.

The concept of the unassigned VLAN is useful for security purposes orwhen using a port for monitoring a mirrored port.

Brouter portsA brouter port is actually a one-port VLAN. The difference between abrouter port and a standard IP protocol-based VLAN configured to dorouting is that the routing interface of the brouter port is not subject to thespanning tree state of the port.

A brouter port is applicable to customer IP_VLANs; it is not supportedwhen NNI is associated with PBB or PBT interfaces.

VLAN rulesThe following are VLAN rules for the Metro Ethernet Routing Switch 8600.

• In addition to the default VLAN, the Metro Ethernet Routing Switch8600 can support up to 1980 VLANs (1972 if R modules are present inthe chassis). VLAN IDs value range is from 1 to 4093.

• If you enable tagging on a port that is in a VLAN, the spanning treegroup configuration for that port is lost. To preserve VLAN assignmentof ports, enable tagging on the ports before you assign the ports toVLANs.

• A tagged port can belong to multiple VLANs and multiple spanning treegroups. When a tagged port belongs to multiple spanning tree groups,the BPDUs are tagged for all spanning tree groups except for spanningtree group 1. Under the default configuration, the default spanning treegroup is number 1.

• An untagged port can belong to only one port-based VLAN. A port in aport-based VLAN can belong to other policy-based VLANs.

• For every VLAN with MultiLink Trunking that you create, you reducethe number of available VLANs by eight.


NN46220-511 04.01 26 June 2009


.


• When Enhanced Operation mode is disabled, a VLAN cannot spanmultiple spanning tree groups; that is, the ports in the VLAN must allbe within one spanning tree group.

When Enhanced Operation mode is enabled, VLAN scalability is notaffected.

• The VLAN membership of a frame is determined by the port-basedVLAN.

MultiLink trunking and VLAN scalabilityThe maximum number of VLANs depends on whether the VLANs resideon a multilink trunk. With Enhanced Operation mode, you can nowincrease the maximum number of VLANs when you use MultiLink Trunking(MLT) to 1980 (1972 if R modules are present in the chassis) and to 989when you use SMLT. Enhanced Operation mode requires Metro EthernetRouting Switch 8600 E, M, or R modules.

CAUTIONRisk of loss of network connectivityWhen Enhanced Operation mode is enabled, only MetroEthernet Routing Switch 8600 E, M, or R modules are initialized(other modules are placed offline). To avoid losing modulesand network connectivity, replace pre-E, M, or R modules ormove the network connections to an E, M, or R module beforeenabling Enhanced Operation mode.

For instructions about configuring Enhanced Operation mode, see:

• “Configuring Enhanced Operation mode” (page 151) (Device Manager)

• “Configuring Enhanced Operation mode” (page 253) (CLI)

VLAN scaling formulasFigure 25 "Formulas for VLAN scaling" (page 97) shows the formulas usedfor VLAN scaling.


NN46220-511 04.01 26 June 2009


.

Considerations and limitations 97

Figure 25Formulas for VLAN scaling

Maximum VLAN support comparison with Enhanced OperationmodeTable 6 "Maximum numbers of port/protocol-based VLANs" (page97) shows the maximum number of VLANs available with and withoutEnhanced Operation mode.

Table 6Maximum numbers of port/protocol-based VLANs

VLAN typeMaximum VLAN support withenhanced mode enabled

Maximum VLAN support withenhanced mode disabled

MLT 1980 240

IST/SMLT 989 120

Module behavior comparison with Enhanced Operation modeTable 7 "Module behavior with and without Enhanced Operation mode"(page 97) compares the behavior of Metro Ethernet Routing Switch 8600modules with and without Enhanced Operation mode:

Table 7Module behavior with and without Enhanced Operation mode

Module type Enhanced Operationmode setting

Behavior

E, M, or Rmodule

Enable (true) The module is initialized and comes online. It can beconfigured with up to 1980 VLANs with MLT.

E, M, or Rmodule

Disable (false) The module is initialized and comes online. It can beconfigured with up to 240 VLANs with MLT.


NN46220-511 04.01 26 June 2009


.


Table 7Module behavior with and without Enhanced Operation mode (cont’d.)

Module type Enhanced Operationmode setting

Behavior

Legacy module Enable (true) The module is not initialized and remains offline. Thefollowing error message is displayed and a trap is sent:

[12/18/01 15:17:25] Card taken off-line:Slot=1 Type= -- [12/18/01 15:17:25]ERROR Code=0x3006b Task=rcStartchCardIn: can’t initialize a non ETICKETcard in enhanced operation mode

Legacy module Disable (false) The module is initialized and remains online. It can beconfigured with up to 240 VLANs with MLT.

Interoperability between operation mode and module typeR mode supports the operation of R module-specific features. Themodules (pre-E, E, M, and R) that are enabled depend on the operationmode (default, M, or R) and the system configuration. Table 8"Operation mode and module type interoperability" (page 98) shows thisinteroperability information.

Table 8Operation mode and module type interoperability

Module types

Chassisconfiguration

Operationmode

R M E Pre-E

Default — — — enabled

M — — enabled —

Same typemodulechassis

R enabled — — —

Default enabled enabled enabled enabled

M enabled enabled disabled disabled

Mixed typemodulechassis

R enabled disabled disabled disabled


NN46220-511 04.01 26 June 2009


.

99.

Configuring VLANs using DeviceManager

This section describes how to configure VLANs on an Metro EthernetRouting Switch 8600 with Device Manager includes the following topics:

• “Displaying defined VLANs” (page 99)

• “Configuring port-based VLANs” (page 101)

• “Configuring policy-based VLANs” (page 107)

• “Managing a VLAN” (page 119)

• “Managing VLAN bridging” (page 137)

• “Configuring Enhanced Operation mode” (page 151)

Displaying defined VLANsTo display all defined VLANs, their configurations, and their current status:

Step Action

1 From the Device Manager menu bar, choose VLAN > VLANs.

The VLAN box appears with the Basic tab displayed, whichshows all defined VLANs (Figure 26 "VLAN, Basic tab" (page100)).

The VLAN box appears with the Basic tab displayed, whichshows all defined VLANs.


NN46220-511 04.01 26 June 2009


.

100 Configuring VLANs using Device Manager

Figure 26VLAN, Basic tab

--End--

For more information, see Table 9 "VLAN, Basic tab fields" (page 100).

Table 9VLAN, Basic tab fields

Field Description

Id VLAN ID for the VLAN.

Name Name of the VLAN.

IfIndex The logical interface index assigned to the VLAN.

Color Identifier A proprietary color scheme to associate a color with the VLAN.Color does not affect how frames are forwarded.

Type Type of VLAN:

• byPort: This VLAN type is the only one supported for EVPNservices.

• byIpSubnet: This VLAN type cannot be used for EVPN services.

• byProtocolId: This VLAN type cannot be used for EVPNservices.

• bySrcMac: This VLAN type cannot be used for EVPN services.

• bySvlan: This VLAN type cannot be used for EVPN services.

StgId The ID of the spanning tree group to which the VLAN belongs.


NN46220-511 04.01 26 June 2009


.

Configuring port-based VLANs 101

Table 9VLAN, Basic tab fields (cont’d.)

Field Description

PortMembers The slot/port of each possible VLAN member.

ActiveMembers The slot/port of each active VLAN member, including all staticmembers and potential members meeting the policy.

StaticMembers Slot/port of each static (always) member of a protocol-based VLAN.

NotAllowToJoin The slot/ports that are never allowed to become a member of theprotocol-based VLAN.

OspfPassiveMembers The slot/ports of each OSPF passive member.

ProtocolId Specify the network protocol for protocol-based VLANs. This valueis taken from the Assigned Numbers RFC.

• ip (IP version 4)

• appleTalk (AppleTalk on Ethernet Type 2 and Ethernet SNAPframes)

• decLat (DEC LAT protocol)

• decOther (Other DEC protocols)

• sna802dot2 (IBM SNA on IEEE 802.2 frames)

• snaEthernet2 (IBM SNA on Ethernet Type 2 frames)

• netBIOS (NetBIOS protocol)

• xns (Xerox XNS)

• vines (Banyan VINES)

• ipv6 (IP version 6)

• usrDefined (user-defined protocol)

• RARP (Reverse Address Resolution Protocol)

• PPPoE (Point-to-Point Protocol over Ethernet)

if the VLAN type is port-based, None is displayed in the Basic tabProtocolId field.

SubnetAddr The source IP subnet address (IP subnet-based VLANs only).

SubnetMask The source IP subnet mask (IP subnet-based VLANs only).

Configuring port-based VLANsA port-based VLAN is a VLAN in which the ports are explicitly configuredto be in the VLAN.


NN46220-511 04.01 26 June 2009


.


This section describes how you can create and configure port-basedVLANs using the following procedures.

• “Creating a port-based VLAN” (page 102)

• “Configuring an IP address for a VLAN” (page 106)

Creating a port-based VLANTo create a port-based VLAN:

Step Action


The VLAN box appears with the Basic tab displayed, whichshows all defined VLANs (Figure 26 "VLAN, Basic tab" (page100)).

2 In the Basic tab, click Insert.

The VLAN, Insert Basic box appears (Figure 27 "VLAN, InsertBasic box" (page 103)).


NN46220-511 04.01 26 June 2009


.


Figure 27VLAN, Insert Basic box

3 In the Id box, enter an unused VLAN ID, or use the ID provided.

• (Optional) In Name, type the VLAN name, or use the nameprovided.

• (Optional) In Color Identifier, click the down arrow andchoose a color from the list, or use the color provided.


NN46220-511 04.01 26 June 2009


.


4 In the StgId box, type or select the spanning tree group ID of theVLAN.

5 In the Type box, select byPort.

6 In the PortMembers box, click the ellipsis (...).

The VlanPortMembers box appears (Figure 28 "VlanPortMembers" (page 104)).Figure 28VlanPortMembers

7 Click the ports that are always members. The ports that areselected are recessed, while the non selected ports are notrecessed. Port numbers that are dimmed cannot be selected asVLAN port members. (For example, you cannot select ports thatdo not have the same spanning tree group ID as that of the newVLAN.)

8 Click OK.

The Port Membership box closes and the port members appearin the Insert Basic box.

9 In the VLAN, Insert Basic box, click Insert.

The Insert box closes and the new VLAN is displayed in theBasic tab.

10 In the Basic tab, click Close.

The VLAN is configured and the VLAN box closes.

For more information, see Table 10 "VLAN, Insert Basic fields"(page 104).

--End--

Table 10VLAN, Insert Basic fields

Field Description

Id A value that uniquely identifies the virtual LAN associated withthis entry. This value corresponds to the lower 12 bits in the IEEE802.1Q VLAN tag.


NN46220-511 04.01 26 June 2009


.


Table 10VLAN, Insert Basic fields (cont’d.)

Field Description

Name An assigned name for this VLAN.

Color Identifier An assigned color code for this VLAN. The value of this object isused by the VLAN Manager GUI tool.

Stg Id Indicates the Spanning Tree Group (STG) used by this VLAN todetermine the state of its ports. If this VLAN is not associated withan STG, set StgId to zero. This field is shown only if the switch isin STG mode.

MstpInstance Indicates the MSTP instance for the VLAN. This field is shown onlyif the switch is in MSTP mode.

Type The type of VLAN, distinguished according to the policy used todefine its port membership.

PortMembers The set of ports that are members (static or dynamic) of this VLAN.

StaticMembers The set of ports that are static members of this VLAN. A staticmember of a VLAN is always active and is never aged out.

NotAllowtoJoin The set of ports that are not allowed to become members of thisVLAN.

OspfPassiveMembers The set of ports in the VLAN that are designated as OSPF passive

SubnetAddr The IP subnet address of this VLAN. This value is meaningful onlyif Type is equal to byIpSubnet. For other VLAN types it must havethe value 0.0.0.0.

SubnetMask The IP subnet mask of this VLAN. This value is meaningful only ifType is equal to byIpSubnet. For other VLAN types it must have thevalue 0.0.0.0.

ProtocolId The protocol identifier of this VLAN. This value is meaningful only ifType is equal to byProtocolId. For other VLAN types it must havethe value none.

UserDefinedPid When ProtocolId is set to usrDefined in a protocol-based VLAN, thisfield represents the 16 bit user defined protocol identifier.

Encap This is the encapsulation type for user defined protocol-basedVLANs. This is not meaningful for other types of VLANs. The defaultvalue is null.

AgingTime The timeout period (in seconds) used for aging out FDB entries ofthis VLAN.

QosLevel Used to specify the QoS level which packets, carried in this VLAN,should be processed with.

FirewallVlanType The firewall VLAN type for port-based VLANs.

FirewallClusterId Firewall cluster ID.


NN46220-511 04.01 26 June 2009


.


Configuring an IP address for a VLANTo configure an IP address for a VLAN:

Step Action


The VLAN box appears with the Basic tab displayed (Figure 26"VLAN, Basic tab" (page 100)).

2 In the Basic tab, select the VLAN for which you are configuringan IP address.

The VLAN is highlighted.

3 Click IP.

The IP, VLAN box for the selected VLAN appears with the IPAddress tab displayed (Figure 29 "IP, VLAN box" (page 106)).Figure 29IP, VLAN box

4 Click Insert.

The Insert IP Address box appears (Figure 30 "IP, VLAN, InsertIP Address box" (page 106)).Figure 30IP, VLAN, Insert IP Address box

5 Enter an IP address and net mask for routing purposes.

6 Click Insert.

The Insert IP box closes and the IP Address and Net Maskappear in the IP, VLAN box.

7 In the IP, VLAN box and the VLAN box, click Close.

The IP subnet-based VLAN is configured.


NN46220-511 04.01 26 June 2009


.

Configuring policy-based VLANs 107

For more information, see Table 11 "IP, VLAN fields" (page 107).

--End--

Table 11IP, VLAN fields

Field Description

Interface Identifies the interface to which this entry is applicable.

Ip Address The IP address to which addressing informationpertains.

NetMask The subnet mask associated with the IP address of thisentry. The value of the mask is an IP address with allthe network bits set to 1 and all the hosts bits set to 0.

BcastAddrFormat The IP broadcast address format used on thisinterface.

ReasmMaxSize The size of the largest IP packets which this entitycan reassemble from incoming IP fragmented packetsreceived on this interface.

VlanId Identifies the virtual LAN associated with this entry.This value corresponds to the lower 12 bits in the IEEE802.1Q VLAN tag.

BrouterPort Indicates whether this entry corresponds to a brouterport (as opposed to a routable VLAN). This valuecannot be changed after the row is created.

Configuring policy-based VLANsA policy-based VLAN consists of ports that are dynamically added to theVLAN on the basis of the traffic coming into the port. Policy-based VLANtypes include:

• Protocol-based

• User-defined protocol-based

• MAC address-based

• IP subnet-based

• sVLAN-based

ATTENTIONThe policy-based VLANs are only supported for non EVPN service that is,B-VLAN, PBT-VLAN, PLSB-VLAN and MMRP-VLANs cannot belong to thesetypes of VLANs and can only be port-based VLANs.

This section describes how you can create and configure policy-basedVLANs using the following procedures.


NN46220-511 04.01 26 June 2009


.


• “Creating a source IP subnet-based VLAN” (page 108)

• “Creating a protocol-based VLAN” (page 109)

• “Configuring user-defined protocol-based VLANs” (page 111)

• “Creating a source MAC address-based VLAN” (page 114)

Creating a source IP subnet-based VLANTo create a source IP subnet-based VLAN:

Step Action


The VLAN box appears with the Basic tab displayed (see Figure26 "VLAN, Basic tab" (page 100).


The VLAN, Insert Basic box appears (see Figure 27 "VLAN,Insert Basic box" (page 103).

3 In the Type box, select byIpSubnet.

4 In the Id box, type the VLAN ID.

5 (Optional) In the Name box, type the VLAN name.

If no name is entered, a default name is created.

6 (Optional) In the Color Identifier box, select the color or use thecolor provided.

This color is used by VLAN Manager to visually distinguish theVLANs in a network.

7 In the StgId box, select the spanning tree group ID of the VLAN.

8 Specify port membership by clicking the ellipsis (...) for one ofthe following:

• PortMembers (use this for VLAN by IpSubnet, Protocolid, orSrcMac)

• StaticMembers

• NotAllowedToJoin

The VlanPortMembers box appears (Figure 31 "VlanPortMembers" (page 109).


NN46220-511 04.01 26 June 2009


.


Figure 31VlanPortMembers

9 Click each port to choose the desired color:

• Yellow—Potential members

• Green—Always members, static

• Red—Never members, not allowed to join

In a source IP subnet-based VLAN, a potential member becomesan active member of the VLAN when a frame is received fromthe specified source IP address.

10 Click OK.

The Port Membership box closes, and the port members appearsin the VLAN, Insert Basic box.

11 In the SubnetAddr box, enter an IP address for the VLAN.

12 In the SubnetMask box, enter an IP subnet mask for the VLAN.

13 In the AgingTime box, enter the timeout period in seconds foraging out the dynamic VLAN member ports, or use the 600second default.

14 (Optional) In the QosLevel box, select a Quality of Service level(0 to 6).

15 Click Insert.

The VLAN, Insert Basic box closes, and the source IPsubnet-based VLAN appears in the Basic tab.

--End--

Creating a protocol-based VLANTo create a protocol-based VLAN:

Step Action





NN46220-511 04.01 26 June 2009


.



3 In the Type box, select byProtocolId.

4 In the Id box, type the unique VLAN ID, or use the ID provided.

5 (Optional) In the Name box, type the VLAN name, or use thename provided.

6 (Optional) In the Color Identifier box, select the color, or usethe color provided.


7 In the StgID box, select the spanning tree group ID of the VLAN.

8 To specify the VLAN port membership, click the ellipsis (...) forone of the following fields.

• Port Members

• StaticMembers


The VlanPortMembers box appears (see Figure 35"VlanPortMembers" (page 117)).

9 In the VlanPortMembers box, click each port button to choosethe desired membership color.

• Yellow: Potential members—dynamic (potential members aretreated as always members).

• Green: Always members—static

• Red: Never members—not allowed to join

When you have two VLANs with potential members and youwant to move ports from one VLAN to the other, you must firstchange their port membership to Never. Then you can assignthe ports to the other VLAN.

When a protocol-based VLAN is created, all ports in theunderlying STG are automatically added as potential membersif they are not already members of an existing protocol-basedVLAN of the same type.

In a protocol-based VLAN for a Metro Ethernet Routing Switch8600 module, a potential member becomes an active member ofthe VLAN when a frame of the specified protocol is received.

10 Click OK.

The VlanPortMembers box closes and the port members areadded to the Insert Basic box.


NN46220-511 04.01 26 June 2009


.


11 In the ProtocolId box, select a protocol ID.

To configure a non-standard protocol, see “Configuringuser-defined protocol-based VLANs” (page 111).

12 In the AgingTime box, specify the timeout period, in seconds,for aging out the dynamic member ports of the VLAN, or use thedefault of 600 seconds.

13 In the QosLevel box, select a level.

14 Click Insert.

The VLAN, Insert Basic box closes, and the protocol-basedVLAN is added to the Basic tab of the VLAN box.

15 Click Close.

The VLAN is configured and the VLAN box closes.

--End--

Configuring user-defined protocol-based VLANsYou can create user-defined protocol-based VLANs in support of networkswith non-standard protocols.

To create a user-defined protocol-based VLAN:

Step Action



2 On the Basic tab, click Insert.


3 In the Type box, select byProtocolId.

4 To specify the VLAN port membership, click the ellipsis (...) forone of the following fields.

• Port Members

• StaticMembers




NN46220-511 04.01 26 June 2009


.


5 In the VlanPortMembers box, click each port button to achievethe desired membership color.

• Yellow: Potential members—dynamic

• Green: Always members—static

• Red: Never members—not allowed to joinIn a user-defined protocol-based VLAN on a Metro EthernetRouting Switch 8600 module, a potential member becomesan active member when a frame from the specified protocol isreceived.

6 In the ProtocolId box, select usrDefined.

The UserDefinedPID field becomes editable and the Encap fieldbecomes active. See the following figure, (Figure 32 "VLAN,Insert Basic" (page 113).


NN46220-511 04.01 26 June 2009


.


Figure 32VLAN, Insert Basic

7 In the UserDefinedPID box, enter the protocol ID for the protocolin the format 0x (protocol type in hexadecimal).

In the Metro Ethernet Routing Switch 8600 modules, the 16-bitPID assigned to a protocol-based VLAN specifies either anEthertype or a SNAP PID, depending on whether the frameencapsulation is Ethernet 2, 802.2, or LLC-SNAP, respectively.


NN46220-511 04.01 26 June 2009


.


The following PIDs are not valid:

• PID0x0000 through 0x05dc: overlaps with the 802.3 framelength

• PIDs of predefined protocols (for example, IP, AppleTalk)

• PID 0x8100: reserved by 802.1Q to identify tagged frames

• PID0x9000: used by the diagnostic loopback frames

• PID0x8808: used by 802.3x pause frames

8 In the AgingTime box, specify the timeout period, in seconds,for aging out the dynamic member ports of the VLAN, or use thedefault of 600 seconds.

9 In the QosLevel box, select a level.

10 Click Insert.

The VLAN, Insert Basic box closes, and the protocol-basedVLAN is added to the Basic tab of the VLAN box.

11 Click Close.

The non-standard protocol-based VLAN is configured.

--End--

Creating a source MAC address-based VLANBefore creating a source MAC-based VLAN, you must first enable sourceMAC address-based VLANs in the system.


• “Enabling source MAC address-based VLANs on the system” (page114)

• “Configuring a source MAC address-based VLAN” (page 116)

• “Creating a source MAC address-based VLAN using batch files” (page118)

Enabling source MAC address-based VLANs on the systemTo enable source MAC address-based VLANs on the system:

Step Action

1 From the Device Manager menu bar, choose Edit > Chassis.

The Chassis box appears with the System tab displayed.

2 Click the System Flags tab.


NN46220-511 04.01 26 June 2009


.


The System Flags tab appears (see Figure 33 "Chassis, SystemFlags tab" (page 115)).Figure 33Chassis, System Flags tab

3 Clear the GlobalFilterEnable check box.

• Global filters are disabled when the GlobalFilterEnable checkbox is cleared.

• Global filters are enabled when the GlobalFilterEnable checkbox is selected.

4 Click Apply.

5 Select the VlanBySrcMacEnable check box.

• Source MAC-based VLANs are enabled when theGlobalFilterEnable check box is selected.

6 Click Apply.

The Chassis box closes and source MAC address-based VLANsare enabled on the system.

--End--


NN46220-511 04.01 26 June 2009


.


Configuring a source MAC address-based VLANBefore configuring a source MAC address-based VLAN, you must firstenable source MAC address-based VLANs on the system (see “Enablingsource MAC address-based VLANs on the system” (page 114).

To configure a source MAC-address-based VLAN:

Step Action



2 Click Insert.


3 In the Type box, select bySrcMac.

The fields needed to set up source MAC-based VLANs becomeeditable. See Figure 34 "VLAN, Insert Basic, bySrcMac" (page116).Figure 34VLAN, Insert Basic, bySrcMac

4 In the Id box, enter a unique VLAN ID.


NN46220-511 04.01 26 June 2009


.


5 (Optional) In the Name box, type the VLAN name, or use theone provided.

6 (Optional) In the Color Identifier box, select a color, or use theone provided.


7 In the StgId box, click the down arrow, and select a spanningtree group ID for the VLAN.

8 To specify the VLAN port membership, click the ellipsis (...) forone of the following fields:

• Port Members

• StaticMembers



9 Click each port to choose the desired color.

• Yellow—Potential members, dynamic

• Green—Always members, static

• Red—Never members, not allowed to join

Figure 35VlanPortMembers

10 Click Ok.

The VlanPortMembers box closes, and the selected portmembers appear in the VLAN, Insert Basic box.

11 In the Aging Time box, specify the timeout period in secondsfor aging out the dynamic member ports of the VLAN, or use thedefault of 600 seconds.

12 (Optional) In the QosLevel box, select a Quality of Service level,or use the default, level 1.

13 Click Insert.


NN46220-511 04.01 26 June 2009


.


The VLAN, Insert Basic box closes, and the VLAN appears onthe Basic tab.

14 On the VLAN Basic tab, select the newly created VLAN.


15 Click Mac.

The MAC, VLAN box appears.

16 Click Insert.

The Insert MAC VLAN box appears.

17 In the MacAddr box, specify a source MAC address for theVLAN.

18 Click Insert.

The Insert MAC VLAN box closes and the MAC address appearsin the MAC, VLAN box.

19 Click Close.

The MAC, VLAN and VLAN boxes close, and the Source MACaddress-based VLAN is configured.

--End--

In a source MAC-based VLAN, a potential member becomes an activemember of the VLAN when a frame with the specified source MACaddress is received.

Creating a source MAC address-based VLAN using batch filesBefore configuring a source MAC address-based VLAN, you must firstenable source MAC address-based VLANs on the system (see “Enablingsource MAC address-based VLANs on the system” (page 114)).

To create a source MAC address-based VLAN using batch files:

Step Action


The VLAN box appears with the Basic tab displayed (see Figure26 "VLAN, Basic tab" (page 100)).

2 In the VLAN Basic tab, select a source MAC address-basedVLAN.


3 Click Mac.

The MAC, VLAN box appears.


NN46220-511 04.01 26 June 2009


.

Managing a VLAN 119

4 Click File.

The Edit MAC VLAN box appears.

5 Do one of the following:

• To add a MAC address from a file, select Add From File anduse the selection box to browse for the file location.

• To save a MAC address to a file, select it, select Save toFile, and use the selection box to browse for a save location.

• To delete a MAC address, select it, and select DeleteMembers on Device.

6 Click Close.

The Edit MAC box closes.

7 Click Close in the MAC VLAN, and VLAN boxes.

The source MAC address-based VLAN is configured.

--End--

Managing a VLANAfter you have configured a VLAN, you may wish to enable features toimprove VLAN performance. This section describes how to configureadvanced VLAN operations, such as forwarding, MAC addressauto-learning, and Loop Detection.


• “Changing VLAN port membership” (page 120)

• “Configuring advanced VLAN features” (page 120)

• “Configuring VLAN forwarding” (page 123)

• “Configuring a VLAN to accept tagged or untagged frames” (page 125)

• “Configuring Untagging Default VLAN on a Tagged Port” (page 128)

• “Configuring MAC address auto-learning on a VLAN” (page 129)

• “Modifying auto-learned MAC addresses” (page 131)

• “Configuring VLAN Loop Detection” (page 133)

• “Configuring directed broadcast on a VLAN” (page 135)

ATTENTIONAfter you create a VLAN, you cannot change the VLAN type. You must firstdelete the VLAN, and then create a new VLAN of a different type.


NN46220-511 04.01 26 June 2009


.


Changing VLAN port membershipTo change VLAN port membership:

Step Action

1 On the Device Manager menu bar, choose VLAN > VLANs.

The VLAN box appears with the Basic tag displayed (see Figure26 "VLAN, Basic tab" (page 100)).

The VLAN box appears with the Basic tag displayed.

2 Double-click the PortMember number for the VLAN whose portsyou want to change.

The PortMembers box appears (Figure 36 "PortMembers box"(page 120)).Figure 36PortMembers box

3 Click the port members you wish to add or remove.

4 Click Ok.

The Port Member box closes and the changes appear in theBasic tab.

5 Click Apply.

The VLAN’s port membership is changed and the VLAN boxcloses.

--End--

Configuring advanced VLAN featuresThe Advanced tab contains information which can be useful introubleshooting—VlanOperationAction can be especially useful.


NN46220-511 04.01 26 June 2009


.

Managing a VLAN 121

Step Action



2 Click the Advanced tab.

The Advanced tab appears (Figure 37 "VLAN, Advanced tab"(page 121)).

3 Configure the parameters as required.Figure 37VLAN, Advanced tab

For more information, see Table 12 "VLAN, Advanced tab fields"(page 121).

--End--

Table 12VLAN, Advanced tab fields

Field Description

Id The VLAN ID.

Name The name of the VLAN.

IfIndex The logical interface index assigned to the VLAN.

Type Type of VLAN:

• byPort

• byIpSubnet

• byProtocolId

• bySrcMac

• bySvlan

• byIds


NN46220-511 04.01 26 June 2009


.


Table 12VLAN, Advanced tab fields (cont’d.)

Field Description

ProtocolId Specify the network protocol for protocol-based VLANs.This value is taken from the Assigned Numbers RFC.

• ip (IP version 4)

• appleTalk (AppleTalk on Ethernet Type 2 andEthernet SNAP frames)

• decLat (DEC LAT protocol)

• decOther (Other DEC protocols)

• sna802dot2 (IBM SNA on IEEE 802.2 frames)

• snaEthernet2 (IBM SNA on Ethernet Type 2frames)

• netBIOS (NetBIOS protocol)

• xns (Xerox XNS)

• vines (Banyan VINES)

• ipv6 (IP version 6)

• usrDefined (user-defined protocol)

• RARP (Reverse Address Resolution protocol)

• PPPoE (Point-to-point protocol over Ethernet)

If the VLAN type is port-based, None is displayed in theBasic tab ProtocolId field.

Encap Specifies the encapsulation method. Values are:

• Ethernet II

• SNAP

• LLC

• RAW

AgingTime The timeout period in seconds for aging out thedynamic member ports of policy-based VLANs.

MacAddress The MAC address assigned to the virtual routerinterface for this VLAN. This field is relevant only whenthe VLAN is configured for routing. This MAC addressis used as the Source MAC in routed frames, ARPreplies, or RIP and OSPF frames.


NN46220-511 04.01 26 June 2009


.

Managing a VLAN 123

Table 12VLAN, Advanced tab fields (cont’d.)

Field Description

Vlan Operation Action One of the following VLAN-related actions:

• flushMacFdb—flush MAC forwarding table for VLAN

• flushArp—flush ARP table for VLAN

• flushIp—flush IP route table for VLAN

• flushDynMemb—flush dynamic VLAN port members

• all—flush all tables for VLAN

• flushSnoopMem—flush dynamically learnedmulticast group membership

• triggerRipUpdate—set automatic triggered updatesfor RIP

• flushSnoopMRtr—flush learned multicast routerports

Result Result code for action.

UserDefinedPid Specifies the 16-bit user-defined network protocolidentifier when the ProtocolID field is set to usrDefinedfor a protocol-based VLAN type.

UserPriority User-assigned priority level.

QosLevel User-assigned Quality of Service level.

FirewallVlanType The firewall VLAN type for port-based VLANs.

FirewallClusterId Firewall cluster ID.

Configuring VLAN forwardingThe VLAN Forwarding tab configures filtering for the VLAN.

Step Action



2 Click the Forwarding tab.

The Forwarding tab appears (Figure 38 "VLAN, Forwarding tab"(page 124)).


NN46220-511 04.01 26 June 2009


.


Figure 38VLAN, Forwarding tab

Table 13 "VLAN, Forwarding tab" (page 124) describes the fieldsin the Forwarding tab, as well as those displayed by clicking theFilter button.

Table 13VLAN, Forwarding tab

Field Description

Address An address for which the filter has forwardingor filtering information.

VlanId The ID of the VLAN.

Port The port number.

Monitor Select true or false to copy packets with a MACaddress in the source or destination field. Usedwith port mirroring.

QoSLevel User-assigned Quality of Service level.

SmltRemote Specifies whether you want to use split multilinktrunking.

Status Values include:

• self—one of the bridge addresses

• learned—a learned entry that is beingused

• mgmt—a static entry

3 Click Filter.

The VLAN, Forwarding—Filter tab appears (Figure 39 "VLAN,Forwarding, Filter tab" (page 125)).


NN46220-511 04.01 26 June 2009


.

Managing a VLAN 125

Figure 39VLAN, Forwarding, Filter tab

4 Configure the filter.

5 Click Filter.

--End--

Configuring a VLAN to accept tagged or untagged framesPerform the following steps to configure a VLAN to accept tagged oruntagged frames from a port:

Step Action

1 In the Device Manager main window, select the port.

The port is highlighted.

2 From the Device Manager menu bar, choose Edit > Port >General.

The Port box appears with the Interface tab displayed (seeFigure 40 "Port, Interface tab" (page 126)).


NN46220-511 04.01 26 June 2009


.


Figure 40Port, Interface tab

3 Click the VLAN tab.

The VLAN tab appears.

The VLAN tab appears (Figure 41 "Port, VLAN tab" (page 127)).


NN46220-511 04.01 26 June 2009


.

Managing a VLAN 127

Figure 41Port, VLAN tab

4 To configure tagging on the port, select the PerformTaggingcheck box. This setting is applied to all VLANs associated withthe port.

If the check box is selected, tagging is enabled. All frames sentfrom this port are tagged. You can either discard the taggedframes (step 5) or forward them to a VLAN (go to step 6).

• If the check box is cleared, tagging is disabled. The port doesnot send tagged frames. The switch removes the tag beforesending the frame out of the port. You can either discard theuntagged frames (go to step 5) or forward them to a VLAN(go to step 6).

ATTENTIONWhen you enable tagging on an untagged port, the previousconfiguration of VLANs, STGs, and MLTs is lost for that port. Inaddition, the port resets and runs Spanning Tree Protocol, thusbreaking connectivity while the protocol goes through the usualblocking and learning states before the forwarding state.

5 Do one of the following:

• To discard tagged frames on a port for which tagging isdisabled, select DiscardTaggedFrames.

• To discard untagged frames on a port for which tagging isenabled, select DiscardUntaggedFrames.

To optimize performance, on untagged ports in configurationsin which you do not expect to see tagged frames, setDiscardTaggedFrames to true. However, on untagged ports forinterconnecting switches, set DiscardTaggedFrames to false.


NN46220-511 04.01 26 June 2009


.


6 To designate a default VLAN to associate with discarded frames,enter a VLAN ID in the Default VLAN ID box (or use the defaultVLAN 1).

7 Click Apply > Close.

Tagging is configured for the port.

For more information, see Table 14 "Port, VLAN tab" (page 128).

--End--

Table 14Port, VLAN tab

Field Description

PerformTagging Enable or disable the port on the current VLAN to performtagging

VlanNames Identifies which VLANs this port is assigned. Each VLAN ID isstored as a two octet value. The first octet in the pair holds bits15 to 8 of the VLAN ID, the second octet holds bits 7 to 0 ofthe VLAN ID.

DiscardTaggedFrames Determines how to process tagged frames received on thisaccess port. When the flag is set, these frames are discardedby the forwarding process. When the flag is reset, these framesare processed normally.

DiscardUntaggedFrames Determines how to process untagged frames received on thistagged port. When the flag is set, these frames are discardedby the forwarding process. When the flag is reset, these framesare assigned to the VLAN specified by the DefaultVlanId.

UntagDefaultVLAN Enables or disables egress tagging on the default VLAN of theport.

DefaultVlanId The VLAN ID assigned to untagged frames received on thistrunk port. This field is meaningless when the port is not atrunk port.

LoopDetect Enables loop detection.

ArpDetect Enables or disables the ARP loop detection feature on this port.If a loop is detected, the port is disabled. For more informationabout this feature, see Configuring IP Routing Operations.

LoopDetectAction This value is used to specify the action which needs to betaken once a MAC loop is detected on a specific port. Theyinclude portDown, vlanBlock, and macDiscard.

Configuring Untagging Default VLAN on a Tagged PortThe Untagging Default VLAN on a Tagged Port feature separatesuntagged packets originating from a PC from the tagged packetsoriginating from an IP phone.


NN46220-511 04.01 26 June 2009


.

Managing a VLAN 129

To enable this feature with Device Manager:

Step Action

1 In Device Manager, select a port.

2 Right-click and choose Edit > Port > General.

The Port box appears.

3 Click the VLAN tab (Figure 42 "VLAN, UntagDefaultVlan" (page129)).

4 Select UntagDefaultVlan.

5 Click Apply.Figure 42VLAN, UntagDefaultVlan

--End--

Configuring MAC address auto-learning on a VLANYou can use MAC address auto-learning to define VLAN ports that youwant to automatically learn MAC addresses.

To configure MAC address learning for a VLAN:


NN46220-511 04.01 26 June 2009


.


Step Action

1 From the Device Manager menu bar, choose VLAN > MACLearning.

The VLanMacLearning box appears with the Manual Edit tabdisplayed (Figure 43 "VLanMacLearning, Manual Edit tab" (page130)).Figure 43VLanMacLearning, Manual Edit tab

2 Click Insert.

The VLAN MAC Learning, Insert Manual Edit box appears(Figure 44 "VLanMacLearning, Insert Manual Edit box" (page130)).Figure 44VLanMacLearning, Insert Manual Edit box

3 In the Address box, enter the source MAC address.

4 In the Ports box, click the ellipsis ( ... ).

The BridgeManualEditPorts box appears and shows theavailable ports (Figure 45 "BridgeManualEditPorts box" (page131)).


NN46220-511 04.01 26 June 2009


.

Managing a VLAN 131

Figure 45BridgeManualEditPorts box

5 Click the ports you want to configure to use VLAN MAC learning,and then click Ok.

The BridgeManualEditPorts box closes and the port numbers areadded to the Insert Manual Edit box.

6 Click Insert.

The Insert Manual Edit box closes and the MAC address andports are added to the VLAN MAC Learning Manual Edit box.

7 Click Close.

VLAN MAC learning is configured and the box closes.

For more information, see Table 15 "VLAN MAC Learning, InsertManual Edit tab fields" (page 131)

--End--

Table 15VLAN MAC Learning, Insert Manual Edit tab fields

Field Description

Address The source MAC address of an entry.

PortsThe allowed ports on which the MAC address of this entry arelearned.

Modifying auto-learned MAC addressesUse the Auto Learn tab to change a MAC address that was automaticallylearned to one that can be manually edited.

To modify a MAC address that was automatically learned:


NN46220-511 04.01 26 June 2009


.


Step Action

1 On the Device Manager menu bar, choose VLAN > MACLearning.

The VlanMacLearning box appears with the Manual Edit tabdisplayed (see Figure 43 "VLanMacLearning, Manual Edit tab"(page 130)).

2 Click the Auto Learn tab.

The Auto Learn tab appears and shows automatically learnedMAC addresses (Figure 46 "VLanMacLearning, Auto Learn tab"(page 132)).Figure 46VLanMacLearning, Auto Learn tab

3 Double-click in the Auto Learn Action field on the address youwant to change, and select ConvertToManualEdit from the list.

4 Click Apply.

The Auto Learn Action is changed.

For more information, see Table 16 "VLAN Auto Learn tab fields"(page 132).

--End--

Table 16VLAN Auto Learn tab fields

Field Description

Address The source MAC address of the auto-learned entries.


NN46220-511 04.01 26 June 2009


.

Managing a VLAN 133

Table 16VLAN Auto Learn tab fields (cont’d.)

Field Description

Port The port where the MAC address was learned.

Auto Learn Action This field is for converting an auto-learned MACaddress entry to a manual edit MAC address entry.The variable provides a mechanism for you to move aMAC address entry from the auto-learned table to theManual Edit table.

Settings:

• None

• convertToManualEdit

Configuring VLAN Loop DetectionOn a per-port basis, the Loop Detection feature detects MAC addressesthat are looping from one port to other ports. After a loop is detected, theport on which the MAC addresses were learned is disabled. Additionally,if a MAC address is found to loop, the MAC address is disabled for thatVLAN. The Loop Detection feature must only be enabled on SMLT ports,and never used on IST ports or core SMLT square or full mesh ports.

You can also use Simple Loop Prevention Protocol to detect VLAN loops.

To configure Loop Detection using Device Manager, do the following:

Step Action

1 In Device Manager, select a port and right-click.

A menu appears.

2 Select Edit General, and then click the VLAN tab.

The VLAN tab appears (Figure 47 "Port, VLAN loop detect"(page 134)). Table 14 "Port, VLAN tab" (page 128) describes thefields in the VLAN tab.


NN46220-511 04.01 26 June 2009


.


Figure 47Port, VLAN loop detect

3 Select the LoopDetect check box.

4 In the LoopDetectAction box, select the action to be taken ifa loop is detected.

Nortel recommends that you select portDown as opposed toa VLAN shutdown (vlanBlock). If vlanBlock is selected, theVLAN is shut down, not the port. The access switch continuesto forward traffic to the port. If portDown is selected, then theaccess switch recovers by detecting the failed link.

5 Click Apply.

6 To view loop detection information, click Loop Detect.

The Loop Detected tab appears (Figure 48 "Loop Detected"(page 135)), showing loop detection information.


NN46220-511 04.01 26 June 2009


.

Managing a VLAN 135

Figure 48Loop Detected

For more information, see Table 17 "LoopDetected dialog boxparameters" (page 135).

--End--

Table 17LoopDetected dialog box parameters

Field Description

PortIndex Port number.

VlanId The assigned ID of the VLAN.

Value Specifies that a loop has been detected (yes), orthat no loop has been detected (no).

Configuring directed broadcast on a VLANYou can enable or disable directed broadcast traffic forwarding for an IPinterface on the Direct Broadcast tab.

To configure directed broadcast for a VLAN:

Step Action



The VLAN box appears with the Basic tab displayed.

2 Select a VLAN.


3 Click IP.


NN46220-511 04.01 26 June 2009


.


The IP, VLAN box appears with the IP Address tab displayed(Figure 29 "IP, VLAN box" (page 106)).

4 Click the Direct Broadcast tab.

The Direct Broadcast tab appears.

The Direct Broadcast tab appears (Figure 49 "IP, VLAN, DirectBroadcast tab" (page 136)).Figure 49IP, VLAN, Direct Broadcast tab

5 Select DirectBroadcastEnable.

• If selected, IP-directed broadcasts are enabled.

• If cleared, IP-directed broadcasts are suppressed.

Multiple VLANs or IPs in the same subnet but in differentswitches must be configured simultaneously.

6 Click Apply, and then click Close.

Directed broadcast is configured for the VLAN.

For more information, see Table 18 "IP, VLAN Direct Broadcasttab" (page 136).

--End--

Table 18IP, VLAN Direct Broadcast tab

Field Description

DirectBroadcastEnable If enabled, an Isolated Routing Port (IRP) canforward directed broadcast traffic. A directedbroadcast is a frame sent to the subnetbroadcast address on a remote IP subnet. Bydisabling or suppressing directed broadcaston an interface, all frames sent to the subnetbroadcast address for a local router interfaceare dropped. Disabling this function protectsa host from possible denial of service (DoS)attacks.


NN46220-511 04.01 26 June 2009


.

Managing VLAN bridging 137

Field Description

This feature is enabled by default. With thefeature enabled, the CPU does not receive acopy of the directed broadcast. As a result, theswitch does not respond to a subnet broadcastping sent from a remote subnet.

Managing VLAN bridgingBridging occurs at Layer 2 of the Open Systems Interconnect (OSI) model,in which only the MAC address in the packet header is considered whenforwarding. With the Metro Ethernet Routing Switch 8600, all bridgingis done within the context of a VLAN, in which each VLAN has its ownbridging configuration and forwarding table.


• “Configuring the forwarding database timeout” (page 137)

• “Viewing the forwarding database for a specific VLAN” (page 138)

• “Clearing learned MAC addresses from the forwarding database”(page 140)

• “Configuring static forwarding” (page 142)

• “MAC-layer bridge packet filtering” (page 145)

• “Configuring a MAC-layer bridge filter” (page 146)

• “Configuring the Global MAC filter” (page 150)

Configuring the forwarding database timeoutTo configure the forwarding database (FDB) timeout:

Step Action




2 Select a VLAN, and then click Bridge.

The Bridge, VLAN box appears with the FDB Aging tabdisplayed.


NN46220-511 04.01 26 June 2009


.


The Bridge, VLAN box appears with the FDB Aging tabdisplayed (Figure 50 "Bridge, VLAN, FDB Aging tab" (page138)).Figure 50Bridge, VLAN, FDB Aging tab

3 In the FdbAging box, enter an interval, in seconds, for aging outdynamically learned forwarding information, or keep the default(300 seconds).

4 Click Apply and then click Close.

Your changes are applied and the Bridge, VLAN box closes.

For more information, see Table 19 "Bridge VLAN, FDB Agingtab fields" (page 138).

--End--

Table 19Bridge VLAN, FDB Aging tab fields

Field Description

FdbAging The timeout period (in seconds) used for aging outFDB entries of this VLAN.

Viewing the forwarding database for a specific VLANThe Forwarding tab shows the forwarding database for the VLAN andcontains unicast information about bridge forwarding or filtering. Thisinformation is used by transparent bridging to determine how to forward areceived frame.

To view all entries in the forwarding database, for a specific VLAN:

Step Action




NN46220-511 04.01 26 June 2009


.


The VLAN box appears with the Basic tab displayed (Figure 26"VLAN, Basic tab" (page 100)).

2 Select a VLAN and click Bridge.

The Bridge, VLAN box appears with the FDB Aging tabdisplayed (see Figure 50 "Bridge, VLAN, FDB Aging tab" (page138)).

The Bridge, VLAN box appears with the FDB Aging tabdisplayed.

3 Click the Forwarding tab.

The Bridge, VLAN, Forwarding tab appears.

The Bridge, VLAN, Forwarding tab appears (Figure 51 "Bridge,VLAN, Forwarding tab" (page 139)).Figure 51Bridge, VLAN, Forwarding tab

For more information, see Table 20 "Bridge, VLAN, Forwardingtab fields" (page 139).

--End--

Table 20Bridge, VLAN, Forwarding tab fields

Field Description

Address A unicast MAC address for which the bridge hasforwarding or filtering information.


Port Either a value of zero (0) or the port number of the porton which a frame having the specified MAC addresswas seen. A value of 0 indicates a self-assigned MACaddress.

Monitor Select true or false to copy packets with a MACaddress in the source or destination field. Used withport mirroring.


NN46220-511 04.01 26 June 2009


.


Table 20Bridge, VLAN, Forwarding tab fields (cont’d.)

Field Description

QosLevel Quality of Service level.

SmltRemote Specifies whether you want to use SMLT.

Status Values include:


• learned—a learned entry that is being used


Clearing learned MAC addresses from the forwarding databaseFor troubleshooting, you need to manually flush the bridge forwardingdatabase of learned MAC addresses.

You can perform this procedure for all MAC addresses as described inthe following sections:

• “Clearing learned MAC addresses by VLAN” (page 140)

• “Clearing learned MAC addresses for all VLANs by port” (page 141)

Clearing learned MAC addresses by VLANTo clear the forwarding database of learned MAC addresses for a VLAN:

Step Action




2 In the VLAN box, click the Advanced tab.

The Advanced tab appears.

The Advanced tab appears (Figure 52 "VLAN, Advanced" (page141)).


NN46220-511 04.01 26 June 2009


.


Figure 52VLAN, Advanced

3 Double-click in the VLAN Operation Action field, and chooseFlushMacFdb from the list.

4 Click Apply.

The VLAN is set for flushing the bridge forwarding database.

--End--

Clearing learned MAC addresses for all VLANs by portTo clear learned MAC addresses from the forwarding database for allVLANs by port:

Step Action

1 From the Device Manager main window, select a port.


2 From the menu bar, choose Edit > Port > General.

The Port box appears with the Interface tab displayed (seeFigure 53 "Port, Interface, FlushMacFDB" (page 142)).

The Port box appears with the Interface tab displayed.


NN46220-511 04.01 26 June 2009


.


Figure 53Port, Interface, FlushMacFDB

3 In the Action box, select FlushMacFdb.

4 Click Apply.

All learned MAC addresses are cleared from the forwardingdatabase (FDB) for VLANs associated with this port.

5 Click Close.

--End--

Configuring static forwardingThe Static tab contains static forwarding information configured by local ornetwork bridge management. The information is used to specify the set ofports that are allowed to forward frames.

Entries are valid for unicast and for group/broadcast addresses.


NN46220-511 04.01 26 June 2009


.


To configure forwarding information:

Step Action




2 In the VLAN box, select a VLAN and then click Bridge.

The Bridge, VLAN box appears (see Figure 50 "Bridge, VLAN,FDB Aging tab" (page 138)).

The Bridge, VLAN box appears.

3 Click the Static tab.

The Static tab is displayed.

The Static tab is displayed (Figure 54 "Bridge, VLAN, Static tab"(page 143)).Figure 54Bridge, VLAN, Static tab

4 In the Static tab, click Insert.

The Bridge, VLAN Insert Static box appears.

The Bridge, VLAN Insert Static box appears (Figure 55 "Bridge,VLAN, Insert Static box" (page 144)).


NN46220-511 04.01 26 June 2009


.


Figure 55Bridge, VLAN, Insert Static box

5 In the MacAddress box, enter a forwarding destination MACaddress.

6 In the Port box, click the ellipsis (...).

The BridgeStaticPort box appears (Figure 56 "BridgeStaticPort"(page 144)).Figure 56BridgeStaticPort

7 Select the port on which the frame is received.

8 Click Ok.

The Bridge Static Port box closes and the selected port appearsin the Insert Static box.

9 To copy packets with a MAC address in the source or destinationfield, select Monitor.

10 In the QoS box, select a Quality of Service level, or keep thedefault, level 1. Note that Level 7 is reserved for network controltraffic.

11 Click Insert.


NN46220-511 04.01 26 June 2009


.


The Insert Static box closes and the static information appearsin the Bridge, VLAN Static tab.

12 Click Close.

The static forwarding information is configured, and the BridgeVLAN box closes.

For more information, see Table 21 "Bridge VLAN static fields"(page 145).

--End--

Table 21Bridge VLAN static fields

Field Description

MacAddress The destination MAC address in a frame to whichthe forwarding information for this entry applies. Thisobject can take the value of a unicast address.

Port The port number of the port on which the frame isreceived.

Monitor Setting to copy packets with a MAC address in thesource or destination field. Used with port mirroring. InStatic tab, display = true or false.

QosLevel Quality of Service level.

Status Specifies the status of this entry. Select one of thefollowing values:

• permanent—in use and remains so after the nextbridge reset. This is the default value.

• deleteOnReset—in use and remains so until thenext bridge reset.

• deleteOnTimeout—currently in use and remains sountil it is aged.

• other—in use but the conditions under which itremains so are different from other values.

MAC-layer bridge packet filteringTo perform MAC-layer bridging, the switch must know the destinationMAC-layer address of each device on each attached network so it canforward packets to the appropriate destination. MAC-layer addresses arestored in the bridging table, and you can filter packet traffic based on thedestination MAC-layer address information.


NN46220-511 04.01 26 June 2009


.


For MAC address filtering, the Metro Ethernet Routing Switch 8600supports Bridge Management Information Base (MIB) filtering (RFC 1493).The number of MAC filters is limited to 100. You can create a filter entry inmuch the same way as you create a static MAC entry, by entering a MACaddress and the port on which it resides. In the MAC filter record, you canalso specify ports to discard source or destination packets for the MACaddress on a port.

Global MAC filtering eliminates the need for configuring multiple per-VLANfilter records for the same MAC. It provides the ability to discard a list ofMAC addresses, globally, on the switch. By using a global list you do nothave to configure a MAC per VLAN.

Configuring static multicastTo configure static multicast:

Step Action

1 On the Device Manager menu, select VLAN > VLANs > Basic >Bridge > Multicast.

2 Click Insert

3 In the Address box, enter the required IP Address for the VLAN.

4 Click the button beside ForwardingPorts to select the requiredports.

5 Click the button beside MltIds to select the required MLT.

6 Click Insert.

--End--

Configuring a MAC-layer bridge filterTo configure a MAC layer bridge filter:

Step Action




2 In the VLAN box, select a VLAN and click Bridge.

The Bridge, VLAN box appears (see Figure 50 "Bridge, VLAN,FDB Aging tab" (page 138)).


NN46220-511 04.01 26 June 2009


.


The Bridge, VLAN box appears.

3 Click the Filter tab.

The Filter tab appears.

The Filter tab appears (Figure 57 "Bridge, VLAN, Filter tab"(page 147)).Figure 57Bridge, VLAN, Filter tab

4 Click Insert.

The Bridge, VLAN Insert Filter box appears.

The Bridge, VLAN Insert Filter box appears (Figure 58 "Bridge,VLAN, Insert Filter box" (page 147)).Figure 58Bridge, VLAN, Insert Filter box

5 In the MacAddress box, enter the MAC address used to matchthe destination address of incoming packets.

6 In the Port box, click the ellipsis (...).

The BridgeFilterPort box appears (Figure 59 "BridgeFilterPort"(page 148)).


NN46220-511 04.01 26 June 2009


.


Figure 59BridgeFilterPort

7 Click the port on which this MAC address is found, and then clickOK.

The BridgeFilterPort box closes and the port is added to the Portbox on the Bridge, VLAN, Insert Filter box.

8 In the SrcDiscard box, click the ellipsis (...).

The BridgeFilterSrcDiscard box appears (Figure 60"BridgeFilterSrcDiscard box" (page 148)).Figure 60BridgeFilterSrcDiscard box

9 Click the ports from which you do not want packet traffic receivedby this MAC address, and then click Ok.

The box closes and the ports are added to the SrcDiscard field inthe Bridge, VLAN, Insert Filter box.

10 In the DestDiscard box, click the ellipsis (...).

The BridgeFilterDestDiscard box appears (Figure 61"BridgeFilterDestDiscard box" (page 149)).


NN46220-511 04.01 26 June 2009


.


Figure 61BridgeFilterDestDiscard box

11 Click the ports to which you do not want packet traffic sent fromthis MAC address, and then click Ok.

The box closes and the ports are added to the DestDiscard boxin the Bridge, VLAN, Insert Filter box.

12 Enable Pcap if required.

13 Click Insert.

The Insert Filter box closes and the filter appears in the Filtertab.

14 In the Bridge VLAN box and the VLAN box, click Close.

The MAC layer bridge filter is configured.

For more information, see Table 22 "Bridge VLAN Filter fields"(page 149).

--End--

Table 22Bridge VLAN Filter fields

Field Description

MacAddress The MAC address of this entry. This address is used tomatch the destination address of incoming packets.

Port Port on which this MAC address is found.


SrcDiscard Specify a set of ports. Traffic arriving on any of thespecified ports is not forwarded to this MAC address.

DestDiscard Specify a set of ports. Traffic arriving on any of thespecified ports from this MAC address is discarded.


NN46220-511 04.01 26 June 2009


.


Table 22Bridge VLAN Filter fields (cont’d.)

Field Description

Status Specifies the status of the VLAN. Values include:


• learned—a learned entry that is being used


Pcap Enable or disable the Packet Capture Tool (PCAP) forthe MAC address (FDB filter). For more informationabout PCAP, see Using the Packet Capture Tool .

Configuring the Global MAC filterGlobal MAC filtering eliminates the need for configuring multiple per-VLANfilter records for the same MAC. It provides the ability to discard a list ofMAC addresses, globally, on the switch. By using a global list you do nothave to configure a MAC per VLAN.

To configure the Global MAC filter:

Step Action

1 From the Device Manager window, select VLAN > GlobalMac Filtering. The GlobalMacFiltering tab appears (Figure 62"GlobalMacFiltering tab" (page 150)).Figure 62GlobalMacFiltering tab

Table 23 "GlobalMacFiltering tab fields" (page 151) describes thefields on the GlobalMacFiltering tab.

2 Click Insert.

The GlobalMacFiltering, Insert Mac Filter box appears Figure 63"GlobalMacFiltering, Insert Mac Filter box" (page 151) .


NN46220-511 04.01 26 June 2009


.


Figure 63GlobalMacFiltering, Insert Mac Filter box

3 In the GlobalMacFilterAddress box, enter the address, andthen click Insert.

The address you entered appears in the GlobalMacFiltering tab.

.

--End--

Table 23GlobalMacFiltering tab fields

Field Description

GlobalMacFilterAddress A MAC address which the switch discardsglobally.

Configuring Enhanced Operation modeWith Enhanced Operation mode, you can now increase the maximumnumber of VLANs when you use MultiLink Trunking to 1980 (1972 if Rmodules are present in the chassis) and to 989 when you use SMLT.Enhanced Operation mode requires Metro Ethernet Routing Switch 8600E, M, or R modules.

CAUTIONWhen Enhanced Operation mode is enabled, only MetroEthernet Routing Switch 8600 E, M, or R modules are initialized(other modules are placed offline). To avoid losing modulesand network connectivity, replace pre-E, M, or R modules ormove the network connections to an E, M, or R module beforeenabling Enhanced Operation mode.

To enable Enhanced Operation mode:

Step Action

1 From the Device Manager menu bar, choose Edit > Chassis.

The Chassis box appears with the System tab displayed.

2 Click the System Flags tab.


NN46220-511 04.01 26 June 2009


.


The System Flags tab appears.

The System Flags tab appears (Figure 64 "Chassis, SystemFlags tab" (page 152)).Figure 64Chassis, System Flags tab

3 Select the NewEnhancedOperMode check box.

4 Click Apply.

The system notifies you that the setting takes effect after saveand reboot.

5 Click the System tab.

The System tab appears.

The System tab appears (Figure 65 "Chassis, SystemSaveRuntimeConfig" (page 153)).


NN46220-511 04.01 26 June 2009


.


Figure 65Chassis, System SaveRuntimeConfig

6 In the ActionGroup1 box, select saveRuntimeConfig.

7 Click Apply > Close.

--End--

Enhanced Operation mode is configured.


NN46220-511 04.01 26 June 2009


.



NN46220-511 04.01 26 June 2009


.

155.

Configuring spanning tree usingDevice Manager

This section discusses using Device Manager to create, manage, andmonitor spanning tree groups (STG), and discusses using Device Managerto configure Spanning Tree Protocol (STP), and Multiple Spanning TreeProtocol (MSTP).


• “Choosing the spanning tree mode” (page 155)

• “Configuring Spanning Tree Protocol” (page 156)

• “Configuring Multiple Spanning Tree Protocol” (page 169)

Choosing the spanning tree modeYou can choose to use STP, or MSTP with the Metro Ethernet RoutingSwitch 8600. To configure the mode:

Step Action

1 From the Device Manager menu bar, choose VLAN > SpanningTree > Globals.

The Spanning Tree Globals box appears (Figure 66 "SpanningTree, Globals" (page 156)).


NN46220-511 04.01 26 June 2009


.

156 Configuring spanning tree using Device Manager

Figure 66Spanning Tree, Globals

2 Select the required spanning tree mode.

3 Click Apply.

ATTENTIONAfter you change the mode, you must reboot the switch for changesto take effect. You can reboot the switch using the command lineinterface (CLI) by first saving the boot file with the command savebootconfig, and then entering the command boot <filename>,where filename is the saved boot config file. You can also rebootthe switch using Device Manager. Go to Edit > Chassis. In theActionGroup1 box, select saveBootConfig. Click Apply. Next, inActionGroup4, select softReset. Click Apply.

--End--

Configuring Spanning Tree ProtocolThis section discusses using Device Manager to create, manage, andmonitor spanning tree groups.


• “Creating a STG” (page 157)

• “Editing an STG” (page 161)

• “Adding ports to an STG” (page 161)

• “Viewing the STG status” (page 162)

• “Viewing STG ports” (page 165)

• “Enabling STP on a port” (page 167)

• “Deleting an STG” (page 168)

• “Configuring STG topology change detection” (page 168)


NN46220-511 04.01 26 June 2009


.

Configuring Spanning Tree Protocol 157

Creating a STGA network can include multiple instances of STP. The collection of ports inone spanning tree instance is called a spanning tree group (STG). TheMetro Ethernet Routing Switch 8600 supports STP and up to 64 spanningtree groups.

This information applies to Metro Ethernet Routing Switch 8600 modulesonly. Spanning Tree Protocol must be disabled on split multilink trunking(SMLT) or interswitch trunk ports, because spanning tree is not asupported configuration on these ports.

To create a STG:

Step Action

1 From the Device Manager menu bar, choose VLAN > SpanningTree > STG.

The STG, Configuration tab appears (Figure 67 "STG,Configuration tab" (page 157)).Figure 67STG, Configuration tab

2 On the Configuration tab, click Insert.

The STG, Insert Configuration box appears (see Figure 68 "STG,Insert Configuration" (page 158)).

For more information, see Table 24 "STG configuration fields"(page 159)


NN46220-511 04.01 26 June 2009


.


Figure 68STG, Insert Configuration

3 Use the fields in the STG, Insert Configuration box to configurethe STG.

In the STG table, the STG ID and TaggedBpduVlanId mustbe unique. If you change the STG ID without updatingTaggedBpduVlandId, the insertion can fail because of a duplicateTaggedBpduVlanId.

4 In the PortMembers box, click the ellipses ( ... ).

The StgPortMembers box (Figure 69 "StgPortMembers" (page158)) appears.Figure 69StgPortMembers


NN46220-511 04.01 26 June 2009


.


5 Click the ports you want to add to the STG, and then click Ok.

The StgPortMembers box closes, and the ports are added to thePort Members field in the Insert Configuration box.

Spanning Tree Protocol must be disabled on SMLT or interswitchtrunk ports.

6 Click Insert.

The Insert Configuration box closes, and the STG appears in theConfiguration tab.

7 Click Close.

The STG is configured.

For more information, see Table 24 "STG configuration fields"(page 159).

--End--

Table 24STG configuration fields

Field Description

Id The ID number for the STG.

The STG ID and TaggedBpduVlanId must be uniquein the STG table. If you change the STG ID withoutupdating TaggedBpduVlanId, the insertion can failbecause of a duplicate TaggedBpduVlanId.

Type Specifies the type of STG.

• normal = normal STG

• svlan = stacked VLAN STG

• plsb = PLSB STG

Priority Sets the STP bridge priority, in decimal.

BridgeMaxAge The value in hundredths of a second that all bridgesuse for MaxAge when this bridge is acting as the root.

The 802.1d-1990 standard specifies that theBridgeMaxAge range is related to the value ofBridgeHelloTime. The default is 2000 (20 seconds).


NN46220-511 04.01 26 June 2009


.


Table 24STG configuration fields (cont’d.)

Field Description

BridgeHelloTime The value in hundredths of a second that all bridgesuse for HelloTime when this bridge is acting as theroot. The granularity of this timer is specified by theIEEE 802.1d-1990 standard to be in increments of1/100 of a second. The default is 200 (2 seconds).

BridgeForwardDelay The value in hundredths of a second that all bridgesuse for forward delay when this bridge is acting as theroot. The default is 1500 (15 seconds).

EnableSTP Enables or disables the spanning tree algorithm for theSTG.

StpTrapEnable Enables SNMP traps to be sent to trace receiver everytime an STP topology occurs.

TaggedBpduAddress Represents a MAC address; specifically for taggedBPDUs.

TaggedBpduVlanId Represents the VLAN tag associated with the STG.This ID is used to tag BPDUs through a non-IEEEtagging bridge to another Metro Ethernet RoutingSwitch 8600.

By default, the TaggedBpduVlanId is an addresscalculated based on the STG ID by Device Manager.Accepting the default value calculated by DeviceManager makes it much simpler to coordinate STGsacross multiple switches. If you enter a custom valuefor this field, you must manually coordinate it across allswitches.

The STG ID and TaggedBpduVlanId must be uniquein the STG table. If you change the STG ID withoutupdating TaggedBpduVlanId, the insertion can failbecause of a duplicate TaggedBpduVlanId.

Port Members The ports you want to become members of the newSTG.


NN46220-511 04.01 26 June 2009


.


Table 24STG configuration fields (cont’d.)

Field Description

You cannot select a port if it is:

• configured as Single Port SMLT, MLT-based SMLT,or IST

• configured as members of any other STG

NtStgEnable Indicates whether this STG is operating in Nortel modeor in Cisco mode:

• true—Nortel mode

• false—Cisco mode

Untagged ports can belong to only one STG.

Editing an STGThe information about editing an STG applies to Metro Ethernet RoutingSwitch 8600 modules only.

To edit an STG:

Step Action


The STG, Configuration box appears (Figure 67 "STG,Configuration tab" (page 157)).

2 Double-click the field for the STG you want to edit.

The field becomes editable.

3 Enter a new value or select a new setting from the menu.

4 Click Apply.

The changes are applied to the STG.

--End--

Adding ports to an STGTo add ports to a spanning tree group:


NN46220-511 04.01 26 June 2009


.


Step Action


The STG, Configuration tab appears (Figure 67 "STG,Configuration tab" (page 157)).

2 Double-click the Port Members field for the STG.

The StgPortMembers box (Figure 70 "StgPortMembers box"(page 162)) appears, indicating the port members assigned tothis STG.Figure 70StgPortMembers box

3 Click the ports you want to add to the STG, and click OK.

The StgPortMembers box closes, and the ports are added to thePort Members field in the Configuration tab.

Spanning Tree Protocol must be disabled on SMLT or IST ports.

4 Click Apply.

The ports are added to the STG.

--End--

Viewing the STG statusYou can use the STG Status tab to view the status of the spanning tree foreach STG that is associated with the network.

To view STG status:

Step Action



NN46220-511 04.01 26 June 2009


.



2 Click the Status tab.

The Status tab appears (Figure 71 "STG, Status tab" (page163)), displaying the STG status.Figure 71STG, Status tab

For more information, see Table 25 "STG Status fields" (page163).

--End--

Table 25STG Status fields

Field Description

BridgeAddress The MAC address used by this bridge when it must bereferred to in a unique fashion.

NumPorts The number of ports controlled by this bridging entity.

ProtocolSpecification An indication of what version of the SpanningTree Protocol is being run. The IEEE 802.1dimplementations return ieee8021d.

TimeSinceTopologyChange

The time in hundredths of a second since the last timea topology change was detected by the bridge entity orSTG.


NN46220-511 04.01 26 June 2009


.


Table 25STG Status fields (cont’d.)

Field Description

TopChanges A topology change trap is sent by a bridge when any ofits configured ports transitions from the Learning stateto the Forwarding state, or from the Forwarding stateto the Blocking state. The trap is not sent if a new roottrap is sent for the same transition. Implementation ofthis trap is optional.

DesignatedRoot The bridge identifier of the root of the spanning tree asdetermined by the Spanning Tree Protocol as executedby this node. This value is used as the Root Identifierparameter in all Configuration Bridge PDUs originatedby this node.

RootCost The cost of the path to the root as seen from thisbridge.

RootPort The port number of the port that offers the lowest costpath from this bridge to the root bridge.

MaxAge The maximum age of Spanning Tree Protocolinformation learned from the network on any portbefore it is discarded, in units of hundredths of asecond. This is the actual value that this bridge iscurrently using.

HelloTime The amount of time in hundredths of a second betweentransmission of config BPDUs by this node on any portwhen it is the root of the spanning tree. The defaultvalue is 200 (2 seconds).

HoldTime The time interval in hundredths of a second duringwhich no more than two configuration bridge PDUsshall be transmitted by this node. The default value is100 (1 second).

ForwardDelay The time interval in hundredths of a second thatcontrols how fast a port changes its spanning statewhen moving toward the Forwarding state. The valuedetermines how long the port stays in each of theListening and Learning states, which precede theForwarding state. This value is also used when atopology change is detected and is under way, to ageall dynamic entries in the Forwarding Database. Notethat this value is the one this bridge is currently using,in contrast to StgBridgeForwardDelay, which is thevalue that this bridge and all others would use if thisbridge becomes the root. The default value is 1500 (15seconds).


NN46220-511 04.01 26 June 2009


.


Viewing STG portsUse the Ports tab to view the status of ports for each STG that isassociated with the network.

To view STG ports:

Step Action



2 Click the Ports tab.

The Ports tab appears(Figure 72 "STG, Ports tab" (page 165)).For parameter descriptions, see Table 26 "STG Ports tab fields"(page 165).Figure 72STG, Ports tab

For more information, see Table 26 "STG Ports tab fields" (page165).

--End--

Table 26STG Ports tab fields

Field Description

Port The port number of the port for which this entry contains Spanning TreeProtocol management information.

StgId The STG identifier assigned to this port.


NN46220-511 04.01 26 June 2009


.


Table 26STG Ports tab fields (cont’d.)

Field Description

Priority The value of the priority field which is contained in the first octet of thePort ID. The other octet of the Port ID is given by the value of rcStgPort.

Although port priority values can range from 0 to 255, on the MetroEthernet Routing Switch 8600, only the following values are used: 0, 16,32, 48, 64, 80, 96, 112, 128, 144, 160, 176, 192, 208, 224, 240.

State The current state of the port as defined by the application of the SpanningTree Protocol:

disabled

blocking

listening

learning

forwarding

broken

This state controls what action a port takes on reception of the frame. Ifthe bridge has detected a port that is malfunctioning, it places that portinto the broken state. For ports that are disabled, this object has a valueof disable.

EnableStp The STP state of the port.

Enabled—BPDUs are processed in accordance with STP.

Disabled—The port stays in a forwarding state, received BPDUs aredropped and not processed, and no BPDU is generated.

FastStart When this flag is set, the port is moved straight to the forwarding stateupon being enabled.

true (enables FastStart for the port)

false (default, disables FastStart for the port)

This setting is contrary to that specified in the IEEE 802.1d standard forSpanning Tree Protocol (STP), in which a port enters the blocking statefollowing the initialization of the bridging device or from the disabled statewhen the port is enabled through configuration.


NN46220-511 04.01 26 June 2009


.


Table 26STG Ports tab fields (cont’d.)

Field Description

PathCost The contribution of this port to the path cost of paths toward the spanningtree root that includes this port. The 802.1d-1990 protocol recommendsthat the default value of this parameter be inversely proportion to thespeed of the attached LAN.

DesignatedRoot The unique bridge identifier of the bridge recorded as the root in theconfiguration BPDUs transmitted by the designated bridge for thesegment to which the port is attached.

DesignatedCost The path cost of the designated port of the segment connected to thisport. This value is compared to the Root Path Cost field in receivedbridge PDUs.

DesignatedBridge The bridge identifier of the bridge that this port considers to be thedesignated bridge for this port’s segment.

DesignatedPort The port identifier of the port on the designated bridge for this portsegment.

ForwardTransitions The number of times this port has transitioned from the learning state tothe forwarding state.

ChangeDetection The change detection setting (true or false) for this port. Can only beconfigured on access ports. If you enable change detection on an MLTwith access ports, the setting is automatically applied to all ports in theMLT.

Enabling STP on a portTo enable STP for a port:

Step Action




The Ports tab appears (Figure 72 "STG, Ports tab" (page 165)).

3 Click in the EnableStp field for the port you want to enable.

A menu appears.

4 From the menu, choose true.

The EnableStp setting changes.

5 Click Apply.


NN46220-511 04.01 26 June 2009


.


STP is enabled for the port.

--End--

Deleting an STGThe deleting an STG procedure applies to Metro Ethernet Routing Switch8600 modules only.

To delete an STG:

Step Action


The STG box appears (Figure 67 "STG, Configuration tab" (page157)).

2 Click the STG that you want to delete.

3 Click Delete.

All VLANs must be deleted from an STG before you can removethe STG.

--End--

Configuring STG topology change detectionTo configure topology change detection on a port:

Step Action




The Ports tab appears (Figure 72 "STG, Ports tab" (page 165)).

3 Double-click the ChangeDetection field for a port.

The menu of change detection settings appears.

4 From the menu, choose one of the following:

• To enable change detection on the port, choose true.

• To disable change detection on the port, choose false.


NN46220-511 04.01 26 June 2009


.

Configuring Multiple Spanning Tree Protocol 169

5 Click Apply.

Change detection is configured for the port.

--End--

Configuring Multiple Spanning Tree ProtocolTo configure MSTP, you must first enable it.

For more information about enabling MSTP, see “Choosing the spanningtree mode” (page 155).

This section contains the following topics:

• “Configuring MSTP globally” (page 169)

• “Configuring CIST ports for MSTP” (page 172)

• “Viewing statistics for the CIST ports” (page 175)

• “Configuring MSTI bridges for MSTP” (page 177)

• “Mapping an MSTI to a VLAN” (page 178)

• “Configuring MSTI ports for MSTP” (page 178)

• “Viewing MSTI port statistics” (page 180)

• “Viewing MSTI port notification” (page 181)

Configuring MSTP globallyTo configure MSTP globally:

Step Action

1 From the Device Manager menu bar, choose VLAN > SpanningTree > MSTP.

The MSTP, Globals tab appears (Figure 73 "MSTP, Globals"(page 170)).


NN46220-511 04.01 26 June 2009


.


Figure 73MSTP, Globals

2 Edit desired fields to configure MSTP.

3 Click Apply.

For more information, see Table 27 "MSTP, Globals fields" (page171).

--End--


NN46220-511 04.01 26 June 2009


.


Table 27MSTP, Globals fields

Field Description

TxHoldCount The value used by the port transmit state machine to limit themaximum transmission rate.

MaxHopCount Indicates the maximum hop count. The granularity of this timer isspecified to be 1 second. An agent can return a bad value error ifyou attempt to set a value which is not a whole number of seconds.

NoOfInstancesSupported Indicates the maximum number of spanning tree instancessupported.

MstpUpCount The number of times the MSTP module was enabled. A trap isgenerated on the occurrence of this event.

MstpDownCount The number of times the MSTP module was disabled. A trap isgenerated on the occurrence of this event.

PbtMsti The MSTI instance ID for the PBT.

PlsbGlobalMsti The MSTI instance ID for PLSB VLANS.

ForceProtocolVersion The version of Spanning Tree Protocol the bridge currently runs.stpCompatible indicates that the Spanning Tree Protocol asspecified in IEEE 802.1d is in use; and mstp indicates that theMultiple Spanning Tree Protocol as specified in IEEE 802.1s is inuse.

BrgAddress The MAC address used by this bridge when it must be referred to ina unique fashion. Nortel recommends that this be the numericallysmallest MAC address of all ports that belong to this bridge. Whenconcatenated with MstCistBridgePriority or MstBridgePriority, aunique bridge identifier is formed which is used in the Spanning TreeProtocol.

Root The bridge identifier of the root of the common spanning tree asdetermined by the Spanning Tree Protocol by this node. This valueis used as the CIST root identifier parameter in all configurationbridge PDUs originated by this node.

RegionalRoot The bridge identifier of the root of the multiple spanning tree regionas determined by the Spanning Tree Protocol as executed bythis node. This value is used as the CIST regional root identifierparameter in all configuration bridge PDUs originated by this node.

RootCost The cost of the path to the CIST root from this bridge.

RegionalRootCost The cost of the path to the CIST regional root from this bridge.

RootPort The port number of the port which offers the lowest path cost fromthis bridge to the CIST root bridge.

BridgePriority The value of the writable portion of the bridge identifier comprisingof the first two octets. The values you enter for bridge priority mustbe in steps of 4096.


NN46220-511 04.01 26 June 2009


.


Table 27MSTP, Globals fields (cont’d.)

Field Description

BridgeMaxAge The value that all bridges use for MaxAge when this bridge acts asthe root. The granularity of this timer is specified to be 1 second.An agent can return a bad value error if you attempt to set a valuewhich is not a whole number of seconds. The default is 2000.

BridgeForwardDelay The value that all bridges use for forward delay when this bridgeacts as the root. Note that 802.1d specifies that the range for thisparameter is related to the value of BridgeMaxAge. The granularityof this timer is specified to be 1 second. An agent can return a badvalue error if you attempt to set a value which is not a whole numberof seconds. The default is 1500.

HoldTime This time value determines the interval length during which no morethan two configuration bridge PDUs can be transmitted by this node,in units of hundredths of a second.

MaxAge The maximum age of Spanning Tree Protocol information learnedfrom the network on any port before it is discarded, in units ofhundredths of a second. This is the value that this bridge currentlyuses.

ForwardDelay This time value, measured in units of hundredths of a second,controls how fast a port changes its spanning state when movingtowards the forwarding state. The value determines how long theport stays in a particular state before moving to the next state.


The time (in hundredths of a second) since the TcWhile Timer forany port in this bridge was non-zero for Common Spanning Tree.

TopChanges The number of times that there was at least one non-zero TcWhileTimer on this bridge for Common Spanning Tree.

NewRootBridgeCount The number of times this bridge has detected a root bridge changefor Common Spanning Tree. A trap is generated on the occurrenceof this event.

RegionName The name for the region configuration. By default the region name isequal to the bridge MAC Address.

RegionVersion Version of the MST region.

ConfigIdSel The configuration identifier format selector used by the bridge. Thishas a fixed value of 0 to indicate RegionName, RegionVersions arespecified as in the standard.

ConfigDigest The configured MD5 digest value for this region, which must be 16octets long.

RegionConfigChange Count The number of times a region configuration identifier change wasdetected. A trap is generated on the occurrence of this event.

Configuring CIST ports for MSTPTo configure Common and Internal Spanning Tree (CIST) ports for MSTP:


NN46220-511 04.01 26 June 2009


.


Step Action

1 In Device Manager, go to VLAN > Spanning Tree > MSTP.

The MSTP box appears.

2 In the MSTP box, click the CIST Port tab.

The MSTP, CIST Port tab appears (Figure 74 "MSTP, CIST Porttab" (page 173)).Figure 74MSTP, CIST Port tab

3 Use the fields in the CIST Port box to configure the MSTP.

4 Click Apply.

The MSTP, CIST Port tab contains per-port information that iscommon to all bridge and spanning tree instances.

For more information, see Table 28 "MSTP, CIST Port fields"(page 174).

--End--


NN46220-511 04.01 26 June 2009


.


Table 28MSTP, CIST Port fields

Field Description

Port The port number of the port for which this entry contains spanning treeinformation

PathCost The contribution of this port to the path cost of paths towards the CISTroot which includes this port.

Priority The four most significant bits of the port identifier of the spanning treeinstance can be modified by setting the CistPortPriority value. The valuesthat are set for port priority must be in steps of 16.

Although port priority values can range from 0 to 255, on the MetroEthernet Routing Switch 8600, only the following values are used: 0, 16,32, 48, 64, 80, 96, 112, 128, 144, 160, 176, 192, 208, 224, 240.

DesignatedRoot The unique bridge identifier of the bridge recorded as the CIST root in theconfiguration BPDUs transmitted.

DesignatedCost The path cost of the designated port of the segment which connects tothis port.

DesignatedBridge The unique bridge identifier of the bridge which this port considers to bethe designated bridge for the port’s segment.


RegionalRoot The unique bridge identifier of the bridge recorded as the CIST regionalroot identifier in the configuration BPDUs transmitted.

RegionalPathCost The contribution of this port to the path cost of paths towards the CISTregional root which include this port.

ProtocolMigration Indicates the protocol migration state of this port. When operating inMSTP mode, writing true to this object forces this port to transmit MSTPBPDUs without instance information. Any other operation on this objecthas no effect and it returns false when read.

AdminEdgeStatus The administrative value of the Edge Port parameter. A value of trueindicates that this port is an edge-port, and a value of false indicates thatthis port is a non-edge-port.

OperEdgeStatus The operational value of the Edge Port parameter. The object isinitialized to the value of AdminEdgeStatus and is set false on receptionof a BPDU.

AdminP2P The administrative point-to-point status of the LAN segment attachedto this port. A value of forceTrue indicates that this port is treated as ifit connects to a point-to-point link. A value of forceFalse indicates thatthis port is treated as having a shared media connection. A value of autoindicates that this port is considered to have a point-to-point link if it is anaggregator and all of its members are aggregatable, or if the MAC entityis configured for full duplex operation, either through auto-negotiation orby management means.


NN46220-511 04.01 26 June 2009


.


Table 28MSTP, CIST Port fields (cont’d.)

Field Description

OperP2P The operational point-to-point status of the LAN segment attached to thisport. It indicates whether a port is considered to have a point-to-pointconnection or not. The value is determined by management or byauto-detection as described in the AdminP2P object.

HelloTime The amount of time between the transmission of configuration bridgePDUs by this node on this port in units of hundredths of a second.

OperVersion This indicates whether the port is operationally in the MSTP mode or theSTP-compatible mode, that is, whether the port transmits MST BPDUs,RST BPDUs or Config/TCN BPDUs.

EffectivePortState The effective operational state of the port for CIST. This is true only whenthe port is operationally UP at the interface and protocol levels for CIST.This is set to false for all other conditions.

State Current state of the port as defined by the common spanning treeprotocol. It can be disabled, discarding, learning, or forwarding.

ForcePortState Current state of the port, which can be changed to either Disabled orEnabled for the base spanning tree instance.

SelectedPortRole Selected port role of the port for this spanning tree instance.

CurrentPortRole Current port role of the port for this spanning tree instance.

Viewing statistics for the CIST portsYou can view statistics for the CIST ports. To view statistics:

Step Action



2 In the MSTP box, click the CIST Port tab.

The MSTP, CIST Port tab appears.

3 Click on a port, and then click Graph.

The CIST Port Stats window appears (Figure 75 "CIST PortStats" (page 176)).


NN46220-511 04.01 26 June 2009


.


Figure 75CIST Port Stats

For more information, see Table 29 "MSTP CIST Port Statsfields" (page 176).

--End--

Table 29MSTP CIST Port Stats fields

Field Description

ForwardTransitions Number of times this port has transitioned to the forwardingstate.

RxMstBpduCount Number of MSTP BPDUs received on this port.

RxConfigBpduCount Number of configuration BPDUs received on this port.

RxTcnBpduCount Number of TCN BPDUs received on this port.

TxMstBpduCount Number of MSTP BPDUs transmitted from this port.

TxConfigBpduCount Number of configuration BPDUs transmitted from this port.

TxTcnBpduCount Number of TCN BPDUs transmitted from this port.

InvalidMstBpduRxCount Number of Invalid MSTP BPDUs received on this port.

InvalidConfigBpduRxCount Number of invalid configuration BPDUs received on this port.


NN46220-511 04.01 26 June 2009


.


Table 29MSTP CIST Port Stats fields (cont’d.)

Field Description

InvalidTcnBpduRxCount Number of invalid TCN BPDUs received on this port. Thenumber of times this port has migrated from one STP protocolversion to another. The relevant protocol is STP-Compatible. Atrap is generated on the occurrence of this event.

ProtocolMigrationCount The number of times this port has migrated from oneSTP protocol version to another. The relevant protocol isSTP-Compatible. A trap is generated on the occurrence of thisevent.

Configuring MSTI bridges for MSTPTo configure Multiple Spanning Tree Instance (MSTI) bridges:

Step Action



2 In the MSTP box, click the MSTI Bridges tab.

MSTI bridge instances are generated by the switch after youcreate a VLAN in MSTP mode.

3 Use the MSTI Bridges fields to configure the MSTP.

4 Click Apply.

For more information, see Table 30 "MSTI Bridges fields" (page177).

--End--

Table 30MSTI Bridges fields

Field Description

Instance Spanning tree instance to which this information belongs.

Regional Root MSTI regional root identifier value for the instance. This valueis used as the MSTI regional root identifier parameter in allconfiguration bridge PDUs originated by this node.

Priority The writable portion of the MSTI bridge identifier comprising of thefirst two octets. The values that are set for bridge priority must be insteps of 4096.

Root Cost The cost of the path to the MSTI regional root as seen by thisbridge.


NN46220-511 04.01 26 June 2009


.


Field Description

Root Port The port number of the port which offers the lowest path cost fromthis bridge to the MSTI region root bridge.


The time (in hundredths of a second) since the TcWhile Timer forany port in this bridge was non-zero for this spanning tree instance.

TopChanges The number of times that there was at least one non-zero TcWhileTimer on this bridge for this spanning tree instance.

NewRootCount The number of times this bridge has detected a root bridgechange for this spanning tree instance. A trap is generated on theoccurrence of this event.

InstanceUpcount The number of times a new spanning tree instance was created. Atrap is generated on the occurrence of this event.

InstanceDownCount The number of times a spanning tree instance was deleted. A trap isgenerated on the occurrence of this event.

BridgeInstId The Spanning Tree Instance to which the information belongs.

BridgeVlanMap A list of the mapped VLANs on the spanning tree instance.

Mapping an MSTI to a VLANTo map an MSTI to a VLAN, do the following:

Step Action



2 In the MSTP box, click the MSTI Bridges tab.

3 Click VLANs and map the MSTI to a VLAN or to a range ofVLANs.

MSTI bridge instances are generated by the switch after youcreate a VLAN in MSTP mode.

4 Click Apply.

--End--

Configuring MSTI ports for MSTPTo configure MSTI ports, do the following:

Step Action




NN46220-511 04.01 26 June 2009


.


2 In the MSTP box, click the MSTI Port tab.

The MSTI Port tab appears (Figure 76 "MSTP, MSTI Port tab"(page 179)). (Port members selected on the VLAN > Basic tabappear in the MSTI Port tab).Figure 76MSTP, MSTI Port tab

3 Use the fields in the MSTI Port box to configure the MSTP.

4 Click Apply.

For more information, see Table 31 "MSTP, MSTI Port fields"(page 179).

--End--

Table 31MSTP, MSTI Port fields

Field Description

Port The port number of the port for which this entry contains spanning treeinformation.

BridgeInstance Spanning tree instance to which the information belongs.

PathCost The contribution of this port to the path cost of paths towards the MSTIroot which includes this port.

Priority The four most significant bits of the port identifier for a given spanningtree instance can be modified independently for each spanning treeinstance supported by the bridge. The values set for port priority mustbe in steps of 16.

DesignatedRoot The unique bridge identifier of the bridge recorded as the MSTI regionalroot in the configuration BPDUs transmitted.

DesignatedBridge The unique bridge identifier of the bridge which this port considers to bethe designated bridge for the port segment.


State Current state of the port as defined by the MSTP. A port which is inforwarding state in one instance can be in discarding (blocking) state inanother instance.


NN46220-511 04.01 26 June 2009


.


Table 31MSTP, MSTI Port fields (cont’d.)

Field Description

ForcePortState Current state of the port which can be changed to either disabled orenabled for the specific spanning tree instance.

DesignatedCost The path cost of the designated port of the segment connected to thisport.

CurrentPortRole Current port role of the port for this spanning tree instance.

EffectivePortState The effective operational state of the port for specific instance. This istrue when the port is operationally up at the interface and protocol levelsfor the specific instance. This is set to false at all other times.

Viewing MSTI port statisticsYou can view statistics for the MSTI Ports.

Step Action



2 In the MSTP box, click the MSTI Port tab.

The MSTP, MSTI Port tab appears (Figure 76 "MSTP, MSTI Porttab" (page 179)).

3 Click on a port, and then click Graph.

The MSTI Port Stats window appears (Figure 77 "MSTIPort.BridgeInstance" (page 180)).Figure 77MSTI Port.BridgeInstance

For more information, see Table 32 "MSTI Port Stats fields"(page 181).

--End--


NN46220-511 04.01 26 June 2009


.


Table 32MSTI Port Stats fields

Field Description

ForwardTransitions Number of times this port has transitioned to theforwarding state for this specific instance.

ReceivedBPDUs Number of BPDUs received by this port for thisspanning tree instance.

TransmittedBPDUs Number of BPDUs transmitted on this port for thisspanning tree instance.

InvalidBPDUsRcvd Number of invalid BPDUs received on this port for thisspanning tree instance.

Viewing MSTI port notificationYou can view the port notification information that occurred in each of theports for protocol migration and invalid packet received.

Step Action


2 In the MSTP box, click the MSTI Port Notification tab.

For more information, see Table 33 "MSTI Port Notificationfields" (page 181).

--End--

Table 33MSTI Port Notification fields

Field Description

Index A unique value, greater than zero, indicating the portnumber.

MigrationType The port protocol migration type that occurred in theport.

PktErrType The type of invalid packet received in each port.

PktErrVal The packet error value corresponding to the packettype.


NN46220-511 04.01 26 June 2009


.



NN46220-511 04.01 26 June 2009


.

183.

Configuring link aggregation usingDevice Manager

This section describes how to configure link aggregation in your network.

Only SMLT is applicable to NNI; all other technology is applicable to bothUNI and NNI.


• “Configuring link aggregation” (page 183)

• “Configuring Split Multilink Trunking” (page 208)

• “Configuring Simple Loop Prevention Protocol” (page 220)

Configuring link aggregationThis section describes how to configure and manage link aggregation,including LACP and multilink trunking. This section includes the followingtopics:

• “Configuring LACP globally” (page 184)

• “Adding a MultiLink/LACP trunk” (page 185)

• “Adding ports to a multilink trunk” (page 192)

• “Viewing multilink trunk interface statistics” (page 193)

• “Viewing multilink trunk Ethernet error statistics” (page 195)

• “Managing LACP information” (page 198)

• “Configuring a port for LACP” (page 201)

• “Viewing LACP statistics” (page 206)

Standby mode for aggregation groups of larger than eight ports is notsupported in the current release.


NN46220-511 04.01 26 June 2009


.

184 Configuring link aggregation using Device Manager

Configuring LACP globallyThe main purpose of LACP is to manage switch ports and their portmemberships to form link aggregation groups (LAG). LACP candynamically add or remove LAG ports, depending on their availability andstates.

To configure Link Aggregation Control Protocol (LACP) globally:

Step Action

1 From the Device Manager menu bar, choose VLAN >MLT/LACP.

The MLT_LACP, LACP Global tab appears (Figure 78"MLT_LACP, LACP Global tab" (page 184)).Figure 78MLT_LACP, LACP Global tab

2 To enable LACP globally, select Enable.

3 Edit the remaining boxes as desired, or retain the default values.

Table 34 "MLT_LACP, LACP Global tab fields" (page185) defines the MLT_LACP, LACP Global tab fields.

Configuration changes to the LACP timers are not reflectedimmediately. LACP timers are not reset until the next time LACPis restarted globally or on a port. This ensures consistency withpeer switches.

4 Click Apply.

Table 34 "MLT_LACP, LACP Global tab fields" (page 185).

--End--


NN46220-511 04.01 26 June 2009


.

Configuring link aggregation 185

Table 34MLT_LACP, LACP Global tab fields

Field Description

Enable Globally enable or disable LACP.

SystemPriority Sets the system priority to all the LACP enabledaggregators and ports.

FastPeriodicTime Specifies the number of milliseconds betweenperiodic transmissions using short timeouts. Setsthis value to all LACP enabled ports.

FastPeriodicTimeOper The operating value of the fast periodic timer onthe port.

SlowPeriodicTime Specifies the number of milliseconds betweenperiodic transmissions using long timeouts. Setsthis value to all LACP enabled ports.

SlowPeriodicTimeOper The operating value of the slow periodic timer onthe port.

AggrWaitTimeOper The operating value of the aggregate wait timer onthe port.

AggrWaitTime Specifies the number of milliseconds to delayaggregation to allow multiple links to aggregatesimultaneously.

TimeoutScale Sets the value used to calculate timeout timefrom the periodic time. Sets this value to all LACPenabled ports. The range is 2 to 10.

TimeoutScaleOper The operating value of the timeout scale on theport.

SmltSysId Sets the LACP system ID for split multilink trunks.This is an optional parameter, and is only usedfor SMLT situations. You must configure thesame LACP SMLT system ID on both aggregationswitches to avoid loss of data. Nortel recommendsthat the SmltSysId be configured such that itmatches the base MAC address of one of thechassis.

Adding a MultiLink/LACP trunkTo add a MultiLink/LACP trunk:

Step Action


2 Click the MultiLink/LACP Trunks tab.


NN46220-511 04.01 26 June 2009


.


Figure 79MLT_LACP, MultiLink/LACP Trunks

3 In the MultiLink/LACP Trunks box, click Insert to display theMLT_LACP, Insert Multilink/LACP Trunks box.


NN46220-511 04.01 26 June 2009


.


Figure 80MLT_LACP, Insert MultiLink/LACP Trunks box

4 In the Id text box, type the ID number for the multilink trunk.

5 In the SvlanPortType text box, select normal.

Do not select uni, or nni, as these options generate errormessages on MERS.

6 In the PortType section, select access or trunk.

7 In the Name text box, type a name for the multilink trunk, oraccept the default name.

8 Select member ports and VLANs for this MLT/LACP trunk:

a In the PortMembers box, click the ellipsis (...), select thedesired ports in the MltPortMembers box that appears, andthen click Ok.

b In the VlanIds box, click the ellipsis (...), select the desiredVLANs in the VlanIds box that appears, and then click Ok.

9 In the MltType section, select normalMLT, istMLT, or splitMLT.


NN46220-511 04.01 26 June 2009


.


For information about configuring SMLT, see “Adding aMLT-based SMLT” (page 208).

• If splitMLT is chosen, in the SmltID box, enter the SMLT IDnumber.

10 In the Multicast Distribution box, select enable or disable.

Multicast distribution over MLT is supported only on MetroEthernet Routing Switch 8600 E, M, and R modules.

11 Select or clear NtStgEnable.

12 In the Aggregatable box, select enable or disable.

13 Click Insert.

The MLT is added to the MultiLink/LACP Trunks tab in theMLT_LACP box.

For more information, see “MultiLink/LACP Trunks tab fields”(page 188).

--End--

MultiLink/LACP Trunks tab fields

Table 35MultiLink/LACP Trunks tab fields

Field Description

Id A value that uniquely identifies the multilink trunk.

SvlanPortType Sets multilink trunk port type:

• normal (default)

• uni (user-to-network interface)You must configure ports to which you wantto provide VLAN transparency as UNI ports.UNI ports can only belong to one SVLAN.When you designate a port as a UNI port, theDiscardTaggedFrames parameter is automaticallyconfigured (Edit > Port > General > VLAN). Thisprevents traffic from leaking to other VLANs.

• nni (network-to-network interface)NNI ports interconnect the switches in thecore network, drop untagged frames oningress, and insert the SVLAN tag at theegress. When you configure an NNI port,the DiscardUnTaggedFrames parameter isautomatically configured (Edit > Port > General >VLAN).


NN46220-511 04.01 26 June 2009


.


Table 35MultiLink/LACP Trunks tab fields (cont’d.)

Field Description

ATTENTIONUni and nni options generate error messages onMERS. Leave the option at its default value ofnormal to avoid these error messages.

PortType Sets access or trunk port.

When the aggregatable field is set to enable, this fieldbecomes read-only.

Name The name given to the multilink trunk.

PortMembers The ports assigned to the multilink trunk.

MLT is supported on 10Base-T, 100Base-TX,100Base-FX, and Gigabit Ethernet ports. All ports in anmultilink trunk must be of the same media type (copperor fiber) and have the same settings for speed andduplex. All untagged ports must belong to the samespanning tree group.

For Metro Ethernet Routing Switch 8600 modules,up to eight same-type ports can belong to a singlemultilink trunk.


VlanIds The VLANs to which the ports belong.


MltType Specifies the type of multilink trunk:

• normalMLT

• istMLT

• splitMLT

SmltId The split multilink trunk ID assigned to both ends of thesplit trunk.

The corresponding split multilink trunks betweenaggregation switches must have the same SMLT ID.


NN46220-511 04.01 26 June 2009


.



Field Description

Multicast Distribution The multicast distribution state on MLT ports:

• enabled

• disabled (default)

Multicast distribution must also be configured on thechassis (Edit > Chassis > Mcast MLT Distribution). Formore information, see Configuration — IP Multicast(NN46220-519). .

Multicast distribution over MLT is supported only onMetro Ethernet Routing Switch 8600 E, M, and Rmodules.

Lacp10gBackup Enable or disable 10G MLT reliance backup mode.The default is disable.

LocalDistributionOption

Specify the MLT load distribution option. Select eitherbmac, cmac, bvid, or isid. The default is bmac.

• bmac—Egress port selection is based on the UNIMAC source address (SA) and destination address(DA).

• cmac—Egress port selection is based on thecustomer MAC SA and DA.

• bvid—Provides link protection. The b-vid optionallows users to specify primary and secondaryMLT ports for a particular SP VLAN. Egress portselection is based on the port priority and state.

• isid—Egress port selection is based on the I-SID orTDI.

Note that the bvid option is only valid if there is a B-VIDlist for the SP VLAN or B-VLAN.

NtStgEnable Specifies if this multilink trunk is operating in NortelMode or in Cisco Mode.

• true—Nortel mode

• false—Cisco mode

Aggregatable Specifies if link aggregation is enabled or disabled.


NN46220-511 04.01 26 June 2009


.



Field Description

UniAggrMacIDx Specify the MLT aggregator MAC index. Enter a valuein the range from 0 to 448. The default setting is 0.

Before an MLT ID can be assigned to a UNI or I-SID,the aggregator MAC offset value for that MLT must beset in the range 1 to 448.

QinqEtherType Specify the QinQ ethernet type value in hexadecimalformat. This is only used when the MLT is associatedwith a QinQ service UNI. The default is 8020(hexadecimal).

EgressCosProfileName

Specify the MLT egress Class Of Service profile name.The default is DEFAULT_PORT_PROFILE.

EgressPolicerAdminState

Enable or disable the MLT egress policer. The defaultis disable.

AggrEgressBandwidth Select disable for the split bandwidth policer; enablefor the aggregator bandwidth policer. The default is toenable the aggregator egress bandwidth policer.

AggrIngressBandwidth

Select disable for the split bandwidth policer; enablefor the aggregator bandwidth policer. The default is toenable the aggregator ingress bandwidth policer.

AggrMacAlloc Enable or disable aggregated MAC allocation. Thedefault is disable.

MtuAdminState Enable or disable the MTU Admin state. The defaultis disable.

Mtu The Maximum Transmission Unit size. Enter a value inthe range from 1518 to 9600.

InterfaceType Specifies the type of interface:

• normal

• silent

• uni

ConfiguredMembers The set of ports that are configured members of a MLT.

Ports can be added to a MLT through the ConfiguredMembers field only if aggregate is enabled for the MLT.


NN46220-511 04.01 26 June 2009


.



Field Description

When aggregate is enabled, PortMembers showsall the active members under the MLT which havenegotiated, while ConfiguredMembers shows thestatically added ports under the MLT. It also allowsports to be added under MLT.

Adding ports to a multilink trunkTo add ports to an existing multilink trunk:

Step Action


The MLT_LACP, LACP Global tab appears.


The MultiLink/LACP Trunks tab appears (Figure 79 "MLT_LACP,MultiLink/LACP Trunks" (page 186)).

3 Click Insert.

The MLT_LACP, Insert MultiLink/LACP Trunks box (Figure 80"MLT_LACP, Insert MultiLink/LACP Trunks box" (page 187))appears.

4 Double-click in the PortMembers box for the multilink trunk towhich you are adding ports.

The MltPortMembers box (Figure 81 "MltPortMembers box"(page 193)) appears, showing the ports currently assigned forthe selected multilink trunk. Available ports are editable.


NN46220-511 04.01 26 June 2009


.


Figure 81MltPortMembers box

5 In the MltPortMembers box, click the port numbers to be added,or click All to add all ports to the multilink trunk.

For Metro Ethernet Routing Switch 8600 modules, up to eightsame-type ports can belong to a single multilink trunk.

6 Click Ok.

The MltPortMembers box closes. The port numbers are addedto the selected multilink trunk on the MultiLink/LACP Trunks tabin the MLT_LACP box.

7 Click Apply.

The ports are added to the multilink trunk.

--End--

Viewing multilink trunk interface statisticsTo view multilink trunk interface statistics:

Step Action


The MLT_LACP, LACP Global tab appears (Figure 78"MLT_LACP, LACP Global tab" (page 184)).



3 Select a multilink trunk.

4 Click Graph.


NN46220-511 04.01 26 June 2009


.


The Statistics, MLT, Interface tab appears Figure 82 "Statistics,MLT, Interface tab" (page 194), displaying interface statistics forthe selected multilink trunk.Figure 82Statistics, MLT, Interface tab

For more information, see Table 36 "Statistics, MLT, Interfacetab fields" (page 194).

--End--

Table 36Statistics, MLT, Interface tab fields

Field Description

InOctets The total number of octets received on the multilink trunk interface,including framing characters.

OutOctets The total number of octets transmitted out of the multilink trunk interface,including framing characters.

InUcastPkts The number of packets delivered by this multilink trunk to higher levelprotocols that were not addressed to a multicast or broadcast addressat this sublayer.

OutUcastPkts The number of packets that higher level protocols requested betransmitted that were not addressed to a multicast address at thismultilink trunk. This total number includes those packets discarded orunsent.

InMulticastPkt The number of packets delivered to this multilink trunk that wereaddressed to a multicast address at this sublayer. For a MAC layerprotocol, this number includes both Group and Functional addresses.


NN46220-511 04.01 26 June 2009


.


Table 36Statistics, MLT, Interface tab fields (cont’d.)

Field Description

OutMulticast The total number of packets that higher-level protocols requested betransmitted, and that were addressed to a multicast address at thismultilink trunk, including those that were discarded or not sent. For aMAC layer protocol, this number includes both Group and Functionaladdresses.

InBroadcastPkt The number of packets delivered to this multilink trunk that wereaddressed to a broadcast address at this sublayer.

OutBroadcast The total number of packets that higher-level protocols requested betransmitted, and that were addressed to a broadcast address at thismultilink trunk, including those that were discarded or not sent.

Viewing multilink trunk Ethernet error statisticsTo view multilink trunk Ethernet error statistics:

Step Action


The MLT_LACP box appears (Figure 78 "MLT_LACP, LACPGlobal tab" (page 184)).



3 Select a multilink trunk, and then click Graph.

The Statistics, MLT box appears (Figure 82 "Statistics, MLT,Interface tab" (page 194)).

4 Click the Ethernet Errors tab.

The Ethernet Errors tab (Figure 83 "Statistics, MLT, EthernetErrors tab" (page 196)) appears, displaying statistics.


NN46220-511 04.01 26 June 2009


.


Figure 83Statistics, MLT, Ethernet Errors tab

For more information, see Table 37 "Statistics, MLT, EthernetErrors tab fields" (page 196).

--End--

Table 37Statistics, MLT, Ethernet Errors tab fields

Field Description

AlignmentErrors A count of frames received on a particular multilinktrunk that are not an integral number of octets inlength and do not pass the FCS check. The countrepresented by an instance of this object incrementswhen the alignmentError status is returned by the MACservice to the LLC (or other MAC user). Receivedframes for which multiple error conditions occur are,according to the conventions of IEEE 802.3 LayerManagement, counted exclusively according to theerror status presented to the LLC.

FCSErrors A count of frames received on a multilink trunk that arean integral number of octets in length but do not passthe Frame Check Sequence (FCS) check. The countrepresented by an instance of this object incrementswhen the FrameCheckError status is returned by theMAC service to the LLC (or other MAC user). Receivedframes for which multiple error conditions occur are,according to the conventions of IEEE 802.3 LayerManagement, counted exclusively according to theerror status presented to the LLC.


NN46220-511 04.01 26 June 2009


.


Table 37Statistics, MLT, Ethernet Errors tab fields (cont’d.)

Field Description

IMacTransmitError A count of frames for which transmission on aparticular multilink trunk fails due to an internal MACsublayer transmit error. A frame is only counted byan instance of this object if it is not counted by thecorresponding instance of either the LateCollisionsobject, the ExcessiveCollisions object, or theCarrierSenseErrors object.

IMacReceiveError A count of frames for which reception on a particularmultilink trunk fails due to an internal MAC sublayerreceive error. A frame is only counted by an instanceof this object if it is not counted by the correspondinginstance of either the FrameTooLongs object, theAlignmentErrors object, or the FCSErrors object.

The precise meaning of the count represented by aninstance of this object is implementation specific. Inparticular, an instance of this object can represent acount of receive errors on a particular interface that arenot otherwise counted.

CarrierSenseError The number of times that the carrier sense conditionwas lost or never asserted when attempting to transmita frame on a particular multilink trunk. The countrepresented by an instance of this object incrementsat most once per transmission attempt, even if thecarrier sense condition fluctuates during a transmissionattempt.

FrameTooLong A count of frames received on a particular multilinktrunk that exceeds the maximum permitted frame size.The count represented by an instance of this objectincrements when the frameTooLong status is returnedby the MAC service to the LLC (or other MAC user).Received frames for which multiple error conditionsoccur are, according to the conventions of IEEE 802.3Layer Management, counted exclusively according tothe error status presented to the LLC.

SQETestError A count of times that the SQE test error message isgenerated by the PLS sublayer for a particular multilinktrunk. The SQE test error message is defined insection 7.2.2.2.4 of ANSI/IEEE 802.3-1985.


NN46220-511 04.01 26 June 2009


.


Table 37Statistics, MLT, Ethernet Errors tab fields (cont’d.)

Field Description

DeferredTransmiss A count of frames for which the first transmissionattempt on a particular multilink trunk is delayedbecause the medium is busy. The count representedby an instance of this object does not include framesinvolved in collisions.

SingleCollFrames A count of successfully transmitted frames on aparticular multilink trunk for which transmissionis inhibited by exactly one collision. A frame thatis counted by an instance of this object is alsocounted by the corresponding instance of eitherthe ifOutUcastPkts object, the ifOutMulticastPktsobject, or the ifOutBroadcastPkts object, and isnot counted by the corresponding instance of theMultipleCollisionFrames object.

MultipleCollFrames A count of successfully transmitted frames on aparticular multilink trunk for which transmission isinhibited by more than one collision. A frame thatis counted by an instance of this object is alsocounted by the corresponding instance of eitherthe ifOutUcastPkts object, the ifOutMulticastPktsobject, or the ifOutBroadcastPkts object, and isnot counted by the corresponding instance of theSingleCollisionFrames object.

LateCollisions The number of times that a collision is detected on aparticular multilink trunk later than 512 bit-times intothe transmission of a packet; 512 corresponds to 51.2microseconds on a 10 Mb/s system. A (late) collisionincluded in a count represented by an instance of thisobject is also considered as a (generic) collision forpurposes of other collision-related statistics.

ExcessiveCollis A count of frames for which transmission on aparticular multilink trunk fails due to excessivecollisions.

Managing LACP informationStandby mode for aggregation groups of larger than eight ports is notsupported in the current release.

To manage LACP information:


NN46220-511 04.01 26 June 2009


.


Step Action


The MLT_LACP, LACP Global tab appears (Figure 78"MLT_LACP, LACP Global tab" (page 184)).

2 Click the LACP tab.

The LACP tab appears Figure 84 "MLT_LACP, LACP tab" (page199), displaying multilink trunk information.Figure 84MLT_LACP, LACP tab

For more information, see Table 38 "MLT_LACP, LACP tabfields" (page 199).

3 Click on the fields to edit them. Some fields cannot be edited, asnoted in Table 38 "MLT_LACP, LACP tab fields" (page 199) .

4 Click Apply.

--End--

Table 38MLT_LACP, LACP tab fields

Field Description

Index The unique identifier allocated to this aggregatorby the local system. This attribute identifies anaggregator instance among the subordinatemanaged objects of the containing object. Thisvalue is read-only.

MACAddress The six octet read-only value carrying the individualMAC address assigned to the aggregator.

ActorSystemPriority The two octet read-write value indicating thepriority value associated with the actor’s system ID.


NN46220-511 04.01 26 June 2009


.


Table 38MLT_LACP, LACP tab fields (cont’d.)

Field Description

ActorSystemID The six octet read-write MAC address value usedas a unique identifier for the system that containsthis aggregator.

From the perspective of the link aggregationmechanisms, only a single combination of actorsystem ID and system priority are considered,and no distinction is made between the values ofthese parameters for an aggregator and the portsthat are associated with it; that is, the protocol isdescribed in terms of the operation of aggregationwithin a single system. However, the managedobjects provided for the aggregator and the portboth allow management of these parameters.The result of this is to permit a single piece ofequipment to be configured by management tocontain more than one system from the point ofview of the operation of link aggregation. Thiscan be of particular use in the configuration ofequipment that has limited aggregation capability.

AggregateOrIndividual Indicates whether the aggregator represents anaggregate (true) or an individual link (false)

ActorAdminKey The current administrative value of the key for theaggregator. The administrative key value can differfrom the operational key value. This is a 16 bitread-write value. The meaning of particular keyvalues is of local significance.

ActorOperKey The current operational value of the key for theaggregator. The administrative key value can differfrom the operational key value. This is a 16 bitread-only value. The meaning of particular keyvalues is of local significance.

PartnerSystemID The six octet read-only MAC address valueconsisting of the unique identifier for the currentprotocol partner of this aggregator. A value of zeroindicates that there is no known partner. If theaggregation is manually configured, this system IDvalue is a value assigned by the local system.


NN46220-511 04.01 26 June 2009


.


Table 38MLT_LACP, LACP tab fields (cont’d.)

Field Description

PartnerSystemPriority The two octet read-only value that indicates thepriority value associated with the partner systemID. If the aggregation is manually configured, thissystem priority value is a value assigned by thelocal System.

PartnerOperKey The current operational value of the key for theaggregator current protocol partner. This is a 16bit read-only value. If the aggregation is manuallyconfigured, this key value is a value assigned bythe local system.

Configuring a port for LACPTo configure a port for LACP:

Step Action

1 Select a port.

2 From the Device Manager menu bar, choose Edit > Port >General.

The Port, Interface tab appears.


The Port, LACP tab appears (Figure 85 "Port, LACP tab" (page202)), displaying multilink trunk information.


NN46220-511 04.01 26 June 2009


.


Figure 85Port, LACP tab

For more information, see Table 39 "Port, LACP tab fields" (page202).

4 Select AdminEnable.

5 Edit the remaining boxes as desired.

6 Click Apply.

--End--

Table 39Port, LACP tab fields

Field Description

AdminEnable Sets the enabled status for LACP for the port.

OperEnable Indicates the operational status of LACP for the port.

FastPeriodicTime Specifies the number of milliseconds between periodictransmissions using short timeouts for all LACP enabled ports.

FastPeriodicTimeOper The operating value of the fast periodic timer on the port.

SlowPeriodicTime Specifies the number of milliseconds between periodictransmissions using long timeouts for all LACP enabled ports.

SlowPeriodicTimeOper The operating value of the slow periodic timer on the port.

AggrWaitTime Specifies the number of milliseconds to delay aggregation toallow multiple links to aggregate simultaneously.

AggrWaitTimeOper The operating value of the aggregate wait timer on the port.


NN46220-511 04.01 26 June 2009


.


Table 39Port, LACP tab fields (cont’d.)

Field Description

TimeoutScale Sets the value used to calculate timeout time from the periodictime. Set this value to all LACP enabled ports.

TimeoutScaleOper The operating value of the timeout scale on the port.

ActorSystemPriority The two octet read-write value indicating the priority valueassociated with the actor system ID.

ActorSystemID The six octet read-write MAC address value used as a uniqueidentifier for the system that contains this aggregator.

From the perspective of the link aggregation mechanisms, onlya single combination of actor system ID and system priorityare considered, and no distinction is made between the valuesof these parameters for an aggregator and the ports that areassociated with it; that is, the protocol is described in terms ofthe operation of aggregation within a single system. However,the managed objects provided for the aggregator and the portboth allow management of these parameters. The result of thisis to permit a single piece of equipment to be configured bymanagement to contain more than one system from the pointof view of the operation of link aggregation. This can be ofparticular use in the configuration of equipment that has limitedaggregation capability.

ActorAdminKey The current administrative value of the key for the aggregator.The administrative key value can differ from the operationalkey value. This is a 16-bit read-write value. The meaning ofparticular key values is of local significance.

ActorOperKey The current operational value of the key for the aggregator.The administrative key value can differ from the operationalkey value. This is a 16-bit read-only value. The meaning ofparticular key values is of local significance.

SelectedAggID The identifier value of the aggregator that this aggregation porthas currently selected. Zero indicates that the aggregationport has not selected an aggregator, either because it is in theprocess of detaching from an aggregator or because there isno suitable aggregator available for it to select. This value isread-only.

AttachedAggID The identifier value of the aggregator to which this aggregationport is currently attached. Zero indicates that the aggregationport is not currently attached to an aggregator. This value isread-only.


NN46220-511 04.01 26 June 2009


.



Field Description

ActorPort The port number locally assigned to the aggregation port. Theport number is communicated in LACPDUs as the Actor_Port.This value is read-only.

ActorPortPriority The priority value assigned to this aggregation port. This 16-bitvalue is read-write.

ActorAdminState A string of eight bits, corresponding to the administrative valuesas transmitted by the actor in LACPDUs. The values are:

• the first bit corresponds to bit 0 of Actor_State(LACP_Activity)

• the second bit corresponds to bit 1 (LACP_Timeout)

• the third bit corresponds to bit 2 (Aggregation)

• the fourth bit corresponds to bit 3 (Synchronization)

• the fifth bit corresponds to bit 4 (Collecting)

• the sixth bit corresponds to bit 5 (Distributing)

• the seventh bit corresponds to bit 6 (Defaulted)

• the eighth bit corresponds to bit 7 (Expired)

These values allow administrative control over the values ofLACP_Activity, LACP_Timeout and aggregation. This attributevalue is read-write.

ActorOperState A string of eight bits, corresponding to the current operationalvalues of Actor_State as transmitted by the actor in LACPDUs.This attribute value is read-only.

PartnerAdminSystemPriority The current administrative value of the port number forthe protocol Partner. This is a 16 bit read-write value.The assigned value is used, along with the value ofPartnerAdminSystemPriority, PartnerAdminSystemID,PartnerAdminKey, and PartnerAdminPortPriority, to achievemanually configured aggregation.

PartnerOperSystemPriority A two octet read-only value indicating the operational value ofpriority associated with the partner system ID. The value of thisattribute can contain the manually configured value carried inPartnerAdminSystemPriority if there is no protocol partner.

PartnerAdminSystemID A six octet read-write MAC address value representingthe administrative value of the aggregation port protocolpartner’s system ID. The assigned value is used, along withthe value of PartnerAdminSystemPriority, PartnerAdminKey,PartnerAdminPort, and PartnerAdminPortPriority, to achievemanually configured aggregation.


NN46220-511 04.01 26 June 2009


.



Field Description

PartnerOperSystemID A six octet read-only MAC address value representing thecurrent value of the aggregation port’s protocol partner systemID. A value of zero indicates that there is no known protocolpartner. The value of this attribute can contain the manuallyconfigured value carried in PartnerAdminSystemID if there isno protocol partner.

PartnerAdminKey The current administrative value of the key for theprotocol partner. This is a 16 bit read-write value.The assigned value is used, along with the value ofPartnerAdminSystemPriority, PartnerAdminSystemID,PartnerAdminPort, and PartnerAdminPortPriority, to achievemanually configured aggregation.

PartnerOperKey The current operational value of the key for the aggregatorcurrent protocol partner. This is a 16-bit read-only value. If theaggregation is manually configured, this key value is a valueassigned by the local system.

PartnerAdminPort The current administrative value of the port number forthe protocol partner. This is a 16 bit read-write value.The assigned value is used, along with the value ofPartnerAdminSystemPriority, PartnerAdminSystemID,PartnerAdminKey, and PartnerAdminPortPriority, to achievemanually configured aggregation.

PartnerOperPort The operational port number assigned to this aggregation portby the aggregation port’s protocol partner. The value of thisattribute can contain the manually configured value carried inAggPortPartnerAdminPort if there is no protocol partner. This16 bit value is read-only.

PartnerAdminPortPriority The current administrative value of the port priority forthe protocol Partner. This is a 16 bit read-write value.The assigned value is used, along with the value ofPartnerAdminSystemPriority, PartnerAdminSystemID,PartnerAdminKey, and PartnerAdminPort, to achieve manuallyconfigured aggregation.

PartnerOperPortPriority The priority value assigned to this aggregation port by thepartner. The value of this attribute can contain the manuallyconfigured value carried in PartnerAdminPortPriority if there isno protocol Partner. This 16 bit value is read-only.


NN46220-511 04.01 26 June 2009


.



Field Description

PartnerAdminState A string of eight bits, corresponding to the currentadministrative value of Actor_State for the protocol partner.This attribute value is read-write. The assigned value is used toachieve manually configured aggregation.

PartnerOperState A string of eight bits, corresponding to the current values ofActor_State in the most recently received LACPDU transmittedby the protocol Partner. In the absence of an active protocolpartner, this value can reflect the manually configured valuePartnerAdminState. This attribute value is read-only.

Viewing LACP statisticsTo view LACP statistics for a particular port:

Step Action

1 Select a port.

2 From the Device Manager menu bar, choose Graph > Port.

The Graph Port, Interface tab appears (Figure 86 "Graph Port,Interface tab" (page 206)).Figure 86Graph Port, Interface tab



NN46220-511 04.01 26 June 2009


.


The LACP tab appears (Figure 87 "Graph Port, LACP tab" (page207)), displaying LACP statistics.Figure 87Graph Port, LACP tab

4 You can change the Poll Interval if desired.

For more information, see Table 40 "Graph Port, LACP tabfields" (page 207).

--End--

Table 40Graph Port, LACP tab fields

Field Description

LACPDUsRx The number of valid link aggregation control protocol data units(LACPDU) received on this aggregation port.

MarkerPDUsRx The number of valid marker PDUs received on this aggregationport.

MarkerResponsePDUsRx The number of valid marker response PDUs received on thisaggregation port.

UnknownRx The number of frames received that either:

• carry Slow Protocols Ethernet type values, but contain anunknown PDU.

• are addressed to the Slow Protocols group MAC Address,but do not carry the Slow Protocols Ethernet Type.

IllegalRx The number of frames received that carry the Slow ProtocolsEthernet Type value (43B.4), but contain a badly formed PDUor an illegal value of Protocol Subtype (43B.4).

LACPDUsTx The number of LACPDUs transmitted on this aggregation port.


NN46220-511 04.01 26 June 2009


.


Table 40Graph Port, LACP tab fields (cont’d.)

Field Description

MarkerPDUsTx The number of marker PDUs transmitted on this aggregationport.

MarkerResponsePDUsTx The number of marker response PDUs transmitted on thisaggregation port.

Configuring Split Multilink TrunkingRouted SMLT, or RSMLT, is a Layer 3 protocol whereas SMLT is a Layer2 protocol. SMLT is described in this document, and RSMLT is describedin the document Configuring IP Routing Operations.

This section describes how to use Device Manager to configure SplitMultiLink Trunking (SMLT) and includes the following topics:

• “Adding a MLT-based SMLT” (page 208)

• “Viewing MLT-based SMLTs” (page 210)

• “Adding ports to an MLT-based SMLT” (page 211)

• “Configuring an IST multilink trunk” (page 212)

• “Viewing IST statistics” (page 214)

• “Configuring a single port split multilink trunk” (page 216)

• “Viewing Single Port SMLTs” (page 218)

• “Deleting a Single Port SMLT” (page 219)

Adding a MLT-based SMLTIf you are configuring SMLT, you do not need to create a multilink trunkbefore creating an SMLT. You can create an SMLT by selecting themultilink trunk type as split multilink trunk and then specifying an SMLT ID.

To add an MLT-based split multilink trunk:

Step Action


The MLT_LACP box appears (Figure 78 "MLT_LACP, LACPGlobal tab" (page 184)).



NN46220-511 04.01 26 June 2009


.

Configuring Split Multilink Trunking 209


3 Click Insert.

The MultiLink/LACP, Insert MultiLink/LACP Trunks box (Figure80 "MLT_LACP, Insert MultiLink/LACP Trunks box" (page 187))appears.

4 In the Id box, the next available MLT ID is displayed. You canuse this ID or type an available MLT ID number.

5 In the SvlanPortType box, select normal.

6 In the PortType box, select Access or Trunk.

7 In the Name box, type a name to identify the MLT-based splitmultilink trunk port.

8 In the PortMembers box, click the ellipsis (...).

The MltPortMembers box appears, displaying the available ports.

9 Click the ports you want to include in the MLT-based splitmultilink trunk.

For Metro Ethernet Routing Switch 8600 modules, up to eightsame-type ports can belong to a multilink trunk.

10 Click Ok.

The MltPortMembers box closes and the ports are added to thePortMembers box on the Insert MultiLink Trunks tab.

11 In the VlanIds box, click the ellipsis (...).

The VlanIds box appears, displaying the available VLANs.

12 Select the VLAN IDs for the MLT-based split multilink trunk port,and then click Ok.

The VlanIds box closes and the VLANs are added to the VlanIdsbox in the MLT, Insert Trunks box.

13 In the MltType box, select splitMLT.

The SmltId box becomes editable.

14 In the SmltId box, type an unused SMLT ID.

The corresponding split multilink trunks between aggregationswitches must have matching SMLT IDs. The same ID numbermust be used on both switches.

To view the SMLT IDs currently in use on the switch, see“Viewing Single Port SMLTs” (page 218).

15 Click Insert.

The Insert MultiLink/LACP Trunks box closes, and the newMLT-based split multilink trunk appears in the MultiLink/LACPTrunks tab.


NN46220-511 04.01 26 June 2009


.


16 On the MultiLink/LACP Trunks tab, click Close.

The MLT-based split multilink trunk is added.

--End--

Viewing MLT-based SMLTsTo view the MLT-based split multilink trunks configured on your switch:

Step Action

1 From the menu bar, choose VLAN > SMLT.

The SMLT box appears (Figure 94 "SMLT, Single Port SMLT"(page 219)).

2 Click the SMLT Info tab.

The SMLT Info tab appears with all the configured MLT-basedsplit multilink trunks displayed (Figure 88 "SMLT, SMLT Info tab"(page 210)).Figure 88SMLT, SMLT Info tab

For more information, see Table 41 "SMLT, SMLT Info tab fields"(page 210).

--End--

Table 41SMLT, SMLT Info tab fields

Field Description

Id Read-only field displaying the MLT ID for this splitmultilink trunk.


NN46220-511 04.01 26 June 2009


.


Table 41SMLT, SMLT Info tab fields (cont’d.)

Field Description

SmltId The MLT-based split multilink trunk ID number.

MltType Specifies the type of multilink trunk:

• normalMLT

• istMLT

• splitMLT

RunningType Indicates the MLT operational type:

• normalMLT

• istMLT

• splitMLT

Adding ports to an MLT-based SMLTTo add ports to an existing MLT-based split multilink trunk:

Step Action


The LACP Global tab appears (Figure 78 "MLT_LACP, LACPGlobal tab" (page 184)).



3 Double-click the PortMembers box for the MLT-based splitmultilink trunk to which you are adding ports.

The MltPortMembers box (Figure 81 "MltPortMembers box"(page 193)) appears for the specified SMLT ID. Available portsare editable.

4 Select the port numbers to be added, or click All to select allports.

• For Metro Ethernet Routing Switch 8600 modules, up to eightsame-type ports can belong to a single multilink trunk.

5 Click Ok.

The MltPortMembers box closes and the ports are added to thePort Members box on the MultiLink Trunks tab.


NN46220-511 04.01 26 June 2009


.


6 On the MultiLink/LACP Trunks tab, click Apply.

The ports are added to the MLT-based split multilink trunk.

--End--

Configuring an IST multilink trunkTo configure an IST multilink trunk:

Step Action





3 Click Insert.

The MLT_LACP, Insert Multilink/LACP Trunks box (Figure 80"MLT_LACP, Insert MultiLink/LACP Trunks box" (page 187))appears.

4 In the PortMembers box for the IST multilink trunk, click theellipsis (...).

The MltPortMembers box appears, displaying the available ports.

5 Click the ports you want to include in the IST multilink trunk.

6 Click Ok.

The MltPortMembers box closes and the ports are added tothe PortMembers box for the IST multilink trunk in the InsertMultiLink Trunks tab.

7 In the MltType box, select istMLT.

8 In the PortType box, select trunk.

9 Configure the remaining boxes as required.

10 Click Insert.

The IST MLT box appears (Figure 89 "IST MLT" (page 213)).


NN46220-511 04.01 26 June 2009


.


Figure 89IST MLT

11 Enter the peer IP address and the VLAN ID.

12 Select enable, then click Apply.

The IST is added to the MLT_LACP box.

13 Disable CP-Limit on the port using the CLI command:

config ethernet <slot/port> cp-limit disable

The IST multilink trunk is configured.

For more information, see Table 42 "Ist multilink trunk fields"(page 213).

--End--

Table 42Ist multilink trunk fields

Field Description

PeerIp IST multilink trunk peer IP address.

VlanId An IST VLAN ID number.

SessionEnable Enables and disables IST functionality.

Editing an ISTTo edit an existing IST, use the following procedure.

Step Action

1 In Device Manager, go to VLAN > MLT/LACP >MultiLink/LACP Trunks.

2 In the MLT_LACP box, select the IST.


NN46220-511 04.01 26 June 2009


.


3 Click IstMlt.

The IST MLT box (Figure 90 "IST MLT" (page 214)) appears.For field definitions, see Table 42 "Ist multilink trunk fields" (page213) .Figure 90IST MLT

4 In the PeerIp box, enter the peer IP address.

5 In the VlanId box, enter a VLAN ID.

6 In the SessionEnable box, select either enable or disable.

7 Click Apply.

The IST MLT box closes and the changes are applied.

--End--

Viewing IST statisticsTo view IST statistics on an interface:

Step Action



2 Click the Ist/SMLT Stats tab.

The Ist/SMLT Stats tab appears (Figure 91 "Ist/SMLT Stats tab"(page 215)).


NN46220-511 04.01 26 June 2009


.


Figure 91Ist/SMLT Stats tab

For more information, see Table 43 "MLT_LACP, Ist/SMLT Statstab fields" (page 215).

--End--

Table 43MLT_LACP, Ist/SMLT Stats tab fields

Field Description

SmltIstDownCnt The number of IST down messages.

SmltHelloTxMsgCnt The number of hello messages transmitted.

SmltHelloRxMsgCnt The number of hello messages received.

SmltLearnMacAddrTxMsgCnt The number of learn MAC address messages transmitted.

SmltLearnMacAddrRxMsgCnt The number of learn MAC address messages received.

SmltMacAddrAgeOutTxMsgCnt The number of MAC address aging out messagestransmitted.

SmltMacAddrAgeOutRxMsgCnt The number of MAC address aging out messagesreceived.


NN46220-511 04.01 26 June 2009


.


Table 43MLT_LACP, Ist/SMLT Stats tab fields (cont’d.)

Field Description

SmltMacAddrAgeExpTxMsgCnt The number of MAC address age expired messagestransmitted.

SmltMacAddrAgeExpRxMsgCnt The number of MAC address age expired messagesreceived.

SmltStgInfoTxMsgCnt The number of SMLT STG info messages transmitted.

SmltStgInfoRxMsgCnt The number of SMLT STG info messages received.

SmltDelMacAddrTxMsgCnt The number of deleted MAC address messagestransmitted.

SmltDelMacAddrRxMsgCnt The number of deleted MAC address messages received.

SmltSmltDownTxMsgCnt The number of SMLT down messages transmitted.

SmltSmltDownRxMsgCnt The number of SMLT down messages received.

SmltSmltUpTxMsgCnt The number of SMLT up messages transmitted.

SmltSmltUpRxMsgCnt The number of SMLT up messages received.

SmltSendMacTblTxMsgCnt The number of send MAC table messages transmitted.

SmltSendMacTblRxMsgCnt The number of send MAC table messages received.

SmltIgmpTxMsgCnt The number of IGMP messages transmitted.

SmltIgmpRxMsgCnt The number of IGMP messages received.

SmltPortDownTxMsgCnt The number of port down messages transmitted.

SmltPortDownRxMsgCnt The number of port down messages received.

SmltReqMacTblTxMsgCnt The number of request MAC table messages transmitted.

SmltReqMacTblRx MsgCnt The number of request MAC table messages received.

SmltRxUnknownMsgTypeCnt The number of unknown SMLT messages received.

Configuring a single port split multilink trunkPorts that are already configured as MLT or MLT-based split multilinktrunks cannot be configured as a single port split multilink trunk. You mustfirst remove the split trunk and then reconfigure the ports as a single portsplit multilink trunk.

LACP is supported on single port split multilink trunks.

To configure a single port split multilink trunk:

Step Action

1 From the Device Manager main window, select the port.


NN46220-511 04.01 26 June 2009


.





3 Click the SMLT tab.

The Port, SMLT tab (Figure 92 "Port, SMLT tab" (page 217))appears.

The SMLT tab indicates if this port is already configured as MLTor MLT-based SMLT. If so, you cannot configure Single PortSMLT.Figure 92Port, SMLT tab

4 Click Insert.

The Insert SMLT box appears (Figure 93 "Port, Insert SMLT"(page 217)).Figure 93Port, Insert SMLT

5 In the SmltId box, enter an unused SMLT ID number.

To view the SMLT IDs that are already in use on your switch,see “Viewing Single Port SMLTs” (page 218).

6 Click Insert.

A warning message appears, informing you that the spanningtree protocol has been disabled while configuring the port withSMLT.

7 Click Ok.

The Insert SMLT box closes and the ID is entered.


NN46220-511 04.01 26 June 2009


.


Table 44 "Port SMLT tab fields" (page 218).

--End--

Table 44Port SMLT tab fields

Field Description

Port The slot/port number for the port.

MltId Indicates one of the following:

• A value of 1 to 32 (or 128 for R modules in R mode)indicates that the port is part of an multilink trunk,and Single Port SMLT cannot be configured on thisport.

• A value of 0 indicates that no multilink trunk isassigned, and the port can be configured for SinglePort SMLT.

SmltId The split multilink trunk ID.

• A read-only field indicates the port Single PortSMLT ID assignment.

• A blank field indicates the port is not configuredfor Single Port SMLT. Find an unused SMLT ID byviewing the currently used IDs. See “Viewing SinglePort SMLTs” (page 218).

Viewing Single Port SMLTsTo view the single port split multilink trunks configured on your switch:

Step Action

1 From the menu bar, choose VLAN > SMLT.

The SMLT box appears, and shows the single port split multilinktrunks currently configured on your switch Figure 94 "SMLT,Single Port SMLT" (page 219).


NN46220-511 04.01 26 June 2009


.


Figure 94SMLT, Single Port SMLT

--End--

For more information, see Table 45 "SMLT, Single Port SMLT tab fields"(page 219).

Table 45SMLT, Single Port SMLT tab fields

Field Description

Port Indicates the port interface index number.

SmltId The ID number of the single port split multilink trunk.

RunningType Indicates the port operational type:

• normalMLT

• istMLT

• splitMLT

Deleting a Single Port SMLTTo delete a single port split multilink trunk:

Step Action

1 From the Device Manager main window, select the port.



NN46220-511 04.01 26 June 2009


.




3 Click the SMLT tab.

The Port, SMLT tab (Figure 95 "Deleting a Single Port SMLT"(page 220)) appears, displaying the Single Port SMLT ID.Figure 95Deleting a Single Port SMLT

4 Select the single port split multilink trunk.

The single port split multilink trunk is highlighted.

5 Click Delete, and then click Close.

The single port split multilink trunk is deleted.

--End--

Configuring Simple Loop Prevention ProtocolSimple Loop Prevention Protocol (SLPP) is used at the edge of a networkto prevent loops in a SMLT network if Spanning Tree is not used.

SMLT is only applicable to NNI ports.

This section describes how to configure Simple Loop Prevention Protocol(SLPP), and includes the following topics:

• “Configuring SLPP globally” (page 220)

• “Configuring the SLPP by VLAN” (page 222)

• “Configuring the SLPP by port” (page 223)

Configuring SLPP globallyTo configure Simple Loop Prevention Protocol (SLPP) globally:


NN46220-511 04.01 26 June 2009


.

Configuring Simple Loop Prevention Protocol 221

Step Action

1 From the Device Manager menu bar, select VLAN > SLPP.

The Slpp box appears with the Global tag displayed.Figure 96SLPP, Global

For more information, see Table 46 "SLPP, Global tab fields"(page 221).

2 Select GlobalEnable.

3 In the TransmissionInterval box, enter a value for the timeinterval for loop detection.

4 In the EtherType box, enter the SLPP protocol value as ahexadecimal number.

5 In the UniPorts field, specify the UNI ports added under theSLPP global configuration.

6 Click Apply.

--End--

Table 46SLPP, Global tab fields

Field Description

GlobalEnable Globally enables or disables SLPP.

TransmissionInterval Sets the interval (in milliseconds) for which loopdetection occurs. The range is 500 to 5000 ms, andthe default is 500 ms.

Ether Type Specifies the SLPP protocol identification. This value isexpressed in hexadecimal.

UniPorts Specifies the UNI ports added under the SLPP globalconfiguration.


NN46220-511 04.01 26 June 2009


.


Configuring the SLPP by VLAN

Step Action


The Slpp box appears with the Global tag displayed.

2 Click the VLANS tab.

The VLANS tab appears.Figure 97Slpp, VLANS tab

3 Click Insert.

The Slpp, Insert VLANS box appears.Figure 98Slpp, Insert VLANS

For more information, see Table 47 "Slpp, Insert VLANS fields"(page 223).

4 Click the VlanID ellipsis (...).

The VlanId box appears.


NN46220-511 04.01 26 June 2009


.


Figure 99Slpp, Insert VlanId

5 Select the desired VLAN ID.

6 Click Ok.

7 Select SlppEnable.

8 Click Insert.

The ID and status of the selected VLAN appears in the Slpp,VLANS box (Figure 97 "Slpp, VLANS tab" (page 222)).

--End--

Table 47Slpp, Insert VLANS fields

Field Description

VlanId Specifies the VLAN.

SlppEnable Enables SLPP on the selected VLAN. The SLPPpacket transmission and reception process is activeonly when the SLPP operation is enabled. When theSLPP operation is disabled, no SLPP packet is sent,and any received SLPP packet is discarded.

Configuring the SLPP by portTo configure SLPP by port:

Step Action


The Slpp box appears with the Global tag displayed.



NN46220-511 04.01 26 June 2009


.


The Slpp, Ports tab appears displaying all available ports.Figure 100Slpp, Ports tab

3 Click the SlppEnable box for the desired port and select true toenable SLPP.

4 Click Apply.

The ID and status of selected VLAN appears in the Slpp, VLANSdialog box (Figure 97 "Slpp, VLANS tab" (page 222)).

For more information, see Table 48 "Slpp, Ports tab fields" (page224).

--End--

Table 48Slpp, Ports tab fields

Field Description

IfIndex Specifies the interface index number for a port.

PktRxThreshold Specifies the threshold for packet reception from 1to 20. After a port reaches the packet threshold, it isdisabled.


NN46220-511 04.01 26 June 2009


.


Table 48Slpp, Ports tab fields (cont’d.)

Field Description

SlppEnable Enables SLPP on the selected interface.

IncomingVlanId VLAN ID of the classified packet on a port disabled bySLPP.

SrcNodeType Specifies the source node type of the received SLPPpacket.

PktRxCount Specifies the total number of SLPP packets receivedon the port. Valid values are 1 to 500.


NN46220-511 04.01 26 June 2009


.



NN46220-511 04.01 26 June 2009


.

227.

Setting the sVLAN Ethertype usingDevice Manager

Use this procedure to configure the stacked VLAN (sVLAN) Ethertype forthe switch.

sVLANs are not supported on the Metro Ethernet Routing Switch 8600R modules.

Procedure 1Setting the sVLAN Ethertype

Step Action

1 From the Device Manager menu, select VLAN, SVLAN.

The Svlan, Ether Type tab appears, displaying the Ether typesused for sVLAN tagging.Figure 101SVLAN, Ether Type tab


NN46220-511 04.01 26 June 2009


.

228 Setting the sVLAN Ethertype using Device Manager

2 To modify an Ethertype, double-click an EtherType box andenter a new value.

“SVLAN, Ether Type tab” (page 228) describes the sVLAN EtherType tab.

3 Click Apply.

The Ethertype is configured.

--End--

SVLAN, Ether Type tabTable 49SVLAN, Ether Type tab

Field Description

Id Index ID for this row in the table of switch levels.

Level The switch level associated with this entry.

EtherType Specifies the Ethertype used for sVLAN tagging.

The following are the default Ethertypes and switchlevels:

• Level 0 — 0x8100 (Ethertype defined by IEEE for802.1Q tagged frames)

• Level 1 — 0x8020

• Level 2 — 0x8030

• Level 3 — 0x8040

• Level 4 — 0x8050

• Level 5 — 0x8060

• Level 6 — 0x8070

• Level 7 — 0x8080


NN46220-511 04.01 26 June 2009


.

229.

Setting the sVLAN switch level usingDevice Manager

Use this procedure to configure the stacked VLAN (sVLAN) switch level.

sVLANs are not supported on the Metro Ethernet Routing Switch 8600R modules.

Procedure 2Setting the sVLAN switch level

Step Action

1 From the Device Manager menu, select VLAN, SVLAN.

The Svlan, Ether Type tab appears, displaying the Ether typesused for sVLAN tagging.Figure 102SVLAN, Ether Type tab

2 Click the Level tab.


NN46220-511 04.01 26 June 2009


.

230 Setting the sVLAN switch level using Device Manager

The Level tab appears.Figure 103Svlan box, Level tab

3 In the ActiveLevel box, enter an active switch level.

Change the switch level default of 0 to a value of 1 through 7before configuring UNI or NNI ports.

4 Click Apply.

The active switch level is configured.

For more information, see “SVLAN, Level tab” (page 230).

--End--

SVLAN, Level tabTable 50SVLAN, Level tab

Field Description

Active Level Specifies the active level for the switch. The default islevel 0.

You must configure the switch level to 1 or abovebefore configuring UNI or NNI ports.


NN46220-511 04.01 26 June 2009


.

231.

Configuring Simple Loop PreventionProtocol with Device Manager

Use this procedure to add UNI ports under the global SLPP config, or todisplay the total number of SLPP PDUs received on a particular port.

Procedure 3Configuring Simple Loop Prevention Protocol

Step Action

1 From the Device Manager menu, select VLAN -> SLPP-> Ports.


NN46220-511 04.01 26 June 2009


.

232 Configuring Simple Loop Prevention Protocol with Device Manager

Figure 104SLPP box, Ports tab

Because this screen does not show port types, just the portnumbers, you must know which ports are UNI or NNI.

For more information, see “SLPP, Ports tab fields” (page 232)

--End--

SLPP, Ports tab fieldsTable 51SLPP, Ports tab

Field Description

PktRxCount Indicates the number of SLPP PDUs received on the port.

SrcNodeType This is the same as SLPP PDU Generator column displayed via the CLIShow Command.


NN46220-511 04.01 26 June 2009


.

233.

Configuring and managing VLANsusing the CLI

This section describes how to configure and manage VLANs using thecommand line interface (CLI), and includes the following topics:

• “Roadmap of VLAN commands” (page 233)

• “Configuring and managing a VLAN” (page 237)

• “Using the VLAN show commands” (page 258)

• “Using the show ports commands for VLANs” (page 280)

• “Using the VLAN IP commands” (page 283)

For conceptual information about VLANs, see “VLANs” (page 21).

Roadmap of VLAN commandsThe following roadmap lists the VLAN commands and their parameters.Use this list as a quick reference.

Command Parameter

config vlan <vid> create info

byIDS <sid> [name <value>] [color<value>]

byipsubnet <sid> <ipaddr/mask> [name <value>] [color <value>]

byipsubnet-mstp <instance-id><ipaddr|mask> [name <value>][color <value>]

byport <sid> [name <value>] [color<value>]

byport-mstp <instance-id>[name <value>] [color <value>][naap-vlan] [firewall-vlan][firewall-peering-vlan]


NN46220-511 04.01 26 June 2009


.

234 Configuring and managing VLANs using the CLI

Command Parameter

byprotocol <sid> <ip|appleTalk|decLat|decOther|sna802dot2|snaEthernet2|netBios|xns|vines|ipV6|usrDefined|rarp|PPPoE> [<pid>] [name <value>][color <value>] [encap <value>]

byprotocol-mstp <instance-id><ip|appleTalk|decLat|decOther|sna802dot2|snaEthernet2|netBios|xns|vines|ipV6|usrDefined|rarp|PPPoE>[<pid>] [name <value>] [color<value>] [encap <value>]

bysrcmac <sid> [name <value>][color <value>]

bysrcmac-mstp <instance-id> [name<value>] [color <value>]

bysvlan <sid> [name <value>][color <value>]

bysvlan-mstp <instance-id> [name<value>] [color <value>]

forIDS <sid> [name <value>] [color<value>]

forIDS-mstp <instance-id> [name<value>] [color <value>]

config vlan <vid> info

add-ring <integer> [<ibtvlan-true|rctvlan-true>]

addDsapSsap <DSAP/SSAP values>

btag-ethertype-apply <true|false>

tls-ipmc <enable|disable>

ext-filter <fwd-all|fwd-unreg|filter-unreg> [port <value>] [all]

mgmt-vlan <true|false>

mmrp <enable|disable>

removeDsapSsap <DSAP/SSAP values>

action <action choice>

add-mlt <integer>

agetime <integer>

delete

qos-level <integer>


NN46220-511 04.01 26 June 2009


.

Roadmap of VLAN commands 235

Command Parameter

name <vname>

config vlan <vid> fdb-entry info

aging-time <seconds>

flush

monitor <mac> status <value><true|false>

qos-level <mac> status <value><0..7>

sync

config vlan <vid> fdb-filter info

add <mac> port <value> [qos<value>]

pcap <mac> <enable|disable>

remove <mac>

config vlan <vid> fdb-filternotallowfrom

info

add <mac> port <value> [<srcOnly|dstOnly|Both>]

remove <mac> port <value>[<srcOnly|dstOnly|Both>]

config vlan <vid> fdb-static info

add <mac> port <value> [qos<value>]

remove <mac>

config vlan <vid> ports info

add <ports> [member <value>]

remove <ports> [member <value>]

ospf-passive <true|false> <ports>

config vlan <vid> srcmac info

add <macaddr>

remove <macaddr>

config vlan <vid> ip info


NN46220-511 04.01 26 June 2009


.


Command Parameter

create <ipaddr|mask> [mac_offset<value>]

delete <ipaddr>

Rvs-Path-Chk <enable|disable>[mode <value>]

config vlan <vid> ip nlb-unicast-mode

info

<enable|disable>

config sys set flag enhanced-operational-mode

<true|false>

config ethernet <port> loop-detect<enable|disable>

action <port-down|vlan-block|mac-discard>

arp-detect <enable|disable>

config ether <ports> auto-recover-port <enable|disable>

config ethernet <port number>action clearLoopDetectAlarm

config ethernet <port number> info

config mac-flap-time-limit<10..5000 milliseconds>

show ports info loop-detected port<port number>

show sys link-flap-detectgeneral-info

show ports info loop-detected port<port number>

show vlan info all <vid> ] [port<value>] [by <value>]

show vlan info advance <vid>][port <value>]

show vlan info arp [<vid>] [port<value>]

show vlan info basic [<vid>] [port<value>]

show vlan info brouter-port [port<value>]


NN46220-511 04.01 26 June 2009


.

Configuring and managing a VLAN 237

Command Parameter

show vlan info fdb-entry [<vid>][mac <value>] [port <value>]

show vlan info fdb-filter [<vid>][mac <value>] [port <value>]

show vlan info fdb-static [<vid>][mac <value>] [port <value>]

show vlan info igmp [<vid>] [port<value>]

show vlan info ip [<vid>] [port<value>]

show vlan info ports [<vid>] [port<value>]

show vlan info srcmac [<vid>][port <value>]

show ports info all [vlan <value>][port <value>] [by <value>]

show ports info vlans [vlan<value>] [port <value>]

Configuring and managing a VLANTo create VLANs, add or remove ports in the VLAN, set priority, changea VLAN name, or perform other operations, use the VLAN configurationcommands. You can also configure reverse path checking, loop detection,Enhanced Operation mode, and other features using the CLI. In all VLANcommands in this section, vid is the VLAN ID.

This section includes the following procedures:

• “Creating a VLAN” (page 238)

• “Performing general VLAN operations” (page 243)

• “Configuring VLAN parameters in the forwarding database” (page 245)

• “Limiting MAC learning” (page 250)

• “Adding or removing VLAN ports” (page 251)

• “Adding or removing VLAN source MAC addresses” (page 252)

• “Configuring Untagging Default VLAN on a Tagged Port” (page 252)

• “Configuring Enhanced Operation mode” (page 253)

• “Configuring VLAN Loop Detection” (page 254)

• “Configuring spoof detection for a VLAN” (page 258)


NN46220-511 04.01 26 June 2009


.


Creating a VLANTo create a VLAN, use the following command:

config vlan <vid> create

You can specify the type of VLAN and assign an IP address to the VLANusing this command. The required parameter vid is the VLAN ID. VLAN 1is the default VLAN.

This command includes the following parameters:


followed by:

info Shows information about the type of the specified VLAN.

byIDS <sid> [name <value>][color <value> ]

Creates a VLAN for IDS.

<sid> is spanning tree ID 1 to 64.

name <value> is the name of the vlan from 0 to 64characters.

color <value> is the color of the VLAN (0 to 32). Thecolor attribute is used by Optivity software to display theVLAN.

The EVPN services type must be byport and therefore thisVLAN type cannot be used for EVPN services.

byipsubnet <sid> <ipaddr/mask> [ name <value> ] [color<value> ]

Creates an IP subnet-based VLAN.

• sid is a spanning tree group ID.

• ipaddr/mask is the IP address and mask {a.b.c.d/x| a.b.c.d/x.x.x.x | default}.

• name <value> is the name of the VLAN from 0 to 20characters.

• color <value> is the color of the VLAN (0 to 32).The color attribute is used by Optivity software todisplay the VLAN.

This command is available only for the Metro EthernetRouting Switch 8600.



NN46220-511 04.01 26 June 2009


.



followed by:

byipsubnet-mstp <instance-id> <ipaddr|mask> [name <value>] [color <value> ]

Creates a VLAN by IP subnet.

• <instance-id> is the instance ID from 0 to 63.

• <ipaddr/mask> is the subnet address or mask{a.b.c.d/x | a.b.c.d/x.x.x.x | default}.

• name <value> is the name of the VLAN.

• color <value> is the color of the VLAN from 0 to32. The color attribute is used by Optivity software todisplay the VLAN.


byport <sid> [name <value> ][color <value> ]

Creates a port-based VLAN.

• <sid> is the spanning tree group ID from 1 to 64characters.


• color <value> is the color of the VLAN from 0 to32. The color attribute is used by Optivity software todisplay the VLAN.

This VLAN type is the only one supported for EVPNservices with STP mode set to default.

byport-mstp <instance-id>[name <value> ] [color <value>] [naap-vlan] [firewall-vlan][firewall-peering-vlan]

Creates a VLAN by port.


• name <value> is the name of the VLAN.

• color <value> is the color of the VLAN from 0 to 32.

• naap-vlan marks the VLAN as a NAAP VLAN.

• firewall-vlan marks the VLAN as a firewall VLAN.

• firewall-peering-vlan marks the VLAN as afirewall peering VLAN.

This VLAN type is the only one supported for EVPNservices with STP mode set to MSTP.

The system checks the consistency with the existingmapping of the Multiple Spanning Tree Instance (MSTI)and the VLAN identifier (VID). If correct, the VLAN is


NN46220-511 04.01 26 June 2009


.



followed by:

created; if not correct, a warning for traffic disruption isdisplayed and the mapping is updated only when the userconfirms the change.

byprotocol <sid> <ip|appleTalk|declat|decOther|sna802dot2|snaEthernet2|netBios|xns|vines|ipV6|usrDefined|rarp|PPPoE>[<pid>] [name <value>] [color<value>] [encap <value>]

Creates a protocol-based VLAN.

• <sid> is spanning tree ID.

• ip|appleTalk|decLat|decOther|sna802dot2|snaEthernet2|netBios|xns|vines|ipV6|usrDefined|rarp |PPPoE specifies the protocol.

• pid is a user-defined protocol ID number inhexadecimal.



• encap <value> is the frame encapsulation method.


byprotocol-mstp <instance-id> <ip|appleTalk|decLat|decOther|sna802dot2|snaEthernet2|netBios|xns|vines|ipV6|usrDefined|rarp|PPPoE> [ <pid> ][name <value> ] [color <value>] [encap <value> ]

Creates a VLAN by protocol.

• <instance-id> is the instance ID.

• <ip|appleTalk|decLat|decOther|sna802dot2|snaEthernet2|netBios|xns|vines|ipV6|usrDefined|rarp|PPPoE> is the protocol ID.

• <pid> is the user-defined PID number.



• encap <value> is the frame encapsulation with thevalues ethernet-ii, llc, or snap.



NN46220-511 04.01 26 June 2009


.



followed by:

bysrcmac <sid> [name <value> ][color <value> ]

Creates a VLAN by source MAC address.

• <sid> is the spanning tree ID from 1 to 64.



This command is available only for the Metro EthernetRouting Switch 8600.


bysrcmac-mstp <instance-id>[name <value> ] [color <value>]

Creates a VLAN by source MAC address





bysvlan <sid> [name <value> ][color <value> ]

Creates an sVLAN.


• name <value> is the name of the sVLAN from 0 to 20characters.




NN46220-511 04.01 26 June 2009


.



followed by:

bysvlan-mstp <instance-id>[name <value> ] [color <value>]

Creates an sVLAN.


• name <value> is the name of the sVLAN.

• color <value> is the color of the sVLAN from 0 to32. The color attribute is used by Optivity software todisplay the VLAN.


forIDS <sid> [name <value> ][color <value> ]

Creates a VLAN for IDS.




forIDS-mstp <instance-id>[name <value> ] [color <value>]

Creates a VLAN for IDS




Figure 105 "Config vlan create info command output" (page 243) showssample output for the config vlan create info command.


NN46220-511 04.01 26 June 2009


.


Figure 105Config vlan create info command output

Performing general VLAN operationsTo perform general VLAN operations, such as setting a Quality of Service(QoS) level for the VLAN or adding or changing the name of a VLAN, usethe following command:

config vlan <vid>

In all VLAN commands, vid is the VLAN ID.

This command includes the following options:

config vlan <vid>

followed by:

info Shows characteristics of the specified VLAN (Figure 106"Config vlan info command output" (page 244)).

action <action choice> Flushes a table or triggers an RIP update.

• <action choice> is {none| flushMacFdb|flushArp|flushIp| flushDynMemb|all|flushSnoopMemb|triggerRipUpdate|flushSenders| flushSnoopMRtr}. Toflush all tables, use all.

add-mlt <integer> Adds an MLT to a VLAN.

• <integer> is the MLT ID.

agetime <integer> Sets the VLAN aging time in seconds.

delete Deletes a VLAN.The mapping between the Multiple Spanning TreeInstance (MSTI) and the VLAN Identifier (VID) is notdeleted.


NN46220-511 04.01 26 June 2009


.


config vlan <vid>

followed by:

qos-level <integer> Sets a Quality of Service level for a VLAN.

• <integer> is the QoS level.

QoS level 7 is reserved for network control traffic.

name <vname> Changes the name of a VLAN.

• <vname> is a string of length 0 to 20 characters.

Figure 106 "Config vlan info command output" (page 244) shows sampleoutput for the config vlan info command.

Figure 106Config vlan info command output


The following configuration example uses the config vlan commands todelete a VLAN.

After configuring the parameters, use the info command to show asummary of the results.


NN46220-511 04.01 26 June 2009


.


MERS-8606:5/config/vlan/10# addDsapSsap 0x0808MERS-8606:5/config/vlan/10# infoSub-Context: create fdb-entry fdb-filter fdb-static ip ipx ports srcmacstatic-mcastmacCurrent Context:action : N/A

add-mlt :addDsapSsap : 0x000c,0x0808

removeDsapSsap : N/Aagetime : 600delete : N/A

qoslevel : 1name : VLAN-1000

MERS-8606:5/config/vlan/10# removeDsapSsap 0x0808MERS-8606:5/config/vlan/10# infoSub-Context: create fdb-entry fdb-filter fdb-static ip ipx ports srcmacstatic-mcastmacCurrent Context:action : N/A

add-mlt :addDsapSsap : 0x000c

removeDsapSsap : N/Aagetime : 600delete : N/A

qoslevel : 1name : VLAN-1000

Configuring VLAN parameters in the forwarding databaseThis section includes the following topics:

• “Configuring or modifying VLAN entries in the forwarding database”(page 245)

• “Configuring VLAN filter members” (page 246)

• “Setting or modifying parameters of VLAN not allowed filter member”(page 248)

• “Configuring VLAN static member parameters” (page 249)

Configuring or modifying VLAN entries in the forwardingdatabaseTo configure or modify VLAN entries in the forwarding database, enter thefollowing command:

config vlan <vid> fdb-entry



NN46220-511 04.01 26 June 2009


.


config vlan <vid> fdb-entry

followed by:

info Shows current level parameter settings and next leveldirectories.

aging-time <seconds> Sets the forwarding database aging timer.

• <seconds> indicates the timeout period in seconds.

flush Flushes forwarding database.

monitor <mac> status<value> <true|false>

Sets forwarding database monitor parameters.

• <mac> indicates the MAC address.

• status <value> allows you to view the current statusof the forwarding database according to one of thefollowing choices: {other|invalid|learned|self|mgmt}.

• <true|false> enables or disables the monitor.

qos-level <mac> status<value> <0..7>

Sets a QoS level for a VLAN.


• status <value> is the forwarding databasestatus according to one of the following choices:{other|invalid|learned|self|mgmt}.

• <0..7> sets the QoS level.


sync Synchronizes the switch forwarding database with theforwarding database of the other aggregation switch.

Configuring VLAN filter membersTo configure VLAN filter members, enter the following command:

config vlan <vid> fdb-filter

The config vlan <vid> fdb-filter command includes the following options:


followed by:



NN46220-511 04.01 26 June 2009


.



followed by:

add <mac> port <value> [qos<value> ]

Adds a filter member to a VLAN bridge.


• port <value> indicates the port (slot/port) number.

• qos <value> is the QoS level.


pcap <mac> <enable|disable> Enables or disables the Packet Capture Tool (PCAP).


For more information about PCAP, see Using the PacketCapture Tool.

remove <mac> Removes a filter member from a VLAN bridge.



The following configuration example uses the config vlan fdb-filtercommands to:

• Add a filter member to the VLAN bridge

• Remove a filter member from a VLAN bridge


MERS-8606:5/config/vlan/10/fdb-filter# add 2:2:2:2:2:2 port 1/1MERS-8606:5/config/vlan/10/fdb-filter# infoSub-Context: notallowfromCurrent Context:

add :mac - 02:02:02:02:02:02port - 1/1Pcap - Disableremove : N/A

MERS-8606:5/config/vlan/10/fdb-filter# remove 2:2:2:2:2:2MERS-8606:5/config/vlan/10/fdb-filter# infoSub-Context: notallowfromCurrent Context:

add :remove : N/A


NN46220-511 04.01 26 June 2009


.


Setting or modifying parameters of VLAN not allowed filtermemberTo set or modify VLAN not allowed filter member parameters, enter thefollowing command:

config vlan <vid> fdb-filter notallowfrom


config vlan <vid> fdb-filter notallowfrom

followed by:


add <mac> port <value>[<srcOnly|dstOnly|Both>]

Adds a not allowed filter member to a VLAN bridge.


• <value> indicates the port (slot/port) number.

• <srcOnly}dstOnly|Both> is optional to set amask.

remove <mac> port <value>[<srcOnly|dstOnly|Both>]

Removes a not allowed filter member from a VLAN bridge.


• <value> indicates the port (slot/port) number.

• <srcOnly}dstOnly|Both> is optional to set amask.


The following configuration example uses the config vlan fdb-filternotallowfrom commands to:

• Add a not allowed filter member to a VLAN bridge

• Remove a not allowed filter member to a VLAN bridge



NN46220-511 04.01 26 June 2009


.


MERS-8606:5/config/vlan/10/fdb-filter# notallowfromMERS-8606:5/config/vlan/10/fdb-filter/notallowfrom# add 2:2:2:2:2:2 port1/2 BothMERS-8606:5/config/vlan/1000/fdb-filter/notallowfrom# infoSub-Context:Current Context:

add :mac - 02:02:02:02:02:02Dest Discard set - 1/2Src Discard set - 1/2remove : N/A

MERS-8606:5/config/vlan/10/fdb-filter/notallowfrom# remove 2:2:2:2:2:2port 1/2 srcOnlyMERS-8606:5/config/vlan/10/fdb-filter/notallowfrom# infoSub-Context:Current Context:

add :mac - 02:02:02:02:02:02Dest Discard set - 1/2Src Discard set -remove : N/A

Configuring VLAN static member parametersTo configure VLAN static member parameters, enter the followingcommand:

config vlan <vid> fdb-static


config vlan <vid> fdb-static

followed by:


add <mac> port <value> [qos<value> ]

Adds a static member to a VLAN bridge.


• port <value> indicates the port (slot/port) number.

• qos <value> is the QoS level.


remove <mac> Removes a static member from a VLAN bridge.



NN46220-511 04.01 26 June 2009


.


Limiting MAC learningThis feature allows you to limit the number of forwarding database entrieslearned on a particular port to a user-specified value. After the number oflearned forwarding database entries reaches the maximum limit, packetswith unknown source MAC addresses are dropped by the hardware. Ifthe count drops below a configured minimum value due to forwardingdatabase aging, learning is reenabled on the port. Users can configurevarious actions—logging, sending traps, and disabling the port—when thenumber of forwarding database entries reaches the configured maximumlimit.

The following CLI commands are implemented for this feature:

config ethernet <ports> limit-fdb-learning fdbprotect<enable|disable>

This command enables or disables the feature on the specified ports. Thedefault value is disable.

config ethernet <ports> limit-fdb-learning max-mac-count<value>

This command sets the maximum limit of forwarding database entries(fdb-entries) that can be learned on the specified ports. The default valueis 1024.

config ethernet <ports> limit-fdb-learning min-mac-count<value>

This command sets the minimum limit of fdb-entries at which fdb-learningwill be reenabled on the specified ports. The default value is 512.

config ethernet <ports> limit-fdb-learning info

This command shows the configuration information related to the feature.

config ethernet <ports> limit-fdb-learning violation-log-trap <enable|disable>

This command enables or disables logging to syslog file and trapgeneration when a maximum limit is reached. The default value is disable.

config ethernet <ports> limit-fdb-learning violation-down-port <enable|disable>

This command enables or disables the action taken on the ports in theevent of a violation. The default value is disable.


NN46220-511 04.01 26 June 2009


.


There is no Device Manager support for this feature in this release.

To change max-mac-count or min-mac-count when the feature is alreadyenabled, flush the fdb-entries on the particular port using the commandconfig ether <ports> action flushMacFdb.

Adding or removing VLAN portsTo add or remove ports in the VLAN, enter the following command:

config vlan <vid> ports


config vlan <vid> ports

followed by:

info Shows member status of the ports in the VLAN (Figure107 "Config vlan ports info command output" (page 252)).

add <ports> [member <value> ] Adds one or more ports to an existing VLAN.

• <ports> is the port list.

• member <value> is the port member type. It can beportmember (always a member), static (sometimesa member), or notallowed (never a member).

remove <ports> [member<value> ]

Removes ports from a VLAN but does not delete theVLAN.


• member <value> is the port member type. It can beportmember (always a member), static (sometimesa member), or notallowed (never a member).

ospf-passive <true|false><ports>

Enables or disables the OSPF passive port.

• <true|false> enables or disables the OSPF port.


Figure 107 "Config vlan ports info command output" (page 252) showssample output for the config vlan ports info command.


NN46220-511 04.01 26 June 2009


.


Figure 107Config vlan ports info command output

Adding or removing VLAN source MAC addressesTo add or remove VLAN source MAC addresses, enter the followingcommand:

config vlan <vid> srcmac


config vlan <vid> srcmac

followed by:


add <macaddr> Adds a source MAC address to a VLAN.

• <macaddr> is the MAC address to be added.

remove <macaddr> Removes a source MAC address from a VLAN.

• <macaddr> is the MAC address to be removed.

Configuring Untagging Default VLAN on a Tagged PortThe Untagging Default VLAN on a Tagged Port feature separatesuntagged packets originating from a PC from the tagged packetsoriginating from a IP phone.

The following command enables the Untagging Default VLAN on a TaggedPort feature:


NN46220-511 04.01 26 June 2009


.


config ethernet <ports> untag-port-default-vlan<enable|disable>

where

<ports> is the port of list of ports in slot/portformat.

Configuring Enhanced Operation modeEnhanced Operation mode enables the Metro Ethernet Routing Switch8600 to support more VLANs. With MLT, you can create a maximum of 1980 VLANs (1 972 with R modules in the chassis). With SMLT, the limit is989 VLANs. For more information about enhanced operation concepts,see “MultiLink trunking and VLAN scalability” (page 96).

To configure enhanced operation for 1 980 VLANs on the Metro EthernetRouting Switch 8600, use the following command:


You must save the configuration and reset the switch before the changetakes effect.

The config sys set flag enhanced-operational-mode commandincludes the following options:


followed by:

true Enables Enhanced Operation mode to support 1 980 VLANs for the system.

false Disables Enhanced Operation mode for the system.

Configuration example: configuring support for 1980 VLANs

This configuration example uses the preceding commands to configuresupport for up to 1980 VLANs. Figure 108 "Configuration example forsupporting 1980 VLANs command output" (page 254) shows sampleoutput for these configuration commands.


NN46220-511 04.01 26 June 2009


.


Figure 108Configuration example for supporting 1980 VLANs command output

Configuring VLAN Loop DetectionOn a per-port basis, the Loop Detection feature detects MAC addressesthat are looping from one port to other ports. After a loop is detected, theport on which the MAC addresses were learned is disabled. Additionally,if a MAC address is found to loop, the MAC address is disabled for thatVLAN.

The Loop Detection feature must only be enabled on SMLT ports, andnever used on IST ports or core SMLT square or full mesh ports.

You can also use Simple Loop Prevention Protocol to detect VLAN loops(see “Simple Loop Prevention Protocol” (page 90)).

For information about the Loop Detection feature, see “VLAN LoopDetection” (page 36). See “SMLT triangle with loop detection configurationexample” (page 379) for a CLI loop detection configuration example.

To enable or disable loop detection, enter the CLI command:

config ethernet <port> loop-detect <enable|disable>

The config ethernet <port> loop-detect command includes the followingoptions:


NN46220-511 04.01 26 June 2009


.


config ethernet <port> loop-detect <enable|disable>

followed by:

action<port-down|vlan-block|mac-discard>

Specifies the loop detect action to be taken.

• port-down shuts down the port upon detecting aflapping MAC address (an address that is enabled anddisabled repeatedly).

• vlan-block shuts down the VLAN upon detecting aflapping MAC address

• mac-discard

arp-detect <enable|disable> The ARP-Detect feature is used for IP configuredinterfaces for ARP packets. This feature should beenabled (in addition to loop detection) on routedinterfaces.

The MAC flap time limit is configured by using the mac-flap-time-limit command. Note that this interval should be staggered between apair of SMLT switches. By default, the mac-flap-time-limit is set to 500milliseconds.

config mac-flap-time-limit <10..5000 milliseconds>

To view the current flap time settings, enter the following command:

config info

To view link-flap-detection information, enter the following command:

show sys link-flap-detect general-info

Figure 109 "Config and show sys link-flap-detect command output" (page256) shows sample output for these commands.


NN46220-511 04.01 26 June 2009


.


Figure 109Config and show sys link-flap-detect command output

To display the results of loop detection in any VLAN, enter the CLIcommand:

show ports info loop-detected port <port number>

To verify whether the loop detection feature is enabled or disabled on theport, enter the CLI command:

config ethernet <port number> info

The CLI command to enable or disable auto-recovery on individual portsis as follows:

config ether <ports> auto-recover-port <enable|disable>

The default value is disable.

The CLI command to set the recovery timer on a port is as follows:

config auto-recover-delay <seconds>

The range is 5 to 3600 seconds, and the default value is 30 seconds.

To clear loop detection alarms, enter the CLI command:

config ethernet <port number> action clearLoopDetectAlarm

Figure 110 "Sample configuration using the loop-detect commands." (page257) shows sample CLI output using the loop detect commands.


NN46220-511 04.01 26 June 2009


.


Figure 110Sample configuration using the loop-detect commands.

Loop detection warning messages

The following log message and trap is generated when MAC addressdiscarding is set due to loop-detect:


NN46220-511 04.01 26 June 2009


.


MAC has been disabled due to MAC <xx:xx:xx:xx:xx:xx>flapping more than <n> times in <t> milliseconds from<port-number> to <port-number>.

The following log message and trap is generated when a port, which hasbeen disabled due to CP-Limit or link-flap, is auto-recovered:

port <port-num> re-enabled by auto recovery

The following log message and trap is generated when a port which hasbeen disabled due to the loop detection feature is auto-recovered:

Loop detect action <action> cleared on port <port-num> byauto recovery

Configuring spoof detection for a VLANA port can be configured to prevent IP spoofing by using the following CLIcommands. For more information about this feature, see “Prevention of IPspoofing within a VLAN” (page 35).

To enable or disable spoof detection, enter the following command:

config ethernet <ports> spoof-detect <enable|disable>

To enable or disable auto-recovery on a port use the command:

config ethernet <ports> auto-recover-port <enable|disable>

If you are using SMLT, be sure to configure spoof detection on both SMLTaggregation switches to avoid connectivity issues.

ATTENTIONEnabling the spoof detection feature requires you to reboot the switch.

Using the VLAN show commandsTo obtain configuration information about all VLANs on the switch orspecified VLANs, use the show vlan commands.


• “Displaying general VLAN information” (page 259)

• “Displaying forwarding database information” (page 270)

• “Displaying forwarding database filters” (page 271)

• “Displaying database status, MAC address, and QoS levels” (page272)

• “Displaying additional parameters” (page 273)

• “Displaying ARP configurations” (page 274)


NN46220-511 04.01 26 June 2009


.

Using the VLAN show commands 259

• “Displaying VLAN information” (page 275)

• “Displaying brouter port information” (page 276)

• “Displaying IGMP switch operation information” (page 277)

• “Displaying VLAN routing (IP) configuration” (page 278)

• “Displaying port member status” (page 278)

• “Displaying source MAC addresses” (page 280)

Displaying general VLAN informationTo display all general information about the VLANs on the switch or aspecified VLAN, enter the following command:

show vlan info all [ <vid> ] [port <value> ] [by <value> ]

where

<vid> is the VLAN ID from 1 to 4092,port <value> is the port or range of ports,by <value> is the group ID.

Figure 111 "Show vlan info all command output" (page 260) shows sampleoutput of this command.


NN46220-511 04.01 26 June 2009


.


Figure 111Show vlan info all command output

The following table shows the field descriptions for this command.

Table 52Show vlan info all field descriptions

Field Description

Vlan Basic

VLAN ID Indicates the VLAN ID.

NAME Indicates the administrator assigned name to the VLAN.


NN46220-511 04.01 26 June 2009


.


Table 52Show vlan info all field descriptions (cont’d.)

Field Description

TYPE Indicates the type of VLAN, distinguished according to the policyused to define its port membership. Options include:

byPort—VLAN by Port

byIpSubnet—VLAN by IP subnet

byProtocolId—VLAN by protocol ID

bySrcMac—VLAN by source MAC address

byDstMcast—VLAN by destination multicast

byIds—VLAN by IDS VLAN

STG ID Indicates the Spanning Tree Group (STG) used by this VLAN todetermine the state of its ports. If this VLAN is not associated withany STG, it is zero.

PROTOCOLID Indicates the protocol identifier of this VLAN. For other VLAN types ithas the value of none. Options include:

none

ip

appleTalk

decLat

decOther

sna802dot2

snaEthernet2

netBios

xns

vines

ipV6

usrDefined


NN46220-511 04.01 26 June 2009


.



Field Description

rarp

pPPoE

SUBNETADDR Indicates the IP subnet address of this VLAN. For other VLAN typesit has the value of 0.0.0.0.

SUBNETMASK Indicates the IP subnet mask of this VLAN. For other VLAN types ithas the value of 0.0.0.0.

Vlan Port


PORT MEMBER Indicates the set of ports that are members (static or dynamic) ofthis VLAN.

ACTIVE MEMBER Indicates the set of ports that are currently active in this VLAN.Active ports include all static ports and any dynamic ports where theVLAN policy was met.

STATIC MEMBER Indicates the set of ports that are static members of this VLAN. Astatic member of a VLAN is always active and is never aged out.

NOT_ALLOW MEMBER Indicates the set of ports that are not allowed to become membersof this VLAN.

Vlan ATM Port


PORT NUM Indicates the port number.

PVC LIST Indicates the PVC list.

Ospf Passive Port Members

VLAN Indicates the VLAN ID.

PORT NUM Indicates the VLAN port number for the passive OSPF interface.

Vlan Advance


NAME Indicates the name assigned to the VLAN.

IF INDEX Indicates the interface index.

QOS LVL Indicates the QoS level packets carried in this VLAN for processing.

AGING TIME Indicates the timeout period (in seconds) used for aging out dynamicmembers of this VLAN. This field is only relevant for policy-basedVLANs.


NN46220-511 04.01 26 June 2009


.



Field Description

MAC ADDRESS Indicates the MAC address assigned to the virtual router interfaceof this VLAN. This field is meaningful only if VlanRoutingEnable isequal to true.

ACTION Inidciates VLAN related actions. Options include:

none—none of the following

flushMacFdb—flush MAC forwarding table

flushArp—flush ARP table

flushIp—flush IP route table

flushDynMemb—flush dynamic members

all—flush all tables

flushSnoopMemb—flush IGMP snoop members

triggerRipUpdate—manually trigger RIP update

flushSnoopMRtr—flush snoop multicast router

RESULT Indicates the result from the last VLAN action. Options include:

none

inProgress

success

fail

Vlan Arp


DOPROXY Indicates if ARP proxy responses are enabled or disabled on thespecified interface.

DORESP Indicates if the sending of ARP responses is enabled or disabledon the specified interface.

Vlan Fdb


STATUS Indicates the status of FDB forwarding on the VLAN.


NN46220-511 04.01 26 June 2009


.



Field Description


INTERFACE Indicates the interface.

MONITOR Indicates whether monitoring is performed on this unicast MACaddress. If monitoring is enabled, any packet received witha matching destination MAC address is forwarded to the portconfigured to receive monitor traffic.


SMLT REMOTE Indicates the MAC address for remote learnt, either local or remote.

Vlan Filter


STATUS Indicates the status of the VLAN filter.


PORT Indicates the port number.


PCAP Indicates the status of PCAP on the filter.

DEST_DISCARD SET Indicates a set of ports. Traffic arriving on any of the specified portsfrom this MAC address.

SRC_DISCARD SET Indicates a set of ports. Traffic arriving on any of the specified portsis not forwarded to this MAC address.

Vlan Static


STATUS Indicates the status of the static VLAN.


PORT Indicates the port number.

MONITOR Indicates whether monitoring is performed on this unicast MACaddress. If monitoring is enabled, any packet received witha matching destination MAC address is forwarded to the portconfigured to receive monitor traffic.


IDS Vlan Info



NN46220-511 04.01 26 June 2009


.



Field Description

MAC LEARNING Indicates the type of MAC learning.

DISABLED PORTS Indicates the disabled port numbers.

Vlan Ip


IP ADDRESS Indicates the IP subnet address of this VLAN. This value ismeaningful only if the VLAN type is set to IP subnet. For other VLANtypes, it has the value of 0.0.0.0.

NET MASK Indicates the IP subnet mask of this VLAN. This value is meaningfulonly if the VLAN type is set to IP subnet. For other VLAN types ithas the value of 0.0.0.0.

BCASTADDR FORMAT Indicates the IP broadcast address format used on this interface.

REASM MAXSIZE Indicates the size of the largest IP datagram that this entity canreassemble from incoming IP fragmented datagrams received onthis interface.

ADVERTISE WHEN_DOWN

Indicates whether the VLAN state change is notified to Layer 3or not, provided the VLAN is configured as a routable interface.A VLAN is considered to be up if at least one member of theport-based VLAN has link up, or at least one port member ofthe policy-based has an entry in the MGID or at least one staticmember of the policy-based VLAN has link up. Otherwise, a VLANis considered to be down. If the value is true then the interface statechange does not notify to Layer 3. (that is, it always stays up). If thevalue is false then the VLAN state change is notified to Layer 3 sothat IP related status reflects the routable interface state.

DIRECTED BROADCAST Indicates the status of directed broadcast.

RPC Indicates the status of RPC.

RPC MODE Indicates the RPC mode type.

Vlan Dhcp

VLAN ID Indicates the VLAN ID number

IF INDEX Indicates the interface index number. Numbers 1 to 256 are ports;numbers above 257 are VLANs.

ENABLE Indicates if DHCP is enabled on the port.

MAX HOP Indicates the maximum number of hops a DHCP packet can takefrom the source device to the destination device (that is, DHCPclient to DHCP server)

MIN SEC Indicates the minimum number of seconds to wait between receivinga DHCP packet and actually forwarding the DHCP packet to thedestination device. A value of zero indicates forwarding should bedone immediately without any delay.


NN46220-511 04.01 26 June 2009


.



Field Description

MODE Indicates what type of DHCP packets this interface should support.A value of none results in all incoming DHCP and BOOTP packetsto be dropped. Options include none, bootp, dhcp, and both.

ALWAYS BCAST Indicates if DHCP reply packets are broadcast to the DHCP clienton this interface.

Vlan Ospf

VLAN ID Indicates the VLAN

ENABLE Indicates the status of OSPF configured on the port.

HELLO INTERVAL Indicates the length of time, in seconds (1 to FFFF) between theHello packets that the router sends on the interface.

RTRDEAD INTERVAL Indicates the number of seconds (1 to FFFF) that router Hellopackets have not been seen before neighbors declare the routerdown.

DESIGRTR PRIORITY Indicates the priority of this interface. Used in multiaccess networks.This field is used in the designated router election algorithm. Thevalue 0 indicates the router is not eligible to become the designatedrouter on this particular network. In the event of a tie in this value,routers use their router id as a tie breaker. The default is 1.

METRIC Indicates the metric for this type of service (TOS) on this interface.The value of the TOS metric is (10^9 / interface speed). The defaultis 1.

FFFF—There is no route for this TOS.

POS/IPCP links—defaults to 0.

0—The interface speed is used as the metric value when the stateof the interface is up.

AUTHTYPE Indicates the type of authentication required for the interface.

none—No authentication required.

simple password—All OSPF updates received by the interface mustcontain the authentication key specified in the interface AuthKeyfield.

MD5 authentication—All OSPF updates received by the interfacemust contain the MD5 key.

AUTHKEY Indicates the key (up to 8 characters) required when simplepassword authentication is specified in the interface AuthType field.


NN46220-511 04.01 26 June 2009


.



Field Description

INTF Indicates the interface type.

AREA ID Indicates the area where the host is found. By default, the area thatis submitting the OSPF interface is in 0.0.0.0.

Vlan Rip

PORT NUM Indicates the ports on the VLAN.

ENABLE Indicates the status of RIP on the port.s for a VLAN

DEFAULT SUPPLY Indicates if the default route must be advertised out this interface.

The default route is advertised only if it exists in the routing table.

DEFAULT LISTEN Indicates if the default route must be learned on this interface whenadvertised by another router connected to the interface.

TRIGGERED UPDATE Indicates the status of the RIP triggered update on the interface.

AUTOAGG ENABLE Indicates the status of auto aggregation on the interface.

SUPPLY Indicates the status of advertising RIP routes through the interface.

LISTEN Indicates the status of RIP reception on the interface.

POISON Indicates the status of poison reverse on the interface. If disabled,split horizon is invoked, meaning that IP routes learned from animmediate neighbor are not advertised back to the neighbor fromwhich the routes were learned.

If enabled, the RIP update sent to a neighbor from which a route islearned is poisoned with a metric of 16. In this manner, the routeentry is not passed along to the neighbor, because historically 16 isinfinity in terms of hops on a network. The default is disable.

Vlan Ip Igmp


QUERY INTVL Indicates the interval (in seconds) between IGMP Host-Querypackets transmitted on this interface.

QUERY MAX RESP Indicates the interval (in seconds) for the maximum query responsetime advertised in IGMPv2 queries on this interface. Smaller valuesallow a router to prune groups faster.

ROBUST Indicates the tuning for the expected packet loss on a subnet. If asubnet is expected to be lossy, the Robustness variable can beincreased. IGMP is robust to (Robustness - 1) packet losses.

VERSION Indicates the version of IGMP that is running on this interface. Thisobject configures a router capable of running either value. For IGMPto function correctly, all routers on a LAN must be configured to runthe same version of IGMP on that LAN.


NN46220-511 04.01 26 June 2009


.



Field Description

LAST MEMB QUERY Indicates the max response in a group specific query.

PROXY SNOOP ENABLE Indicates the status of IGMP proxy snoop on the VLAN.

SNOOP ENABLE Indicates the status of IGMP snooping on the VLAN.

SSM SNOOP ENABLE Indicates the status of SSM IGMP snooping on the VLAN.

FAST LEAVE ENABLE Indicates the status of fast leave.

FAST LEAVE PORTS Indicates the ports that have fast leave enabled.

Vlan Ip Dvmrp

IF Indicates the ifIndex value of the interface for which DVMRP isenabled.

ADDR Indicates the IP address this system uses as a source address onthis interface.

METRIC Indicates the distance metric for this interface used to calculatedistance vectors.

OPERSTAT Indicates the current operational state of this DVMRP interface.

DEFAULT LISTEN Indicates whether the switch can learn DVMRP default routes overthis interface.

DEFAULT SUPPLY Indicates the whether the switch should supply DVMRP defaultroutes over this interface.

DEFAULT METRIC Indicates the cost of the DVMRP default route that this interfacegenerates and supplies when it is configured to supply default route.

ADVERTISE SELF Indicates whether the switch can advertise this local network.

IN-POLICY Indicates the DVMRP accept policy name configured on thisinterface.

OUT-POLICY Indicates the DVMRP announce policy name configured on thisinterface.

INTF TYPE Indicates the type of this DVMRP interface, whether it uses a tunnel,source routing, a physical interface for which there is a a querier, ora physical interface for which there is not a querier (subnet).

Vlan Ip Icmp Route Discovery


ADV_ADDRESS Indicates the advertisement address to which the route discoveryadvertisements transmitted on this interface.

ADV_FLAG Indicates the flag to indicate whether or not the address is to beadvertised on this interface.

LIFETIME Indicates the value to be placed in the lifetime field of routerAdvertisements sent from the interface.


NN46220-511 04.01 26 June 2009


.



Field Description

MAX_INT Indicates the maximum time allowed between sending routerAdvertisements from this interface.

MIN_INT Indicates the minimum time allowed between sending routerAdvertisements from this interface.

PREF_LEVEL Indicates the preferability of the router address as a default router

Manual Edit Mac

MAC ADDRESS Indicates the MAC address that is learned on the port.

PORTS Indicates the allowed ports that can learn this MAC address.

Autolearn Mac

MAC ADDRESS Indicates the MAC address that is automatically learned on the port.

PORT Indicates the allowed ports that can automatically learn this MACaddress.

Vlan Ip Pim

VLAN-ID Identifies the VLAN.

PIM-ENABLE The state of PIM on the VLAN.

MODE The configured mode of this VLAN. The valid modes are SSM andSparse.

HELLOINT Indicates how long to wait (in seconds) before the PIM switch sendsout the next hello message to neighboring switches. The defaulthello interval is 30 seconds.

JPINT Indicates how long to wait (in seconds) before the PIM switch sendsout the next join/prune message to its upstream neighbors. Thedefault join/prune interval is 60 seconds.

CBSR PREF The preference for this local interface to become a candidate BSR.The Candidate BSR with the highest BSR-priority and address isreferred to as the preferred BSR. The default is -1, which indicatesthat the current interface is not a candidate BSR.

INTF TYPE Indicates whether the PIM interface is active or passive.

Vlan Ip Pgm

VLAN-ID Identifies the VLAN.

ENABLE Shows whether PGM is enabled or disabled on this interface.

STATE Indicates the current state (up or down) of PGM.

NAK_RE_XMIT INTERVAL Specifies how long to wait for an NCF (in milliseconds) beforeretransmitting the NAK (negative acknowledgement). The default is1 000 milliseconds.

MAX_NAK_REXMIT_COUNT

Specifies the maximum number of NAK retransmission packetsallowed per second.


NN46220-511 04.01 26 June 2009


.



Field Description

NAK_RDATA INTERVAL Specifies how long to wait for RDATA (in milliseconds) afterreceiving an NCF.

NAK_ELIMINATEINTERVAL

Specifies the length of time (in milliseconds) during where a networkelement (NE) eliminates duplicate NAKs. When this interval expires,the NE suspends NAK elimination until the first duplicate arrives.After this NAK is forwarded, the NE again eliminates duplicate NAKsfor the specified interval. This parameter must be less than theNAK_RDATA INTERVAL.

Vlan Mcastmac


MAC ADDRESS Indicates the MAC address.

PORT LIST Indicates the list of ports.

MLT GROUPS Indicates the MLT groups.

Vlan Firewall

ID Indicates the VLAN ID.

NAME Indicates the VLAN name assigned by the user.

FIREWALL TYPE Indicates the firewall VLAN type for port-based VLANs. Optionsinclude:

none

naap

enforceable

peering

CLUSTER ID Indicates the firewall cluster ID.

Displaying forwarding database informationTo display forwarding database information for the specified VLAN, enterthe following command:

show vlan info fdb-entry [ <vid> ] [mac <value> ] [port<value> ]

where

<vid> is the VLAN ID from 1 to 4 092.port <port-list> is the port or range of ports in

slot/port format.


NN46220-511 04.01 26 June 2009


.


mac <value> is the MAC address.

The <vid>, port, and mac are optional parameters.

Figure 112 "Show vlan info fdb-entry command output" (page 271) showssample output for the show vlan info fdb-entry command.

Figure 112Show vlan info fdb-entry command output

See the appropriate section in Table 52 "Show vlan info all fielddescriptions" (page 260) for an explanation of each heading in theprevious figure.

Displaying forwarding database filtersTo display the forwarding database filters for the specified VLAN, enter thefollowing command:

show vlan info fdb-filter [ <vid> ] [mac <value> ] [port<value> ]

where


slot/port format.mac <value> is the MAC address.

The <vid>, port, and mac are optional parameters.

The display includes the VLAN ID, the status, the VLAN MAC address,and the ports from which the VLAN is not allowed to receive frames.

Figure 113 "Show vlan info fdb-filter command output" (page 272) showssample output for the show vlan info fdb-filter command.


NN46220-511 04.01 26 June 2009


.


Figure 113Show vlan info fdb-filter command output


Displaying database status, MAC address, and QoS levelsTo display the static forwarding database status, the VLAN MAC address,and the QoS level for the specified VLAN, enter the following command:

show vlan info fdb-static [ <vid> ] [mac <value> ] [port<value> ]

where


slot/port format.mac <value> is the MAC address.

The <vid>, port, and macare optional parameters.

Figure 114 "Show vlan info fdb-static command output" (page 273) showssample output for the show vlan info fdb-static command.


NN46220-511 04.01 26 June 2009


.


Figure 114Show vlan info fdb-static command output


Displaying additional parametersTo display additional parameters for the specified VLAN or all VLANs,enter the following command:

show vlan info advance [ <vid> ] [port <value> ]

where

vid is the VLAN ID from 1 to 4 092,port <value> is the port or range of ports.

Entering a vid or port <value> is optional. When you enter a vidor port <value>, the command shows information for the specifiedVLAN or port. Without the vid or port <value>, the command showsinformation for all the configured VLANs.

All zeros in the MAC ADDRESS column indicate that there is no IPaddress associated with that VLAN.

Figure 115 "Show vlan info advance command output" (page 274) showssample output for the show vlan info advance command.


NN46220-511 04.01 26 June 2009


.


Figure 115Show vlan info advance command output


Displaying ARP configurationsTo display the Address Resolution Protocol (ARP) configuration for allVLANs or the specified VLAN, enter the following command:

show vlan info arp [ <vid> ] [port <value> ]

where




NN46220-511 04.01 26 June 2009


.


Figure 116 "Show vlan info arp command output" (page 275) showssample output for the show vlan info arp command.

Figure 116Show vlan info arp command output


Displaying VLAN informationTo display the basic configuration for all VLANs or a specified VLAN, enterthe following command:

show vlan info basic [ <vid> ] [port <value> ]

where



Figure 117 "Show vlan info basic command output" (page 276) showssample output for the show vlan info basic command.


NN46220-511 04.01 26 June 2009


.


Figure 117Show vlan info basic command output


Displaying brouter port informationTo display the brouter port VLAN information for all VLANs on the switchor for the specified VLAN, enter the following command:

show vlan info brouter-port [port <value> ]

where

port <value> is the portlist {slot/port[-slot/port][,...]}. Entering a value is optional.When you enter a value, the command showsinformation for the specified port. Withoutthe value, the command shows information forall the configured VLANs.

This command is available only for the Metro Ethernet Routing Switch8600.

Figure 118 "Show vlan info brouter-port command output" (page277) shows sample output for the show vlan info brouter-portcommand.


NN46220-511 04.01 26 June 2009


.


Figure 118Show vlan info brouter-port command output

Displaying IGMP switch operation informationTo display information about IGMP operation in the switch, enter thefollowing command:

show vlan info igmp [ <vid> ] [port <value> ]

where



Figure 119 "Show vlan info igmp command output" (page 277) showssample output for the show vlan info igmp command.

Figure 119Show vlan info igmp command output


NN46220-511 04.01 26 June 2009


.



Displaying VLAN routing (IP) configurationTo display the routing (IP) configuration for all VLANs on the switch or forthe specified VLAN, enter the following command:

show vlan info ip [ <vid> ] [port <value> ]

where



Figure 120 "Show vlan info ip command output" (page 278) shows sampleoutput for the show vlan info ip command.

Figure 120Show vlan info ip command output


Displaying port member statusTo display the port member status for all VLANs on the switch or for thespecified VLAN, enter the following command:

show vlan info ports [ <vid> ] [port <value> ]


NN46220-511 04.01 26 June 2009


.


where



A port can be an active member, a static member, or a not-allowedmember.

Figure 121 "Show vlan info ports command output" (page 279) showssample output for the show vlan info ports command.

Figure 121Show vlan info ports command output



NN46220-511 04.01 26 June 2009


.


Displaying source MAC addressesTo display the source MAC address for any source MAC-based VLANs onthe switch, or for the specified VLAN, if it is source MAC-based, enter thefollowing command:

show vlan info srcmac [ <vid> ] [port <value> ]

where



Figure 122 "Show vlan info srcmac command output" (page 280) showssample output for the show vlan info srcmac command.

Figure 122Show vlan info srcmac command output


Using the show ports commands for VLANsTo obtain configuration port information about all VLANs on the switch orspecified VLANs, use the show ports commands.


• “Displaying port tagging information” (page 281)

• “Displaying all port VLAN information” (page 282)


NN46220-511 04.01 26 June 2009


.

Using the show ports commands for VLANs 281

Displaying port tagging informationTo display VLAN port tagging information, enter the following command:

show ports info vlans [vlan <value> ] [port <value> ]

where

vlan <value> is the VLAN ID from 1 to 4092,port <value> is the port or range of ports.

Entering a vlan <value> or port <value> is optional. When you entera vlan <value> or port <value>, the command shows information forthe specified VLAN or port. Without the vlan <value> or port <value>,the command shows information for all the configured VLANs.

Figure 123 "Show ports info vlan command output" (page 281) showssample output for this command.

Figure 123Show ports info vlan command output


Table 53Show ports info field descriptions

Field Description

PORT NUM Indicates the port and slot number.

TAGGING Indicates the state of ingress and egress tagging on the port.

DISCARD TAGFRAM Indicates the state of how to process tagged frames received on thisaccess port. When the flag is set, these frames are discarded bythe forwarding process. When the flag is reset, these frames areprocessed normally. This only applies when the port is a trunk port.


NN46220-511 04.01 26 June 2009


.


Table 53Show ports info field descriptions (cont’d.)

Field Description

DISCARD UNTAGFRAM Indicates the state of how to process untagged frames received onthis trunk port. When the flag is set, these frames are discarded bythe forwarding process. When the flag is reset, these frames areassigned to the default VLAN ID specified by Default VlanId. Thisonly applies when the port is a trunk port.

DEFAULT VLANID Indicates the VLAN ID assigned to untagged frames received on thistrunk port. This only applies when the port is a trunk port.

VLAN IDS Indicates the VLANs assigned to this port.

PORT TYPE Indicates the type of port: normal, UNI, or NNI.

UNTAG DEFVLAN Indicates the status of egress tagging on the default VLAN port.

Displaying all port VLAN informationTo display all port VLAN information, enter the following command:

show ports info all [vlan <value> ] [port <value> ] [by<value> ]

where

vlan <value> is the VLAN ID from 1 to 4092port <value> is the port or range of portsby <value> is the group ID.

Entering a vlan <value>, port <value> or by <value> is optional.When you enter a vlan <value> , port <value> or by <value>, thecommand shows information for the specified VLAN, port, or group ID.Without optional parameters, the command shows information for all theconfigured VLANs.

Figure 124 "Show ports info port all command output" (page 283) showssample output for this command.


NN46220-511 04.01 26 June 2009


.

Using the VLAN IP commands 283

Figure 124Show ports info port all command output

Table 52 "Show vlan info all field descriptions" (page 260) shows the fielddescriptions for this command.

Using the VLAN IP commandsThe VLAN IP commands described in this section are general routingcommands for the VLAN. Other VLAN commands are included in thesections of this manual that describe commands used with a specificprotocol or feature.


NN46220-511 04.01 26 June 2009


.


Assigning an IP address to a VLANTo assign an IP address to a VLAN, use the following command:

config vlan <vid> ip

where

vid is the VLAN ID from 1 to 4 092. Entering a vid isoptional. When you enter a vid, the commandshows information for the specified VLAN.Without the vid, the command shows informationfor all the configured VLANs.


config vlan <vid> ip

followed by:


create <ipaddr|mask>[mac_offset <value> ]

Assigns an IP address and subnet mask to the VLAN.

• <ipaddr|mask> is the IP address and mask {a.b.c.d}.

• mac_offset <value> is a user-assigned MACaddress. This MAC address is in place of the defaultMAC address.

delete <ipaddr> Deletes the specified VLAN address.

Rvs-Path-Chk <enable|disable> [mode <value> ]

Enables or disables reverse path checking.

• <enable|disable> enables or disables reverse pathchecking.

• mode <value> is the mode for reverse pathchecking—exist-only or strict.

See Configuring and Managing Security () for moreinformation about Reverse Path Checking.

Figure 125 "Config vlan ip info command output" (page 285) shows sampleoutput for the config vlan ip info command.


NN46220-511 04.01 26 June 2009


.

Using the VLAN IP commands 285

Figure 125Config vlan ip info command output


NN46220-511 04.01 26 June 2009


.



NN46220-511 04.01 26 June 2009


.

287.

Configuring STGs using the CLIYou can set up spanning tree groups (STG) by using the spanning treegroup commands. You can set parameters for a group and for ports in thatgroup. You can also enable or disable the Spanning Tree Protocol in anSTG.

The Metro Ethernet Routing Switch 8600 modules support up to 64 STGsin a switch.

This section includes information about configuring STG and itsparameters by using the appropriate commands and includes the followingtopics:

• “Roadmap of spanning tree commands” (page 287)

• “Configuring the spanning tree protocol mode” (page 290)

• “Configuring Spanning Tree Protocol” (page 290)


For conceptual information about spanning tree protocols, see “Spanningtree protocols” (page 37).

Roadmap of spanning tree commandsThe following roadmap lists all spanning tree commands and theirparameters. Use this list as a quick reference.

Command Parameter

config bootconfig flags spanning-tree-mode <mstp|default>

config mstp info

pathcost-type <16-bit|32-bit>

hop count <number>

tx-holdcount <number>


NN46220-511 04.01 26 June 2009


.

288 Configuring STGs using the CLI

Command Parameter

config mstp region info

name <string>

revision <number>

config-id-sel <number>

config mstp cist info

force-version <stp-compatible|mstp>

forward-delay <number>

max-age <number>

priority <number>

config mstp plsb-msti <instid>

config mstp msti <instid> info

priority

show mstp config

show mstp instance

show mstp stats

show mstp status

show ports info mstp cistinfo [vlan <value>] [port<value>]

mstiinfo [vlan <value>] [port<value>]

ciststat [vlan <value>] [port<value>]

mstistat [vlan <value>] [port<value>]

cistrole [vlan <value>] [port<value>]

mstirole [vlan <value>] [port<value>]

clear ports mstpstats [<ports>]

config eth <portlist> mstp cist info

edge-port <true|false>

forceportstate <enable|disable>

hello-time <value>

p2p <forcetrue|forcefalse| auto>


NN46220-511 04.01 26 June 2009


.

Roadmap of spanning tree commands 289

Command Parameter

protocol-migration <true|false>

priority <value>

pathcost <number>

config eth <portlist> mstp msti<instid>

info

priority <value>

pathcost <value>

forceport state <enable|disable>

config stg <sid> info

add ports <ports>

create [<ports>] [vlan <value>][mac <value>] [type <value>][ntstg <value>]

delete

forward-delay <timeval>

group-stp <enable|disable>

hello-interval <timeval>

max-age <timeval>

priority <number>

remove ports <value>

trap-stp <enable|disable>

config ethernet <ports> stg <sid> info

change-detection <enable|disable>

faststart <enable|disable>

pathcost <intval>

priority <intval>

stp <enable|disable>

faststart <enable|disable>

show stg show-all

show stg info config <sid>

show stg info status <sid>


NN46220-511 04.01 26 June 2009


.


Command Parameter

show ports info stg main [vlan<value>] [port <value>]

show ports info stg extended [vlan<value>] [port <value>]

show ports stats stg <ports>

Configuring the spanning tree protocol modeThere are two spanning tree protocol modes on the Metro EthernetRouting Switch 8600: Multiple Spanning Tree Protocol (MSTP) and Legacy(Spanning Tree Protocol). To set the spanning tree mode of the switch,use the following command:

config bootconfig flags spanning-tree-mode <mstp|default>

where

mstp|default are the Spanning Tree modes MSTP andLegacy. The default is Legacy.

To change the spanning tree mode, you must use the commands savebootconfig to save the boot configuration and boot to reboot theswitch. You must start a new session on the switch.

The config bootconfig flags spanning-tree-mode command is inthe CLI Global configuration mode.

Configuring Spanning Tree ProtocolThe operation of the Spanning Tree Protocol (STP) is defined in theIEEE 802.1d standard. The STP detects and eliminates logical loops ina bridged or switched network. When multiple paths exist, the spanningtree algorithm configures the network so that a bridge or switch usesonly the most efficient path. If that path fails, the protocol automaticallyreconfigures the network and makes another path active, which sustainsnetwork operations.

Spanning Tree Protocol is the default spanning tree protocol used by theMetro Ethernet Routing Switch 8600. This section includes the followingtopics:

• “Configuring spanning tree group parameters” (page 291)

• “Configuring STG port parameters” (page 293)

• “Configuring topology change detection” (page 295)

• “Using the show STG commands” (page 297)


NN46220-511 04.01 26 June 2009


.


Configuring spanning tree group parametersTo configure parameters for a specified spanning tree group, enter thefollowing command:

config stg <sid>

where

sid is the spanning tree group ID.


config stg <sid>

followed by:

info Shows characteristics of the spanning tree group.

add ports <ports> Adds port to a spanning tree group.

• <ports> specifies one or more slot/port numbers.

Ports can not be added to the STG if they are:

• configured as Single Port SMLT

• configured as members of another STG

create [ <ports> ] [vlan<value> ] [mac <value> ] [type<value> ] [ntstg <value> ]

Creates a new spanning tree group.

• <ports> specifies one or more slot/port numbers.

Ports cannot be added to the STG if configured as SinglePort SMLT, or as a member of another STG.

• vlan <value> is the VLAN ID. If a VLAN spansmultiple switches, it must be within the same STGacross all switches.

• mac <value> is the MAC address.

• type <value> is the type of STG. Choices arestgnormal, stgsvlan, or stgplsb.

• ntstg <value> enables or disables STP. Choicesare enable or disable.

delete Deletes the specified spanning tree group.

forward-delay <timeval> Sets the bridge forward delay time in hundredths of asecond. The default is 1500 (15 seconds).

group-stp <enable|disable> Enables or disables the Spanning Tree Protocol on thespecified spanning tree group.

hello-interval <timeval> Sets the bridge hello time in hundredths of a second. Thedefault is 200 (2 seconds).


NN46220-511 04.01 26 June 2009


.


config stg <sid>

followed by:

max-age <timeval> Sets the bridge maximum age time in hundredths of asecond. The default is 2000 (20 seconds).

priority <number> Sets the bridge priority number.

• <number> is between 0 and 65 35.

remove ports <value> Removes ports from a spanning tree group.

• <value> is the specified port.

trap-stp <enable|disable> Enables or disables the Spanning Tree Protocol trap forthe specified spanning tree group.

Disabling the Spanning Tree Protocol can reduce CPU overhead slightly.However, unless you are using the switch in a simple network with littlepossibility of looping, Nortel recommends that you leave the SpanningTree Protocol enabled.

Figure 126 "Config stg info command output" (page 292) shows sampleoutput for the config stg info command.

Figure 126Config stg info command output


NN46220-511 04.01 26 June 2009


.


Configuring STG port parametersPorts must have tagging enabled to belong to multiple spanning treegroups.

Nortel recommends that you enable FastStart as an alternative to disablingSpanning Tree Protocol on an individual port. The Spanning Tree Protocolis currently not supported on SMLT/IST ports, and must be disabled.

To configure spanning tree group port parameters, enter the followingcommand:

config ethernet <ports> stg <sid>

where

<ports> is the slot/port you want to add to the STG.<sid> is the spanning tree group ID.



followed by:

info Shows current settings for the port spanningtree group.

faststart <enable|disable> Enables or disables the FastStart feature. WhenFastStart is enabled, the port goes throughthe normal listening and learning states beforeforwarding, but the hold time for these statesis the bridge hello timer (2 seconds by default)instead of the bridge forward delay timer (15seconds by default).

change-detection <enable|disable> Enables or disables topology change detectionfor the specified spanning tree. The default isenable.

pathcost <intval> Sets the contribution of this port to the pathcost.

• <intval> is the cost (1 to 65 35).


NN46220-511 04.01 26 June 2009


.



followed by:

priority <intval> Sets the priority of this port.

• <intval> is the priority (0 to 255).

Although port priority values can range from 0to 255, only the following values are used: 0,16, 32, 48, 64, 80, 96, 112, 128, 144, 160, 176,192, 208, 224, 240

stp <enable|disable> Enables or disables the Spanning TreeProtocol.

Spanning Tree Protocol must be disabled onSMLT or IST ports.

To display the current settings for the spanning tree group, use thefollowing command:


where


Figure 127 "Config ethernet slot/port stg sid info command output" (page294) shows sample output for this command.

Figure 127Config ethernet slot/port stg sid info command output


NN46220-511 04.01 26 June 2009


.


Configuring topology change detectionChange detection is enabled by default. With change detection enabled,when a topology change occurs, a trap is sent containing the MACaddress of the STG sending the topology change notification (TCN), theport number, and the STG ID. You can use this information to identify thedevice. For more information about change detection, see “Spanning TreeProtocol topology change detection” (page 40).

To configure topology change detection, use the following command:

config ethernet <ports> stg <sid> change-detection<enable|disable>

where


If you enable change detection on an MLT with access ports, the settingis automatically applied to all ports in the MLT.

Querying the change detection settingTo query the change detection setting, use the following command:


where


Figure 127 "Config ethernet slot/port stg sid info command output" (page294) shows sample output for this command.

The show ports info stg main command (Figure 128 "Show ports infostg main command output" (page 296)) also shows the change detectionsetting.


NN46220-511 04.01 26 June 2009


.


Figure 128Show ports info stg main command output


Table 54Show ports info stg field descriptions

Field Description

SID Indicates the STG identifier this port is assigned to.

PORT_NUM Indicates the port number and slot.

PRIO Indicates the value of the priority field that is contained in thefirst (in network byte order) octet of the (two octet long) port ID.


NN46220-511 04.01 26 June 2009


.


Table 54Show ports info stg field descriptions (cont’d.)

Field Description

STATE Indicates the port current state as defined by the application ofthe Spanning Tree Protocol. This state controls what action aport takes on reception of a frame. If the bridge has detecteda port that is malfunctioning it places that port into the brokenstate. Options include:

• disabled

• blocking

• listening

• learning

• forwarding

• broken

ENABLE STP Indicates that the Spanning Tree Protocol is active in this STG.

FASTSTART Indicates that the port is moved straight to the forwarding stateupon being enabled.

PATHCOST Indicates the contribution of this port to the path cost ofpaths towards the spanning tree root which includes thisport. 802.1d-1990 recommends that the default value ofthis parameter be inversely proportional to the speed of theattached LAN.

FORWARD TRANSITION Indicates the number of times this port has transitioned fromthe learning state to the forwarding state.

CHANGE DETECTION Indicates if topology change notifications are sent for the port.

Using the show STG commandsTo display the status of spanning tree on the switch or on a port, use theshow stg commands.

This section includes information on show commands:

• “Displaying all STG information” (page 298)

• “Displaying STG configurations” (page 301)

• “Displaying STG status” (page 302)

• “Displaying basic STG information” (page 303)

• “Displaying additional STG information” (page 304)

• “Displaying STG statistics counters” (page 305)


NN46220-511 04.01 26 June 2009


.


Displaying all STG informationTo display all spanning tree group information, enter the followingcommand:

show stg show-all

The command uses the syntax:

show stg show-all file <value>

where

<value> is the filename to which the output will beredirected.

Figure 129 "Show stg show-all sample output" (page 299) shows sampleoutput for this command.


NN46220-511 04.01 26 June 2009


.


Figure 129Show stg show-all sample output


Table 55Show stg show-all field descriptions

Field Description

Stg Config

STG ID Indicates the STG identifier.

PRIORITY Indicates the value of the priority field that is contained in thefirst (in network byte order) octet of the two octet long port ID.

BRIDGE MAX_AGE Indicates the value that all bridges use for the bridge maximumage when this bridge acts as the root.


NN46220-511 04.01 26 June 2009


.


Table 55Show stg show-all field descriptions (cont’d.)

Field Description

BRIDGE HELLO_TIME Indicates the value that all bridges use for the bridge hello timerwhen this bridge acts as the root.

FORWARD DELAY Indicates the value that all bridges use for forward delay whenthis bridge acts as the root. This time value, measured in unitsof hundredths of a second, controls how fast a port changesits spanning state when moving towards the forwarding state.The value determines how long the port stays in each of thelistening and learning states, which precede the forwardingstate. This value is also used, when a topology change isdetected and is underway, to age all dynamic entries in theforwarding database.

ENABLE STP Indicates that the Spanning Tree Protocol is active in this STG.

STPTRAP TRAP Indicates the traps relating to the Spanning Tree Protocol whichare sent for this STG.

NT-STG Indicates the whether this STG is operating in Nortel mode orin Cisco mode.

• enable—Nortel mode

• disable—Cisco mode

Stg Status


BRIDGE ADDRESS Indicates the MAC address used by this bridge when it must bereferred to in a unique fashion. Nortel recommends that thisbe the numerically smallest MAC address of all the ports thatbelong to this bridge.

NUM PORTS Indicates the number of ports controlled by this bridging entity.

PROTOCOL SPECIFICATION Indicates the version of the Spanning Tree Protocol that isused. The value decLb100 indicates the DEC LAN bridge 100Spanning Tree protocol. IEEE 802.1d implementations willreturn ieee8021d.

TOP CHANGES Indicates the total number of topology changes detected by thisbridge since the management entity was last reset or initialized.

DESIGNATED ROOT Indicates the bridge identifier of the root of the spanning tree asdetermined by the Spanning Tree Protocol as executed by thisnode. This value is used as the root identifier parameter in allconfiguration Bridge PDUs originated by this node.

ROOT COST Indicates the cost of the path to the root as seen from thisbridge.

ROOT PORT Indicates the port number of the port that offers the lowest costpath from this bridge to the root bridge.


NN46220-511 04.01 26 June 2009


.


Table 55Show stg show-all field descriptions (cont’d.)

Field Description

MAX AGE Indicates the maximum age of Spanning Tree Protocolinformation learned from the network on any port before it isdiscarded, in units of hundredths of a second. This is the actualvalue that this bridge is currently using.

HELLO TIME Indicates the amount of time between the transmission ofconfiguration bridge PDUs by this node on any port when it isthe root of the spanning tree or trying to become so, in units ofhundredths of a second. This is the actual value that this bridgeis currently using.

HOLD TIME Indicates the interval length during which no more than twoconfiguration bridge PDUs are transmitted by this node, in unitsof hundredths of a second.

FORWARD DELAY Indicates the how fast (in hundredths of a second) a portchanges its spanning state when moving towards theForwarding state. The value determines how long the portstays in each of the listening and learning states, whichprecede the forwarding state. This value is also used, whena topology change is detected and is underway, to age alldynamic entries in the forwarding database.

This value is the one that this bridge is currently using, incontrast to the bridge forward delay which is the value that thisbridge and all others would start using if this bridge were tobecome the root.

Displaying STG configurationsTo display the spanning tree group configuration for the switch or for thespecified spanning tree group, enter the following command:


The command syntax is:


where

<sid> is the spanning tree group ID.

Figure 130 "Show stg info config command output" (page 302) showssample output for the show stg info config command.


NN46220-511 04.01 26 June 2009


.


Figure 130Show stg info config command output

For descriptions of the parameters for this command, see Table 55 "Showstg show-all field descriptions" (page 299).

Displaying STG statusTo display the spanning tree group status for the specified spanning treegroup or all STGs, enter the following command:

show stg info status <sid>

where

<sid> is the spanning tree group ID.

Figure 131 "Show stg info status command output" (page 303) showssample output for the show stg info status command.


NN46220-511 04.01 26 June 2009


.


Figure 131Show stg info status command output

For descriptions of the parameters for this command, see Table 55 "Showstg show-all field descriptions" (page 299).

Displaying basic STG informationTo display basic spanning tree group information about one or morespecified ports or about all ports, enter the following command:

show ports info stg main [vlan <value> ] [port <value> ]

where

vlan <value> is the VLAN ID from 1 to 4 092,port <value> is the port or range of ports.


(For more information about the show ports info stg extendedcommand, see “Displaying basic STG information” (page 303).)

Figure 132 "Show ports info stg main command output" (page 304) showssample output for the show ports info stg main command.


NN46220-511 04.01 26 June 2009


.


Figure 132Show ports info stg main command output

For descriptions of the parameters for this command, see Table 54 "Showports info stg field descriptions" (page 296).

Displaying additional STG informationTo display additional spanning tree group information about the specifiedport or about all ports, enter the following command:

show ports info stg extended [vlan <value> ] [port <value> ]

where

vlan <value> is the VLAN ID from 1 to 4 092,port <value> is the port or range of ports.


This information is less often used in switch monitoring than theinformation obtained with the show ports info stg main command( “Displaying basic STG information” (page 303)).

Figure 133 "Show ports info stg extended command output" (page305) shows sample output for the show ports info stg extendedcommand.


NN46220-511 04.01 26 June 2009


.


Figure 133Show ports info stg extended command output


Table 56Show ports info stg extended field descriptions

Field Description



DESIGNATED ROOT Indicates the bridge identifier of the root of thespanning tree as determined by the SpanningTree Protocol as executed by this node. Thisvalue is used as the root identifier parameterin all configuration bridge PDUs originated bythis node.

DESIGNATED ROOT COST Indicates the cost of the path to the root asseen from this bridge.

DESIGNATED BRIDGEADDRESS

Indicates the MAC address used by this bridgewhen it must be referred to in a unique fashion.Nortel recommends that this be the numericallysmallest MAC address of all the ports thatbelong to this bridge.

DESIGNATED ROOT PORT Indicates the port number of the port that offersthe lowest cost path from this bridge to the rootbridge.

Displaying STG statistics countersTo display statistics counters for spanning tree groups on all ports or thespecified port, enter the following command:

show ports stats stg <ports>


NN46220-511 04.01 26 June 2009


.


where

<ports> is the port or list of ports.

Figure 134 "Show ports stats stg command (partial output)" (page306) shows sample output for the show ports stats stg command.

Figure 134Show ports stats stg command (partial output)


Table 57Show ports stats stg extended field descriptions

Field Description


IN_CONFIG BPDU Indicates the number of configuration BPUsreceived by this port.

IN_TCN BPDU Indicates the number of topology changenotification BPUs received by this port.

IN_BAD BPDU Indicates the number of bad BPUs received by thisport.

OUT_CONFIG BPDU Indicates the number of Config BPUs transmittedby this port.

OUT_TCN BPDU Indicates the number of topology changenotification BPUs transmitted by this port.

Configuring Multiple Spanning Tree ProtocolThis section describes the following topics:


• “Configuring MSTP region” (page 308)

• “Configuring MSTP CIST” (page 309)


NN46220-511 04.01 26 June 2009


.


• “Configuring MSTP MSTI” (page 310)

• “Mapping an MSTI to a VLAN” (page 310)

• “Showing MSTP configurations” (page 311)

• “Showing MSTP instance information” (page 313)

• “Showing MSTP bridge statistics information” (page 314)

• “Showing MSTP status” (page 315)

• “Showing MSTP port information” (page 316)

Configuring Multiple Spanning Tree ProtocolYou can configure multiple spanning trees using MSTP for an individualVLAN or for multiple VLANs. To set the Multiple Spanning Tree Protocol(MSTP) configuration version, use the following command.

config mstp

The config mstp command is in the CLI Global configuration mode.


config mstp

followed by:

info Shows current level parameter settings and nextlevel directories.

pathcost-type <16-bit|32-bit> Sets the MSTP default path cost version; default is32 bits.

hop count <number> Sets the MSTP hop count. The range is 400 to 4000hundredths of a second; default is 2000.

tx-holdcount <number> Sets the MSTP Transmit Hold Count. The range is1 to 10; the default is 3.

pbt-msti <instance-id> Specifies the Multiple Spanning Tree Instance (MSTI)dedicated to this PBT.

Specify a number between 1 and 63. A value of 0 isused to clear the PBT MSTI.

If VLANs are already mapped to the MSTI, theVLANs must be unmapped before you configure theMSTP.

plsb-msti <instance-id> Specifies the Multiple Spanning Tree Instance (MSTI)as PLSB type.


NN46220-511 04.01 26 June 2009


.


config mstp

followed by:

Specify a number between 1 and 63. A value of 0 isused to clear the PLSB MSTI.

Figure 135 "Config mstp info command" (page 308) shows sample outputfor the config mstp info command.

Figure 135Config mstp info command

Configuring MSTP regionTo configure the MSTP region, use the following command:

config mstp region

The config mstp region command is in the CLI Global configurationmode.


config mstp region

followed by:


name <string> Sets the MSTP configuration name.

• <string> is from 1 to 32 characters.

revision <number> Sets the MSTP region revision number

• <number> is between 0 and 65 535.

config-id-sel <number> Sets the MSTP region configuration ID number.

• <number> is between 0 and 255.

The following figure shows sample output for the config mstp regioncommands.


NN46220-511 04.01 26 June 2009


.


Figure 136Config mstp region command

Configuring MSTP CISTTo configure the MSTP Common and Internal Spanning Tree (CIST)parameters, use the following command:

config mstp cist


config mstp cist

followed by:


force-version <stp-compatible|mstp>

Sets the CIST version.

forward-delay <number> Sets the CIST forward delay from 400 to 3000hundredths of a second; default is 1500.

max-age <number> Sets the CIST maximum age time from 600 to 4000hundredths of a second for the bridge; the default is2000. The step size is in hundreds.

priority <number> Sets the CIST bridge priority from 0 to 61 440 insteps of 4096; the default is 32 768.

The following figure shows sample output of these commands.


NN46220-511 04.01 26 June 2009


.


Figure 137Config mstp cist command

Configuring MSTP MSTITo set the Multiple Spanning Tree Instance (MSTI) configuration version,use the following command:

config mstp msti <instid>

where

<instid> is the instance ID.

The config mstp msti command is in the CLI Instance configurationmode.

This command uses the following options:

config mstp msti <instid>

followed by:

info Shows current level parameter settings and nextlevel directories.The MSTI to VLAN mapping is included in thedisplayed information.

priority Sets the MSTP bridge priority. Allowed values are4096, 8192, 12 288, 16 384, 20 480, 24 576, 28 672,32 768, 36 864, 40 960, 45 056, 49 152, 53 248, 57344, 61 440.

Mapping an MSTI to a VLANA Multiple Spanning Tree Instance-VLAN identifier (MSTI-VID) pool can becreated before VLANs are created. The configuration digest for the node iscalculated based on the MSTI-VID pool. VLANs can therefore be addedand removed without having a negative impact on traffic.


NN46220-511 04.01 26 June 2009


.


To map an MSTI to a VLAN or a range of VLANs, use the followingcommand:

config mstp msti <instance-id> add-vlans <vlan-range>

This command uses the following options:

config mstp msti <instance-id> add-vlans <vlan-range>

<instance-id> The instance identification number.Valid values are: 1 to 63.

Only PBT VLANs can be mapped to a PBT MSTI;you cannot map PBT VLANs to a normal MSTI.

<vlan-range> The VLAN range.Valid values are: 2 to 4094.

To specify a list of VLANs, use a comma. Forexample:configure mstp msti 1 vlan 10, 20, 30

To specify a list and a range of VLANs, use acomma and a dash. For example:configure mstp msti 1 vlan 10, 20,30-40,42

If a specified VLAN is mapped to an instanceother than the specified instance ID, a message isdisplayed to warn you that traffic may be impacted.

A VLAN-MSTI mapping cannot be changed if theVLAN currently exists. An error is displayed if thespecified VLAN is configured on the switch and itis not mapped to the specified instance. You mustdelete the VID first.

To unmap an MSTI from a VLAN or a range of VLANs, use the followingcommand:

config mstp msti <instance-id> remove-vlans <vlan-range>

For variable information, see the preceding table.

Showing MSTP configurationsTo display the Multiple Spanning Tree Protocol (MSTP) relatedbridge-level VLAN and region information, use the following command:

show mstp config


NN46220-511 04.01 26 June 2009


.


The show mstp config command is in the CLI Global configurationmode.

Figure 138 "Show mstp config." (page 312) shows sample output for thiscommand.

Figure 138Show mstp config.


Table 58show mstp config field descriptions

Field Description

Mstp Module Status Indicates if MSTP is enabled on the module.

Number of Msti Supported Indicates the number of MSTIs supported on themodule.

Cist Bridge priority Indicates the CIST bridge priority.

Stp Version Indicates the STP version.

Cist Bridge Max Age Indicates the CIST bridge maximum age inseconds.

Cist Bridge Forward Delay Indicates the CIST bridge forwarding delay inseconds.

Tx Hold Count Indicates the transmission hold count.


NN46220-511 04.01 26 June 2009


.


Table 58show mstp config field descriptions (cont’d.)

Field Description

PathCost Default Type Indicates the PathCost default type.

Max Hop Count Indicates the maximum hop count allowed.

Msti Config Id Selector Indicates the MSTI configuration identificationselector.

Msti Region Name Indicates the MSTI region name.

Msti Region Version Indicates the MSTI region version.

Msti Config Digest Indicates the MSTI configuration digest. This valueis generated automatically by the Metro EthernetRouting Switch.

Showing MSTP instance informationTo show the MSTP instance-specific bridge and VLAN information, use thefollowing command:

show mstp instance <instid>

where

<instid> is the instance ID.

Figure 139 "Show mstp instance command" (page 313) shows sampleoutput for this command.

Figure 139Show mstp instance command


NN46220-511 04.01 26 June 2009


.



Table 59show mstp instance field descriptions

Field Description

Instance ID Indicates the MSTP MSTI instance ID.

Msti Bridge RegionalRoot

Indicates the MSTP MSTI bridge regional rootaddress.

Msti Bridge Priority Indicates the MSTP MSTI bridge priority.

Msti Root Cost Indicates the MSTP MSTI root cost.

Msti Root Port Indicates the MSTP MSTI root port number.

Msti Instance VlanMapped

The four variables that begin with Msti Instance VlanMapped show which VLANs are assigned to theMSTI. The range is 4000. In an effort to simplify thedisplay of this range, VLAN mapping is divided intoclusters of 1000 VLANs per variable name.Msti Instance Vlan Mapped indicates the MSTPMSTI instance VLAN mapped between 1 and 1 024.The mapping for the instance is displayed evenwhen there is no VLAN created for the instance.

Msti Instance VlanMapped2k

Indicates the MSTP MSTI instance VLAN mapped.





Showing MSTP bridge statistics informationTo display the MSTP related bridge-level statistics, use the followingcommand:

show mstp stats

The show mstp stats command is in the CLI Global configuration mode.

Figure 140 "Show mstp stats" (page 315) shows sample output for thiscommand.


NN46220-511 04.01 26 June 2009


.


Figure 140Show mstp stats


Table 60Show mstp stats field descriptions

Field Description

Mstp UP Count Indicates the MSTP up count.

Mstp Down Count Indicates the MSTP down count.

Region Config ChangeCount

Indicates the number of region configurationchanges.

Time since topologychange

Indicates how long ago in seconds the STP topologychanged.

Topology change count Indicates the number of topology changes.

New Root Bridge Count Indicates the number of new root bridges.

Showing MSTP statusTo display the MSTP related status information known by the selectedbridge, use the following command:

show mstp status

The show mstp status command is in the CLI Global configurationmode.

Figure 141 "Show mstp status command" (page 316) shows sample outputfor this command.


NN46220-511 04.01 26 June 2009


.


Figure 141Show mstp status command

Showing MSTP port informationTo display the MSTP, CIST port, and MSTI port information maintained byevery port of the Common Spanning Tree, use the following command:

show ports info mstp

This command includes the following parameters:


followed by:

cistinfo [vlan <value> ] [port<value> ]

Shows port CIST configuration.

• vlan <value> specifies the VLAN IDs.

• port <value> specifies the portlist.

mstiinfo [vlan <value> ] [port<value> ]

Shows port MSTI configuration.



ciststat [vlan <value> ] [port<value> ]

Shows statistics for CIST port.




NN46220-511 04.01 26 June 2009


.



followed by:

mstistat [vlan <value> ] [port<value> ]

Shows port MSTI stats.



cistrole [vlan <value> ] [port<value> ]

Shows port CIST port role.



mstirole [vlan <value> ] [port<value> ]

Shows port MSTI port role.



ATTENTIONYou can clear the MSTP ports CIST and MSTI stats using the followingcommand:clear ports mstpstats [<ports>]

External and internal path costs are displayed incorrectly in the show portsinfo CLI output for the CIST and MST.

Figure 142 "Show ports info mstp cistinfo command output" (page318) shows sample output for this command.


NN46220-511 04.01 26 June 2009


.


Figure 142Show ports info mstp cistinfo command output

Configuring Ethernet MSTP CISTTo configure the Ethernet MSTP CIST parameters for a port, use thefollowing command:

config eth <portlist> mstp cist

where

<portlist> is the port list.

The config eth mstp cist command is in the CLI Global configurationmode.


NN46220-511 04.01 26 June 2009


.



config eth <portlist> mstp cist

followed by:


edge-port <true|false> Sets the MSTP edge port parameter for the port.

forceportstate <enable|disable> Set forceportstate for a port.

hello-time <value> Sets the hello time for a port from 100 to 1000hundredths of a second.

p2p <forcetrue|forcefalse|auto> Sets the Ethernet MSTP CIST point-to-pointparameter for the port.

protocol-migration <true|false> Sets the Ethernet MSTP CIST protocol-migrationparameter for the port.

priority <value> Sets the Ethernet MSTP CIST priority parameter forthe port. The priority must be set in steps of 16 withinthe range of 0 to 240.

pathcost <number> Sets the MSTP path cost parameter for the port.

stp <disable|enable> Sets STP for a port.The default is enable.

Configuring Ethernet MSTP MSTITo configure the Ethernet MSTP MSTI parameters on a port, use thefollowing command:

config eth <portlist> mstp msti <instid>

where

<portlist> is the port list, and<instid> is the instance ID.

The config eth mstp msti command is in the CLI Global configurationmode.



followed by:



NN46220-511 04.01 26 June 2009


.



followed by:

priority <value> Sets the Ethernet MSTP MSTI priority parameterfor the port.

pathcost <value> Sets the MSTP MSTI path cost parameter for theport.

forceport state <enable|disable> Sets the MSTP MSTI force port state parameterfor the port.

stp <disable|enable> Sets STP for a port.The default is enable.


NN46220-511 04.01 26 June 2009


.

321.

Configuring link aggregation using theCLI

Link aggregation allows you to bundle a set of ports into a port group,which is represented as one logical interface to upper layer protocols.

This section describes the link aggregation commands.

For conceptual information about link aggregation, see “Link aggregation(MLT, SMLT, LACP)” (page 47).

Only SMLT is applicable to NNI; all other technology is applicable to bothUNI and NNI.


• “Roadmap of link aggregation commands” (page 321)

• “Configuring link aggregation” (page 325)

• “Using the MLT and SMLT show commands” (page 344)

• “Troubleshooting SMLT problems” (page 354)

• “Global MAC filtering” (page 358)

Roadmap of link aggregation commandsThe following roadmap lists the commands used for configuring linkaggregation.

Command Parameter

config mlt <mid> info

create

cp-limit <enable|disable>[multicast-limit <value>][broadcast-limit <value>]

delete


NN46220-511 04.01 26 June 2009


.

322 Configuring link aggregation using the CLI

Command Parameter

mcast-distribution <enable|disable>

name <string>

perform-tagging <enable|disable>

svlan-porttype <uni|nni|normal>

ntstg <enable|disable>

config mlt <mid> add info

ports <ports>

vlan <vid>

config mlt <mid> remove info

ports <ports>

vlan <vid>

config lacp info

enable

disable

aggr-wait-time <milliseconds>

system-priority <integer>

smlt-sys-id <BaseMac>

fast-periodic-time <milliseconds>

slow-periodic-time <milliseconds>

timeout-scale <integer>

config mlt <mlt id> lacp info

enable

disable

clear-link-aggrgate

key <integer>


config <port-type> <slot|port> lacpinfo

enable

disable

aggr-wait-time <milliseconds>

fast-periodic-time <milliseconds>


NN46220-511 04.01 26 June 2009


.

Roadmap of link aggregation commands 323

Command Parameter

key <integer>

aggregation <true|false>

mode <active|passive>

partner-key <int>

partner-port <int>

partner-port-priority <int>

partner-state <hex>

partner-system-id <mac>

partner-system-priority <int>

port-priority <integer>



port-priority <integer>



timeout <long|short>

timeout-scale <integer>

show lacp info

show ports info lacp all [vlan <value>] [port <value>]

actor-admin [vlan <value>] [port<value>]

actor-oper [vlan <value>] [port<value>]

partner-admin [vlan <value>] [port<value>]

partner-oper [vlan <value>] [port<value>]

extension [vlan <value>] [port<value>]

show ports stats lacp [port<value>]

show mlt lacp info <ifindex>


NN46220-511 04.01 26 June 2009


.


Command Parameter

config mlt <mid> smlt info

create smlt-id <value>

delete

config mlt <mid> ist info

create ip <value> vlan-id <value>

delete

disable

enable

config ethernet <slot/port>cp-limit

<enable|disable>

multicast-limit <value>

broadcast-limit <value>

config ethernet <port> smlt<smltid>

info

create

delete

config sys set smlt-on-single-cp<enable|disable> [timer <value> ]

show mlt show-all [file <value>]

show mlt error collision [<mid>]

show mlt error main [<mid>]

show mlt info [<mid>]

show mlt ist info

show mlt stats [<mid>]

show ports info smlt [vlan <value>] [port <value>]

show ports info config [vlan<value> ] [port <value>]

show smlt info [<mid>]

config fdb fdb-filter info

add <mac>


NN46220-511 04.01 26 June 2009


.


Command Parameter

remove <mac>

config slpp info

add <vid>

remove <vid>

add uni-ports <ports>

remove uni-ports <ports>

operation <enable|disable>

etherType <pid>

tx-interval <integer>

config ethernet <portlist> slpp info

packet-rx-threshold <integer>

packet-rx <enable|disable>

clear-packet-rx-count

show slpp info

port <slot/port>

Configuring link aggregationLink aggregation allows you to bundle a set of ports into a port group,which is represented as one logical interface to upper layer protocols.

This section includes configuration commands for the following topics:

• “Link aggregation commands” (page 326)

• “Adding ports to a link aggregation group” (page 327)

• “Removing ports from a link aggregation group” (page 327)

• “Global LACP commands” (page 328)

• “Aggregator configuration commands” (page 329)

• “Port configuration commands” (page 331)

• “LACP show commands” (page 333)

• “Creating a split multilink trunk from an existing multilink trunk” (page338)

• “Creating an interswitch trunk” (page 339)

• “Creating a single port split multilink trunk” (page 343)

• “Configuring SMLT-on-Single-CPU” (page 344)


NN46220-511 04.01 26 June 2009


.


Link aggregation commandsTo set up multilink trunks on the switch, enter the following command:

config mlt <mid>

where

<mid> is the multilink trunk ID.

The required parameter mid specifies the link aggregation ID.


config mlt <mid>

followed by:

info Shows current settings for the specified linkaggregation group.

create Creates a link aggregation group.

cp-limit <enable|disable> [multicast-limit <value> ] [broadcast-limit<value> ]

Sets the control packet rate limit.

• <enable|disable> = Enables or disablescontrol packet rate limit. To reenablethe ports, issue the command configethernet slot/port state disable,and then enable.

• multicast-limit <value> is themulticast control frame rate.

• broadcast-limit <value> is thebroadcast frame rate.

delete Deletes a link aggregation group.

mcast-distribution <enable|disable> Enables or disables multicast distribution perlink aggregation group. Multicast distributionis disabled by default. For detailed informationabout commands used to configure multicastdistribution over link aggregation, seeConfiguration — IP Multicast (NN46220-519).

name <string> Names a link aggregation group.

• <string> is the name, from 0 to 20characters.

perform-tagging <enable|disable> Enables or disables tagging on a linkaggregation port.


NN46220-511 04.01 26 June 2009


.


config mlt <mid>

followed by:

svlan-porttype <uni|nni|normal> Sets the port type to normal, uni, or nni.

ntstg <enable|disable> Enables or disables NTSTG.

Figure 143 "Config mlt info command output" (page 327) shows sampleoutput for the config mlt info command.

Figure 143Config mlt info command output

Adding ports to a link aggregation groupTo add Ethernet ports to an LACP MLT, ensure the ports and MLT are inthe appropriate VLANs; the LACP keys match; and LACP is enabled onthe ports, on MLT, and globally. For more information, see “LACP-basedMLT for UNI configuration example” (page 404) and “LACP-based MLT forNNI configuration example” (page 405).

Removing ports from a link aggregation groupTo remove Ethernet ports from an LACP MLT, disable LACP on theEthernet port, change the key back to the default, and make aggregationfalse. For more information, see “LACP-based MLT for UNI configurationexample” (page 404) and “LACP-based MLT for NNI configurationexample” (page 405).


NN46220-511 04.01 26 June 2009


.


Global LACP commandsLACP can be enabled or disabled globally. When the LACP system priorityis set globally, it applies to all LACP-enabled aggregators and ports. WhenLACP is enabled on an aggregator or a port, it will use the global systempriority value.

CAUTIONChanges to LACP made at the global level override and reset allport level settings.

Standby mode for LACP aggregation groups of larger than eight ports isnot supported in the current release.

LACP can be described in terms of link aggregation operations withina single system. You can configure a single piece of equipment suchthat it contains more than one system (from the point of view of the linkaggregation operation).

The basic command syntax is:

config lacp


config lacp

followed by:


enable Enables LACP globally.

disable Disables LACP globally.

aggr-wait-time <milliseconds> Sets the aggregator wait time in milliseconds.

system-priority <integer> Sets LACP system priority globally.

• <integer> is the system priority valuewithin the range of 0 to 65 535.


NN46220-511 04.01 26 June 2009


.


config lacp

followed by:

smlt-sys-id <BaseMac> Sets the LACP system ID globally for splitmultilink trunks. This is an optional parameter,and is only used for SMLT situations. You mustconfigure the same LACP SMLT system IDon both aggregation switches to avoid loss ofdata. Nortel recommends that the smlt-sys-id beconfigured such that it matches the base MACaddress of one of the chassis.

• <BaseMac> is the MAC address in theformat {0x00:0x00:0x00:0x00:0x00:0x00}.

fast-periodic-time <milliseconds> Sets the fast periodic time globally.

• <milliseconds> is the fast periodic timevalue.

slow-periodic-time <milliseconds> Sets the slow periodic time globally.

• <milliseconds> is the slow periodic timevalue.

timeout-scale <integer> Sets a timeout scale globally.

• <integer> is the timeout scale value from2 to 10.

Configuration changes to LACP timers are not reflected immediately.LACP timers are not reset until the next time LACP is restarted globally oron a port. This ensures consistency with peer switches.

Aggregator configuration commandsWhen LACP is enabled globally on a multilink trunk, that multilink trunk isassociated with an aggregator and used for link aggregation. When LACPis disabled on a multilink trunk, this multilink trunk functions as a legacymultilink trunk. Using the command clear-link-aggrgate is equivalentto disabling and reenabling LACP on the multilink trunk.

You can attach ports to an aggregator only if their system priorities arethe same; otherwise, they are considered to be operating in two differentswitches. You can attach ports to an aggregator only if their keys are thesame.

The basic command syntax is:

config mlt <mlt id> lacp


NN46220-511 04.01 26 June 2009


.


where

<mlt id> is the multilink trunk ID.



followed by:


enable Enables LACP for a specific multilink trunk.

disable Disables LACP for a specific multilink trunk.

clear-link-aggrgate Clears link aggregation information for a specificmultilink trunk.

key <integer> Sets LACP aggregator key for a specificmultilink trunk.

• <integer> is the LACP actor admin key.

system-priority <integer> Sets LACP system priority for a specific multilinktrunk.

• <integer> is the system priority within therange 0 to 65 535.


followed by:


enable Enables LACP for a specific multilink trunk.

disable Disables LACP for a specific multilink trunk.

clear-link-aggrgate Clears link aggregation information for a specificmultilink trunk.

key <integer> Sets LACP aggregator key for a specificmultilink trunk.

• <integer> is the LACP actor admin key.

system-priority <integer> Sets LACP system priority for a specific multilinktrunk.

• <integer> is the system priority within therange 0 to 65 535.


NN46220-511 04.01 26 June 2009


.


Port configuration commands

ATTENTIONChanges made at the global level override and reset all port level settings.

You can enable or disable LACP on selected ports. A port can operatein active or passive mode. You can configure LACP to use long timeoutor short timeout. A port can be configured to be an individual link or anaggregateable link. All the timers are configurable, however, when youchange a timer, ensure that you restart LACP either globally, or on theport, for the changes to be consistent across the link. The basic commandsyntax is:

config <port-type> <slot|port> lacp

where

<port-type> is Ethernet (eth) or Packet over SONET(pos); and

<slot|port> is the slot and port number.


config <port-type> <slot/port> lacp

followed by:


enable Enables LACP for a specific port type.

disable Disables LACP for a specific port type.

aggr-wait-time <milliseconds> Sets the aggregation wait time (in milliseconds)for a specific port type.

fast-periodic-time <milliseconds> Sets the fast periodic time (in milliseconds) for aspecific port type.

key <integer> Sets LACP aggregation key for a specificport type. You can use a default key only forindividual ports

aggregation <true|false> Sets individual port or aggregatable for aspecific port type.

• true sets port as aggregatable.

• false sets port as individual.

mode <active|passive> Sets the mode as active or passive for aspecific port type.


NN46220-511 04.01 26 June 2009


.



followed by:

partner-key <int> Sets the port partner administration key value.

• <int> is the LACP partner administrativekey; an integer value in the range of 0 and65 535.

partner-port <int> Sets the port partner administration port value.

• <int> is the LACP partner’s administrativeport; an integer value in the range of 0 and65 535.

partner-port-priority <int> Sets the port partner administration port priorityvalue.

• <int> is the LACP partner administrativeport priority; an integer value in the range of0 and 65 535.

partner-state <hex> Sets the port partner administration state.

• <hex> is the LACP partner administrativestate bitmap (Exp, Def, Dis, Col, Syn, Agg,Time, Act).

Example:

• Activity = true

• Aggregating = true

• val = 00000101 (0x05) {0x0..0xff}

partner-system-id <mac> Sets the port partner administration system ID.

• <mac> is the LACP partner administrativesystem ID MAC address in the format:0x00:0x00:0x00:0x00:0x00:0x00.

partner-system-priority <int> Sets the port partner administration systempriority value.

• <int> is the LACP partner administrativesystem priority; an integer value in the rangeof 0 and 65 535.

port-priority <integer> Sets the LACP port priority to specific port type.The default value is 32 768.

• <integer> is the port priority value; aninteger value in the range of 0 and 65 535.


NN46220-511 04.01 26 June 2009


.



followed by:

slow-periodic-time <milliseconds> Sets the slow periodic time (in milliseconds) fora specific port type.

system-priority <integer> Sets system priority for a specific port-type.

• <integer> is the system priority valuewithin the range of 0 to 65 535.

timeout <long|short> Sets the timeout value to either long or short fora specific port type.

timeout-scale <integer> Sets a timeout scale for a specific port type.The default value is 3, and the range is 2 to 10.

LACP show commandsThis section describes show commands you can use to display LACPinformation.

Displaying global LACP configuration informationTo display global LACP configuration information, enter the followingcommand:

show lacp info

Figure 144 "Show lacp info" (page 333) shows the output for the showlacp info command.

Figure 144Show lacp info


NN46220-511 04.01 26 June 2009


.


Displaying LACP configuration informationTo display LACP configuration information, enter the following command:

show ports info lacp

The show ports info lacp command also includes the followingoptions:

show ports info lacp

followed by:

actor-admin [vlan <value> ] [port<value> ]

Shows port LACP actor administrativeinformation.

• vlan <value> is the VLAN ID.

• port <value> is the port or port list.

actor-oper [vlan <value> ] [port<value> ]

Shows port LACP actor operational information.



all [vlan <value> ] [port <value> ] Shows all port LACP information.



partner-admin [vlan <value> ] [port<value> ]

Shows port LACP partner administrativeinformation.



partner-oper [vlan <value> ] [port<value> ]

Shows port LACP partner operationalinformation.



extension [vlan <value> ] [port<value> ]

Shows port LACP timer information.



Figure 145 "Show ports info lacp all" (page 335) shows some of the outputfor this command. When the all parameter is used, LACP information isgiven for each field described in the show ports info lacp table.


NN46220-511 04.01 26 June 2009


.


Figure 145Show ports info lacp all

Displaying LACP statistics information per portTo display LACP statistics information per port, enter the followingcommand:

show ports stats lacp [port <value> ]

where

port <value> is the port list.

Figure 146 "Show ports stats lacp" (page 336) shows sample output forthe show ports stats lacp command.


NN46220-511 04.01 26 June 2009


.


Figure 146Show ports stats lacp


Table 61Show ports stats lacp field descriptions

Field Description

PORT NUM Specifies the port number.

TX LACPDU The number of LACPDUs transmitted on thisaggregation port.

RX LACPDU The number of valid link aggregation controlprotocol data units (LACPDU) received on thisaggregation port.

TX MARKER PDU The number of marker PDUs transmitted on thisaggregation port.

RX MARKER PDU The number of valid marker PDUs received on thisaggregation port.

TX MARKERRESPPDU The number of marker response PDUs transmittedon this aggregation port.

RX MARKERRESPPDU The number of valid marker response PDUsreceived on this aggregation port.

RX UNKNOWN The number of frames received that either:

• carry Slow Protocols Ethernet type values, butcontain an unknown PDU.

• are addressed to the Slow Protocols groupMAC Address, but do not carry the SlowProtocols Ethernet Type.

RX ILLEGAL The number of frames received that carry the SlowProtocols Ethernet Type value (43B.4), but containa badly formed PDU or an illegal value of ProtocolSubtype (43B.4).


NN46220-511 04.01 26 June 2009


.


Displaying LACP configuration information per aggregatorTo display LACP configuration information per aggregator, enter thefollowing command:

show mlt lacp info <ifindex>

where

<ifindex> is the interface index from 64 to 4351.

Figure 147 "Show mlt lacp" (page 337) shows the output for the show mltlacp command.

Figure 147Show mlt lacp

You can also use the following command:

show mlt lacp info

Figure 148 "Show mlt lacp info" (page 338) shows the output for the showmlt lacp info command.


NN46220-511 04.01 26 June 2009


.


Figure 148Show mlt lacp info

Creating a split multilink trunk from an existing multilink trunkRouted SMLT, or RSMLT, is a Layer 3 protocol whereas SMLT is a Layer2 protocol. SMLT is described in this document, and RSMLT is describedin the document Configuring IP Routing Operations.


NN46220-511 04.01 26 June 2009


.


To create a split multilink trunk from an existing multilink trunk, enter thefollowing command:

config mlt <mid> smlt

where

<mid> is the MLT ID.

Before you can create a split multilink trunk, you must first create amultilink trunk (see “Link aggregation commands” (page 326)).


config mlt <mid> smlt

followed by:

info Shows ports and VLANs added to the multilinktrunk.

create smlt-id <value> Creates a split multilink trunk from an existingmultilink trunk.

• <value> is an integer value with a range of1 to 32 (1 to 256 for R modules in R mode).The value must match the peer switchSMLT-ID.

If the SMLT ID already exists on a single portsplit multilink trunk, you cannot assign it to anMLT-based split multilink trunk.

delete Deletes an existing split multilink trunk.

Creating an interswitch trunkTo create an interswitch trunk from an existing multilink trunk, enter thefollowing command:

config mlt <mid> ist

where




NN46220-511 04.01 26 June 2009


.


config mlt <mid> ist

followed by:


create ip <value> vlan-id <value> Creates an interswitch trunk from an existingmultilink trunk (see “Creating an interswitchtrunk from an existing multilink trunk” (page340)).

• ip <value> is a peer IP address

• vlan-id <value> is an integer value.

The peer IP address is the IP address of theIST VLAN on the other aggregation switch.

delete Deletes an existing IST.

You must disable an IST before you can deleteit.

disable Disables an existing IST.

enable Enables an existing IST.

Creating an interswitch trunk from an existing multilink trunkTo create an interswitch trunk from an existing multilink trunk, enter thefollowing command:

config mlt <mlt-id> ist create ip <value> vlan-id <value>

where

<mlt-id> is the MLT ID;ip <value> is the IP address of the peer switch; andvlan-id <value> is the VLAN ID.

An interswitch trunk is enabled when you first create it.

The peer IP address is the IP address of the InterSwitch Trunking (IST)VLAN on the peer aggregation switch. A VLAN created on the redundantaggregation switch must also be created on the second aggregationswitch. The interswitch trunk treats the two switches as a single switch. Toallow the two switches to communicate, you must assign an IP addressto both VLANs.

For example:


NN46220-511 04.01 26 June 2009


.


switch A switch B

VLAN 20 VLAN 20

10.1.1.1. /24 <--------IST--------> 10.1.1.2 /24 *

* Same subnet, same VLAN.

Figure 149 "Config mlt ist create ip vlan-id command output" (page341) shows sample output for the config mlt ist create ip vlan-idcommand, followed by the info command.

Figure 149Config mlt ist create ip vlan-id command output

Enabling and disabling an interswitch trunkTo enable and disable the interswitch trunk, enter the following command:

config mlt <mlt-id> ist <enable|disable>

where

<mlt-id> is the MLT ID.

Figure 150 "Config mlt ist enable/disable command output" (page341) shows sample output for the config mlt ist enable and configmlt ist disable commands. It includes the system warning thatappears when you disable the IST.

Figure 150Config mlt ist enable/disable command output


NN46220-511 04.01 26 June 2009


.


Configuring CP-Limit for an ISTThe CP-Limit feature is disabled by default on all IST ports. It can beenabled on the port under any of the following conditions:

• if the port is removed from the interswitch trunk

• if the interswitch trunk is deleted

• if the interswitch trunk is converted to a normal multilink trunk

Nortel recommends that you disable CP-Limit on IST links. For moreinformation, see "About CP-Limit and SMLT IST" on page 64.

To configure CP-Limit for the interswitch trunk, enter the followingcommand:

config ethernet <slot/port> cp-limit

where

<slot/port> specifies the slot or port.


config ethernet <slot/port> cp-limit

followed by:

<enable|disable> Enables or disables control packet rate limit(CP-Limit). The default setting is enabled.

If you want to reenable CP-Limit on a port, youmust first disable the port and then reenableit (config ethernet <slot/port> state<disable|enable>).

multicast-limit <value> Sets the multicast control frame packet persecond rate (1000 to 100 000).

broadcast-limit <value> Sets the broadcast frame packet per secondrate (1000 to 100 000).

For information about viewing current CP-Limit status for an IST multilinktrunk, see Figure 143 "Config mlt info command output" (page 327).

Deleting an interswitch trunkTo delete the interswitch trunk, enter the following command:

config mlt <mlt-id> ist delete

where


NN46220-511 04.01 26 June 2009


.


<mlt-id> is the MLT ID.

You must disable the interswitch trunk before deleting it (see “Enabling anddisabling an interswitch trunk” (page 341)).

Creating a single port split multilink trunkTo create a single port split multilink trunk, enter the following command:

config ethernet <port> smlt <smltid>

where

<port> is the port number, and<smltid> is the MLT ID.


config ethernet <port> smlt <smltid>

followed by:

info Shows the port SMLT information.

create Creates a single port split multilink trunk.

delete Deletes a single port split multilink trunk.

You cannot use SMLT on brouter ports. LACP is supported on single portsplit multilink trunks. For more information about single port split multilinktrunking, see “Single Port SMLT” (page 79).

Configuration example: single port split multilink trunkThe configuration example shown in Figure 151 "Configuration example:Single Port SMLT" (page 344) uses the commands described previouslyto create a single port split multilink trunk on port 4/5. The switchautomatically disables spanning tree protocol on the port after it isconfigured for SMLT.



NN46220-511 04.01 26 June 2009


.


Figure 151Configuration example: Single Port SMLT

Configuring SMLT-on-Single-CPUTo support SMLT on an aggregation switch with a single CPU, enter thefollowing command:

config sys set smlt-on-single-cp <enable|disable> [timer<value> ]

where

enable enables the SMLT-on-Single-CPU feature;disable disables the SMLT-on-Single-CPU feature;timer <value> sets the SMLT-on-Single-CPU feature

timeout value.

The timeout value determines when the Input/Output (I/O) modules portlink status goes down after the single CPU becomes non-operational. Theparameter is a numerical value in the range 1 to 3. If not set, the defaultvalue (3) is used. A timer value of 1 relates to approximately 3 seconds ofdetection time and a timer value of 3 relates to approximately 9 secondsof detection time.

Using the MLT and SMLT show commandsTo display information and statistics about MLT operation in the switch,use the show mlt commands.


NN46220-511 04.01 26 June 2009


.

Using the MLT and SMLT show commands 345

This section includes information on show commands:

• “Displaying all multilink trunk information” (page 345)

• “Displaying information about collision errors” (page 348)

• “Displaying information about Ethernet errors” (page 349)

• “Displaying multilink trunk status” (page 350)

• “Displaying interswitch trunk status” (page 350)

• “Displaying split multilink trunk status” (page 351)

• “Displaying all ports configured for single port split multilink trunk”(page 352)

• “Displaying a port configured for Single Port SMLT” (page 353)

• “Displaying MLT statistics” (page 353)

Displaying all multilink trunk informationThe show mlt show-all command shows all multilink trunk information.

The command uses the syntax:

show mlt show-all [file <value> ]

where

<value> is the filename to which the output will bedirected.

Figure 152 "Show mlt show-all sample output" (page 346), Figure 153"Show mlt show-all sample output (continued)" (page 347), and Figure 154"Show mlt show-all sample output (continued)" (page 348) show sampleoutput for this command.


NN46220-511 04.01 26 June 2009


.


Figure 152Show mlt show-all sample output


NN46220-511 04.01 26 June 2009


.


Figure 153Show mlt show-all sample output (continued)


NN46220-511 04.01 26 June 2009


.


Figure 154Show mlt show-all sample output (continued)

Displaying information about collision errorsTo display information about collision errors in the specified multilink trunk,or for all multilink trunks, enter the following command:

show mlt error collision [ <mid> ]

where


Figure 155 "Show mlt error collision command output" (page 349) showssample output for the show mlt error collision command.


NN46220-511 04.01 26 June 2009


.


Figure 155Show mlt error collision command output

Displaying information about Ethernet errorsTo display information about the types of Ethernet errors sent and receivedby the specified multilink trunk or all multilink trunks, enter the followingcommand:

show mlt error main [ <mid> ]

where


Figure 156 "Show mlt error main command output" (page 349) showssample output for the show mlt error main command. The IMACcolumns refer to internal MAC address errors.

Figure 156Show mlt error main command output


NN46220-511 04.01 26 June 2009


.


Displaying multilink trunk statusTo display the status of MultiLink Trunking for the switch or for thespecified multilink trunk ID, enter the following command:

show mlt info [ <mid> ]

where


Figure 157 "Show mlt info command output" (page 350) shows sampleoutput for the show mlt info command:

Figure 157Show mlt info command output

Displaying interswitch trunk statusTo display the status of interswitch trunking for the switch or for thespecified multilink trunk ID, enter the following command:

show mlt ist info

Figure 158 "Show mlt ist info command output" (page 351) shows sampleoutput for the show mlt ist info command.


NN46220-511 04.01 26 June 2009


.


Figure 158Show mlt ist info command output

Displaying split multilink trunk statusTo display split multilink trunk status for the switch or for a specific SMLTID, enter the following command:

show smlt info [ <mid> ]

where


The switch shows both MLT-based split multilink trunk information andsingle port split multilink trunk information.

Figure 159 "Show smlt info command output" (page 352) shows outputfrom a sample show smlt info command.


NN46220-511 04.01 26 June 2009


.


Figure 159Show smlt info command output

Displaying all ports configured for single port split multilink trunkTo view all ports currently configured for single port split multilink trunk,enter the following command:

show ports info smlt [vlan <value> ] [port <value> ]

where

vlan <value> is the VLAN ID, andport <value> is a port or list of ports.

The VLAN ID and the port are optional parameters.

Figure 160 "Show ports info smlt command output" (page 353) shows theoutput from a sample show ports info smlt command.


NN46220-511 04.01 26 June 2009


.


Figure 160Show ports info smlt command output

Displaying a port configured for Single Port SMLTTo view a port configured for Single Port SMLT, enter the followingcommand:

show ports info config [vlan <value> ] [port <value> ]

where

vlan <value> is the VLAN ID, andport <value> is a port or list of ports.

Figure 161 "Show ports info config command output" (page 353) showsoutput from a sample show ports info config command.

Figure 161Show ports info config command output

Displaying MLT statisticsTo display MultiLink Trunking statistics for the switch or for the specifiedmultilink trunk ID, enter the following command:


NN46220-511 04.01 26 June 2009


.


show mlt stats [ <mid> ]

where


Figure 162 "Show mlt stats command output" (page 354) shows sampleoutput for the show mlt stats command.

Figure 162Show mlt stats command output

Troubleshooting SMLT problemsThis section provides procedures for troubleshooting IST problems andsingle-user problems.

The following topics are included:

• “Troubleshooting IST problems” (page 354)

• “Troubleshooting problems with a single user” (page 357)

Troubleshooting IST problemsTo troubleshoot SMLT IST problems:


NN46220-511 04.01 26 June 2009


.

Troubleshooting SMLT problems 355

Step Action

1 Enter the show mlt ist stat command to display the ISTmessage count. (Figure 163 "Show mlt ist stat command output"(page 355)).Figure 163Show mlt ist stat command output

2 Enter the show mlt info command to display all the multilinktrunks in the switch, their admin-type, running type, ports, andVLANs (Figure 157 "Show mlt info command output" (page350)).

3 Check to ensure that IST is operational by using the show mltist info command (Figure 164 "Show mlt ist info commandoutput" (page 356)).


NN46220-511 04.01 26 June 2009


.


Figure 164Show mlt ist info command output

4 If IST is not operational, check to ensure that:

a The correct VLAN ID exists on either side of the interswitchtrunk

b The IST configuration contains the correct local and peer IPaddresses

5 If IST is operational, check that the SMLT port is operating byusing the show mlt smlt info command (Figure 165 "Showmlt smlt info command output" (page 356)).

a If the SMLT status is SMLT, the status is correct.Figure 165Show mlt smlt info command output

b If the SMLT status is NORMAL, the link is running in a normal(single) mode and not SMLT mode. The reasons for this canbe as follows:


NN46220-511 04.01 26 June 2009


.

Troubleshooting SMLT problems 357

• the remote split multilink trunk link is not operational

• the ID is not configured on the other switch. To determinethis, check to see whether the SMLT IDs match

• the IST is not operational

--End--

Troubleshooting problems with a single userTo determine if only a single user is affected, check the VLAN FDB tableson both IST switches using the show vlan info fdb-entry <vlan-id>command. Both FDB tables should be synchronized.

The command shows whether:

• The MAC address is learned on the local SMLT port (that is, SMLTREMOTE flag is false). See Figure 166 "Show vlan info fdb-entrycommand output" (page 357).

or

• The MAC address is learned through IST from a remote SMLT port(that is, the SMLT REMOTE flag is true).

The FDB table entry for the client connected to the user access switchmust specify the learned split multilink trunk port as INTERFACE in bothIST switches.

Figure 166Show vlan info fdb-entry command output


NN46220-511 04.01 26 June 2009


.


Global MAC filteringYou can globally configure MAC filtering to disallow bridging or routing ofany packets transmitted or received from specified MAC addresses on anyVLAN.

To globally filter MAC addresses, use the following command:

config fdb fdb-filter


config fdb fdb-filter

followed by:

info Show current level parameter settings and nextlevel directories.

add <mac> Adds a global FDB filter.

• <mac> is the MAC address to filter.

Enter the MAC address in the following format{0x00:0x00:0x00:0x00:0x00:0x00}.

remove <mac> Removes a global FDB filter.

• <mac> is the MAC address to filter.

Enter the MAC address in the following format{0x00:0x00:0x00:0x00:0x00:0x00}.

Figure 167 "Config fdb fdb-filter info command output" (page 358) show anexample of the config fdb fdb-filter info command output.

Figure 167Config fdb fdb-filter info command output

Figure 168 "Show fdb fdb-filter command output" (page 359) shows anexample of the show fdb fdb-filter command output:


NN46220-511 04.01 26 June 2009


.

Global MAC filtering 359

Figure 168Show fdb fdb-filter command output


NN46220-511 04.01 26 June 2009


.



NN46220-511 04.01 26 June 2009


.

361.

Configuring Simple Loop PreventionProtocol

Logical loops can occur in SMLT networks because of misconfigurations,switch problems, or because MLT is not operating correctly. You candetect loops with Simple Loop Prevention Protocol (SLPP). For moreinformation about SLPP, see .

SMLT is only applicable to NNI ports.

The following topics are included:

• “Configuring SLPP on a port” (page 362)

• “Showing SLPP information” (page 363)

• “Showing SLPP port information” (page 364)

To configure Simple Loop Prevention Protocol, use the followingcommand:

config slpp

This command has the following options:

config slpp

followed by:

add <vid> Adds a VLAN to a SLPP transmission list.

• <vid> is the ID of the VLAN.

etherType <pid> Specifies the SLPP PDU Ether type.

• <pid> is the SLPP protocol ID in hexadecimalformat.

remove <vid> Removes a VLAN from a SLPP transmission list.

• <vid> is the ID of the VLAN.


NN46220-511 04.01 26 June 2009


.

362 Configuring Simple Loop Prevention Protocol

config slpp

followed by:


operation <enable|disable> Enables or disables the SLPP operation.

The SLPP packets transmit and receive process isactive only when the SLPP operation is enabled.When the SLPP operation is disabled, no SLPPpacket is sent out, and any received SLPP packet isdiscarded.

tx-interval <integer> Sets the SLPP packet transmit interval.

• <integer> is the SLPP packet transmit interval.

The range is 500 to 5000 ms, and the default is 500ms.

Figure 169 "Config slpp slpp info command" (page 362) shows how todisplay the SLPP transmission list and operation state.

Figure 169Config slpp slpp info command

Configuring SLPP on a portTo configure SLPP on a port, use the following command:

config ethernet <portlist> slpp

where

portlist is the slot/port.



NN46220-511 04.01 26 June 2009


.

Showing SLPP information 363

config ethernet <portlist> slpp

followed by:

packet-rx <enable|disable> Enables or disables SLPP packet reception on thelisted ports

packet-rx-threshold <integer> Specifies the SLPP reception threshold on the ports.The threshold is an integer.


clear-packet-rx-count Manually clears the total number of SLPP PDUsreceived on a particular port.

The packet reception threshold specifies how many SLPP packets arereceived by the port before it is administratively disabled. Figure 170"Config ethernet command" (page 363) shows how to display the SLPPstate on a port:

Figure 170Config ethernet command

Showing SLPP informationTo show SLPP information, use the following command:

show slpp info

The following shows SLPP information.

=====================================================SLPP Info

=====================================================etherType (hex) : 0x8104operation: disabled


NN46220-511 04.01 26 June 2009


.


tx-interval : 5000vlan : 1, 3, 4

uni-ports :2/1,2/3

For an SLPP configuration example, see “Single Port SMLT with SLPPconfiguration example” (page 377).

Showing SLPP port informationTo show SLPP port information, use the following command:

show ports info slpp [port <value> ]

where

port <value> is the port list.

ATTENTIONThe Incoming VLAN Id and the SLPP PDU originator is displayed only when aport shuts down on reception of SLPP PDUs and pkt-rx-threshold of the port isreached.

The following shows SLPP information.

ERS-8606:5# show ports info slpp port 2/6,2/16=========================================================================

Port Interface=========================================================================

PORT PKT-RX PKT-RX PKT-RX INCOMING SLPP PDUNUM THRESHOLD COUNT VLAN ID ORIGINATOR-------------------------------------------------------------------------2/6 enable 200 181 10 local2/16 enable 200 181 10 local


Table 62Show ports info slpp field descriptions

Field Description

PORT NUM Specifies the port number.

PKT-RX Specifies if SLPP is enabled or disabled.

PKT-RX THRESHOLD Specifies the threshold for packet reception asa range of 1 to 20. After the port reaches thepacket threshold, it shuts down.

INCOMING VLAN ID VLAN ID of the classified packet on a portdisabled by SLPP.


NN46220-511 04.01 26 June 2009


.

Showing SLPP port information 365

Table 62Show ports info slpp field descriptions (cont’d.)

Field Description

PKT-RX Count Specifies the total number of SLPP PDUsreceived on a port irrespective of the VLAN towhich the port belongs.

SLPP PDU ORIGINATOR Specifies the originator of the SLPP PDU.


NN46220-511 04.01 26 June 2009


.



NN46220-511 04.01 26 June 2009


.

367.

Device Manager configurationexamples

This section provides examples of common link aggregation configurationtasks using Device Manager.

• For conceptual information about VLANs and link aggregation, see“Layer 2 operational concepts” (page 21).

• For Device Manager link aggregation configuration information, see“Configuring link aggregation using Device Manager” (page 183).


• “SMLT and LACP configuration example” (page 367)

• “Single Port SMLT and LACP configuration example” (page 371)

SMLT and LACP configuration exampleThe Metro Ethernet Routing Switch 8600 fully supports the IEEE 802.3adLink Aggregation Control Protocol. LACP is supported on MLT and DMLTlinks and extends to a pair of SMLT switches.

With this extension, the Metro Ethernet Routing Switch 8600 provides astandardized external link aggregation interface to third party vendor IEEE802.3ad implementations.

In this example, Metro Ethernet Routing Switch 8600C is used asthe SMLT client; any switch that supports LACP can be used as anLACP-enabled SMLT client.

Do not use 802.3ad on the interswitch trunk. The LACP keys on the SMLTcore switches must match (Metro Ethernet Routing Switch 8600 A, MetroEthernet Routing Switch 8600 B).

The following figure shows the network topology.


NN46220-511 04.01 26 June 2009


.

368 Device Manager configuration examples

Figure 171SMLT and LACP configuration example

Assume the following:

• The interswitch trunk has already been created.

• VLAN 100 has already been created on all three switches with theport membership as described in Figure 171 "SMLT and LACPconfiguration example" (page 368).

• Metro Ethernet Routing Switch 8600 C is already configured and usesports 1/10 to 1/13. The LACP key on this switch does not need tomatch that of the SMLT core switches.

• The LACP key on both Metro Ethernet Routing Switch 8600 A andMetro Ethernet Routing Switch 8600 B must match.

The following configuration can be performed on both SMLT core switches.

Step Action

1 Using Device Manager, go to VLAN > MLT/LACP.

The MLT_LACP box appears.

2 On the LACP Global tab, ensure that Enable is selected.

Accept the default values for the other parameters.


NN46220-511 04.01 26 June 2009


.

SMLT and LACP configuration example 369

3 Click Apply.

4 Click the Multilink/LACP Trunks tab.

The Multilink/LACP Trunks box appears.

5 Click Insert.

The MLT_LACP, Insert Multilink/LACP Trunks box appears.Figure 172Insert Multilink/LACP Trunks box

6 Configure the parameters as shown in Figure 172 "InsertMultilink/LACP Trunks box" (page 369).

7 Click Insert.

The following figure shows the port information. (To view thisinformation, go to VLAN > MLT/LACP > Multilink/LACP Trunks.)


NN46220-511 04.01 26 June 2009


.


Figure 173MLT LACP information

8 Go to VLAN > MLT/LACP > LACP.

The MLT_LACP box appears.

9 Change the ActorAdminKey to 1; this is the same key numberthat will be applied to ports 1/10 and 1/11.Figure 174MLT_LACP, LACP tab

10 Ensure that the ports 1/10 and 1/11 belong to exactly the sameVLANs, otherwise the LAG will not display. On each LAG port,three fields must be changed in the order given:

a Click on the LAG port, and right-click.

b Select Edit General > LACP.

c Set ActorAdminKey equal to 1 and then click Apply.

d Set ActorAdminState to aggregation and then click Apply.

e Select AdminEnable and then click Apply.

Assuming the configuration on Metro Ethernet Routing Switch8600C is correct and you have link connectivity, VLAN >MLT/LACP > MLT/LACP now displays port 1/10 and 1/11.

--End--


NN46220-511 04.01 26 June 2009


.

Single Port SMLT and LACP configuration example 371

Single Port SMLT and LACP configuration exampleSingle Port SMLT lets you configure a split multilink trunk using a singleport. The Single Port SMLT behaves like an MLT-based SMLT and cancoexist with SMLTs in the same system; however, an SMLT ID can belongto either an MLT-SMLT or a Single Port SMLT per chassis.With SinglePort SMLT, you can scale the number of split multilink trunks on a switchto a maximum number of available ports.

This example highlights the steps used to configure Single Port SMLTusing LACP to create the LAG. Any LACP-enabled device can be used asthe LACP client. The following figure shows the network topology.

Figure 175Network topology for Single Port SMLT example

Assume the following:

• The interswitch trunk has already been created as shown in thepreceding figure.

• VLAN 10 has already been created on the two switches with the portmembership described in the preceding figure.

• The LACP keys on both Metro Ethernet Routing Switch 8600A andMetro Ethernet Routing Switch 8600B must match. The LACP key onthe server (LACP client) does not have to match the Metro EthernetRouting Switch 8600 key.

The following configuration must be performed on both SMLT coreswitches:


NN46220-511 04.01 26 June 2009


.


Step Action

1 In Device Manager, select the port to be configured andright-click.

2 Select Edit General > SMLT.

The Port box appears.Figure 176Port box

3 Click Insert.

The Insert SMLT box appears.Figure 177Insert SMLT

4 Insert a new SMLT group ID. The ID must match on all ports onboth SMLT core switches.

5 Click Insert.

6 Set the LACP key, check aggregate, and click the LACP tab andenable LACP by selecting the AdminEnable check box.


NN46220-511 04.01 26 June 2009


.


Figure 178LACP enable

7 Click Apply.

--End--


NN46220-511 04.01 26 June 2009


.



NN46220-511 04.01 26 June 2009


.

375.

CLI configuration examplesThis section provides examples of common link aggregation configurationtasks, including the command line interface (CLI) commands you use tocreate the configuration.

• For conceptual information about VLANs and link aggregation, see“Layer 2 operational concepts” (page 21).

• For information about the commands used in these examples, see:

— “Configuring VLANs using Device Manager” (page 99)

— “Configuring STGs using the CLI” (page 287)

— “Configuring link aggregation using the CLI” (page 321)


• “MultiLink Trunking configuration example” (page 376)

• “Single Port SMLT with SLPP configuration example” (page 377)

• “SMLT triangle with loop detection configuration example” (page 379)

• “Square SMLT configuration example” (page 386)

• “Full mesh SMLT configuration example” (page 390)

• “SMLT and VRRP configuration example” (page 394)

• “SMLT and multicast configuration example” (page 397)

• “Triangle SMLT and LACP configuration example” (page 398)

• “Single Port SMLT and LACP configuration example” (page 401)

• “Multiple Spanning Tree Protocol configuration example” (page 406)

• “LACP-based MLT for UNI configuration example” (page 404)

• “LACP-based MLT for NNI configuration example” (page 405)


NN46220-511 04.01 26 June 2009


.

376 CLI configuration examples

MultiLink Trunking configuration exampleThis configuration example shows how to create a multilink trunk anda VLAN (VLAN 100) between two Metro Ethernet Routing Switch 8600devices. The network is used to carry user traffic Figure 179 "MLT withina VLAN" (page 376).

Figure 179MLT within a VLAN

The following sections provide step-by-step procedures that show how toconfigure switch S1 and S2 for this example.

Configuring S1

Step Action

1 Create VLAN 100:

MERS-8606:5# config vlan 100 create byport 1

2 Create multilink trunk10:

MERS-8606:5# config mlt 10 createMERS-8606:5# config mlt 10 add ports 1/1,1/2,2/1,2/2MERS-8606:5# config mlt 10 add vlan 100

--End--

Configuring S2

Step Action

1 Create VLAN 100:

MERS-8606:5# config vlan 100 create byport 1

2 Create multilink trunk 10:


NN46220-511 04.01 26 June 2009


.

Single Port SMLT with SLPP configuration example 377

MERS-8606:5# config mlt 10 createMERS-8606:5# config mlt 10 add ports 1/1,1/2,2/1,2/2MERS-8606:5# config mlt 10 add vlan 100

3 To have an MLT-UNI, when creating the endpoint, add the MLTID and leave port, ring ID, mod ID and esuport empty.

--End--

Single Port SMLT with SLPP configuration exampleThe single port Split MultiLink Trunking (SMLT) design is similar to thetriangle SMLT design. The only difference is that only a single port fromeach InterSwitch Trunking (IST) switch goes to the access server. Thefollowing figure shows the network topology.

Figure 180Single Port SMLT

Configuring Metro Ethernet Routing Switch 8600A

Step Action

1 Configure VLANs:

MERS8600-B:5# config vlan 1900 create byport 1MERS8600-B:5# config vlan 10 create byport 1


NN46220-511 04.01 26 June 2009


.


2 Enable SLPP and add VLAN 10:

MERS8600-B:5# config slpp add 10MERS8600-B:5# config slpp operation enable

3 Configure MLT 5 used for the IST link and add the IST VLAN:

MERS8600-B:5# config mlt 5 createMERS8600-B:5# config mlt 5 add ports 2/1,3/1MERS8600-B:5# config vlan 1900 add-mlt 5

4 Configure the IP address and interswitch trunk. The IP addresspoints to the partner interswitch trunk node:

MERS8600-B:5# config vlan 1900 ip create 1.1.1.1/30MERS8600-B:5# config mlt 5 ist create ip 1.1.1.2vlan-id 1900

5 Configure Single Port SMLT:

MERS8600-B:5# config ether 1/1 smlt 1 create

6 Enable SLPP packet reception on port 1/1:

MERS8600-B:5# config ethernet 1/1 slpp packet-rxenable

--End--

Configuring MERS8600C

Step Action

1 Configure VLANs:

MERS8600-C:5# config vlan 1900 create byport 1MERS8600-C:5# config vlan 10 create byport 1

2 Enable SLPP:

MERS8600-C:5# config slpp add 10MERS8600-C:5# config slpp operation enable

3 Configure MLT. VLAN 10 must be spanned across theinterswitch trunk (MLT-5):

MERS-8606:5# config mlt 5 createMERS-8606:5# config mlt 5 add ports 2/1,3/1MERS-8606:5# config mlt 5 add vlan 1900

4 Configure IP address and IST. The IP address points to thepartner IST node:

MERS-8606:5# config vlan 1900 ip create 1.1.1.2/30MERS-8606:5# config mlt 5 ist create ip 1.1.1.1vlan-id 1900


NN46220-511 04.01 26 June 2009


.

SMLT triangle with loop detection configuration example 379

5 Configure Single Port SMLT:

MERS-8606:5# config ether 1/1 smlt 1 create

6 Enable SLPP packet reception on port 1/1, and set the thresholdto 1:

MERS8600-C:5# config ethernet 1/1 slpp packet-rxenableMERS8610-C:5# config ethernet 1/1 slpppacket-rx-threshold 1

To view the status of all SMLT ports, and show SLPPconfiguration information, use the following commands:

MERS8610-B:5# show port info smlt port 1/1MERS8610-B:5# show slpp infoMERS8610-B:5# show ports info slpp port 1/1MERS8600-B:5# show log file tail

If port 1/1 is disabled on either Metro Ethernet Routing Switch8600A or Metro Ethernet Routing Switch 8600B because eitherswitch received its own SLPP-PDU, a message is logged and atrap will be used.

--End--

SMLT triangle with loop detection configuration exampleThis configuration example shows how to create an SMLT triangle usingthree Metro Ethernet Routing Switch 8600 devices and a VLAN (VLAN 10),which is used to carry user traffic Figure 181 "SMLT triangle configurationexample" (page 380). The following configuration example is based ona three node network where MERS8600A is the SMLT client. Althoughonly one port is used to connect to the SMLT client from each SMLTaggregation switch in this example, up to 8 total links can be used to carrytraffic between the two.


NN46220-511 04.01 26 June 2009


.


Figure 181SMLT triangle configuration example

The following sections provide step-by-step procedures that show how toconfigure switches Metro Ethernet Routing Switch 8600A, Metro EthernetRouting Switch 8600B, and Metro Ethernet Routing Switch 8600C for thisexample. The procedure configures:

• VLAN 1900 for the IST VLAN using MLT ID = 5

• VLAN 10 to the SMLT VLAN using MLT ID = 1

• SLPP packet receive threshold on MERS8600B (default) andMERS8600C (5)

Configuring MERS8600B

Step Action

1 Configure VLANs:

MERS-8606-B:5# config vlan 1900 create byport 1MERS-8606-B:5# config vlan 10 create byport 1

2 Configure MLT 5 used for the IST link and add the IST VLAN.Disable the CP-Limit for ports 2/1 and 3/1:


NN46220-511 04.01 26 June 2009


.


MERS-8606-B:5# config mlt 5 createMERS-8606-B:5# config mlt 5 add ports 2/1,3/1MERS-8606-B:5# config ether 2/1,3/1 cp-limitdisableMERS-8606-B:5# config vlan 1900 add-mlt 5

3 Configure the IST IP address and create the interswitch trunkusing MLT 5. The IP address is the IP address of the remotepartner IST node.

MERS-8606-B:5# config vlan 1900 ip create1.1.1.1/30MERS-8606-B:5# config mlt 5 ist create ip 1.1.1.2vlan-id 1900

4 Configure the SMLT link:

MERS-8606-B:5# config mlt 1 createMERS-8606-B:5# config mlt 1 perform-tagging enableMERS-8606-B:5# config mlt 1 add ports 1/1MERS-8606-B:5# config mlt 1 smlt create smlt-id 1

5 Add VLAN 10 to the interswitch trunk and SMLT VLANs:

MERS-8606-B:5# config vlan 10 add-mlt 1MERS-8606-B:5# config vlan 10 add-mlt 5

6 Enable loop detection on port 1/1. By default, the actionwill be set to portdown. This can be verified by using theshow config module port or config ethernet 1/1info command. The loop detect timers should be staggeredbetween the MERS8600B and MERS8600C: change the defaultmac-flap-time-limit from the default setting of 500 ms to700 ms.

MERS-8606-B:5# config ethernet 1/1 loop-detectenableMERS-8606-B:5# config mac-flap-time-limit 700

--End--


Step Action

1 Configure VLANs:

MERS-8606-C:5# config vlan 1900 create byport 1MERS-8606-C:5# config vlan 10 create byport 1

2 Configure MLT 5 used for the IST link and add the IST VLAN.Disable CP-Limit for ports 2/1 and 3/1.


NN46220-511 04.01 26 June 2009


.


MERS-8606-C:5# config mlt 5 createMERS-8606-C:5# config mlt 5 add ports 2/1,3/1MERS-8606-C:5# config ether 2/1,3/1 cp-limitdisableMERS-8606-C:5# config vlan 1900 add-mlt 5

3 Configure the IST IP address and create the interswitch trunkusing MLT 5. The IP address used is the IP address of theremote partner IST node.

MERS-8606-C:5# config vlan 1900 ip create1.1.1.2/30MERS-8606-C:5# config mlt 5 create ip 1.1.1.1vlan-id 1900

4 Configure the SMLT link:

MERS-8606-C:5# config mlt 1 createMERS-8606-C:5# config mlt 1 perform-tagging enableMERS-8606-C:5# config mlt 1 add ports 1/1MERS-8606-C:5# config mlt 1 smlt create smlt-id 1

5 Add VLAN 10 to the IST and SMLT VLANs:

MERS-8606-C:5# config vlan 10 add-mlt 1MERS-8606-C:5# config vlan 10 add-mlt 5

6 Enable loop detection on port 1/1:

MERS-8606-C:5# config ethernet 1/1 loop-detectenable

--End--

Configuring MERS8600A

Step Action

1 Configure VLAN 10:

MERS-8606-A:5# config vlan 10 create byport 1MERS-8606-A:5# config vlan 10 ports add 2/1-2/5

2 Configure the MLT link:

MERS-8606-A:5# config mlt 1 createMERS-8606-A:5# config mlt 1 perform-tagging enableMERS-8606-A:5# config mlt 1 add ports 1/1,1/2MERS-8606-A:5# config vlan 10 add-mlt 1

3 Enable Spanning Tree fast start on ports 2/1 to 2/5:


NN46220-511 04.01 26 June 2009


.


MERS-8606-A:5# config ethernet 2/1-2/5 stg 1faststart enable

--End--

Verifying network operations

Figure 182 "Show mlt info output" (page 383) to Figure 185 "Loopdetection commands" (page 386) show commands you can use to verifythat the network is operating correctly.

Figure 182Show mlt info output

The MLT CURRENT status for MLT-5 is ist. If this status is norm thenthe IST is not active; there may be a misconfiguration or the links are notactive. The current MLT mode is smlt. If there is a misconfiguration or alink down in the network, the value of MLT CURRENT would be norm.


NN46220-511 04.01 26 June 2009


.


Figure 183Show mlt commands


NN46220-511 04.01 26 June 2009


.


Figure 184Show mlt commands, part 2

Loop Detection


NN46220-511 04.01 26 June 2009


.


Suppose a loop is formed between MERS8600A, MERS8600B, andMERS8600C. The commands shown in Figure 185 "Loop detectioncommands" (page 386) show commands you can use to display the MACaddress that is looping.

Figure 185Loop detection commands

Square SMLT configuration exampleThe main rule for a square configuration (see Figure 186 "Square SMLT"(page 387)) is that the IST pairs, MERS8600A and D, and B and C, eachmust have matching SMLT IDs. However, these IDs can differ between thetwo IST pairs. The initial configuration creates the IST links between A andB, and C and D. Note that the IST IP addresses differ; Nortel recommendsthat you use a different subnet for the IST IP addresses between the pairs.


NN46220-511 04.01 26 June 2009


.

Square SMLT configuration example 387

Figure 186Square SMLT


Step Action

1 Disable CP-Limit on IST ports:

MERS-8606:5# config ether 2/1,3/1 cp-limit disable

2 Configure VLANs:

MERS-8606:5# config vlan 1900 create byport 1MERS-8606:5# config vlan 10 create byport 1


MERS-8606:5# config mlt 5 createMERS-8606:5# config mlt 5 add ports 2/1,3/1


NN46220-511 04.01 26 June 2009


.


MERS-8606:5# config mlt 5 add vlan 1900MERS-8606:5# config mlt 5 add vlan 10

4 Configure the IP address and IST. The IP address points to thepartner IST node:


5 Configure SMLT. The SMLT ID must be identical for each ISTpair:

MERS-8606:5# config mlt 1 createMERS-8606:5# config mlt 1 smlt create smlt-id 1MERS-8606:5# config mlt 1 add vlan 10MERS-8606:5# config mlt 1 add ports 1/1

--End--


Step Action



2 Configure VLANs:



MERS-8606:5# config mlt 5 createMERS-8606:5# config mlt 5 add ports 2/1,3/1MERS-8606:5# config mlt 5 add vlan 1900MERS-8606:5# config mlt 5 add vlan 10




MERS-8606:5# config mlt 1 createMERS-8606:5# config mlt 1 smlt create smlt-id 1


NN46220-511 04.01 26 June 2009


.

Square SMLT configuration example 389

MERS-8606:5# config mlt 1 add vlan 10MERS-8606:5# config mlt 1 add ports 1/1

--End--


Step Action



2 Configure VLANs:








--End--

Configuring MERS8600D

Step Action



2 Configure VLANs:


NN46220-511 04.01 26 June 2009


.









Use the show mlt info and the show smlt info commandsto verify the status of the multilink trunks.

--End--

Full mesh SMLT configuration exampleThe full mesh SMLT design is similar to the square SMLT, except morelinks are added to fully mesh the four nodes (see Figure 187 "Full meshSMLT" (page 391)). As with the square configuration, it is imperative thatall links within the SMLT group contain the same SMLT ID, however, thisID need not be the same between each IST pair.


NN46220-511 04.01 26 June 2009


.

Full mesh SMLT configuration example 391

Figure 187Full mesh SMLT


Step Action



2 Configure VLANs:






NN46220-511 04.01 26 June 2009


.




MERS-8606:5# config mlt 1 createMERS-8606:5# config mlt 1 smlt create smlt-id 1MERS-8606:5# config mlt 1 add vlan 10MERS-8606:5# config mlt 1 add ports 1/1,1/17

--End--


Step Action



2 Configure VLANs:








--End--



NN46220-511 04.01 26 June 2009


.

Full mesh SMLT configuration example 393

Step Action



2 Configure VLANs:




4 Configure the IP address and IST. The IP address points to thepartner interswitch trunk node:




--End--

Configuring MERS8600D

Step Action



2 Configure VLANs:


3 Configure MLT. VLAN 10 must be spanned across the IST(MLT-5):

MERS-8606:5# config mlt 5 createMERS-8606:5# config mlt 5 add ports 2/1,3/1


NN46220-511 04.01 26 June 2009


.


MERS-8606:5# config mlt 5 add vlan 1900MERS-8606:5# config mlt 5 add vlan 10



5 Configure SMLT. The SMLT ID must be identical for eachinterswitch trunk pair:


--End--

Use the show mlt info and the show smlt info commands to verifythe status of the multilink trunks.

SMLT and VRRP configuration exampleIn cases in which the Metro Ethernet Routing Switch is providing thenext-hop gateway, and is in Virtual Router Redundancy Protocol (VRRP)mode, the Metro Ethernet Routing Switch can provide additional VRRPbenefits. In this example (see Figure 188 "Network topology for SMLT andVRRP" (page 395)), MERS8600A is acting solely as a Layer 2 switch, witha single VLAN 10 configured. The server in this example has a next-hopgateway configured for the VRRP IP.


NN46220-511 04.01 26 June 2009


.

SMLT and VRRP configuration example 395

Figure 188Network topology for SMLT and VRRP


Step Action



2 Configure VLANs:




4 Configure IP address and IST. The IP address points to thepartner IST node.



NN46220-511 04.01 26 June 2009


.


5 Configure SMLT. The SMLT ID must be identical on both nodes:


6 VRRP configuration. These commands add the VRRP virtual IPaddress of 10.10.10.1 to VLAN 10 with BackupMaster enabledso that both MERS8600B and MERS8600C can respond to ARP.

MERS-8606:5# config vlan 10 ip create 10.10.10.2/24MERS-8606:5# config vlan 10 ip vrrp 1 address10.10.10.1MERS-8606:5# config vlan 10 ip vrrp 1 backup-masterenableMERS-8606:5# config vlan 10 ip vrrp 1 holddown-timer 60MERS-8606:5# config vlan 10 ip vrrp 1 enable

--End--


Step Action



2 Configure VLANs:




4 Configure IP address and IST. The IP address points to thepartner IST node.


5 Configure SMLT. The SMLT ID must be identical on both nodes:

MERS-8606:5# config mlt 1 createMERS-8606:5# config mlt 1 smlt create smlt-id 1


NN46220-511 04.01 26 June 2009


.

SMLT and multicast configuration example 397

MERS-8606:5# config mlt 1 add vlan 10MERS-8606:5# config mlt 1 add ports 1/1

6 VRRP configuration. These commands add the VRRP virtual IPaddress of 10.10.10.1 to VLAN 10 with BackupMaster enabledso that both MERS8600B and MERS8600C can respond to ARP.

MERS-8606:5# config vlan 10 ip create 10.10.10.3/24MERS-8606:5# config vlan 10 ip vrrp 1 address10.10.10.1MERS-8606:5# config vlan 10 ip vrrp 1 backup-masterenableMERS-8606:5# config vlan 10 ip vrrp 1 holddown-timer 65MERS-8606:5# config vlan 10 ip vrrp 1 enable

--End--


Step Action

1 Configure MLT on A:

MERS-8606:5# config vlan 10 create byport 1MERS-8606:5# config mlt 1 createMERS-8606:5# config mlt 1 add ports 1/1,1/17MERS-8606:5# config mlt 1 add vlan 10

--End--

The status of VRRP can be seen using the command show ip vrrpinfo.

SMLT and multicast configuration exampleUse the following steps to configure multicast distribution over a MLTgroup:

Step Action

1 Configure multicast distribution globally:

MERS-8606:5# config sys mcast-mlt-distributionenable

2 Configure multicast distribution on each MLT group:


NN46220-511 04.01 26 June 2009


.


MERS-8606:5# config mlt 1 mcast-distributionenable

--End--

The default settings allow all sources and groups to be distributed overMLT (when enabled). Distribution can be controlled by controlling thesource/group masks:

MERS-8606:5# config sys mcast-mlt-distribution grp-mask0.0.0.255MERS-8606:5# config sys mcast-mlt-distribution src-mask0.0.255.255

Triangle SMLT and LACP configuration exampleThis configuration example shows how to build and configure a triangleSMLT network using LACP to enable the dynamic set up of SMLT linksFigure 189 "SMLT and IEEE 802.3ad configuration example" (page 399).


NN46220-511 04.01 26 June 2009


.

Triangle SMLT and LACP configuration example 399

Figure 189SMLT and IEEE 802.3ad configuration example

The following sections provide step-by-step procedures that show how toconfigure switch S1, S2, and S3 for this example.

Configuring S1

Step Action

1 Create IST VLAN 1900:

MERS-8606:5# config vlan 1900 create byport 1MERS-8606:5# config mlt 5 createMERS-8606:5# config mlt 5 add ports 1/1,2/1MERS-8606:5# config mlt 5 perform-tagging enableMERS-8606:5# config mlt 5 add vlan 1900MERS-8606:5# config vlan 1900 ip create 1.1.1.1/30MERS-8606:5# config mlt 5 ist create ip 1.1.1.2vlan-id 1900


NN46220-511 04.01 26 June 2009


.


2 Create the SMLT VLAN and add ports:

MERS-8606:5# config vlan 100 create byport 1MERS-8606:5# config vlan 100 ports add 3/1,3/2MERS-8606:5# config vlan 100 add-mlt 5

3 Configure LACP on ports:

MERS-8606:5# config ether 3/1,3/2 lacp key 10MERS-8606:5# config ether 3/1,3/2 lacp aggregationtrueMERS-8606:5# config ether 3/1,3/2 lacp enable

4 Create SMLT and configure LACP. Ensure keys match port andkeys are same for both SMLT aggregation switches:

MERS-8606:5# config mlt 10 createMERS-8606:5# config mlt 10 smlt create smlt-id 10MERS-8606:5# config mlt 10 perform-tagging enableMERS-8606:5# config mlt 10 lacp key 10MERS-8606:5# config mlt 10 lacp enableMERS-8606:5# config ether 3/1,3/2 discard-untagged-frames enable

--End--

Configuring S2

Step Action

1 Create IST VLAN 1900:

MERS-8606:5# config vlan 1900 create byport 1MERS-8606:5# config mlt 5 createMERS-8606:5# config mlt 5 add ports 1/1,2/1MERS-8606:5# config mlt 5 perform-tagging enableMERS-8606:5# config mlt 5 add vlan 1900MERS-8606:5# config vlan 1900 ip create 1.1.1.2/30MERS-8606:5# config mlt 5 ist create ip 1.1.1.1vlan-id 1900

2 Create the SMLT VLAN and add ports:

MERS-8606:5# config vlan 100 create byport 1MERS-8606:5# config vlan 100 ports add 3/1,3/2MERS-8606:5# config vlan 100 add-mlt 5


MERS-8606:5# config ether 3/1,3/2 lacp key 10MERS-8606:5# config ether 3/1,3/2 lacp aggregationtrueMERS-8606:5# config ether 3/1,3/2 lacp enable


NN46220-511 04.01 26 June 2009


.


4 Create SMLT and configure LACP. Ensure keys match: port andkeys must be the same for both SMLT aggregation switches:

MERS-8606:5# config mlt 10 createMERS-8606:5# config mlt 10 smlt create smlt-id 10MERS-8606:5# config mlt 10 perform-tagging enableMERS-8606:5# config mlt 10 lacp key 10MERS-8606:5# config mlt 10 lacp enableMERS-8606:5# config ether 3/1,3/2 discard-untagged-frames enable

--End--

Configuring S3

Step Action

1 Create VLAN 100 and add ports:

MERS-8606:5# config vlan 100 create byport 1MERS-8606:5# config vlan 100 ports add 3/1-3/4


MERS-8606:5# config ether 3/1-3/4 lacp key 20MERS-8606:5# config ether 3/1-3/4 lacp aggregationtrueMERS-8606:5# config ether 3/1-3/4 lacp enable

3 Create MLT 10 and configure LACP. Ensure keys match: portand keys must be the same for both SMLT aggregation switches:

MERS-8606:5# config mlt 10 createMERS-8606:5# config mlt 10 perform-tagging enableMERS-8606:5# config mlt 10 lacp key 10MERS-8606:5# config mlt 10 lacp enableMERS-8606:5# config ether 3/1-3/4 discard-untagged-frames enable

--End--

Single Port SMLT and LACP configuration exampleSingle Port SMLT lets you configure a split multilink trunk using a singleport. The single port split multilink trunk behaves just like an MLT-basedSMLT and can coexist with SMLTs in the same system; however, anSMLT ID can belong to either an MLT-SMLT or a single port split multilinktrunk per chassis. With Single Port SMLT, you can scale the number ofsplit multilink trunks on a switch to a maximum number of available ports.


NN46220-511 04.01 26 June 2009


.


When SMLT is enabled on a port, its key becomes default and aggregationbecomes true. The selection logic selects the default aggregator for theSMLT port. When SMLT is disabled on a port, aggregation becomes false.This example highlights the steps in configuring Single Port SMLT usingLACP to create the LAG. Although a Metro Ethernet Routing Switch 8600is used for the SMLT client, any LACP enabled device can be used.

Figure 190 "Network topology" (page 402) shows the network topology forthis configuration example.

Figure 190Network topology


Step Action

1 To create the interswitch trunk, enter the following commands:

MERS-8606:5# conf vlan 1900 create byport 1MERS-8606:5# conf mlt 5 createMERS-8606:5# conf mlt 5 add ports 1/1,2/1MERS-8606:5# conf mlt 5 perform-tagging enableMERS-8606:5# conf mlt 5 add vlan 1900MERS-8606:5# conf vlan 1900 ip create 1.1.1.1/30MERS-8606:5# conf mlt 5 ist create ip 1.1.1.2vlan-id 1900

2 To create the user VLAN, enter the following commands:


NN46220-511 04.01 26 June 2009


.


MERS-8606:5# conf vlan 10 create byport 1MERS-8606:5# conf vlan 10 ports add 1/10

3 To create the single port split multilink trunk, enter the followingcommand:

MERS-8606:5# conf ether 1/10 smlt 1 create

4 To enable LACP on each port, enter the following command. Nokey is required. The default key is used:

MERS-8606:5# conf ether 1/10 lacp enable

--End--


Step Action

1 To create the interswitch trunk, enter the following commands:

MERS-8606:5# conf vlan 1900 create byport 1MERS-8606:5# conf mlt 5 createMERS-8606:5# conf mlt 5 add ports 1/1,2/1MERS-8606:5# conf mlt 5 perform-tagging enableMERS-8606:5# conf mlt 5 add vlan 1900MERS-8606:5# conf vlan 1900 ip create 1.1.1.2/30MERS-8606:5# conf mlt 5 ist create ip 1.1.1.1vlan-id 1900

2 To create the user VLAN, enter the following commands:

MERS-8606:5# conf vlan 10 create byport 1MERS-8606:5# conf vlan 10 ports add 1/10

3 To create the single port split multilink trunk, enter the followingcommand:

MERS-8606:5# conf ether 1/10 smlt 1 create


MERS-8606:5# conf ether 1/10 lacp enable

--End--


Step Action

1 To create the multilink trunk, enter the following commands:


NN46220-511 04.01 26 June 2009


.


MERS-8606:5# conf mlt 10 createMERS-8606:5# conf mlt 10 lacp key 10MERS-8606:5# conf mlt 10 lacp enable

2 To create the user VLAN and add ports, enter the followingcommands:

MERS-8606:5# conf vlan 10 create byport 1MERS-8606:5# conf vlan 10 ports add 1/1-1/2

3 To configure LACP on the ports, enter the following commands:

MERS-8606:5# conf ether 1/1-1/2 lacp key 10MERS-8606:5# conf ether 1/1-1/2 lacp aggregationtrue


MERS-8606:5# conf ether 1/1-1/2 lacp enable

--End--

LACP-based MLT for UNI configuration exampleThe following section is an example of configuring an LACP-based MLTfor UNI.

Step Action

1 Enable tagging and configure 1/1 and 1/2 as tagged ports.

MERS-8606:5# config ethernet 1/1 perform-taggingenableMERS-8606:5# config ethernet 1/1 interface-typeuniMERS-8606:5# config ethernet 1/2 perform-taggingenableMERS-8606:5# config ethernet 1/2 interface-typeuni

2 Add ports to the VLAN.

MERS-8606:5# config vlan 100 ports add 1/1,1/2

3 Configure LACP on ports.

MERS-8606:5# config ethernet 1/1 lacp key 2MERS-8606:5# config ethernet 1/1 lacp aggregationtrueMERS-8606:5# config ethernet 1/1 lacp enableMERS-8606:5# config ethernet 1/2 lacp key 2MERS-8606:5# config ethernet 1/2 lacp aggregation


NN46220-511 04.01 26 June 2009


.

LACP-based MLT for NNI configuration example 405

trueMERS-8606:5# config ethernet 1/2 lacp enable

4 Create MLT 2 and configure LACP.

MERS-8606:5# config mlt 2 createMERS-8606:5# config mlt 2 interface-type uniMERS-8606:5# config mlt 2 perform-tagging enableMERS-8606:5# config mlt 2 add vlan 100MERS-8606:5# config mlt 2 lacp key 2MERS-8606:5# config mlt 2 lacp enable

5 Enable LACP globally.

MERS-8606:5# config lacp enable

--End--

LACP-based MLT for NNI configuration exampleThe following section is an example of configuring an LACP-based MLTfor NNI.

Step Action

1 Enable tagging and configure 1/1 and 1/2 as tagged ports:

MERS-8606:5# config ethernet 1/1 perform-taggingenableMERS-8606:5# config ethernet 1/1 interface-typenormalMERS-8606:5# config ethernet 1/2 perform-taggingenableMERS-8606:5# config ethernet 1/2 interface-typenormal

2 Add ports to the VLAN.

MERS-8606:5# config vlan 100 ports add 1/1,1/2

3 Configure LACP on ports.

MERS-8606:5# config ethernet 1/1 lacp key 2MERS-8606:5# config ethernet 1/1 lacp aggregationtrueMERS-8606:5# config ethernet 1/1 lacp enableMERS-8606:5# config ethernet 1/2 lacp key 2MERS-8606:5# config ethernet 1/2 lacp aggregationtrueMERS-8606:5# config ethernet 1/2 lacp enable

4 Create MLT 2 and configure LACP.


NN46220-511 04.01 26 June 2009


.


MERS-8606:5# config mlt 2 createMERS-8606:5# config mlt 2 interface-type normalMERS-8606:5# config mlt 2 perform-tagging enableMERS-8606:5# config mlt 2 add vlan 100MERS-8606:5#config mlt 2 lacp key 2MERS-8606:5# config mlt 2 lacp enable

5 Enable LACP globally.

MERS-8606:5# config lacp enable

--End--

Multiple Spanning Tree Protocol configuration exampleThe following section gives an example using MSTP. The topology is givenin Figure 191 "Multiple spanning tree topology" (page 406). This networkhas the following parameters:

Figure 191Multiple spanning tree topology


NN46220-511 04.01 26 June 2009


.

Multiple Spanning Tree Protocol configuration example 407

• Switches B1 and B2 are in multiple spanning tree region 2.

• B1 is configured so that it becomes the CIST root; it has the lowestCIST priority of 4096.

• B2 is configured so that it becomes the CIST backup; it has the nexthighest CIST priority of 8192.

• There are two MSTI instances; MSTI 1 for VLAN 3 and MSTI 2 forVLAN 4.

• B1 GbE interface 2/2 is configured with a MSTI 2 priority of 16, whileB2 GbE interface 4/1 is configured with a MSTI 1 priority of 16. Thisresults in VLAN load balancing.

• Switches B3, B4, B5, and B6 are in multiple spanning tree region 1.

• B3 is configured so that it becomes the CIST regional root; it has aCIST priority of 12288. B4 becomes the backup CIST regional root;it has a priority of 16384.

• There are two MSTI instances; MSTI 1 for VLAN 3, and MSTI 2 forVLAN 4.

• B4 is configured so that it is the MSTI root for VLAN 3 and the backupMSTI root for VLAN 4. Configure the MSTI priority for MSTI 1 to 4096,and the MSTI priority for MSTI 2 to 8192.

• B3 is configured so that it is the MSTI root for VLAN 4 and the backupMSTI root for VLAN 3. Configure the MSTI priority for MSTI 1 to 8192,and the MSTI priority for MSTI 2 to 4096.

Configuring MERS8600 B1

Step Action

1 Set the switch to use MSTP mode. This requires you to savethe configuration and boot the switch. Enter the followingcommands:

MERS8600-B1:6# config bootconfig flagsspanning-tree-mode mstpMERS8600-B1:6# save bootconfigMERS8600-B1:6# boot -y

2 Configure the MSTP region:

MERS8600-B1:6# config mstp region config-id-sel 2MERS8600-B1:6# config mstp region name region2MERS8600-B1:6# config mstp region revision 1

3 Configure GbE ports 2/1, 2/2, 2/4, and 2/4 as tagged ports:


NN46220-511 04.01 26 June 2009


.


MERS8600-B1:6# config ethernet 2/1,2/2,2/4,2/5perform-tagging enable

4 Add VLAN 3:

MERS8600-B1:6# config vlan 3 create byport-mstp 1MERS8600-B1:6# config vlan 3 ports add 2/1,2/2,2/4,2/5,1/15

5 Add VLAN 4:


6 Change the MSTP CIST bridge priority:

MERS8600-B1:6# config mstp cist priority 4096

7 Configure the MSTP 2 priority:

MERS8600-B1:6# config ethernet 2/2 mstp msti 2priority 16

8 Configure ports 1/15 and 1/16 as a MSTP edge ports:

MERS8600-B1:6# config ethernet 1/15,1/16 mstp cistedge-port true

--End--


Step Action

1 Set the switch to use MSTP mode. This requires you to savethe configuration and boot the switch. Enter the followingcommands:

MERS8600-B2:6# config bootconfig flagsspanning-tree-mode mstpMERS8600-B2:6# save bootconfigMERS8600-B2:6# boot -y

2 Configure MSTP region:

MERS8600-B2:6# config mstp region config-id-sel 2MERS8600-B2:6# config mstp region name region2MERS8600-B2:6# config mstp region revision 1

3 Configure GbE ports 4/1, 4/2, 4/4, and 4/5 as tagged ports:

MERS8600-B2:6# config ethernet 4/1,4/2,4/4,4/5perform-tagging enable

4 Add VLAN 3:


NN46220-511 04.01 26 June 2009


.



5 Add VLAN 4:


6 Change the MSTP CIST bridge priority:

MERS8600-B2:6# config mstp cist priority 8192

7 Configure the MSTP 1 priority:

MERS8600-B2:6# config ethernet 4/1 mstp msti 1priority 16

8 Configure ports as MSTP edge ports:

MERS8600-B2:6# config ethernet 3/15,3/16 mstp cistedge-port true

--End--


Step Action

1 Enable the MSTP mode:

MERS1624G-B3:4# config stp version mstp

2 Change MSTP bridge priority:

MERS1624G-B3:4# config stp instance_id 0 priority12288

3 Add VLAN 3:

MERS1624G-B3:4# create vlan 3 vid 3 type portMERS1624G-B3:4# config vlan 3 add untagged 10MERS1624G-B3:4# config vlan 3 add tagged 1,3,5,7

4 Add VLAN 4:


5 Configure ports 1 and 3 for 1 Gbps full duplex to be compatiblewith the ES GbE interfaces:

MERS1624G-B3:4# config ports 1,3 speed 1000_full

6 Configure the MSTP region and revision:


NN46220-511 04.01 26 June 2009


.


MERS1624G-B3:4# config stp region name region1MERS1624G-B3:4# config stp region mstconfigidsel 1MERS1624G-B3:4# config stp region revision 1

7 Add MSTI 1, change the MSTI priority, and add VLAN 3:

MERS1624G-B3:4# create stp instance_id 1MERS1624G-B3:4# config stp instance_id 2 priority8192MERS1624G-B3:4# config stp_vlan instance_id 1 add 3



--End--


Step Action

1 Enable MSTP mode:

MERS1624G-B4:4# config stp version mstp

2 Change MSTP bridge priority:

MERS1624G-B4:4# config stp instance_id 0 priority12288

3 Add VLAN 3:


4 Add VLAN 4:


5 Configure ports 1 and 3 for 1 Gbps full duplex to be compatiblewith the ES GbE interfaces:

MERS1624G-B4:4# config ports 1,3 speed 1000_full

6 Configure the MSTP region and version:

MERS1624G-B4:4# config stp region name region1MERS1624G-B4:4# config stp region mstconfigidsel 1MERS1624G-B4:4# config stp region revision 1



NN46220-511 04.01 26 June 2009


.





--End--

Configuring ES 470 B5

Step Action

1 Change spanning tree operation mode to MSTP and reboot theswitch:

ES470_48(config)# spanning-tree op-mode mstpES470_48(config)# bootReboot the unit(s) (y/n) ? y

2 Add tagging:

ES470_48(config)# vlan ports 47,48 tagging tagall

3 Add VLAN 3 and members:

ES470_48(config)# vlan create 3 type portES470_48(config)# vlan members add 3 15,47,48

4 Remove VLAN port member from the default VLAN:

ES470_48(config)# vlan members remove 1 15,47,48

5 Add VLAN 4 and port members:


6 Remove VLAN port members from the default VLAN:

ES470_48(config)# vlan members remove 1 16


ES470_48(config)# spanning-tree mstp regionconfig-id-sel 1 region-name region1 region-version1

8 Add MSTP MSTI 1 and add VLAN 3:


NN46220-511 04.01 26 June 2009


.


ES470_48(config)# spanning-tree mstp msti 1ES470_48(config)# spanning-tree mstp msti 1add-vlan 3



If an error message appears stating that you cannot modifysettings and nontagged ports cannot span multiple STPGs, thenensure that all appropriate ports have tagging enabled. In thisexample, this applies to ports 47 and 48.

10 Configure ports 6 and 7 as MSTP edge ports:

ES470_48(config)# interface fastEthernet 15,16ES470_48(config-if)# spanning-tree mstp edge-porttrue

--End--

Configuring ES 470 B6

Step Action

1 Change spanning tree operation mode to MSTP and reboot theswitch:

ES470_48(config)# spanning-tree op-mode mstpES470_48(config)# boot Reboot the unit(s) (y/n) ? y

2 Add tagging:

ES470_48(config)# vlan ports 47,48 tagging tagall




ES470_48(config)# vlan members remove 1 15,47,48




ES470_48(config)# vlan members remove 1 16



NN46220-511 04.01 26 June 2009


.

Dual home UNI and MSTP configuration example 413

ES470_48(config)# spanning-tree mstp regionconfig-id-sel 1 region-name region1 region-version1





10 Configure ports 6 and 7 as MSTP edge ports:

ES470_48(config)# interface fastEthernet 15,16ES470_48(config-if)# spanning-tree mstp edge-porttrue

--End--

Dual home UNI and MSTP configuration exampleThe following section gives a sample configuration file to show how dualhome UNI and MSTP commands work together.

Step Action

1 Enter the following commands to configure the maintenancedomain (MD).

MERS-8606:5# config cfm md "nmd" create index 2maint-level 2MERS-8606:5# config cfm md "pmd" create index 1maint-level 5config cfm md "vmd" create index 3 maint-level 3

2 Enter the following commands to configure the maintenanceassociation (MA).

MERS-8606:5# config cfm md "nmd" ma "nma" createindex 2 ccm-interval 1000 auto-detect enableMERS-8606:5# config cfm md "pmd" ma "pma" createindex 1 auto-detect enableconfig cfm md "vmd" ma "vma1" create index 1ccm-interval 1000 ccm-type unicastMERS-8606:5# config cfm md "vmd" ma "vma3" createindex 1 ccm-interval 1000 ccm-type unicast


NN46220-511 04.01 26 June 2009


.


3 Enter the following commands to configure the maintenanceendpoint.

MERS-8606:5# config cfm md "nmd" ma "nma" mep 5create state enableMERS-8606:5# config cfm md "pmd" ma "pma" mep 25create state enableconfig cfm md "vmd" ma "vma1" mep 3 create stateenableMERS-8606:5# config cfm md "vmd" ma "vma3" mep 3create state enable

4 Enter the following commands to configure the remotemaintenance endpoint.

MERS-8606:5# config cfm md "nmd" ma "nma" rmep 2create remote-mac 00:1a:8f:06:d3:dfMERS-8606:5# config cfm md "vmd" ma "vma1" rmep 1create remote-mac 00:1a:8f:06:d0:80config cfm md "vmd" ma "vma3" rmep 35 createremote-mac 00:1a:8f:06:d0:a0

5 Enter the following commands to configure the maintenanceintermediate point.

MERS-8606:5# cfm md "iclientmd" mip 500 create

6 Enter the following commands to perform phase 1 of portconfiguration.

MERS-8606:5# config ethernet 2/1 perform-taggingenableMERS-8606:5# config ethernet 2/1 interface-typeuniconfig ethernet 2/1 qnq-ethertype 0x88a8MERS-8606:5# config ethernet 2/3 perform-tagging enableMERS-8606:5# config ethernet 2/3 interface-typeuniMERS-8606:5# config ethernet 2/3 qnq-ethertype0x88a8MERS-8606:5# config ethernet 2/5 perform-taggingenableMERS-8606:5# config ethernet 2/5 interface-typeuniMERS-8606:5# config ethernet 2/5 qnq-ethertype0x88a8MERS-8606:5# config ethernet 2/6 perform-taggingenableMERS-8606:5# config ethernet 2/6 interface-typeuniMERS-8606:5# config ethernet 2/6 qnq-ethertype0x88a8MERS-8606:5# config ethernet 2/20 perform-tagging


NN46220-511 04.01 26 June 2009


.


enableMERS-8606:5# config ethernet 2/20 interface-typenormalMERS-8606:5# config ethernet 2/30 perform-taggingenableMERS-8606:5# config ethernet 2/30 interface-typenormal

7 Enter the following commands to configure MLT.

MERS-8606:5# mlt 16 createMERS-8606:5# mlt 16 add ports 2/20,2/30mlt 16 perform-tagging enable

8

ATTENTIONUNI configurationThe RCT port or MLT is not explicitly configured, as it in dual homering. It is derived from the rct-vid.

Enter the following commands to configure MSTP dual homeUNI.

MERS-8606:5# config dh-uni 1 create mac-offset 53MERS-8606:5# config dh-uni 1 name “Lab link 1”config dh-uni 1 rct-hello-interval 1MERS-8606:5#config dh-uni 1 port 2/1MERS-8606:5# config dh-uni 1 partner-dh-uni-mac00:15:e8:a4:60:81MERS-8606:5# config dh-uni 2 create mac-offset 2MERS-8606:5# config dh-uni 2 createMERS-8606:5# config dh-uni 2 name “Lab link 2”MERS-8606:5# config dh-uni 2 rct-hello-interval 1MERS-8606:5# config dh-uni 2 port 2/3MERS-8606:5# config dh-uni 2 partner-dh-uni-mac00:15:e8:a4:60:82

9 Enter the following command to configure B-VLAN.

MERS-8606:5# config vlan 100 create byport-mstprstp 1

10 Enter the following commands to configure RCT-VLAN.

MERS-8606:5# config vlan 1000 create byport-mstprstp 2config vlan 1000 add-mlt 16MERS-8606:5# config vlan1000 add-nodal-mep nmd.nma.5

11 Enter the following commands to configure VLAN MEP VLAN.

MERS-8606:5# config vlan 11 create byport-mstprstp1


NN46220-511 04.01 26 June 2009


.


MERS-8606:5# config vlan 11 ports remove 2/2-2/30member portmemberMERS-8606:5# config vlan 11 ports add 2/1 memberportmemberMERS-8606:5# config vlan 11 cfm-port 2/1 add-mep“vmd.vma.1”MERS-8606:5# config vlan 13 create byport-mstprstp1MERS-8606:5# config vlan 13 ports remove2/1-2/2,2/4-2/30 member portmemberMERS-8606:5# config vlan 13 ports add 2/3 memberportmemberMERS-8606:5# config vlan 13 cfm-port 2/3 add-mep“vmd.vma.3”

12 If using CFM for port down detection into access, enter thefollowing commands to configure the port.

MERS-8606:5# config ethernet 2/1 cfm-vid 100MERS-8606:5# config ethernet 2/1 add-mep“pmd.pma.25”MERS-8606:5# config ethernet 2/1 add-cfm-control-mep pmd.pma.25MERS-8606:5# config ethernet 2/1 mstp cistforceportstate disableMERS-8606:5# config ethernet 2/3 mstp cistforceportstate disable

13 Enter the following commands to configure dual home UNI,phase 2.

MERS-8606:5# config dh-uni 1 add-controller-mepsnmd.nma.1.1MERS-8606:5# config dh-uni 1 add-controller-mepsvmd.vma1.3.1MERS-8606:5# config dh-uni 1 rct-vid 1000MERS-8606:5# config dh-uni 1 state enableMERS-8606:5# config dh-uni 2 add-controller-mepsnmd.nma.1.1MERS-8606:5# config dh-uni 2 add-controller-mepsvmd.vma3.3MERS-8606:5# config dh-uni 2 rct-vid 1000MERS-8606:5# config dh-uni 2 state enable

14 Enter the following commands to configure MSTP.

MERS-8606:5# config access-mstp 1 createMERS-8606:5# config access-mstp 1 bridge-mac00:15:e8:a4:60:81MERS-8606:5# config access-mstp 1 priority 0MERS-8606:5# config access-mstp 1 forward-delay1500


NN46220-511 04.01 26 June 2009


.


MERS-8606:5# config access-mstp 1 max-age 2000MERS-8606:5# config access-mstp 1 msti 1 createMERS-8606:5# config access-mstp 1 msti 1 priority 0MERS-8606:5# config access-mstp 1 msti 1 add-vlan100-199,2000MERS-8606:5# config access-mstp 1 msti 2 createMERS-8606:5# config access-mstp 1 msti 2 priority 0MERS-8606:5# config access-mstp 1 msti 2 add-vlan200-299MERS-8606:5# config access-mstp 1 msti 3 priority 0MERS-8606:5# config access-mstp 1 msti 3 add-vlan300-399MERS-8606:5# config access-mstp 1 msti 4 priority 0MERS-8606:5# config access-mstp 1 msti 4 add-vlan400-499MERS-8606:5# config access-mstp 1 name “Labnetwork”MERS-8606:5# config access-mstp 1 revision-level 2MERS-8606:5# config access-mstp 1 config-id-sel 0MERS-8606:5# config access-mstp 1 dh-uni 1 addMERS-8606:5# config access-mstp 1 dh-uni 1add-master-msti 1MERS-8606:5# config access-mstp 1 dh-uni 1add-backup-msti 2-3MERS-8606:5# config access-mstp 1 dh-uni 2 addMERS-8606:5# config access-mstp 1 dh-uni 2add-backup-msti 4

15 Enter the following commands to I-SID.

ATTENTIONYou can add/remove B-VLAN to/from dual home UNI when theendpoint is enabled/disabled.

Sub-endpoint 0 is supported; “dh-uni 1 create” is the same as “dh-uni1.0 create”.

MERS-8606:5# config i-sid 1 createMERS-8606:5# config i-sid 1 b-vlan 100MERS-8606:5# config i-sid 1 mac-table-size 100MERS-8606:5# config i-sid 1 end-point dh-uni 1createMERS-8606:5# config i-sid 1 end-point dh-uni 1service-type qnq1MERS-8606:5# config i-sid 1 end-point dh-uni 1ingress-policer disableMERS-8606:5# config i-sid 1 end-point dh-uni 1s-vlan 110MERS-8606:5# config i-sid 1 end-point dh-uni 1state enableMERS-8606:5# config i-sid 1 end-point dh-uni 1cfm-vid 200 add-client-mep "cmd.cma.3" direction


NN46220-511 04.01 26 June 2009


.


upMERS-8606:5# config i-sid 1 end-point dh-uni 1cfm-vid 200 add-client-mip "oaismd.1"MERS-8606:5# config i-sid 1 end-point dh-uni 1 cfm-vid 200 add-client-mep "oclientmd.oclientma.1"direction down

--End--


NN46220-511 04.01 26 June 2009


.

419.

AppendixTap and OctaPID assignment (Release3.x feature set)

The switch fabric in the Metro Ethernet Routing Switch 8600 module hasnine switching taps, one for each of the eight I/O slots (1 to 4 and 7 to 10),and one for the CPU slots (5 and 6). Taps 0 to 7 map to the eight I/O slotsand can support up to eight OctaPIDs. Each OctaPID can support up toeight ports.

In the Metro Ethernet Routing Switch 8600, a physical port number is 10bits long and has the following format:

bits 96: Tap number (015)

bits 53: OctaPID number (07)

bits 20: MAC port number (07)

The tap number bits and the OctaPID number bits combined (bits 93) areusually referred to as the OctaPID ID.

Table 63 "Available module types and OctapPID ID assignments" (page420) lists the module types that are currently available, along withthe associated OctaPID ID assignments for each module.


NN46220-511 04.01 26 June 2009


.

420 Tap and OctaPID assignment (Release 3.x feature set)

Table 63Available module types and OctapPID ID assignments

Module type Port type OctaPID IDassignment

1000BASE-SX Table 64 "8608GBE/8608GBM/8608GTE/8608GTM/8608SXE modules"(page 421)

1000BASE-LX

1000BASE-ZX

8608GBE and 8608GBM Modules

1000BASE-XD

8608GTE and 8608GTM Modules 1000BASE-T Table 64 "8608GBE/8608GBM/8608GTE/8608GTM/8608SXE modules"(page 421)

8608SXE Module 1000BASE-SX Table 64 "8608GBE/8608GBM/8608GTE/8608GTM/8608SXE modules"(page 421)

8616SXE Module 1000BASE-SX Table 65 "8616SXEmodule" (page 421)

8624FXE Module 100BASE-FX Table 66 "8624FXEmodule" (page 422)

10BASE-T/100BASE-TX Table 67 "8632TXEand 8632TZM modules"(page 422)

1000BASE-SX

1000BASE-LX

1000BASE-ZX

8632TXE and 8632TXM Modules

1000BASE-XD

8648TXE and 8648TXM Modules 10/100 Mb/s Table 68 "8648TXE and8648TXM modules"(page 422)

OC-3c MDA Table 69 "8672ATMEand 8672ATMMmodules" (page 423)

OC-12c MDA

8672ATME and 8672ATMM Modules

DS3

8681XLR Module 10GBASE-LR Table 70 "8681XLRmodule" (page 423)


NN46220-511 04.01 26 June 2009


.


Table 63Available module types and OctapPID ID assignments (cont’d.)

Module type Port type OctaPID IDassignment

8681XLW Module 10GBASE-LW Table 71 "8681XLWmodule" (page 424)

OC-3c MDA Table 72 "8683POSMmodule" (page 424)

8683POSM Module

OC-12c MDA

Table 64 "8608GBE/8608GBM/8608GTE/8608GTM/8608SXE modules"(page 421) describes the OctaPID ID and port assignments for the8608GBE, 8608GBM, 8608GTE, 8608GTM, and 8608SXE modules.

Table 648608GBE/8608GBM/8608GTE/8608GTM/8608SXE modules

OctaPID ID assignment Port assignment

OctaPID ID: 0 Port 1








Table 65 "8616SXE module" (page 421) describes the OctaPID ID andport assignments for the 8616SXE Module.

Table 658616SXE module


OctaPID ID: 0 Ports 1 and 2









NN46220-511 04.01 26 June 2009


.


Table 66 "8624FXE module" (page 422) describes the OctaPID ID andport assignments for the 8624FXE Module.

Table 668624FXE module


OctaPID ID: 0 Ports 1 through 8



Table 67 "8632TXE and 8632TZM modules" (page 422) describesthe OctaPID ID and port assignments for the 8632TXE and 8632TXMmodules.

Table 678632TXE and 8632TZM modules






OctaPID ID: 6 Port 33 (GBIC port)

OctaPID ID: 7 Port 34 (GBIC port)

Table 68 "8648TXE and 8648TXM modules" (page 422) describesthe OctaPID ID and port assignments for the 8648TXE and 8648TXMModules.

Table 688648TXE and 8648TXM modules









NN46220-511 04.01 26 June 2009


.


Table 69 "8672ATME and 8672ATMM modules" (page 423) describesthe OctaPID ID and port assignments for the 8672ATME and 8672ATMMModules.

Table 698672ATME and 8672ATMM modules


OctaPID ID: 0 • Ports 1 through 4 (with OC-3c MDA)

• Port 1 (with OC-12c MDA)

• Ports 1 through 2 (with DS-3 MDA)

OctaPID ID: 1 • Ports 5 through 8 (with OC-3c MDA)


• Ports 5 through 6 (with DS-3 MDA)

OctaPID ID: 2 Not used

Table 70 "8681XLR module" (page 423) describes the OctaPID ID andport assignments for the 8681XLR Module.

Table 708681XLR module


OctaPID ID: 0

OctaPID ID: 1

OctaPID ID: 2

OctaPID ID: 3

OctaPID ID: 4

OctaPID ID: 5

OctaPID ID: 6

OctaPID ID: 7

Port 1

Table 71 "8681XLW module" (page 424) describes the OctaPID ID andport assignments for the 8681XLW Module.


NN46220-511 04.01 26 June 2009


.


Table 718681XLW module


OctaPID ID: 0

OctaPID ID: 1

OctaPID ID: 2

OctaPID ID: 3

OctaPID ID: 4

OctaPID ID: 5

OctaPID ID: 6

OctaPID ID: 7

Port 1

Table 72 "8683POSM module" (page 424) describes the OctaPID ID andport assignments for the 8683POSM Module.

Table 728683POSM module


OctaPID ID: 0 • Ports 1 and 2 (with OC-3c MDA)







NN46220-511 04.01 26 June 2009


.

425.

Glossaryaggregation switch

A switch that aggregates multiple user access switches andprovides core connections.

boundary portA bridge port that attaches a multiple spanning tree bridge to aLAN that is not in the same region.

Common and Internal Spanning Tree (CIST)The single spanning tree calculated by STP together with thelogical continuation of that connectivity through MST bridgesand regions, calculated by MSTP to ensure that all LANs in thebridged LAN are simply and fully connected.

Common Spanning Tree (CST)The single spanning tree calculated by STP and MSTP to connectmultiple spanning tree regions.

Internal spanning tree (IST)An internal spanning tree that operates in a given multiplespanning tree region. Within a multiple spanning tree region,multiple spanning instances can be configured. Instance 0 withina region is known as the Internal Spanning Tree (IST).

Interswitch trunkA parallel point to point link that connects two aggregationswitches together. The two aggregation switches use this channelto share information so that they can operate as a single logicalswitch. There can be only one interswitch trunk per SMLTaggregation switch.


NN46220-511 04.01 26 June 2009


.

426 Glossary

Interswitch Trunking (IST)A method of link aggregation that allows two aggregation switchesto connect. The two aggregation switches use this channel toshare information so that they can operate as a single logicalswitch. There can be only one interswitch trunk per SMLTaggregation switch.

MultiLink Trunking (MLT)MultiLink trunking is a method of link aggregation that allowsmultiple Ethernet trunks to be aggregated together to providea single logical trunk. A multilink trunk provides the combinedbandwidth of the multiple links, as well as the physical layerprotection against the failure of any single link.

Multiple Spanning Tree Instance (MSTI)One of a number of spanning trees calculated by MSTP withina multiple spanning tree region. The instance provides a fullyconnected active topology for frames classified as belonging to aVLAN that is mapped to the MSTI by the MST configuration tableused by the multiple spanning tree bridges of the MST region.

MST bridgeA bridge capable of supporting the CST, and one or more MSTIs,and of selectively mapping frames classified in any given VLAN tothe CST or a given MSTI.

MST regionA set of LANs and MST bridges, physically connected via ports onthose MST bridges, where each LAN CIST designated bridge isan MST bridge. Each port is either the designated port on one ofthe LANs, or else a non-designated port of an MST bridge that isconnected to one of the LANs. The port MCID matches the MCIDof the designated bridge of that LAN.

peer IP addressThe IP address of the neighbor IST switch VLAN that is chosenfor configuring the interswitch trunk. Note that the peer IP addressis the IP address of the IST VLAN on the other aggregationswitch. You need only configure one VLAN with an IP address forthe IST protocol to work. All other VLANs on the interswitch trunkdo not require an IP address if you choose not to have VLANrouting enabled.


NN46220-511 04.01 26 June 2009


.

427

Single Port SMLTA multilink trunk where one or both ends are split between twoaggregation switches; however only one port can be configured oneach aggregation switch per SMLT ID.

Single Spanning Tree (SST) bridgeA bridge capable of supporting only a single spanning tree: theCST. The SST may be supported by the Spanning Tree Protocol(STP) defined in IEEE 802.1d-1998.

SMLT aggregation switchesThe two switches that share an IST link.

Typically, one or more switches that connect to multiple wiringcloset switches, edge switches or CPE devices, usually within asingle building.

SMLT clientA switch located at the edge of the network, such as in a wiringcloset or CPE. An SMLT client switch must be able to perform linkaggregation (such as with MLT or some other compatible method)but does not require any SMLT intelligence.

SMLT IDThe identification number used to specify the correspondingpair of SMLT links. This number is identified between the twoaggregation switches and must be paired on each aggregationswitch.

SMLT setTwo SMLT aggregation switches and their directly connectedSMLT clients.

SMLT squareA pair of SMLT aggregation switches connected as SMLT clientsto another pair of SMLT aggregation switches.

SMLT triangleA configuration where an SMLT client and the two aggregationswitches form a triangle.

Spanning treeA simply and fully connected active topology formed from thearbitrary physical topology of connected bridged LAN componentsby relaying frames through selected bridge ports. The STP


NN46220-511 04.01 26 June 2009


.

428 Glossary

parameters and states are used and exchanged to facilitate thecalculation of that active topology and to control the bridge relayfunction.

Spanning tree groupA collection of ports in one spanning tree instance.

Split multilink trunkA multilink trunk where one or both ends are split between twoaggregation switches, thus forming what is typically referred to asan SMLT triangle or SMLT square.

user access switchA switch located at the edge of the network. End stations typicallyconnect directly to a user access switch.


NN46220-511 04.01 26 June 2009


.

Copyright 2010 Ciena® Corporation

Ciena Metro Ethernet Routing Switch 8600

Documentation Roadmap

Copyright 2010 Ciena CorporationAll Rights Reserved

Printed in Canada, India, and the United States of AmericaRelease: 5.2Publication: NN46220-101 Document status: StandardDocument revision: 03.01Document release date: 21 November 2008

To provide feedback or to report a problem in this document, e-mail us at [email protected]

www.ciena.comLEGAL NOTICE

While the information in this document is believed to be accurate and reliable, except as otherwise expressly agreed to in writing NORTEL PROVIDES THIS DOCUMENT "AS IS" WITHOUT WARRANTY OR CONDITION OF ANY KIND, EITHER EXPRESS OR IMPLIED. The information and/or products described in this document are subject to change with out notice.

Any usage in this document of Nortel, Nortel Networks, the Nortel logo, and Globemark now refer to Ciena Corporation.

All other trademarks are the property of the irrespective owners.

Documents

NN46220 511 (MERS8600 R6.0 Configuration VLANs Spanning Tree and Link Aggregation) Rev04.01