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

MERS 8600® Metro Ethernet Routing Switch 8600

Configuration — VLANs, Spanning Tree, and Link Aggregation Software Release 6.0

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

LEGAL NOTICES THIS DOCUMENT CONTAINS CONFIDENTIAL AND TRADE SECRET INFORMATION OF CIENA CORPORATION AND ITS RECEIPT OR POSSESSION DOES NOT CONVEY ANY RIGHTS TO REPRODUCE OR DISCLOSE ITS CONTENTS, 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 CIENA CORPORATION IS STRICTLY FORBIDDEN. EVERY EFFORT HAS BEEN MADE TO ENSURE THAT THE INFORMATION IN THIS DOCUMENT IS COMPLETE AND ACCURATE AT THE TIME OF PRINTING; HOWEVER, THE INFORMATION CONTAINED IN THIS DOCUMENT IS 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 other countries. It may not be reproduced or distributed in any form by any means, altered in any fashion, or stored in a data base 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 for unauthorized use or access. Contacting Ciena 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]

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

877-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]

Sales and General Information

Training and Documentation

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

MERS 8600 Metro Ethernet Routing Switch 8600 Copyright Ciena® Corporation

NN46220-511 - Revision 04.01 June 26, 2009

IMPORTANT: PLEASE READ THIS LICENSE AGREEMENT ("AGREEMENT") CAREFULLY BEFORE INSTALLING OR USING CIENA CORPORATION ("Ciena") SOFTWARE, HARDWARE OR DOCUMENTATION (COLLECTIVELY, THE "EQUIPMENT"). BY INSTALLING OR USING THE EQUIPMENT, YOU ACKNOWLEDGE THAT YOU HAVE READ THIS AGREEMENT 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, Ciena grants to you, as end user, a non-exclusive license to use the Ciena software (the "Software") in object code form solely in connection with, and as embedded within, the Equipment,. You shall have the right to use the Software solely for your own internal use and benefit. You may make one copy of the Software and documentation solely for backup and archival purpose, however you must reproduce and affix all copyright and other proprietary rights notices that appear 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 expressly authorized herein; (iii) modify the Software nor provide any third person the means to do the same; (iv) create derivative works, translate, disassemble, recompile, reverse engineer or attempt to obtain the source code of the Software in any way; or (v) alter, destroy, or otherwise remove any proprietary notices or labels on or embedded within the Software or documentation. You acknowledge that this license is subject to Section 365 of the U.S. Bankruptcy Code and requires Ciena's consent to any assignment related to a bankruptcy proceeding. Sole title to the Software and documentation, to any derivative works, and to any associated patents and copyrights, remains with Ciena or its licensors. Ciena reserves to itself and its licensors all rights in the Software and documentation not expressly granted to you. You shall preserve intact any notice of copyright, trademark, logo, legend or other notice of ownership from any original or copies of the Software or documentation. 2. Audit: Upon Ciena's reasonable request, but not more frequently than annually without reasonable cause, you shall permit Ciena to audit the use of the Software at such times as may be mutually agreed upon to ensure compliance 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 Information to any third party without prior written consent of Ciena, will use it only for purposes for which it was disclosed, use your best efforts to prevent and protect the contents of the Software from unauthorized disclosure or use, and must treat it with the same degree of care as you do your own similar information, but with no less than reasonable care. You acknowledge that the design and structure of the Software constitute trade secrets and/or copyrighted materials of Ciena 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 and 52-227-19 or DFARS Section 52.227-7013(C)(1)(ii), as applicable. The Equipment and any accompanying technical data (collectively "Materials") are commercial within the meaning of applicable Federal acquisition regulations. These Materials were developed fully at private expense. U.S. Government use of the Materials is restricted by this Agreement, and all other U.S. Government use is prohibited. In accordance with FAR 12.212 and DFAR Supplement 227.7202, software delivered to you is commercial computer software and the use of that software is further restricted by this Agreement. 5. Term of License. This license is effective until terminated. Customer may terminate this license at any time by giving written notice to Ciena [or] and destroying or erasing all copies of Software including any documentation. Ciena may terminate this Agreement and your license to the Software immediately by giving you written notice of termination in the event that either (i) you breach any term or condition of this Agreement or (ii) you are wound up other than voluntarily for the purposes of amalgamation or reorganization, have a receiver appointed or enter into liquidation or bankruptcy or analogous process in your home country. Termination shall be without prejudice to any other rights or remedies Ciena may have. In the event of any termination you will have no right to keep or use the Software or any copy of the Software for any purpose and you shall destroy and erase all copies of such Software in its possession or control, and forward written certification to Ciena that all such copies of Software have been destroyed or erased.

MERS 8600 Metro Ethernet Routing Switch 8600 Copyright Ciena® Corporation

NN46220-511 - Revision 04.01 June 26, 2009

6. Compliance with laws. You agree to comply with all applicable laws, including all import regulations, and to obtain all required licenses and permits related to installation and use of Equipment. Software, including technical data, is subject to U.S. export control laws, including the U.S. Export Administration Act and its associated regulations, and may be subject to export or import regulations in other countries. Customer agrees to comply strictly with all such regulations 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 AMOUNTS PAID BY YOU FOR THE SOFTWARE. THIS LIMITATION APPLIES TO ALL CAUSES OF ACTION, INCLUDING WITHOUT LIMITATION BREACH OF CONTRACT, BREACH OF WARRANTY, NEGLIGENCE, STRICT LIABILITY, MISREPRESENTATION AND OTHER TORTS. THE LIMITATIONS OF LIABILITY DESCRIBED IN THIS SECTION ALSO APPLY TO ANY THIRD-PARTY SUPPLIER OF Ciena. NEITHER Ciena NOR ANY OF ITS THIRD-PARTY SUPPLIERS 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 INFORMED OF 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 rights in the Software, but otherwise neither this Agreement nor any rights hereunder may be assigned nor duties delegated by either party, and any attempt to do so will be void. This Agreement shall be governed by the laws of the State of Maryland (without regard to the conflict of laws provisions) and shall be enforceable in the courts of Maryland. The U.N. Convention on Contracts for the International Sale of Goods shall not apply hereto. This Agreement constitutes the complete and exclusive statement of agreement between the parties relating to the license for the Software and supersedes all proposals, communications, purchase orders, and prior agreements, verbal or written, between the parties. If any portion hereof is found to be void or unenforceable, the remaining provisions shall remain in full force and effect.

MERS 8600 Metro Ethernet Routing Switch 8600 Copyright Ciena® Corporation

NN46220-511 - Revision 04.01 June 26, 2009

3

.

Contents Software license New in this release

9 13

Features 14 Co-existence of PLSB with LACP 14 Other changes 16 clear ports mstpstats command 16 PLSB-MSTI 16

Introduction

17

Acronyms 18

Layer 2 operational concepts VLANs 21 Port-based VLANs 22 Policy-based VLANs 24 Multihoming support 30 Port types 30 VLAN tagging and port types 31 VLAN virtual router interfaces 35 IP routing and VLANs 35 Prevention of IP spoofing within a VLAN 35 VLAN Loop Detection 36 Multiple MAC Registration Protocol 37 Spanning tree protocols 37 Spanning Tree Protocol 37 Spanning Tree Protocol with PLSB 42 Spanning Tree Protocol with PBT 43 Multiple Spanning Tree Protocol 43 Link aggregation (MLT, SMLT, LACP) 47 MultiLink Trunking (MLT) 48 IEEE 802.3ad-based link aggregation 60 Split MultiLink Trunking (SMLT) 69 Simple Loop Prevention Protocol 90 SLPP and UNI Ports 92

Nortel Metro Ethernet Routing Switch 8600 Configuration — VLANs, Spanning Tree, and Link Aggregation NN46220-511 04.01 26 June 2009 Copyright © 2007-2009 Nortel Networks. All Rights Reserved.

21

4 SLPP general notes 93 Considerations and limitations 94 VLAN implementation on the Metro Ethernet Routing Switch 8600 VLAN rules 95 MultiLink trunking and VLAN scalability 96

94

Configuring VLANs using Device Manager

99

Displaying defined VLANs 99 Configuring port-based VLANs 101 Creating a port-based VLAN 102 Configuring an IP address for a VLAN 106 Configuring policy-based VLANs 107 Creating a source IP subnet-based VLAN 108 Creating a protocol-based VLAN 109 Configuring user-defined protocol-based VLANs 111 Creating a source MAC address-based VLAN 114 Managing a VLAN 119 Changing VLAN port membership 120 Configuring advanced VLAN features 120 Configuring VLAN forwarding 123 Configuring a VLAN to accept tagged or untagged frames 125 Configuring Untagging Default VLAN on a Tagged Port 128 Configuring MAC address auto-learning on a VLAN 129 Modifying auto-learned MAC addresses 131 Configuring VLAN Loop Detection 133 Configuring directed broadcast on a VLAN 135 Managing VLAN bridging 137 Configuring the forwarding database timeout 137 Viewing the forwarding database for a specific VLAN 138 Clearing learned MAC addresses from the forwarding database 140 Configuring static forwarding 142 MAC-layer bridge packet filtering 145 Configuring static multicast 146 Configuring a MAC-layer bridge filter 146 Configuring the Global MAC filter 150 Configuring Enhanced Operation mode 151

Configuring spanning tree using Device Manager Choosing the spanning tree mode 155 Configuring Spanning Tree Protocol 156 Creating a STG 157 Editing an STG 161 Adding ports to an STG 161 Viewing the STG status 162 Viewing STG ports 165 Nortel Metro Ethernet Routing Switch 8600 Configuration — VLANs, Spanning Tree, and Link Aggregation NN46220-511 04.01 26 June 2009 Copyright © 2007-2009 Nortel Networks. All Rights Reserved.

155

5 Enabling STP on a port 167 Deleting an STG 168 Configuring STG topology change detection 168 Configuring Multiple Spanning Tree Protocol 169 Configuring MSTP globally 169 Configuring CIST ports for MSTP 172 Viewing statistics for the CIST ports 175 Configuring MSTI bridges for MSTP 177 Configuring MSTI ports for MSTP 178 Viewing MSTI port statistics 180 Viewing MSTI port notification 181

Configuring link aggregation using Device Manager

183

Configuring link aggregation 183 Configuring LACP globally 184 Adding a MultiLink/LACP trunk 185 Adding ports to a multilink trunk 192 Viewing multilink trunk interface statistics 193 Viewing multilink trunk Ethernet error statistics 195 Managing LACP information 198 Configuring a port for LACP 201 Viewing LACP statistics 206 Configuring Split Multilink Trunking 208 Adding a MLT-based SMLT 208 Viewing MLT-based SMLTs 210 Adding ports to an MLT-based SMLT 211 Configuring an IST multilink trunk 212 Editing an IST 213 Viewing IST statistics 214 Configuring a single port split multilink trunk 216 Viewing Single Port SMLTs 218 Deleting a Single Port SMLT 219 Configuring Simple Loop Prevention Protocol 220 Configuring SLPP globally 220 Configuring the SLPP by VLAN 222 Configuring the SLPP by port 223

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

227

228

Setting the sVLAN switch level using Device Manager

229

Configuring Simple Loop Prevention Protocol with Device Manager

231

SLPP, Ports tab fields 232

Nortel Metro Ethernet Routing Switch 8600 Configuration — VLANs, Spanning Tree, and Link Aggregation NN46220-511 04.01 26 June 2009 Copyright © 2007-2009 Nortel Networks. All Rights Reserved.

6

Configuring and managing VLANs using the CLI

233

Roadmap of VLAN commands 233 Configuring and managing a VLAN 237 Creating a VLAN 238 Performing general VLAN operations 243 Configuring VLAN parameters in the forwarding database 245 Limiting MAC learning 250 Adding or removing VLAN ports 251 Adding or removing VLAN source MAC addresses 252 Configuring Untagging Default VLAN on a Tagged Port 252 Configuring Enhanced Operation mode 253 Configuring VLAN Loop Detection 254 Configuring spoof detection for a VLAN 258 Using the VLAN show commands 258 Displaying general VLAN information 259 Displaying forwarding database information 270 Displaying forwarding database filters 271 Displaying database status, MAC address, and QoS levels 272 Displaying additional parameters 273 Displaying ARP configurations 274 Displaying VLAN information 275 Displaying brouter port information 276 Displaying IGMP switch operation information 277 Displaying VLAN routing (IP) configuration 278 Displaying port member status 278 Displaying source MAC addresses 280 Using the show ports commands for VLANs 280 Displaying port tagging information 281 Displaying all port VLAN information 282 Using the VLAN IP commands 283 Assigning an IP address to a VLAN 284

Configuring STGs using the CLI Roadmap of spanning tree commands 287 Configuring the spanning tree protocol mode 290 Configuring Spanning Tree Protocol 290 Configuring spanning tree group parameters 291 Configuring STG port parameters 293 Configuring topology change detection 295 Using the show STG commands 297 Configuring Multiple Spanning Tree Protocol 306 Configuring Multiple Spanning Tree Protocol 307 Configuring MSTP region 308

Nortel Metro Ethernet Routing Switch 8600 Configuration — VLANs, Spanning Tree, and Link Aggregation NN46220-511 04.01 26 June 2009 Copyright © 2007-2009 Nortel Networks. All Rights Reserved.

287

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

Configuring link aggregation using the CLI

321

Roadmap of link aggregation commands 321 Configuring link aggregation 325 Link aggregation commands 326 Adding ports to a link aggregation group 327 Removing ports from a link aggregation group 327 Global LACP commands 328 Aggregator configuration commands 329 Port configuration commands 331 LACP show commands 333 Creating a split multilink trunk from an existing multilink trunk 338 Creating an interswitch trunk 339 Creating a single port split multilink trunk 343 Configuring SMLT-on-Single-CPU 344 Using the MLT and SMLT show commands 344 Displaying all multilink trunk information 345 Displaying information about collision errors 348 Displaying information about Ethernet errors 349 Displaying multilink trunk status 350 Displaying interswitch trunk status 350 Displaying split multilink trunk status 351 Displaying all ports configured for single port split multilink trunk 352 Displaying a port configured for Single Port SMLT 353 Displaying MLT statistics 353 Troubleshooting SMLT problems 354 Troubleshooting IST problems 354 Troubleshooting problems with a single user 357 Global MAC filtering 358

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

Nortel Metro Ethernet Routing Switch 8600 Configuration — VLANs, Spanning Tree, and Link Aggregation NN46220-511 04.01 26 June 2009 Copyright © 2007-2009 Nortel Networks. All Rights Reserved.

361

8

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

367 371

CLI configuration examples

375

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

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

Nortel Metro Ethernet Routing Switch 8600 Configuration — VLANs, Spanning Tree, and Link Aggregation NN46220-511 04.01 26 June 2009 Copyright © 2007-2009 Nortel Networks. All Rights Reserved.

419

9

.

Software license This section contains the Nortel Networks software license.

Nortel Networks Inc. software license agreement This Software License Agreement ("License Agreement") is between you, the end-user ("Customer") and Nortel Networks Corporation and its subsidiaries and affiliates ("Nortel Networks"). PLEASE READ THE FOLLOWING CAREFULLY. YOU MUST ACCEPT THESE LICENSE TERMS IN ORDER TO DOWNLOAD AND/OR USE THE SOFTWARE. USE OF THE SOFTWARE CONSTITUTES YOUR ACCEPTANCE OF THIS LICENSE AGREEMENT. If you do not accept these terms and conditions, return the Software, unused and in the original shipping container, within 30 days of purchase to obtain a credit for the full purchase price. "Software" is owned or licensed by Nortel Networks, its parent or one of its 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) and related licensed materials including all whole or partial copies. Nortel Networks grants you a license to use the Software only in the country where you acquired the Software. You obtain no rights other than those granted to you under this License Agreement. You are responsible for the selection of the Software and for the installation of, use of, and results obtained from the Software. 1. Licensed Use of Software. Nortel Networks grants Customer a nonexclusive license to use a copy of the Software on only one machine at 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 with designated hardware or Customer furnished equipment ("CFE"), Customer is granted a nonexclusive license to use Software only on such hardware or CFE, as applicable. Software contains trade secrets and Customer agrees to treat Software as confidential information using the same care and discretion Customer uses with its own similar information that it does not wish to disclose, publish or disseminate. Customer will ensure that anyone who uses the Software does so only in compliance with the terms Nortel Metro Ethernet Routing Switch 8600 Configuration — VLANs, Spanning Tree, and Link Aggregation NN46220-511 04.01 26 June 2009 Copyright © 2007-2009 Nortel Networks. All Rights Reserved.

10 Software license

of this Agreement. Customer shall not a) use, copy, modify, transfer or distribute the Software except as expressly authorized; b) reverse assemble, reverse compile, reverse engineer or otherwise translate the Software; c) create derivative works or modifications unless expressly authorized; or d) sublicense, rent or lease the Software. Licensors of intellectual property to Nortel Networks are beneficiaries of this provision. Upon termination or breach of the license by Customer or in the event designated hardware or CFE is no longer in use, Customer will promptly return the Software to Nortel Networks or certify its destruction. Nortel Networks may audit by remote polling or other reasonable means to determine Customer’s Software activation or usage levels. If suppliers of third party software included in Software require Nortel Networks to include additional or different terms, Customer agrees to abide by such terms provided by Nortel Networks with respect to such third party software. 2. Warranty. Except as may be otherwise expressly agreed to in writing between Nortel Networks and Customer, Software is provided "AS IS" without any warranties (conditions) of any kind. NORTEL NETWORKS DISCLAIMS ALL WARRANTIES (CONDITIONS) FOR THE SOFTWARE, EITHER EXPRESS OR IMPLIED, INCLUDING, BUT NOT LIMITED TO THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE AND ANY WARRANTY OF NON-INFRINGEMENT. Nortel Networks is not obligated to provide support of any kind for the Software. Some jurisdictions do not allow exclusion of implied warranties, and, in such event, the above exclusions may not apply. 3. Limitation of Remedies. IN NO EVENT SHALL NORTEL NETWORKS OR ITS AGENTS OR SUPPLIERS BE LIABLE FOR ANY OF THE FOLLOWING: a) DAMAGES BASED ON ANY THIRD PARTY CLAIM; b) LOSS OF, OR DAMAGE TO, CUSTOMER’S RECORDS, FILES OR DATA; OR c) DIRECT, INDIRECT, SPECIAL, INCIDENTAL, PUNITIVE, OR CONSEQUENTIAL DAMAGES (INCLUDING LOST PROFITS OR SAVINGS), WHETHER IN CONTRACT, TORT OR OTHERWISE (INCLUDING NEGLIGENCE) ARISING OUT OF YOUR USE OF THE SOFTWARE, EVEN IF NORTEL NETWORKS, ITS AGENTS OR SUPPLIERS HAVE BEEN ADVISED OF THEIR POSSIBILITY. The forgoing limitations of remedies also apply to any developer and/or supplier of the Software. Such developer and/or supplier is an intended beneficiary of this Section. Some jurisdictions do not allow these limitations or exclusions and, in such event, they may not apply. 4.

General

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

Nortel Metro Ethernet Routing Switch 8600 Configuration — VLANs, Spanning Tree, and Link Aggregation NN46220-511 04.01 26 June 2009 Copyright © 2007-2009 Nortel Networks. All Rights Reserved.

Nortel Networks Inc. software license agreement

11

software documentation and, in the event Software is licensed for or on behalf of the United States Government, the respective rights to the software and software documentation are governed by Nortel Networks standard commercial license in accordance with U.S. Federal Regulations at 48 C.F.R. Sections 12.212 (for non-DoD entities) and 48 C.F.R. 227.7202 (for DoD entities).

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

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

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

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

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

Nortel Metro Ethernet Routing Switch 8600 Configuration — VLANs, Spanning Tree, and Link Aggregation NN46220-511 04.01 26 June 2009 Copyright © 2007-2009 Nortel Networks. All Rights Reserved.

12 Software license

Nortel Metro Ethernet Routing Switch 8600 Configuration — VLANs, Spanning Tree, and Link Aggregation NN46220-511 04.01 26 June 2009 Copyright © 2007-2009 Nortel Networks. All Rights Reserved.

13

.

New in this release The following sections detail what’s new in Nortel Metro Ethernet Routing Switch 8600 Configuration — VLANs, Spanning Tree, and Link Aggregation (NN46220-511) for release 6.0.

• •

“Features” (page 14) “Other changes” (page 16)

Nortel Metro Ethernet Routing Switch 8600 Configuration — VLANs, Spanning Tree, and Link Aggregation NN46220-511 04.01 26 June 2009 Copyright © 2007-2009 Nortel Networks. All Rights Reserved.

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 enhancements The DFO feature includes Link Aggregation Control Protocol (LACP) enhancements. The behavior of LACP-enabled MLTs is changed so that you 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 RC modules. The current LACP behavior is not changed; the ports can still be added and removed dynamically. If communication of the Link Aggregation Control Protocol data unit (LACPDU) on the port with peer node does not agree, traffic is not transmitted and accepted on this port. In this condition, the port is in an STG-disabled state. For more information, see “LACP and MLT” (page 64) and “LACP keys” (page 66).

SLPP enhancements You can specify the UNI ports added under the SLPP global configuration and view the total number of SLPP packets received on the port. This release includes additional enhancements to show packet rx counts and clear commands for the packet rx. For more information, see “Simple Loop Prevention Protocol” (page 90), “Configuring SLPP globally” (page 220), and “Configuring the SLPP by port” (page 223).

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

Nortel Metro Ethernet Routing Switch 8600 Configuration — VLANs, Spanning Tree, and Link Aggregation NN46220-511 04.01 26 June 2009 Copyright © 2007-2009 Nortel Networks. All Rights Reserved.

Co-existence of PLSB with LACP

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

Nortel Metro Ethernet Routing Switch 8600 Configuration — VLANs, Spanning Tree, and Link Aggregation NN46220-511 04.01 26 June 2009 Copyright © 2007-2009 Nortel Networks. All Rights Reserved.

15

16 New in this release

Other changes See the following section for details and locations of the changes made to this document.

clear ports mstpstats command • Added "clear ports mstpstats" command information.

See “Roadmap of spanning tree commands” (page 287) and Attention Box that follows the 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).

• •

Updated the screen capture in “Configuring MSTP globally” (page 169).

PLSB-MSTI Updated Table 27 "MSTP, Globals fields" (page 171).

Nortel Metro Ethernet Routing Switch 8600 Configuration — VLANs, Spanning Tree, and Link Aggregation NN46220-511 04.01 26 June 2009 Copyright © 2007-2009 Nortel Networks. All Rights Reserved.

17

.

Introduction This guide describes how to configure VLANs, spanning tree, and link aggregation on the Nortel Metro Ethernet Routing Switch 8600 (MERS 8600).

Prerequisites This guide is intended for network administrators with the following background:

• • • • •

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 8600 Fundamentals (NN46220-100). Ensure that you are running the latest version of the Metro Ethernet Routing Switch 8600 Software Release 6.0 and Device Manager software. For information about upgrading the Metro Ethernet Routing Switch 8600 Software Release 6.0 and Device Manager, see Nortel Metro Ethernet 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) Nortel Metro Ethernet Routing Switch 8600 Configuration — VLANs, Spanning Tree, and Link Aggregation NN46220-511 04.01 26 June 2009 Copyright © 2007-2009 Nortel Networks. All Rights Reserved.

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)

Acronyms This 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

Nortel Metro Ethernet Routing Switch 8600 Configuration — VLANs, Spanning Tree, and Link Aggregation NN46220-511 04.01 26 June 2009 Copyright © 2007-2009 Nortel Networks. All Rights Reserved.

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

Nortel Metro Ethernet Routing Switch 8600 Configuration — VLANs, Spanning Tree, and Link Aggregation NN46220-511 04.01 26 June 2009 Copyright © 2007-2009 Nortel Networks. All Rights Reserved.

20 Introduction

VLACP

Virtual Link Aggregation Control Protocol

VLAN

virtual local area network

XOR

exclusive OR

Nortel Metro Ethernet Routing Switch 8600 Configuration — VLANs, Spanning Tree, and Link Aggregation NN46220-511 04.01 26 June 2009 Copyright © 2007-2009 Nortel Networks. All Rights Reserved.

21

.

Layer 2 operational concepts This section describes Layer 2 operational concepts and features supported on your Metro Ethernet Routing Switch. See “Device Manager configuration examples” (page 367) and “CLI configuration examples” (page 375) for configuration examples, including command line interface (CLI) commands, for concepts described in this section. 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)

VLANs Using a virtual LAN (VLAN), you can divide your LAN into smaller groups without interfering with the physical network. VLAN practical applications include the following:

• •

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

•

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

You can create VLANs, or workgroups, for specific types of network traffic.

By dividing the network into separate VLANs, you can create separate broadcast domains. This arrangement conserves bandwidth, especially in networks supporting broadcast and multicast applications that flood the network with traffic. A VLAN workgroup can include members from a number of dispersed physical segments on the network, improving traffic flow between them.

Nortel Metro Ethernet Routing Switch 8600 Configuration — VLANs, Spanning Tree, and Link Aggregation NN46220-511 04.01 26 June 2009 Copyright © 2007-2009 Nortel Networks. All Rights Reserved.

22 Layer 2 operational concepts

The Metro Ethernet Routing Switch 8600 Software Release 6.0 performs the Layer 2 switching functions necessary to transmit information within VLANs, as well as the Layer 3 routing functions necessary for VLANs to communicate with one another. A VLAN can be defined for a single switch or it can span multiple switches. A port can be a member of multiple VLANs. A port-based VLAN is the only type of VLAN provisioning supported for Provider 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 using Device Manager” (page 99) and “Configuring and managing VLANs using the 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 VLANs A port-based VLAN is a VLAN in which the ports are explicitly configured to be in the VLAN. When creating a port-based VLAN on a switch, you assign a VLAN identification number (VLAN ID) and specify the ports that belong to the VLAN. The VLAN ID is used to coordinate VLANs across multiple switches. A port-based VLAN is the only type of VLAN provisioning supported for Provider Backbone Bridging (PBB) services running on B-VLANs, PBT VLANs, or PLSB VLANs. Port-based VLANs are known as B-VLANs, PBT VLANs, or PLSB VLANs.

Nortel Metro Ethernet Routing Switch 8600 Configuration — VLANs, Spanning Tree, and Link Aggregation NN46220-511 04.01 26 June 2009 Copyright © 2007-2009 Nortel Networks. All Rights Reserved.

VLANs

23

A port interface can be set to either UNI, NNI or silent. Silent is the default and, as a security feature, does not allow any VLANs or UNI to be assigned to the port until it is changed to UNI or NNI. When a port is set to UNI, the Encapsulated Virtual Private Network (EVPN) concept applies; the port is tied to an end-point, which is tied to an I-SID, which is either tied to a B-VLAN, PLSB-VLAN or PBT-VLAN, depending on the transport method selected for that I-SID. The B-VLAN, PLSB-VLAN and PBT-VLAN can only be port-based VLANs. When a port is set to NNI, it can be assigned to any VLAN type. NNI trunk ports must be assigned as needed. Rings must be added to all B-VLANs that the UNIs are assigned to after the ring ID is created and ports 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 and the encapsulation is removed to form a Virtual Private Network (VPN). When encapsulated, EVPN traffic is transported over normal ports through the network. The example in Figure 1 "Port-based VLAN" (page 24) shows two port-based VLANs: one for the marketing department, and one for the sales department. Ports are assigned to each port-based VLAN. A change in the sales area can move the sales representative at port 3/1 (the first port in the input/output (I/O) module in chassis slot 3) to the marketing department without moving cables. With a port-based VLAN, you only need to indicate in Device Manager or the CLI that port 3/1 in the sales VLAN now is a member of the marketing VLAN.

Nortel Metro Ethernet Routing Switch 8600 Configuration — VLANs, Spanning Tree, and Link Aggregation NN46220-511 04.01 26 June 2009 Copyright © 2007-2009 Nortel Networks. All Rights Reserved.

24 Layer 2 operational concepts Figure 1 Port-based VLAN

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

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

This section includes the following topics:

• • • • •

“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 types In a policy-based VLAN, a port can be designated as always a member or never a member of the VLAN describing the port membership types. In addition, you can designate a port as a potential member of the VLAN on the Metro Ethernet Routing Switch 8600. When a port is designated as a potential member of the VLAN, and the incoming traffic matches

Nortel Metro Ethernet Routing Switch 8600 Configuration — VLANs, Spanning Tree, and Link Aggregation NN46220-511 04.01 26 June 2009 Copyright © 2007-2009 Nortel Networks. All Rights Reserved.

VLANs

25

the policy, the port is dynamically added to the VLAN. Potential member ports that join the VLAN are removed, timed out from the VLAN when the timeout (aging time) period of that VLAN expires. Port membership in a VLAN is determined by the traffic coming into the port. Nortel recommends that you designate at least some ports as always a member of the VLAN. If a server or router connects to a port, then designate that port as always a member of a VLAN. If a server connects to a port that is only a potential member and the server sends very little traffic, a client fails to reach the server if the server port has timed out of the VLAN. A port can belong to one port-based VLAN and many policy-based VLANs. Table 1 "Port membership types for policy-based VLANs" (page 25) describes port membership types for policy-based VLANs. Table 1 Port membership types for policy-based VLANs Membership type

Description

Static

Static members are always active members of the VLAN after they are configured as belonging to that VLAN. This membership type is used in policy-based and port-based VLANs.

(always a member)

Not allowed to join

•

In policy-based VLANs, the tagged ports are usually configured as static members.

•

In port-based VLANs, all ports are always static members.

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

(never a member)

Table 2 "Supported VLAN types for NNI and Layer 2 ports" (page 25) lists supported policy-based VLANs. Table 2 Supported 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

Nortel Metro Ethernet Routing Switch 8600 Configuration — VLANs, Spanning Tree, and Link Aggregation NN46220-511 04.01 26 June 2009 Copyright © 2007-2009 Nortel Networks. All Rights Reserved.

26 Layer 2 operational concepts

Protocol-based VLANs Protocol-based VLANs are an effective way to segment your network into broadcast domains according to the network protocols in use. Traffic generated by any network protocol—Appletalk, Point-to-Point Protocol over Ethernet (PPPoE)—can be automatically confined to its own VLAN. All ports within a protocol-based VLAN must be in the same port-based VLAN. However, the same port within a port-based VLAN can belong to multiple protocol-based VLANs. Port tagging is not required for a port to be a member of multiple protocol-based VLANs. The Metro Ethernet Routing Switch 8600 supports the following protocol-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 a remote site through a device, such as a modem, so that multiple users can share a common line connection to the Internet. PPPoE combines the Point-to-Point Protocol (PPP), commonly used in dial-up connections, with the Ethernet protocol, which supports multiple users in a local area network (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:

Nortel Metro Ethernet Routing Switch 8600 Configuration — VLANs, Spanning Tree, and Link Aggregation NN46220-511 04.01 26 June 2009 Copyright © 2007-2009 Nortel Networks. All Rights Reserved.

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 a protocol-based VLAN that transports PPPoE traffic to the Internet Service Provider (ISP) network. The traffic to the ISP is bridged. IP traffic can also be routed to the LAN using port-based VLANs, IP protocol-based VLANs, or IP subnet-based VLANs. Figure 2 PPPoE and IP configuration

User-defined protocol-based VLANs You can create user-defined protocol-based VLANs to support networks with non-standard protocols. For user-defined protocol-based VLANs, you can specify the Protocol Identifier (PID) for the VLAN. Frames that match the 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

Nortel Metro Ethernet Routing Switch 8600 Configuration — VLANs, Spanning Tree, and Link Aggregation NN46220-511 04.01 26 June 2009 Copyright © 2007-2009 Nortel Networks. All Rights Reserved.

28 Layer 2 operational concepts

Table 3 "PIDs that cannot be used for user-defined protocol-based VLANs" (page 28) lists reserved, predefined policy-based PIDs that cannot be used as user-defined PIDs. Table 3 PIDs 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 VLANs As with all policy-based VLANs, using source media access control (MAC) address VLANs allows Metro Ethernet Routing Switch 8600 modules to associate frames with a VLAN based on the frame content. With source MAC-based VLANs, a frame is associated with a VLAN if the source MAC address is one of the MAC addresses explicitly associated with the VLAN. To create a source MAC-based VLAN, you add the MAC address to a list of MAC addresses that constitutes the VLAN. However, because it is necessary to explicitly associate MAC addresses with a source MAC-based VLAN, the administrative overhead can be quite high. Use source MAC-based VLANs when you want to enforce a MAC level security scheme to differentiate groups of users. For example, in a university environment, the students are part of a student VLAN with certain services and access privileges, and the faculty are part of a source MAC-based VLAN with faculty services and access privileges. Therefore, Nortel Metro Ethernet Routing Switch 8600 Configuration — VLANs, Spanning Tree, and Link Aggregation NN46220-511 04.01 26 June 2009 Copyright © 2007-2009 Nortel Networks. All Rights Reserved.

VLANs

29

a student and a faculty member can plug into the same port, but have access to a different range of services. To provide the correct services throughout the campus, the source MAC-based VLAN must be defined on 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 the spanning tree group (STG) are automatically made potential members of the VLAN by default. The source MAC VLAN must have static port members on either the access or trunk switch for source MAC VLANS to explicitly associate the MAC address with the source MAC VLAN. If the static port members are not set, then any source MAC address gains access to the network.

IP subnet-based VLANs Metro Ethernet Routing Switch 8600 modules support policy-based VLANs based on IP subnets. You can assign access ports to multiple subnet-based VLANs. A frame’s membership in a subnet-based VLAN is based on the IP source address associated with a mask. Subnet-based VLANs 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 transit network. Figure 3 "Incorrect use of an IP subnet-based VLAN" (page 30) shows two examples of the incorrect use of IP subnet-based VLANs that result in traffic loss. In the IP unicast routing example, the host on 172.100.10.2 sends 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 does not arrive at the router in switch 1. Switch 1 will not assign this frame to IP subnet-based VLAN 2 because the IP address of the traffic source does not match the IP subnet assigned to VLAN 2. If the access link in VLAN 2 which connects switches 1 and 2 is a tagged link, the traffic is associated with the VLAN tag, not the IP address, and is forwarded correctly to switch 1. In the IP multicast routing example, the multicast stream is on an access link that is part of IP subnet-based VLAN 2. If the source IP address in the multicast data packets received on the access port is not within the subnet of VLAN 2 (a likely scenario), the multicast stream will not reach the multicast router (MR).

Nortel Metro Ethernet Routing Switch 8600 Configuration — VLANs, Spanning Tree, and Link Aggregation NN46220-511 04.01 26 June 2009 Copyright © 2007-2009 Nortel Networks. All Rights Reserved.

30 Layer 2 operational concepts Figure 3 Incorrect use of an IP subnet-based VLAN

Multihoming support Using the multihoming feature, the Metro Ethernet Routing Switch 8600 can support clients or servers that have multiple IPs addresses associated with a single MAC address. Multihomed hosts can be connected to port-based VLANs. All other types of VLANs are not supported. The IP addresses associated with a single MAC address on a host must be in the same IP subnet. Multihomed hosts with up to 16 IP addresses for each MAC address are supported on the Metro Ethernet Routing Switch 8600.

Port types A port interface type can be set to either UNI, Normal or Silent. Silent is the default and, as a security feature, does not allow any VLANs or UNI to be 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. The port must be tied to an end-point to transport traffic. This is a port that normally faces the customer equipment.

Nortel Metro Ethernet Routing Switch 8600 Configuration — VLANs, Spanning Tree, and Link Aggregation NN46220-511 04.01 26 June 2009 Copyright © 2007-2009 Nortel Networks. All Rights Reserved.

VLANs

31

When a port interface type is set to normal, it can be used for regular L2 traffic (no EVPN) and use any VLAN type, or it can be used as an NNI interface that has B-VLAN, PLSB-VLAN or PBT-VLAN, which can only be port-based VLANs. This is a port that normally faces the service provider network. When a switch boots with the factory default configuration, the ports do not belong to a VLAN (they belong to NULL VLAN) and the port type is set to "silent" (it will be part of NULL VLAN and will not process BPDU and topology packets). The interface-type value must be set to "UNI" for the port before configuring a UNI, I-SID endpoint, MLT endpoint, and CUST-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 the port using the following command. config ethernetinterface-type

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

VLAN tagging and port types The Metro Ethernet Routing Switch 8600 supports the IEEE 802.1Q specification for tagging frames and coordinating VLANs across multiple switches. VLAN tagging is required for NNI and UNI ports when using the ports for EVPN services. Port types can be of three types: UNI, normal, and silent. By default, port type is untagged and silent to prevent traffic from forwarding. Figure 4 "VLAN tag insertion" (page 32) shows how an additional four octet (tag) header is inserted in a frame after the source address and before the frame type. The tag contains the VLAN ID associated with the frame.

Nortel Metro Ethernet Routing Switch 8600 Configuration — VLANs, Spanning Tree, and Link Aggregation NN46220-511 04.01 26 June 2009 Copyright © 2007-2009 Nortel Networks. All Rights Reserved.

32 Layer 2 operational concepts Figure 4 VLAN tag insertion

802.1Q tagged ports Tagging a frame adds four octets to a frame, making it bigger than the traditional maximum frame size. These frames are sometimes referred to as baby giant frames. If a device does not support IEEE 802.1Q tagging, it can have problems interpreting tagged frames and receiving baby giant frames. On the Metro Ethernet Routing Switch 8600, whether or not tagged frames are 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 on that port. When you enable tagging on an untagged port, the previous port configuration of VLANs, STGs, and multilink trunking (MLT) is lost. In addition, the port resets and runs Spanning Tree Protocol. This process breaks connectivity while the protocol proceeds through the normal blocking 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 multiple VLANs to other IEEE 802.1Q-compliant devices.

Nortel Metro Ethernet Routing Switch 8600 Configuration — VLANs, Spanning Tree, and Link Aggregation NN46220-511 04.01 26 June 2009 Copyright © 2007-2009 Nortel Networks. All Rights Reserved.

VLANs

33

If you disable tagging on a port, it does not send tagged frames. A non-tagged port connects an Metro Ethernet Routing Switch to devices that do not support IEEE 802.1Q tagging. If a tagged frame is forwarded to a port with tagging set to false, the Metro Ethernet Routing Switch removes the tag from the frame before sending it to the port.

Treatment of tagged and untagged frames The Metro Ethernet Routing Switch 8600 associates a frame with a VLAN based on the data content of the frame and the configuration of the destination port. The treatment of the frame depends on whether it is tagged or untagged. If a tagged frame is received on a tagged port with a VLAN ID specified in the tag, the Metro Ethernet Routing Switch 8600 directs it to that VLAN if the VLAN is present. For tagged frames received on an untagged port, you can configure that port to either discard the frame or accept it. The discarding of tagged frames on an untagged port is not applicable for the port-based VLAN. If you choose not to discard tagged frames, the Metro Ethernet Routing Switch 8600 sends the frame to the VLAN identified in the frame tag. For untagged frames, VLAN membership is implied from the content of the frame itself. For untagged frames received on a tagged port, you can configure the port to either discard or accept the frame. If you configure a tagged port to accept untagged frames, the port must be assigned to a port-based VLAN in spanning tree group 1 (STG1). The frame is forwarded based on the VLAN on which the frame is received, and on the forwarding options available for that VLAN. The Metro Ethernet Routing Switch 8600 tries to associate untagged frames with a VLAN. 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 feature This feature provides the ability to connect both an IP phone and a PC to a single port of a Metro Ethernet Routing Switch 8600. The default VLAN feature is only applicable to NNI ports when the NNI is not associated with any PBB or PBT interfaces; it is not applicable to UNI ports on PBB and PBT. Most IP phones ship with an embedded three port switch, and traffic coming from the phone is generally tagged (VLAN ID configured statically or remotely). However, the traffic originating from a PC is usually untagged traffic and must be separated from the IP phone traffic. This separation ensures that broadcast traffic from the PC does not impact voice quality. Nortel Metro Ethernet Routing Switch 8600 Configuration — VLANs, Spanning Tree, and Link Aggregation NN46220-511 04.01 26 June 2009 Copyright © 2007-2009 Nortel Networks. All Rights Reserved.

34 Layer 2 operational concepts

In the case of the Metro Ethernet Routing Switch, when an IP phone is attached to an untagged port and configured into an IP subnet-based VLAN, it can fail to register with a remote Internet Telephony Gateway (or equivalent device) dependent on the netmask of the destination IP address (Call Server subnet). Figure 5 Network with IP phone and PC

In Figure 5 "Network with IP phone and PC" (page 34), IP phones and PCs coexist on the same port due to the use of an embedded IP Phone Layer 2 switch. In this scenario, the port is configured to be untagged and is a member of two IP subnet-based VLANs. In this network configuration, under certain conditions, packets from the IP phone are not routed and therefore are unable to reach their designated Call Server to register. The Untagging Default VLAN on a Tagged Port feature separates untagged packets originating from a PC from the tagged packets originating from the IP phone. You can configure the switch to send untagged packets for the default VLAN on a tagged port. After you configure this option, all the packets sent on a tagged port for the default VLAN are untagged packets. When a port belongs to multiple VLANs, and the port is removed from the current default VLAN, the lowest VLAN by index (among the VLANs of 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 Loop Detection” (page 254). To configure this feature using Device Manager, see “Configuring Untagging Default VLAN on a Tagged Port” (page 128).

Nortel Metro Ethernet Routing Switch 8600 Configuration — VLANs, Spanning Tree, and Link Aggregation NN46220-511 04.01 26 June 2009 Copyright © 2007-2009 Nortel Networks. All Rights Reserved.

VLANs

35

VLAN virtual router interfaces Virtual router interfaces correspond to routing on a virtual port that is associated with a VLAN. This type of routing is the routing of IP traffic to and from a VLAN. Because a given port can belong to multiple VLANs (some of which are configured for routing on the switch and some of which are not), there is no longer a one-to-one correspondence between the physical port and the router interface. For VLAN routing, the router interface for the VLAN is called a virtual router interface because the IP address is assigned to an interface on the routing entity in the switch. This initial interface has a one-to-one correspondence with a VLAN on any given switch. VLAN routing is applicable to customer IP_VLAN UNIs and is used to manage devices attached to UNIs or rings, including Ethernet Services Units within the ring. It is not applicable to PBB and PBT B-VLANs.

IP routing and VLANs Metro Ethernet Routing Switch 8600 modules support IP routing on port-based VLANs only. IP routing can be applied to a UNI for IP management. IP routing is not supported on VLANs based on other protocols, including user-defined protocol-based VLANs.

Prevention of IP spoofing within a VLAN You can prevent VLAN logical IP spoofing by blocking the external use of the switch IP address. A configurable option is provided, on a per-port basis, which detects a duplicate IP address (that is, an address that is the same as the switch VLAN IP address) and blocks all packets with a source or 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 the logical VLAN IP address, all traffic coming to any port of the switch in that VLAN (with this MAC address as source/destination address) is silently discarded by the hardware. After detecting a duplicate IP address, the switch sends a gratuitous ARP packet to inform devices on the VLAN about the correct MAC address for that IP address. You can specify a time on a configurable global timer after which the MAC discard record is deleted 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).

Nortel Metro Ethernet Routing Switch 8600 Configuration — VLANs, Spanning Tree, and Link Aggregation NN46220-511 04.01 26 June 2009 Copyright © 2007-2009 Nortel Networks. All Rights Reserved.

36 Layer 2 operational concepts

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

ATTENTION Enabling the IP spoofing feature requires you to reboot the switch.

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

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

On a per-port basis, the Loop Detection feature detects MAC addresses that are looping from one port to other ports. After a loop is detected, the port on which the MAC addresses were learned is disabled. Additionally, if a MAC address is found to loop, the MAC address is disabled for that VLAN. The Loop Detection feature is used at the edge of a network to prevent loops. It detects whether the same MAC address appears on different ports. This feature can disable a VLAN or a port. The Loop Detection feature can also disable a group of ports if it detects the same MAC address on two different ports five times in a configurable amount of time. 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. The Loop Detection feature is configured per-switch. If a loop detection event 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 detect action is mac-discard, the MAC address is disabled. Any incoming packets with this source or destination MAC address will be discarded for that VLAN.

•

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

Nortel Metro Ethernet Routing Switch 8600 Configuration — VLANs, Spanning Tree, and Link Aggregation NN46220-511 04.01 26 June 2009 Copyright © 2007-2009 Nortel Networks. All Rights Reserved.

Spanning tree protocols

•

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

•

Loop detection cannot be enabled on interswitch trunk ports.

37

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

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

Spanning tree protocols The Metro Ethernet Routing Switch 8600 can use one of two spanning tree protocols: the Spanning Tree Protocol and the Multiple Spanning Tree Protocol. For information about configuring spanning tree, see “Configuring spanning tree using Device Manager” (page 155) and “Configuring STGs using the CLI” (page 287). This section includes the following topics:

• • •

“Spanning Tree Protocol” (page 37) “Spanning Tree Protocol with PLSB” (page 42) “Spanning Tree Protocol with PBT” (page 43)

Spanning Tree Protocol The operation of the Spanning Tree Protocol (STP) is defined in the IEEE 802.1d standard. The STP detects and eliminates logical loops in a bridged or switched network. When multiple paths exist, the spanning tree algorithm configures the network so that a bridge or switch uses only the most efficient path. If that path fails, the protocol automatically reconfigures the network and makes another path active, which sustains network operations. You can control path redundancy for VLANs by implementing the STP. A network can include multiple instances of STP. The collection of ports in one spanning tree instance is called a spanning tree group (STG). Metro Ethernet Routing Switch 8600 modules support STP and up to 64 spanning tree groups. Nortel Metro Ethernet Routing Switch 8600 Configuration — VLANs, Spanning Tree, and Link Aggregation NN46220-511 04.01 26 June 2009 Copyright © 2007-2009 Nortel Networks. All Rights Reserved.

38 Layer 2 operational concepts

This section includes the following topics:

• • • • •

“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 groups Each STG consists of a collection of ports that belong to the same instance of the STP protocol. These STP instances are completely independent 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 possible within the same switch; that is, the routing switch can participate in the negotiation for multiple spanning trees. Figure 6 "Multiple spanning tree groups" (page 38) shows multiple spanning tree groups. Figure 6 Multiple spanning tree groups

Nortel Metro Ethernet Routing Switch 8600 Configuration — VLANs, Spanning Tree, and Link Aggregation NN46220-511 04.01 26 June 2009 Copyright © 2007-2009 Nortel Networks. All Rights Reserved.

Spanning tree protocols

39

Spanning Tree Protocol controls The ports associated with a VLAN must be contained within a single spanning tree group. If you do not allow a VLAN to span multiple STGs, you avoid problems with spanning tree blocking ports (which causes a loss of connectivity within the VLAN). Each untagged port can belong to only one STG, while tagged ports can belong to more than one STG. When a tagged port belongs to more than one STG, the spanning tree BPDUs are tagged to distinguish the BPDUs of one STG from those of another STG. BPDUs from STG 1 are not tagged. The tagged BPDUs are transmitted using a multicast MAC address as tagged frames with a VLAN ID, and you specify the multicast MAC address and the VLAN ID. Because tagged BPDUs are not part of the 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 the spanning tree group level. If you disable the protocol at the group level, received BPDUs are handled like a MAC-level multicast and flooded out of the other ports of the STG. Note that an STG can contain one or more VLANs. Remember that MAC broadcasts are flooded out on all ports of a VLAN; a BPDU is a MAC-level message, but the BPDU is flooded out of all ports on the STG, which can encompass many VLANs. When STP is globally enabled on the STG, BPDU handling depends on the STP setting of the port:

•

When STP is enabled on the port, received BPDUs are processed in accordance 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 is generated.

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

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

Nortel Metro Ethernet Routing Switch 8600 Configuration — VLANs, Spanning Tree, and Link Aggregation NN46220-511 04.01 26 June 2009 Copyright © 2007-2009 Nortel Networks. All Rights Reserved.

40 Layer 2 operational concepts

FastStart is intended for access ports in which only one device is connected to the switch (as in workstations with no other spanning tree devices). It may not be desirable to wait the usual 30 to 35 seconds for spanning tree initialization and bridge learning. Use Spanning Tree FastStart with caution. This procedure is contrary to that specified in the IEEE 802.1d standard for Spanning Tree Protocol (STP), in which a port enters the blocking state following the initialization of the bridging device or from the disabled state when the port is enabled through configuration.

Understanding STGs and VLANs For the purposes of Spanning Tree Protocol negotiation, the ports on a Metro Ethernet Routing Switch 8600 can be divided into groups of ports where each group of ports performs its own spanning tree negotiation with neighboring devices. In a Metro Ethernet Routing Switch 8600, these groups of ports are called spanning tree groups (STG). The Metro Ethernet Routing Switch 8600 supports up to 64 STGs. The ports in a VLAN are always a subset of the ports in an STG. A VLAN can include all the ports in a given STG, and there can be multiple VLANs in an STG, but a VLAN cannot have more ports than exist in the STG. Because VLANs are always subsets of STGs, the recommended practice is to plan STGs and then create VLANs. In the Metro Ethernet Routing Switch 8600 default configuration, a single STG encompasses all the ports in the switch. For most applications, this configuration is sufficient. The default STG is assigned ID 1 (STG1). If a VLAN spans multiple switches, it must be within the same STG across all switches; that is, the ID of the STG in which it is defined must be the same across all devices.

Spanning Tree Protocol topology change detection Change detection enables the detection of topology changes and sends a topology change notification (TCN) to the root on a per-port basis. Change detection is enabled by default. When change detection is enabled and a topology change occurs, a trap is sent with the following information so that 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 is connected, and where powering that end station on and off will trigger the TCN. Change detection is referenced in IEEE 802.1d. Nortel Metro Ethernet Routing Switch 8600 Configuration — VLANs, Spanning Tree, and Link Aggregation NN46220-511 04.01 26 June 2009 Copyright © 2007-2009 Nortel Networks. All Rights Reserved.

Spanning tree protocols

41

Topology change detection configuration rules When you work with change detection settings:

•

You can configure change detection only on access ports. This also applies to link aggregation ports.

•

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

•

In a link aggregation group with access ports, modifications to change detection for a member port are automatically applied to the remaining member ports.

To configure change detection using Device Manager, see “Configuring STG topology change detection” (page 168). To configure change detection using the CLI, see “Configuring topology change detection” (page 295).

Per-VLAN spanning tree The Metro Ethernet Routing Switch supports standards-based IEEE 802.1d STP in addition to supporting proprietary mechanisms for multiple instances of spanning tree. Unfortunately, the IEEE 802.1d spanning tree provides only one instance of 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 network in 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 all switches. Figure 7 802.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).

Nortel Metro Ethernet Routing Switch 8600 Configuration — VLANs, Spanning Tree, and Link Aggregation NN46220-511 04.01 26 June 2009 Copyright © 2007-2009 Nortel Networks. All Rights Reserved.

42 Layer 2 operational concepts

The Metro Ethernet Routing Switch 8600 uses a tagged BPDU address that is associated with a VLAN tag ID. The VLAN tag ID is applied to one or more VLANs, and is used among switches to prevent loops. The same tagged 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 8 Multiple instances of spanning tree

With software release 3.7 or greater, you can configure your Metro Ethernet Routing Switch using either of two methods: Metro Ethernet Routing Switch 8600 tagged BPDU or PVST+. Similar to the Metro Ethernet Routing Switch 8600 implementation of multiple STP instances, PVST+ uses the standard IEEE 802.1d STP for VLAN 1; all other VLANs use PVST+ BPDUs. You can use IEEE 802.1Q VLAN tagging to tunnel the multicast PVST+ BPDUs within a IEEE 802.1Q region. The standard BPDUs for VLAN 1 are all addressed to the well-known STP multicast address 01-80-C2-00-00-00, while PVST+ BPDUs in other VLANs are addressed to the multicast address of 01-00-0C-CC-CC-CD. You can use PVST+ to load balance the VLANs by changing the VLAN bridge priority.

Spanning Tree Protocol with PLSB Provider Link State Bridging (PLSB) does not support xSTP. When PLSB is 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-STG must be created. PLSB is a simple, robust networking solution that displaces conventional Ethernet networking solutions for E-LAN services achieved through the use of a Link State Routing Protocol as the control plane rather than conventional spanning tree protocols. PBT and PLSB are complementary Nortel Metro Ethernet Routing Switch 8600 Configuration — VLANs, Spanning Tree, and Link Aggregation NN46220-511 04.01 26 June 2009 Copyright © 2007-2009 Nortel Networks. All Rights Reserved.

Spanning tree protocols

43

as they address different problems (for example, E-Line versus E-LAN services) while leveraging a common data plane approach (that is MAC-in-MAC, PBT style configuration in a VLAN partition). PLSB and existing Ethernet control protocols (for example, spanning tree) can operate side-by-side in the same network infrastructure ensuring smooth network evolution.

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

Multiple Spanning Tree Protocol The operation of the Multiple Spanning Tree Protocol (MSTP or IEEE 802.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 to achieve the following:

•

reduced convergence time from 30 seconds to less than one second for 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 topology change 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 Protocol configuration example” (page 406).

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

•

An STP-compatible port transmits and receives only STP BPDUs. Any MSTP 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. User intervention is required to change this port back to MSTP mode. This process is called Port Protocol Migration.

Nortel Metro Ethernet Routing Switch 8600 Configuration — VLANs, Spanning Tree, and Link Aggregation NN46220-511 04.01 26 June 2009 Copyright © 2007-2009 Nortel Networks. All Rights Reserved.

44 Layer 2 operational concepts

Differences in port roles MSTP is an enhanced version of STP. These two protocols have almost the 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 4 Differences in port roles for STP and MSTP Port Role

STP

MSTP

Description

Root

Yes

Yes

This port receives a better BPDU than its own and has the best path to reach the Root. The root port is in Forwarding state. The root port and designated ports can be in the Discarding state before they go to root forwarding.

Designated

Yes

Yes

This port has the best BPDU on the segment. The designated port is in the Forwarding state.

Alternate

No

Yes

This port receives a better BPDU than its own BPDU, and there is a Root port within the same switch. The alternate port is in the Discarding state.

Backup

No

Yes

This port receives a better BPDU than its own BPDU, and this BPDU is from another port within the same switch. The backup port is in the Discarding state.

Port roles—root forwarding role MSTP root forwarding roles are as follows:

Nortel Metro Ethernet Routing Switch 8600 Configuration — VLANs, Spanning Tree, and Link Aggregation NN46220-511 04.01 26 June 2009 Copyright © 2007-2009 Nortel Networks. All Rights Reserved.

Spanning tree protocols

45

•

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 that is the closest to the root bridge in terms of path cost.

•

The spanning tree algorithm elects a single root bridge in a bridged network per spanning tree instance.

•

The root bridge is the only bridge in a network that does not have root ports; 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’s BPDUs. The bridge that sends the best BPDU is, by mutual agreement, the root bridge for the segment.

•

The corresponding port on the bridge is referred to as a Designated Forwarding 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 received better path cost BPDUs from another bridge.

Edge port MSTP uses a new parameter called the edge port. When a port connects to a non-switch device, such as a PC or a workstation, it must be configured as an edge port. An active edge port enters forwarding state without delay. An edge port becomes a non-edge port if it receives a BPDU. Path cost values MSTP recommends new path cost values that support a wide range of link speeds. The following table lists the recommended path cost values.

Nortel Metro Ethernet Routing Switch 8600 Configuration — VLANs, Spanning Tree, and Link Aggregation NN46220-511 04.01 26 June 2009 Copyright © 2007-2009 Nortel Networks. All Rights Reserved.

46 Layer 2 operational concepts Table 5 Recommended path cost values Link Speed

Recommended Value

Less than or equal to 100 Kb/s 1 Mb/s 10 Mb/s 100 Mb/s

200 000 000 20 000 000 2 000 000 200 000

1 Gb/s 10 Gb/s 100 Gb/s

20 000 2 000 200

1 Tb/s 10 Tb/s

20 2

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

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

Nortel Metro Ethernet Routing Switch 8600 Configuration — VLANs, Spanning Tree, and Link Aggregation NN46220-511 04.01 26 June 2009 Copyright © 2007-2009 Nortel Networks. All Rights Reserved.

Link aggregation (MLT, SMLT, LACP)

47

Switch A port 1 and switch B port 1 exchange BPDUs. Switch A knows that it is the root and that switch A port 1 is the designated port. Switch B learns that switch A has higher priority. Switch B port 1 becomes the root port. 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 the proposal bit set. Switch B receives the proposal BPDU and sets its non-edge ports to discarding 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 to forwarding state. PC 1 and PC 2 can now communicate. The negotiation process now moves on to switch B port 3 and its partner port. PC 3 cannot exchange data with either PC 1 or PC 2 until the negotiation process between switch B and switch C finishes. The MSTP convergence time depends on how quickly the switch can exchange BPDUs during the negotiation process, and on the number of switches 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 link aggregation:

•

MultiLink Trunking (MLT) is a statically configured link bundling method.

•

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

•

If Provider Link State Bridging (PLSB) MLT ISIS interface and LACP are configured on the same MLT, when a port configured on the LAG comes up, the port is added dynamically to MLT, and LACP informs PLSB ISIS to bring up the ISIS circuit. When a port configured on the LAG goes down, the port is removed dynamically from MLT, and if the port is the last port on the MLT, LACP informs PLSB ISIS to bring down ISIS circuit.

•

Both MLT and IEEE 802.3ad-based link aggregation are defined as point-to-point functions, although Split MultiLink Trunking (SMLT) allows you to connect a multilink trunk point to two SMLT endpoints. Nortel Metro Ethernet Routing Switch 8600 Configuration — VLANs, Spanning Tree, and Link Aggregation NN46220-511 04.01 26 June 2009 Copyright © 2007-2009 Nortel Networks. All Rights Reserved.

48 Layer 2 operational concepts

SMLT can connect two SMLT end points to two other SMLT endpoints as well.

•

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

For information about configuring link aggregation, see “Configuring link aggregation using Device Manager” (page 183) and “Configuring link aggregation using the CLI” (page 321). See “Device Manager configuration examples” (page 367) and “CLI configuration examples” (page 375) for configuration examples, including CLI commands, for concepts described in this section. This section includes the following topics:

• • •

“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 aggregates multiple ports so that they logically act like a single port, but with the aggregated bandwidth. Grouping multiple ports into a logical link provides higher aggregate throughput on a switch-to-switch or switch-to-server application. MultiLink Trunking provides media and module redundancy. Module redundancy is provided in the form of Distributed MLT (DMLT), which you can use to aggregate similar ports from different modules. MLT links must be statically configured to be trunk group members. This section includes the following topics:

• • • • • • •

“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) Nortel Metro Ethernet Routing Switch 8600 Configuration — VLANs, Spanning Tree, and Link Aggregation NN46220-511 04.01 26 June 2009 Copyright © 2007-2009 Nortel Networks. All Rights Reserved.

Link aggregation (MLT, SMLT, LACP)

• •

49

“Multicast traffic redistribution” (page 55) “MLT examples” (page 56)

MLT UNI MLT is based on 802.3ad link aggregation (LAG), which allows multiple Ethernet links to be grouped into one bundle. MLT UNI is supported on R and RC modules, and on ESM ports. MLT links can be on the same card or across different physical cards to provide card redundancy, referred to as Distributed MLT (DMLT). A single MLT cannot span different card types. MLT UNI is not supported on Ethernet Services Unit access ports when the 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 MAC address is used as the source and destination MAC for OEL2 and PBB encapsulation. ISID endpoint and TDI endpoint traffic statistics are displayed as an aggregation of statistics from each MLT member port used by a given entity. For more information on using and configuring MLT UNI, see Engineering Guidelines (NN46220-200).

MLT load distribution options Load distribution algorithms on Metro Ethernet Routing Switch for traffic distribution across an MLT are supported for on both MLT UNI and NNI MLT. The actual distribution and forwarding is performed in the hardware. The following distinct hardware MLT distribution types are supported on Metro Ethernet Routing Switch: C-MAC Hash The MLT link is chosen based on a hash of the associated source and destination customer MAC address (C-MAC SA and DA), if the ingress link is an R or RC module NNI, or R or RC module UNI.

Nortel Metro Ethernet Routing Switch 8600 Configuration — VLANs, Spanning Tree, and Link Aggregation NN46220-511 04.01 26 June 2009 Copyright © 2007-2009 Nortel Networks. All Rights Reserved.

50 Layer 2 operational concepts

If the ingress UNI is on an ESM card, the hash is based on the source customer MAC and destination B-MAC/UNI MAC (C-MAC SA and B-MAC DA). If the CPE is a router or the VPN type is point-to-point, this option results in unicast frames between two Metro Ethernet Routing Switch UNIs taking the same egress MLT link. A typical router deployment has a single IP link between 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 source and destination UNI MAC or source and destination I-SID MAC (UNI MAC/BMAC SA and DA). If the traffic type is OEL2 and the ingress MLT port is a legacy NNI port or ESM local TLS/Ring/Standalone, this traffic is hashed based on the OEL2 UNI ID. For R and RC modules, and ESM MLT-UNI, OEL2, traffic is hashed based on the UNI MAC/BMAC. For E-LINE (point to point) service, this option results in all VPN traffic to egress a single link of an MLT UNI. B-MAC Hash is the default option for MLT-UNI. It is also used if the configured option is not supported by the ingress hardware. For more information 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 priority list for VPNs that use different SPVLANs/BVLANs within the core of the network. For a given VPN, because a VPN must be in a single SPVLAN/BVID, traffic always chooses the same link (highest priority). This can effectively distribute traffic over an MLT UNI only if there are several SPVLANs/BVLANs in use in the core of the Metro Ethernet Routing Switch network. This option is likely to be deployed for interconnection between networks, where different VPNs can be put into different core VLANs. This option can allow greater than 1G throughput for an MLT (independent of MAC addresses) under nonfailure conditions.

Nortel Metro Ethernet Routing Switch 8600 Configuration — VLANs, Spanning Tree, and Link Aggregation NN46220-511 04.01 26 June 2009 Copyright © 2007-2009 Nortel Networks. All Rights Reserved.

Link aggregation (MLT, SMLT, LACP)

51

Packets in the same flow are guaranteed to be placed on the same link in the MLT group, therefore guaranteeing frame ordering. Each VID is given a primary and secondary link. A primary failure causes switchover to secondary; upon recovery traffic is reverted. Ingress traffic from the CPE can 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 R or RC module. If the ingress card is ESM or Legacy NNI, the default B-MAC Hash is used instead. If the packet received is not a PBB or OEL2 encapsulated packet, the default B-MAC hash is used. The egress MLT link is chosen based on a hash of the associated ISID or TDI number. Frames are hashed such that all frames that are a member of a single TDI or ISID are sent over the same link. In order for this option to effectively distribute traffic, several TDI or ISIDs must be present on the MLT UNI. For more details on MLT load distribution, see Engineering Guidelines (NN46220-200).

Metro Ethernet Routing Switch 8600 MLT hash algorithms The Metro Ethernet Routing Switch distributes traffic across MLT link members based on several criteria. Regardless of which load distribution option is chosen, the actual algorithm varies based on the Ingress hardware to the node and the protocol or service being used. Different card types and vintages have different capabilities to distribute traffic. Legacy NNI The original 8000 series Legacy I/O modules are used only for NNI ports or trunks. The Legacy I/O module performs the hash algorithm based on the 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 IP routed or IP bridged traffic and x is the number of active links in the MLT.

Nortel Metro Ethernet Routing Switch 8600 Configuration — VLANs, Spanning Tree, and Link Aggregation NN46220-511 04.01 26 June 2009 Copyright © 2007-2009 Nortel Networks. All Rights Reserved.

52 Layer 2 operational concepts

IP traffic is always hashed on the SA/DA IP address using the 6 bit LSB XOR 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 BMAC option 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 bit LSB XOR function. ESM8668 MLT UNI MLT-UNI on ESM cards perform the same algorithm as described for Legacy cards. However the hash is based on the UNI MAC fields when the BMAC option is chosen. R and RC module UNI/NNI (including MLT) The R and RC module hash algorithm uses 32 bit polynomial function routine to determine the distribution. The formula uses 32 bits from the source and 32 bits from the destination address, and uses the polynomial function to determine an MLT link index for a particular flow. The 32 bit polynomial function inputs are always SA/DA UNI MAC/B-MAC for EVPN traffic, or IP SA/DA for IP routed or bridged non EVPN traffic. Metro Ethernet Routing Switch 8600 provides a CLI command to generate the hash results for selected source and destination addresses. This command can be used to verify what MLT links are used for a select combination. The following is an example CLI command for ISID: config sys set hash-calc getmltindex traffic-type non-ip dest-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. Because there is only one field used to hash with, a fixed value for dest-val equal to 1:0:0:0:0:0:0 is used when TDI/ISID (in hex format) is used as the src-val.

Multicast/Broadcast Hashing For broadcast and multicast traffic (including EVPN traffic that fails CMAC lookup, for example multicast in the BVID), the traffic sent across the MLT differs based on the Ingress hardware type. Legacy modules send the broadcast or multicast traffic to a single link defined by the first link in the MGID table on the switch fabric. This link is not deterministic. Nortel Metro Ethernet Routing Switch 8600 Configuration — VLANs, Spanning Tree, and Link Aggregation NN46220-511 04.01 26 June 2009 Copyright © 2007-2009 Nortel Networks. All Rights Reserved.

Link aggregation (MLT, SMLT, LACP)

53

R modules send the broadcast or multicast traffic to a single link defined by 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 broadcast or multicast traffic (including flooding unknown EVPN traffic) that can traverse an MLT. Also, the first link, as defined above, can be different for each direction between two nodes. The result is that forward and reverse multicast traffic take different links in an MLT group based on the direction between two nodes.

MultiLink Trunking rules All Metro Ethernet Routing Switch 8600 multilink trunks operate under the following set of rules:

•

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

•

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

•

All ports in a multilink trunk must be in the same STG, unless the port is 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 commands must be included in the MLT UNI before the MLT can be used for a UNI endpoint.

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

•

Up to 128 MLT groups (using R modules and R mode) are supported with as many as 8 same-type ports belonging to a single multilink trunk.

•

The ports in a multilink trunk can span modules, providing module redundancy.

•

Apply filters individually to each port in a multilink trunk.

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

Nortel Metro Ethernet Routing Switch 8600 Configuration — VLANs, Spanning Tree, and Link Aggregation NN46220-511 04.01 26 June 2009 Copyright © 2007-2009 Nortel Networks. All Rights Reserved.

54 Layer 2 operational concepts

This algorithm is the same multicast flow distribution algorithm used for IEEE 802.3ad-based link aggregation. As a result, you can distribute the load on different ports of the multilink trunk and achieve an even distribution of the streams. In applications such as TV distribution, multicast traffic distribution is particularly important, because bandwidth requirements can be substantial when a large number of TV streams are employed. The Multicast Distribution over MLT feature is supported only on Metro Ethernet Routing Switch 8600 E, M, and R modules. As a result, all the modules that have ports in a multilink trunk must be Metro Ethernet Routing Switch 8600 E, M, or R modules to enable multicast flow distribution over MLT.

Multicast distribution algorithm To determine the port for a particular source, group (S, G) pair, use the number of active MLT ports to MOD the number generated by the XOR (exclusive OR operation) for each byte of the masked group address, with the masked source address. By default, the group mask and source mask is 255.255.255.255. A byte with a value of 255 in the mask means that the corresponding byte in the group or source address is taken into account when the algorithm is applied. 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] AND GM[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 be sequential if the streams are similar to those in this example. Nortel Metro Ethernet Routing Switch 8600 Configuration — VLANs, Spanning Tree, and Link Aggregation NN46220-511 04.01 26 June 2009 Copyright © 2007-2009 Nortel Networks. All Rights Reserved.

Link aggregation (MLT, SMLT, LACP)

55

For this example, assume that the MLT ports are 1/1 to 1/4, that the mask configuration is 0.0.0.0 for the source mask and 0.0.0.255 for the group mask, 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 goes on port 1/2, X.Y.Z.3 goes on port 1/3, X.Y.Z.4 goes on port 1/4, X.Y.Z.5 goes on port 1/1, and so on. Configuration example In this configuration example, only the first byte of the group mask, and the first two bytes of the source subnet mask are considered when distributing the streams. config config config config

sys sys sys sys

mcast-mlt-distribution mcast-mlt-distribution mcast-mlt-distribution mcast-mlt-distribution

grp-mask 255.0.0.0 src-mask 255.255.0.0 enable redistribution enable

When you configure flow distribution over MLT, Nortel recommends that you choose source and group masks that result in the most even traffic distribution over the multilink trunk links. For example, if you find that group addresses change incrementally, while there are few sources sending to different groups, use a source mask of 0.0.0.0 and a group mask of 255.255.255.255. In most cases, this provides a sequential distribution of traffic on the multilink trunk links. For a detailed description of commands used to configure multicast flow distribution over MLT, see Configuration — IP Multicast (NN46220-519).

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

Nortel Metro Ethernet Routing Switch 8600 Configuration — VLANs, Spanning Tree, and Link Aggregation NN46220-511 04.01 26 June 2009 Copyright © 2007-2009 Nortel Networks. All Rights Reserved.

56 Layer 2 operational concepts

By default, redistribution is disabled. When you add or remove a link from the multilink trunk, the active streams continue flowing on their original links if redistribution is disabled. If redistribution is enabled, however, the active streams are redistributed according to the distribution algorithm on the links of the multilink trunk. Traffic redistribution can cause minor traffic interruptions. To minimize the effect of redistribution of multicast traffic on the multilink trunks, the implementation does not move the streams to the appropriate links all at once. Instead, it redistributes a few streams at every time tick of the system. To that end, when an MLT port becomes inactive and redistribution is disabled, only the affected streams are redistributed on the remaining active ports. If redistribution is enabled, all the streams are redistributed on the MLT ports based on the assignment provided by the distribution algorithm. For more information, see “Multicast distribution algorithm” (page 54). When a new port becomes active in a multilink trunk and redistribution is disabled, existing streams remain on their original links. If you need to redistribute the streams dynamically to split the load on all the links of the multilink trunk, you can enable redistribution. This results in a few streams being redistributed every system time tick. For a detailed description of the commands used to configure multicast flow distribution over MLT, see Configuration — IP Multicast (NN46220-519).

MLT examples This section provides three MLT examples and includes the following topics:

• •

Switch-to-switch MLT example Client/server MLT example

Switch-to-switch MLT example The following figure shows two multilink trunks (T1 and T2) connecting switch S1 to switches S2 and S3.

Nortel Metro Ethernet Routing Switch 8600 Configuration — VLANs, Spanning Tree, and Link Aggregation NN46220-511 04.01 26 June 2009 Copyright © 2007-2009 Nortel Networks. All Rights Reserved.

Link aggregation (MLT, SMLT, LACP)

57

Figure 10 Switch-to-switch multilink trunk configuration

Each of the trunks shown in Figure 10 "Switch-to-switch multilink trunk configuration" (page 57) can be configured with multiple switch ports to increase bandwidth and redundancy. When traffic between switch-to-switch connections approaches single port bandwidth limitations, you can create a multilink trunk to supply the additional bandwidth required to improve performance. Switch-to-server MLT example This example applies to MLT UNIs where the servers are attached to MLT UNIs. Figure 11 "Switch-to-server multilink trunk configuration" (page 58) shows a typical switch-to-server trunk configuration. In this example, file server FS1 utilizes dual MAC addresses, using one MAC address for each network interface card (NIC). No multilink trunk is configured on FS1. FS2 is a single MAC server (with a four port NIC) and is configured as multilink trunk configuration T1.

Nortel Metro Ethernet Routing Switch 8600 Configuration — VLANs, Spanning Tree, and Link Aggregation NN46220-511 04.01 26 June 2009 Copyright © 2007-2009 Nortel Networks. All Rights Reserved.

58 Layer 2 operational concepts Figure 11 Switch-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 trunk T1. Client/server MLT example Figure 12 "Client/server multilink trunk configuration" (page 59) shows an example of how multilink trunks can be used in a client/server configuration. In this example, both servers are connected directly to switch S1. FS2 is connected through a multilink trunk configuration (T1). The switch-to-switch connections are through multilink trunk T2, T3, and T4. Clients accessing data from the servers (FS1 and FS2) are provided with maximized bandwidth through T1, T2, T3, and T4. On the Metro Ethernet Routing Switch 8600, trunk members (the ports that comprise each multilink trunk) do not have to be consecutive switch ports; they can be selected across different modules for module redundancy.

Nortel Metro Ethernet Routing Switch 8600 Configuration — VLANs, Spanning Tree, and Link Aggregation NN46220-511 04.01 26 June 2009 Copyright © 2007-2009 Nortel Networks. All Rights Reserved.

Link aggregation (MLT, SMLT, LACP)

59

Figure 12 Client/server multilink trunk configuration

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

•

All ports in the multilink trunk must belong to the same spanning tree group 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 is forwarding. You can disable the Nortel Spanning Tree Protocol (ntstg ) if you do not want to receive BPDUs on all ports.

Nortel Metro Ethernet Routing Switch 8600 Configuration — VLANs, Spanning Tree, and Link Aggregation NN46220-511 04.01 26 June 2009 Copyright © 2007-2009 Nortel Networks. All Rights Reserved.

60 Layer 2 operational concepts

•

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

•

Path cost is inversely proportional to the active multilink trunk bandwidth.

IEEE 802.3ad-based link aggregation IEEE 802.3ad-based (IEEE 802.3 2002 clause 43) link aggregation allows you to aggregate one or more links together to form a link aggregation group (LAG), such that a MAC client can treat the LAG as if it were a single link. Although IEEE 802.3ad-based link aggregation and MLT provide similar services, MLT is statically defined, whereas IEEE 802.3ad-based link aggregation is dynamic and provides more functionality through the Link Aggregation Control Protocol (LACP). LACP dynamically detects whether links can be aggregated into a link aggregation group and does so when links become available. IEEE 802.3ad was designed for point-to-point link aggregation only. However, the Metro Ethernet Routing Switch 8600 provides extensions to support IEEE 802.3ad in SMLT configurations, thereby allowing any IEEE 802.3ad-capable device to be connected to an SMLT aggregation pair. This section includes the following topics:

• • • • • • • • • • •

“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)

Nortel Metro Ethernet Routing Switch 8600 Configuration — VLANs, Spanning Tree, and Link Aggregation NN46220-511 04.01 26 June 2009 Copyright © 2007-2009 Nortel Networks. All Rights Reserved.

Link aggregation (MLT, SMLT, LACP)

61

IEEE 802.3ad overview The IEEE 802.3ad standard comprises of service interfaces, the Link Aggregation Control Protocol, the Marker Protocol, link aggregation selection logic, parser/multiplexer, frame distribution, and frame collection functions. Figure 13 "Link aggregation sublayer (according to IEEE 802.3ad)" (page 61) shows the major functions of IEEE 802.3ad defined as multiple link aggregation. Figure 13 Link aggregation sublayer (according to IEEE 802.3ad)

LACP The main purpose of LACP is to manage switch ports and their port memberships to form link aggregation groups (LAG). LACP can dynamically add or remove LAG ports, depending on their availability and states. Aside from automatic link aggregation, a side benefit of LACP is its ability to detect link layer failure within a service provider network. LACP packets are exchanged end to end, thus if a link in the middle fails, but the local ports do not register the failure, LACP times out and disables the port for traffic.

Nortel Metro Ethernet Routing Switch 8600 Configuration — VLANs, Spanning Tree, and Link Aggregation NN46220-511 04.01 26 June 2009 Copyright © 2007-2009 Nortel Networks. All Rights Reserved.

62 Layer 2 operational concepts

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

Link aggregation operations As shown in Figure 13 "Link aggregation sublayer (according to IEEE 802.3ad)" (page 61), the link aggregation sublayer comprises the following functions:

•

Frame distribution: This block takes frames submitted by the MAC client and submits them for transmission on the appropriate port, based on a frame distribution algorithm employed by the Frame Distributor. Frame distribution also includes an optional Marker Generator/Receiver used for the Marker Protocol. For the Metro Ethernet Routing Switch 8600, only the Marker Receiver function is implemented. Refer to “MultiLink Trunking (MLT)” (page 48) for details about the frame distribution function.

•

Frame collection: This block passes frames received from the various ports to the MAC client. Frame collection also includes a Marker Responder, used for the Marker Protocol.

•

Aggregator Parser/Multiplexers:

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

— During receive operations, these blocks distinguish among Marker Request, Marker Response, and MAC Client PDUs, and pass each to the appropriate entity (Marker Responder, Marker Receiver, and Collector, respectively).

•

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

•

Aggregation Control: This block configures and controls link aggregation. It incorporates LACP, which can be used for automatic communication of aggregation capabilities between systems. and automatic configuration of link aggregation.

•

Control Parser/Multiplexers:

Nortel Metro Ethernet Routing Switch 8600 Configuration — VLANs, Spanning Tree, and Link Aggregation NN46220-511 04.01 26 June 2009 Copyright © 2007-2009 Nortel Networks. All Rights Reserved.

Link aggregation (MLT, SMLT, LACP)

63

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

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

Principles of link aggregation Link aggregation allows you to group switch ports together to form a link group to another switch or server, thus increasing aggregate throughput of the 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 MAC client. The Aggregator binds to one or more ports within a system.

•

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

•

A system can contain multiple aggregators serving multiple MAC clients. 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 the Link Aggregation Control function for that system. The control function determines which links can be aggregated, aggregates them, binds the ports within the system to an appropriate aggregator, and monitors conditions to determine when a change in aggregation is needed. Such determination and binding can be under manual control through direct manipulation 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 of a LACP.

•

The LACP uses peer exchanges across the links to determine, on an ongoing basis, the aggregation capability of the various links, and continuously provides the maximum level of aggregation capability achievable between a given pair of systems.

•

Frame ordering is maintained for certain sequences of frame exchanges between MAC Clients. The distributor ensures that all frames of a given conversation are passed to a single port. For any given port, the collector is required to pass frames to the MAC client in the order that they are received from that port. The collector is

Nortel Metro Ethernet Routing Switch 8600 Configuration — VLANs, Spanning Tree, and Link Aggregation NN46220-511 04.01 26 June 2009 Copyright © 2007-2009 Nortel Networks. All Rights Reserved.

64 Layer 2 operational concepts

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

•

Conversations can be moved among ports within an aggregation, both for load balancing and for maintaining availability in the event of link failures.

•

The standard does not impose any particular distribution algorithm on the distributor. Use an algorithm that is appropriate for the supported MAC 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 exchanges that 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 MAC address, which is used as the MAC address of the aggregation from the perspective of the MAC Client, both as a source address for transmitted frames and as the destination address for received frames. The MAC address of the aggregator can be one of the MAC addresses of a port in the associated LAG.

LACP and MLT When you configure standards-based link aggregation, you must enable the aggregatable field. After you enable the aggregatable field, the LACP aggregator is one-to-one mapped to the specified multilink trunk. For example, when you configure a link aggregation group (LAG), you must 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 key matches its own.

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

Nortel Metro Ethernet Routing Switch 8600 Configuration — VLANs, Spanning Tree, and Link Aggregation NN46220-511 04.01 26 June 2009 Copyright © 2007-2009 Nortel Networks. All Rights Reserved.

Link aggregation (MLT, SMLT, LACP)

65

deleted from the associated LAG port member list. When the last port member is deleted from the LAG, the LAG is deleted from all VLANs and STGs. When LACP is enabled on any MLT containing ports, MLT LACP attributes override all the port level LACP attributes for the statically added ports. To enable tagging on ports belonging to LAG, first disable LACP on the port, and then enable tagging on the port and enable LACP. In release 6.0, the behavior of LACP-enabled MLTs is changed so that ports can be added and removed from an LACP-enabled MLT statically, as well as dynamically. This change is applicable on both UNI and NNI MLT/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 not transmitted and accepted on this port. In this condition, the port is in an STG-disabled state. Because ports can now be added and removed from an LACP-enabled MLT statically, the following points are also supported:

• •

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

•

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

dynamic addition and removal of B-VLANs and ACLs on an LACP-enabled MLT

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

•

When you sets the LACP system ID for split multilink trunks, you must configure the same LACP SMLT system ID on both aggregation switches to avoid loss of data. Nortel recommends that the SmltSysId be configured such that it matches the base MAC address of one of the chassis.

•

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

•

If an SMLT aggregation switch has LACP enabled on some of its multilink trunks, do not change LACP system priority after LACP is enabled on ports. If some ports do not enter the desired multilink trunk Nortel Metro Ethernet Routing Switch 8600 Configuration — VLANs, Spanning Tree, and Link Aggregation NN46220-511 04.01 26 June 2009 Copyright © 2007-2009 Nortel Networks. All Rights Reserved.

66 Layer 2 operational concepts

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

•

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

Using the smlt-sys-id enables the use of any third-party switch as a wiring closet switch in an SMLT configuration. This enhancement provides an option for the administrator to configure the system id on the aggregation switch. The actor system priority of actor system id (LACP_DEFAULT_SYS_PRIO), configured by the user, and an actor key equal to the SMLT-ID or SLT-ID, is sent to the wiring closet switch. The administrator must ensure that the same value of system id is configured on the both the aggregation switches.

LACP priority LACP priority is configured at the system level and at the port level. • Port priority—determines which ports are aggregated into LAG if more than eight ports are configured for the LAG, as in a standby-port configuration. • System priority—generates the switch ID when communicating with other switches. For SMLT applications, this is used to determine a master/slave relationship between the SMLT switches. Nortel recommends that this value remain at its default value. If it must be changed, Nortel recommends that you disable LACP first, and then reenable it after the value is changed.

LACP keys LACP keys are used to determine which ports are eligible to be aggregated into a LAG. The LACP keys are defined under the ports when the multilink trunk is configured. The ports whose keys match the multilink trunk’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 with SMLT.

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

• • •

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 a MLT. Nortel Metro Ethernet Routing Switch 8600 Configuration — VLANs, Spanning Tree, and Link Aggregation NN46220-511 04.01 26 June 2009 Copyright © 2007-2009 Nortel Networks. All Rights Reserved.

Link aggregation (MLT, SMLT, LACP)

•

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

•

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

67

LACP timers You can customize failover times by changing the LACP timer attributes (fast periodic time; slow periodic time; aggregate wait time). These values are set by default to match the IEEE 802.3ad values. If they are changed, these values must match on the ports participating in aggregation between two 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 you change a LACP timer globally, this value is set on all ports. The global timer 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 the port level. By default, the Metro Ethernet Routing Switch 8600 uses the long timer. LACP uses the following timers, which have the parameters indicated:

• • •

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 or on a port. This action ensures consistency with peer switches. When you enable LACP on a port, the timer values used are those set at the port level. Toggling of the LACP status is required when timer values change. Existing ports are not impacted by this change unless you toggle the LACP status on the port.

Nortel Metro Ethernet Routing Switch 8600 Configuration — VLANs, Spanning Tree, and Link Aggregation NN46220-511 04.01 26 June 2009 Copyright © 2007-2009 Nortel Networks. All Rights Reserved.

68 Layer 2 operational concepts

LACP modes LACP uses two mode types, active and passive.

•

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

•

Passive mode—ports participate in LACP but do not initiate the aggregation process. Passive mode ports must be partnered with active mode ports for aggregation to occur.

LACP and spanning tree interaction LACP module operation is only affected by the physical link state or its LACP peer status. When a link is enabled or disabled, the LACP module is notified. The STP forwarding state does not affect the operation of LACP module. LACPDUs can be sent even if the port is in the STP blocking state. Unlike legacy multilink trunks, configuration changes (such as speed and duplex mode) to a LAG member port are not applied to all the member ports in the multilink trunk. Instead, the changed port is removed from the LAG and the corresponding aggregator, and the user is alerted when the configuration is created. In contrast to MLT, IEEE 802.3ad-based link aggregation does not expect BPDUs to be replicated over all ports in the trunk group. Therefore, you must enter the ntstg disable command to disable the parameter on the spanning tree group for LACP-based link aggregation. For more information about this command, see “Configuring Spanning Tree Protocol” (page 156) . Be aware that this parameter is applicable to all trunk groups that are members of the spanning tree group. This is necessary when internetworking with devices that only send BPDUs out of one port of the LAG.

Link aggregation rules Metro Ethernet Routing Switch 8600 link aggregation groups operate under the following rules:

• • • •

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

•

Link aggregation groups must be in the same STP groups.

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) and Multiple Spanning Tree Protocol (MSTP).

Nortel Metro Ethernet Routing Switch 8600 Configuration — VLANs, Spanning Tree, and Link Aggregation NN46220-511 04.01 26 June 2009 Copyright © 2007-2009 Nortel Networks. All Rights Reserved.

Link aggregation (MLT, SMLT, LACP)

• •

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

• • •

A maximum of eight active links are supported per LAG.

69

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

A maximum of eight standby links are supported per LAG. You can configure up to eight ports (mixture of active and standby ports) in an 802.3ad group.

Split MultiLink Trunking (SMLT) Routed SMLT, or RSMLT, is a Layer 3 protocol whereas SMLT is a Layer 2 protocol. SMLT is described in this document, and RSMLT is described in 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 and includes the following topics. For help with common terms and acronyms used 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)

Overview Link aggregation technologies are popular for improving link bandwidth efficiency and preventing link failures. IEEE 802.3ad is the standardized link aggregation protocol, although various vendors have developed their own proprietary implementations. IEEE 802.3ad is defined for point-to-point applications, however; it was not designed to recover around a nodal failure. Split MultiLink Trunking (SMLT) is an extension to IEEE 802.3ad that improves Layer 2 and Layer 3 resiliency by providing nodal protection, in addition to link failure protection, and flexible bandwidth scaling. SMLT

Nortel Metro Ethernet Routing Switch 8600 Configuration — VLANs, Spanning Tree, and Link Aggregation NN46220-511 04.01 26 June 2009 Copyright © 2007-2009 Nortel Networks. All Rights Reserved.

70 Layer 2 operational concepts

achieves this by allowing edge switches using IEEE 802.3ad to dual-home to two SMLT aggregation switches. SMLT is transparent to attached devices supporting IEEE 802.3ad. Because SMLT inherently avoids loops due to its superior enhanced link aggregation protocol, SMLT networks do not need to use the IEEE 802.1d Spanning Tree Protocol to enable loop-free triangle topologies. This is accomplished by implementing a method that allows two aggregation switches to appear as a single device to edge switches, which are dual-homed to the aggregation switches. The aggregation switches are interconnected using an interswitch trunk, which allows them to exchange addressing and state information (permitting rapid fault detection and forwarding path modification). Although SMLT is primarily designed for Layer 2, it also provides benefits for Layer 3 networks as well. Layer 2 edge switches must support some form of link aggregation (such as MLT) to allow communications with an SMLT aggregation switch.

Advantages of SMLT SMLT improves the reliability of Layer 2 networks that operate between user access switches and the network center aggregation switch by providing:

• • • • • •

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 only on the 8683XLR/XZR modules. Single point of failure elimination SMLT helps eliminate all single points of failure and creates multiple paths from 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 no modification on the part of the majority of existing user access devices. SMLT compared to Spanning Tree Protocol

Nortel Metro Ethernet Routing Switch 8600 Configuration — VLANs, Spanning Tree, and Link Aggregation NN46220-511 04.01 26 June 2009 Copyright © 2007-2009 Nortel Networks. All Rights Reserved.

Link aggregation (MLT, SMLT, LACP)

71

Networks that are designed to have user access switches dual-homed to two aggregation switches, and have VLANs spanning two or more user access 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" (page 71) shows a typical aggregator switch configuration that is dependent upon STP for loop detection. Figure 14 Resilient networks with Spanning Tree Protocol

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

Nortel Metro Ethernet Routing Switch 8600 Configuration — VLANs, Spanning Tree, and Link Aggregation NN46220-511 04.01 26 June 2009 Copyright © 2007-2009 Nortel Networks. All Rights Reserved.

72 Layer 2 operational concepts

Resilient networks with SMLT is supported for IP routing and for services associated with customer IP VLAN UNIs. Figure 15 Resilient networks with SMLT

SMLT operations Figure 16 "Metro Ethernet Routing Switch 8600 as SMLT aggregation switches" (page 73) illustrates an SMLT configuration with a pair of Metro Ethernet 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 shown in this SMLT example.

• • •

Interswitch trunking CP Limit and SMLT interswitch trunking Other SMLT aggregation switch connections

Nortel Metro Ethernet Routing Switch 8600 Configuration — VLANs, Spanning Tree, and Link Aggregation NN46220-511 04.01 26 June 2009 Copyright © 2007-2009 Nortel Networks. All Rights Reserved.

Link aggregation (MLT, SMLT, LACP)

73

Figure 16 Metro Ethernet Routing Switch 8600 as SMLT aggregation switches

Interswitch trunking SMLT aggregation switches must be connected through an interswitch trunk. For example, user access switches B and C are connected to the aggregation switches via multilink trunks split between the two aggregation switches. As shown in Figure 16 "Metro Ethernet Routing Switch 8600 as SMLT aggregation switches" (page 73), the implementation of SMLT only requires two SMLT-capable aggregation switches. These switches must be connected through an interswitch trunk. Aggregation switches use the interswitch trunk to:

•

Confirm that they are alive and exchange MAC address forwarding tables.

•

Send traffic between single switches attached to the aggregation switches.

•

Serve as a backup if one SMLT link fails.

Nortel Metro Ethernet Routing Switch 8600 Configuration — VLANs, Spanning Tree, and Link Aggregation NN46220-511 04.01 26 June 2009 Copyright © 2007-2009 Nortel Networks. All Rights Reserved.

74 Layer 2 operational concepts

Because the interswitch trunk is required for SMLT, for proper operation Nortel recommends that you use multiple links on the interswitch trunk to ensure reliability and high availability. Nortel recommends using Gigabit Ethernet links for interswitch trunk connectivity to provide enough bandwidth for potential cross traffic. Asynchronous Transfer Mode (ATM) and Packet over SONET (PoS) links are 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 of multicast and broadcast traffic that can be sent to the CPU from a physical port. 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 the multicast packets-per-second value to 6000 pps.

Note that for SMLT ports, CP Limit is enabled by default. Packets that are destined for the control plane (that is, packets that have a QoS level of 7 such as BPDU, OSPF hello) trigger this feature. When the threshold is reached, CP Limit disables the port from which the offending traffic is received. You can enable CP Limit for all ports so that the Metro Ethernet Routing Switch 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 interswitch trunk ports so that these ports are not disabled, which can compromise the stability of SMLT. Do not confuse CP Limit with port rate limiting. Port rate limiting and CP Limit serve different purposes. Port level rate limiting, if enabled, limits all packets with broadcast and multicast addresses to control the amount of user traffic. CP Limit is a protection mechanism for the control plane that only counts packets that are destined for the control plane, or packets that are processed by the CPU with a QoS=7. The CPU can count packets which are not counted by the CP Limit feature. Such packet types can include auto-topology or NetBIOS. The QoS level ensures that control plane traffic (with QoS=7) is processed first in the case of congestion in the CPU buffer.

Nortel Metro Ethernet Routing Switch 8600 Configuration — VLANs, Spanning Tree, and Link Aggregation NN46220-511 04.01 26 June 2009 Copyright © 2007-2009 Nortel Networks. All Rights Reserved.

Link aggregation (MLT, SMLT, LACP)

75

If the actual packets-per-second rate sent from a port exceeds the defined rate, then the port is administratively shut down to protect the CPU from continued bombardment. Disabling interswitch trunk ports in this way can impair network traffic flow, as this is a critical port for SMLT configurations. Nortel recommends that an interswitch multilink trunk contain at least two physical ports. Nortel also recommends that you disable CP-Limit on all physical 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 (CP Limit) arises. Note that, although it is likely that one of the multilink trunk ports (risers) will be disabled in such a condition, traffic continues to flow uninterrupted 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 cp-limit

The Metro Ethernet Routing Switch 8600 also supports the Extended CP Limit feature. For more information about Extended CP Limit, see Configuring Network Management. Other SMLT aggregation switch connections The example shown in Figure 16 "Metro Ethernet Routing Switch 8600 as SMLT aggregation switches" (page 73) includes end stations which connect to each of the switches. In this example, a, b1, b2, c1, c2, and d are clients and printers, while e and f are servers or routers. User access switches B and C can use any method to determine which link of their multilink trunk connections to use to forward a packet, as long as 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. SMLT aggregation switches always send traffic directly to a user access switch, and only use the interswitch trunk for traffic that they cannot forward in another, 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 flows from A to switch E and is forwarded over its direct link to B. Traffic coming from b1 or b2 to a is sent by B on one of its multilink trunk ports. Nortel Metro Ethernet Routing Switch 8600 Configuration — VLANs, Spanning Tree, and Link Aggregation NN46220-511 04.01 26 June 2009 Copyright © 2007-2009 Nortel Networks. All Rights Reserved.

76 Layer 2 operational concepts

B can send traffic from b1 to a on the link to switch E, and traffic from b2 to a on the link to F. In the case of traffic from b1, switch E forwards the traffic directly to switch A, while traffic from b2, which arrived at F, is forwarded 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 multilink trunk to the core. No matter which switch (E or F) it arrives at, it will be sent 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 trunk because it is the shortest path. This is treated as a standard link; SMLT and 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/c2 allows you to have one active VRRP Master per IP subnet. It is passed across the interswitch trunk if switch C sends it to E.

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

•

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

•

When a packet is received, a look-up is performed on the forwarding database. If an entry exists, and if the entry was learned locally from the split multilink trunk or through the interswitch trunk as a remote split multilink trunk, it is forwarded out the local port (the packet should not be sent to the interswitch trunk for forwarding unless there is no local connection). Unknown and Broadcast packets are flooded out all ports that are members of this VLAN.

•

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

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

Nortel Metro Ethernet Routing Switch 8600 Configuration — VLANs, Spanning Tree, and Link Aggregation NN46220-511 04.01 26 June 2009 Copyright © 2007-2009 Nortel Networks. All Rights Reserved.

Link aggregation (MLT, SMLT, LACP)

77

learned from node B. On B, that same entry is shown as being directly learned through MLT-1 because SMLT REMOTE is false. Figure 18 "Network topology for traffic flow example" (page 78) shows the network topology. When a packet arrives at node C destined for 00:E0:7B:B3:04:00, if the SMLT REMOTE status is true, then the switch tries to send the packet out MLT-1 first, rather than through the interswitch trunk. Traffic rarely traverses the interswitch trunk unless there is a failure. If this same packet arrives at B, then it will be forwarded to MLT-1 on the local ports. Figure 17 Output of the command show vlan info fdb-e 10

Nortel Metro Ethernet Routing Switch 8600 Configuration — VLANs, Spanning Tree, and Link Aggregation NN46220-511 04.01 26 June 2009 Copyright © 2007-2009 Nortel Networks. All Rights Reserved.

78 Layer 2 operational concepts Figure 18 Network topology for traffic flow example

SMLT-on-Single-CPU feature Beginning with Metro Ethernet Routing Switch 8600 Software Release 3.5 and continuing through the latest hardware revisions, an enhancement was added to improve SMLT failover behaviors for single CPU/SF configurations. Prior to release 5.2, Nortel required that two switch fabric modules be installed in a chassis running SMLT. This was a requirement because SMLT clients did not reroute traffic around SMLT aggregation switches with a single failed CPU. Thus, packet loss can occur in this rare failure case. The SMLT-on-Single-CPU feature establishes a polling mechanism between the CPU and the interface modules. Because single CPU/SF configurations do not benefit from standard CPU/SF redundancy, in the rare event that a CPU failure occurs on the aggregation switch, this enhancement forces the interface modules offline and allows network redundancy configurations to activate more quickly. You can configure this feature using the CLI. For instructions, see “Configuring SMLT-on-Single-CPU” (page 344).

Nortel Metro Ethernet Routing Switch 8600 Configuration — VLANs, Spanning Tree, and Link Aggregation NN46220-511 04.01 26 June 2009 Copyright © 2007-2009 Nortel Networks. All Rights Reserved.

Link aggregation (MLT, SMLT, LACP)

79

This feature is applicable to all I/O modules capable of supporting the new Single CPU/Switch Fabric reliability enhancement. By default, the SMLT-on-Single-CPU feature is disabled. The SMLT-on-Single-CPU feature can also be implemented on dual SSF/CPU chassis, and is independent of SMLT design. In dual SSF/CPU systems, Nortel recommends that you consider enabling this feature. Its use provides for faster High-Availability-like failover for dual SSF/CPU systems in terms of proper link status. This feature is fully supported on R modules; R modules always operate in this mode independent of configuration settings. R modules have been designed for faster failover without software control. Note that not all versions of Classic modules can support this feature. If nonsupported modules are in a chassis which has this feature enabled, you cannot enable the parameter, and the following error message appears: Chassis configuration inappropriate for this feature. For information about module version support, consult the Metro Ethernet Routing Switch 8600 6.0 Release Notes. The 8608SX/8608SXE modules are an example of nonsupported module types.

Single Port SMLT Single Port SMLT lets you configure a split multilink trunk using a single port. The Single Port SMLT behaves like an MLT-based SMLT, and can coexist with SMLTs in the same system. Single Port SMLT lets you scale the number of split multilink trunks on a switch to the maximum number of available ports. Split multilink trunk links can exist in the following combinations on the SMLT-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 must support MLT.

•

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

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

Nortel Metro Ethernet Routing Switch 8600 Configuration — VLANs, Spanning Tree, and Link Aggregation NN46220-511 04.01 26 June 2009 Copyright © 2007-2009 Nortel Networks. All Rights Reserved.

80 Layer 2 operational concepts

• •

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

•

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

•

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

•

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

•

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

•

LACP is supported on single port split multilink trunks.

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 their behavior.

Split multilink trunk topologies There are four generic topologies in which SMLT can be deployed. The user can choose either a Single Port SMLT configuration, a triangle configuration, 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 8600 multilink trunk Group ID limit for server farm applications. In this case, you can use Single Port SMLT (see Figure 19 "Single Port SMLT topology" (page 81)). This topology allows scaling up to the maximum number of ports on a switch. Any Layer 2 switch capable of link aggregation can be used as the client in this case.

Nortel Metro Ethernet Routing Switch 8600 Configuration — VLANs, Spanning Tree, and Link Aggregation NN46220-511 04.01 26 June 2009 Copyright © 2007-2009 Nortel Networks. All Rights Reserved.

Link aggregation (MLT, SMLT, LACP)

81

Figure 19 Single Port SMLT topology

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

Nortel Metro Ethernet Routing Switch 8600 Configuration — VLANs, Spanning Tree, and Link Aggregation NN46220-511 04.01 26 June 2009 Copyright © 2007-2009 Nortel Networks. All Rights Reserved.

82 Layer 2 operational concepts Figure 20 SMLT triangle topology

SMLT square topology Often used in an enterprise core, the square SMLT configuration provides network resiliency. Figure 21 "SMLT square topology" (page 83) shows this topology.

Nortel Metro Ethernet Routing Switch 8600 Configuration — VLANs, Spanning Tree, and Link Aggregation NN46220-511 04.01 26 June 2009 Copyright © 2007-2009 Nortel Networks. All Rights Reserved.

Link aggregation (MLT, SMLT, LACP) Figure 21 SMLT square topology

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

Nortel Metro Ethernet Routing Switch 8600 Configuration — VLANs, Spanning Tree, and Link Aggregation NN46220-511 04.01 26 June 2009 Copyright © 2007-2009 Nortel Networks. All Rights Reserved.

83

84 Layer 2 operational concepts Figure 22 SMLT full mesh topology

Using MLT-based SMLT with Single Port SMLT You can configure a split multilink trunk with a single port split multilink trunk 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" (page 85) shows how this configuration can be used for upgrading an MLT-based split multilink trunk to a single port split multilink trunk without taking down the split trunk.

Nortel Metro Ethernet Routing Switch 8600 Configuration — VLANs, Spanning Tree, and Link Aggregation NN46220-511 04.01 26 June 2009 Copyright © 2007-2009 Nortel Networks. All Rights Reserved.

Link aggregation (MLT, SMLT, LACP)

85

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

To configure Single Port SMLT using Device Manager, see “Configuring a single port split multilink trunk” (page 216). To configure Single Port SMLT using the CLI, see “Creating a single port split multilink trunk” (page 343).

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

Nortel Metro Ethernet Routing Switch 8600 Configuration — VLANs, Spanning Tree, and Link Aggregation NN46220-511 04.01 26 June 2009 Copyright © 2007-2009 Nortel Networks. All Rights Reserved.

86 Layer 2 operational concepts

With this protocol, the Metro Ethernet Routing Switch 8600 provides a standardized external link aggregation interface to third-party vendor IEEE 802.3ad implementations. This protocol extension provides dynamic link aggregation mechanisms. Advantages of this protocol extension include:

•

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

•

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

•

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

Supported scenarios SMLT/IEEE link aggregation interaction supports all known SMLT scenarios in which an IEEE 802.3ad SMLT pair can be connected to SMLT clients, or in which two IEEE 802.3ad SMLT pairs can be connected to each other in a square or full mesh topology. Non-supported scenarios Some factors leading to failure are:

• •

Wrong ports connected

•

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

•

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

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

Only dual-homed devices will benefit from this enhancement.

Nortel Metro Ethernet Routing Switch 8600 Configuration — VLANs, Spanning Tree, and Link Aggregation NN46220-511 04.01 26 June 2009 Copyright © 2007-2009 Nortel Networks. All Rights Reserved.

Link aggregation (MLT, SMLT, LACP)

87

SMLT network design considerations If you use LACP in a square SMLT topology, LACP must have the same keys for that SMLT LAG; otherwise, the aggregation can fail if a switch failure occurs. Use the following procedure when designing and configuring a SMLT network (for more information, see Network Design Guidelines). Step

Action

1

Define a separate VLAN for the IST protocol: config mlt 1 ist create ip vlan-id

2

Disable CP-Limit on the IST ports: config ethernet cp-limit disable

3

Keep CP-Limit enabled on the split multilink trunk ports and change multicast-limit value to 6000: config ethernet cp-limit enable multicast-limit 6000

4

Disable loop detect on split multilink trunk ports: config ethernet loop-detect disable

5

Enable tagging on split multilink trunk links: config ethernet perform-tagging enable

6

Enable dropping of untagged frames on split multilink trunk links: config ethernet untagged-frames-discard enable --End--

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

SMLT and IP routing This section describes SMLT and IP routing interactions and includes the following topics:

• • •

SMLT and Virtual Router Redundancy Protocol (VRRP) VRRP BackupMaster Routed SMLT (RSMLT) Nortel Metro Ethernet Routing Switch 8600 Configuration — VLANs, Spanning Tree, and Link Aggregation NN46220-511 04.01 26 June 2009 Copyright © 2007-2009 Nortel Networks. All Rights Reserved.

88 Layer 2 operational concepts

SMLT and VRRP

ATTENTION VRRP is supported for IP routing and for services associated with Customer IP VLAN UNIs.

Using VRRP, you can have one active primary router per IP subnet, with all other network VRRP interfaces operating in backup mode. VRRP, when used with SMLT, becomes less efficient. Users that access switches aggregated into two Split-MLT switches send their shared traffic load (based on source and destination MAC or IP addresses) on all uplinks towards the SMLT aggregation switches. VRRP, however, has only one active routing interface enabled. All other interfaces are in backup (standby) mode. In this case, all traffic is forwarded over the IST link towards the primary VRRP switch. Potentially, all traffic that arrives at the VRRP backup interface is forwarded, so there is not enough bandwidth on the IST link to carry all the aggregated riser traffic. However, an enhancement to VRRP overcomes this issue by ensuring that the IST trunk is not used in such a case for primary data forwarding. VRRP BackupMaster

ATTENTION VRRP is supported for IP routing and for services associated with Customer IP VLAN UNIs.

If enabled, the VRRP BackupMaster acts as an IP router for packets destined for the logical VRRP IP address. Thus, all traffic is directly routed to the subnetwork it is destined for, and not Layer 2 switched to the VRRP master. This eliminates a potential limitation in the available interswitch trunk bandwidth. To avoid potential frame duplication problems, the VRRP BackupMaster feature for SMLT can only be used on interfaces that are defined for SMLT. It cannot be used in conjunction with hubs to avoid frame duplication. Also, it cannot be used on brouter or VLAN interfaces. When using SMLT with routing on SMLT aggregation switches, Nortel recommends that you use VRRP for default gateway redundancy. In a VRRP environment, usually one switch is active and the other is backup. For SMLT, an active-active concept can be used by enabling VRRP BackupMaster. The VRRP BackupMaster router will route traffic that is received on the SMLT VLAN, thus avoiding traffic flow across the interswitch trunk. This provides true load sharing abilities.

Nortel Metro Ethernet Routing Switch 8600 Configuration — VLANs, Spanning Tree, and Link Aggregation NN46220-511 04.01 26 June 2009 Copyright © 2007-2009 Nortel Networks. All Rights Reserved.

Link aggregation (MLT, SMLT, LACP)

89

The BackupMaster feature provides an additional benefit. Under normal VRRP operation, a hello packet is sent every second. When three hellos are not received, all switches automatically revert to master mode. This results in a 3 second outage. When you are using VRRP in an SMLT environment, and a link goes down, traffic is automatically forwarded to the remaining ports configured for SMLT VRRP BackupMaster. Because both switches are processing traffic, the node immediately recognizes the VRRP state change, so there is faster failure recovery (less than 1 second). The following sections describe a few guidelines to follow when using VRRP BackupMaster with SMLT:

•

The VRRP virtual IP address and the VLAN IP address cannot be the same.

•

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

•

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

•

Enable hold-down times on both VRRP sides (Master and BackupMaster).

Routed SMLT (RSMLT)

ATTENTION RSMLT is supported for IP routing and for services associated with Customer IP VLAN UNIs.

SMLT subsecond failover benefits are only supported in Layer 2 networks. When routing is involved, depending on the specific routing protocol, this convergence time can cause network interruptions ranging from seconds to minutes. The Nortel RSMLT feature extends the subsecond failover benefit to core topologies by providing an active-active router concept to core SMLT networks. Supported scenarios are split multilink trunk triangle, square, and full mesh topologies, with routing enabled on the core VLANs.

Nortel Metro Ethernet Routing Switch 8600 Configuration — VLANs, Spanning Tree, and Link Aggregation NN46220-511 04.01 26 June 2009 Copyright © 2007-2009 Nortel Networks. All Rights Reserved.

90 Layer 2 operational concepts

Routing protocols can be any of the following protocol types: IP Unicast Static 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 Routing Operations.

Simple Loop Prevention Protocol Simple Loop Prevention Protocol (SLPP) is used at the edge of a network to prevent loops in a SMLT network if Spanning Tree is not used. SLPP is focused on SMLT networks; however, it also works with other configurations. 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 are erroneously directly connected together)

•

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

•

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

You can detect loops with SLPP. You can also use the Metro Ethernet Routing Switch 8600 Loop Detection feature (see “Configuring VLAN Loop Detection” (page 133)). Loop detection is achieved by detecting if a SLPP test packet—called a SLPP-packet data unit (SLPP-PDU)— is received on a peering split multilink trunk switch port or on the same switch from which it originated. If the packet is received by the originating switch, or by a peer aggregation switch 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, the SLPP-PDU eventually returns to the originating port and is received by the CP. The CP disables that port, and a message appears on the console to describe the reason. After a port is disabled, it remains disabled, and manual intervention is required to reenable the port. The port auto-enable feature can be used to reenable the port after a predefined interval.

Nortel Metro Ethernet Routing Switch 8600 Configuration — VLANs, Spanning Tree, and Link Aggregation NN46220-511 04.01 26 June 2009 Copyright © 2007-2009 Nortel Networks. All Rights Reserved.

Simple Loop Prevention Protocol

91

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

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

• •

SLPP-PDUs are forwarded on a per VLAN basis.

•

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

•

SLPP-PDUs are automatically forwarded on all ports of the VLANs that are 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 switch MAC address.

•

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

•

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

•

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

•

The SLPP-PDU packet transmission interval default is 500 milliseconds and 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-PDUs are sent out only on the active MLT UNI port.

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

Nortel Metro Ethernet Routing Switch 8600 Configuration — VLANs, Spanning Tree, and Link Aggregation NN46220-511 04.01 26 June 2009 Copyright © 2007-2009 Nortel Networks. All Rights Reserved.

92 Layer 2 operational concepts

•

The SLPP-PDU can be received by the originating CP or the peer SMLT CP. All other switches treat the SLPP-PDU as a normal multicast packet, ignore it, and forward it to the VLAN.

•

SLPP-PDU transmission and reception only operates on ports for which STP is in forwarding state (if STP is enabled on one switch in the path).

•

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

•

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

— Enable SLPP packet reception only on UNI Ports and SMLT access ports. Never enable it on SMLT IST ports, nor on any NNI ports 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 core SMLT switches so that if a loop is detected, the access ports on both switches does not go down, which avoids SMLT client isolation.

SLPP and UNI Ports When you add a VLAN under global SLPP config, SLPP PDUs are transmitted at a configured interval, on all ports with type NNI of that VLAN. For port types UNI, if a UNI port is part of a VLAN, and that VLAN is added to the SLPP configuration, SLPP PDUs are not sent out on that UNI port. SLPP PDUs are only sent out of UNI ports when those ports are added as part of “add-uni-port” config under global SLPP configuration. SLPP-PDUs are sent out periodically from the UNI ports that are configured at the SLPP global level. The periodicity is also configurable at the global level. SLPP-PDUs sent out of UNI ports are always untagged. Tagged SLPP frames can be received on the UNI port if SLPP is enabled and part of the add-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

Nortel Metro Ethernet Routing Switch 8600 Configuration — VLANs, Spanning Tree, and Link Aggregation NN46220-511 04.01 26 June 2009 Copyright © 2007-2009 Nortel Networks. All Rights Reserved.

SLPP general notes 93

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

SLPP general notes Because SLPP is port-based, a port and all associated I-SID/UNIs on the effected port if a UNI port, will be disabled if it receives SLPP-BDUs on one or more VLANs on a tagged port. For example, if the SLPP packet receive threshold is set to five, a port is shut down if it receives five SLPP-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 is a 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 than 50 SLPP frames) on a heavily-loaded Metro Ethernet Routing Switch 8600, the switch experiences high CPU utilization if a loop occurs. Because of the high Rx-threshold, the switch can become unstable during, and sometimes after, loop clearing. For example, in a network containing an edge switch connected with 32 SLTs to two Metro Ethernet Routing Switch 8600s, the following parameters 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 port rx-threshold values of up to 500 SLPP frames, high values should only be used on lightly-loaded switches. The total number of SLPP sessions (UNI ports + NNI (VLANS)) supported by the MERS-8600 is 60 sessions per chassis. However, there will be no consistency to limit this to 60. To prevent overloading of the CPU and COP, release 6.0 supports the control of aggregate traffic from different ports to the CPU and COP. The Metro Ethernet Routing Switch supports a packet per second rate limit where it discards control frames and CFM frames that are directed to the CPU and COP. SLPP is therefore rate limited.

Nortel Metro Ethernet Routing Switch 8600 Configuration — VLANs, Spanning Tree, and Link Aggregation NN46220-511 04.01 26 June 2009 Copyright © 2007-2009 Nortel Networks. All Rights Reserved.

94 Layer 2 operational concepts

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

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

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 8600 This section describes how to implement VLANs on the Metro Ethernet Routing Switch 8600 and describes default VLANs, unassigned VLANs, and brouter ports. It also summarizes the defaults and rules regarding VLAN creation on the Metro Ethernet Routing Switch 8600. This section includes the following topics:

• • •

“Default VLAN” (page 94) “Unassigned VLAN” (page 94) “Brouter ports” (page 95)

Default VLAN Metro Ethernet Routing Switch 8600 devices are factory configured so that all ports are in a port-based VLAN called the default VLAN. Because all ports are in the default VLAN, the switch behaves like a Layer 2 switch. The VLAN ID of this default VLAN is always 1, and it is always a port-based VLAN. The default VLAN cannot be deleted. The default VLAN feature is only applicable to NNI ports when the NNI is not associated with any PBB or PBT interfaces.

Unassigned VLAN Internally, an Metro Ethernet Routing Switch 8600 supports a placeholder for ports that is called an unassigned port-based VLAN. This concept is used for ports that are removed from all port-based VLANs. Ports can 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 Nortel Metro Ethernet Routing Switch 8600 Configuration — VLANs, Spanning Tree, and Link Aggregation NN46220-511 04.01 26 June 2009 Copyright © 2007-2009 Nortel Networks. All Rights Reserved.

Considerations and limitations 95

port-based VLAN, the port belongs to the unassigned VLAN and the frame is dropped. Only ports in the unassigned VLAN have no spanning tree group association, so these ports do not participate in Spanning Tree Protocol negotiation; that is, no Bridge Protocol Data Units (BPDU) are sent out of ports in the unassigned VLAN. Because it is an internal construct, the unassigned VLAN cannot be deleted. If a user-defined spanning tree group is deleted, the ports are moved to the unassigned VLAN and can later be assigned to another spanning tree group. Moving the ports to the unassigned VLAN avoids creating unwanted loops and duplicate connections. If routing is disabled in these ports, the port is completely isolated and no Layer 2 or Layer 3 functionality is provided. The concept of the unassigned VLAN is useful for security purposes or when using a port for monitoring a mirrored port.

Brouter ports A brouter port is actually a one-port VLAN. The difference between a brouter port and a standard IP protocol-based VLAN configured to do routing is that the routing interface of the brouter port is not subject to the spanning tree state of the port. A brouter port is applicable to customer IP_VLANs; it is not supported when NNI is associated with PBB or PBT interfaces.

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

•

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

•

If you enable tagging on a port that is in a VLAN, the spanning tree group configuration for that port is lost. To preserve VLAN assignment of ports, enable tagging on the ports before you assign the ports to VLANs.

•

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

•

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

•

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

Nortel Metro Ethernet Routing Switch 8600 Configuration — VLANs, Spanning Tree, and Link Aggregation NN46220-511 04.01 26 June 2009 Copyright © 2007-2009 Nortel Networks. All Rights Reserved.

96 Layer 2 operational concepts

•

When Enhanced Operation mode is disabled, a VLAN cannot span multiple spanning tree groups; that is, the ports in the VLAN must all be within one spanning tree group. When Enhanced Operation mode is enabled, VLAN scalability is not affected.

•

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

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

CAUTION Risk of loss of network connectivity When Enhanced Operation mode is enabled, only Metro Ethernet Routing Switch 8600 E, M, or R modules are initialized (other modules are placed offline). To avoid losing modules and network connectivity, replace pre-E, M, or R modules or move the network connections to an E, M, or R module before enabling 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 formulas Figure 25 "Formulas for VLAN scaling" (page 97) shows the formulas used for VLAN scaling.

Nortel Metro Ethernet Routing Switch 8600 Configuration — VLANs, Spanning Tree, and Link Aggregation NN46220-511 04.01 26 June 2009 Copyright © 2007-2009 Nortel Networks. All Rights Reserved.

Considerations and limitations 97 Figure 25 Formulas for VLAN scaling

Maximum VLAN support comparison with Enhanced Operation mode Table 6 "Maximum numbers of port/protocol-based VLANs" (page 97) shows the maximum number of VLANs available with and without Enhanced Operation mode. Table 6 Maximum numbers of port/protocol-based VLANs VLAN type

Maximum VLAN support with enhanced mode enabled

Maximum VLAN support with enhanced mode disabled

MLT

1980

240

IST/SMLT

989

120

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

Enhanced Operation mode setting

Behavior

E, M, or R module

Enable (true)

The module is initialized and comes online. It can be configured with up to 1980 VLANs with MLT.

E, M, or R module

Disable (false)

The module is initialized and comes online. It can be configured with up to 240 VLANs with MLT.

Nortel Metro Ethernet Routing Switch 8600 Configuration — VLANs, Spanning Tree, and Link Aggregation NN46220-511 04.01 26 June 2009 Copyright © 2007-2009 Nortel Networks. All Rights Reserved.

98 Layer 2 operational concepts

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

Enhanced Operation mode setting

Legacy module

Enable (true)

Behavior The module is not initialized and remains offline. The following 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=rcStart chCardIn: can’t initialize a non ETICKET card in enhanced operation mode

Legacy module

Disable (false)

The module is initialized and remains online. It can be configured with up to 240 VLANs with MLT.

Interoperability between operation mode and module type R mode supports the operation of R module-specific features. The modules (pre-E, E, M, and R) that are enabled depend on the operation mode (default, M, or R) and the system configuration. Table 8 "Operation mode and module type interoperability" (page 98) shows this interoperability information. Table 8 Operation mode and module type interoperability Module types Chassis configuration

Operation mode

R

M

E

Pre-E

Same type module chassis

Default

—

—

—

enabled

M

—

—

enabled

—

R

enabled

—

—

—

Default

enabled

enabled

enabled

enabled

M

enabled

enabled

disabled

disabled

R

enabled

disabled

disabled

disabled

Mixed type module chassis

Nortel Metro Ethernet Routing Switch 8600 Configuration — VLANs, Spanning Tree, and Link Aggregation NN46220-511 04.01 26 June 2009 Copyright © 2007-2009 Nortel Networks. All Rights Reserved.

99

.

Configuring VLANs using Device Manager This section describes how to configure VLANs on an Metro Ethernet Routing 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 VLANs To 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, which shows all defined VLANs (Figure 26 "VLAN, Basic tab" (page 100)). The VLAN box appears with the Basic tab displayed, which shows all defined VLANs.

Nortel Metro Ethernet Routing Switch 8600 Configuration — VLANs, Spanning Tree, and Link Aggregation NN46220-511 04.01 26 June 2009 Copyright © 2007-2009 Nortel Networks. All Rights Reserved.

100

Configuring VLANs using Device Manager

Figure 26 VLAN, Basic tab

--End--

For more information, see Table 9 "VLAN, Basic tab fields" (page 100). Table 9 VLAN, 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:

StgId

•

byPort: This VLAN type is the only one supported for EVPN services.

• •

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

• •

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

byProtocolId: This VLAN type cannot be used for EVPN services.

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

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

Nortel Metro Ethernet Routing Switch 8600 Configuration — VLANs, Spanning Tree, and Link Aggregation NN46220-511 04.01 26 June 2009 Copyright © 2007-2009 Nortel Networks. All Rights Reserved.

Configuring port-based VLANs

101

Table 9 VLAN, 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 static members 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 the protocol-based VLAN.

OspfPassiveMembers

The slot/ports of each OSPF passive member.

ProtocolId

Specify the network protocol for protocol-based VLANs. This value is taken from the Assigned Numbers RFC.

• •

ip (IP version 4)

• • • • • • • • • • •

decLat (DEC LAT protocol)

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

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 tab ProtocolId 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 VLANs A port-based VLAN is a VLAN in which the ports are explicitly configured to be in the VLAN.

Nortel Metro Ethernet Routing Switch 8600 Configuration — VLANs, Spanning Tree, and Link Aggregation NN46220-511 04.01 26 June 2009 Copyright © 2007-2009 Nortel Networks. All Rights Reserved.

102

Configuring VLANs using Device Manager

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

• •

“Creating a port-based VLAN” (page 102) “Configuring an IP address for a VLAN” (page 106)

Creating a port-based VLAN To create a port-based VLAN: Step

Action

1

From the Device Manager menu bar, choose VLAN > VLANs. The VLAN box appears with the Basic tab displayed, which shows all defined VLANs (Figure 26 "VLAN, Basic tab" (page 100)).

2

In the Basic tab, click Insert. The VLAN, Insert Basic box appears (Figure 27 "VLAN, Insert Basic box" (page 103)).

Nortel Metro Ethernet Routing Switch 8600 Configuration — VLANs, Spanning Tree, and Link Aggregation NN46220-511 04.01 26 June 2009 Copyright © 2007-2009 Nortel Networks. All Rights Reserved.

Configuring port-based VLANs

103

Figure 27 VLAN, 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 name provided.

•

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

Nortel Metro Ethernet Routing Switch 8600 Configuration — VLANs, Spanning Tree, and Link Aggregation NN46220-511 04.01 26 June 2009 Copyright © 2007-2009 Nortel Networks. All Rights Reserved.

104

Configuring VLANs using Device Manager

4

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

5

In the Type box, select byPort.

6

In the PortMembers box, click the ellipsis (...). The VlanPortMembers box appears (Figure 28 "VlanPortMemb ers" (page 104)). Figure 28 VlanPortMembers

7

Click the ports that are always members. The ports that are selected are recessed, while the non selected ports are not recessed. Port numbers that are dimmed cannot be selected as VLAN port members. (For example, you cannot select ports that do not have the same spanning tree group ID as that of the new VLAN.)

8

Click OK. The Port Membership box closes and the port members appear in the Insert Basic box.

9

In the VLAN, Insert Basic box, click Insert. The Insert box closes and the new VLAN is displayed in the Basic 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 10 VLAN, Insert Basic fields Field

Description

Id

A value that uniquely identifies the virtual LAN associated with this entry. This value corresponds to the lower 12 bits in the IEEE 802.1Q VLAN tag.

Nortel Metro Ethernet Routing Switch 8600 Configuration — VLANs, Spanning Tree, and Link Aggregation NN46220-511 04.01 26 June 2009 Copyright © 2007-2009 Nortel Networks. All Rights Reserved.

Configuring port-based VLANs

105

Table 10 VLAN, 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 is used by the VLAN Manager GUI tool.

Stg Id

Indicates the Spanning Tree Group (STG) used by this VLAN to determine the state of its ports. If this VLAN is not associated with an STG, set StgId to zero. This field is shown only if the switch is in STG mode.

MstpInstance

Indicates the MSTP instance for the VLAN. This field is shown only if the switch is in MSTP mode.

Type

The type of VLAN, distinguished according to the policy used to define 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 static member of a VLAN is always active and is never aged out.

NotAllowtoJoin

The set of ports that are not allowed to become members of this VLAN.

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 only if Type is equal to byIpSubnet. For other VLAN types it must have the value 0.0.0.0.

SubnetMask

The IP subnet mask of this VLAN. This value is meaningful only if Type is equal to byIpSubnet. For other VLAN types it must have the value 0.0.0.0.

ProtocolId

The protocol identifier of this VLAN. This value is meaningful only if Type is equal to byProtocolId. For other VLAN types it must have the value none.

UserDefinedPid

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

Encap

This is the encapsulation type for user defined protocol-based VLANs. This is not meaningful for other types of VLANs. The default value is null.

AgingTime

The timeout period (in seconds) used for aging out FDB entries of this 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.

Nortel Metro Ethernet Routing Switch 8600 Configuration — VLANs, Spanning Tree, and Link Aggregation NN46220-511 04.01 26 June 2009 Copyright © 2007-2009 Nortel Networks. All Rights Reserved.

106

Configuring VLANs using Device Manager

Configuring an IP address for a VLAN To configure an IP address for a VLAN: Step

Action

1

From the Device Manager menu bar, choose VLAN > VLANs. 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 configuring an IP address. The VLAN is highlighted.

3

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

4

Click Insert. The Insert IP Address box appears (Figure 30 "IP, VLAN, Insert IP Address box" (page 106)). Figure 30 IP, 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 Mask appear in the IP, VLAN box.

7

In the IP, VLAN box and the VLAN box, click Close. The IP subnet-based VLAN is configured.

Nortel Metro Ethernet Routing Switch 8600 Configuration — VLANs, Spanning Tree, and Link Aggregation NN46220-511 04.01 26 June 2009 Copyright © 2007-2009 Nortel Networks. All Rights Reserved.

Configuring policy-based VLANs

107

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

Table 11 IP, VLAN fields Field

Description

Interface

Identifies the interface to which this entry is applicable.

Ip Address

The IP address to which addressing information pertains.

NetMask

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

BcastAddrFormat

The IP broadcast address format used on this interface.

ReasmMaxSize

The size of the largest IP packets which this entity can reassemble from incoming IP fragmented packets received on this interface.

VlanId

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

BrouterPort

Indicates whether this entry corresponds to a brouter port (as opposed to a routable VLAN). This value cannot be changed after the row is created.

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

• • • • •

Protocol-based User-defined protocol-based MAC address-based IP subnet-based sVLAN-based

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

This section describes how you can create and configure policy-based VLANs using the following procedures. Nortel Metro Ethernet Routing Switch 8600 Configuration — VLANs, Spanning Tree, and Link Aggregation NN46220-511 04.01 26 June 2009 Copyright © 2007-2009 Nortel Networks. All Rights Reserved.

108

Configuring VLANs using Device Manager

• • • •

“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 VLAN To create a source IP subnet-based VLAN: Step

Action

1

From the Device Manager menu bar, choose VLAN > VLANs. The VLAN box appears with the Basic tab displayed (see Figure 26 "VLAN, Basic tab" (page 100).

2

In the Basic tab, click Insert. 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 the color provided. This color is used by VLAN Manager to visually distinguish the VLANs 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 of the following:

•

PortMembers (use this for VLAN by IpSubnet, Protocolid, or SrcMac)

• •

StaticMembers NotAllowedToJoin

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

Nortel Metro Ethernet Routing Switch 8600 Configuration — VLANs, Spanning Tree, and Link Aggregation NN46220-511 04.01 26 June 2009 Copyright © 2007-2009 Nortel Networks. All Rights Reserved.

Configuring policy-based VLANs

109

Figure 31 VlanPortMembers

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 becomes an active member of the VLAN when a frame is received from the specified source IP address. 10

Click OK. The Port Membership box closes, and the port members appears in 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 for aging out the dynamic VLAN member ports, or use the 600 second 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 IP subnet-based VLAN appears in the Basic tab. --End--

Creating a protocol-based VLAN To create a protocol-based VLAN: Step

Action

1

From the Device Manager menu bar, choose VLAN > VLANs. The VLAN box appears with the Basic tab displayed (see Figure 26 "VLAN, Basic tab" (page 100).

2

In the Basic tab, click Insert.

Nortel Metro Ethernet Routing Switch 8600 Configuration — VLANs, Spanning Tree, and Link Aggregation NN46220-511 04.01 26 June 2009 Copyright © 2007-2009 Nortel Networks. All Rights Reserved.

110

Configuring VLANs using Device Manager

The VLAN, Insert Basic box appears (see Figure 27 "VLAN, Insert Basic box" (page 103). 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 the name provided.

6

(Optional) In the Color Identifier box, select the color, or use the color provided. This color is used by VLAN Manager to visually distinguish the VLANs in a network.

7

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

8

To specify the VLAN port membership, click the ellipsis (...) for one of the following fields.

• • •

Port Members StaticMembers NotAllowedToJoin The VlanPortMembers box appears (see Figure 35 "VlanPortMembers" (page 117)).

9

In the VlanPortMembers box, click each port button to choose the desired membership color.

•

Yellow: Potential members—dynamic (potential members are treated as always members).

• •

Green: Always members—static Red: Never members—not allowed to join

When you have two VLANs with potential members and you want to move ports from one VLAN to the other, you must first change their port membership to Never. Then you can assign the ports to the other VLAN. When a protocol-based VLAN is created, all ports in the underlying STG are automatically added as potential members if they are not already members of an existing protocol-based VLAN of the same type. In a protocol-based VLAN for a Metro Ethernet Routing Switch 8600 module, a potential member becomes an active member of the VLAN when a frame of the specified protocol is received. 10

Click OK. The VlanPortMembers box closes and the port members are added to the Insert Basic box.

Nortel Metro Ethernet Routing Switch 8600 Configuration — VLANs, Spanning Tree, and Link Aggregation NN46220-511 04.01 26 June 2009 Copyright © 2007-2009 Nortel Networks. All Rights Reserved.

Configuring policy-based VLANs

11

111

In the ProtocolId box, select a protocol ID. To configure a non-standard protocol, see “Configuring user-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 the default of 600 seconds.

13

In the QosLevel box, select a level.

14

Click Insert. The VLAN, Insert Basic box closes, and the protocol-based VLAN 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 VLANs You can create user-defined protocol-based VLANs in support of networks with non-standard protocols. To create a user-defined protocol-based VLAN: Step

Action

1

From the Device Manager menu bar, choose VLAN > VLANs. The VLAN box appears with the Basic tab displayed (see Figure 26 "VLAN, Basic tab" (page 100).

2

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

3

In the Type box, select byProtocolId.

4

To specify the VLAN port membership, click the ellipsis (...) for one of the following fields.

• • •

Port Members StaticMembers NotAllowedToJoin The VlanPortMembers box appears (see Figure 35 "VlanPortMembers" (page 117)).

Nortel Metro Ethernet Routing Switch 8600 Configuration — VLANs, Spanning Tree, and Link Aggregation NN46220-511 04.01 26 June 2009 Copyright © 2007-2009 Nortel Networks. All Rights Reserved.

112

Configuring VLANs using Device Manager

5

In the VlanPortMembers box, click each port button to achieve the desired membership color.

• • •

6

Yellow: Potential members—dynamic Green: Always members—static Red: Never members—not allowed to join In a user-defined protocol-based VLAN on a Metro Ethernet Routing Switch 8600 module, a potential member becomes an active member when a frame from the specified protocol is received.

In the ProtocolId box, select usrDefined. The UserDefinedPID field becomes editable and the Encap field becomes active. See the following figure, (Figure 32 "VLAN, Insert Basic" (page 113).

Nortel Metro Ethernet Routing Switch 8600 Configuration — VLANs, Spanning Tree, and Link Aggregation NN46220-511 04.01 26 June 2009 Copyright © 2007-2009 Nortel Networks. All Rights Reserved.

Configuring policy-based VLANs

113

Figure 32 VLAN, Insert Basic

7

In the UserDefinedPID box, enter the protocol ID for the protocol in the format 0x (protocol type in hexadecimal). In the Metro Ethernet Routing Switch 8600 modules, the 16-bit PID assigned to a protocol-based VLAN specifies either an Ethertype or a SNAP PID, depending on whether the frame encapsulation is Ethernet 2, 802.2, or LLC-SNAP, respectively.

Nortel Metro Ethernet Routing Switch 8600 Configuration — VLANs, Spanning Tree, and Link Aggregation NN46220-511 04.01 26 June 2009 Copyright © 2007-2009 Nortel Networks. All Rights Reserved.

114

Configuring VLANs using Device Manager

The following PIDs are not valid:

•

PID0x0000 through 0x05dc: overlaps with the 802.3 frame length

• • • •

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 the default of 600 seconds.

9

In the QosLevel box, select a level.

10

Click Insert. The VLAN, Insert Basic box closes, and the protocol-based VLAN 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 VLAN Before creating a source MAC-based VLAN, you must first enable source MAC address-based VLANs in the system. This section includes the following topics:

•

“Enabling source MAC address-based VLANs on the system” (page 114)

• •

“Configuring a source MAC address-based VLAN” (page 116) “Creating a source MAC address-based VLAN using batch files” (page 118)

Enabling source MAC address-based VLANs on the system To 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. Nortel Metro Ethernet Routing Switch 8600 Configuration — VLANs, Spanning Tree, and Link Aggregation NN46220-511 04.01 26 June 2009 Copyright © 2007-2009 Nortel Networks. All Rights Reserved.

Configuring policy-based VLANs

115

The System Flags tab appears (see Figure 33 "Chassis, System Flags tab" (page 115)). Figure 33 Chassis, System Flags tab

3

Clear the GlobalFilterEnable check box.

•

Global filters are disabled when the GlobalFilterEnable check box is cleared.

•

Global filters are enabled when the GlobalFilterEnable check box is selected.

4

Click Apply.

5

Select the VlanBySrcMacEnable check box.

• 6

Source MAC-based VLANs are enabled when the GlobalFilterEnable check box is selected.

Click Apply. The Chassis box closes and source MAC address-based VLANs are enabled on the system. --End--

Nortel Metro Ethernet Routing Switch 8600 Configuration — VLANs, Spanning Tree, and Link Aggregation NN46220-511 04.01 26 June 2009 Copyright © 2007-2009 Nortel Networks. All Rights Reserved.

116

Configuring VLANs using Device Manager

Configuring a source MAC address-based VLAN Before configuring a source MAC address-based VLAN, you must first enable source MAC address-based VLANs on the system (see “Enabling source MAC address-based VLANs on the system” (page 114). To configure a source MAC-address-based VLAN: Step

Action

1

From the Device Manager menu bar, choose VLAN > VLANs. The VLAN box appears with the Basic tab displayed (see Figure 26 "VLAN, Basic tab" (page 100).

2

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

3

In the Type box, select bySrcMac. The fields needed to set up source MAC-based VLANs become editable. See Figure 34 "VLAN, Insert Basic, bySrcMac" (page 116). Figure 34 VLAN, Insert Basic, bySrcMac

4

In the Id box, enter a unique VLAN ID.

Nortel Metro Ethernet Routing Switch 8600 Configuration — VLANs, Spanning Tree, and Link Aggregation NN46220-511 04.01 26 June 2009 Copyright © 2007-2009 Nortel Networks. All Rights Reserved.

Configuring policy-based VLANs

117

5

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

6

(Optional) In the Color Identifier box, select a color, or use the one provided. This color is used by VLAN Manager to visually distinguish the VLANs in a network.

7

In the StgId box, click the down arrow, and select a spanning tree group ID for the VLAN.

8

To specify the VLAN port membership, click the ellipsis (...) for one of the following fields:

• • •

Port Members StaticMembers NotAllowedToJoin

The VlanPortMembers box appears (see Figure 35 "VlanPortMembers" (page 117)). 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 35 VlanPortMembers

10

Click Ok. The VlanPortMembers box closes, and the selected port members appear in the VLAN, Insert Basic box.

11

In the Aging Time box, specify the timeout period in seconds for aging out the dynamic member ports of the VLAN, or use the default of 600 seconds.

12

(Optional) In the QosLevel box, select a Quality of Service level, or use the default, level 1.

13

Click Insert.

Nortel Metro Ethernet Routing Switch 8600 Configuration — VLANs, Spanning Tree, and Link Aggregation NN46220-511 04.01 26 June 2009 Copyright © 2007-2009 Nortel Networks. All Rights Reserved.

118

Configuring VLANs using Device Manager

The VLAN, Insert Basic box closes, and the VLAN appears on the Basic tab. 14

On the VLAN Basic tab, select the newly created VLAN. The VLAN is highlighted.

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 the VLAN.

18

Click Insert. The Insert MAC VLAN box closes and the MAC address appears in the MAC, VLAN box.

19

Click Close. The MAC, VLAN and VLAN boxes close, and the Source MAC address-based VLAN is configured. --End--

In a source MAC-based VLAN, a potential member becomes an active member of the VLAN when a frame with the specified source MAC address is received.

Creating a source MAC address-based VLAN using batch files Before configuring a source MAC address-based VLAN, you must first enable source MAC address-based VLANs on the system (see “Enabling source MAC address-based VLANs on the system” (page 114)). To create a source MAC address-based VLAN using batch files: Step

Action

1

From the Device Manager menu bar, choose VLAN > VLANs. The VLAN box appears with the Basic tab displayed (see Figure 26 "VLAN, Basic tab" (page 100)).

2

In the VLAN Basic tab, select a source MAC address-based VLAN. The VLAN is highlighted.

3

Click Mac. The MAC, VLAN box appears.

Nortel Metro Ethernet Routing Switch 8600 Configuration — VLANs, Spanning Tree, and Link Aggregation NN46220-511 04.01 26 June 2009 Copyright © 2007-2009 Nortel Networks. All Rights Reserved.

Managing a VLAN

4

119

Click File. The Edit MAC VLAN box appears.

5

Do one of the following:

6

•

To add a MAC address from a file, select Add From File and use the selection box to browse for the file location.

•

To save a MAC address to a file, select it, select Save to File, and use the selection box to browse for a save location.

•

To delete a MAC address, select it, and select Delete Members on Device.

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 VLAN After you have configured a VLAN, you may wish to enable features to improve VLAN performance. This section describes how to configure advanced VLAN operations, such as forwarding, MAC address auto-learning, and Loop Detection. This section includes the following topics:

• • • • • • • • •

“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)

ATTENTION After you create a VLAN, you cannot change the VLAN type. You must first delete the VLAN, and then create a new VLAN of a different type.

Nortel Metro Ethernet Routing Switch 8600 Configuration — VLANs, Spanning Tree, and Link Aggregation NN46220-511 04.01 26 June 2009 Copyright © 2007-2009 Nortel Networks. All Rights Reserved.

120

Configuring VLANs using Device Manager

Changing VLAN port membership To 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 Figure 26 "VLAN, Basic tab" (page 100)). The VLAN box appears with the Basic tag displayed.

2

Double-click the PortMember number for the VLAN whose ports you want to change. The PortMembers box appears (Figure 36 "PortMembers box" (page 120)). Figure 36 PortMembers 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 the Basic tab.

5

Click Apply. The VLAN’s port membership is changed and the VLAN box closes. --End--

Configuring advanced VLAN features The Advanced tab contains information which can be useful in troubleshooting—VlanOperationAction can be especially useful.

Nortel Metro Ethernet Routing Switch 8600 Configuration — VLANs, Spanning Tree, and Link Aggregation NN46220-511 04.01 26 June 2009 Copyright © 2007-2009 Nortel Networks. All Rights Reserved.

Managing a VLAN

121

Step

Action

1

From the Device Manager menu bar, choose VLAN > VLANs. The VLAN box appears with the Basic tab displayed (see Figure 26 "VLAN, Basic tab" (page 100)).

2

Click the Advanced tab. The Advanced tab appears (Figure 37 "VLAN, Advanced tab" (page 121)).

3

Configure the parameters as required. Figure 37 VLAN, Advanced tab

For more information, see Table 12 "VLAN, Advanced tab fields" (page 121). --End--

Table 12 VLAN, 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

Nortel Metro Ethernet Routing Switch 8600 Configuration — VLANs, Spanning Tree, and Link Aggregation NN46220-511 04.01 26 June 2009 Copyright © 2007-2009 Nortel Networks. All Rights Reserved.

122

Configuring VLANs using Device Manager

Table 12 VLAN, 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)

• • • •

decLat (DEC LAT protocol)

• • • • • • •

netBIOS (NetBIOS protocol)

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

decOther (Other DEC protocols) sna802dot2 (IBM SNA on IEEE 802.2 frames) snaEthernet2 (IBM SNA on Ethernet Type 2 frames)

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 tab ProtocolId field. Encap

Specifies the encapsulation method. Values are:

• • • •

Ethernet II SNAP LLC RAW

AgingTime

The timeout period in seconds for aging out the dynamic member ports of policy-based VLANs.

MacAddress

The MAC address assigned to the virtual router interface for this VLAN. This field is relevant only when the VLAN is configured for routing. This MAC address is used as the Source MAC in routed frames, ARP replies, or RIP and OSPF frames.

Nortel Metro Ethernet Routing Switch 8600 Configuration — VLANs, Spanning Tree, and Link Aggregation NN46220-511 04.01 26 June 2009 Copyright © 2007-2009 Nortel Networks. All Rights Reserved.

Managing a VLAN

123

Table 12 VLAN, Advanced tab fields (cont’d.) Field

Description

Vlan Operation Action

One of the following VLAN-related actions:

• • • • • •

flushMacFdb—flush MAC forwarding table for VLAN

•

triggerRipUpdate—set automatic triggered updates for RIP

•

flushSnoopMRtr—flush learned multicast router ports

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 learned multicast group membership

Result

Result code for action.

UserDefinedPid

Specifies the 16-bit user-defined network protocol identifier when the ProtocolID field is set to usrDefined for 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 forwarding The VLAN Forwarding tab configures filtering for the VLAN. Step

Action

1

From the Device Manager menu bar, choose VLAN > VLANs. The VLAN box appears with the Basic tab displayed (see Figure 26 "VLAN, Basic tab" (page 100)).

2

Click the Forwarding tab. The Forwarding tab appears (Figure 38 "VLAN, Forwarding tab" (page 124)).

Nortel Metro Ethernet Routing Switch 8600 Configuration — VLANs, Spanning Tree, and Link Aggregation NN46220-511 04.01 26 June 2009 Copyright © 2007-2009 Nortel Networks. All Rights Reserved.

124

Configuring VLANs using Device Manager Figure 38 VLAN, Forwarding tab

Table 13 "VLAN, Forwarding tab" (page 124) describes the fields in the Forwarding tab, as well as those displayed by clicking the Filter button. Table 13 VLAN, Forwarding tab

3

Field

Description

Address

An address for which the filter has forwarding or filtering information.

VlanId

The ID of the VLAN.

Port

The port number.

Monitor

Select true or false to copy packets with a MAC address in the source or destination field. Used with port mirroring.

QoSLevel

User-assigned Quality of Service level.

SmltRemote

Specifies whether you want to use split multilink trunking.

Status

Values include:

• •

self—one of the bridge addresses

•

mgmt—a static entry

learned—a learned entry that is being used

Click Filter. The VLAN, Forwarding—Filter tab appears (Figure 39 "VLAN, Forwarding, Filter tab" (page 125)).

Nortel Metro Ethernet Routing Switch 8600 Configuration — VLANs, Spanning Tree, and Link Aggregation NN46220-511 04.01 26 June 2009 Copyright © 2007-2009 Nortel Networks. All Rights Reserved.

Managing a VLAN Figure 39 VLAN, Forwarding, Filter tab

4

Configure the filter.

5

Click Filter. --End--

Configuring a VLAN to accept tagged or untagged frames Perform the following steps to configure a VLAN to accept tagged or untagged 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 (see Figure 40 "Port, Interface tab" (page 126)).

Nortel Metro Ethernet Routing Switch 8600 Configuration — VLANs, Spanning Tree, and Link Aggregation NN46220-511 04.01 26 June 2009 Copyright © 2007-2009 Nortel Networks. All Rights Reserved.

125

126

Configuring VLANs using Device Manager Figure 40 Port, Interface tab

3

Click the VLAN tab. The VLAN tab appears. The VLAN tab appears (Figure 41 "Port, VLAN tab" (page 127)).

Nortel Metro Ethernet Routing Switch 8600 Configuration — VLANs, Spanning Tree, and Link Aggregation NN46220-511 04.01 26 June 2009 Copyright © 2007-2009 Nortel Networks. All Rights Reserved.

Managing a VLAN

127

Figure 41 Port, VLAN tab

4

To configure tagging on the port, select the PerformTagging check box. This setting is applied to all VLANs associated with the port. If the check box is selected, tagging is enabled. All frames sent from this port are tagged. You can either discard the tagged frames (step 5) or forward them to a VLAN (go to step 6).

•

If the check box is cleared, tagging is disabled. The port does not send tagged frames. The switch removes the tag before sending the frame out of the port. You can either discard the untagged frames (go to step 5) or forward them to a VLAN (go to step 6).

ATTENTION When you enable tagging on an untagged port, the previous configuration of VLANs, STGs, and MLTs is lost for that port. In addition, the port resets and runs Spanning Tree Protocol, thus breaking connectivity while the protocol goes through the usual blocking and learning states before the forwarding state.

5

Do one of the following:

•

To discard tagged frames on a port for which tagging is disabled, select DiscardTaggedFrames.

•

To discard untagged frames on a port for which tagging is enabled, select DiscardUntaggedFrames.

To optimize performance, on untagged ports in configurations in which you do not expect to see tagged frames, set DiscardTaggedFrames to true. However, on untagged ports for interconnecting switches, set DiscardTaggedFrames to false.

Nortel Metro Ethernet Routing Switch 8600 Configuration — VLANs, Spanning Tree, and Link Aggregation NN46220-511 04.01 26 June 2009 Copyright © 2007-2009 Nortel Networks. All Rights Reserved.

128

Configuring VLANs using Device Manager

6

To designate a default VLAN to associate with discarded frames, enter a VLAN ID in the Default VLAN ID box (or use the default VLAN 1).

7

Click Apply > Close. Tagging is configured for the port. For more information, see Table 14 "Port, VLAN tab" (page 128). --End--

Table 14 Port, VLAN tab Field

Description

PerformTagging

Enable or disable the port on the current VLAN to perform tagging

VlanNames

Identifies which VLANs this port is assigned. Each VLAN ID is stored as a two octet value. The first octet in the pair holds bits 15 to 8 of the VLAN ID, the second octet holds bits 7 to 0 of the VLAN ID.

DiscardTaggedFrames

Determines how to process tagged frames received on this access port. When the flag is set, these frames are discarded by the forwarding process. When the flag is reset, these frames are processed normally.

DiscardUntaggedFrames

Determines how to process untagged frames received on this tagged port. When the flag is set, these frames are discarded by the forwarding process. When the flag is reset, these frames are assigned to the VLAN specified by the DefaultVlanId.

UntagDefaultVLAN

Enables or disables egress tagging on the default VLAN of the port.

DefaultVlanId

The VLAN ID assigned to untagged frames received on this trunk port. This field is meaningless when the port is not a trunk 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 information about this feature, see Configuring IP Routing Operations.

LoopDetectAction

This value is used to specify the action which needs to be taken once a MAC loop is detected on a specific port. They include portDown, vlanBlock, and macDiscard.

Configuring Untagging Default VLAN on a Tagged Port The Untagging Default VLAN on a Tagged Port feature separates untagged packets originating from a PC from the tagged packets originating from an IP phone. Nortel Metro Ethernet Routing Switch 8600 Configuration — VLANs, Spanning Tree, and Link Aggregation NN46220-511 04.01 26 June 2009 Copyright © 2007-2009 Nortel Networks. All Rights Reserved.

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" (page 129)).

4

Select UntagDefaultVlan.

5

Click Apply. Figure 42 VLAN, UntagDefaultVlan

--End--

Configuring MAC address auto-learning on a VLAN You can use MAC address auto-learning to define VLAN ports that you want to automatically learn MAC addresses. To configure MAC address learning for a VLAN:

Nortel Metro Ethernet Routing Switch 8600 Configuration — VLANs, Spanning Tree, and Link Aggregation NN46220-511 04.01 26 June 2009 Copyright © 2007-2009 Nortel Networks. All Rights Reserved.

130

Configuring VLANs using Device Manager

Step

Action

1

From the Device Manager menu bar, choose VLAN > MAC Learning. The VLanMacLearning box appears with the Manual Edit tab displayed (Figure 43 "VLanMacLearning, Manual Edit tab" (page 130)). Figure 43 VLanMacLearning, Manual Edit tab

2

Click Insert. The VLAN MAC Learning, Insert Manual Edit box appears (Figure 44 "VLanMacLearning, Insert Manual Edit box" (page 130)). Figure 44 VLanMacLearning, 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 the available ports (Figure 45 "BridgeManualEditPorts box" (page 131)).

Nortel Metro Ethernet Routing Switch 8600 Configuration — VLANs, Spanning Tree, and Link Aggregation NN46220-511 04.01 26 June 2009 Copyright © 2007-2009 Nortel Networks. All Rights Reserved.

Managing a VLAN

131

Figure 45 BridgeManualEditPorts 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 are added to the Insert Manual Edit box.

6

Click Insert. The Insert Manual Edit box closes and the MAC address and ports 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, Insert Manual Edit tab fields" (page 131) --End--

Table 15 VLAN MAC Learning, Insert Manual Edit tab fields Field

Description

Address

The source MAC address of an entry.

Ports

The allowed ports on which the MAC address of this entry are learned.

Modifying auto-learned MAC addresses Use the Auto Learn tab to change a MAC address that was automatically learned to one that can be manually edited. To modify a MAC address that was automatically learned:

Nortel Metro Ethernet Routing Switch 8600 Configuration — VLANs, Spanning Tree, and Link Aggregation NN46220-511 04.01 26 June 2009 Copyright © 2007-2009 Nortel Networks. All Rights Reserved.

132

Configuring VLANs using Device Manager

Step

Action

1

On the Device Manager menu bar, choose VLAN > MAC Learning. The VlanMacLearning box appears with the Manual Edit tab displayed (see Figure 43 "VLanMacLearning, Manual Edit tab" (page 130)).

2

Click the Auto Learn tab. The Auto Learn tab appears and shows automatically learned MAC addresses (Figure 46 "VLanMacLearning, Auto Learn tab" (page 132)). Figure 46 VLanMacLearning, Auto Learn tab

3

Double-click in the Auto Learn Action field on the address you want 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 16 VLAN Auto Learn tab fields Field

Description

Address

The source MAC address of the auto-learned entries.

Nortel Metro Ethernet Routing Switch 8600 Configuration — VLANs, Spanning Tree, and Link Aggregation NN46220-511 04.01 26 June 2009 Copyright © 2007-2009 Nortel Networks. All Rights Reserved.

Managing a VLAN

133

Table 16 VLAN 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 MAC address entry to a manual edit MAC address entry. The variable provides a mechanism for you to move a MAC address entry from the auto-learned table to the Manual Edit table. Settings:

• •

None convertToManualEdit

Configuring VLAN Loop Detection On a per-port basis, the Loop Detection feature detects MAC addresses that are looping from one port to other ports. After a loop is detected, the port on which the MAC addresses were learned is disabled. Additionally, if a MAC address is found to loop, the MAC address is disabled for that VLAN. 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 the fields in the VLAN tab.

Nortel Metro Ethernet Routing Switch 8600 Configuration — VLANs, Spanning Tree, and Link Aggregation NN46220-511 04.01 26 June 2009 Copyright © 2007-2009 Nortel Networks. All Rights Reserved.

134

Configuring VLANs using Device Manager Figure 47 Port, VLAN loop detect

3

Select the LoopDetect check box.

4

In the LoopDetectAction box, select the action to be taken if a loop is detected. Nortel recommends that you select portDown as opposed to a VLAN shutdown (vlanBlock). If vlanBlock is selected, the VLAN is shut down, not the port. The access switch continues to forward traffic to the port. If portDown is selected, then the access 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.

Nortel Metro Ethernet Routing Switch 8600 Configuration — VLANs, Spanning Tree, and Link Aggregation NN46220-511 04.01 26 June 2009 Copyright © 2007-2009 Nortel Networks. All Rights Reserved.

Managing a VLAN

135

Figure 48 Loop Detected

For more information, see Table 17 "LoopDetected dialog box parameters" (page 135). --End--

Table 17 LoopDetected dialog box parameters Field

Description

PortIndex

Port number.

VlanId

The assigned ID of the VLAN.

Value

Specifies that a loop has been detected (yes), or that no loop has been detected (no).

Configuring directed broadcast on a VLAN You can enable or disable directed broadcast traffic forwarding for an IP interface on the Direct Broadcast tab. To configure directed broadcast for a VLAN: Step

Action

1

From the Device Manager menu bar, choose VLAN > VLANs. The VLAN box appears with the Basic tab displayed (see Figure 26 "VLAN, Basic tab" (page 100)). The VLAN box appears with the Basic tab displayed.

2

Select a VLAN. The VLAN is highlighted.

3

Click IP.

Nortel Metro Ethernet Routing Switch 8600 Configuration — VLANs, Spanning Tree, and Link Aggregation NN46220-511 04.01 26 June 2009 Copyright © 2007-2009 Nortel Networks. All Rights Reserved.

136

Configuring VLANs using Device Manager

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, Direct Broadcast tab" (page 136)). Figure 49 IP, 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 different switches 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 Broadcast tab" (page 136). --End--

Table 18 IP, VLAN Direct Broadcast tab Field

Description

DirectBroadcastEnable

If enabled, an Isolated Routing Port (IRP) can forward directed broadcast traffic. A directed broadcast is a frame sent to the subnet broadcast address on a remote IP subnet. By disabling or suppressing directed broadcast on an interface, all frames sent to the subnet broadcast address for a local router interface are dropped. Disabling this function protects a host from possible denial of service (DoS) attacks.

Nortel Metro Ethernet Routing Switch 8600 Configuration — VLANs, Spanning Tree, and Link Aggregation NN46220-511 04.01 26 June 2009 Copyright © 2007-2009 Nortel Networks. All Rights Reserved.

Managing VLAN bridging

Field

137

Description This feature is enabled by default. With the feature enabled, the CPU does not receive a copy of the directed broadcast. As a result, the switch does not respond to a subnet broadcast ping sent from a remote subnet.

Managing VLAN bridging Bridging occurs at Layer 2 of the Open Systems Interconnect (OSI) model, in which only the MAC address in the packet header is considered when forwarding. With the Metro Ethernet Routing Switch 8600, all bridging is done within the context of a VLAN, in which each VLAN has its own bridging configuration and forwarding table. This section includes the following topics:

• • • • • • •

“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 timeout To configure the forwarding database (FDB) timeout: Step

Action

1

From the Device Manager menu bar, choose VLAN > VLANs. The VLAN box appears with the Basic tab displayed (see Figure 26 "VLAN, Basic tab" (page 100)). The VLAN box appears with the Basic tab displayed.

2

Select a VLAN, and then click Bridge. The Bridge, VLAN box appears with the FDB Aging tab displayed.

Nortel Metro Ethernet Routing Switch 8600 Configuration — VLANs, Spanning Tree, and Link Aggregation NN46220-511 04.01 26 June 2009 Copyright © 2007-2009 Nortel Networks. All Rights Reserved.

138

Configuring VLANs using Device Manager

The Bridge, VLAN box appears with the FDB Aging tab displayed (Figure 50 "Bridge, VLAN, FDB Aging tab" (page 138)). Figure 50 Bridge, VLAN, FDB Aging tab

3

In the FdbAging box, enter an interval, in seconds, for aging out dynamically 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 Aging tab fields" (page 138). --End--

Table 19 Bridge VLAN, FDB Aging tab fields Field

Description

FdbAging

The timeout period (in seconds) used for aging out FDB entries of this VLAN.

Viewing the forwarding database for a specific VLAN The Forwarding tab shows the forwarding database for the VLAN and contains unicast information about bridge forwarding or filtering. This information is used by transparent bridging to determine how to forward a received frame. To view all entries in the forwarding database, for a specific VLAN: Step

Action

1

From the Device Manager menu bar, choose VLAN > VLANs. The VLAN box appears with the Basic tab displayed. Nortel Metro Ethernet Routing Switch 8600 Configuration — VLANs, Spanning Tree, and Link Aggregation NN46220-511 04.01 26 June 2009 Copyright © 2007-2009 Nortel Networks. All Rights Reserved.

Managing VLAN bridging

139

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 tab displayed (see Figure 50 "Bridge, VLAN, FDB Aging tab" (page 138)). The Bridge, VLAN box appears with the FDB Aging tab displayed.

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 51 Bridge, VLAN, Forwarding tab

For more information, see Table 20 "Bridge, VLAN, Forwarding tab fields" (page 139). --End--

Table 20 Bridge, VLAN, Forwarding tab fields Field

Description

Address

A unicast MAC address for which the bridge has forwarding or filtering information.

VlanId

The ID of the VLAN.

Port

Either a value of zero (0) or the port number of the port on which a frame having the specified MAC address was seen. A value of 0 indicates a self-assigned MAC address.

Monitor

Select true or false to copy packets with a MAC address in the source or destination field. Used with port mirroring.

Nortel Metro Ethernet Routing Switch 8600 Configuration — VLANs, Spanning Tree, and Link Aggregation NN46220-511 04.01 26 June 2009 Copyright © 2007-2009 Nortel Networks. All Rights Reserved.

140

Configuring VLANs using Device Manager

Table 20 Bridge, VLAN, Forwarding tab fields (cont’d.) Field

Description

QosLevel

Quality of Service level.

SmltRemote

Specifies whether you want to use SMLT.

Status

Values include:

• • •

self—one of the bridge addresses learned—a learned entry that is being used mgmt—a static entry

Clearing learned MAC addresses from the forwarding database For troubleshooting, you need to manually flush the bridge forwarding database of learned MAC addresses. You can perform this procedure for all MAC addresses as described in the 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 VLAN To clear the forwarding database of learned MAC addresses for a VLAN: Step

Action

1

From the Device Manager menu bar, choose VLAN > VLANs. The VLAN box appears with the Basic tab displayed (see Figure 26 "VLAN, Basic tab" (page 100)). The VLAN box appears with the Basic tab displayed.

2

In the VLAN box, click the Advanced tab. The Advanced tab appears. The Advanced tab appears (Figure 52 "VLAN, Advanced" (page 141)).

Nortel Metro Ethernet Routing Switch 8600 Configuration — VLANs, Spanning Tree, and Link Aggregation NN46220-511 04.01 26 June 2009 Copyright © 2007-2009 Nortel Networks. All Rights Reserved.

Managing VLAN bridging

141

Figure 52 VLAN, Advanced

3

Double-click in the VLAN Operation Action field, and choose FlushMacFdb 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 port To clear learned MAC addresses from the forwarding database for all VLANs by port: Step

Action

1

From the Device Manager main window, select a port. The port is highlighted.

2

From the menu bar, choose Edit > Port > General. The Port box appears with the Interface tab displayed (see Figure 53 "Port, Interface, FlushMacFDB" (page 142)). The Port box appears with the Interface tab displayed.

Nortel Metro Ethernet Routing Switch 8600 Configuration — VLANs, Spanning Tree, and Link Aggregation NN46220-511 04.01 26 June 2009 Copyright © 2007-2009 Nortel Networks. All Rights Reserved.

142

Configuring VLANs using Device Manager Figure 53 Port, Interface, FlushMacFDB

3

In the Action box, select FlushMacFdb.

4

Click Apply. All learned MAC addresses are cleared from the forwarding database (FDB) for VLANs associated with this port.

5

Click Close. --End--

Configuring static forwarding The Static tab contains static forwarding information configured by local or network bridge management. The information is used to specify the set of ports that are allowed to forward frames. Entries are valid for unicast and for group/broadcast addresses.

Nortel Metro Ethernet Routing Switch 8600 Configuration — VLANs, Spanning Tree, and Link Aggregation NN46220-511 04.01 26 June 2009 Copyright © 2007-2009 Nortel Networks. All Rights Reserved.

Managing VLAN bridging

143

To configure forwarding information: Step

Action

1

From the Device Manager menu bar, choose VLAN > VLANs. The VLAN box appears with the Basic tab displayed (see Figure 26 "VLAN, Basic tab" (page 100)). The VLAN box appears with the Basic tab displayed.

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 54 Bridge, 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)).

Nortel Metro Ethernet Routing Switch 8600 Configuration — VLANs, Spanning Tree, and Link Aggregation NN46220-511 04.01 26 June 2009 Copyright © 2007-2009 Nortel Networks. All Rights Reserved.

144

Configuring VLANs using Device Manager Figure 55 Bridge, VLAN, Insert Static box

5

In the MacAddress box, enter a forwarding destination MAC address.

6

In the Port box, click the ellipsis (...). The BridgeStaticPort box appears (Figure 56 "BridgeStaticPort" (page 144)). Figure 56 BridgeStaticPort

7

Select the port on which the frame is received.

8

Click Ok. The Bridge Static Port box closes and the selected port appears in the Insert Static box.

9

To copy packets with a MAC address in the source or destination field, select Monitor.

10

In the QoS box, select a Quality of Service level, or keep the default, level 1. Note that Level 7 is reserved for network control traffic.

11

Click Insert.

Nortel Metro Ethernet Routing Switch 8600 Configuration — VLANs, Spanning Tree, and Link Aggregation NN46220-511 04.01 26 June 2009 Copyright © 2007-2009 Nortel Networks. All Rights Reserved.

Managing VLAN bridging

145

The Insert Static box closes and the static information appears in the Bridge, VLAN Static tab. 12

Click Close. The static forwarding information is configured, and the Bridge VLAN box closes. For more information, see Table 21 "Bridge VLAN static fields" (page 145). --End--

Table 21 Bridge VLAN static fields Field

Description

MacAddress

The destination MAC address in a frame to which the forwarding information for this entry applies. This object can take the value of a unicast address.

Port

The port number of the port on which the frame is received.

Monitor

Setting to copy packets with a MAC address in the source or destination field. Used with port mirroring. In Static tab, display = true or false.

QosLevel

Quality of Service level.

Status

Specifies the status of this entry. Select one of the following values:

•

permanent—in use and remains so after the next bridge reset. This is the default value.

•

deleteOnReset—in use and remains so until the next bridge reset.

•

deleteOnTimeout—currently in use and remains so until it is aged.

•

other—in use but the conditions under which it remains so are different from other values.

MAC-layer bridge packet filtering To perform MAC-layer bridging, the switch must know the destination MAC-layer address of each device on each attached network so it can forward packets to the appropriate destination. MAC-layer addresses are stored in the bridging table, and you can filter packet traffic based on the destination MAC-layer address information.

Nortel Metro Ethernet Routing Switch 8600 Configuration — VLANs, Spanning Tree, and Link Aggregation NN46220-511 04.01 26 June 2009 Copyright © 2007-2009 Nortel Networks. All Rights Reserved.

146

Configuring VLANs using Device Manager

For MAC address filtering, the Metro Ethernet Routing Switch 8600 supports Bridge Management Information Base (MIB) filtering (RFC 1493). The number of MAC filters is limited to 100. You can create a filter entry in much the same way as you create a static MAC entry, by entering a MAC address and the port on which it resides. In the MAC filter record, you can also specify ports to discard source or destination packets for the MAC address on a port. Global MAC filtering eliminates the need for configuring multiple per-VLAN filter records for the same MAC. It provides the ability to discard a list of MAC addresses, globally, on the switch. By using a global list you do not have to configure a MAC per VLAN.

Configuring static multicast To 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 required ports.

5

Click the button beside MltIds to select the required MLT.

6

Click Insert. --End--

Configuring a MAC-layer bridge filter To configure a MAC layer bridge filter: Step

Action

1

From the Device Manager menu bar, choose VLAN > VLANs. The VLAN box appears with the Basic tab displayed (see Figure 26 "VLAN, Basic tab" (page 100)). The VLAN box appears with the Basic tab displayed.

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)).

Nortel Metro Ethernet Routing Switch 8600 Configuration — VLANs, Spanning Tree, and Link Aggregation NN46220-511 04.01 26 June 2009 Copyright © 2007-2009 Nortel Networks. All Rights Reserved.

Managing VLAN bridging

147

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 57 Bridge, 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 58 Bridge, VLAN, Insert Filter box

5

In the MacAddress box, enter the MAC address used to match the destination address of incoming packets.

6

In the Port box, click the ellipsis (...). The BridgeFilterPort box appears (Figure 59 "BridgeFilterPort" (page 148)).

Nortel Metro Ethernet Routing Switch 8600 Configuration — VLANs, Spanning Tree, and Link Aggregation NN46220-511 04.01 26 June 2009 Copyright © 2007-2009 Nortel Networks. All Rights Reserved.

148

Configuring VLANs using Device Manager Figure 59 BridgeFilterPort

7

Click the port on which this MAC address is found, and then click OK. The BridgeFilterPort box closes and the port is added to the Port box 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 60 BridgeFilterSrcDiscard box

9

Click the ports from which you do not want packet traffic received by this MAC address, and then click Ok. The box closes and the ports are added to the SrcDiscard field in the Bridge, VLAN, Insert Filter box.

10

In the DestDiscard box, click the ellipsis (...). The BridgeFilterDestDiscard box appears (Figure 61 "BridgeFilterDestDiscard box" (page 149)).

Nortel Metro Ethernet Routing Switch 8600 Configuration — VLANs, Spanning Tree, and Link Aggregation NN46220-511 04.01 26 June 2009 Copyright © 2007-2009 Nortel Networks. All Rights Reserved.

Managing VLAN bridging

149

Figure 61 BridgeFilterDestDiscard box

11

Click the ports to which you do not want packet traffic sent from this MAC address, and then click Ok. The box closes and the ports are added to the DestDiscard box in 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 Filter tab.

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 22 Bridge VLAN Filter fields Field

Description

MacAddress

The MAC address of this entry. This address is used to match the destination address of incoming packets.

Port

Port on which this MAC address is found.

VlanId

The ID of the VLAN.

SrcDiscard

Specify a set of ports. Traffic arriving on any of the specified ports is not forwarded to this MAC address.

DestDiscard

Specify a set of ports. Traffic arriving on any of the specified ports from this MAC address is discarded.

Nortel Metro Ethernet Routing Switch 8600 Configuration — VLANs, Spanning Tree, and Link Aggregation NN46220-511 04.01 26 June 2009 Copyright © 2007-2009 Nortel Networks. All Rights Reserved.

150

Configuring VLANs using Device Manager

Table 22 Bridge VLAN Filter fields (cont’d.) Field

Description

Status

Specifies the status of the VLAN. Values include:

• • • Pcap

self—one of the bridge addresses learned—a learned entry that is being used mgmt—a static entry

Enable or disable the Packet Capture Tool (PCAP) for the MAC address (FDB filter). For more information about PCAP, see Using the Packet Capture Tool .

Configuring the Global MAC filter Global MAC filtering eliminates the need for configuring multiple per-VLAN filter records for the same MAC. It provides the ability to discard a list of MAC addresses, globally, on the switch. By using a global list you do not have to configure a MAC per VLAN. To configure the Global MAC filter: Step

Action

1

From the Device Manager window, select VLAN > Global Mac Filtering. The GlobalMacFiltering tab appears (Figure 62 "GlobalMacFiltering tab" (page 150)). Figure 62 GlobalMacFiltering tab

Table 23 "GlobalMacFiltering tab fields" (page 151) describes the fields on the GlobalMacFiltering tab. 2

Click Insert. The GlobalMacFiltering, Insert Mac Filter box appears Figure 63 "GlobalMacFiltering, Insert Mac Filter box" (page 151) .

Nortel Metro Ethernet Routing Switch 8600 Configuration — VLANs, Spanning Tree, and Link Aggregation NN46220-511 04.01 26 June 2009 Copyright © 2007-2009 Nortel Networks. All Rights Reserved.

Configuring Enhanced Operation mode

151

Figure 63 GlobalMacFiltering, Insert Mac Filter box

3

In the GlobalMacFilterAddress box, enter the address, and then click Insert. The address you entered appears in the GlobalMacFiltering tab. . --End--

Table 23 GlobalMacFiltering tab fields Field

Description

GlobalMacFilterAddress

A MAC address which the switch discards globally.

Configuring Enhanced Operation mode With Enhanced Operation mode, you can now increase the maximum number of VLANs when you use MultiLink Trunking to 1980 (1972 if R modules are present in the chassis) and to 989 when you use SMLT. Enhanced Operation mode requires Metro Ethernet Routing Switch 8600 E, M, or R modules.

CAUTION When Enhanced Operation mode is enabled, only Metro Ethernet Routing Switch 8600 E, M, or R modules are initialized (other modules are placed offline). To avoid losing modules and network connectivity, replace pre-E, M, or R modules or move the network connections to an E, M, or R module before enabling 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.

Nortel Metro Ethernet Routing Switch 8600 Configuration — VLANs, Spanning Tree, and Link Aggregation NN46220-511 04.01 26 June 2009 Copyright © 2007-2009 Nortel Networks. All Rights Reserved.

152

Configuring VLANs using Device Manager

The System Flags tab appears. The System Flags tab appears (Figure 64 "Chassis, System Flags tab" (page 152)). Figure 64 Chassis, System Flags tab

3

Select the NewEnhancedOperMode check box.

4

Click Apply. The system notifies you that the setting takes effect after save and reboot.

5

Click the System tab. The System tab appears. The System tab appears (Figure 65 "Chassis, System SaveRuntimeConfig" (page 153)).

Nortel Metro Ethernet Routing Switch 8600 Configuration — VLANs, Spanning Tree, and Link Aggregation NN46220-511 04.01 26 June 2009 Copyright © 2007-2009 Nortel Networks. All Rights Reserved.

Configuring Enhanced Operation mode Figure 65 Chassis, System SaveRuntimeConfig

6

In the ActionGroup1 box, select saveRuntimeConfig.

7

Click Apply > Close. --End--

Enhanced Operation mode is configured.

Nortel Metro Ethernet Routing Switch 8600 Configuration — VLANs, Spanning Tree, and Link Aggregation NN46220-511 04.01 26 June 2009 Copyright © 2007-2009 Nortel Networks. All Rights Reserved.

153

154

Configuring VLANs using Device Manager

Nortel Metro Ethernet Routing Switch 8600 Configuration — VLANs, Spanning Tree, and Link Aggregation NN46220-511 04.01 26 June 2009 Copyright © 2007-2009 Nortel Networks. All Rights Reserved.

155

.

Configuring spanning tree using Device Manager This section discusses using Device Manager to create, manage, and monitor spanning tree groups (STG), and discusses using Device Manager to configure Spanning Tree Protocol (STP), and Multiple Spanning Tree Protocol (MSTP). This section includes the following topics:

• • •

“Choosing the spanning tree mode” (page 155) “Configuring Spanning Tree Protocol” (page 156) “Configuring Multiple Spanning Tree Protocol” (page 169)

Choosing the spanning tree mode You can choose to use STP, or MSTP with the Metro Ethernet Routing Switch 8600. To configure the mode: Step

Action

1

From the Device Manager menu bar, choose VLAN > Spanning Tree > Globals. The Spanning Tree Globals box appears (Figure 66 "Spanning Tree, Globals" (page 156)).

Nortel Metro Ethernet Routing Switch 8600 Configuration — VLANs, Spanning Tree, and Link Aggregation NN46220-511 04.01 26 June 2009 Copyright © 2007-2009 Nortel Networks. All Rights Reserved.

156

Configuring spanning tree using Device Manager Figure 66 Spanning Tree, Globals

2

Select the required spanning tree mode.

3

Click Apply.

ATTENTION After you change the mode, you must reboot the switch for changes to take effect. You can reboot the switch using the command line interface (CLI) by first saving the boot file with the command save bootconfig, and then entering the command boot , where filename is the saved boot config file. You can also reboot the switch using Device Manager. Go to Edit > Chassis. In the ActionGroup1 box, select saveBootConfig. Click Apply. Next, in ActionGroup4, select softReset. Click Apply.

--End--

Configuring Spanning Tree Protocol This section discusses using Device Manager to create, manage, and monitor spanning tree groups. This section includes the following topics:

• • • • • • • •

“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)

Nortel Metro Ethernet Routing Switch 8600 Configuration — VLANs, Spanning Tree, and Link Aggregation NN46220-511 04.01 26 June 2009 Copyright © 2007-2009 Nortel Networks. All Rights Reserved.

Configuring Spanning Tree Protocol

157

Creating a STG A network can include multiple instances of STP. The collection of ports in one spanning tree instance is called a spanning tree group (STG). The Metro Ethernet Routing Switch 8600 supports STP and up to 64 spanning tree groups. This information applies to Metro Ethernet Routing Switch 8600 modules only. Spanning Tree Protocol must be disabled on split multilink trunking (SMLT) or interswitch trunk ports, because spanning tree is not a supported configuration on these ports. To create a STG: Step

Action

1

From the Device Manager menu bar, choose VLAN > Spanning Tree > STG. The STG, Configuration tab appears (Figure 67 "STG, Configuration tab" (page 157)). Figure 67 STG, 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)

Nortel Metro Ethernet Routing Switch 8600 Configuration — VLANs, Spanning Tree, and Link Aggregation NN46220-511 04.01 26 June 2009 Copyright © 2007-2009 Nortel Networks. All Rights Reserved.

158

Configuring spanning tree using Device Manager Figure 68 STG, Insert Configuration

3

Use the fields in the STG, Insert Configuration box to configure the STG. In the STG table, the STG ID and TaggedBpduVlanId must be unique. If you change the STG ID without updating TaggedBpduVlandId, the insertion can fail because of a duplicate TaggedBpduVlanId.

4

In the PortMembers box, click the ellipses ( ... ). The StgPortMembers box (Figure 69 "StgPortMembers" (page 158)) appears. Figure 69 StgPortMembers

Nortel Metro Ethernet Routing Switch 8600 Configuration — VLANs, Spanning Tree, and Link Aggregation NN46220-511 04.01 26 June 2009 Copyright © 2007-2009 Nortel Networks. All Rights Reserved.

Configuring Spanning Tree Protocol

5

159

Click the ports you want to add to the STG, and then click Ok. The StgPortMembers box closes, and the ports are added to the Port Members field in the Insert Configuration box. Spanning Tree Protocol must be disabled on SMLT or interswitch trunk ports.

6

Click Insert. The Insert Configuration box closes, and the STG appears in the Configuration tab.

7

Click Close. The STG is configured. For more information, see Table 24 "STG configuration fields" (page 159). --End--

Table 24 STG configuration fields Field

Description

Id

The ID number for the STG. The STG ID and TaggedBpduVlanId must be unique in the STG table. If you change the STG ID without updating TaggedBpduVlanId, the insertion can fail because 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 bridges use for MaxAge when this bridge is acting as the root. The 802.1d-1990 standard specifies that the BridgeMaxAge range is related to the value of BridgeHelloTime. The default is 2000 (20 seconds).

Nortel Metro Ethernet Routing Switch 8600 Configuration — VLANs, Spanning Tree, and Link Aggregation NN46220-511 04.01 26 June 2009 Copyright © 2007-2009 Nortel Networks. All Rights Reserved.

160

Configuring spanning tree using Device Manager

Table 24 STG configuration fields (cont’d.) Field

Description

BridgeHelloTime

The value in hundredths of a second that all bridges use for HelloTime when this bridge is acting as the root. The granularity of this timer is specified by the IEEE 802.1d-1990 standard to be in increments of 1/100 of a second. The default is 200 (2 seconds).

BridgeForwardDelay

The value in hundredths of a second that all bridges use for forward delay when this bridge is acting as the root. The default is 1500 (15 seconds).

EnableSTP

Enables or disables the spanning tree algorithm for the STG.

StpTrapEnable

Enables SNMP traps to be sent to trace receiver every time an STP topology occurs.

TaggedBpduAddress

Represents a MAC address; specifically for tagged BPDUs.

TaggedBpduVlanId

Represents the VLAN tag associated with the STG. This ID is used to tag BPDUs through a non-IEEE tagging bridge to another Metro Ethernet Routing Switch 8600. By default, the TaggedBpduVlanId is an address calculated based on the STG ID by Device Manager. Accepting the default value calculated by Device Manager makes it much simpler to coordinate STGs across multiple switches. If you enter a custom value for this field, you must manually coordinate it across all switches. The STG ID and TaggedBpduVlanId must be unique in the STG table. If you change the STG ID without updating TaggedBpduVlanId, the insertion can fail because of a duplicate TaggedBpduVlanId.

Port Members

The ports you want to become members of the new STG.

Nortel Metro Ethernet Routing Switch 8600 Configuration — VLANs, Spanning Tree, and Link Aggregation NN46220-511 04.01 26 June 2009 Copyright © 2007-2009 Nortel Networks. All Rights Reserved.

Configuring Spanning Tree Protocol

161

Table 24 STG configuration fields (cont’d.) Field

Description You cannot select a port if it is:

NtStgEnable

•

configured as Single Port SMLT, MLT-based SMLT, or IST

•

configured as members of any other STG

Indicates whether this STG is operating in Nortel mode or in Cisco mode:

• •

true—Nortel mode false—Cisco mode

Untagged ports can belong to only one STG.

Editing an STG The information about editing an STG applies to Metro Ethernet Routing Switch 8600 modules only. To edit an STG: Step

Action

1

From the Device Manager menu bar, choose VLAN > Spanning Tree > STG. 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 STG To add ports to a spanning tree group:

Nortel Metro Ethernet Routing Switch 8600 Configuration — VLANs, Spanning Tree, and Link Aggregation NN46220-511 04.01 26 June 2009 Copyright © 2007-2009 Nortel Networks. All Rights Reserved.

162

Configuring spanning tree using Device Manager

Step

Action

1

From the Device Manager menu bar, choose VLAN > Spanning Tree > STG. 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 to this STG. Figure 70 StgPortMembers 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 the Port 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 status You can use the STG Status tab to view the status of the spanning tree for each STG that is associated with the network. To view STG status: Step

Action

1

From the Device Manager menu bar, choose VLAN > Spanning Tree > STG. Nortel Metro Ethernet Routing Switch 8600 Configuration — VLANs, Spanning Tree, and Link Aggregation NN46220-511 04.01 26 June 2009 Copyright © 2007-2009 Nortel Networks. All Rights Reserved.

Configuring Spanning Tree Protocol

163

The STG, Configuration tab appears (Figure 67 "STG, Configuration tab" (page 157)). 2

Click the Status tab. The Status tab appears (Figure 71 "STG, Status tab" (page 163)), displaying the STG status. Figure 71 STG, Status tab

For more information, see Table 25 "STG Status fields" (page 163). --End--

Table 25 STG Status fields Field

Description

BridgeAddress

The MAC address used by this bridge when it must be referred to in a unique fashion.

NumPorts

The number of ports controlled by this bridging entity.

ProtocolSpecification

An indication of what version of the Spanning Tree Protocol is being run. The IEEE 802.1d implementations return ieee8021d.

TimeSinceTopologyC hange

The time in hundredths of a second since the last time a topology change was detected by the bridge entity or STG.

Nortel Metro Ethernet Routing Switch 8600 Configuration — VLANs, Spanning Tree, and Link Aggregation NN46220-511 04.01 26 June 2009 Copyright © 2007-2009 Nortel Networks. All Rights Reserved.

164

Configuring spanning tree using Device Manager

Table 25 STG Status fields (cont’d.) Field

Description

TopChanges

A topology change trap is sent by a bridge when any of its configured ports transitions from the Learning state to the Forwarding state, or from the Forwarding state to the Blocking state. The trap is not sent if a new root trap is sent for the same transition. Implementation of this trap is optional.

DesignatedRoot

The bridge identifier of the root of the spanning tree as determined by the Spanning Tree Protocol as executed by this node. This value is used as the Root Identifier parameter in all Configuration Bridge PDUs originated by this node.

RootCost

The cost of the path to the root as seen from this bridge.

RootPort

The port number of the port that offers the lowest cost path from this bridge to the root bridge.

MaxAge

The maximum age of Spanning Tree Protocol information learned from the network on any port before it is discarded, in units of hundredths of a second. This is the actual value that this bridge is currently using.

HelloTime

The amount of time in hundredths of a second between transmission of config BPDUs by this node on any port when it is the root of the spanning tree. The default value is 200 (2 seconds).

HoldTime

The time interval in hundredths of a second during which no more than two configuration bridge PDUs shall be transmitted by this node. The default value is 100 (1 second).

ForwardDelay

The time interval in hundredths of a second that controls how fast a port changes its spanning state when moving toward the Forwarding state. The value determines how long the port stays in each of the Listening and Learning states, which precede the Forwarding state. This value is also used when a topology change is detected and is under way, to age all dynamic entries in the Forwarding Database. Note that this value is the one this bridge is currently using, in contrast to StgBridgeForwardDelay, which is the value that this bridge and all others would use if this bridge becomes the root. The default value is 1500 (15 seconds).

Nortel Metro Ethernet Routing Switch 8600 Configuration — VLANs, Spanning Tree, and Link Aggregation NN46220-511 04.01 26 June 2009 Copyright © 2007-2009 Nortel Networks. All Rights Reserved.

Configuring Spanning Tree Protocol

165

Viewing STG ports Use the Ports tab to view the status of ports for each STG that is associated with the network. To view STG ports: Step

Action

1

From the Device Manager menu bar, choose VLAN > Spanning Tree > STG. The STG, Configuration tab appears (Figure 67 "STG, Configuration tab" (page 157)).

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 72 STG, Ports tab

For more information, see Table 26 "STG Ports tab fields" (page 165). --End--

Table 26 STG Ports tab fields Field

Description

Port

The port number of the port for which this entry contains Spanning Tree Protocol management information.

StgId

The STG identifier assigned to this port.

Nortel Metro Ethernet Routing Switch 8600 Configuration — VLANs, Spanning Tree, and Link Aggregation NN46220-511 04.01 26 June 2009 Copyright © 2007-2009 Nortel Networks. All Rights Reserved.

166

Configuring spanning tree using Device Manager

Table 26 STG Ports tab fields (cont’d.) Field

Description

Priority

The value of the priority field which is contained in the first octet of the Port 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 Metro Ethernet 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 Spanning Tree Protocol: disabled blocking listening learning forwarding broken This state controls what action a port takes on reception of the frame. If the bridge has detected a port that is malfunctioning, it places that port into the broken state. For ports that are disabled, this object has a value of 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 are dropped and not processed, and no BPDU is generated.

FastStart

When this flag is set, the port is moved straight to the forwarding state upon 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 for Spanning Tree Protocol (STP), in which a port enters the blocking state following the initialization of the bridging device or from the disabled state when the port is enabled through configuration.

Nortel Metro Ethernet Routing Switch 8600 Configuration — VLANs, Spanning Tree, and Link Aggregation NN46220-511 04.01 26 June 2009 Copyright © 2007-2009 Nortel Networks. All Rights Reserved.

Configuring Spanning Tree Protocol

167

Table 26 STG Ports tab fields (cont’d.) Field

Description

PathCost

The contribution of this port to the path cost of paths toward the spanning tree root that includes this port. The 802.1d-1990 protocol recommends that the default value of this parameter be inversely proportion to the speed of the attached LAN.

DesignatedRoot

The unique bridge identifier of the bridge recorded as the root in the configuration BPDUs transmitted by the designated bridge for the segment to which the port is attached.

DesignatedCost

The path cost of the designated port of the segment connected to this port. This value is compared to the Root Path Cost field in received bridge PDUs.

DesignatedBridge

The bridge identifier of the bridge that this port considers to be the designated bridge for this port’s segment.

DesignatedPort

The port identifier of the port on the designated bridge for this port segment.

ForwardTransitions

The number of times this port has transitioned from the learning state to the forwarding state.

ChangeDetection

The change detection setting (true or false) for this port. Can only be configured on access ports. If you enable change detection on an MLT with access ports, the setting is automatically applied to all ports in the MLT.

Enabling STP on a port To enable STP for a port: Step

Action

1

From the Device Manager menu bar, choose VLAN > Spanning Tree > STG. The STG, Configuration tab appears (Figure 67 "STG, Configuration tab" (page 157)).

2

Click the Ports tab. 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.

Nortel Metro Ethernet Routing Switch 8600 Configuration — VLANs, Spanning Tree, and Link Aggregation NN46220-511 04.01 26 June 2009 Copyright © 2007-2009 Nortel Networks. All Rights Reserved.

168

Configuring spanning tree using Device Manager

STP is enabled for the port. --End--

Deleting an STG The deleting an STG procedure applies to Metro Ethernet Routing Switch 8600 modules only. To delete an STG: Step

Action

1

From the Device Manager menu bar, choose VLAN > Spanning Tree > STG. The STG box appears (Figure 67 "STG, Configuration tab" (page 157)).

2

Click the STG that you want to delete.

3

Click Delete. All VLANs must be deleted from an STG before you can remove the STG. --End--

Configuring STG topology change detection To configure topology change detection on a port: Step

Action

1

From the Device Manager menu bar, choose VLAN > Spanning Tree > STG. The STG, Configuration tab appears (Figure 67 "STG, Configuration tab" (page 157)).

2

Click the Ports tab. 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.

Nortel Metro Ethernet Routing Switch 8600 Configuration — VLANs, Spanning Tree, and Link Aggregation NN46220-511 04.01 26 June 2009 Copyright © 2007-2009 Nortel Networks. All Rights Reserved.

Configuring Multiple Spanning Tree Protocol

5

169

Click Apply. Change detection is configured for the port. --End--

Configuring Multiple Spanning Tree Protocol To configure MSTP, you must first enable it. For more information about enabling MSTP, see “Choosing the spanning tree 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 globally To configure MSTP globally: Step

Action

1

From the Device Manager menu bar, choose VLAN > Spanning Tree > MSTP. The MSTP, Globals tab appears (Figure 73 "MSTP, Globals" (page 170)).

Nortel Metro Ethernet Routing Switch 8600 Configuration — VLANs, Spanning Tree, and Link Aggregation NN46220-511 04.01 26 June 2009 Copyright © 2007-2009 Nortel Networks. All Rights Reserved.

170

Configuring spanning tree using Device Manager Figure 73 MSTP, Globals

2

Edit desired fields to configure MSTP.

3

Click Apply. For more information, see Table 27 "MSTP, Globals fields" (page 171). --End--

Nortel Metro Ethernet Routing Switch 8600 Configuration — VLANs, Spanning Tree, and Link Aggregation NN46220-511 04.01 26 June 2009 Copyright © 2007-2009 Nortel Networks. All Rights Reserved.

Configuring Multiple Spanning Tree Protocol

171

Table 27 MSTP, Globals fields Field

Description

TxHoldCount

The value used by the port transmit state machine to limit the maximum transmission rate.

MaxHopCount

Indicates the maximum hop count. 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 value which is not a whole number of seconds.

NoOfInstancesSupported

Indicates the maximum number of spanning tree instances supported.

MstpUpCount

The number of times the MSTP module was enabled. A trap is generated on the occurrence of this event.

MstpDownCount

The number of times the MSTP module was disabled. A trap is generated 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 as specified in IEEE 802.1d is in use; and mstp indicates that the Multiple Spanning Tree Protocol as specified in IEEE 802.1s is in use.

BrgAddress

The MAC address used by this bridge when it must be referred to in a unique fashion. Nortel recommends that this be the numerically smallest MAC address of all ports that belong to this bridge. When concatenated with MstCistBridgePriority or MstBridgePriority, a unique bridge identifier is formed which is used in the Spanning Tree Protocol.

Root

The bridge identifier of the root of the common spanning tree as determined by the Spanning Tree Protocol by this node. This value is used as the CIST root identifier parameter in all configuration bridge PDUs originated by this node.

RegionalRoot

The bridge identifier of the root of the multiple spanning tree region as determined by the Spanning Tree Protocol as executed by this node. This value is used as the CIST regional root identifier parameter 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 from this bridge to the CIST root bridge.

BridgePriority

The value of the writable portion of the bridge identifier comprising of the first two octets. The values you enter for bridge priority must be in steps of 4096.

Nortel Metro Ethernet Routing Switch 8600 Configuration — VLANs, Spanning Tree, and Link Aggregation NN46220-511 04.01 26 June 2009 Copyright © 2007-2009 Nortel Networks. All Rights Reserved.

172

Configuring spanning tree using Device Manager

Table 27 MSTP, Globals fields (cont’d.) Field

Description

BridgeMaxAge

The value that all bridges use for MaxAge when this bridge acts as the 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 value which is not a whole number of seconds. The default is 2000.

BridgeForwardDelay

The value that all bridges use for forward delay when this bridge acts as the root. Note that 802.1d specifies that the range for this parameter is related to the value of BridgeMaxAge. 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 value which is not a whole number of seconds. The default is 1500.

HoldTime

This time value determines the interval length during which no more than 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 learned from the network on any port before it is discarded, in units of hundredths of a second. This is the value that this bridge currently uses.

ForwardDelay

This time value, measured in units of hundredths of a second, controls how fast a port changes its spanning state when moving towards the forwarding state. The value determines how long the port stays in a particular state before moving to the next state.

TimeSinceTopology Change

The time (in hundredths of a second) since the TcWhile Timer for any port in this bridge was non-zero for Common Spanning Tree.

TopChanges

The number of times that there was at least one non-zero TcWhile Timer on this bridge for Common Spanning Tree.

NewRootBridgeCount

The number of times this bridge has detected a root bridge change for Common Spanning Tree. A trap is generated on the occurrence of this event.

RegionName

The name for the region configuration. By default the region name is equal to the bridge MAC Address.

RegionVersion

Version of the MST region.

ConfigIdSel

The configuration identifier format selector used by the bridge. This has a fixed value of 0 to indicate RegionName, RegionVersions are specified as in the standard.

ConfigDigest

The configured MD5 digest value for this region, which must be 16 octets long.

RegionConfigChange Count

The number of times a region configuration identifier change was detected. A trap is generated on the occurrence of this event.

Configuring CIST ports for MSTP To configure Common and Internal Spanning Tree (CIST) ports for MSTP: Nortel Metro Ethernet Routing Switch 8600 Configuration — VLANs, Spanning Tree, and Link Aggregation NN46220-511 04.01 26 June 2009 Copyright © 2007-2009 Nortel Networks. All Rights Reserved.

Configuring Multiple Spanning Tree Protocol

Step

Action

1

In Device Manager, go to VLAN > Spanning Tree > MSTP.

173

The MSTP box appears. 2

In the MSTP box, click the CIST Port tab. The MSTP, CIST Port tab appears (Figure 74 "MSTP, CIST Port tab" (page 173)). Figure 74 MSTP, 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 is common to all bridge and spanning tree instances. For more information, see Table 28 "MSTP, CIST Port fields" (page 174). --End--

Nortel Metro Ethernet Routing Switch 8600 Configuration — VLANs, Spanning Tree, and Link Aggregation NN46220-511 04.01 26 June 2009 Copyright © 2007-2009 Nortel Networks. All Rights Reserved.

174

Configuring spanning tree using Device Manager

Table 28 MSTP, CIST Port fields Field

Description

Port

The port number of the port for which this entry contains spanning tree information

PathCost

The contribution of this port to the path cost of paths towards the CIST root which includes this port.

Priority

The four most significant bits of the port identifier of the spanning tree instance can be modified by setting the CistPortPriority value. The values that are set for port priority must be in steps of 16. Although port priority values can range from 0 to 255, on the Metro Ethernet 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 the configuration BPDUs transmitted.

DesignatedCost

The path cost of the designated port of the segment which connects to this port.

DesignatedBridge

The unique bridge identifier of the bridge which this port considers to be the designated bridge for the port’s segment.

DesignatedPort

The port identifier of the port on the designated bridge for this port segment.

RegionalRoot

The unique bridge identifier of the bridge recorded as the CIST regional root identifier in the configuration BPDUs transmitted.

RegionalPathCost

The contribution of this port to the path cost of paths towards the CIST regional root which include this port.

ProtocolMigration

Indicates the protocol migration state of this port. When operating in MSTP mode, writing true to this object forces this port to transmit MSTP BPDUs without instance information. Any other operation on this object has no effect and it returns false when read.

AdminEdgeStatus

The administrative value of the Edge Port parameter. A value of true indicates that this port is an edge-port, and a value of false indicates that this port is a non-edge-port.

OperEdgeStatus

The operational value of the Edge Port parameter. The object is initialized to the value of AdminEdgeStatus and is set false on reception of a BPDU.

AdminP2P

The administrative point-to-point status of the LAN segment attached to this port. A value of forceTrue indicates that this port is treated as if it connects to a point-to-point link. A value of forceFalse indicates that this port is treated as having a shared media connection. A value of auto indicates that this port is considered to have a point-to-point link if it is an aggregator and all of its members are aggregatable, or if the MAC entity is configured for full duplex operation, either through auto-negotiation or by management means.

Nortel Metro Ethernet Routing Switch 8600 Configuration — VLANs, Spanning Tree, and Link Aggregation NN46220-511 04.01 26 June 2009 Copyright © 2007-2009 Nortel Networks. All Rights Reserved.

Configuring Multiple Spanning Tree Protocol

175

Table 28 MSTP, CIST Port fields (cont’d.) Field

Description

OperP2P

The operational point-to-point status of the LAN segment attached to this port. It indicates whether a port is considered to have a point-to-point connection or not. The value is determined by management or by auto-detection as described in the AdminP2P object.

HelloTime

The amount of time between the transmission of configuration bridge PDUs 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 the STP-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 when the 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 tree protocol. It can be disabled, discarding, learning, or forwarding.

ForcePortState

Current state of the port, which can be changed to either Disabled or Enabled 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 ports You can view statistics for the CIST ports. To view statistics: 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.

3

Click on a port, and then click Graph. The CIST Port Stats window appears (Figure 75 "CIST Port Stats" (page 176)).

Nortel Metro Ethernet Routing Switch 8600 Configuration — VLANs, Spanning Tree, and Link Aggregation NN46220-511 04.01 26 June 2009 Copyright © 2007-2009 Nortel Networks. All Rights Reserved.

176

Configuring spanning tree using Device Manager Figure 75 CIST Port Stats

For more information, see Table 29 "MSTP CIST Port Stats fields" (page 176). --End--

Table 29 MSTP CIST Port Stats fields Field

Description

ForwardTransitions

Number of times this port has transitioned to the forwarding state.

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.

Nortel Metro Ethernet Routing Switch 8600 Configuration — VLANs, Spanning Tree, and Link Aggregation NN46220-511 04.01 26 June 2009 Copyright © 2007-2009 Nortel Networks. All Rights Reserved.

Configuring Multiple Spanning Tree Protocol

177

Table 29 MSTP CIST Port Stats fields (cont’d.) Field

Description

InvalidTcnBpduRxCount

Number of invalid TCN BPDUs received on this port. The number of times this port has migrated from one STP protocol version to another. The relevant protocol is STP-Compatible. A trap is generated on the occurrence of this event.

ProtocolMigrationCount

The number of times this port has migrated from one STP protocol version to another. The relevant protocol is STP-Compatible. A trap is generated on the occurrence of this event.

Configuring MSTI bridges for MSTP To configure Multiple Spanning Tree Instance (MSTI) bridges: Step

Action

1

In Device Manager, go to VLAN > Spanning Tree > MSTP. The MSTP box appears.

2

In the MSTP box, click the MSTI Bridges tab. MSTI bridge instances are generated by the switch after you create 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" (page 177). --End--

Table 30 MSTI Bridges fields Field

Description

Instance

Spanning tree instance to which this information belongs.

Regional Root

MSTI regional root identifier value for the instance. This value is used as the MSTI regional root identifier parameter in all configuration bridge PDUs originated by this node.

Priority

The writable portion of the MSTI bridge identifier comprising of the first two octets. The values that are set for bridge priority must be in steps of 4096.

Root Cost

The cost of the path to the MSTI regional root as seen by this bridge.

Nortel Metro Ethernet Routing Switch 8600 Configuration — VLANs, Spanning Tree, and Link Aggregation NN46220-511 04.01 26 June 2009 Copyright © 2007-2009 Nortel Networks. All Rights Reserved.

178

Configuring spanning tree using Device Manager

Field

Description

Root Port

The port number of the port which offers the lowest path cost from this bridge to the MSTI region root bridge.

TimeSinceTopology Change

The time (in hundredths of a second) since the TcWhile Timer for any 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 TcWhile Timer on this bridge for this spanning tree instance.

NewRootCount

The number of times this bridge has detected a root bridge change for this spanning tree instance. A trap is generated on the occurrence of this event.

InstanceUpcount

The number of times a new spanning tree instance was created. A trap is generated on the occurrence of this event.

InstanceDownCount

The number of times a spanning tree instance was deleted. A trap is generated 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 VLAN To map an MSTI to a VLAN, do the following: Step

Action

1

In Device Manager, go to VLAN > Spanning Tree > MSTP. The MSTP box appears.

2

In the MSTP box, click the MSTI Bridges tab.

3

Click VLANs and map the MSTI to a VLAN or to a range of VLANs. MSTI bridge instances are generated by the switch after you create a VLAN in MSTP mode.

4

Click Apply. --End--

Configuring MSTI ports for MSTP To configure MSTI ports, do the following: Step

Action

1

In Device Manager, go to VLAN > Spanning Tree > MSTP. The MSTP box appears. Nortel Metro Ethernet Routing Switch 8600 Configuration — VLANs, Spanning Tree, and Link Aggregation NN46220-511 04.01 26 June 2009 Copyright © 2007-2009 Nortel Networks. All Rights Reserved.

Configuring Multiple Spanning Tree Protocol

2

179

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 tab appear in the MSTI Port tab). Figure 76 MSTP, 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 31 MSTP, MSTI Port fields Field

Description

Port

The port number of the port for which this entry contains spanning tree information.

BridgeInstance

Spanning tree instance to which the information belongs.

PathCost

The contribution of this port to the path cost of paths towards the MSTI root which includes this port.

Priority

The four most significant bits of the port identifier for a given spanning tree instance can be modified independently for each spanning tree instance supported by the bridge. The values set for port priority must be in steps of 16.

DesignatedRoot

The unique bridge identifier of the bridge recorded as the MSTI regional root in the configuration BPDUs transmitted.

DesignatedBridge

The unique bridge identifier of the bridge which this port considers to be the designated bridge for the port segment.

DesignatedPort

The port identifier of the port on the designated bridge for this port segment.

State

Current state of the port as defined by the MSTP. A port which is in forwarding state in one instance can be in discarding (blocking) state in another instance.

Nortel Metro Ethernet Routing Switch 8600 Configuration — VLANs, Spanning Tree, and Link Aggregation NN46220-511 04.01 26 June 2009 Copyright © 2007-2009 Nortel Networks. All Rights Reserved.

180

Configuring spanning tree using Device Manager

Table 31 MSTP, MSTI Port fields (cont’d.) Field

Description

ForcePortState

Current state of the port which can be changed to either disabled or enabled for the specific spanning tree instance.

DesignatedCost

The path cost of the designated port of the segment connected to this port.

CurrentPortRole

Current port role of the port for this spanning tree instance.

EffectivePortState

The effective operational state of the port for specific instance. This is true when the port is operationally up at the interface and protocol levels for the specific instance. This is set to false at all other times.

Viewing MSTI port statistics You can view statistics for the MSTI Ports. Step

Action

1

In Device Manager, go to VLAN > Spanning Tree > MSTP. The MSTP box appears.

2

In the MSTP box, click the MSTI Port tab. The MSTP, MSTI Port tab appears (Figure 76 "MSTP, MSTI Port tab" (page 179)).

3

Click on a port, and then click Graph. The MSTI Port Stats window appears (Figure 77 "MSTI Port.BridgeInstance" (page 180)). Figure 77 MSTI Port.BridgeInstance

For more information, see Table 32 "MSTI Port Stats fields" (page 181). --End--

Nortel Metro Ethernet Routing Switch 8600 Configuration — VLANs, Spanning Tree, and Link Aggregation NN46220-511 04.01 26 June 2009 Copyright © 2007-2009 Nortel Networks. All Rights Reserved.

Configuring Multiple Spanning Tree Protocol

181

Table 32 MSTI Port Stats fields Field

Description

ForwardTransitions

Number of times this port has transitioned to the forwarding state for this specific instance.

ReceivedBPDUs

Number of BPDUs received by this port for this spanning tree instance.

TransmittedBPDUs

Number of BPDUs transmitted on this port for this spanning tree instance.

InvalidBPDUsRcvd

Number of invalid BPDUs received on this port for this spanning tree instance.

Viewing MSTI port notification You can view the port notification information that occurred in each of the ports for protocol migration and invalid packet received. Step

Action

1

In Device Manager, go to VLAN > Spanning Tree > MSTP.

2

In the MSTP box, click the MSTI Port Notification tab. For more information, see Table 33 "MSTI Port Notification fields" (page 181). --End--

Table 33 MSTI Port Notification fields Field

Description

Index

A unique value, greater than zero, indicating the port number.

MigrationType

The port protocol migration type that occurred in the port.

PktErrType

The type of invalid packet received in each port.

PktErrVal

The packet error value corresponding to the packet type.

Nortel Metro Ethernet Routing Switch 8600 Configuration — VLANs, Spanning Tree, and Link Aggregation NN46220-511 04.01 26 June 2009 Copyright © 2007-2009 Nortel Networks. All Rights Reserved.

182

Configuring spanning tree using Device Manager

Nortel Metro Ethernet Routing Switch 8600 Configuration — VLANs, Spanning Tree, and Link Aggregation NN46220-511 04.01 26 June 2009 Copyright © 2007-2009 Nortel Networks. All Rights Reserved.

183

.

Configuring link aggregation using Device Manager This section describes how to configure link aggregation in your network. Only SMLT is applicable to NNI; all other technology is applicable to both UNI and NNI. This section includes the following topics:

• • •

“Configuring link aggregation” (page 183) “Configuring Split Multilink Trunking” (page 208) “Configuring Simple Loop Prevention Protocol” (page 220)

Configuring link aggregation This section describes how to configure and manage link aggregation, including LACP and multilink trunking. This section includes the following topics:

• • • • • • • •

“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 not supported in the current release.

Nortel Metro Ethernet Routing Switch 8600 Configuration — VLANs, Spanning Tree, and Link Aggregation NN46220-511 04.01 26 June 2009 Copyright © 2007-2009 Nortel Networks. All Rights Reserved.

184

Configuring link aggregation using Device Manager

Configuring LACP globally The main purpose of LACP is to manage switch ports and their port memberships to form link aggregation groups (LAG). LACP can dynamically add or remove LAG ports, depending on their availability and states. 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 78 MLT_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" (page 185) defines the MLT_LACP, LACP Global tab fields. Configuration changes to the LACP timers are not reflected immediately. LACP timers are not reset until the next time LACP is restarted globally or on a port. This ensures consistency with peer switches.

4

Click Apply. Table 34 "MLT_LACP, LACP Global tab fields" (page 185). --End--

Nortel Metro Ethernet Routing Switch 8600 Configuration — VLANs, Spanning Tree, and Link Aggregation NN46220-511 04.01 26 June 2009 Copyright © 2007-2009 Nortel Networks. All Rights Reserved.

Configuring link aggregation

185

Table 34 MLT_LACP, LACP Global tab fields Field

Description

Enable

Globally enable or disable LACP.

SystemPriority

Sets the system priority to all the LACP enabled aggregators and ports.

FastPeriodicTime

Specifies the number of milliseconds between periodic transmissions using short timeouts. Sets this value to all LACP enabled ports.

FastPeriodicTimeOper

The operating value of the fast periodic timer on the port.

SlowPeriodicTime

Specifies the number of milliseconds between periodic transmissions using long timeouts. Sets this value to all LACP enabled ports.

SlowPeriodicTimeOper

The operating value of the slow periodic timer on the port.

AggrWaitTimeOper

The operating value of the aggregate wait timer on the port.

AggrWaitTime

Specifies the number of milliseconds to delay aggregation to allow multiple links to aggregate simultaneously.

TimeoutScale

Sets the value used to calculate timeout time from the periodic time. Sets this value to all LACP enabled ports. The range is 2 to 10.

TimeoutScaleOper

The operating value of the timeout scale on the port.

SmltSysId

Sets the LACP system ID for split multilink trunks. This is an optional parameter, and is only used for SMLT situations. You must configure the same LACP SMLT system ID on both aggregation switches to avoid loss of data. Nortel recommends that the SmltSysId be configured such that it matches the base MAC address of one of the chassis.

Adding a MultiLink/LACP trunk To add a MultiLink/LACP trunk: Step

Action

1

From the Device Manager menu bar, choose VLAN > MLT/LACP.

2

Click the MultiLink/LACP Trunks tab.

Nortel Metro Ethernet Routing Switch 8600 Configuration — VLANs, Spanning Tree, and Link Aggregation NN46220-511 04.01 26 June 2009 Copyright © 2007-2009 Nortel Networks. All Rights Reserved.

186

Configuring link aggregation using Device Manager

Figure 79 MLT_LACP, MultiLink/LACP Trunks

3

In the MultiLink/LACP Trunks box, click Insert to display the MLT_LACP, Insert Multilink/LACP Trunks box.

Nortel Metro Ethernet Routing Switch 8600 Configuration — VLANs, Spanning Tree, and Link Aggregation NN46220-511 04.01 26 June 2009 Copyright © 2007-2009 Nortel Networks. All Rights Reserved.

Configuring link aggregation

187

Figure 80 MLT_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 error messages on MERS.

6

In the PortType section, select access or trunk.

7

In the Name text box, type a name for the multilink trunk, or accept the default name.

8

Select member ports and VLANs for this MLT/LACP trunk: a In the PortMembers box, click the ellipsis (...), select the desired ports in the MltPortMembers box that appears, and then click Ok. b In the VlanIds box, click the ellipsis (...), select the desired VLANs in the VlanIds box that appears, and then click Ok.

9

In the MltType section, select normalMLT, istMLT, or splitMLT.

Nortel Metro Ethernet Routing Switch 8600 Configuration — VLANs, Spanning Tree, and Link Aggregation NN46220-511 04.01 26 June 2009 Copyright © 2007-2009 Nortel Networks. All Rights Reserved.

188

Configuring link aggregation using Device Manager

For information about configuring SMLT, see “Adding a MLT-based SMLT” (page 208).

• 10

If splitMLT is chosen, in the SmltID box, enter the SMLT ID number.

In the Multicast Distribution box, select enable or disable. Multicast distribution over MLT is supported only on Metro Ethernet 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 the MLT_LACP box. For more information, see “MultiLink/LACP Trunks tab fields” (page 188). --End--

MultiLink/LACP Trunks tab fields Table 35 MultiLink/LACP Trunks tab fields Field

Description

Id

A value that uniquely identifies the multilink trunk.

SvlanPortType

Sets multilink trunk port type:

• •

normal (default)

•

nni (network-to-network interface) NNI ports interconnect the switches in the core network, drop untagged frames on ingress, and insert the SVLAN tag at the egress. When you configure an NNI port, the DiscardUnTaggedFrames parameter is automatically configured (Edit > Port > General > VLAN).

uni (user-to-network interface) You must configure ports to which you want to provide VLAN transparency as UNI ports. UNI ports can only belong to one SVLAN. When you designate a port as a UNI port, the DiscardTaggedFrames parameter is automatically configured (Edit > Port > General > VLAN). This prevents traffic from leaking to other VLANs.

Nortel Metro Ethernet Routing Switch 8600 Configuration — VLANs, Spanning Tree, and Link Aggregation NN46220-511 04.01 26 June 2009 Copyright © 2007-2009 Nortel Networks. All Rights Reserved.

Configuring link aggregation

189

Table 35 MultiLink/LACP Trunks tab fields (cont’d.) Field

Description

ATTENTION Uni and nni options generate error messages on MERS. Leave the option at its default value of normal to avoid these error messages. PortType

Sets access or trunk port. When the aggregatable field is set to enable, this field becomes 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 an multilink trunk must be of the same media type (copper or fiber) and have the same settings for speed and duplex. All untagged ports must belong to the same spanning tree group. For Metro Ethernet Routing Switch 8600 modules, up to eight same-type ports can belong to a single multilink trunk. When the aggregatable field is set to enable, this field becomes read-only.

VlanIds

The VLANs to which the ports belong. When the aggregatable field is set to enable, this field becomes read-only.

MltType

Specifies the type of multilink trunk:

• • • SmltId

normalMLT istMLT splitMLT

The split multilink trunk ID assigned to both ends of the split trunk. The corresponding split multilink trunks between aggregation switches must have the same SMLT ID.

Nortel Metro Ethernet Routing Switch 8600 Configuration — VLANs, Spanning Tree, and Link Aggregation NN46220-511 04.01 26 June 2009 Copyright © 2007-2009 Nortel Networks. All Rights Reserved.

190

Configuring link aggregation using Device Manager

Table 35 MultiLink/LACP Trunks tab fields (cont’d.) Field

Description

Multicast Distribution

The multicast distribution state on MLT ports:

• •

enabled disabled (default)

Multicast distribution must also be configured on the chassis (Edit > Chassis > Mcast MLT Distribution). For more information, see Configuration — IP Multicast (NN46220-519). . Multicast distribution over MLT is supported only on Metro Ethernet Routing Switch 8600 E, M, and R modules. Lacp10gBackup

Enable or disable 10G MLT reliance backup mode. The default is disable.

LocalDistributionOptio n

Specify the MLT load distribution option. Select either bmac, cmac, bvid, or isid. The default is bmac.

•

bmac—Egress port selection is based on the UNI MAC source address (SA) and destination address (DA).

•

cmac—Egress port selection is based on the customer MAC SA and DA.

•

bvid—Provides link protection. The b-vid option allows users to specify primary and secondary MLT ports for a particular SP VLAN. Egress port selection is based on the port priority and state.

•

isid—Egress port selection is based on the I-SID or TDI.

Note that the bvid option is only valid if there is a B-VID list for the SP VLAN or B-VLAN. NtStgEnable

Specifies if this multilink trunk is operating in Nortel Mode or in Cisco Mode.

• • Aggregatable

true—Nortel mode false—Cisco mode

Specifies if link aggregation is enabled or disabled.

Nortel Metro Ethernet Routing Switch 8600 Configuration — VLANs, Spanning Tree, and Link Aggregation NN46220-511 04.01 26 June 2009 Copyright © 2007-2009 Nortel Networks. All Rights Reserved.

Configuring link aggregation

191

Table 35 MultiLink/LACP Trunks tab fields (cont’d.) Field

Description

UniAggrMacIDx

Specify the MLT aggregator MAC index. Enter a value in 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 be set in the range 1 to 448.

QinqEtherType

Specify the QinQ ethernet type value in hexadecimal format. This is only used when the MLT is associated with a QinQ service UNI. The default is 8020 (hexadecimal).

EgressCosProfileNam e

Specify the MLT egress Class Of Service profile name. The default is DEFAULT_PORT_PROFILE.

EgressPolicerAdminS tate

Enable or disable the MLT egress policer. The default is disable.

AggrEgressBandwidth

Select disable for the split bandwidth policer; enable for the aggregator bandwidth policer. The default is to enable the aggregator egress bandwidth policer.

AggrIngressBandwidt h

Select disable for the split bandwidth policer; enable for the aggregator bandwidth policer. The default is to enable the aggregator ingress bandwidth policer.

AggrMacAlloc

Enable or disable aggregated MAC allocation. The default is disable.

MtuAdminState

Enable or disable the MTU Admin state. The default is disable.

Mtu

The Maximum Transmission Unit size. Enter a value in the range from 1518 to 9600.

InterfaceType

Specifies the type of interface:

• • • ConfiguredMembers

normal silent uni

The set of ports that are configured members of a MLT. Ports can be added to a MLT through the Configured Members field only if aggregate is enabled for the MLT.

Nortel Metro Ethernet Routing Switch 8600 Configuration — VLANs, Spanning Tree, and Link Aggregation NN46220-511 04.01 26 June 2009 Copyright © 2007-2009 Nortel Networks. All Rights Reserved.

192

Configuring link aggregation using Device Manager

Table 35 MultiLink/LACP Trunks tab fields (cont’d.) Field

Description When aggregate is enabled, PortMembers shows all the active members under the MLT which have negotiated, while ConfiguredMembers shows the statically added ports under the MLT. It also allows ports to be added under MLT.

Adding ports to a multilink trunk To add ports to an existing multilink trunk: Step

Action

1

From the Device Manager menu bar, choose VLAN > MLT/LACP. The MLT_LACP, LACP Global tab appears.

2

Click the MultiLink/LACP Trunks tab. 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 to which you are adding ports. The MltPortMembers box (Figure 81 "MltPortMembers box" (page 193)) appears, showing the ports currently assigned for the selected multilink trunk. Available ports are editable.

Nortel Metro Ethernet Routing Switch 8600 Configuration — VLANs, Spanning Tree, and Link Aggregation NN46220-511 04.01 26 June 2009 Copyright © 2007-2009 Nortel Networks. All Rights Reserved.

Configuring link aggregation

193

Figure 81 MltPortMembers 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 eight same-type ports can belong to a single multilink trunk.

6

Click Ok. The MltPortMembers box closes. The port numbers are added to the selected multilink trunk on the MultiLink/LACP Trunks tab in the MLT_LACP box.

7

Click Apply. The ports are added to the multilink trunk. --End--

Viewing multilink trunk interface statistics To view multilink trunk interface statistics: 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)).

2

Click the MultiLink/LACP Trunks tab. The MultiLink/LACP Trunks tab appears (Figure 79 "MLT_LACP, MultiLink/LACP Trunks" (page 186)).

3

Select a multilink trunk.

4

Click Graph.

Nortel Metro Ethernet Routing Switch 8600 Configuration — VLANs, Spanning Tree, and Link Aggregation NN46220-511 04.01 26 June 2009 Copyright © 2007-2009 Nortel Networks. All Rights Reserved.

194

Configuring link aggregation using Device Manager

The Statistics, MLT, Interface tab appears Figure 82 "Statistics, MLT, Interface tab" (page 194), displaying interface statistics for the selected multilink trunk. Figure 82 Statistics, MLT, Interface tab

For more information, see Table 36 "Statistics, MLT, Interface tab fields" (page 194). --End--

Table 36 Statistics, 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 level protocols that were not addressed to a multicast or broadcast address at this sublayer.

OutUcastPkts

The number of packets that higher level protocols requested be transmitted that were not addressed to a multicast address at this multilink trunk. This total number includes those packets discarded or unsent.

InMulticastPkt

The number of packets delivered to this multilink trunk that were addressed to a multicast address at this sublayer. For a MAC layer protocol, this number includes both Group and Functional addresses.

Nortel Metro Ethernet Routing Switch 8600 Configuration — VLANs, Spanning Tree, and Link Aggregation NN46220-511 04.01 26 June 2009 Copyright © 2007-2009 Nortel Networks. All Rights Reserved.

Configuring link aggregation

195

Table 36 Statistics, MLT, Interface tab fields (cont’d.) Field

Description

OutMulticast

The total number of packets that higher-level protocols requested be transmitted, and that were addressed to a multicast address at this multilink trunk, including those that were discarded or not sent. For a MAC layer protocol, this number includes both Group and Functional addresses.

InBroadcastPkt

The number of packets delivered to this multilink trunk that were addressed to a broadcast address at this sublayer.

OutBroadcast

The total number of packets that higher-level protocols requested be transmitted, and that were addressed to a broadcast address at this multilink trunk, including those that were discarded or not sent.

Viewing multilink trunk Ethernet error statistics To view multilink trunk Ethernet error statistics: Step

Action

1

From the Device Manager menu bar, choose VLAN > MLT/LACP. The MLT_LACP box appears (Figure 78 "MLT_LACP, LACP Global tab" (page 184)).

2

Click the MultiLink/LACP Trunks tab. The MultiLink/LACP Trunks tab appears (Figure 79 "MLT_LACP, MultiLink/LACP Trunks" (page 186)).

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, Ethernet Errors tab" (page 196)) appears, displaying statistics.

Nortel Metro Ethernet Routing Switch 8600 Configuration — VLANs, Spanning Tree, and Link Aggregation NN46220-511 04.01 26 June 2009 Copyright © 2007-2009 Nortel Networks. All Rights Reserved.

196

Configuring link aggregation using Device Manager Figure 83 Statistics, MLT, Ethernet Errors tab

For more information, see Table 37 "Statistics, MLT, Ethernet Errors tab fields" (page 196). --End--

Table 37 Statistics, MLT, Ethernet Errors tab fields Field

Description

AlignmentErrors

A count of frames received on a particular multilink trunk that are not an integral number of octets in length and do not pass the FCS check. The count represented by an instance of this object increments when the alignmentError status is returned by the MAC service to the LLC (or other MAC user). Received frames for which multiple error conditions occur are, according to the conventions of IEEE 802.3 Layer Management, counted exclusively according to the error status presented to the LLC.

FCSErrors

A count of frames received on a multilink trunk that are an integral number of octets in length but do not pass the Frame Check Sequence (FCS) check. The count represented by an instance of this object increments when the FrameCheckError status is returned by the MAC service to the LLC (or other MAC user). Received frames for which multiple error conditions occur are, according to the conventions of IEEE 802.3 Layer Management, counted exclusively according to the error status presented to the LLC.

Nortel Metro Ethernet Routing Switch 8600 Configuration — VLANs, Spanning Tree, and Link Aggregation NN46220-511 04.01 26 June 2009 Copyright © 2007-2009 Nortel Networks. All Rights Reserved.

Configuring link aggregation

197

Table 37 Statistics, MLT, Ethernet Errors tab fields (cont’d.) Field

Description

IMacTransmitError

A count of frames for which transmission on a particular multilink trunk fails due to an internal MAC sublayer transmit error. A frame is only counted by an instance of this object if it is not counted by the corresponding instance of either the LateCollisions object, the ExcessiveCollisions object, or the CarrierSenseErrors object.

IMacReceiveError

A count of frames for which reception on a particular multilink trunk fails due to an internal MAC sublayer receive error. A frame is only counted by an instance of this object if it is not counted by the corresponding instance of either the FrameTooLongs object, the AlignmentErrors object, or the FCSErrors object. The precise meaning of the count represented by an instance of this object is implementation specific. In particular, an instance of this object can represent a count of receive errors on a particular interface that are not otherwise counted.

CarrierSenseError

The number of times that the carrier sense condition was lost or never asserted when attempting to transmit a frame on a particular multilink trunk. The count represented by an instance of this object increments at most once per transmission attempt, even if the carrier sense condition fluctuates during a transmission attempt.

FrameTooLong

A count of frames received on a particular multilink trunk that exceeds the maximum permitted frame size. The count represented by an instance of this object increments when the frameTooLong status is returned by the MAC service to the LLC (or other MAC user). Received frames for which multiple error conditions occur are, according to the conventions of IEEE 802.3 Layer Management, counted exclusively according to the error status presented to the LLC.

SQETestError

A count of times that the SQE test error message is generated by the PLS sublayer for a particular multilink trunk. The SQE test error message is defined in section 7.2.2.2.4 of ANSI/IEEE 802.3-1985.

Nortel Metro Ethernet Routing Switch 8600 Configuration — VLANs, Spanning Tree, and Link Aggregation NN46220-511 04.01 26 June 2009 Copyright © 2007-2009 Nortel Networks. All Rights Reserved.

198

Configuring link aggregation using Device Manager

Table 37 Statistics, MLT, Ethernet Errors tab fields (cont’d.) Field

Description

DeferredTransmiss

A count of frames for which the first transmission attempt on a particular multilink trunk is delayed because the medium is busy. The count represented by an instance of this object does not include frames involved in collisions.

SingleCollFrames

A count of successfully transmitted frames on a particular multilink trunk for which transmission is inhibited by exactly one collision. A frame that is counted by an instance of this object is also counted by the corresponding instance of either the ifOutUcastPkts object, the ifOutMulticastPkts object, or the ifOutBroadcastPkts object, and is not counted by the corresponding instance of the MultipleCollisionFrames object.

MultipleCollFrames

A count of successfully transmitted frames on a particular multilink trunk for which transmission is inhibited by more than one collision. A frame that is counted by an instance of this object is also counted by the corresponding instance of either the ifOutUcastPkts object, the ifOutMulticastPkts object, or the ifOutBroadcastPkts object, and is not counted by the corresponding instance of the SingleCollisionFrames object.

LateCollisions

The number of times that a collision is detected on a particular multilink trunk later than 512 bit-times into the transmission of a packet; 512 corresponds to 51.2 microseconds on a 10 Mb/s system. A (late) collision included in a count represented by an instance of this object is also considered as a (generic) collision for purposes of other collision-related statistics.

ExcessiveCollis

A count of frames for which transmission on a particular multilink trunk fails due to excessive collisions.

Managing LACP information Standby mode for aggregation groups of larger than eight ports is not supported in the current release. To manage LACP information:

Nortel Metro Ethernet Routing Switch 8600 Configuration — VLANs, Spanning Tree, and Link Aggregation NN46220-511 04.01 26 June 2009 Copyright © 2007-2009 Nortel Networks. All Rights Reserved.

Configuring link aggregation

Step

Action

1

From the Device Manager menu bar, choose VLAN > MLT/LACP.

199

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" (page 199), displaying multilink trunk information. Figure 84 MLT_LACP, LACP tab

For more information, see Table 38 "MLT_LACP, LACP tab fields" (page 199). 3

Click on the fields to edit them. Some fields cannot be edited, as noted in Table 38 "MLT_LACP, LACP tab fields" (page 199) .

4

Click Apply. --End--

Table 38 MLT_LACP, LACP tab fields Field

Description

Index

The unique identifier allocated to this aggregator by the local system. This attribute identifies an aggregator instance among the subordinate managed objects of the containing object. This value is read-only.

MACAddress

The six octet read-only value carrying the individual MAC address assigned to the aggregator.

ActorSystemPriority

The two octet read-write value indicating the priority value associated with the actor’s system ID.

Nortel Metro Ethernet Routing Switch 8600 Configuration — VLANs, Spanning Tree, and Link Aggregation NN46220-511 04.01 26 June 2009 Copyright © 2007-2009 Nortel Networks. All Rights Reserved.

200

Configuring link aggregation using Device Manager

Table 38 MLT_LACP, LACP tab fields (cont’d.) Field

Description

ActorSystemID

The six octet read-write MAC address value used as a unique identifier for the system that contains this aggregator. From the perspective of the link aggregation mechanisms, only a single combination of actor system ID and system priority are considered, and no distinction is made between the values of these parameters for an aggregator and the ports that are associated with it; that is, the protocol is described in terms of the operation of aggregation within a single system. However, the managed objects provided for the aggregator and the port both allow management of these parameters. The result of this is to permit a single piece of equipment to be configured by management to contain more than one system from the point of view of the operation of link aggregation. This can be of particular use in the configuration of equipment that has limited aggregation capability.

AggregateOrIndividual

Indicates whether the aggregator represents an aggregate (true) or an individual link (false)

ActorAdminKey

The current administrative value of the key for the aggregator. The administrative key value can differ from the operational key value. This is a 16 bit read-write value. The meaning of particular 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 operational key value. This is a 16 bit read-only value. The meaning of particular key values is of local significance.

PartnerSystemID

The six octet read-only MAC address value consisting of the unique identifier for the current protocol partner of this aggregator. A value of zero indicates that there is no known partner. If the aggregation is manually configured, this system ID value is a value assigned by the local system.

Nortel Metro Ethernet Routing Switch 8600 Configuration — VLANs, Spanning Tree, and Link Aggregation NN46220-511 04.01 26 June 2009 Copyright © 2007-2009 Nortel Networks. All Rights Reserved.

Configuring link aggregation

201

Table 38 MLT_LACP, LACP tab fields (cont’d.) Field

Description

PartnerSystemPriority

The two octet read-only value that indicates the priority value associated with the partner system ID. If the aggregation is manually configured, this system priority value is a value assigned by the local System.

PartnerOperKey

The current operational value of the key for the aggregator current protocol partner. This is a 16 bit read-only value. If the aggregation is manually configured, this key value is a value assigned by the local system.

Configuring a port for LACP To 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.

3

Click the LACP tab. The Port, LACP tab appears (Figure 85 "Port, LACP tab" (page 202)), displaying multilink trunk information.

Nortel Metro Ethernet Routing Switch 8600 Configuration — VLANs, Spanning Tree, and Link Aggregation NN46220-511 04.01 26 June 2009 Copyright © 2007-2009 Nortel Networks. All Rights Reserved.

202

Configuring link aggregation using Device Manager Figure 85 Port, LACP tab

For more information, see Table 39 "Port, LACP tab fields" (page 202). 4

Select AdminEnable.

5

Edit the remaining boxes as desired.

6

Click Apply. --End--

Table 39 Port, 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 periodic transmissions 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 periodic transmissions 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 to allow multiple links to aggregate simultaneously.

AggrWaitTimeOper

The operating value of the aggregate wait timer on the port.

Nortel Metro Ethernet Routing Switch 8600 Configuration — VLANs, Spanning Tree, and Link Aggregation NN46220-511 04.01 26 June 2009 Copyright © 2007-2009 Nortel Networks. All Rights Reserved.

Configuring link aggregation

203

Table 39 Port, LACP tab fields (cont’d.) Field

Description

TimeoutScale

Sets the value used to calculate timeout time from the periodic time. 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 value associated with the actor system ID.

ActorSystemID

The six octet read-write MAC address value used as a unique identifier for the system that contains this aggregator. From the perspective of the link aggregation mechanisms, only a single combination of actor system ID and system priority are considered, and no distinction is made between the values of these parameters for an aggregator and the ports that are associated with it; that is, the protocol is described in terms of the operation of aggregation within a single system. However, the managed objects provided for the aggregator and the port both allow management of these parameters. The result of this is to permit a single piece of equipment to be configured by management to contain more than one system from the point of view of the operation of link aggregation. This can be of particular use in the configuration of equipment that has limited aggregation capability.

ActorAdminKey

The current administrative value of the key for the aggregator. The administrative key value can differ from the operational key value. This is a 16-bit read-write value. The meaning of particular 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 operational key value. This is a 16-bit read-only value. The meaning of particular key values is of local significance.

SelectedAggID

The identifier value of the aggregator that this aggregation port has currently selected. Zero indicates that the aggregation port has not selected an aggregator, either because it is in the process of detaching from an aggregator or because there is no suitable aggregator available for it to select. This value is read-only.

AttachedAggID

The identifier value of the aggregator to which this aggregation port is currently attached. Zero indicates that the aggregation port is not currently attached to an aggregator. This value is read-only.

Nortel Metro Ethernet Routing Switch 8600 Configuration — VLANs, Spanning Tree, and Link Aggregation NN46220-511 04.01 26 June 2009 Copyright © 2007-2009 Nortel Networks. All Rights Reserved.

204

Configuring link aggregation using Device Manager

Table 39 Port, LACP tab fields (cont’d.) Field

Description

ActorPort

The port number locally assigned to the aggregation port. The port 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-bit value is read-write.

ActorAdminState

A string of eight bits, corresponding to the administrative values as 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 of LACP_Activity, LACP_Timeout and aggregation. This attribute value is read-write. ActorOperState

A string of eight bits, corresponding to the current operational values 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 for the protocol Partner. This is a 16 bit read-write value. The assigned value is used, along with the value of PartnerAdminSystemPriority, PartnerAdminSystemID, PartnerAdminKey, and PartnerAdminPortPriority, to achieve manually configured aggregation.

PartnerOperSystemPriority

A two octet read-only value indicating the operational value of priority associated with the partner system ID. The value of this attribute can contain the manually configured value carried in PartnerAdminSystemPriority if there is no protocol partner.

PartnerAdminSystemID

A six octet read-write MAC address value representing the administrative value of the aggregation port protocol partner’s system ID. The assigned value is used, along with the value of PartnerAdminSystemPriority, PartnerAdminKey, PartnerAdminPort, and PartnerAdminPortPriority, to achieve manually configured aggregation.

Nortel Metro Ethernet Routing Switch 8600 Configuration — VLANs, Spanning Tree, and Link Aggregation NN46220-511 04.01 26 June 2009 Copyright © 2007-2009 Nortel Networks. All Rights Reserved.

Configuring link aggregation

205

Table 39 Port, LACP tab fields (cont’d.) Field

Description

PartnerOperSystemID

A six octet read-only MAC address value representing the current value of the aggregation port’s protocol partner system ID. A value of zero indicates that there is no known protocol partner. The value of this attribute can contain the manually configured value carried in PartnerAdminSystemID if there is no protocol partner.

PartnerAdminKey

The current administrative value of the key for the protocol partner. This is a 16 bit read-write value. The assigned value is used, along with the value of PartnerAdminSystemPriority, PartnerAdminSystemID, PartnerAdminPort, and PartnerAdminPortPriority, to achieve manually configured aggregation.

PartnerOperKey

The current operational value of the key for the aggregator current protocol partner. This is a 16-bit read-only value. If the aggregation is manually configured, this key value is a value assigned by the local system.

PartnerAdminPort

The current administrative value of the port number for the protocol partner. This is a 16 bit read-write value. The assigned value is used, along with the value of PartnerAdminSystemPriority, PartnerAdminSystemID, PartnerAdminKey, and PartnerAdminPortPriority, to achieve manually configured aggregation.

PartnerOperPort

The operational port number assigned to this aggregation port by the aggregation port’s protocol partner. The value of this attribute can contain the manually configured value carried in AggPortPartnerAdminPort if there is no protocol partner. This 16 bit value is read-only.

PartnerAdminPortPriority

The current administrative value of the port priority for the protocol Partner. This is a 16 bit read-write value. The assigned value is used, along with the value of PartnerAdminSystemPriority, PartnerAdminSystemID, PartnerAdminKey, and PartnerAdminPort, to achieve manually configured aggregation.

PartnerOperPortPriority

The priority value assigned to this aggregation port by the partner. The value of this attribute can contain the manually configured value carried in PartnerAdminPortPriority if there is no protocol Partner. This 16 bit value is read-only.

Nortel Metro Ethernet Routing Switch 8600 Configuration — VLANs, Spanning Tree, and Link Aggregation NN46220-511 04.01 26 June 2009 Copyright © 2007-2009 Nortel Networks. All Rights Reserved.

206

Configuring link aggregation using Device Manager

Table 39 Port, LACP tab fields (cont’d.) Field

Description

PartnerAdminState

A string of eight bits, corresponding to the current administrative value of Actor_State for the protocol partner. This attribute value is read-write. The assigned value is used to achieve manually configured aggregation.

PartnerOperState

A string of eight bits, corresponding to the current values of Actor_State in the most recently received LACPDU transmitted by the protocol Partner. In the absence of an active protocol partner, this value can reflect the manually configured value PartnerAdminState. This attribute value is read-only.

Viewing LACP statistics To 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 86 Graph Port, Interface tab

3

Click the LACP tab.

Nortel Metro Ethernet Routing Switch 8600 Configuration — VLANs, Spanning Tree, and Link Aggregation NN46220-511 04.01 26 June 2009 Copyright © 2007-2009 Nortel Networks. All Rights Reserved.

Configuring link aggregation

207

The LACP tab appears (Figure 87 "Graph Port, LACP tab" (page 207)), displaying LACP statistics. Figure 87 Graph Port, LACP tab

4

You can change the Poll Interval if desired. For more information, see Table 40 "Graph Port, LACP tab fields" (page 207). --End--

Table 40 Graph 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 aggregation port.

MarkerResponsePDUsRx

The number of valid marker response PDUs received on this aggregation port.

UnknownRx

The number of frames received that either:

•

carry Slow Protocols Ethernet type values, but contain an unknown 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 Protocols Ethernet Type value (43B.4), but contain a badly formed PDU or an illegal value of Protocol Subtype (43B.4).

LACPDUsTx

The number of LACPDUs transmitted on this aggregation port.

Nortel Metro Ethernet Routing Switch 8600 Configuration — VLANs, Spanning Tree, and Link Aggregation NN46220-511 04.01 26 June 2009 Copyright © 2007-2009 Nortel Networks. All Rights Reserved.

208

Configuring link aggregation using Device Manager

Table 40 Graph Port, LACP tab fields (cont’d.) Field

Description

MarkerPDUsTx

The number of marker PDUs transmitted on this aggregation port.

MarkerResponsePDUsTx

The number of marker response PDUs transmitted on this aggregation port.

Configuring Split Multilink Trunking Routed SMLT, or RSMLT, is a Layer 3 protocol whereas SMLT is a Layer 2 protocol. SMLT is described in this document, and RSMLT is described in the document Configuring IP Routing Operations. This section describes how to use Device Manager to configure Split MultiLink 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 SMLT If you are configuring SMLT, you do not need to create a multilink trunk before creating an SMLT. You can create an SMLT by selecting the multilink trunk type as split multilink trunk and then specifying an SMLT ID. To add an MLT-based split multilink trunk: Step

Action

1

From the Device Manager menu bar, choose VLAN > MLT/LACP. The MLT_LACP box appears (Figure 78 "MLT_LACP, LACP Global tab" (page 184)).

2

Click the MultiLink/LACP Trunks tab.

Nortel Metro Ethernet Routing Switch 8600 Configuration — VLANs, Spanning Tree, and Link Aggregation NN46220-511 04.01 26 June 2009 Copyright © 2007-2009 Nortel Networks. All Rights Reserved.

Configuring Split Multilink Trunking

209

The MultiLink/LACP Trunks tab appears (Figure 79 "MLT_LACP, MultiLink/LACP Trunks" (page 186)). 3

Click Insert. The MultiLink/LACP, Insert MultiLink/LACP Trunks box (Figure 80 "MLT_LACP, Insert MultiLink/LACP Trunks box" (page 187)) appears.

4

In the Id box, the next available MLT ID is displayed. You can use 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 split multilink 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 split multilink trunk. For Metro Ethernet Routing Switch 8600 modules, up to eight same-type ports can belong to a multilink trunk.

10

Click Ok. The MltPortMembers box closes and the ports are added to the PortMembers 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 VlanIds box 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 aggregation switches must have matching SMLT IDs. The same ID number must 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 new MLT-based split multilink trunk appears in the MultiLink/LACP Trunks tab. Nortel Metro Ethernet Routing Switch 8600 Configuration — VLANs, Spanning Tree, and Link Aggregation NN46220-511 04.01 26 June 2009 Copyright © 2007-2009 Nortel Networks. All Rights Reserved.

210

Configuring link aggregation using Device Manager

16

On the MultiLink/LACP Trunks tab, click Close. The MLT-based split multilink trunk is added. --End--

Viewing MLT-based SMLTs To 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-based split multilink trunks displayed (Figure 88 "SMLT, SMLT Info tab" (page 210)). Figure 88 SMLT, SMLT Info tab

For more information, see Table 41 "SMLT, SMLT Info tab fields" (page 210). --End--

Table 41 SMLT, SMLT Info tab fields Field

Description

Id

Read-only field displaying the MLT ID for this split multilink trunk.

Nortel Metro Ethernet Routing Switch 8600 Configuration — VLANs, Spanning Tree, and Link Aggregation NN46220-511 04.01 26 June 2009 Copyright © 2007-2009 Nortel Networks. All Rights Reserved.

Configuring Split Multilink Trunking

211

Table 41 SMLT, SMLT Info tab fields (cont’d.) Field

Description

SmltId

The MLT-based split multilink trunk ID number.

MltType

Specifies the type of multilink trunk:

• • • RunningType

normalMLT istMLT splitMLT

Indicates the MLT operational type:

• • •

normalMLT istMLT splitMLT

Adding ports to an MLT-based SMLT To add ports to an existing MLT-based split multilink trunk: Step

Action

1

From the Device Manager menu bar, choose VLAN > MLT/LACP. The LACP Global tab appears (Figure 78 "MLT_LACP, LACP Global tab" (page 184)).

2

Click the MultiLink/LACP Trunks tab. The MultiLink/LACP Trunks tab appears (Figure 79 "MLT_LACP, MultiLink/LACP Trunks" (page 186)).

3

Double-click the PortMembers box for the MLT-based split multilink trunk to which you are adding ports. The MltPortMembers box (Figure 81 "MltPortMembers box" (page 193)) appears for the specified SMLT ID. Available ports are editable.

4

Select the port numbers to be added, or click All to select all ports.

• 5

For Metro Ethernet Routing Switch 8600 modules, up to eight same-type ports can belong to a single multilink trunk.

Click Ok. The MltPortMembers box closes and the ports are added to the Port Members box on the MultiLink Trunks tab.

Nortel Metro Ethernet Routing Switch 8600 Configuration — VLANs, Spanning Tree, and Link Aggregation NN46220-511 04.01 26 June 2009 Copyright © 2007-2009 Nortel Networks. All Rights Reserved.

212

Configuring link aggregation using Device Manager

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 trunk To configure an IST multilink trunk: Step

Action

1

From the Device Manager menu bar, choose VLAN > MLT/LACP. The LACP Global tab appears (Figure 78 "MLT_LACP, LACP Global tab" (page 184)).

2

Click the MultiLink/LACP Trunks tab. 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

In the PortMembers box for the IST multilink trunk, click the ellipsis (...). 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 to the PortMembers box for the IST multilink trunk in the Insert MultiLink 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)).

Nortel Metro Ethernet Routing Switch 8600 Configuration — VLANs, Spanning Tree, and Link Aggregation NN46220-511 04.01 26 June 2009 Copyright © 2007-2009 Nortel Networks. All Rights Reserved.

Configuring Split Multilink Trunking Figure 89 IST 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 cp-limit disable

The IST multilink trunk is configured. For more information, see Table 42 "Ist multilink trunk fields" (page 213). --End--

Table 42 Ist 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 IST To 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. Nortel Metro Ethernet Routing Switch 8600 Configuration — VLANs, Spanning Tree, and Link Aggregation NN46220-511 04.01 26 June 2009 Copyright © 2007-2009 Nortel Networks. All Rights Reserved.

213

214

Configuring link aggregation using Device Manager

3

Click IstMlt. The IST MLT box (Figure 90 "IST MLT" (page 214)) appears. For field definitions, see Table 42 "Ist multilink trunk fields" (page 213) . Figure 90 IST 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 statistics To view IST statistics on an interface: Step

Action

1

From the Device Manager menu bar, choose VLAN > MLT/LACP. The LACP Global tab appears (Figure 78 "MLT_LACP, LACP Global tab" (page 184)).

2

Click the Ist/SMLT Stats tab. The Ist/SMLT Stats tab appears (Figure 91 "Ist/SMLT Stats tab" (page 215)).

Nortel Metro Ethernet Routing Switch 8600 Configuration — VLANs, Spanning Tree, and Link Aggregation NN46220-511 04.01 26 June 2009 Copyright © 2007-2009 Nortel Networks. All Rights Reserved.

Configuring Split Multilink Trunking

215

Figure 91 Ist/SMLT Stats tab

For more information, see Table 43 "MLT_LACP, Ist/SMLT Stats tab fields" (page 215). --End--

Table 43 MLT_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 messages transmitted.

SmltMacAddrAgeOutRxMsgCnt

The number of MAC address aging out messages received.

Nortel Metro Ethernet Routing Switch 8600 Configuration — VLANs, Spanning Tree, and Link Aggregation NN46220-511 04.01 26 June 2009 Copyright © 2007-2009 Nortel Networks. All Rights Reserved.

216

Configuring link aggregation using Device Manager

Table 43 MLT_LACP, Ist/SMLT Stats tab fields (cont’d.) Field

Description

SmltMacAddrAgeExpTxMsgCnt

The number of MAC address age expired messages transmitted.

SmltMacAddrAgeExpRxMsgCnt

The number of MAC address age expired messages received.

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 messages transmitted.

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 trunk Ports that are already configured as MLT or MLT-based split multilink trunks cannot be configured as a single port split multilink trunk. You must first remove the split trunk and then reconfigure the ports as a single port split 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.

Nortel Metro Ethernet Routing Switch 8600 Configuration — VLANs, Spanning Tree, and Link Aggregation NN46220-511 04.01 26 June 2009 Copyright © 2007-2009 Nortel Networks. All Rights Reserved.

Configuring Split Multilink Trunking

217

The port is highlighted. 2

From the menu bar, choose Edit > Port > General. The Port box appears.

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 MLT or MLT-based SMLT. If so, you cannot configure Single Port SMLT. Figure 92 Port, SMLT tab

4

Click Insert. The Insert SMLT box appears (Figure 93 "Port, Insert SMLT" (page 217)). Figure 93 Port, 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 spanning tree protocol has been disabled while configuring the port with SMLT.

7

Click Ok. The Insert SMLT box closes and the ID is entered.

Nortel Metro Ethernet Routing Switch 8600 Configuration — VLANs, Spanning Tree, and Link Aggregation NN46220-511 04.01 26 June 2009 Copyright © 2007-2009 Nortel Networks. All Rights Reserved.

218

Configuring link aggregation using Device Manager

Table 44 "Port SMLT tab fields" (page 218). --End--

Table 44 Port SMLT tab fields Field

Description

Port

The slot/port number for the port.

MltId

Indicates one of the following:

SmltId

•

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 this port.

•

A value of 0 indicates that no multilink trunk is assigned, and the port can be configured for Single Port SMLT.

The split multilink trunk ID.

•

A read-only field indicates the port Single Port SMLT ID assignment.

•

A blank field indicates the port is not configured for Single Port SMLT. Find an unused SMLT ID by viewing the currently used IDs. See “Viewing Single Port SMLTs” (page 218).

Viewing Single Port SMLTs To 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 multilink trunks currently configured on your switch Figure 94 "SMLT, Single Port SMLT" (page 219).

Nortel Metro Ethernet Routing Switch 8600 Configuration — VLANs, Spanning Tree, and Link Aggregation NN46220-511 04.01 26 June 2009 Copyright © 2007-2009 Nortel Networks. All Rights Reserved.

Configuring Split Multilink Trunking

219

Figure 94 SMLT, Single Port SMLT

--End--

For more information, see Table 45 "SMLT, Single Port SMLT tab fields" (page 219). Table 45 SMLT, 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 SMLT To delete a single port split multilink trunk: Step

Action

1

From the Device Manager main window, select the port. The port is highlighted.

Nortel Metro Ethernet Routing Switch 8600 Configuration — VLANs, Spanning Tree, and Link Aggregation NN46220-511 04.01 26 June 2009 Copyright © 2007-2009 Nortel Networks. All Rights Reserved.

220

Configuring link aggregation using Device Manager

2

From the menu bar, choose Edit > Port > General. The Port box appears.

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 95 Deleting 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 Protocol Simple Loop Prevention Protocol (SLPP) is used at the edge of a network to 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 globally To configure Simple Loop Prevention Protocol (SLPP) globally:

Nortel Metro Ethernet Routing Switch 8600 Configuration — VLANs, Spanning Tree, and Link Aggregation NN46220-511 04.01 26 June 2009 Copyright © 2007-2009 Nortel Networks. All Rights Reserved.

Configuring Simple Loop Prevention Protocol

Step

Action

1

From the Device Manager menu bar, select VLAN > SLPP.

221

The Slpp box appears with the Global tag displayed. Figure 96 SLPP, 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 time interval for loop detection.

4

In the EtherType box, enter the SLPP protocol value as a hexadecimal number.

5

In the UniPorts field, specify the UNI ports added under the SLPP global configuration.

6

Click Apply. --End--

Table 46 SLPP, Global tab fields Field

Description

GlobalEnable

Globally enables or disables SLPP.

TransmissionInterval

Sets the interval (in milliseconds) for which loop detection occurs. The range is 500 to 5000 ms, and the default is 500 ms.

Ether Type

Specifies the SLPP protocol identification. This value is expressed in hexadecimal.

UniPorts

Specifies the UNI ports added under the SLPP global configuration.

Nortel Metro Ethernet Routing Switch 8600 Configuration — VLANs, Spanning Tree, and Link Aggregation NN46220-511 04.01 26 June 2009 Copyright © 2007-2009 Nortel Networks. All Rights Reserved.

222

Configuring link aggregation using Device Manager

Configuring the SLPP by VLAN Step

Action

1

From the Device Manager menu bar, select VLAN > SLPP. The Slpp box appears with the Global tag displayed.

2

Click the VLANS tab. The VLANS tab appears. Figure 97 Slpp, VLANS tab

3

Click Insert. The Slpp, Insert VLANS box appears. Figure 98 Slpp, Insert VLANS

For more information, see Table 47 "Slpp, Insert VLANS fields" (page 223). 4

Click the VlanID ellipsis (...). The VlanId box appears.

Nortel Metro Ethernet Routing Switch 8600 Configuration — VLANs, Spanning Tree, and Link Aggregation NN46220-511 04.01 26 June 2009 Copyright © 2007-2009 Nortel Networks. All Rights Reserved.

Configuring Simple Loop Prevention Protocol Figure 99 Slpp, 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 47 Slpp, Insert VLANS fields Field

Description

VlanId

Specifies the VLAN.

SlppEnable

Enables SLPP on the selected VLAN. The SLPP packet transmission and reception process is active only when the SLPP operation is enabled. When the SLPP operation is disabled, no SLPP packet is sent, and any received SLPP packet is discarded.

Configuring the SLPP by port To configure SLPP by port: Step

Action

1

From the Device Manager menu bar, select VLAN > SLPP. The Slpp box appears with the Global tag displayed.

2

Click the Ports tab.

Nortel Metro Ethernet Routing Switch 8600 Configuration — VLANs, Spanning Tree, and Link Aggregation NN46220-511 04.01 26 June 2009 Copyright © 2007-2009 Nortel Networks. All Rights Reserved.

223

224

Configuring link aggregation using Device Manager

The Slpp, Ports tab appears displaying all available ports. Figure 100 Slpp, Ports tab

3

Click the SlppEnable box for the desired port and select true to enable SLPP.

4

Click Apply. The ID and status of selected VLAN appears in the Slpp, VLANS dialog box (Figure 97 "Slpp, VLANS tab" (page 222)). For more information, see Table 48 "Slpp, Ports tab fields" (page 224). --End--

Table 48 Slpp, Ports tab fields Field

Description

IfIndex

Specifies the interface index number for a port.

PktRxThreshold

Specifies the threshold for packet reception from 1 to 20. After a port reaches the packet threshold, it is disabled.

Nortel Metro Ethernet Routing Switch 8600 Configuration — VLANs, Spanning Tree, and Link Aggregation NN46220-511 04.01 26 June 2009 Copyright © 2007-2009 Nortel Networks. All Rights Reserved.

Configuring Simple Loop Prevention Protocol

225

Table 48 Slpp, 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 by SLPP.

SrcNodeType

Specifies the source node type of the received SLPP packet.

PktRxCount

Specifies the total number of SLPP packets received on the port. Valid values are 1 to 500.

Nortel Metro Ethernet Routing Switch 8600 Configuration — VLANs, Spanning Tree, and Link Aggregation NN46220-511 04.01 26 June 2009 Copyright © 2007-2009 Nortel Networks. All Rights Reserved.

226

Configuring link aggregation using Device Manager

Nortel Metro Ethernet Routing Switch 8600 Configuration — VLANs, Spanning Tree, and Link Aggregation NN46220-511 04.01 26 June 2009 Copyright © 2007-2009 Nortel Networks. All Rights Reserved.

227

.

Setting the sVLAN Ethertype using Device Manager Use this procedure to configure the stacked VLAN (sVLAN) Ethertype for the switch. sVLANs are not supported on the Metro Ethernet Routing Switch 8600 R modules. Procedure 1 Setting the sVLAN Ethertype

Step

Action

1

From the Device Manager menu, select VLAN, SVLAN. The Svlan, Ether Type tab appears, displaying the Ether types used for sVLAN tagging. Figure 101 SVLAN, Ether Type tab

Nortel Metro Ethernet Routing Switch 8600 Configuration — VLANs, Spanning Tree, and Link Aggregation NN46220-511 04.01 26 June 2009 Copyright © 2007-2009 Nortel Networks. All Rights Reserved.

228

Setting the sVLAN Ethertype using Device Manager

2

To modify an Ethertype, double-click an EtherType box and enter a new value. “SVLAN, Ether Type tab” (page 228) describes the sVLAN Ether Type tab.

3

Click Apply. The Ethertype is configured. --End--

SVLAN, Ether Type tab Table 49 SVLAN, 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 switch levels:

•

Level 0 — 0x8100 (Ethertype defined by IEEE for 802.1Q tagged frames)

• • • • • • •

Level 1 — 0x8020 Level 2 — 0x8030 Level 3 — 0x8040 Level 4 — 0x8050 Level 5 — 0x8060 Level 6 — 0x8070 Level 7 — 0x8080

Nortel Metro Ethernet Routing Switch 8600 Configuration — VLANs, Spanning Tree, and Link Aggregation NN46220-511 04.01 26 June 2009 Copyright © 2007-2009 Nortel Networks. All Rights Reserved.

229

.

Setting the sVLAN switch level using Device Manager Use this procedure to configure the stacked VLAN (sVLAN) switch level. sVLANs are not supported on the Metro Ethernet Routing Switch 8600 R modules. Procedure 2 Setting the sVLAN switch level

Step

Action

1

From the Device Manager menu, select VLAN, SVLAN. The Svlan, Ether Type tab appears, displaying the Ether types used for sVLAN tagging. Figure 102 SVLAN, Ether Type tab

2

Click the Level tab. Nortel Metro Ethernet Routing Switch 8600 Configuration — VLANs, Spanning Tree, and Link Aggregation NN46220-511 04.01 26 June 2009 Copyright © 2007-2009 Nortel Networks. All Rights Reserved.

230

Setting the sVLAN switch level using Device Manager

The Level tab appears. Figure 103 Svlan 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 7 before 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 tab Table 50 SVLAN, Level tab Field

Description

Active Level

Specifies the active level for the switch. The default is level 0. You must configure the switch level to 1 or above before configuring UNI or NNI ports.

Nortel Metro Ethernet Routing Switch 8600 Configuration — VLANs, Spanning Tree, and Link Aggregation NN46220-511 04.01 26 June 2009 Copyright © 2007-2009 Nortel Networks. All Rights Reserved.

231

.

Configuring Simple Loop Prevention Protocol with Device Manager Use this procedure to add UNI ports under the global SLPP config, or to display the total number of SLPP PDUs received on a particular port. Procedure 3 Configuring Simple Loop Prevention Protocol

Step

Action

1

From the Device Manager menu, select VLAN -> SLPP-> Ports.

Nortel Metro Ethernet Routing Switch 8600 Configuration — VLANs, Spanning Tree, and Link Aggregation NN46220-511 04.01 26 June 2009 Copyright © 2007-2009 Nortel Networks. All Rights Reserved.

232

Configuring Simple Loop Prevention Protocol with Device Manager Figure 104 SLPP box, Ports tab

Because this screen does not show port types, just the port numbers, you must know which ports are UNI or NNI. For more information, see “SLPP, Ports tab fields” (page 232) --End--

SLPP, Ports tab fields Table 51 SLPP, 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 CLI Show Command.

Nortel Metro Ethernet Routing Switch 8600 Configuration — VLANs, Spanning Tree, and Link Aggregation NN46220-511 04.01 26 June 2009 Copyright © 2007-2009 Nortel Networks. All Rights Reserved.

233

.

Configuring and managing VLANs using the CLI This section describes how to configure and manage VLANs using the command 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 commands The following roadmap lists the VLAN commands and their parameters. Use this list as a quick reference. Command

Parameter

config vlan create

info byIDS [name ] [color ] byipsubnet [ name ] [color ] byipsubnet-mstp [name ] [color ] byport [name ] [color ] byport-mstp [name ] [color ] [naap-vlan] [firewall-vlan] [firewall-peering-vlan]

Nortel Metro Ethernet Routing Switch 8600 Configuration — VLANs, Spanning Tree, and Link Aggregation NN46220-511 04.01 26 June 2009 Copyright © 2007-2009 Nortel Networks. All Rights Reserved.

234

Configuring and managing VLANs using the CLI

Parameter

Command

byprotocol [] [name ] [color ] [encap ] byprotocol-mstp [] [name ] [color ] [encap ] bysrcmac [name ] [color ] bysrcmac-mstp [name ] [color ] bysvlan [name ] [color ] bysvlan-mstp [name ] [color ] forIDS [name ] [color ] forIDS-mstp [name ] [color ] config vlan

info add-ring [] addDsapSsap btag-ethertype-apply tls-ipmc ext-filter [port ] [all] mgmt-vlan mmrp removeDsapSsap action add-mlt agetime delete qos-level

Nortel Metro Ethernet Routing Switch 8600 Configuration — VLANs, Spanning Tree, and Link Aggregation NN46220-511 04.01 26 June 2009 Copyright © 2007-2009 Nortel Networks. All Rights Reserved.

Roadmap of VLAN commands

Parameter

Command

name config vlan fdb-entry

info aging-time flush monitor status qos-level status sync

config vlan fdb-filter

info add port [qos ] pcap remove

config vlan fdb-filter notallowfrom

info add port [] remove port []

config vlan fdb-static

info add port [qos ] remove

config vlan ports

info add [member ] remove [member ] ospf-passive

config vlan srcmac

info add remove

config vlan ip

info

Nortel Metro Ethernet Routing Switch 8600 Configuration — VLANs, Spanning Tree, and Link Aggregation NN46220-511 04.01 26 June 2009 Copyright © 2007-2009 Nortel Networks. All Rights Reserved.

235

236

Configuring and managing VLANs using the CLI

Parameter

Command

create [mac_offset ] delete Rvs-Path-Chk [mode ] config vlan ip nlb-unicast-mo de

info

config sys set flag enhanced-operat ional-mode



config ethernet loop-detect

action arp-detect

config ether auto-recover-p ort config ethernet action clearLoopDetectAlarm config ethernet info config mac-flap-time-limit show ports info loop-detected port show sys link-flap-detect general-info show ports info loop-detected port show vlan info all ] [port ] [by ] show vlan info advance ] [port ] show vlan info arp [] [port ] show vlan info basic [] [port ] show vlan info brouter-port [port ]

Nortel Metro Ethernet Routing Switch 8600 Configuration — VLANs, Spanning Tree, and Link Aggregation NN46220-511 04.01 26 June 2009 Copyright © 2007-2009 Nortel Networks. All Rights Reserved.

Configuring and managing a VLAN

237

Parameter

Command show vlan info fdb-entry [] [mac ] [port ] show vlan info fdb-filter [] [mac ] [port ] show vlan info fdb-static [] [mac ] [port ] show vlan info igmp [] [port ] show vlan info ip [] [port ] show vlan info ports [] [port ] show vlan info srcmac [] [port ] show ports info all [vlan ] [port ] [by ] show ports info vlans [vlan ] [port ]

Configuring and managing a VLAN To create VLANs, add or remove ports in the VLAN, set priority, change a VLAN name, or perform other operations, use the VLAN configuration commands. You can also configure reverse path checking, loop detection, Enhanced Operation mode, and other features using the CLI. In all VLAN commands 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)

Nortel Metro Ethernet Routing Switch 8600 Configuration — VLANs, Spanning Tree, and Link Aggregation NN46220-511 04.01 26 June 2009 Copyright © 2007-2009 Nortel Networks. All Rights Reserved.

238

Configuring and managing VLANs using the CLI

Creating a VLAN To create a VLAN, use the following command: config vlan create

You can specify the type of VLAN and assign an IP address to the VLAN using this command. The required parameter vid is the VLAN ID. VLAN 1 is the default VLAN. This command includes the following parameters: config vlan create followed by: info

Shows information about the type of the specified VLAN.

byIDS [name ] [color ]

Creates a VLAN for IDS. is spanning tree ID 1 to 64. name is the name of the vlan from 0 to 64 characters. color is the color of the VLAN (0 to 32). The color attribute is used by Optivity software to display the VLAN. The EVPN services type must be byport and therefore this VLAN type cannot be used for EVPN services.

byipsubnet [ name ] [color ]

Creates an IP subnet-based VLAN.

• •

sid is a spanning tree group ID.

•

name is the name of the VLAN from 0 to 20 characters.

•

color is the color of the VLAN (0 to 32). The color attribute is used by Optivity software to display the VLAN.

ipaddr/mask is the IP address and mask {a.b.c.d/x | a.b.c.d/x.x.x.x | default}.

This command is available only for the Metro Ethernet Routing Switch 8600. The EVPN services type must be byport and therefore this VLAN type cannot be used for EVPN services.

Nortel Metro Ethernet Routing Switch 8600 Configuration — VLANs, Spanning Tree, and Link Aggregation NN46220-511 04.01 26 June 2009 Copyright © 2007-2009 Nortel Networks. All Rights Reserved.

Configuring and managing a VLAN

239

config vlan create followed by: byipsubnet-mstp [name ] [color ]

Creates a VLAN by IP subnet.

• •

is the instance ID from 0 to 63.

• •

name is the name of the VLAN.

is the subnet address or mask {a.b.c.d/x | a.b.c.d/x.x.x.x | default}.

color is the color of the VLAN from 0 to 32. The color attribute is used by Optivity software to display the VLAN.

The EVPN services type must be byport and therefore this VLAN type cannot be used for EVPN services. byport [name ] [color ]

Creates a port-based VLAN.

•

is the spanning tree group ID from 1 to 64 characters.

•

name is the name of the VLAN from 0 to 20 characters.

•

color is the color of the VLAN from 0 to 32. The color attribute is used by Optivity software to display the VLAN.

This VLAN type is the only one supported for EVPN services with STP mode set to default. byport-mstp [name ] [color ] [naap-vlan] [firewall-vlan] [firewall-peering-vlan]

Creates a VLAN by port.

• • • • • •

is the instance ID from 0 to 63. name is the name of the VLAN. color 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 a firewall peering VLAN.

This VLAN type is the only one supported for EVPN services with STP mode set to MSTP. The system checks the consistency with the existing mapping of the Multiple Spanning Tree Instance (MSTI) and the VLAN identifier (VID). If correct, the VLAN is

Nortel Metro Ethernet Routing Switch 8600 Configuration — VLANs, Spanning Tree, and Link Aggregation NN46220-511 04.01 26 June 2009 Copyright © 2007-2009 Nortel Networks. All Rights Reserved.

240

Configuring and managing VLANs using the CLI

config vlan create followed by: created; if not correct, a warning for traffic disruption is displayed and the mapping is updated only when the user confirms the change. byprotocol [] [name ] [color ] [encap ]

Creates a protocol-based VLAN.

• •

is spanning tree ID.

•

pid is a user-defined protocol ID number in hexadecimal.

•

name is the name of the VLAN from 0 to 20 characters.

•

color is the color of the VLAN (0 to 32). The color attribute is used by Optivity software to display the VLAN.

•

encap is the frame encapsulation method.

ip|appleTalk|decLat|decOther|sna802dot2|s naEthernet2|netBios|xns|vines|ipV6|usrDef ined|rarp |PPPoE specifies the protocol.

The EVPN services type must be byport and therefore this VLAN type cannot be used for EVPN services. byprotocol-mstp [ ] [name ] [color ] [encap ]

Creates a VLAN by protocol.

• •

is the instance ID.

• •

is the user-defined PID number.

•

color is the color of the VLAN (0 to 32). The color attribute is used by Optivity software to display the VLAN.

•

encap is the frame encapsulation with the values ethernet-ii, llc, or snap.

is the protocol ID.

name is the name of the VLAN from 0 to 64 characters.

The EVPN services type must be byport and therefore this VLAN type cannot be used for EVPN services.

Nortel Metro Ethernet Routing Switch 8600 Configuration — VLANs, Spanning Tree, and Link Aggregation NN46220-511 04.01 26 June 2009 Copyright © 2007-2009 Nortel Networks. All Rights Reserved.

Configuring and managing a VLAN

241

config vlan create followed by: bysrcmac [name ] [color ]

Creates a VLAN by source MAC address.

• •

is the spanning tree ID from 1 to 64.

•

color is the color of the VLAN (0 to 32). The color attribute is used by Optivity software to display the VLAN.

name is the name of the VLAN from 0 to 20 characters.

This command is available only for the Metro Ethernet Routing Switch 8600. The EVPN services type must be byport and therefore this VLAN type cannot be used for EVPN services. bysrcmac-mstp [name ] [color ]

Creates a VLAN by source MAC address

• •

is the instance ID from 0 to 63.

•

color is the color of the VLAN (0 to 32). The color attribute is used by Optivity software to display the VLAN.

name is the name of the VLAN from 0 to 64 characters.

The EVPN services type must be byport and therefore this VLAN type cannot be used for EVPN services. bysvlan [name ] [color ]

Creates an sVLAN.

• •

is the spanning tree ID from 1 to 64.

•

color is the color of the VLAN (0 to 32). The color attribute is used by Optivity software to display the VLAN.

name is the name of the sVLAN from 0 to 20 characters.

The EVPN services type must be byport and therefore this VLAN type cannot be used for EVPN services.

Nortel Metro Ethernet Routing Switch 8600 Configuration — VLANs, Spanning Tree, and Link Aggregation NN46220-511 04.01 26 June 2009 Copyright © 2007-2009 Nortel Networks. All Rights Reserved.

242

Configuring and managing VLANs using the CLI

config vlan create followed by: bysvlan-mstp [name ] [color ]

Creates an sVLAN.

• • •

is the instance ID from 0 to 63. name is the name of the sVLAN. color is the color of the sVLAN from 0 to 32. The color attribute is used by Optivity software to display the VLAN.

The EVPN services type must be byport and therefore this VLAN type cannot be used for EVPN services. forIDS [name ] [color ]

forIDS-mstp [name ] [color ]

Creates a VLAN for IDS.

• •

is the spanning tree ID from 1 to 64.

•

color is the color of the VLAN (0 to 32). The color attribute is used by Optivity software to display the VLAN.

name is the name of the VLAN from 0 to 20 characters.

Creates a VLAN for IDS

• •

is the instance ID from 0 to 63.

•

color is the color of the VLAN (0 to 32). The color attribute is used by Optivity software to display the VLAN.

name is the name of the VLAN from 0 to 64 characters.

Figure 105 "Config vlan create info command output" (page 243) shows sample output for the config vlan create info command.

Nortel Metro Ethernet Routing Switch 8600 Configuration — VLANs, Spanning Tree, and Link Aggregation NN46220-511 04.01 26 June 2009 Copyright © 2007-2009 Nortel Networks. All Rights Reserved.

Configuring and managing a VLAN

243

Figure 105 Config vlan create info command output

Performing general VLAN operations To 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, use the following command: config vlan In all VLAN commands, vid is the VLAN ID. This command includes the following options: config vlan followed by: info

Shows characteristics of the specified VLAN (Figure 106 "Config vlan info command output" (page 244)).

action

Flushes a table or triggers an RIP update.

•

add-mlt

is {none| flushMacFdb|flush Arp|flushIp| flushDynMemb|all|flushSnoopMemb| triggerRipUpdate|flushSenders| flushSnoopMRtr}. To flush all tables, use all.

Adds an MLT to a VLAN.

•

is the MLT ID.

agetime

Sets the VLAN aging time in seconds.

delete

Deletes a VLAN. The mapping between the Multiple Spanning Tree Instance (MSTI) and the VLAN Identifier (VID) is not deleted.

Nortel Metro Ethernet Routing Switch 8600 Configuration — VLANs, Spanning Tree, and Link Aggregation NN46220-511 04.01 26 June 2009 Copyright © 2007-2009 Nortel Networks. All Rights Reserved.

244

Configuring and managing VLANs using the CLI

config vlan followed by: qos-level

Sets a Quality of Service level for a VLAN.

•

is the QoS level.

QoS level 7 is reserved for network control traffic. name

Changes the name of a VLAN.

•

is a string of length 0 to 20 characters.

Figure 106 "Config vlan info command output" (page 244) shows sample output for the config vlan info command. Figure 106 Config vlan info command output

Configuration example The following configuration example uses the config vlan commands to delete a VLAN. After configuring the parameters, use the info command to show a summary of the results.

Nortel Metro Ethernet Routing Switch 8600 Configuration — VLANs, Spanning Tree, and Link Aggregation NN46220-511 04.01 26 June 2009 Copyright © 2007-2009 Nortel Networks. All Rights Reserved.

Configuring and managing a VLAN

245

MERS-8606:5/config/vlan/10# addDsapSsap 0x0808 MERS-8606:5/config/vlan/10# info Sub-Context: create fdb-entry fdb-filter fdb-static ip ipx ports srcmac static-mcastmac Current Context: action : N/A add-mlt : addDsapSsap : 0x000c,0x0808 removeDsapSsap : N/A agetime : 600 delete : N/A qoslevel : 1 name : VLAN-1000 MERS-8606:5/config/vlan/10# removeDsapSsap 0x0808 MERS-8606:5/config/vlan/10# info Sub-Context: create fdb-entry fdb-filter fdb-static ip ipx ports srcmac static-mcastmac Current Context: action : N/A add-mlt : addDsapSsap : 0x000c removeDsapSsap : N/A agetime : 600 delete : N/A qoslevel : 1 name : VLAN-1000

Configuring VLAN parameters in the forwarding database This 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 forwarding database To configure or modify VLAN entries in the forwarding database, enter the following command: config vlan fdb-entry This command includes the following options:

Nortel Metro Ethernet Routing Switch 8600 Configuration — VLANs, Spanning Tree, and Link Aggregation NN46220-511 04.01 26 June 2009 Copyright © 2007-2009 Nortel Networks. All Rights Reserved.

246

Configuring and managing VLANs using the CLI

config vlan fdb-entry followed by: info

Shows current level parameter settings and next level directories.

aging-time

Sets the forwarding database aging timer.

•

indicates the timeout period in seconds.

flush

Flushes forwarding database.

monitor status

Sets forwarding database monitor parameters.

qos-level status

• •

indicates the MAC address.

•

enables or disables the monitor.

status allows you to view the current status of the forwarding database according to one of the following choices: {other|invalid|learned|self|mgmt}.

Sets a QoS level for a VLAN.

• •

indicates the MAC address.

•

sets the QoS level.

status is the forwarding database status according to one of the following choices: {other|invalid|learned|self|mgmt}.

QoS level 7 is reserved for network control traffic. Synchronizes the switch forwarding database with the forwarding database of the other aggregation switch.

sync

Configuring VLAN filter members To configure VLAN filter members, enter the following command: config vlan fdb-filter

The config vlan fdb-filter command includes the following options: config vlan fdb-filter followed by: info

Shows current level parameter settings and next level directories.

Nortel Metro Ethernet Routing Switch 8600 Configuration — VLANs, Spanning Tree, and Link Aggregation NN46220-511 04.01 26 June 2009 Copyright © 2007-2009 Nortel Networks. All Rights Reserved.

Configuring and managing a VLAN

247

config vlan fdb-filter followed by: add port [qos ]

Adds a filter member to a VLAN bridge.

• • •

indicates the MAC address. port indicates the port (slot/port) number. qos is the QoS level.

QoS level 7 is reserved for network control traffic. pcap

Enables or disables the Packet Capture Tool (PCAP).

•

indicates the MAC address.

For more information about PCAP, see Using the Packet Capture Tool. remove

Removes a filter member from a VLAN bridge.

•

indicates the MAC address.

Configuration example The following configuration example uses the config vlan fdb-filter commands to:

• •

Add a filter member to the VLAN bridge Remove a filter member from a VLAN bridge

After configuring the parameters, use the info command to show a summary of the results. MERS-8606:5/config/vlan/10/fdb-filter# add 2:2:2:2:2:2 port 1/1 MERS-8606:5/config/vlan/10/fdb-filter# info Sub-Context: notallowfrom Current Context: add : mac - 02:02:02:02:02:02 port - 1/1 Pcap - Disable remove : N/A MERS-8606:5/config/vlan/10/fdb-filter# remove 2:2:2:2:2:2 MERS-8606:5/config/vlan/10/fdb-filter# info Sub-Context: notallowfrom Current Context: add : remove : N/A

Nortel Metro Ethernet Routing Switch 8600 Configuration — VLANs, Spanning Tree, and Link Aggregation NN46220-511 04.01 26 June 2009 Copyright © 2007-2009 Nortel Networks. All Rights Reserved.

248

Configuring and managing VLANs using the CLI

Setting or modifying parameters of VLAN not allowed filter member To set or modify VLAN not allowed filter member parameters, enter the following command: config vlan fdb-filter notallowfrom

This command includes the following options: config vlan fdb-filter notallowfrom followed by: info

Shows current level parameter settings and next level directories.

add port []

Adds a not allowed filter member to a VLAN bridge.

• • • remove port []

indicates the MAC address. indicates the port (slot/port) number. is optional to set a mask.

Removes a not allowed filter member from a VLAN bridge.

• • •

indicates the MAC address. indicates the port (slot/port) number. is optional to set a mask.

Configuration example The following configuration example uses the config vlan fdb-filter notallowfrom commands to:

• •

Add a not allowed filter member to a VLAN bridge Remove a not allowed filter member to a VLAN bridge

After configuring the parameters, use the info command to show a summary of the results.

Nortel Metro Ethernet Routing Switch 8600 Configuration — VLANs, Spanning Tree, and Link Aggregation NN46220-511 04.01 26 June 2009 Copyright © 2007-2009 Nortel Networks. All Rights Reserved.

Configuring and managing a VLAN

249

MERS-8606:5/config/vlan/10/fdb-filter# notallowfrom MERS-8606:5/config/vlan/10/fdb-filter/notallowfrom# add 2:2:2:2:2:2 port 1/2 Both MERS-8606:5/config/vlan/1000/fdb-filter/notallowfrom# info Sub-Context: Current Context: add : mac - 02:02:02:02:02:02 Dest Discard set - 1/2 Src Discard set - 1/2 remove : N/A MERS-8606:5/config/vlan/10/fdb-filter/notallowfrom# remove 2:2:2:2:2:2 port 1/2 srcOnly MERS-8606:5/config/vlan/10/fdb-filter/notallowfrom# info Sub-Context: Current Context: add : mac - 02:02:02:02:02:02 Dest Discard set - 1/2 Src Discard set remove : N/A

Configuring VLAN static member parameters To configure VLAN static member parameters, enter the following command: config vlan fdb-static

This command includes the following options: config vlan fdb-static followed by: info

Shows current level parameter settings and next level directories.

add port [qos ]

Adds a static member to a VLAN bridge.

• • •

indicates the MAC address. port indicates the port (slot/port) number. qos is the QoS level.

QoS level 7 is reserved for network control traffic. remove

Removes a static member from a VLAN bridge.

•

indicates the MAC address.

Nortel Metro Ethernet Routing Switch 8600 Configuration — VLANs, Spanning Tree, and Link Aggregation NN46220-511 04.01 26 June 2009 Copyright © 2007-2009 Nortel Networks. All Rights Reserved.

250

Configuring and managing VLANs using the CLI

Limiting MAC learning This feature allows you to limit the number of forwarding database entries learned on a particular port to a user-specified value. After the number of learned forwarding database entries reaches the maximum limit, packets with unknown source MAC addresses are dropped by the hardware. If the count drops below a configured minimum value due to forwarding database aging, learning is reenabled on the port. Users can configure various actions—logging, sending traps, and disabling the port—when the number of forwarding database entries reaches the configured maximum limit. The following CLI commands are implemented for this feature: config ethernet limit-fdb-learning fdbprotect This command enables or disables the feature on the specified ports. The default value is disable. config ethernet limit-fdb-learning max-mac-count This command sets the maximum limit of forwarding database entries (fdb-entries) that can be learned on the specified ports. The default value is 1024. config ethernet limit-fdb-learning min-mac-count This command sets the minimum limit of fdb-entries at which fdb-learning will be reenabled on the specified ports. The default value is 512. config ethernet limit-fdb-learning info This command shows the configuration information related to the feature. config ethernet limit-fdb-learning violation-logtrap This command enables or disables logging to syslog file and trap generation when a maximum limit is reached. The default value is disable. config ethernet limit-fdb-learning violation-down -port This command enables or disables the action taken on the ports in the event of a violation. The default value is disable. Nortel Metro Ethernet Routing Switch 8600 Configuration — VLANs, Spanning Tree, and Link Aggregation NN46220-511 04.01 26 June 2009 Copyright © 2007-2009 Nortel Networks. All Rights Reserved.

Configuring and managing a VLAN

251

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 already enabled, flush the fdb-entries on the particular port using the command config ether action flushMacFdb.

Adding or removing VLAN ports To add or remove ports in the VLAN, enter the following command: config vlan ports

This command includes the following options: config vlan ports followed by: info

Shows member status of the ports in the VLAN (Figure 107 "Config vlan ports info command output" (page 252)).

add [member ]

Adds one or more ports to an existing VLAN.

• • remove [member ]

member is the port member type. It can be portmember (always a member), static (sometimes a member), or notallowed (never a member).

Removes ports from a VLAN but does not delete the VLAN.

• • ospf-passive

is the port list.

is the port list. member is the port member type. It can be portmember (always a member), static (sometimes a member), or notallowed (never a member).

Enables or disables the OSPF passive port.

• •

enables or disables the OSPF port. is the port list.

Figure 107 "Config vlan ports info command output" (page 252) shows sample output for the config vlan ports info command.

Nortel Metro Ethernet Routing Switch 8600 Configuration — VLANs, Spanning Tree, and Link Aggregation NN46220-511 04.01 26 June 2009 Copyright © 2007-2009 Nortel Networks. All Rights Reserved.

252

Configuring and managing VLANs using the CLI

Figure 107 Config vlan ports info command output

Adding or removing VLAN source MAC addresses To add or remove VLAN source MAC addresses, enter the following command: config vlan srcmac

This command includes the following options: config vlan srcmac followed by: info

Shows current level parameter settings and next level directories.

add

Adds a source MAC address to a VLAN.

• remove

is the MAC address to be added.

Removes a source MAC address from a VLAN.

•

is the MAC address to be removed.

Configuring Untagging Default VLAN on a Tagged Port The Untagging Default VLAN on a Tagged Port feature separates untagged packets originating from a PC from the tagged packets originating from a IP phone. The following command enables the Untagging Default VLAN on a Tagged Port feature:

Nortel Metro Ethernet Routing Switch 8600 Configuration — VLANs, Spanning Tree, and Link Aggregation NN46220-511 04.01 26 June 2009 Copyright © 2007-2009 Nortel Networks. All Rights Reserved.

Configuring and managing a VLAN

253

config ethernet untag-port-default-vlan

where is the port of list of ports in slot/port format. Configuring Enhanced Operation mode Enhanced Operation mode enables the Metro Ethernet Routing Switch 8600 to support more VLANs. With MLT, you can create a maximum of 1 980 VLANs (1 972 with R modules in the chassis). With SMLT, the limit is 989 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 Ethernet Routing Switch 8600, use the following command: config sys set flag enhanced-operational-mode

You must save the configuration and reset the switch before the change takes effect. The config sys set flag enhanced-operational-mode command includes the following options: config sys set flag enhanced-operational-mode 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 configure support for up to 1980 VLANs. Figure 108 "Configuration example for supporting 1980 VLANs command output" (page 254) shows sample output for these configuration commands.

Nortel Metro Ethernet Routing Switch 8600 Configuration — VLANs, Spanning Tree, and Link Aggregation NN46220-511 04.01 26 June 2009 Copyright © 2007-2009 Nortel Networks. All Rights Reserved.

254

Configuring and managing VLANs using the CLI

Figure 108 Configuration example for supporting 1980 VLANs command output

Configuring VLAN Loop Detection On a per-port basis, the Loop Detection feature detects MAC addresses that are looping from one port to other ports. After a loop is detected, the port on which the MAC addresses were learned is disabled. Additionally, if a MAC address is found to loop, the MAC address is disabled for that VLAN. 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 (see “Simple Loop Prevention Protocol” (page 90)). For information about the Loop Detection feature, see “VLAN Loop Detection” (page 36). See “SMLT triangle with loop detection configuration example” (page 379) for a CLI loop detection configuration example. To enable or disable loop detection, enter the CLI command: config ethernet loop-detect

The config ethernet loop-detect command includes the following options: Nortel Metro Ethernet Routing Switch 8600 Configuration — VLANs, Spanning Tree, and Link Aggregation NN46220-511 04.01 26 June 2009 Copyright © 2007-2009 Nortel Networks. All Rights Reserved.

Configuring and managing a VLAN

255

config ethernet loop-detect followed by: action

arp-detect

Specifies the loop detect action to be taken.

•

port-down shuts down the port upon detecting a flapping MAC address (an address that is enabled and disabled repeatedly).

•

vlan-block shuts down the VLAN upon detecting a flapping MAC address

•

mac-discard

The ARP-Detect feature is used for IP configured interfaces for ARP packets. This feature should be enabled (in addition to loop detection) on routed interfaces.

The MAC flap time limit is configured by using the mac-flap-time-l imit command. Note that this interval should be staggered between a pair of SMLT switches. By default, the mac-flap-time-limit is set to 500 milliseconds. config mac-flap-time-limit

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" (page 256) shows sample output for these commands.

Nortel Metro Ethernet Routing Switch 8600 Configuration — VLANs, Spanning Tree, and Link Aggregation NN46220-511 04.01 26 June 2009 Copyright © 2007-2009 Nortel Networks. All Rights Reserved.

256

Configuring and managing VLANs using the CLI

Figure 109 Config and show sys link-flap-detect command output

To display the results of loop detection in any VLAN, enter the CLI command: show ports info loop-detected port

To verify whether the loop detection feature is enabled or disabled on the port, enter the CLI command: config ethernet info

The CLI command to enable or disable auto-recovery on individual ports is as follows: config ether auto-recover-port

The default value is disable. The CLI command to set the recovery timer on a port is as follows: config auto-recover-delay

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 action clearLoopDetectAlarm

Figure 110 "Sample configuration using the loop-detect commands." (page 257) shows sample CLI output using the loop detect commands. Nortel Metro Ethernet Routing Switch 8600 Configuration — VLANs, Spanning Tree, and Link Aggregation NN46220-511 04.01 26 June 2009 Copyright © 2007-2009 Nortel Networks. All Rights Reserved.

Configuring and managing a VLAN Figure 110 Sample configuration using the loop-detect commands.

Loop detection warning messages The following log message and trap is generated when MAC address discarding is set due to loop-detect:

Nortel Metro Ethernet Routing Switch 8600 Configuration — VLANs, Spanning Tree, and Link Aggregation NN46220-511 04.01 26 June 2009 Copyright © 2007-2009 Nortel Networks. All Rights Reserved.

257

258

Configuring and managing VLANs using the CLI MAC has been disabled due to MAC flapping more than times in milliseconds from to .

The following log message and trap is generated when a port, which has been disabled due to CP-Limit or link-flap, is auto-recovered: port re-enabled by auto recovery

The following log message and trap is generated when a port which has been disabled due to the loop detection feature is auto-recovered: Loop detect action cleared on port by auto recovery

Configuring spoof detection for a VLAN A port can be configured to prevent IP spoofing by using the following CLI commands. For more information about this feature, see “Prevention of IP spoofing within a VLAN” (page 35). To enable or disable spoof detection, enter the following command: config ethernet spoof-detect

To enable or disable auto-recovery on a port use the command: config ethernet auto-recover-port

If you are using SMLT, be sure to configure spoof detection on both SMLT aggregation switches to avoid connectivity issues.

ATTENTION Enabling the spoof detection feature requires you to reboot the switch.

Using the VLAN show commands To obtain configuration information about all VLANs on the switch or specified VLANs, use the show vlan commands. This section includes the following topics:

• • • •

“Displaying general VLAN information” (page 259)

• •

“Displaying additional parameters” (page 273)

“Displaying forwarding database information” (page 270) “Displaying forwarding database filters” (page 271) “Displaying database status, MAC address, and QoS levels” (page 272)

“Displaying ARP configurations” (page 274) Nortel Metro Ethernet Routing Switch 8600 Configuration — VLANs, Spanning Tree, and Link Aggregation NN46220-511 04.01 26 June 2009 Copyright © 2007-2009 Nortel Networks. All Rights Reserved.

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 information To display all general information about the VLANs on the switch or a specified VLAN, enter the following command: show vlan info all [ ] [port ] [by ]

where is the VLAN ID from 1 to 4092, port is the port or range of ports, by is the group ID. Figure 111 "Show vlan info all command output" (page 260) shows sample output of this command.

Nortel Metro Ethernet Routing Switch 8600 Configuration — VLANs, Spanning Tree, and Link Aggregation NN46220-511 04.01 26 June 2009 Copyright © 2007-2009 Nortel Networks. All Rights Reserved.

260

Configuring and managing VLANs using the CLI

Figure 111 Show vlan info all command output

The following table shows the field descriptions for this command. Table 52 Show vlan info all field descriptions Field

Description

Vlan Basic VLAN ID

Indicates the VLAN ID.

NAME

Indicates the administrator assigned name to the VLAN.

Nortel Metro Ethernet Routing Switch 8600 Configuration — VLANs, Spanning Tree, and Link Aggregation NN46220-511 04.01 26 June 2009 Copyright © 2007-2009 Nortel Networks. All Rights Reserved.

Using the VLAN show commands

261

Table 52 Show vlan info all field descriptions (cont’d.) Field

Description

TYPE

Indicates the type of VLAN, distinguished according to the policy used 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 to determine the state of its ports. If this VLAN is not associated with any STG, it is zero.

PROTOCOLID

Indicates the protocol identifier of this VLAN. For other VLAN types it has the value of none. Options include: none ip appleTalk decLat decOther sna802dot2 snaEthernet2 netBios xns vines ipV6 usrDefined Nortel Metro Ethernet Routing Switch 8600 Configuration — VLANs, Spanning Tree, and Link Aggregation NN46220-511 04.01 26 June 2009 Copyright © 2007-2009 Nortel Networks. All Rights Reserved.

262

Configuring and managing VLANs using the CLI

Table 52 Show vlan info all field descriptions (cont’d.) Field

Description rarp pPPoE

SUBNETADDR

Indicates the IP subnet address of this VLAN. For other VLAN types it has the value of 0.0.0.0.

SUBNETMASK

Indicates the IP subnet mask of this VLAN. For other VLAN types it has the value of 0.0.0.0.

Vlan Port VLAN ID

Indicates the VLAN ID.

PORT MEMBER

Indicates the set of ports that are members (static or dynamic) of this 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 the VLAN policy was met.

STATIC MEMBER

Indicates the set of ports that are static members of this VLAN. A static 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 members of this VLAN.

Vlan ATM Port VLAN ID

Indicates the VLAN ID.

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 VLAN ID

Indicates the VLAN ID.

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 dynamic members of this VLAN. This field is only relevant for policy-based VLANs.

Nortel Metro Ethernet Routing Switch 8600 Configuration — VLANs, Spanning Tree, and Link Aggregation NN46220-511 04.01 26 June 2009 Copyright © 2007-2009 Nortel Networks. All Rights Reserved.

Using the VLAN show commands

Table 52 Show vlan info all field descriptions (cont’d.) Field

Description

MAC ADDRESS

Indicates the MAC address assigned to the virtual router interface of this VLAN. This field is meaningful only if VlanRoutingEnable is equal 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 VLAN ID

Indicates the VLAN ID.

DOPROXY

Indicates if ARP proxy responses are enabled or disabled on the specified interface.

DORESP

Indicates if the sending of ARP responses is enabled or disabled on the specified interface.

Vlan Fdb VLAN ID

Indicates the VLAN ID.

STATUS

Indicates the status of FDB forwarding on the VLAN.

Nortel Metro Ethernet Routing Switch 8600 Configuration — VLANs, Spanning Tree, and Link Aggregation NN46220-511 04.01 26 June 2009 Copyright © 2007-2009 Nortel Networks. All Rights Reserved.

263

264

Configuring and managing VLANs using the CLI

Table 52 Show vlan info all field descriptions (cont’d.) Field

Description

MAC ADDRESS

Indicates the MAC address assigned to the virtual router interface of this VLAN. This field is meaningful only if VlanRoutingEnable is equal to true.

INTERFACE

Indicates the interface.

MONITOR

Indicates whether monitoring is performed on this unicast MAC address. If monitoring is enabled, any packet received with a matching destination MAC address is forwarded to the port configured to receive monitor traffic.

QOS LVL

Indicates the QoS level packets carried in this VLAN for processing.

SMLT REMOTE

Indicates the MAC address for remote learnt, either local or remote.

Vlan Filter VLAN ID

Indicates the VLAN ID.

STATUS

Indicates the status of the VLAN filter.

MAC ADDRESS

Indicates the MAC address assigned to the virtual router interface of this VLAN. This field is meaningful only if VlanRoutingEnable is equal to true.

PORT

Indicates the port number.

QOS LVL

Indicates the QoS level packets carried in this VLAN for processing.

PCAP

Indicates the status of PCAP on the filter.

DEST_DISCARD SET

Indicates a set of ports. Traffic arriving on any of the specified ports from this MAC address.

SRC_DISCARD SET

Indicates a set of ports. Traffic arriving on any of the specified ports is not forwarded to this MAC address.

Vlan Static VLAN ID

Indicates the VLAN ID.

STATUS

Indicates the status of the static VLAN.

MAC ADDRESS

Indicates the MAC address assigned to the virtual router interface of this VLAN. This field is meaningful only if VlanRoutingEnable is equal to true.

PORT

Indicates the port number.

MONITOR

Indicates whether monitoring is performed on this unicast MAC address. If monitoring is enabled, any packet received with a matching destination MAC address is forwarded to the port configured to receive monitor traffic.

QOS LVL

Indicates the QoS level packets carried in this VLAN for processing.

IDS Vlan Info VLAN ID

Indicates the VLAN ID.

Nortel Metro Ethernet Routing Switch 8600 Configuration — VLANs, Spanning Tree, and Link Aggregation NN46220-511 04.01 26 June 2009 Copyright © 2007-2009 Nortel Networks. All Rights Reserved.

Using the VLAN show commands

265

Table 52 Show vlan info all field descriptions (cont’d.) Field

Description

MAC LEARNING

Indicates the type of MAC learning.

DISABLED PORTS

Indicates the disabled port numbers.

Vlan Ip VLAN ID

Indicates the VLAN ID.

IP ADDRESS

Indicates the IP subnet address of this VLAN. This value is meaningful only if the VLAN type is set to IP subnet. For other VLAN types, it has the value of 0.0.0.0.

NET MASK

Indicates the IP subnet mask of this VLAN. This value is meaningful only if the VLAN type is set to IP subnet. For other VLAN types it has 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 can reassemble from incoming IP fragmented datagrams received on this interface.

ADVERTISE WHEN_DOW N

Indicates whether the VLAN state change is notified to Layer 3 or not, provided the VLAN is configured as a routable interface. A VLAN is considered to be up if at least one member of the port-based VLAN has link up, or at least one port member of the policy-based has an entry in the MGID or at least one static member of the policy-based VLAN has link up. Otherwise, a VLAN is considered to be down. If the value is true then the interface state change does not notify to Layer 3. (that is, it always stays up). If the value is false then the VLAN state change is notified to Layer 3 so that 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 take from the source device to the destination device (that is, DHCP client to DHCP server)

MIN SEC

Indicates the minimum number of seconds to wait between receiving a DHCP packet and actually forwarding the DHCP packet to the destination device. A value of zero indicates forwarding should be done immediately without any delay.

Nortel Metro Ethernet Routing Switch 8600 Configuration — VLANs, Spanning Tree, and Link Aggregation NN46220-511 04.01 26 June 2009 Copyright © 2007-2009 Nortel Networks. All Rights Reserved.

266

Configuring and managing VLANs using the CLI

Table 52 Show vlan info all field descriptions (cont’d.) Field

Description

MODE

Indicates what type of DHCP packets this interface should support. A value of none results in all incoming DHCP and BOOTP packets to be dropped. Options include none, bootp, dhcp, and both.

ALWAYS BCAST

Indicates if DHCP reply packets are broadcast to the DHCP client on 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 the Hello packets that the router sends on the interface.

RTRDEAD INTERVAL

Indicates the number of seconds (1 to FFFF) that router Hello packets have not been seen before neighbors declare the router down.

DESIGRTR PRIORITY

Indicates the priority of this interface. Used in multiaccess networks. This field is used in the designated router election algorithm. The value 0 indicates the router is not eligible to become the designated router 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 default is 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 state of 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 must contain the authentication key specified in the interface AuthKey field. MD5 authentication—All OSPF updates received by the interface must contain the MD5 key.

AUTHKEY

Indicates the key (up to 8 characters) required when simple password authentication is specified in the interface AuthType field.

Nortel Metro Ethernet Routing Switch 8600 Configuration — VLANs, Spanning Tree, and Link Aggregation NN46220-511 04.01 26 June 2009 Copyright © 2007-2009 Nortel Networks. All Rights Reserved.

Using the VLAN show commands

267

Table 52 Show vlan info all field descriptions (cont’d.) Field

Description

INTF

Indicates the interface type.

AREA ID

Indicates the area where the host is found. By default, the area that is 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 when advertised 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 an immediate neighbor are not advertised back to the neighbor from which the routes were learned. If enabled, the RIP update sent to a neighbor from which a route is learned is poisoned with a metric of 16. In this manner, the route entry is not passed along to the neighbor, because historically 16 is infinity in terms of hops on a network. The default is disable.

Vlan Ip Igmp VLAN ID

Indicates the VLAN ID.

QUERY INTVL

Indicates the interval (in seconds) between IGMP Host-Query packets transmitted on this interface.

QUERY MAX RESP

Indicates the interval (in seconds) for the maximum query response time advertised in IGMPv2 queries on this interface. Smaller values allow a router to prune groups faster.

ROBUST

Indicates the tuning for the expected packet loss on a subnet. If a subnet is expected to be lossy, the Robustness variable can be increased. IGMP is robust to (Robustness - 1) packet losses.

VERSION

Indicates the version of IGMP that is running on this interface. This object configures a router capable of running either value. For IGMP to function correctly, all routers on a LAN must be configured to run the same version of IGMP on that LAN.

Nortel Metro Ethernet Routing Switch 8600 Configuration — VLANs, Spanning Tree, and Link Aggregation NN46220-511 04.01 26 June 2009 Copyright © 2007-2009 Nortel Networks. All Rights Reserved.

268

Configuring and managing VLANs using the CLI

Table 52 Show vlan info all field descriptions (cont’d.) 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 is enabled.

ADDR

Indicates the IP address this system uses as a source address on this interface.

METRIC

Indicates the distance metric for this interface used to calculate distance vectors.

OPERSTAT

Indicates the current operational state of this DVMRP interface.

DEFAULT LISTEN

Indicates whether the switch can learn DVMRP default routes over this interface.

DEFAULT SUPPLY

Indicates the whether the switch should supply DVMRP default routes over this interface.

DEFAULT METRIC

Indicates the cost of the DVMRP default route that this interface generates 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 this interface.

OUT-POLICY

Indicates the DVMRP announce policy name configured on this interface.

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, or a physical interface for which there is not a querier (subnet).

Vlan Ip Icmp Route Discovery VLAN ID

Indicates the VLAN ID.

ADV_ADDRESS

Indicates the advertisement address to which the route discovery advertisements transmitted on this interface.

ADV_FLAG

Indicates the flag to indicate whether or not the address is to be advertised on this interface.

LIFETIME

Indicates the value to be placed in the lifetime field of router Advertisements sent from the interface.

Nortel Metro Ethernet Routing Switch 8600 Configuration — VLANs, Spanning Tree, and Link Aggregation NN46220-511 04.01 26 June 2009 Copyright © 2007-2009 Nortel Networks. All Rights Reserved.

Using the VLAN show commands

269

Table 52 Show vlan info all field descriptions (cont’d.) Field

Description

MAX_INT

Indicates the maximum time allowed between sending router Advertisements from this interface.

MIN_INT

Indicates the minimum time allowed between sending router Advertisements 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 MAC address.

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 and Sparse.

HELLOINT

Indicates how long to wait (in seconds) before the PIM switch sends out the next hello message to neighboring switches. The default hello interval is 30 seconds.

JPINT

Indicates how long to wait (in seconds) before the PIM switch sends out the next join/prune message to its upstream neighbors. The default 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 is referred to as the preferred BSR. The default is -1, which indicates that 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) before retransmitting the NAK (negative acknowledgement). The default is 1 000 milliseconds.

MAX_NAK_RE XMIT_COUNT

Specifies the maximum number of NAK retransmission packets allowed per second.

Nortel Metro Ethernet Routing Switch 8600 Configuration — VLANs, Spanning Tree, and Link Aggregation NN46220-511 04.01 26 June 2009 Copyright © 2007-2009 Nortel Networks. All Rights Reserved.

270

Configuring and managing VLANs using the CLI

Table 52 Show vlan info all field descriptions (cont’d.) Field

Description

NAK_RDATA INTERVAL

Specifies how long to wait for RDATA (in milliseconds) after receiving an NCF.

NAK_ELIMINATE INTERVAL

Specifies the length of time (in milliseconds) during where a network element (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 NAKs for the specified interval. This parameter must be less than the NAK_RDATA INTERVAL.

Vlan Mcastmac VLAN ID

Indicates the VLAN ID.

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. Options include: none naap enforceable peering

CLUSTER ID

Indicates the firewall cluster ID.

Displaying forwarding database information To display forwarding database information for the specified VLAN, enter the following command: show vlan info fdb-entry [ ] [mac ] [port ]

where is the VLAN ID from 1 to 4 092. port is the port or range of ports in slot/port format. Nortel Metro Ethernet Routing Switch 8600 Configuration — VLANs, Spanning Tree, and Link Aggregation NN46220-511 04.01 26 June 2009 Copyright © 2007-2009 Nortel Networks. All Rights Reserved.

Using the VLAN show commands

271

mac is the MAC address. The , port, and mac are optional parameters. Figure 112 "Show vlan info fdb-entry command output" (page 271) shows sample output for the show vlan info fdb-entry command. Figure 112 Show vlan info fdb-entry command output

See the appropriate section in Table 52 "Show vlan info all field descriptions" (page 260) for an explanation of each heading in the previous figure.

Displaying forwarding database filters To display the forwarding database filters for the specified VLAN, enter the following command: show vlan info fdb-filter [ ] [mac ] [port ]

where is the VLAN ID from 1 to 4 092. port is the port or range of ports in slot/port format. mac is the MAC address. The , 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) shows sample output for the show vlan info fdb-filter command.

Nortel Metro Ethernet Routing Switch 8600 Configuration — VLANs, Spanning Tree, and Link Aggregation NN46220-511 04.01 26 June 2009 Copyright © 2007-2009 Nortel Networks. All Rights Reserved.

272

Configuring and managing VLANs using the CLI

Figure 113 Show vlan info fdb-filter command output

See the appropriate section in Table 52 "Show vlan info all field descriptions" (page 260) for an explanation of each heading in the previous figure.

Displaying database status, MAC address, and QoS levels To 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 [ ] [mac ] [port ]

where is the VLAN ID from 1 to 4 092. port is the port or range of ports in slot/port format. mac is the MAC address. The , port, and macare optional parameters. Figure 114 "Show vlan info fdb-static command output" (page 273) shows sample output for the show vlan info fdb-static command.

Nortel Metro Ethernet Routing Switch 8600 Configuration — VLANs, Spanning Tree, and Link Aggregation NN46220-511 04.01 26 June 2009 Copyright © 2007-2009 Nortel Networks. All Rights Reserved.

Using the VLAN show commands

273

Figure 114 Show vlan info fdb-static command output

See the appropriate section in Table 52 "Show vlan info all field descriptions" (page 260) for an explanation of each heading in the previous figure.

Displaying additional parameters To display additional parameters for the specified VLAN or all VLANs, enter the following command: show vlan info advance [ ] [port ]

where vid is the VLAN ID from 1 to 4 092, port is the port or range of ports. Entering a vid or port is optional. When you enter a vid or port , the command shows information for the specified VLAN or port. Without the vid or port , the command shows information for all the configured VLANs. All zeros in the MAC ADDRESS column indicate that there is no IP address associated with that VLAN. Figure 115 "Show vlan info advance command output" (page 274) shows sample output for the show vlan info advance command.

Nortel Metro Ethernet Routing Switch 8600 Configuration — VLANs, Spanning Tree, and Link Aggregation NN46220-511 04.01 26 June 2009 Copyright © 2007-2009 Nortel Networks. All Rights Reserved.

274

Configuring and managing VLANs using the CLI

Figure 115 Show vlan info advance command output

See the appropriate section in Table 52 "Show vlan info all field descriptions" (page 260) for an explanation of each heading in the previous figure.

Displaying ARP configurations To display the Address Resolution Protocol (ARP) configuration for all VLANs or the specified VLAN, enter the following command: show vlan info arp [ ] [port ]

where vid is the VLAN ID from 1 to 4 092, port is the port or range of ports. Entering a vid or port is optional. When you enter a vid or port , the command shows information for the specified VLAN or port. Without the vid or port , the command shows information for all the configured VLANs.

Nortel Metro Ethernet Routing Switch 8600 Configuration — VLANs, Spanning Tree, and Link Aggregation NN46220-511 04.01 26 June 2009 Copyright © 2007-2009 Nortel Networks. All Rights Reserved.

Using the VLAN show commands

275

Figure 116 "Show vlan info arp command output" (page 275) shows sample output for the show vlan info arp command. Figure 116 Show vlan info arp command output

See the appropriate section in Table 52 "Show vlan info all field descriptions" (page 260) for an explanation of each heading in the previous figure.

Displaying VLAN information To display the basic configuration for all VLANs or a specified VLAN, enter the following command: show vlan info basic [ ] [port ]

where vid is the VLAN ID from 1 to 4 092, port is the port or range of ports. Entering a vid or port is optional. When you enter a vid or port , the command shows information for the specified VLAN or port. Without the vid or port , the command shows information for all the configured VLANs. Figure 117 "Show vlan info basic command output" (page 276) shows sample output for the show vlan info basic command.

Nortel Metro Ethernet Routing Switch 8600 Configuration — VLANs, Spanning Tree, and Link Aggregation NN46220-511 04.01 26 June 2009 Copyright © 2007-2009 Nortel Networks. All Rights Reserved.

276

Configuring and managing VLANs using the CLI

Figure 117 Show vlan info basic command output

See the appropriate section in Table 52 "Show vlan info all field descriptions" (page 260) for an explanation of each heading in the previous figure.

Displaying brouter port information To display the brouter port VLAN information for all VLANs on the switch or for the specified VLAN, enter the following command: show vlan info brouter-port [port ]

where port is the portlist {slot/port[-slot/po rt][,...]}. Entering a value is optional. When you enter a value, the command shows information for the specified port. Without the value, the command shows information for all the configured VLANs. This command is available only for the Metro Ethernet Routing Switch 8600. Figure 118 "Show vlan info brouter-port command output" (page 277) shows sample output for the show vlan info brouter-port command.

Nortel Metro Ethernet Routing Switch 8600 Configuration — VLANs, Spanning Tree, and Link Aggregation NN46220-511 04.01 26 June 2009 Copyright © 2007-2009 Nortel Networks. All Rights Reserved.

Using the VLAN show commands Figure 118 Show vlan info brouter-port command output

Displaying IGMP switch operation information To display information about IGMP operation in the switch, enter the following command: show vlan info igmp [ ] [port ]

where vid is the VLAN ID from 1 to 4 092, port is the port or range of ports. Entering a vid or port is optional. When you enter a vid or port , the command shows information for the specified VLAN or port. Without the vid or port , the command shows information for all the configured VLANs. Figure 119 "Show vlan info igmp command output" (page 277) shows sample output for the show vlan info igmp command. Figure 119 Show vlan info igmp command output

Nortel Metro Ethernet Routing Switch 8600 Configuration — VLANs, Spanning Tree, and Link Aggregation NN46220-511 04.01 26 June 2009 Copyright © 2007-2009 Nortel Networks. All Rights Reserved.

277

278

Configuring and managing VLANs using the CLI

See the appropriate section in Table 52 "Show vlan info all field descriptions" (page 260) for an explanation of each heading in the previous figure.

Displaying VLAN routing (IP) configuration To display the routing (IP) configuration for all VLANs on the switch or for the specified VLAN, enter the following command: show vlan info ip [ ] [port ]

where vid is the VLAN ID from 1 to 4 092, port is the port or range of ports. Entering a vid or port is optional. When you enter a vid or port , the command shows information for the specified VLAN or port. Without the vid or port , the command shows information for all the configured VLANs. Figure 120 "Show vlan info ip command output" (page 278) shows sample output for the show vlan info ip command. Figure 120 Show vlan info ip command output

See the appropriate section in Table 52 "Show vlan info all field descriptions" (page 260) for an explanation of each heading in the previous figure.

Displaying port member status To display the port member status for all VLANs on the switch or for the specified VLAN, enter the following command: show vlan info ports [ ] [port ]

Nortel Metro Ethernet Routing Switch 8600 Configuration — VLANs, Spanning Tree, and Link Aggregation NN46220-511 04.01 26 June 2009 Copyright © 2007-2009 Nortel Networks. All Rights Reserved.

Using the VLAN show commands

where vid is the VLAN ID from 1 to 4 092, port is the port or range of ports. Entering a vid or port is optional. When you enter a vid or port , the command shows information for the specified VLAN or port. Without the vid or port , the command shows information for all the configured VLANs. A port can be an active member, a static member, or a not-allowed member. Figure 121 "Show vlan info ports command output" (page 279) shows sample output for the show vlan info ports command. Figure 121 Show vlan info ports command output

See the appropriate section in Table 52 "Show vlan info all field descriptions" (page 260) for an explanation of each heading in the previous figure.

Nortel Metro Ethernet Routing Switch 8600 Configuration — VLANs, Spanning Tree, and Link Aggregation NN46220-511 04.01 26 June 2009 Copyright © 2007-2009 Nortel Networks. All Rights Reserved.

279

280

Configuring and managing VLANs using the CLI

Displaying source MAC addresses To display the source MAC address for any source MAC-based VLANs on the switch, or for the specified VLAN, if it is source MAC-based, enter the following command: show vlan info srcmac [ ] [port ]

where vid is the VLAN ID from 1 to 4 092, port is the port or range of ports. Entering a vid or port is optional. When you enter a vid or port , the command shows information for the specified VLAN or port. Without the vid or port , the command shows information for all the configured VLANs. Figure 122 "Show vlan info srcmac command output" (page 280) shows sample output for the show vlan info srcmac command. Figure 122 Show vlan info srcmac command output

See the appropriate section in Table 52 "Show vlan info all field descriptions" (page 260) for an explanation of each heading in the previous figure.

Using the show ports commands for VLANs To obtain configuration port information about all VLANs on the switch or specified VLANs, use the show ports commands. This section includes the following topics:

• •

“Displaying port tagging information” (page 281) “Displaying all port VLAN information” (page 282)

Nortel Metro Ethernet Routing Switch 8600 Configuration — VLANs, Spanning Tree, and Link Aggregation NN46220-511 04.01 26 June 2009 Copyright © 2007-2009 Nortel Networks. All Rights Reserved.

Using the show ports commands for VLANs

281

Displaying port tagging information To display VLAN port tagging information, enter the following command: show ports info vlans [vlan ] [port ]

where vlan is the VLAN ID from 1 to 4092, port is the port or range of ports. Entering a vlan or port is optional. When you enter a vlan or port , the command shows information for the specified VLAN or port. Without the vlan or port , the command shows information for all the configured VLANs. Figure 123 "Show ports info vlan command output" (page 281) shows sample output for this command. Figure 123 Show ports info vlan command output

The following table shows the field descriptions for this command. Table 53 Show 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 this access port. When the flag is set, these frames are discarded by the forwarding process. When the flag is reset, these frames are processed normally. This only applies when the port is a trunk port.

Nortel Metro Ethernet Routing Switch 8600 Configuration — VLANs, Spanning Tree, and Link Aggregation NN46220-511 04.01 26 June 2009 Copyright © 2007-2009 Nortel Networks. All Rights Reserved.

282

Configuring and managing VLANs using the CLI

Table 53 Show ports info field descriptions (cont’d.) Field

Description

DISCARD UNTAGFRAM

Indicates the state of how to process untagged frames received on this trunk port. When the flag is set, these frames are discarded by the forwarding process. When the flag is reset, these frames are assigned to the default VLAN ID specified by Default VlanId. This only applies when the port is a trunk port.

DEFAULT VLANID

Indicates the VLAN ID assigned to untagged frames received on this trunk 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 information To display all port VLAN information, enter the following command: show ports info all [vlan ] [port ] [by ]

where vlan is the VLAN ID from 1 to 4092 port is the port or range of ports by is the group ID. Entering a vlan , port or by is optional. When you enter a vlan , port or by , the command shows information for the specified VLAN, port, or group ID. Without optional parameters, the command shows information for all the configured VLANs. Figure 124 "Show ports info port all command output" (page 283) shows sample output for this command.

Nortel Metro Ethernet Routing Switch 8600 Configuration — VLANs, Spanning Tree, and Link Aggregation NN46220-511 04.01 26 June 2009 Copyright © 2007-2009 Nortel Networks. All Rights Reserved.

Using the VLAN IP commands

283

Figure 124 Show ports info port all command output

Table 52 "Show vlan info all field descriptions" (page 260) shows the field descriptions for this command.

Using the VLAN IP commands The VLAN IP commands described in this section are general routing commands for the VLAN. Other VLAN commands are included in the sections of this manual that describe commands used with a specific protocol or feature.

Nortel Metro Ethernet Routing Switch 8600 Configuration — VLANs, Spanning Tree, and Link Aggregation NN46220-511 04.01 26 June 2009 Copyright © 2007-2009 Nortel Networks. All Rights Reserved.

284

Configuring and managing VLANs using the CLI

Assigning an IP address to a VLAN To assign an IP address to a VLAN, use the following command: config vlan ip

where vid is the VLAN ID from 1 to 4 092. Entering a vid is optional. When you enter a vid, the command shows information for the specified VLAN. Without the vid, the command shows information for all the configured VLANs. This command includes the following options: config vlan ip followed by: info

Shows current level parameter settings and next level directories.

create [mac_offset ]

Assigns an IP address and subnet mask to the VLAN.

• •

is the IP address and mask {a.b.c.d}. mac_offset is a user-assigned MAC address. This MAC address is in place of the default MAC address.

delete

Deletes the specified VLAN address.

Rvs-Path-Chk [mode ]

Enables or disables reverse path checking.

•

enables or disables reverse path checking.

•

mode is the mode for reverse path checking—exist-only or strict.

See Configuring and Managing Security () for more information about Reverse Path Checking.

Figure 125 "Config vlan ip info command output" (page 285) shows sample output for the config vlan ip info command.

Nortel Metro Ethernet Routing Switch 8600 Configuration — VLANs, Spanning Tree, and Link Aggregation NN46220-511 04.01 26 June 2009 Copyright © 2007-2009 Nortel Networks. All Rights Reserved.

Using the VLAN IP commands Figure 125 Config vlan ip info command output

Nortel Metro Ethernet Routing Switch 8600 Configuration — VLANs, Spanning Tree, and Link Aggregation NN46220-511 04.01 26 June 2009 Copyright © 2007-2009 Nortel Networks. All Rights Reserved.

285

286

Configuring and managing VLANs using the CLI

Nortel Metro Ethernet Routing Switch 8600 Configuration — VLANs, Spanning Tree, and Link Aggregation NN46220-511 04.01 26 June 2009 Copyright © 2007-2009 Nortel Networks. All Rights Reserved.

287

.

Configuring STGs using the CLI You can set up spanning tree groups (STG) by using the spanning tree group commands. You can set parameters for a group and for ports in that group. You can also enable or disable the Spanning Tree Protocol in an STG. The Metro Ethernet Routing Switch 8600 modules support up to 64 STGs in a switch. This section includes information about configuring STG and its parameters by using the appropriate commands and includes the following topics:

• • • •

“Roadmap of spanning tree commands” (page 287) “Configuring the spanning tree protocol mode” (page 290) “Configuring Spanning Tree Protocol” (page 290) “Configuring Multiple Spanning Tree Protocol” (page 306)

For conceptual information about spanning tree protocols, see “Spanning tree protocols” (page 37).

Roadmap of spanning tree commands The following roadmap lists all spanning tree commands and their parameters. Use this list as a quick reference. Parameter

Command config bootconfig flags spanning-tr ee-mode config mstp

info pathcost-type hop count tx-holdcount

Nortel Metro Ethernet Routing Switch 8600 Configuration — VLANs, Spanning Tree, and Link Aggregation NN46220-511 04.01 26 June 2009 Copyright © 2007-2009 Nortel Networks. All Rights Reserved.

288

Configuring STGs using the CLI

Command

Parameter

config mstp region

info name revision config-id-sel

config mstp cist

info force-version forward-delay max-age priority

config mstp plsb-msti config mstp msti

info priority

show mstp config show mstp instance show mstp stats show mstp status show ports info mstp

cistinfo [vlan ] [port ] mstiinfo [vlan ] [port ] ciststat [vlan ] [port ] mstistat [vlan ] [port ] cistrole [vlan ] [port ] mstirole [vlan ] [port ]

clear ports mstpstats [] config eth mstp cist

info edge-port forceportstate hello-time p2p

Nortel Metro Ethernet Routing Switch 8600 Configuration — VLANs, Spanning Tree, and Link Aggregation NN46220-511 04.01 26 June 2009 Copyright © 2007-2009 Nortel Networks. All Rights Reserved.

Roadmap of spanning tree commands

Parameter

Command

protocol-migration priority pathcost config eth mstp msti

info priority pathcost forceport state

config stg

info add ports create [] [vlan ] [mac ] [type ] [ntstg ] delete forward-delay group-stp hello-interval max-age priority remove ports trap-stp

config ethernet stg

info change-detection faststart pathcost priority stp faststart

show stg show-all show stg info config show stg info status

Nortel Metro Ethernet Routing Switch 8600 Configuration — VLANs, Spanning Tree, and Link Aggregation NN46220-511 04.01 26 June 2009 Copyright © 2007-2009 Nortel Networks. All Rights Reserved.

289

290

Configuring STGs using the CLI

Parameter

Command show ports info stg main [vlan ] [port ] show ports info stg extended [vlan ] [port ] show ports stats stg

Configuring the spanning tree protocol mode There are two spanning tree protocol modes on the Metro Ethernet Routing 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

where mstp|default are the Spanning Tree modes MSTP and Legacy. The default is Legacy. To change the spanning tree mode, you must use the commands save bootconfig to save the boot configuration and boot to reboot the switch. You must start a new session on the switch. The config bootconfig flags spanning-tree-mode command is in the CLI Global configuration mode.

Configuring Spanning Tree Protocol The operation of the Spanning Tree Protocol (STP) is defined in the IEEE 802.1d standard. The STP detects and eliminates logical loops in a bridged or switched network. When multiple paths exist, the spanning tree algorithm configures the network so that a bridge or switch uses only the most efficient path. If that path fails, the protocol automatically reconfigures the network and makes another path active, which sustains network operations. Spanning Tree Protocol is the default spanning tree protocol used by the Metro Ethernet Routing Switch 8600. This section includes the following topics:

• • • •

“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)

Nortel Metro Ethernet Routing Switch 8600 Configuration — VLANs, Spanning Tree, and Link Aggregation NN46220-511 04.01 26 June 2009 Copyright © 2007-2009 Nortel Networks. All Rights Reserved.

Configuring Spanning Tree Protocol

291

Configuring spanning tree group parameters To configure parameters for a specified spanning tree group, enter the following command: config stg

where sid is the spanning tree group ID. This command includes the following options: config stg followed by: info

Shows characteristics of the spanning tree group.

add ports

Adds port to a spanning tree group.

•

specifies one or more slot/port numbers.

Ports can not be added to the STG if they are:

• • create [ ] [vlan ] [mac ] [type ] [ntstg ]

configured as Single Port SMLT configured as members of another STG

Creates a new spanning tree group.

•

specifies one or more slot/port numbers.

Ports cannot be added to the STG if configured as Single Port SMLT, or as a member of another STG.

•

vlan is the VLAN ID. If a VLAN spans multiple switches, it must be within the same STG across all switches.

• •

mac is the MAC address.

•

ntstg enables or disables STP. Choices are enable or disable.

type is the type of STG. Choices are stgnormal, stgsvlan, or stgplsb.

delete

Deletes the specified spanning tree group.

forward-delay

Sets the bridge forward delay time in hundredths of a second. The default is 1500 (15 seconds).

group-stp

Enables or disables the Spanning Tree Protocol on the specified spanning tree group.

hello-interval

Sets the bridge hello time in hundredths of a second. The default is 200 (2 seconds).

Nortel Metro Ethernet Routing Switch 8600 Configuration — VLANs, Spanning Tree, and Link Aggregation NN46220-511 04.01 26 June 2009 Copyright © 2007-2009 Nortel Networks. All Rights Reserved.

292

Configuring STGs using the CLI

config stg followed by: max-age

Sets the bridge maximum age time in hundredths of a second. The default is 2000 (20 seconds).

priority

Sets the bridge priority number.

• remove ports

Removes ports from a spanning tree group.

• trap-stp

is between 0 and 65 35.

is the specified port.

Enables or disables the Spanning Tree Protocol trap for the 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 little possibility of looping, Nortel recommends that you leave the Spanning Tree Protocol enabled. Figure 126 "Config stg info command output" (page 292) shows sample output for the config stg info command. Figure 126 Config stg info command output

Nortel Metro Ethernet Routing Switch 8600 Configuration — VLANs, Spanning Tree, and Link Aggregation NN46220-511 04.01 26 June 2009 Copyright © 2007-2009 Nortel Networks. All Rights Reserved.

Configuring Spanning Tree Protocol

293

Configuring STG port parameters Ports must have tagging enabled to belong to multiple spanning tree groups. Nortel recommends that you enable FastStart as an alternative to disabling Spanning Tree Protocol on an individual port. The Spanning Tree Protocol is currently not supported on SMLT/IST ports, and must be disabled. To configure spanning tree group port parameters, enter the following command: config ethernet stg

where is the slot/port you want to add to the STG. is the spanning tree group ID. This command includes the following options: config ethernet stg followed by: info

Shows current settings for the port spanning tree group.

faststart

Enables or disables the FastStart feature. When FastStart is enabled, the port goes through the normal listening and learning states before forwarding, but the hold time for these states is the bridge hello timer (2 seconds by default) instead of the bridge forward delay timer (15 seconds by default).

change-detection

Enables or disables topology change detection for the specified spanning tree. The default is enable.

pathcost

Sets the contribution of this port to the path cost.

•

is the cost (1 to 65 35).

Nortel Metro Ethernet Routing Switch 8600 Configuration — VLANs, Spanning Tree, and Link Aggregation NN46220-511 04.01 26 June 2009 Copyright © 2007-2009 Nortel Networks. All Rights Reserved.

294

Configuring STGs using the CLI

config ethernet stg followed by: priority

Sets the priority of this port.

•

is the priority (0 to 255).

Although port priority values can range from 0 to 255, only the following values are used: 0, 16, 32, 48, 64, 80, 96, 112, 128, 144, 160, 176, 192, 208, 224, 240 stp

Enables or disables the Spanning Tree Protocol. Spanning Tree Protocol must be disabled on SMLT or IST ports.

To display the current settings for the spanning tree group, use the following command: config ethernet stg info

where is the slot/port you want to add to the STG. is the spanning tree group ID. Figure 127 "Config ethernet slot/port stg sid info command output" (page 294) shows sample output for this command. Figure 127 Config ethernet slot/port stg sid info command output

Nortel Metro Ethernet Routing Switch 8600 Configuration — VLANs, Spanning Tree, and Link Aggregation NN46220-511 04.01 26 June 2009 Copyright © 2007-2009 Nortel Networks. All Rights Reserved.

Configuring Spanning Tree Protocol

295

Configuring topology change detection Change detection is enabled by default. With change detection enabled, when a topology change occurs, a trap is sent containing the MAC address of the STG sending the topology change notification (TCN), the port number, and the STG ID. You can use this information to identify the device. For more information about change detection, see “Spanning Tree Protocol topology change detection” (page 40). To configure topology change detection, use the following command: config ethernet stg change-detection

where is the slot/port you want to add to the STG. is the spanning tree group ID. If you enable change detection on an MLT with access ports, the setting is automatically applied to all ports in the MLT.

Querying the change detection setting To query the change detection setting, use the following command: config ethernet stg info

where is the slot/port you want to add to the STG. is the spanning tree group ID. Figure 127 "Config ethernet slot/port stg sid info command output" (page 294) shows sample output for this command. The show ports info stg main command (Figure 128 "Show ports info stg main command output" (page 296)) also shows the change detection setting.

Nortel Metro Ethernet Routing Switch 8600 Configuration — VLANs, Spanning Tree, and Link Aggregation NN46220-511 04.01 26 June 2009 Copyright © 2007-2009 Nortel Networks. All Rights Reserved.

296

Configuring STGs using the CLI

Figure 128 Show ports info stg main command output

The following table shows the field descriptions for this command. Table 54 Show 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 the first (in network byte order) octet of the (two octet long) port ID.

Nortel Metro Ethernet Routing Switch 8600 Configuration — VLANs, Spanning Tree, and Link Aggregation NN46220-511 04.01 26 June 2009 Copyright © 2007-2009 Nortel Networks. All Rights Reserved.

Configuring Spanning Tree Protocol

297

Table 54 Show ports info stg field descriptions (cont’d.) Field

Description

STATE

Indicates the port current state as defined by the application of the Spanning Tree Protocol. This state controls what action a port takes on reception of a frame. If the bridge has detected a port that is malfunctioning it places that port into the broken state. 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 state upon being enabled.

PATHCOST

Indicates the contribution of this port to the path cost of paths towards the spanning tree root which includes this port. 802.1d-1990 recommends that the default value of this parameter be inversely proportional to the speed of the attached LAN.

FORWARD TRANSITION

Indicates the number of times this port has transitioned from the learning state to the forwarding state.

CHANGE DETECTION

Indicates if topology change notifications are sent for the port.

Using the show STG commands To display the status of spanning tree on the switch or on a port, use the show 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)

Nortel Metro Ethernet Routing Switch 8600 Configuration — VLANs, Spanning Tree, and Link Aggregation NN46220-511 04.01 26 June 2009 Copyright © 2007-2009 Nortel Networks. All Rights Reserved.

298

Configuring STGs using the CLI

Displaying all STG information To display all spanning tree group information, enter the following command: show stg show-all

The command uses the syntax: show stg show-all file

where is the filename to which the output will be redirected. Figure 129 "Show stg show-all sample output" (page 299) shows sample output for this command.

Nortel Metro Ethernet Routing Switch 8600 Configuration — VLANs, Spanning Tree, and Link Aggregation NN46220-511 04.01 26 June 2009 Copyright © 2007-2009 Nortel Networks. All Rights Reserved.

Configuring Spanning Tree Protocol

299

Figure 129 Show stg show-all sample output

The following table shows the field descriptions for this command. Table 55 Show 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 the first (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 maximum age when this bridge acts as the root.

Nortel Metro Ethernet Routing Switch 8600 Configuration — VLANs, Spanning Tree, and Link Aggregation NN46220-511 04.01 26 June 2009 Copyright © 2007-2009 Nortel Networks. All Rights Reserved.

300

Configuring STGs using the CLI

Table 55 Show stg show-all field descriptions (cont’d.) Field

Description

BRIDGE HELLO_TIME

Indicates the value that all bridges use for the bridge hello timer when this bridge acts as the root.

FORWARD DELAY

Indicates the value that all bridges use for forward delay when this bridge acts as the root. This time value, measured in units of hundredths of a second, controls how fast a port changes its spanning state when moving towards the forwarding state. The value determines how long the port stays in each of the listening and learning states, which precede the forwarding state. This value is also used, when a topology change is detected and is underway, to age all dynamic entries in the forwarding 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 which are sent for this STG.

NT-STG

Indicates the whether this STG is operating in Nortel mode or in Cisco mode.

• •

enable—Nortel mode disable—Cisco mode

Stg Status STG ID

Indicates the STG identifier.

BRIDGE ADDRESS

Indicates the MAC address used by this bridge when it must be referred to in a unique fashion. Nortel recommends that this be the numerically smallest MAC address of all the ports that belong 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 is used. The value decLb100 indicates the DEC LAN bridge 100 Spanning Tree protocol. IEEE 802.1d implementations will return ieee8021d.

TOP CHANGES

Indicates the total number of topology changes detected by this bridge since the management entity was last reset or initialized.

DESIGNATED ROOT

Indicates the bridge identifier of the root of the spanning tree as determined by the Spanning Tree Protocol as executed by this node. This value is used as the root identifier parameter in all configuration Bridge PDUs originated by this node.

ROOT COST

Indicates the cost of the path to the root as seen from this bridge.

ROOT PORT

Indicates the port number of the port that offers the lowest cost path from this bridge to the root bridge.

Nortel Metro Ethernet Routing Switch 8600 Configuration — VLANs, Spanning Tree, and Link Aggregation NN46220-511 04.01 26 June 2009 Copyright © 2007-2009 Nortel Networks. All Rights Reserved.

Configuring Spanning Tree Protocol

301

Table 55 Show stg show-all field descriptions (cont’d.) Field

Description

MAX AGE

Indicates the maximum age of Spanning Tree Protocol information learned from the network on any port before it is discarded, in units of hundredths of a second. This is the actual value that this bridge is currently using.

HELLO TIME

Indicates the amount of time between the transmission of configuration bridge PDUs by this node on any port when it is the root of the spanning tree or trying to become so, in units of hundredths of a second. This is the actual value that this bridge is currently using.

HOLD TIME

Indicates the interval length during which no more than two configuration bridge PDUs are transmitted by this node, in units of hundredths of a second.

FORWARD DELAY

Indicates the how fast (in hundredths of a second) a port changes its spanning state when moving towards the Forwarding state. The value determines how long the port stays in each of the listening and learning states, which precede the forwarding state. This value is also used, when a topology change is detected and is underway, to age all dynamic entries in the forwarding database. This value is the one that this bridge is currently using, in contrast to the bridge forward delay which is the value that this bridge and all others would start using if this bridge were to become the root.

Displaying STG configurations To display the spanning tree group configuration for the switch or for the specified spanning tree group, enter the following command: show stg info config The command syntax is: show stg info config

where is the spanning tree group ID. Figure 130 "Show stg info config command output" (page 302) shows sample output for the show stg info config command.

Nortel Metro Ethernet Routing Switch 8600 Configuration — VLANs, Spanning Tree, and Link Aggregation NN46220-511 04.01 26 June 2009 Copyright © 2007-2009 Nortel Networks. All Rights Reserved.

302

Configuring STGs using the CLI

Figure 130 Show stg info config command output

For descriptions of the parameters for this command, see Table 55 "Show stg show-all field descriptions" (page 299).

Displaying STG status To display the spanning tree group status for the specified spanning tree group or all STGs, enter the following command: show stg info status

where is the spanning tree group ID. Figure 131 "Show stg info status command output" (page 303) shows sample output for the show stg info status command.

Nortel Metro Ethernet Routing Switch 8600 Configuration — VLANs, Spanning Tree, and Link Aggregation NN46220-511 04.01 26 June 2009 Copyright © 2007-2009 Nortel Networks. All Rights Reserved.

Configuring Spanning Tree Protocol

303

Figure 131 Show stg info status command output

For descriptions of the parameters for this command, see Table 55 "Show stg show-all field descriptions" (page 299).

Displaying basic STG information To display basic spanning tree group information about one or more specified ports or about all ports, enter the following command: show ports info stg main [vlan ] [port ]

where vlan is the VLAN ID from 1 to 4 092, port is the port or range of ports. Entering a vlan or port is optional. When you enter a vlan or port , the command shows information for the specified VLAN or port. Without the vlan or port , the command shows information for all the configured VLANs. (For more information about the show ports info stg extended command, see “Displaying basic STG information” (page 303).) Figure 132 "Show ports info stg main command output" (page 304) shows sample output for the show ports info stg main command.

Nortel Metro Ethernet Routing Switch 8600 Configuration — VLANs, Spanning Tree, and Link Aggregation NN46220-511 04.01 26 June 2009 Copyright © 2007-2009 Nortel Networks. All Rights Reserved.

304

Configuring STGs using the CLI

Figure 132 Show ports info stg main command output

For descriptions of the parameters for this command, see Table 54 "Show ports info stg field descriptions" (page 296).

Displaying additional STG information To display additional spanning tree group information about the specified port or about all ports, enter the following command: show ports info stg extended [vlan ] [port ]

where vlan is the VLAN ID from 1 to 4 092, port is the port or range of ports. Entering a vlan or port is optional. When you enter a vlan or port , the command shows information for the specified VLAN or port. Without the vlan or port , the command shows information for all the configured VLANs. This information is less often used in switch monitoring than the information obtained with the show ports info stg main command ( “Displaying basic STG information” (page 303)). Figure 133 "Show ports info stg extended command output" (page 305) shows sample output for the show ports info stg extended command.

Nortel Metro Ethernet Routing Switch 8600 Configuration — VLANs, Spanning Tree, and Link Aggregation NN46220-511 04.01 26 June 2009 Copyright © 2007-2009 Nortel Networks. All Rights Reserved.

Configuring Spanning Tree Protocol

305

Figure 133 Show ports info stg extended command output

The following table shows the field descriptions for this command. Table 56 Show ports info stg extended field descriptions Field

Description

STG ID

Indicates the STG identifier.

PORT NUM

Indicates the port and slot number.

DESIGNATED ROOT

Indicates the bridge identifier of the root of the spanning tree as determined by the Spanning Tree Protocol as executed by this node. This value is used as the root identifier parameter in all configuration bridge PDUs originated by this node.

DESIGNATED ROOT COST

Indicates the cost of the path to the root as seen from this bridge.

DESIGNATED BRIDGE ADDRESS

Indicates the MAC address used by this bridge when it must be referred to in a unique fashion. Nortel recommends that this be the numerically smallest MAC address of all the ports that belong to this bridge.

DESIGNATED ROOT PORT

Indicates the port number of the port that offers the lowest cost path from this bridge to the root bridge.

Displaying STG statistics counters To display statistics counters for spanning tree groups on all ports or the specified port, enter the following command: show ports stats stg Nortel Metro Ethernet Routing Switch 8600 Configuration — VLANs, Spanning Tree, and Link Aggregation NN46220-511 04.01 26 June 2009 Copyright © 2007-2009 Nortel Networks. All Rights Reserved.

306

Configuring STGs using the CLI

where is the port or list of ports. Figure 134 "Show ports stats stg command (partial output)" (page 306) shows sample output for the show ports stats stg command. Figure 134 Show ports stats stg command (partial output)

The following table shows the field descriptions for this command. Table 57 Show ports stats stg extended field descriptions Field

Description

PORT NUM

Indicates the port and slot number.

IN_CONFIG BPDU

Indicates the number of configuration BPUs received by this port.

IN_TCN BPDU

Indicates the number of topology change notification BPUs received by this port.

IN_BAD BPDU

Indicates the number of bad BPUs received by this port.

OUT_CONFIG BPDU

Indicates the number of Config BPUs transmitted by this port.

OUT_TCN BPDU

Indicates the number of topology change notification BPUs transmitted by this port.

Configuring Multiple Spanning Tree Protocol This section describes the following topics:

• • •

“Configuring Multiple Spanning Tree Protocol” (page 307) “Configuring MSTP region” (page 308) “Configuring MSTP CIST” (page 309)

Nortel Metro Ethernet Routing Switch 8600 Configuration — VLANs, Spanning Tree, and Link Aggregation NN46220-511 04.01 26 June 2009 Copyright © 2007-2009 Nortel Networks. All Rights Reserved.

Configuring Multiple Spanning Tree Protocol

• • • • • • •

307

“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 Protocol You can configure multiple spanning trees using MSTP for an individual VLAN 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. This command includes the following options: config mstp followed by: info

Shows current level parameter settings and next level directories.

pathcost-type

Sets the MSTP default path cost version; default is 32 bits.

hop count

Sets the MSTP hop count. The range is 400 to 4000 hundredths of a second; default is 2000.

tx-holdcount

Sets the MSTP Transmit Hold Count. The range is 1 to 10; the default is 3.

pbt-msti

Specifies the Multiple Spanning Tree Instance (MSTI) dedicated to this PBT. Specify a number between 1 and 63. A value of 0 is used to clear the PBT MSTI. If VLANs are already mapped to the MSTI, the VLANs must be unmapped before you configure the MSTP.

plsb-msti

Specifies the Multiple Spanning Tree Instance (MSTI) as PLSB type.

Nortel Metro Ethernet Routing Switch 8600 Configuration — VLANs, Spanning Tree, and Link Aggregation NN46220-511 04.01 26 June 2009 Copyright © 2007-2009 Nortel Networks. All Rights Reserved.

308

Configuring STGs using the CLI

config mstp followed by: Specify a number between 1 and 63. A value of 0 is used to clear the PLSB MSTI.

Figure 135 "Config mstp info command" (page 308) shows sample output for the config mstp info command. Figure 135 Config mstp info command

Configuring MSTP region To configure the MSTP region, use the following command: config mstp region

The config mstp region command is in the CLI Global configuration mode. This command includes the following options: config mstp region followed by: info

Shows current level parameter settings and next level directories.

name

Sets the MSTP configuration name.

• revision

is from 1 to 32 characters.

Sets the MSTP region revision number

• config-id-sel

is between 0 and 65 535.

Sets the MSTP region configuration ID number.

•

is between 0 and 255.

The following figure shows sample output for the config mstp region commands.

Nortel Metro Ethernet Routing Switch 8600 Configuration — VLANs, Spanning Tree, and Link Aggregation NN46220-511 04.01 26 June 2009 Copyright © 2007-2009 Nortel Networks. All Rights Reserved.

Configuring Multiple Spanning Tree Protocol

309

Figure 136 Config mstp region command

Configuring MSTP CIST To configure the MSTP Common and Internal Spanning Tree (CIST) parameters, use the following command: config mstp cist

This command includes the following options: config mstp cist followed by: info

Shows current level parameter settings and next level directories.

force-version

Sets the CIST version.

forward-delay

Sets the CIST forward delay from 400 to 3000 hundredths of a second; default is 1500.

max-age

Sets the CIST maximum age time from 600 to 4000 hundredths of a second for the bridge; the default is 2000. The step size is in hundreds.

priority

Sets the CIST bridge priority from 0 to 61 440 in steps of 4096; the default is 32 768.

The following figure shows sample output of these commands.

Nortel Metro Ethernet Routing Switch 8600 Configuration — VLANs, Spanning Tree, and Link Aggregation NN46220-511 04.01 26 June 2009 Copyright © 2007-2009 Nortel Networks. All Rights Reserved.

310

Configuring STGs using the CLI Figure 137 Config mstp cist command

Configuring MSTP MSTI To set the Multiple Spanning Tree Instance (MSTI) configuration version, use the following command: config mstp msti

where is the instance ID. The config mstp msti command is in the CLI Instance configuration mode. This command uses the following options: config mstp msti followed by: info

Shows current level parameter settings and next level directories. The MSTI to VLAN mapping is included in the displayed information.

priority

Sets the MSTP bridge priority. Allowed values are 4096, 8192, 12 288, 16 384, 20 480, 24 576, 28 672, 32 768, 36 864, 40 960, 45 056, 49 152, 53 248, 57 344, 61 440.

Mapping an MSTI to a VLAN A Multiple Spanning Tree Instance-VLAN identifier (MSTI-VID) pool can be created before VLANs are created. The configuration digest for the node is calculated based on the MSTI-VID pool. VLANs can therefore be added and removed without having a negative impact on traffic.

Nortel Metro Ethernet Routing Switch 8600 Configuration — VLANs, Spanning Tree, and Link Aggregation NN46220-511 04.01 26 June 2009 Copyright © 2007-2009 Nortel Networks. All Rights Reserved.

Configuring Multiple Spanning Tree Protocol

311

To map an MSTI to a VLAN or a range of VLANs, use the following command: config mstp msti add-vlans This command uses the following options: config mstp msti add-vlans 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. The VLAN range. Valid values are: 2 to 4094.



To specify a list of VLANs, use a comma. For example: configure mstp msti 1 vlan 10, 20, 30 To specify a list and a range of VLANs, use a comma and a dash. For example: configure mstp msti 1 vlan 10, 20,30-40,42 If a specified VLAN is mapped to an instance other than the specified instance ID, a message is displayed to warn you that traffic may be impacted. A VLAN-MSTI mapping cannot be changed if the VLAN currently exists. An error is displayed if the specified VLAN is configured on the switch and it is not mapped to the specified instance. You must delete the VID first.

To unmap an MSTI from a VLAN or a range of VLANs, use the following command: config mstp msti remove-vlans For variable information, see the preceding table.

Showing MSTP configurations To display the Multiple Spanning Tree Protocol (MSTP) related bridge-level VLAN and region information, use the following command: show mstp config

Nortel Metro Ethernet Routing Switch 8600 Configuration — VLANs, Spanning Tree, and Link Aggregation NN46220-511 04.01 26 June 2009 Copyright © 2007-2009 Nortel Networks. All Rights Reserved.

312

Configuring STGs using the CLI

The show mstp config command is in the CLI Global configuration mode. Figure 138 "Show mstp config." (page 312) shows sample output for this command. Figure 138 Show mstp config.

The following table shows the field descriptions for this command. Table 58 show 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 the module.

Cist Bridge priority

Indicates the CIST bridge priority.

Stp Version

Indicates the STP version.

Cist Bridge Max Age

Indicates the CIST bridge maximum age in seconds.

Cist Bridge Forward Delay

Indicates the CIST bridge forwarding delay in seconds.

Tx Hold Count

Indicates the transmission hold count.

Nortel Metro Ethernet Routing Switch 8600 Configuration — VLANs, Spanning Tree, and Link Aggregation NN46220-511 04.01 26 June 2009 Copyright © 2007-2009 Nortel Networks. All Rights Reserved.

Configuring Multiple Spanning Tree Protocol

313

Table 58 show 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 identification selector.

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 value is generated automatically by the Metro Ethernet Routing Switch.

Showing MSTP instance information To show the MSTP instance-specific bridge and VLAN information, use the following command: show mstp instance

where is the instance ID. Figure 139 "Show mstp instance command" (page 313) shows sample output for this command. Figure 139 Show mstp instance command

Nortel Metro Ethernet Routing Switch 8600 Configuration — VLANs, Spanning Tree, and Link Aggregation NN46220-511 04.01 26 June 2009 Copyright © 2007-2009 Nortel Networks. All Rights Reserved.

314

Configuring STGs using the CLI

The following table shows the field descriptions for this command. Table 59 show mstp instance field descriptions Field

Description

Instance ID

Indicates the MSTP MSTI instance ID.

Msti Bridge Regional Root

Indicates the MSTP MSTI bridge regional root address.

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 Vlan Mapped

The four variables that begin with Msti Instance Vlan Mapped show which VLANs are assigned to the MSTI. The range is 4000. In an effort to simplify the display of this range, VLAN mapping is divided into clusters of 1000 VLANs per variable name. Msti Instance Vlan Mapped indicates the MSTP MSTI instance VLAN mapped between 1 and 1 024. The mapping for the instance is displayed even when there is no VLAN created for the instance.

Msti Instance Vlan Mapped2k

Indicates the MSTP MSTI instance VLAN mapped.

Msti Instance Vlan Mapped3k

Indicates the MSTP MSTI instance VLAN mapped.

Msti Instance Vlan Mapped4k

Indicates the MSTP MSTI instance VLAN mapped.

Showing MSTP bridge statistics information To display the MSTP related bridge-level statistics, use the following command: 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 this command.

Nortel Metro Ethernet Routing Switch 8600 Configuration — VLANs, Spanning Tree, and Link Aggregation NN46220-511 04.01 26 June 2009 Copyright © 2007-2009 Nortel Networks. All Rights Reserved.

Configuring Multiple Spanning Tree Protocol

315

Figure 140 Show mstp stats

The following table shows the field descriptions for this command. Table 60 Show mstp stats field descriptions Field

Description

Mstp UP Count

Indicates the MSTP up count.

Mstp Down Count

Indicates the MSTP down count.

Region Config Change Count

Indicates the number of region configuration changes.

Time since topology change

Indicates how long ago in seconds the STP topology changed.

Topology change count

Indicates the number of topology changes.

New Root Bridge Count

Indicates the number of new root bridges.

Showing MSTP status To display the MSTP related status information known by the selected bridge, use the following command: show mstp status

The show mstp status command is in the CLI Global configuration mode. Figure 141 "Show mstp status command" (page 316) shows sample output for this command.

Nortel Metro Ethernet Routing Switch 8600 Configuration — VLANs, Spanning Tree, and Link Aggregation NN46220-511 04.01 26 June 2009 Copyright © 2007-2009 Nortel Networks. All Rights Reserved.

316

Configuring STGs using the CLI Figure 141 Show mstp status command

Showing MSTP port information To display the MSTP, CIST port, and MSTI port information maintained by every port of the Common Spanning Tree, use the following command: show ports info mstp

This command includes the following parameters: show ports info mstp followed by: cistinfo [vlan ] [port ]

Shows port CIST configuration.

• • mstiinfo [vlan ] [port ]

port specifies the portlist.

Shows port MSTI configuration.

• • ciststat [vlan ] [port ]

vlan specifies the VLAN IDs.

vlan specifies the VLAN IDs. port specifies the portlist.

Shows statistics for CIST port.

• •

vlan specifies the VLAN IDs. port specifies the portlist.

Nortel Metro Ethernet Routing Switch 8600 Configuration — VLANs, Spanning Tree, and Link Aggregation NN46220-511 04.01 26 June 2009 Copyright © 2007-2009 Nortel Networks. All Rights Reserved.

Configuring Multiple Spanning Tree Protocol

317

show ports info mstp followed by: mstistat [vlan ] [port ]

Shows port MSTI stats.

• • cistrole [vlan ] [port ]

port specifies the portlist.

Shows port CIST port role.

• • mstirole [vlan ] [port ]

vlan specifies the VLAN IDs.

vlan specifies the VLAN IDs. port specifies the portlist.

Shows port MSTI port role.

• •

vlan specifies the VLAN IDs. port specifies the portlist.

ATTENTION You can clear the MSTP ports CIST and MSTI stats using the following command:clear ports mstpstats []

External and internal path costs are displayed incorrectly in the show ports info CLI output for the CIST and MST. Figure 142 "Show ports info mstp cistinfo command output" (page 318) shows sample output for this command.

Nortel Metro Ethernet Routing Switch 8600 Configuration — VLANs, Spanning Tree, and Link Aggregation NN46220-511 04.01 26 June 2009 Copyright © 2007-2009 Nortel Networks. All Rights Reserved.

318

Configuring STGs using the CLI Figure 142 Show ports info mstp cistinfo command output

Configuring Ethernet MSTP CIST To configure the Ethernet MSTP CIST parameters for a port, use the following command: config eth mstp cist

where is the port list. The config eth mstp cist command is in the CLI Global configuration mode. Nortel Metro Ethernet Routing Switch 8600 Configuration — VLANs, Spanning Tree, and Link Aggregation NN46220-511 04.01 26 June 2009 Copyright © 2007-2009 Nortel Networks. All Rights Reserved.

Configuring Multiple Spanning Tree Protocol

319

This command includes the following options: config eth mstp cist followed by: info

Shows current level parameter settings and next level directories.

edge-port

Sets the MSTP edge port parameter for the port.

forceportstate

Set forceportstate for a port.

hello-time

Sets the hello time for a port from 100 to 1000 hundredths of a second.

p2p

Sets the Ethernet MSTP CIST point-to-point parameter for the port.

protocol-migration

Sets the Ethernet MSTP CIST protocol-migration parameter for the port.

priority

Sets the Ethernet MSTP CIST priority parameter for the port. The priority must be set in steps of 16 within the range of 0 to 240.

pathcost

Sets the MSTP path cost parameter for the port.

stp

Sets STP for a port. The default is enable.

Configuring Ethernet MSTP MSTI To configure the Ethernet MSTP MSTI parameters on a port, use the following command: config eth mstp msti

where is the port list, and is the instance ID. The config eth mstp msti command is in the CLI Global configuration mode. This command includes the following options: config eth mstp msti followed by: info

Shows current level parameter settings and next level directories.

Nortel Metro Ethernet Routing Switch 8600 Configuration — VLANs, Spanning Tree, and Link Aggregation NN46220-511 04.01 26 June 2009 Copyright © 2007-2009 Nortel Networks. All Rights Reserved.

320

Configuring STGs using the CLI

config eth mstp msti followed by: priority

Sets the Ethernet MSTP MSTI priority parameter for the port.

pathcost

Sets the MSTP MSTI path cost parameter for the port.

forceport state

Sets the MSTP MSTI force port state parameter for the port.

stp

Sets STP for a port. The default is enable.

Nortel Metro Ethernet Routing Switch 8600 Configuration — VLANs, Spanning Tree, and Link Aggregation NN46220-511 04.01 26 June 2009 Copyright © 2007-2009 Nortel Networks. All Rights Reserved.

321

.

Configuring link aggregation using the CLI 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 both UNI and NNI. This section includes the following topics:

• • • • •

“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 commands The following roadmap lists the commands used for configuring link aggregation. Command

Parameter

config mlt

info create cp-limit [multicast-limit ] [broadcast-limit ] delete

Nortel Metro Ethernet Routing Switch 8600 Configuration — VLANs, Spanning Tree, and Link Aggregation NN46220-511 04.01 26 June 2009 Copyright © 2007-2009 Nortel Networks. All Rights Reserved.

322

Configuring link aggregation using the CLI

Parameter

Command

mcast-distribution name perform-tagging svlan-porttype ntstg config mlt add

info ports vlan

config mlt remove

info ports vlan

config lacp

info enable disable aggr-wait-time system-priority smlt-sys-id fast-periodic-time slow-periodic-time timeout-scale

config mlt lacp

info enable disable clear-link-aggrgate key system-priority

config lacp info enable disable aggr-wait-time fast-periodic-time

Nortel Metro Ethernet Routing Switch 8600 Configuration — VLANs, Spanning Tree, and Link Aggregation NN46220-511 04.01 26 June 2009 Copyright © 2007-2009 Nortel Networks. All Rights Reserved.

Roadmap of link aggregation commands 323

Parameter

Command

key aggregation mode partner-key partner-port partner-port-priority partner-state partner-system-id partner-system-priority port-priority slow-periodic-time system-priority port-priority slow-periodic-time system-priority timeout timeout-scale show lacp info show ports info lacp

all [vlan ] [port ] actor-admin [vlan ] [port ] actor-oper [vlan ] [port ] partner-admin [vlan ] [port ] partner-oper [vlan ] [port ] extension [vlan ] [port ]

show ports stats lacp [port ] show mlt lacp info

Nortel Metro Ethernet Routing Switch 8600 Configuration — VLANs, Spanning Tree, and Link Aggregation NN46220-511 04.01 26 June 2009 Copyright © 2007-2009 Nortel Networks. All Rights Reserved.

324

Configuring link aggregation using the CLI

Command

Parameter

config mlt smlt

info create smlt-id delete

config mlt ist

info create ip vlan-id delete disable enable

config ethernet cp-limit

multicast-limit broadcast-limit

config ethernet smlt

info create delete

config sys set smlt-on-single-cp [timer ] show mlt show-all [file ] show mlt error collision [] show mlt error main [] show mlt info [] show mlt ist info show mlt stats [] show ports info smlt [vlan ] [port ] show ports info config [vlan ] [port ] show smlt info [] config fdb fdb-filter

info add

Nortel Metro Ethernet Routing Switch 8600 Configuration — VLANs, Spanning Tree, and Link Aggregation NN46220-511 04.01 26 June 2009 Copyright © 2007-2009 Nortel Networks. All Rights Reserved.

Configuring link aggregation

325

Parameter

Command

remove config slpp

info add remove add uni-ports remove uni-ports operation etherType tx-interval

config ethernet slpp

info packet-rx-threshold packet-rx clear-packet-rx-count

show slpp

info port

Configuring link aggregation 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 includes configuration commands for the following topics:

• • • • • • • •

“Link aggregation commands” (page 326)

• • •

“Creating an interswitch trunk” (page 339)

“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” (page 338)

“Creating a single port split multilink trunk” (page 343) “Configuring SMLT-on-Single-CPU” (page 344)

Nortel Metro Ethernet Routing Switch 8600 Configuration — VLANs, Spanning Tree, and Link Aggregation NN46220-511 04.01 26 June 2009 Copyright © 2007-2009 Nortel Networks. All Rights Reserved.

326

Configuring link aggregation using the CLI

Link aggregation commands To set up multilink trunks on the switch, enter the following command: config mlt

where is the multilink trunk ID. The required parameter mid specifies the link aggregation ID. This command includes the following options: config mlt followed by: info

Shows current settings for the specified link aggregation group.

create

Creates a link aggregation group.

cp-limit [multica st-limit ] [broadcast-limit ]

Sets the control packet rate limit.

•

= Enables or disables control packet rate limit. To reenable the ports, issue the command config ethernet slot/port state disable, and then enable.

•

multicast-limit is the multicast control frame rate.

•

broadcast-limit is the broadcast frame rate.

delete

Deletes a link aggregation group.

mcast-distribution

Enables or disables multicast distribution per link aggregation group. Multicast distribution is disabled by default. For detailed information about commands used to configure multicast distribution over link aggregation, see Configuration — IP Multicast (NN46220-519).

name

Names a link aggregation group.

• perform-tagging

is the name, from 0 to 20 characters.

Enables or disables tagging on a link aggregation port.

Nortel Metro Ethernet Routing Switch 8600 Configuration — VLANs, Spanning Tree, and Link Aggregation NN46220-511 04.01 26 June 2009 Copyright © 2007-2009 Nortel Networks. All Rights Reserved.

Configuring link aggregation

327

config mlt followed by: svlan-porttype

Sets the port type to normal, uni, or nni.

ntstg

Enables or disables NTSTG.

Figure 143 "Config mlt info command output" (page 327) shows sample output for the config mlt info command. Figure 143 Config mlt info command output

Adding ports to a link aggregation group To add Ethernet ports to an LACP MLT, ensure the ports and MLT are in the appropriate VLANs; the LACP keys match; and LACP is enabled on the ports, on MLT, and globally. For more information, see “LACP-based MLT for UNI configuration example” (page 404) and “LACP-based MLT for NNI configuration example” (page 405).

Removing ports from a link aggregation group To remove Ethernet ports from an LACP MLT, disable LACP on the Ethernet port, change the key back to the default, and make aggregation false. For more information, see “LACP-based MLT for UNI configuration example” (page 404) and “LACP-based MLT for NNI configuration example” (page 405). Nortel Metro Ethernet Routing Switch 8600 Configuration — VLANs, Spanning Tree, and Link Aggregation NN46220-511 04.01 26 June 2009 Copyright © 2007-2009 Nortel Networks. All Rights Reserved.

328

Configuring link aggregation using the CLI

Global LACP commands LACP can be enabled or disabled globally. When the LACP system priority is set globally, it applies to all LACP-enabled aggregators and ports. When LACP is enabled on an aggregator or a port, it will use the global system priority value.

CAUTION Changes to LACP made at the global level override and reset all port level settings.

Standby mode for LACP aggregation groups of larger than eight ports is not supported in the current release. LACP can be described in terms of link aggregation operations within a single system. You can configure a single piece of equipment such that it contains more than one system (from the point of view of the link aggregation operation). The basic command syntax is: config lacp

This command includes the following options: config lacp followed by: info

Shows current level parameter settings and next level directories.

enable

Enables LACP globally.

disable

Disables LACP globally.

aggr-wait-time

Sets the aggregator wait time in milliseconds.

system-priority

Sets LACP system priority globally.

•

is the system priority value within the range of 0 to 65 535.

Nortel Metro Ethernet Routing Switch 8600 Configuration — VLANs, Spanning Tree, and Link Aggregation NN46220-511 04.01 26 June 2009 Copyright © 2007-2009 Nortel Networks. All Rights Reserved.

Configuring link aggregation

329

config lacp followed by: smlt-sys-id

Sets the LACP system ID globally for split multilink trunks. This is an optional parameter, and is only used for SMLT situations. You must configure the same LACP SMLT system ID on both aggregation switches to avoid loss of data. Nortel recommends that the smlt-sys-id be configured such that it matches the base MAC address of one of the chassis.

• fast-periodic-time

Sets the fast periodic time globally.

• slow-periodic-time

is the fast periodic time value.

Sets the slow periodic time globally.

• timeout-scale

is the MAC address in the format {0x00:0x00:0x00:0x00:0x00:0x00}.

is the slow periodic time value.

Sets a timeout scale globally.

•

is the timeout scale value from 2 to 10.

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

Aggregator configuration commands When LACP is enabled globally on a multilink trunk, that multilink trunk is associated with an aggregator and used for link aggregation. When LACP is disabled on a multilink trunk, this multilink trunk functions as a legacy multilink trunk. Using the command clear-link-aggrgate is equivalent to disabling and reenabling LACP on the multilink trunk. You can attach ports to an aggregator only if their system priorities are the same; otherwise, they are considered to be operating in two different switches. You can attach ports to an aggregator only if their keys are the same. The basic command syntax is: config mlt lacp

Nortel Metro Ethernet Routing Switch 8600 Configuration — VLANs, Spanning Tree, and Link Aggregation NN46220-511 04.01 26 June 2009 Copyright © 2007-2009 Nortel Networks. All Rights Reserved.

330

Configuring link aggregation using the CLI

where is the multilink trunk ID. This command includes the following options: config mlt lacp followed by: info

Shows current level parameter settings and next level directories.

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 specific multilink trunk.

key

Sets LACP aggregator key for a specific multilink trunk.

• system-priority

is the LACP actor admin key.

Sets LACP system priority for a specific multilink trunk.

•

is the system priority within the range 0 to 65 535.

config mlt lacp followed by: info

Shows current level parameter settings and next level directories.

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 specific multilink trunk.

key

Sets LACP aggregator key for a specific multilink trunk.

• system-priority

is the LACP actor admin key.

Sets LACP system priority for a specific multilink trunk.

•

is the system priority within the range 0 to 65 535.

Nortel Metro Ethernet Routing Switch 8600 Configuration — VLANs, Spanning Tree, and Link Aggregation NN46220-511 04.01 26 June 2009 Copyright © 2007-2009 Nortel Networks. All Rights Reserved.

Configuring link aggregation

331

Port configuration commands ATTENTION Changes made at the global level override and reset all port level settings.

You can enable or disable LACP on selected ports. A port can operate in active or passive mode. You can configure LACP to use long timeout or short timeout. A port can be configured to be an individual link or an aggregateable link. All the timers are configurable, however, when you change a timer, ensure that you restart LACP either globally, or on the port, for the changes to be consistent across the link. The basic command syntax is: config lacp

where is Ethernet (eth) or Packet over SONET (pos); and is the slot and port number. This command includes the following options: config lacp followed by: info

Shows current level parameter settings and next level directories.

enable

Enables LACP for a specific port type.

disable

Disables LACP for a specific port type.

aggr-wait-time

Sets the aggregation wait time (in milliseconds) for a specific port type.

fast-periodic-time

Sets the fast periodic time (in milliseconds) for a specific port type.

key

Sets LACP aggregation key for a specific port type. You can use a default key only for individual ports

aggregation

Sets individual port or aggregatable for a specific port type.

• • mode

true sets port as aggregatable. false sets port as individual.

Sets the mode as active or passive for a specific port type.

Nortel Metro Ethernet Routing Switch 8600 Configuration — VLANs, Spanning Tree, and Link Aggregation NN46220-511 04.01 26 June 2009 Copyright © 2007-2009 Nortel Networks. All Rights Reserved.

332

Configuring link aggregation using the CLI

config lacp followed by: partner-key

Sets the port partner administration key value.

• partner-port

is the LACP partner administrative key; an integer value in the range of 0 and 65 535.

Sets the port partner administration port value.

• partner-port-priority

Sets the port partner administration port priority value.

• partner-state

is the LACP partner’s administrative port; an integer value in the range of 0 and 65 535.

is the LACP partner administrative port priority; an integer value in the range of 0 and 65 535.

Sets the port partner administration state.

•

is the LACP partner administrative state bitmap (Exp, Def, Dis, Col, Syn, Agg, Time, Act).

Example:

• • • partner-system-id

val = 00000101 (0x05) {0x0..0xff}

is the LACP partner administrative system ID MAC address in the format: 0x00:0x00:0x00:0x00:0x00:0x00.

Sets the port partner administration system priority value.

• port-priority

Aggregating = true

Sets the port partner administration system ID.

• partner-system-priority

Activity = true

is the LACP partner administrative system priority; an integer value in the range of 0 and 65 535.

Sets the LACP port priority to specific port type. The default value is 32 768.

•

is the port priority value; an integer value in the range of 0 and 65 535.

Nortel Metro Ethernet Routing Switch 8600 Configuration — VLANs, Spanning Tree, and Link Aggregation NN46220-511 04.01 26 June 2009 Copyright © 2007-2009 Nortel Networks. All Rights Reserved.

Configuring link aggregation

333

config lacp followed by: slow-periodic-time

Sets the slow periodic time (in milliseconds) for a specific port type.

system-priority

Sets system priority for a specific port-type.

•

is the system priority value within the range of 0 to 65 535.

timeout

Sets the timeout value to either long or short for a specific port type.

timeout-scale

Sets a timeout scale for a specific port type. The default value is 3, and the range is 2 to 10.

LACP show commands This section describes show commands you can use to display LACP information.

Displaying global LACP configuration information To display global LACP configuration information, enter the following command: show lacp info

Figure 144 "Show lacp info" (page 333) shows the output for the show lacp info command. Figure 144 Show lacp info

Nortel Metro Ethernet Routing Switch 8600 Configuration — VLANs, Spanning Tree, and Link Aggregation NN46220-511 04.01 26 June 2009 Copyright © 2007-2009 Nortel Networks. All Rights Reserved.

334

Configuring link aggregation using the CLI

Displaying LACP configuration information To display LACP configuration information, enter the following command: show ports info lacp

The show ports info lacp command also includes the following options: show ports info lacp followed by: actor-admin [vlan ] [port ]

Shows port LACP actor administrative information.

• • actor-oper [vlan ] [port ]

vlan is the VLAN ID. port is the port or port list.

vlan is the VLAN ID. port is the port or port list.

Shows port LACP partner operational information.

• • extension [vlan ] [port ]

port is the port or port list.

Shows port LACP partner administrative information.

• • partner-oper [vlan ] [port ]

vlan is the VLAN ID.

Shows all port LACP information.

• • partner-admin [vlan ] [port ]

port is the port or port list.

Shows port LACP actor operational information.

• • all [vlan ] [port ]

vlan is the VLAN ID.

vlan is the VLAN ID. port is the port or port list.

Shows port LACP timer information.

• •

vlan is the VLAN ID. port is the port or port list.

Figure 145 "Show ports info lacp all" (page 335) shows some of the output for this command. When the all parameter is used, LACP information is given for each field described in the show ports info lacp table.

Nortel Metro Ethernet Routing Switch 8600 Configuration — VLANs, Spanning Tree, and Link Aggregation NN46220-511 04.01 26 June 2009 Copyright © 2007-2009 Nortel Networks. All Rights Reserved.

Configuring link aggregation Figure 145 Show ports info lacp all

Displaying LACP statistics information per port To display LACP statistics information per port, enter the following command: show ports stats lacp [port ]

where port is the port list. Figure 146 "Show ports stats lacp" (page 336) shows sample output for the show ports stats lacp command.

Nortel Metro Ethernet Routing Switch 8600 Configuration — VLANs, Spanning Tree, and Link Aggregation NN46220-511 04.01 26 June 2009 Copyright © 2007-2009 Nortel Networks. All Rights Reserved.

335

336

Configuring link aggregation using the CLI

Figure 146 Show ports stats lacp

The following table shows the field descriptions for this command. Table 61 Show ports stats lacp field descriptions Field

Description

PORT NUM

Specifies the port number.

TX LACPDU

The number of LACPDUs transmitted on this aggregation port.

RX LACPDU

The number of valid link aggregation control protocol data units (LACPDU) received on this aggregation port.

TX MARKER PDU

The number of marker PDUs transmitted on this aggregation port.

RX MARKER PDU

The number of valid marker PDUs received on this aggregation port.

TX MARKERRESPPDU

The number of marker response PDUs transmitted on this aggregation port.

RX MARKERRESPPDU

The number of valid marker response PDUs received on this aggregation port.

RX UNKNOWN

The number of frames received that either:

RX ILLEGAL

•

carry Slow Protocols Ethernet type values, but contain an unknown PDU.

•

are addressed to the Slow Protocols group MAC Address, but do not carry the Slow Protocols Ethernet Type.

The number of frames received that carry the Slow Protocols Ethernet Type value (43B.4), but contain a badly formed PDU or an illegal value of Protocol Subtype (43B.4).

Nortel Metro Ethernet Routing Switch 8600 Configuration — VLANs, Spanning Tree, and Link Aggregation NN46220-511 04.01 26 June 2009 Copyright © 2007-2009 Nortel Networks. All Rights Reserved.

Configuring link aggregation

337

Displaying LACP configuration information per aggregator To display LACP configuration information per aggregator, enter the following command: show mlt lacp info

where is the interface index from 64 to 4351. Figure 147 "Show mlt lacp" (page 337) shows the output for the show mlt lacp command. Figure 147 Show 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 show mlt lacp info command.

Nortel Metro Ethernet Routing Switch 8600 Configuration — VLANs, Spanning Tree, and Link Aggregation NN46220-511 04.01 26 June 2009 Copyright © 2007-2009 Nortel Networks. All Rights Reserved.

338

Configuring link aggregation using the CLI

Figure 148 Show mlt lacp info

Creating a split multilink trunk from an existing multilink trunk Routed SMLT, or RSMLT, is a Layer 3 protocol whereas SMLT is a Layer 2 protocol. SMLT is described in this document, and RSMLT is described in the document Configuring IP Routing Operations.

Nortel Metro Ethernet Routing Switch 8600 Configuration — VLANs, Spanning Tree, and Link Aggregation NN46220-511 04.01 26 June 2009 Copyright © 2007-2009 Nortel Networks. All Rights Reserved.

Configuring link aggregation

339

To create a split multilink trunk from an existing multilink trunk, enter the following command: config mlt smlt

where is the MLT ID. Before you can create a split multilink trunk, you must first create a multilink trunk (see “Link aggregation commands” (page 326)). This command includes the following options: config mlt smlt followed by: info

Shows ports and VLANs added to the multilink trunk.

create smlt-id

Creates a split multilink trunk from an existing multilink trunk.

•

is an integer value with a range of 1 to 32 (1 to 256 for R modules in R mode). The value must match the peer switch SMLT-ID.

If the SMLT ID already exists on a single port split multilink trunk, you cannot assign it to an MLT-based split multilink trunk. Deletes an existing split multilink trunk.

delete

Creating an interswitch trunk To create an interswitch trunk from an existing multilink trunk, enter the following command: config mlt ist

where is the MLT ID. This command includes the following options:

Nortel Metro Ethernet Routing Switch 8600 Configuration — VLANs, Spanning Tree, and Link Aggregation NN46220-511 04.01 26 June 2009 Copyright © 2007-2009 Nortel Networks. All Rights Reserved.

340

Configuring link aggregation using the CLI

config mlt ist followed by: info

Shows current level parameter settings and next level directories.

create ip vlan-id

Creates an interswitch trunk from an existing multilink trunk (see “Creating an interswitch trunk from an existing multilink trunk” (page 340)).

• •

ip is a peer IP address vlan-id is an integer value.

The peer IP address is the IP address of the IST VLAN on the other aggregation switch. delete

Deletes an existing IST. You must disable an IST before you can delete it.

disable

Disables an existing IST.

enable

Enables an existing IST.

Creating an interswitch trunk from an existing multilink trunk To create an interswitch trunk from an existing multilink trunk, enter the following command: config mlt ist create ip vlan-id

where is the MLT ID; ip is the IP address of the peer switch; and vlan-id 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 redundant aggregation switch must also be created on the second aggregation switch. The interswitch trunk treats the two switches as a single switch. To allow the two switches to communicate, you must assign an IP address to both VLANs. For example:

Nortel Metro Ethernet Routing Switch 8600 Configuration — VLANs, Spanning Tree, and Link Aggregation NN46220-511 04.01 26 June 2009 Copyright © 2007-2009 Nortel Networks. All Rights Reserved.

Configuring link aggregation

switch A

switch B

VLAN 20

VLAN 20

10.1.1.1. /24



341

10.1.1.2 /24 *

* Same subnet, same VLAN.

Figure 149 "Config mlt ist create ip vlan-id command output" (page 341) shows sample output for the config mlt ist create ip vlan-id command, followed by the info command. Figure 149 Config mlt ist create ip vlan-id command output

Enabling and disabling an interswitch trunk To enable and disable the interswitch trunk, enter the following command: config mlt ist

where is the MLT ID. Figure 150 "Config mlt ist enable/disable command output" (page 341) shows sample output for the config mlt ist enable and config mlt ist disable commands. It includes the system warning that appears when you disable the IST. Figure 150 Config mlt ist enable/disable command output

Nortel Metro Ethernet Routing Switch 8600 Configuration — VLANs, Spanning Tree, and Link Aggregation NN46220-511 04.01 26 June 2009 Copyright © 2007-2009 Nortel Networks. All Rights Reserved.

342

Configuring link aggregation using the CLI

Configuring CP-Limit for an IST The CP-Limit feature is disabled by default on all IST ports. It can be enabled 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 more information, see "About CP-Limit and SMLT IST" on page 64. To configure CP-Limit for the interswitch trunk, enter the following command: config ethernet cp-limit

where specifies the slot or port. This command includes the following options: config ethernet cp-limit followed by: Enables or disables control packet rate limit (CP-Limit). The default setting is enabled.



If you want to reenable CP-Limit on a port, you must first disable the port and then reenable it (config ethernet state ). multicast-limit

Sets the multicast control frame packet per second rate (1000 to 100 000).

broadcast-limit

Sets the broadcast frame packet per second rate (1000 to 100 000).

For information about viewing current CP-Limit status for an IST multilink trunk, see Figure 143 "Config mlt info command output" (page 327).

Deleting an interswitch trunk To delete the interswitch trunk, enter the following command: config mlt ist delete

where

Nortel Metro Ethernet Routing Switch 8600 Configuration — VLANs, Spanning Tree, and Link Aggregation NN46220-511 04.01 26 June 2009 Copyright © 2007-2009 Nortel Networks. All Rights Reserved.

Configuring link aggregation

343

is the MLT ID. You must disable the interswitch trunk before deleting it (see “Enabling and disabling an interswitch trunk” (page 341)).

Creating a single port split multilink trunk To create a single port split multilink trunk, enter the following command: config ethernet smlt

where is the port number, and is the MLT ID. This command includes the following options: config ethernet smlt 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 port split multilink trunks. For more information about single port split multilink trunking, see “Single Port SMLT” (page 79).

Configuration example: single port split multilink trunk The configuration example shown in Figure 151 "Configuration example: Single Port SMLT" (page 344) uses the commands described previously to create a single port split multilink trunk on port 4/5. The switch automatically disables spanning tree protocol on the port after it is configured for SMLT. After configuring the parameters, use the info command to show a summary of the results.

Nortel Metro Ethernet Routing Switch 8600 Configuration — VLANs, Spanning Tree, and Link Aggregation NN46220-511 04.01 26 June 2009 Copyright © 2007-2009 Nortel Networks. All Rights Reserved.

344

Configuring link aggregation using the CLI Figure 151 Configuration example: Single Port SMLT

Configuring SMLT-on-Single-CPU To support SMLT on an aggregation switch with a single CPU, enter the following command: config sys set smlt-on-single-cp [timer ]

where enable enables the SMLT-on-Single-CPU feature; disable disables the SMLT-on-Single-CPU feature; timer sets the SMLT-on-Single-CPU feature timeout value. The timeout value determines when the Input/Output (I/O) modules port link status goes down after the single CPU becomes non-operational. The parameter is a numerical value in the range 1 to 3. If not set, the default value (3) is used. A timer value of 1 relates to approximately 3 seconds of detection time and a timer value of 3 relates to approximately 9 seconds of detection time.

Using the MLT and SMLT show commands To display information and statistics about MLT operation in the switch, use the show mlt commands.

Nortel Metro Ethernet Routing Switch 8600 Configuration — VLANs, Spanning Tree, and Link Aggregation NN46220-511 04.01 26 June 2009 Copyright © 2007-2009 Nortel Networks. All Rights Reserved.

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 information The show mlt show-all command shows all multilink trunk information. The command uses the syntax: show mlt show-all [file ]

where is the filename to which the output will be directed. 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 sample output for this command.

Nortel Metro Ethernet Routing Switch 8600 Configuration — VLANs, Spanning Tree, and Link Aggregation NN46220-511 04.01 26 June 2009 Copyright © 2007-2009 Nortel Networks. All Rights Reserved.

346

Configuring link aggregation using the CLI

Figure 152 Show mlt show-all sample output

Nortel Metro Ethernet Routing Switch 8600 Configuration — VLANs, Spanning Tree, and Link Aggregation NN46220-511 04.01 26 June 2009 Copyright © 2007-2009 Nortel Networks. All Rights Reserved.

Using the MLT and SMLT show commands Figure 153 Show mlt show-all sample output (continued)

Nortel Metro Ethernet Routing Switch 8600 Configuration — VLANs, Spanning Tree, and Link Aggregation NN46220-511 04.01 26 June 2009 Copyright © 2007-2009 Nortel Networks. All Rights Reserved.

347

348

Configuring link aggregation using the CLI

Figure 154 Show mlt show-all sample output (continued)

Displaying information about collision errors To display information about collision errors in the specified multilink trunk, or for all multilink trunks, enter the following command: show mlt error collision [ ]

where is the MLT ID. Figure 155 "Show mlt error collision command output" (page 349) shows sample output for the show mlt error collision command.

Nortel Metro Ethernet Routing Switch 8600 Configuration — VLANs, Spanning Tree, and Link Aggregation NN46220-511 04.01 26 June 2009 Copyright © 2007-2009 Nortel Networks. All Rights Reserved.

Using the MLT and SMLT show commands

349

Figure 155 Show mlt error collision command output

Displaying information about Ethernet errors To display information about the types of Ethernet errors sent and received by the specified multilink trunk or all multilink trunks, enter the following command: show mlt error main [ ]

where is the MLT ID. Figure 156 "Show mlt error main command output" (page 349) shows sample output for the show mlt error main command. The IMAC columns refer to internal MAC address errors. Figure 156 Show mlt error main command output

Nortel Metro Ethernet Routing Switch 8600 Configuration — VLANs, Spanning Tree, and Link Aggregation NN46220-511 04.01 26 June 2009 Copyright © 2007-2009 Nortel Networks. All Rights Reserved.

350

Configuring link aggregation using the CLI

Displaying multilink trunk status To display the status of MultiLink Trunking for the switch or for the specified multilink trunk ID, enter the following command: show mlt info [ ]

where is the MLT ID. Figure 157 "Show mlt info command output" (page 350) shows sample output for the show mlt info command: Figure 157 Show mlt info command output

Displaying interswitch trunk status To display the status of interswitch trunking for the switch or for the specified multilink trunk ID, enter the following command: show mlt ist info

Figure 158 "Show mlt ist info command output" (page 351) shows sample output for the show mlt ist info command.

Nortel Metro Ethernet Routing Switch 8600 Configuration — VLANs, Spanning Tree, and Link Aggregation NN46220-511 04.01 26 June 2009 Copyright © 2007-2009 Nortel Networks. All Rights Reserved.

Using the MLT and SMLT show commands

351

Figure 158 Show mlt ist info command output

Displaying split multilink trunk status To display split multilink trunk status for the switch or for a specific SMLT ID, enter the following command: show smlt info [ ]

where is the MLT ID. The switch shows both MLT-based split multilink trunk information and single port split multilink trunk information. Figure 159 "Show smlt info command output" (page 352) shows output from a sample show smlt info command.

Nortel Metro Ethernet Routing Switch 8600 Configuration — VLANs, Spanning Tree, and Link Aggregation NN46220-511 04.01 26 June 2009 Copyright © 2007-2009 Nortel Networks. All Rights Reserved.

352

Configuring link aggregation using the CLI

Figure 159 Show smlt info command output

Displaying all ports configured for single port split multilink trunk To view all ports currently configured for single port split multilink trunk, enter the following command: show ports info smlt [vlan ] [port ]

where vlan is the VLAN ID, and port 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 the output from a sample show ports info smlt command.

Nortel Metro Ethernet Routing Switch 8600 Configuration — VLANs, Spanning Tree, and Link Aggregation NN46220-511 04.01 26 June 2009 Copyright © 2007-2009 Nortel Networks. All Rights Reserved.

Using the MLT and SMLT show commands

353

Figure 160 Show ports info smlt command output

Displaying a port configured for Single Port SMLT To view a port configured for Single Port SMLT, enter the following command: show ports info config [vlan ] [port ]

where vlan is the VLAN ID, and port is a port or list of ports. Figure 161 "Show ports info config command output" (page 353) shows output from a sample show ports info config command. Figure 161 Show ports info config command output

Displaying MLT statistics To display MultiLink Trunking statistics for the switch or for the specified multilink trunk ID, enter the following command:

Nortel Metro Ethernet Routing Switch 8600 Configuration — VLANs, Spanning Tree, and Link Aggregation NN46220-511 04.01 26 June 2009 Copyright © 2007-2009 Nortel Networks. All Rights Reserved.

354

Configuring link aggregation using the CLI

show mlt stats [ ]

where is the MLT ID. Figure 162 "Show mlt stats command output" (page 354) shows sample output for the show mlt stats command. Figure 162 Show mlt stats command output

Troubleshooting SMLT problems This section provides procedures for troubleshooting IST problems and single-user problems. The following topics are included:

• •

“Troubleshooting IST problems” (page 354) “Troubleshooting problems with a single user” (page 357)

Troubleshooting IST problems To troubleshoot SMLT IST problems:

Nortel Metro Ethernet Routing Switch 8600 Configuration — VLANs, Spanning Tree, and Link Aggregation NN46220-511 04.01 26 June 2009 Copyright © 2007-2009 Nortel Networks. All Rights Reserved.

Troubleshooting SMLT problems

355

Step

Action

1

Enter the show mlt ist stat command to display the IST message count. (Figure 163 "Show mlt ist stat command output" (page 355)). Figure 163 Show mlt ist stat command output

2

Enter the show mlt info command to display all the multilink trunks in the switch, their admin-type, running type, ports, and VLANs (Figure 157 "Show mlt info command output" (page 350)).

3

Check to ensure that IST is operational by using the show mlt ist info command (Figure 164 "Show mlt ist info command output" (page 356)).

Nortel Metro Ethernet Routing Switch 8600 Configuration — VLANs, Spanning Tree, and Link Aggregation NN46220-511 04.01 26 June 2009 Copyright © 2007-2009 Nortel Networks. All Rights Reserved.

356

Configuring link aggregation using the CLI Figure 164 Show 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 interswitch trunk b The IST configuration contains the correct local and peer IP addresses

5

If IST is operational, check that the SMLT port is operating by using the show mlt smlt info command (Figure 165 "Show mlt smlt info command output" (page 356)). a If the SMLT status is SMLT, the status is correct. Figure 165 Show 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 can be as follows:

Nortel Metro Ethernet Routing Switch 8600 Configuration — VLANs, Spanning Tree, and Link Aggregation NN46220-511 04.01 26 June 2009 Copyright © 2007-2009 Nortel Networks. All Rights Reserved.

Troubleshooting SMLT problems

• •

the remote split multilink trunk link is not operational

•

the IST is not operational

357

the ID is not configured on the other switch. To determine this, check to see whether the SMLT IDs match

--End--

Troubleshooting problems with a single user To determine if only a single user is affected, check the VLAN FDB tables on both IST switches using the show vlan info fdb-entry command. Both FDB tables should be synchronized. The command shows whether:

•

The MAC address is learned on the local SMLT port (that is, SMLT REMOTE flag is false). See Figure 166 "Show vlan info fdb-entry command 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 switch must specify the learned split multilink trunk port as INTERFACE in both IST switches. Figure 166 Show vlan info fdb-entry command output

Nortel Metro Ethernet Routing Switch 8600 Configuration — VLANs, Spanning Tree, and Link Aggregation NN46220-511 04.01 26 June 2009 Copyright © 2007-2009 Nortel Networks. All Rights Reserved.

358

Configuring link aggregation using the CLI

Global MAC filtering You can globally configure MAC filtering to disallow bridging or routing of any packets transmitted or received from specified MAC addresses on any VLAN. To globally filter MAC addresses, use the following command: config fdb fdb-filter This command includes the following options: config fdb fdb-filter followed by: info

Show current level parameter settings and next level directories.

add

Adds a global FDB filter.

•

is the MAC address to filter.

Enter the MAC address in the following format {0x00:0x00:0x00:0x00:0x00:0x00}. remove

Removes a global FDB filter.

•

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 an example of the config fdb fdb-filter info command output. Figure 167 Config fdb fdb-filter info command output

Figure 168 "Show fdb fdb-filter command output" (page 359) shows an example of the show fdb fdb-filter command output:

Nortel Metro Ethernet Routing Switch 8600 Configuration — VLANs, Spanning Tree, and Link Aggregation NN46220-511 04.01 26 June 2009 Copyright © 2007-2009 Nortel Networks. All Rights Reserved.

Global MAC filtering Figure 168 Show fdb fdb-filter command output

Nortel Metro Ethernet Routing Switch 8600 Configuration — VLANs, Spanning Tree, and Link Aggregation NN46220-511 04.01 26 June 2009 Copyright © 2007-2009 Nortel Networks. All Rights Reserved.

359

360

Configuring link aggregation using the CLI

Nortel Metro Ethernet Routing Switch 8600 Configuration — VLANs, Spanning Tree, and Link Aggregation NN46220-511 04.01 26 June 2009 Copyright © 2007-2009 Nortel Networks. All Rights Reserved.

361

.

Configuring Simple Loop Prevention Protocol Logical loops can occur in SMLT networks because of misconfigurations, switch problems, or because MLT is not operating correctly. You can detect loops with Simple Loop Prevention Protocol (SLPP). For more information 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 following command: config slpp

This command has the following options: config slpp followed by: add

Adds a VLAN to a SLPP transmission list.

• etherType

Specifies the SLPP PDU Ether type.

• remove

is the ID of the VLAN.

is the SLPP protocol ID in hexadecimal format.

Removes a VLAN from a SLPP transmission list.

•

is the ID of the VLAN.

Nortel Metro Ethernet Routing Switch 8600 Configuration — VLANs, Spanning Tree, and Link Aggregation NN46220-511 04.01 26 June 2009 Copyright © 2007-2009 Nortel Networks. All Rights Reserved.

362

Configuring Simple Loop Prevention Protocol

config slpp followed by: info

Shows current level parameter settings and next level directories.

operation

Enables or disables the SLPP operation. The SLPP packets transmit and receive process is active only when the SLPP operation is enabled. When the SLPP operation is disabled, no SLPP packet is sent out, and any received SLPP packet is discarded.

tx-interval

Sets the SLPP packet transmit interval.

•

is the SLPP packet transmit interval.

The range is 500 to 5000 ms, and the default is 500 ms.

Figure 169 "Config slpp slpp info command" (page 362) shows how to display the SLPP transmission list and operation state. Figure 169 Config slpp slpp info command

Configuring SLPP on a port To configure SLPP on a port, use the following command: config ethernet slpp

where portlist is the slot/port. This command includes the following options:

Nortel Metro Ethernet Routing Switch 8600 Configuration — VLANs, Spanning Tree, and Link Aggregation NN46220-511 04.01 26 June 2009 Copyright © 2007-2009 Nortel Networks. All Rights Reserved.

Showing SLPP information

363

config ethernet slpp followed by: packet-rx

Enables or disables SLPP packet reception on the listed ports

packet-rx-threshold

Specifies the SLPP reception threshold on the ports. The threshold is an integer.

info

Shows current level parameter settings and next level directories.

clear-packet-rx-count

Manually clears the total number of SLPP PDUs received on a particular port.

The packet reception threshold specifies how many SLPP packets are received by the port before it is administratively disabled. Figure 170 "Config ethernet command" (page 363) shows how to display the SLPP state on a port: Figure 170 Config ethernet command

Showing SLPP information To show SLPP information, use the following command: show slpp info

The following shows SLPP information. ===================================================== SLPP Info ===================================================== etherType (hex) : 0x8104 operation: disabled

Nortel Metro Ethernet Routing Switch 8600 Configuration — VLANs, Spanning Tree, and Link Aggregation NN46220-511 04.01 26 June 2009 Copyright © 2007-2009 Nortel Networks. All Rights Reserved.

364

Configuring Simple Loop Prevention Protocol tx-interval : 5000 vlan : 1, 3, 4 uni-ports :2/1,2/3

For an SLPP configuration example, see “Single Port SMLT with SLPP configuration example” (page 377).

Showing SLPP port information To show SLPP port information, use the following command: show ports info slpp [port ]

where port is the port list. ATTENTION The Incoming VLAN Id and the SLPP PDU originator is displayed only when a port shuts down on reception of SLPP PDUs and pkt-rx-threshold of the port is reached.

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 PDU NUM THRESHOLD COUNT VLAN ID ORIGINATOR ------------------------------------------------------------------------2/6 enable 200 181 10 local 2/16 enable 200 181 10 local

The following table shows the field descriptions for this command. Table 62 Show 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 as a range of 1 to 20. After the port reaches the packet threshold, it shuts down.

INCOMING VLAN ID

VLAN ID of the classified packet on a port disabled by SLPP.

Nortel Metro Ethernet Routing Switch 8600 Configuration — VLANs, Spanning Tree, and Link Aggregation NN46220-511 04.01 26 June 2009 Copyright © 2007-2009 Nortel Networks. All Rights Reserved.

Showing SLPP port information

365

Table 62 Show ports info slpp field descriptions (cont’d.) Field

Description

PKT-RX Count

Specifies the total number of SLPP PDUs received on a port irrespective of the VLAN to which the port belongs.

SLPP PDU ORIGINATOR

Specifies the originator of the SLPP PDU.

Nortel Metro Ethernet Routing Switch 8600 Configuration — VLANs, Spanning Tree, and Link Aggregation NN46220-511 04.01 26 June 2009 Copyright © 2007-2009 Nortel Networks. All Rights Reserved.

366

Configuring Simple Loop Prevention Protocol

Nortel Metro Ethernet Routing Switch 8600 Configuration — VLANs, Spanning Tree, and Link Aggregation NN46220-511 04.01 26 June 2009 Copyright © 2007-2009 Nortel Networks. All Rights Reserved.

367

.

Device Manager configuration examples This section provides examples of common link aggregation configuration tasks 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).

This section includes the following topics:

• •

“SMLT and LACP configuration example” (page 367) “Single Port SMLT and LACP configuration example” (page 371)

SMLT and LACP configuration example The Metro Ethernet Routing Switch 8600 fully supports the IEEE 802.3ad Link Aggregation Control Protocol. LACP is supported on MLT and DMLT links and extends to a pair of SMLT switches. With this extension, the Metro Ethernet Routing Switch 8600 provides a standardized external link aggregation interface to third party vendor IEEE 802.3ad implementations. In this example, Metro Ethernet Routing Switch 8600C is used as the SMLT client; any switch that supports LACP can be used as an LACP-enabled SMLT client. Do not use 802.3ad on the interswitch trunk. The LACP keys on the SMLT core switches must match (Metro Ethernet Routing Switch 8600 A, Metro Ethernet Routing Switch 8600 B). The following figure shows the network topology.

Nortel Metro Ethernet Routing Switch 8600 Configuration — VLANs, Spanning Tree, and Link Aggregation NN46220-511 04.01 26 June 2009 Copyright © 2007-2009 Nortel Networks. All Rights Reserved.

368

Device Manager configuration examples Figure 171 SMLT and LACP configuration example

Assume the following:

• •

The interswitch trunk has already been created.

•

Metro Ethernet Routing Switch 8600 C is already configured and uses ports 1/10 to 1/13. The LACP key on this switch does not need to match that of the SMLT core switches.

•

The LACP key on both Metro Ethernet Routing Switch 8600 A and Metro Ethernet Routing Switch 8600 B must match.

VLAN 100 has already been created on all three switches with the port membership as described in Figure 171 "SMLT and LACP configuration example" (page 368).

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.

Nortel Metro Ethernet Routing Switch 8600 Configuration — VLANs, Spanning Tree, and Link Aggregation NN46220-511 04.01 26 June 2009 Copyright © 2007-2009 Nortel Networks. All Rights Reserved.

SMLT and LACP configuration example

3

Click Apply.

4

Click the Multilink/LACP Trunks tab.

369

The Multilink/LACP Trunks box appears. 5

Click Insert. The MLT_LACP, Insert Multilink/LACP Trunks box appears. Figure 172 Insert Multilink/LACP Trunks box

6

Configure the parameters as shown in Figure 172 "Insert Multilink/LACP Trunks box" (page 369).

7

Click Insert. The following figure shows the port information. (To view this information, go to VLAN > MLT/LACP > Multilink/LACP Trunks.)

Nortel Metro Ethernet Routing Switch 8600 Configuration — VLANs, Spanning Tree, and Link Aggregation NN46220-511 04.01 26 June 2009 Copyright © 2007-2009 Nortel Networks. All Rights Reserved.

370

Device Manager configuration examples Figure 173 MLT 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 number that will be applied to ports 1/10 and 1/11. Figure 174 MLT_LACP, LACP tab

10

Ensure that the ports 1/10 and 1/11 belong to exactly the same VLANs, 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 Switch 8600C is correct and you have link connectivity, VLAN > MLT/LACP > MLT/LACP now displays port 1/10 and 1/11. --End--

Nortel Metro Ethernet Routing Switch 8600 Configuration — VLANs, Spanning Tree, and Link Aggregation NN46220-511 04.01 26 June 2009 Copyright © 2007-2009 Nortel Networks. All Rights Reserved.

Single Port SMLT and LACP configuration example

371

Single Port SMLT and LACP configuration example Single Port SMLT lets you configure a split multilink trunk using a single port. The Single Port SMLT behaves like an MLT-based SMLT and can coexist with SMLTs in the same system; however, an SMLT ID can belong to either an MLT-SMLT or a Single Port SMLT per chassis.With Single Port SMLT, you can scale the number of split multilink trunks on a switch to a maximum number of available ports. This example highlights the steps used to configure Single Port SMLT using LACP to create the LAG. Any LACP-enabled device can be used as the LACP client. The following figure shows the network topology. Figure 175 Network topology for Single Port SMLT example

Assume the following:

•

The interswitch trunk has already been created as shown in the preceding figure.

•

VLAN 10 has already been created on the two switches with the port membership described in the preceding figure.

•

The LACP keys on both Metro Ethernet Routing Switch 8600A and Metro Ethernet Routing Switch 8600B must match. The LACP key on the server (LACP client) does not have to match the Metro Ethernet Routing Switch 8600 key.

The following configuration must be performed on both SMLT core switches:

Nortel Metro Ethernet Routing Switch 8600 Configuration — VLANs, Spanning Tree, and Link Aggregation NN46220-511 04.01 26 June 2009 Copyright © 2007-2009 Nortel Networks. All Rights Reserved.

372

Device Manager configuration examples

Step

Action

1

In Device Manager, select the port to be configured and right-click.

2

Select Edit General > SMLT. The Port box appears. Figure 176 Port box

3

Click Insert. The Insert SMLT box appears. Figure 177 Insert SMLT

4

Insert a new SMLT group ID. The ID must match on all ports on both SMLT core switches.

5

Click Insert.

6

Set the LACP key, check aggregate, and click the LACP tab and enable LACP by selecting the AdminEnable check box.

Nortel Metro Ethernet Routing Switch 8600 Configuration — VLANs, Spanning Tree, and Link Aggregation NN46220-511 04.01 26 June 2009 Copyright © 2007-2009 Nortel Networks. All Rights Reserved.

Single Port SMLT and LACP configuration example Figure 178 LACP enable

7

Click Apply. --End--

Nortel Metro Ethernet Routing Switch 8600 Configuration — VLANs, Spanning Tree, and Link Aggregation NN46220-511 04.01 26 June 2009 Copyright © 2007-2009 Nortel Networks. All Rights Reserved.

373

374

Device Manager configuration examples

Nortel Metro Ethernet Routing Switch 8600 Configuration — VLANs, Spanning Tree, and Link Aggregation NN46220-511 04.01 26 June 2009 Copyright © 2007-2009 Nortel Networks. All Rights Reserved.

375

.

CLI configuration examples This section provides examples of common link aggregation configuration tasks, including the command line interface (CLI) commands you use to create 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) This section includes the following topics:

• • • • • • • • • • • •

“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)

Nortel Metro Ethernet Routing Switch 8600 Configuration — VLANs, Spanning Tree, and Link Aggregation NN46220-511 04.01 26 June 2009 Copyright © 2007-2009 Nortel Networks. All Rights Reserved.

376

CLI configuration examples

MultiLink Trunking configuration example This configuration example shows how to create a multilink trunk and a VLAN (VLAN 100) between two Metro Ethernet Routing Switch 8600 devices. The network is used to carry user traffic Figure 179 "MLT within a VLAN" (page 376). Figure 179 MLT within a VLAN

The following sections provide step-by-step procedures that show how to configure 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 create MERS-8606:5# config mlt 10 add ports 1/1,1/2,2/1,2/ 2 MERS-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:

Nortel Metro Ethernet Routing Switch 8600 Configuration — VLANs, Spanning Tree, and Link Aggregation NN46220-511 04.01 26 June 2009 Copyright © 2007-2009 Nortel Networks. All Rights Reserved.

Single Port SMLT with SLPP configuration example

377

MERS-8606:5# config mlt 10 create MERS-8606:5# config mlt 10 add ports 1/1,1/2,2/1,2/ 2 MERS-8606:5# config mlt 10 add vlan 100 3

To have an MLT-UNI, when creating the endpoint, add the MLT ID and leave port, ring ID, mod ID and esuport empty. --End--

Single Port SMLT with SLPP configuration example The single port Split MultiLink Trunking (SMLT) design is similar to the triangle SMLT design. The only difference is that only a single port from each InterSwitch Trunking (IST) switch goes to the access server. The following figure shows the network topology. Figure 180 Single Port SMLT

Configuring Metro Ethernet Routing Switch 8600A Step

Action

1

Configure VLANs: MERS8600-B:5# config vlan 1900 create byport 1 MERS8600-B:5# config vlan 10 create byport 1 Nortel Metro Ethernet Routing Switch 8600 Configuration — VLANs, Spanning Tree, and Link Aggregation NN46220-511 04.01 26 June 2009 Copyright © 2007-2009 Nortel Networks. All Rights Reserved.

378

CLI configuration examples

2

Enable SLPP and add VLAN 10: MERS8600-B:5# config slpp add 10 MERS8600-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 create MERS8600-B:5# config mlt 5 add ports 2/1,3/1 MERS8600-B:5# config vlan 1900 add-mlt 5

4

Configure the IP address and interswitch trunk. The IP address points to the partner interswitch trunk node: MERS8600-B:5# config vlan 1900 ip create 1.1.1.1/30 MERS8600-B:5# config mlt 5 ist create ip 1.1.1.2 vlan-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-rx enable --End--

Configuring MERS8600C Step

Action

1

Configure VLANs: MERS8600-C:5# config vlan 1900 create byport 1 MERS8600-C:5# config vlan 10 create byport 1

2

Enable SLPP: MERS8600-C:5# config slpp add 10 MERS8600-C:5# config slpp operation enable

3

Configure MLT. VLAN 10 must be spanned across the interswitch trunk (MLT-5): MERS-8606:5# config mlt 5 create MERS-8606:5# config mlt 5 add ports 2/1,3/1 MERS-8606:5# config mlt 5 add vlan 1900

4

Configure IP address and IST. The IP address points to the partner IST node: MERS-8606:5# config vlan 1900 ip create 1.1.1.2/30 MERS-8606:5# config mlt 5 ist create ip 1.1.1.1 vlan-id 1900

Nortel Metro Ethernet Routing Switch 8600 Configuration — VLANs, Spanning Tree, and Link Aggregation NN46220-511 04.01 26 June 2009 Copyright © 2007-2009 Nortel Networks. All Rights Reserved.

SMLT triangle with loop detection configuration example

5

379

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 threshold to 1: MERS8600-C:5# config ethernet 1/1 slpp packet-rx enable MERS8610-C:5# config ethernet 1/1 slpp packet-rx-threshold 1 To view the status of all SMLT ports, and show SLPP configuration information, use the following commands: MERS8610-B:5# MERS8610-B:5# MERS8610-B:5# MERS8600-B:5#

show port info smlt port 1/1 show slpp info show ports info slpp port 1/1 show log file tail

If port 1/1 is disabled on either Metro Ethernet Routing Switch 8600A or Metro Ethernet Routing Switch 8600B because either switch received its own SLPP-PDU, a message is logged and a trap will be used. --End--

SMLT triangle with loop detection configuration example This configuration example shows how to create an SMLT triangle using three Metro Ethernet Routing Switch 8600 devices and a VLAN (VLAN 10), which is used to carry user traffic Figure 181 "SMLT triangle configuration example" (page 380). The following configuration example is based on a three node network where MERS8600A is the SMLT client. Although only one port is used to connect to the SMLT client from each SMLT aggregation switch in this example, up to 8 total links can be used to carry traffic between the two.

Nortel Metro Ethernet Routing Switch 8600 Configuration — VLANs, Spanning Tree, and Link Aggregation NN46220-511 04.01 26 June 2009 Copyright © 2007-2009 Nortel Networks. All Rights Reserved.

380

CLI configuration examples Figure 181 SMLT triangle configuration example

The following sections provide step-by-step procedures that show how to configure switches Metro Ethernet Routing Switch 8600A, Metro Ethernet Routing Switch 8600B, and Metro Ethernet Routing Switch 8600C for this example. 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) and MERS8600C (5)

Configuring MERS8600B Step

Action

1

Configure VLANs: MERS-8606-B:5# config vlan 1900 create byport 1 MERS-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:

Nortel Metro Ethernet Routing Switch 8600 Configuration — VLANs, Spanning Tree, and Link Aggregation NN46220-511 04.01 26 June 2009 Copyright © 2007-2009 Nortel Networks. All Rights Reserved.

SMLT triangle with loop detection configuration example

MERS-8606-B:5# config MERS-8606-B:5# config MERS-8606-B:5# config disable MERS-8606-B:5# config 3

381

mlt 5 create mlt 5 add ports 2/1,3/1 ether 2/1,3/1 cp-limit vlan 1900 add-mlt 5

Configure the IST IP address and create the interswitch trunk using MLT 5. The IP address is the IP address of the remote partner IST node. MERS-8606-B:5# config vlan 1900 ip create 1.1.1.1/30 MERS-8606-B:5# config mlt 5 ist create ip 1.1.1.2 vlan-id 1900

4

Configure the SMLT link: MERS-8606-B:5# config MERS-8606-B:5# config MERS-8606-B:5# config MERS-8606-B:5# config

5

mlt 1 mlt 1 mlt 1 mlt 1

create perform-tagging enable add ports 1/1 smlt create smlt-id 1

Add VLAN 10 to the interswitch trunk and SMLT VLANs: MERS-8606-B:5# config vlan 10 add-mlt 1 MERS-8606-B:5# config vlan 10 add-mlt 5

6

Enable loop detection on port 1/1. By default, the action will be set to portdown. This can be verified by using the show config module port or config ethernet 1/1 info command. The loop detect timers should be staggered between the MERS8600B and MERS8600C: change the default mac-flap-time-limit from the default setting of 500 ms to 700 ms. MERS-8606-B:5# config ethernet 1/1 loop-detect enable MERS-8606-B:5# config mac-flap-time-limit 700 --End--

Configuring MERS8600C Step

Action

1

Configure VLANs: MERS-8606-C:5# config vlan 1900 create byport 1 MERS-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.

Nortel Metro Ethernet Routing Switch 8600 Configuration — VLANs, Spanning Tree, and Link Aggregation NN46220-511 04.01 26 June 2009 Copyright © 2007-2009 Nortel Networks. All Rights Reserved.

382

CLI configuration examples

MERS-8606-C:5# config MERS-8606-C:5# config MERS-8606-C:5# config disable MERS-8606-C:5# config 3

mlt 5 create mlt 5 add ports 2/1,3/1 ether 2/1,3/1 cp-limit vlan 1900 add-mlt 5

Configure the IST IP address and create the interswitch trunk using MLT 5. The IP address used is the IP address of the remote partner IST node. MERS-8606-C:5# config vlan 1900 ip create 1.1.1.2/30 MERS-8606-C:5# config mlt 5 create ip 1.1.1.1 vlan-id 1900

4

Configure the SMLT link: MERS-8606-C:5# config MERS-8606-C:5# config MERS-8606-C:5# config MERS-8606-C:5# config

5

mlt 1 mlt 1 mlt 1 mlt 1

create perform-tagging enable add ports 1/1 smlt create smlt-id 1

Add VLAN 10 to the IST and SMLT VLANs: MERS-8606-C:5# config vlan 10 add-mlt 1 MERS-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-detect enable --End--

Configuring MERS8600A Step

Action

1

Configure VLAN 10: MERS-8606-A:5# config vlan 10 create byport 1 MERS-8606-A:5# config vlan 10 ports add 2/1-2/5

2

Configure the MLT link: MERS-8606-A:5# config MERS-8606-A:5# config MERS-8606-A:5# config MERS-8606-A:5# config

3

mlt 1 create mlt 1 perform-tagging enable mlt 1 add ports 1/1,1/2 vlan 10 add-mlt 1

Enable Spanning Tree fast start on ports 2/1 to 2/5:

Nortel Metro Ethernet Routing Switch 8600 Configuration — VLANs, Spanning Tree, and Link Aggregation NN46220-511 04.01 26 June 2009 Copyright © 2007-2009 Nortel Networks. All Rights Reserved.

SMLT triangle with loop detection configuration example

383

MERS-8606-A:5# config ethernet 2/1-2/5 stg 1 faststart enable --End--

Verifying network operations Figure 182 "Show mlt info output" (page 383) to Figure 185 "Loop detection commands" (page 386) show commands you can use to verify that the network is operating correctly. Figure 182 Show mlt info output

The MLT CURRENT status for MLT-5 is ist. If this status is norm then the IST is not active; there may be a misconfiguration or the links are not active. The current MLT mode is smlt. If there is a misconfiguration or a link down in the network, the value of MLT CURRENT would be norm.

Nortel Metro Ethernet Routing Switch 8600 Configuration — VLANs, Spanning Tree, and Link Aggregation NN46220-511 04.01 26 June 2009 Copyright © 2007-2009 Nortel Networks. All Rights Reserved.

384

CLI configuration examples

Figure 183 Show mlt commands

Nortel Metro Ethernet Routing Switch 8600 Configuration — VLANs, Spanning Tree, and Link Aggregation NN46220-511 04.01 26 June 2009 Copyright © 2007-2009 Nortel Networks. All Rights Reserved.

SMLT triangle with loop detection configuration example

Figure 184 Show mlt commands, part 2

Loop Detection

Nortel Metro Ethernet Routing Switch 8600 Configuration — VLANs, Spanning Tree, and Link Aggregation NN46220-511 04.01 26 June 2009 Copyright © 2007-2009 Nortel Networks. All Rights Reserved.

385

386

CLI configuration examples

Suppose a loop is formed between MERS8600A, MERS8600B, and MERS8600C. The commands shown in Figure 185 "Loop detection commands" (page 386) show commands you can use to display the MAC address that is looping. Figure 185 Loop detection commands

Square SMLT configuration example The 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, each must have matching SMLT IDs. However, these IDs can differ between the two IST pairs. The initial configuration creates the IST links between A and B, and C and D. Note that the IST IP addresses differ; Nortel recommends that you use a different subnet for the IST IP addresses between the pairs.

Nortel Metro Ethernet Routing Switch 8600 Configuration — VLANs, Spanning Tree, and Link Aggregation NN46220-511 04.01 26 June 2009 Copyright © 2007-2009 Nortel Networks. All Rights Reserved.

Square SMLT configuration example

387

Figure 186 Square SMLT

Configuring MERS8600B 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 1 MERS-8606:5# config vlan 10 create byport 1

3

Configure MLT. VLAN 10 must be spanned across the interswitch trunk (MLT-5): MERS-8606:5# config mlt 5 create MERS-8606:5# config mlt 5 add ports 2/1,3/1

Nortel Metro Ethernet Routing Switch 8600 Configuration — VLANs, Spanning Tree, and Link Aggregation NN46220-511 04.01 26 June 2009 Copyright © 2007-2009 Nortel Networks. All Rights Reserved.

388

CLI configuration examples

MERS-8606:5# config mlt 5 add vlan 1900 MERS-8606:5# config mlt 5 add vlan 10 4

Configure the IP address and IST. The IP address points to the partner IST node: MERS-8606:5# config vlan 1900 ip create 1.1.1.1/30 MERS-8606:5# config mlt 5 ist create ip 1.1.1.2 vlan-id 1900

5

Configure SMLT. The SMLT ID must be identical for each IST pair: MERS-8606:5# MERS-8606:5# MERS-8606:5# MERS-8606:5#

config mlt config mlt config mlt config mlt

1 create 1 smlt create smlt-id 1 1 add vlan 10 1 add ports 1/1 --End--

Configuring MERS8600C 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 1 MERS-8606:5# config vlan 10 create byport 1

3

Configure MLT. VLAN 10 must be spanned across the interswitch trunk (MLT-5): MERS-8606:5# MERS-8606:5# MERS-8606:5# MERS-8606:5#

4

config mlt config mlt config mlt config mlt

5 create 5 add ports 2/1,3/1 5 add vlan 1900 5 add vlan 10

Configure IP address and IST. The IP address points to the partner IST node: MERS-8606:5# config vlan 1900 ip create 1.1.1.2/30 MERS-8606:5# config mlt 5 ist create ip 1.1.1.1 vlan-id 1900

5

Configure SMLT. The SMLT ID must be identical for each IST pair: MERS-8606:5# config mlt 1 create MERS-8606:5# config mlt 1 smlt create smlt-id 1

Nortel Metro Ethernet Routing Switch 8600 Configuration — VLANs, Spanning Tree, and Link Aggregation NN46220-511 04.01 26 June 2009 Copyright © 2007-2009 Nortel Networks. All Rights Reserved.

Square SMLT configuration example

389

MERS-8606:5# config mlt 1 add vlan 10 MERS-8606:5# config mlt 1 add ports 1/1 --End--

Configuring MERS8600A 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 1 MERS-8606:5# config vlan 10 create byport 1

3

Configure MLT. VLAN 10 must be spanned across the interswitch trunk (MLT-5): MERS-8606:5# MERS-8606:5# MERS-8606:5# MERS-8606:5#

4

config mlt config mlt config mlt config mlt

5 create 5 add ports 2/1,3/1 5 add vlan 1900 5 add vlan 10

Configure IP address and IST. The IP address points to the partner IST node: MERS-8606:5# config vlan 1900 ip create 2.2.2.1/30 MERS-8606:5# config mlt 5 ist create ip 2.2.2.2 vlan-id 1900

5

Configure SMLT. The SMLT ID must be identical for each IST pair: MERS-8606:5# MERS-8606:5# MERS-8606:5# MERS-8606:5#

config mlt config mlt config mlt config mlt

1 create 1 smlt create smlt-id 1 1 add vlan 10 1 add ports 1/1 --End--

Configuring MERS8600D Step

Action

1

Disable CP-Limit on IST ports: MERS-8606:5# config ether 2/1,3/1 cp-limit disable

2

Configure VLANs:

Nortel Metro Ethernet Routing Switch 8600 Configuration — VLANs, Spanning Tree, and Link Aggregation NN46220-511 04.01 26 June 2009 Copyright © 2007-2009 Nortel Networks. All Rights Reserved.

390

CLI configuration examples

MERS-8606:5# config vlan 1900 create byport 1 MERS-8606:5# config vlan 10 create byport 1 3

Configure MLT. VLAN 10 must be spanned across the interswitch trunk (MLT-5): MERS-8606:5# MERS-8606:5# MERS-8606:5# MERS-8606:5#

4

config mlt config mlt config mlt config mlt

5 create 5 add ports 2/1,3/1 5 add vlan 1900 5 add vlan 10

Configure IP address and IST. The IP address points to the partner IST node: MERS-8606:5# config vlan 1900 ip create 2.2.2.2/30 MERS-8606:5# config mlt 5 ist create ip 2.2.2.1 vlan-id 1900

5

Configure SMLT. The SMLT ID must be identical for each IST pair: MERS-8606:5# MERS-8606:5# MERS-8606:5# MERS-8606:5#

config mlt config mlt config mlt config mlt

1 create 1 smlt create smlt-id 1 1 add vlan 10 1 add ports 1/1

Use the show mlt info and the show smlt info commands to verify the status of the multilink trunks. --End--

Full mesh SMLT configuration example The full mesh SMLT design is similar to the square SMLT, except more links are added to fully mesh the four nodes (see Figure 187 "Full mesh SMLT" (page 391)). As with the square configuration, it is imperative that all links within the SMLT group contain the same SMLT ID, however, this ID need not be the same between each IST pair.

Nortel Metro Ethernet Routing Switch 8600 Configuration — VLANs, Spanning Tree, and Link Aggregation NN46220-511 04.01 26 June 2009 Copyright © 2007-2009 Nortel Networks. All Rights Reserved.

Full mesh SMLT configuration example

391

Figure 187 Full mesh SMLT

Configuring MERS8600B 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 1 MERS-8606:5# config vlan 10 create byport 1

3

Configure MLT. VLAN 10 must be spanned across the interswitch trunk (MLT-5): MERS-8606:5# MERS-8606:5# MERS-8606:5# MERS-8606:5#

4

config mlt config mlt config mlt config mlt

5 create 5 add ports 2/1,3/1 5 add vlan 1900 5 add vlan 10

Configure IP address and IST. The IP address points to the partner IST node:

Nortel Metro Ethernet Routing Switch 8600 Configuration — VLANs, Spanning Tree, and Link Aggregation NN46220-511 04.01 26 June 2009 Copyright © 2007-2009 Nortel Networks. All Rights Reserved.

392

CLI configuration examples

MERS-8606:5# config vlan 1900 ip create 1.1.1.1/30 MERS-8606:5# config mlt 5 ist create ip 1.1.1.2 vlan-id 1900 5

Configure SMLT. The SMLT ID must be identical for each IST pair: MERS-8606:5# MERS-8606:5# MERS-8606:5# MERS-8606:5#

config mlt config mlt config mlt config mlt

1 create 1 smlt create smlt-id 1 1 add vlan 10 1 add ports 1/1,1/17 --End--

Configuring MERS8600C 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 1 MERS-8606:5# config vlan 10 create byport 1

3

Configure MLT. VLAN 10 must be spanned across the interswitch trunk (MLT-5): MERS-8606:5# MERS-8606:5# MERS-8606:5# MERS-8606:5#

4

config mlt config mlt config mlt config mlt

5 create 5 add ports 2/1,3/1 5 add vlan 1900 5 add vlan 10

Configure IP address and IST. The IP address points to the partner IST node: MERS-8606:5# config vlan 1900 ip create 1.1.1.2/30 MERS-8606:5# config mlt 5 ist create ip 1.1.1.1 vlan-id 1900

5

Configure SMLT. The SMLT ID must be identical for each IST pair: MERS-8606:5# MERS-8606:5# MERS-8606:5# MERS-8606:5#

config mlt config mlt config mlt config mlt

1 create 1 smlt create smlt-id 1 1 add vlan 10 1 add ports 1/1,1/17 --End--

Configuring MERS8600A

Nortel Metro Ethernet Routing Switch 8600 Configuration — VLANs, Spanning Tree, and Link Aggregation NN46220-511 04.01 26 June 2009 Copyright © 2007-2009 Nortel Networks. All Rights Reserved.

Full mesh SMLT configuration example

Step

Action

1

Disable CP-Limit on IST ports:

393

MERS-8606:5# config ether 2/1,3/1 cp-limit disable 2

Configure VLANs: MERS-8606:5# config vlan 1900 create byport 1 MERS-8606:5# config vlan 10 create byport 1

3

Configure MLT. VLAN 10 must be spanned across the interswitch trunk (MLT-5): MERS-8606:5# MERS-8606:5# MERS-8606:5# MERS-8606:5#

4

config mlt config mlt config mlt config mlt

5 create 5 add ports 2/1,3/1 5 add vlan 1900 5 add vlan 10

Configure the IP address and IST. The IP address points to the partner interswitch trunk node: MERS-8606:5# config vlan 1900 ip create 2.2.2.1/30 MERS-8606:5# config mlt 5 ist create ip 2.2.2.2 vlan-id 1900

5

Configure SMLT. The SMLT ID must be identical for each IST pair: MERS-8606:5# MERS-8606:5# MERS-8606:5# MERS-8606:5#

config mlt config mlt config mlt config mlt

1 create 1 smlt create smlt-id 1 1 add vlan 10 1 add ports 1/1,1/17 --End--

Configuring MERS8600D 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 1 MERS-8606:5# config vlan 10 create byport 1

3

Configure MLT. VLAN 10 must be spanned across the IST (MLT-5): MERS-8606:5# config mlt 5 create MERS-8606:5# config mlt 5 add ports 2/1,3/1

Nortel Metro Ethernet Routing Switch 8600 Configuration — VLANs, Spanning Tree, and Link Aggregation NN46220-511 04.01 26 June 2009 Copyright © 2007-2009 Nortel Networks. All Rights Reserved.

394

CLI configuration examples

MERS-8606:5# config mlt 5 add vlan 1900 MERS-8606:5# config mlt 5 add vlan 10 4

Configure IP address and IST. The IP address points to the partner IST node: MERS-8606:5# config vlan 1900 ip create 2.2.2.2/30 MERS-8606:5# config mlt 5 ist create ip 2.2.2.1 vlan-id 1900

5

Configure SMLT. The SMLT ID must be identical for each interswitch trunk pair: MERS-8606:5# MERS-8606:5# MERS-8606:5# MERS-8606:5#

config mlt config mlt config mlt config mlt

1 create 1 smlt create smlt-id 1 1 add vlan 10 1 add ports 1/1,1/17 --End--

Use the show mlt info and the show smlt info commands to verify the status of the multilink trunks.

SMLT and VRRP configuration example In cases in which the Metro Ethernet Routing Switch is providing the next-hop gateway, and is in Virtual Router Redundancy Protocol (VRRP) mode, the Metro Ethernet Routing Switch can provide additional VRRP benefits. In this example (see Figure 188 "Network topology for SMLT and VRRP" (page 395)), MERS8600A is acting solely as a Layer 2 switch, with a single VLAN 10 configured. The server in this example has a next-hop gateway configured for the VRRP IP.

Nortel Metro Ethernet Routing Switch 8600 Configuration — VLANs, Spanning Tree, and Link Aggregation NN46220-511 04.01 26 June 2009 Copyright © 2007-2009 Nortel Networks. All Rights Reserved.

SMLT and VRRP configuration example

395

Figure 188 Network topology for SMLT and VRRP

Configuring MERS8600B 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 1 MERS-8606:5# config vlan 10 create byport 1

3

Configure MLT. VLAN 10 must be spanned across the interswitch trunk (MLT-5): MERS-8606:5# MERS-8606:5# MERS-8606:5# MERS-8606:5#

4

config mlt config mlt config mlt config mlt

5 create 5 add ports 2/1,3/1 5 add vlan 1900 5 add vlan 10

Configure IP address and IST. The IP address points to the partner IST node. MERS-8606:5# config vlan 1900 ip create 1.1.1.1/30 MERS-8606:5# config mlt 5 ist create ip 1.1.1.2 vlan-id 1900 Nortel Metro Ethernet Routing Switch 8600 Configuration — VLANs, Spanning Tree, and Link Aggregation NN46220-511 04.01 26 June 2009 Copyright © 2007-2009 Nortel Networks. All Rights Reserved.

396

CLI configuration examples

5

Configure SMLT. The SMLT ID must be identical on both nodes: MERS-8606:5# MERS-8606:5# MERS-8606:5# MERS-8606:5#

6

config mlt config mlt config mlt config mlt

1 create 1 smlt create smlt-id 1 1 add vlan 10 1 add ports 1/1

VRRP configuration. These commands add the VRRP virtual IP address of 10.10.10.1 to VLAN 10 with BackupMaster enabled so that both MERS8600B and MERS8600C can respond to ARP. MERS-8606:5# MERS-8606:5# 10.10.10.1 MERS-8606:5# enable MERS-8606:5# r 60 MERS-8606:5#

config vlan 10 ip create 10.10.10.2/24 config vlan 10 ip vrrp 1 address config vlan 10 ip vrrp 1 backup-master config vlan 10 ip vrrp 1 holddown-time config vlan 10 ip vrrp 1 enable --End--

Configuring MERS8600C 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 1 MERS-8606:5# config vlan 10 create byport 1

3

Configure MLT. VLAN 10 must be spanned across the interswitch trunk (MLT-5): MERS-8606:5# MERS-8606:5# MERS-8606:5# MERS-8606:5#

4

config mlt config mlt config mlt config mlt

5 create 5 add ports 2/1,3/1 5 add vlan 1900 5 add vlan 10

Configure IP address and IST. The IP address points to the partner IST node. MERS-8606:5# config vlan 1900 ip create 1.1.1.2/30 MERS-8606:5# config mlt 5 ist create ip 1.1.1.1 vlan-id 1900

5

Configure SMLT. The SMLT ID must be identical on both nodes: MERS-8606:5# config mlt 1 create MERS-8606:5# config mlt 1 smlt create smlt-id 1

Nortel Metro Ethernet Routing Switch 8600 Configuration — VLANs, Spanning Tree, and Link Aggregation NN46220-511 04.01 26 June 2009 Copyright © 2007-2009 Nortel Networks. All Rights Reserved.

SMLT and multicast configuration example

397

MERS-8606:5# config mlt 1 add vlan 10 MERS-8606:5# config mlt 1 add ports 1/1 6

VRRP configuration. These commands add the VRRP virtual IP address of 10.10.10.1 to VLAN 10 with BackupMaster enabled so that both MERS8600B and MERS8600C can respond to ARP. MERS-8606:5# MERS-8606:5# 10.10.10.1 MERS-8606:5# enable MERS-8606:5# r 65 MERS-8606:5#

config vlan 10 ip create 10.10.10.3/24 config vlan 10 ip vrrp 1 address config vlan 10 ip vrrp 1 backup-master config vlan 10 ip vrrp 1 holddown-time config vlan 10 ip vrrp 1 enable --End--

Configuring MERS8600A Step

Action

1

Configure MLT on A: MERS-8606:5# MERS-8606:5# MERS-8606:5# MERS-8606:5#

config vlan 10 create byport 1 config mlt 1 create config mlt 1 add ports 1/1,1/17 config mlt 1 add vlan 10 --End--

The status of VRRP can be seen using the command show ip vrrp info.

SMLT and multicast configuration example Use the following steps to configure multicast distribution over a MLT group: Step

Action

1

Configure multicast distribution globally: MERS-8606:5# config sys mcast-mlt-distribution enable

2

Configure multicast distribution on each MLT group:

Nortel Metro Ethernet Routing Switch 8600 Configuration — VLANs, Spanning Tree, and Link Aggregation NN46220-511 04.01 26 June 2009 Copyright © 2007-2009 Nortel Networks. All Rights Reserved.

398

CLI configuration examples

MERS-8606:5# config mlt 1 mcast-distribution enable --End--

The default settings allow all sources and groups to be distributed over MLT (when enabled). Distribution can be controlled by controlling the source/group masks: MERS-8606:5# config sys mcast-mlt-distribution grp-mask 0.0.0.255 MERS-8606:5# config sys mcast-mlt-distribution src-mask 0.0.255.255

Triangle SMLT and LACP configuration example This configuration example shows how to build and configure a triangle SMLT network using LACP to enable the dynamic set up of SMLT links Figure 189 "SMLT and IEEE 802.3ad configuration example" (page 399).

Nortel Metro Ethernet Routing Switch 8600 Configuration — VLANs, Spanning Tree, and Link Aggregation NN46220-511 04.01 26 June 2009 Copyright © 2007-2009 Nortel Networks. All Rights Reserved.

Triangle SMLT and LACP configuration example

399

Figure 189 SMLT and IEEE 802.3ad configuration example

The following sections provide step-by-step procedures that show how to configure switch S1, S2, and S3 for this example. Configuring S1 Step

Action

1

Create IST VLAN 1900: MERS-8606:5# MERS-8606:5# MERS-8606:5# MERS-8606:5# MERS-8606:5# MERS-8606:5# MERS-8606:5# vlan-id 1900

config vlan 1900 create byport 1 config mlt 5 create config mlt 5 add ports 1/1,2/1 config mlt 5 perform-tagging enable config mlt 5 add vlan 1900 config vlan 1900 ip create 1.1.1.1/30 config mlt 5 ist create ip 1.1.1.2

Nortel Metro Ethernet Routing Switch 8600 Configuration — VLANs, Spanning Tree, and Link Aggregation NN46220-511 04.01 26 June 2009 Copyright © 2007-2009 Nortel Networks. All Rights Reserved.

400

CLI configuration examples

2

Create the SMLT VLAN and add ports: MERS-8606:5# config vlan 100 create byport 1 MERS-8606:5# config vlan 100 ports add 3/1,3/2 MERS-8606:5# config vlan 100 add-mlt 5

3

Configure LACP on ports: MERS-8606:5# config ether 3/1,3/2 lacp key 10 MERS-8606:5# config ether 3/1,3/2 lacp aggregation true MERS-8606:5# config ether 3/1,3/2 lacp enable

4

Create SMLT and configure LACP. Ensure keys match port and keys are same for both SMLT aggregation switches: MERS-8606:5# config mlt 10 create MERS-8606:5# config mlt 10 smlt create smlt-id 10 MERS-8606:5# config mlt 10 perform-tagging enable MERS-8606:5# config mlt 10 lacp key 10 MERS-8606:5# config mlt 10 lacp enable MERS-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# MERS-8606:5# MERS-8606:5# MERS-8606:5# MERS-8606:5# MERS-8606:5# MERS-8606:5# vlan-id 1900

2

config vlan 1900 create byport 1 config mlt 5 create config mlt 5 add ports 1/1,2/1 config mlt 5 perform-tagging enable config mlt 5 add vlan 1900 config vlan 1900 ip create 1.1.1.2/30 config mlt 5 ist create ip 1.1.1.1

Create the SMLT VLAN and add ports: MERS-8606:5# config vlan 100 create byport 1 MERS-8606:5# config vlan 100 ports add 3/1,3/2 MERS-8606:5# config vlan 100 add-mlt 5

3

Configure LACP on ports: MERS-8606:5# config ether 3/1,3/2 lacp key 10 MERS-8606:5# config ether 3/1,3/2 lacp aggregation true MERS-8606:5# config ether 3/1,3/2 lacp enable

Nortel Metro Ethernet Routing Switch 8600 Configuration — VLANs, Spanning Tree, and Link Aggregation NN46220-511 04.01 26 June 2009 Copyright © 2007-2009 Nortel Networks. All Rights Reserved.

Single Port SMLT and LACP configuration example

4

401

Create SMLT and configure LACP. Ensure keys match: port and keys must be the same for both SMLT aggregation switches: MERS-8606:5# config mlt 10 create MERS-8606:5# config mlt 10 smlt create smlt-id 10 MERS-8606:5# config mlt 10 perform-tagging enable MERS-8606:5# config mlt 10 lacp key 10 MERS-8606:5# config mlt 10 lacp enable MERS-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 1 MERS-8606:5# config vlan 100 ports add 3/1-3/4

2

Configure LACP on ports: MERS-8606:5# config ether 3/1-3/4 lacp key 20 MERS-8606:5# config ether 3/1-3/4 lacp aggregation true MERS-8606:5# config ether 3/1-3/4 lacp enable

3

Create MLT 10 and configure LACP. Ensure keys match: port and keys must be the same for both SMLT aggregation switches: MERS-8606:5# config mlt 10 create MERS-8606:5# config mlt 10 perform-tagging enable MERS-8606:5# config mlt 10 lacp key 10 MERS-8606:5# config mlt 10 lacp enable MERS-8606:5# config ether 3/1-3/4 discard-untagged -frames enable --End--

Single Port SMLT and LACP configuration example Single Port SMLT lets you configure a split multilink trunk using a single port. The single port split multilink trunk behaves just like an MLT-based SMLT and can coexist with SMLTs in the same system; however, an SMLT ID can belong to either an MLT-SMLT or a single port split multilink trunk per chassis. With Single Port SMLT, you can scale the number of split multilink trunks on a switch to a maximum number of available ports.

Nortel Metro Ethernet Routing Switch 8600 Configuration — VLANs, Spanning Tree, and Link Aggregation NN46220-511 04.01 26 June 2009 Copyright © 2007-2009 Nortel Networks. All Rights Reserved.

402

CLI configuration examples

When SMLT is enabled on a port, its key becomes default and aggregation becomes true. The selection logic selects the default aggregator for the SMLT port. When SMLT is disabled on a port, aggregation becomes false. This example highlights the steps in configuring Single Port SMLT using LACP to create the LAG. Although a Metro Ethernet Routing Switch 8600 is used for the SMLT client, any LACP enabled device can be used. Figure 190 "Network topology" (page 402) shows the network topology for this configuration example. Figure 190 Network topology

Configuring MERS8600A Step

Action

1

To create the interswitch trunk, enter the following commands: MERS-8606:5# MERS-8606:5# MERS-8606:5# MERS-8606:5# MERS-8606:5# MERS-8606:5# MERS-8606:5# vlan-id 1900

2

conf vlan 1900 create byport 1 conf mlt 5 create conf mlt 5 add ports 1/1,2/1 conf mlt 5 perform-tagging enable conf mlt 5 add vlan 1900 conf vlan 1900 ip create 1.1.1.1/30 conf mlt 5 ist create ip 1.1.1.2

To create the user VLAN, enter the following commands:

Nortel Metro Ethernet Routing Switch 8600 Configuration — VLANs, Spanning Tree, and Link Aggregation NN46220-511 04.01 26 June 2009 Copyright © 2007-2009 Nortel Networks. All Rights Reserved.

Single Port SMLT and LACP configuration example

403

MERS-8606:5# conf vlan 10 create byport 1 MERS-8606:5# conf vlan 10 ports add 1/10 3

To create the single port split multilink trunk, enter the following command: MERS-8606:5# conf ether 1/10 smlt 1 create

4

To enable LACP on each port, enter the following command. No key is required. The default key is used: MERS-8606:5# conf ether 1/10 lacp enable --End--

Configuring MERS8600B Step

Action

1

To create the interswitch trunk, enter the following commands: MERS-8606:5# MERS-8606:5# MERS-8606:5# MERS-8606:5# MERS-8606:5# MERS-8606:5# MERS-8606:5# vlan-id 1900

2

conf vlan 1900 create byport 1 conf mlt 5 create conf mlt 5 add ports 1/1,2/1 conf mlt 5 perform-tagging enable conf mlt 5 add vlan 1900 conf vlan 1900 ip create 1.1.1.2/30 conf mlt 5 ist create ip 1.1.1.1

To create the user VLAN, enter the following commands: MERS-8606:5# conf vlan 10 create byport 1 MERS-8606:5# conf vlan 10 ports add 1/10

3

To create the single port split multilink trunk, enter the following command: MERS-8606:5# conf ether 1/10 smlt 1 create

4

To enable LACP on each port, enter the following command. No key is required. The default key is used: MERS-8606:5# conf ether 1/10 lacp enable --End--

Configuring MERS8600C Step

Action

1

To create the multilink trunk, enter the following commands:

Nortel Metro Ethernet Routing Switch 8600 Configuration — VLANs, Spanning Tree, and Link Aggregation NN46220-511 04.01 26 June 2009 Copyright © 2007-2009 Nortel Networks. All Rights Reserved.

404

CLI configuration examples

MERS-8606:5# conf mlt 10 create MERS-8606:5# conf mlt 10 lacp key 10 MERS-8606:5# conf mlt 10 lacp enable 2

To create the user VLAN and add ports, enter the following commands: MERS-8606:5# conf vlan 10 create byport 1 MERS-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 10 MERS-8606:5# conf ether 1/1-1/2 lacp aggregation true

4

To enable LACP on each port, enter the following command. No key is required. The default key is used: MERS-8606:5# conf ether 1/1-1/2 lacp enable --End--

LACP-based MLT for UNI configuration example The following section is an example of configuring an LACP-based MLT for UNI. Step

Action

1

Enable tagging and configure 1/1 and 1/2 as tagged ports. MERS-8606:5# enable MERS-8606:5# uni MERS-8606:5# enable MERS-8606:5# uni

2

config ethernet 1/1 perform-tagging config ethernet 1/1 interface-type config ethernet 1/2 perform-tagging config ethernet 1/2 interface-type

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# MERS-8606:5# true MERS-8606:5# MERS-8606:5# MERS-8606:5#

config ethernet 1/1 lacp key 2 config ethernet 1/1 lacp aggregation config ethernet 1/1 lacp enable config ethernet 1/2 lacp key 2 config ethernet 1/2 lacp aggregation

Nortel Metro Ethernet Routing Switch 8600 Configuration — VLANs, Spanning Tree, and Link Aggregation NN46220-511 04.01 26 June 2009 Copyright © 2007-2009 Nortel Networks. All Rights Reserved.

LACP-based MLT for NNI configuration example

405

true MERS-8606:5# config ethernet 1/2 lacp enable 4

Create MLT 2 and configure LACP. MERS-8606:5# MERS-8606:5# MERS-8606:5# MERS-8606:5# MERS-8606:5# MERS-8606:5#

5

config mlt config mlt config mlt config mlt config mlt config mlt

2 create 2 interface-type uni 2 perform-tagging enable 2 add vlan 100 2 lacp key 2 2 lacp enable

Enable LACP globally. MERS-8606:5# config lacp enable --End--

LACP-based MLT for NNI configuration example The following section is an example of configuring an LACP-based MLT for NNI. Step

Action

1

Enable tagging and configure 1/1 and 1/2 as tagged ports: MERS-8606:5# enable MERS-8606:5# normal MERS-8606:5# enable MERS-8606:5# normal

2

config ethernet 1/1 perform-tagging config ethernet 1/1 interface-type config ethernet 1/2 perform-tagging config ethernet 1/2 interface-type

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# MERS-8606:5# true MERS-8606:5# MERS-8606:5# MERS-8606:5# true MERS-8606:5#

4

config ethernet 1/1 lacp key 2 config ethernet 1/1 lacp aggregation config ethernet 1/1 lacp enable config ethernet 1/2 lacp key 2 config ethernet 1/2 lacp aggregation config ethernet 1/2 lacp enable

Create MLT 2 and configure LACP.

Nortel Metro Ethernet Routing Switch 8600 Configuration — VLANs, Spanning Tree, and Link Aggregation NN46220-511 04.01 26 June 2009 Copyright © 2007-2009 Nortel Networks. All Rights Reserved.

406

CLI configuration examples

MERS-8606:5# config mlt 2 create MERS-8606:5# config mlt 2 interface-type normal MERS-8606:5# config mlt 2 perform-tagging enable MERS-8606:5# config mlt 2 add vlan 100 MERS-8606:5#config mlt 2 lacp key 2 MERS-8606:5# config mlt 2 lacp enable 5

Enable LACP globally. MERS-8606:5# config lacp enable --End--

Multiple Spanning Tree Protocol configuration example The following section gives an example using MSTP. The topology is given in Figure 191 "Multiple spanning tree topology" (page 406). This network has the following parameters: Figure 191 Multiple spanning tree topology

Nortel Metro Ethernet Routing Switch 8600 Configuration — VLANs, Spanning Tree, and Link Aggregation NN46220-511 04.01 26 June 2009 Copyright © 2007-2009 Nortel Networks. All Rights Reserved.

Multiple Spanning Tree Protocol configuration example

407

• •

Switches B1 and B2 are in multiple spanning tree region 2.

•

B2 is configured so that it becomes the CIST backup; it has the next highest CIST priority of 8192.

•

There are two MSTI instances; MSTI 1 for VLAN 3 and MSTI 2 for VLAN 4.

•

B1 GbE interface 2/2 is configured with a MSTI 2 priority of 16, while B2 GbE interface 4/1 is configured with a MSTI 1 priority of 16. This results in VLAN load balancing.

• •

Switches B3, B4, B5, and B6 are in multiple spanning tree region 1.

•

There are two MSTI instances; MSTI 1 for VLAN 3, and MSTI 2 for VLAN 4.

•

B4 is configured so that it is the MSTI root for VLAN 3 and the backup MSTI 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 backup MSTI root for VLAN 3. Configure the MSTI priority for MSTI 1 to 8192, and the MSTI priority for MSTI 2 to 4096.

B1 is configured so that it becomes the CIST root; it has the lowest CIST priority of 4096.

B3 is configured so that it becomes the CIST regional root; it has a CIST priority of 12288. B4 becomes the backup CIST regional root; it has a priority of 16384.

Configuring MERS8600 B1 Step

Action

1

Set the switch to use MSTP mode. This requires you to save the configuration and boot the switch. Enter the following commands: MERS8600-B1:6# config bootconfig flags spanning-tree-mode mstp MERS8600-B1:6# save bootconfig MERS8600-B1:6# boot -y

2

Configure the MSTP region: MERS8600-B1:6# config mstp region config-id-sel 2 MERS8600-B1:6# config mstp region name region2 MERS8600-B1:6# config mstp region revision 1

3

Configure GbE ports 2/1, 2/2, 2/4, and 2/4 as tagged ports:

Nortel Metro Ethernet Routing Switch 8600 Configuration — VLANs, Spanning Tree, and Link Aggregation NN46220-511 04.01 26 June 2009 Copyright © 2007-2009 Nortel Networks. All Rights Reserved.

408

CLI configuration examples

MERS8600-B1:6# config ethernet 2/1,2/2,2/4,2/5 perform-tagging enable 4

Add VLAN 3: MERS8600-B1:6# config vlan 3 create byport-mstp 1 MERS8600-B1:6# config vlan 3 ports add 2/1,2/2,2/ 4,2/5,1/15

5

Add VLAN 4: MERS8600-B1:6# config vlan 4 create byport-mstp 2 MERS8600-B1:6# config vlan 4 ports add 2/1,2/2,2/ 4,2/5,1/16

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 2 priority 16

8

Configure ports 1/15 and 1/16 as a MSTP edge ports: MERS8600-B1:6# config ethernet 1/15,1/16 mstp cist edge-port true --End--

Configuring MERS8600 B2 Step

Action

1

Set the switch to use MSTP mode. This requires you to save the configuration and boot the switch. Enter the following commands: MERS8600-B2:6# config bootconfig flags spanning-tree-mode mstp MERS8600-B2:6# save bootconfig MERS8600-B2:6# boot -y

2

Configure MSTP region: MERS8600-B2:6# config mstp region config-id-sel 2 MERS8600-B2:6# config mstp region name region2 MERS8600-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/5 perform-tagging enable

4

Add VLAN 3:

Nortel Metro Ethernet Routing Switch 8600 Configuration — VLANs, Spanning Tree, and Link Aggregation NN46220-511 04.01 26 June 2009 Copyright © 2007-2009 Nortel Networks. All Rights Reserved.

Multiple Spanning Tree Protocol configuration example

409

MERS8600-B2:6# config vlan 3 create byport-mstp 1 MERS8600-B2:6# config vlan 3 ports add 4/1,4/2,4/ 4,4/5,3/15 5

Add VLAN 4: MERS8600-B2:6# config vlan 4 create byport-mstp 2 MERS8600-B2:6# config vlan 4 ports add 4/1,4/2,4/ 4,4/5,3/16

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 1 priority 16

8

Configure ports as MSTP edge ports: MERS8600-B2:6# config ethernet 3/15,3/16 mstp cist edge-port true --End--

Configuring MERS1600 B3 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 priority 12288

3

Add VLAN 3: MERS1624G-B3:4# create vlan 3 vid 3 type port MERS1624G-B3:4# config vlan 3 add untagged 10 MERS1624G-B3:4# config vlan 3 add tagged 1,3,5,7

4

Add VLAN 4: MERS1624G-B3:4# create vlan 4 vid 4 type port MERS1624G-B3:4# config vlan 4 add untagged 11 MERS1624G-B3:4# config vlan 4 add tagged 1,3,5,7

5

Configure ports 1 and 3 for 1 Gbps full duplex to be compatible with the ES GbE interfaces: MERS1624G-B3:4# config ports 1,3 speed 1000_full

6

Configure the MSTP region and revision:

Nortel Metro Ethernet Routing Switch 8600 Configuration — VLANs, Spanning Tree, and Link Aggregation NN46220-511 04.01 26 June 2009 Copyright © 2007-2009 Nortel Networks. All Rights Reserved.

410

CLI configuration examples

MERS1624G-B3:4# config stp region name region1 MERS1624G-B3:4# config stp region mstconfigidsel 1 MERS1624G-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 1 MERS1624G-B3:4# config stp instance_id 2 priority 8192 MERS1624G-B3:4# config stp_vlan instance_id 1 add 3

8

Add MSTI 2, change the MSTI priority, and add VLAN 4: MERS1624G-B3:4# create stp instance_id 2 MERS1624G-B3:4# config stp instance_id 2 priority 4096 MERS1624G-B3:4# config stp_vlan instance_id 2 add 4 --End--

Configuring MERS1600 B4 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 priority 12288

3

Add VLAN 3: MERS1624G-B4:4# create vlan 3 vid 3 type port MERS1624G-B4:4# config vlan 3 add untagged 10 MERS1624G-B4:4# config vlan 3 add tagged 1,3,5,7

4

Add VLAN 4: MERS1624G-B4:4# create vlan 4 vid 4 type port MERS1624G-B4:4# config vlan 4 add untagged 11 MERS1624G-B4:4# config vlan 4 add tagged 1,3,5,7

5

Configure ports 1 and 3 for 1 Gbps full duplex to be compatible with 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 region1 MERS1624G-B4:4# config stp region mstconfigidsel 1 MERS1624G-B4:4# config stp region revision 1

7

Add MSTI 1, change the MSTI priority, and add VLAN 3: Nortel Metro Ethernet Routing Switch 8600 Configuration — VLANs, Spanning Tree, and Link Aggregation NN46220-511 04.01 26 June 2009 Copyright © 2007-2009 Nortel Networks. All Rights Reserved.

Multiple Spanning Tree Protocol configuration example

411

MERS1624G-B4:4# create stp instance_id 1 MERS1612G-B4:4# config stp instance_id 1 priority 4096 MERS1624G-B4:4# config stp_vlan instance_id 1 add 3 8

Add MSTI 2, change the MSTI priority, and add VLAN 4: MERS1624G-B4:4# create stp instance_id 2 MERS1624G-B4:4# config stp instance_id 2 priority 8192 MERS1624G-B4:4# config stp_vlan instance_id 2 add 4 --End--

Configuring ES 470 B5 Step

Action

1

Change spanning tree operation mode to MSTP and reboot the switch: ES470_48(config)# spanning-tree op-mode mstp ES470_48(config)# boot Reboot 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 port ES470_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: ES470_48(config)# vlan create 4 type port ES470_48(config)# vlan members add 4 16,47,48

6

Remove VLAN port members from the default VLAN: ES470_48(config)# vlan members remove 1 16

7

Configure the MSTP region and version: ES470_48(config)# spanning-tree mstp region config-id-sel 1 region-name region1 region-version 1

8

Add MSTP MSTI 1 and add VLAN 3:

Nortel Metro Ethernet Routing Switch 8600 Configuration — VLANs, Spanning Tree, and Link Aggregation NN46220-511 04.01 26 June 2009 Copyright © 2007-2009 Nortel Networks. All Rights Reserved.

412

CLI configuration examples

ES470_48(config)# spanning-tree mstp msti 1 ES470_48(config)# spanning-tree mstp msti 1 add-vlan 3 9

Add MSTP MSTI 2 and add VLAN 4: ES470_48(config)# spanning-tree mstp msti 2 ES470_48(config)# spanning-tree mstp msti 2 add-vlan 4 If an error message appears stating that you cannot modify settings and nontagged ports cannot span multiple STPGs, then ensure that all appropriate ports have tagging enabled. In this example, this applies to ports 47 and 48.

10

Configure ports 6 and 7 as MSTP edge ports: ES470_48(config)# interface fastEthernet 15,16 ES470_48(config-if)# spanning-tree mstp edge-port true --End--

Configuring ES 470 B6 Step

Action

1

Change spanning tree operation mode to MSTP and reboot the switch: ES470_48(config)# spanning-tree op-mode mstp ES470_48(config)# boot Reboot the unit(s) (y/n) ? y

2

Add tagging: ES470_48(config)# vlan ports 47,48 tagging tagall

3

Add VLAN 3 and port members: ES470_48(config)# vlan create 3 type port ES470_48(config)# vlan members add 3 15,47,48

4

Remove VLAN port members from the default VLAN: ES470_48(config)# vlan members remove 1 15,47,48

5

Add VLAN 4 and port members: ES470_48(config)# vlan create 4 type port ES470_48(config)# vlan members add 4 16,47,48

6

Remove VLAN port members from the default VLAN: ES470_48(config)# vlan members remove 1 16

7

Configure the MSTP region and version:

Nortel Metro Ethernet Routing Switch 8600 Configuration — VLANs, Spanning Tree, and Link Aggregation NN46220-511 04.01 26 June 2009 Copyright © 2007-2009 Nortel Networks. All Rights Reserved.

Dual home UNI and MSTP configuration example

413

ES470_48(config)# spanning-tree mstp region config-id-sel 1 region-name region1 region-version 1 8

Add MSTP MSTI 1 and add VLAN 3: ES470_48(config)# spanning-tree mstp msti 1 ES470_48(config)# spanning-tree mstp msti 1 add-vlan 3

9

Add MSTP MSTI 2 and add VLAN 4: ES470_48(config)# spanning-tree mstp msti 2 ES470_48(config)# spanning-tree mstp msti 2 add-vlan 4

10

Configure ports 6 and 7 as MSTP edge ports: ES470_48(config)# interface fastEthernet 15,16 ES470_48(config-if)# spanning-tree mstp edge-port true --End--

Dual home UNI and MSTP configuration example The following section gives a sample configuration file to show how dual home UNI and MSTP commands work together. Step

Action

1

Enter the following commands to configure the maintenance domain (MD). MERS-8606:5# config cfm md "nmd" create index 2 maint-level 2 MERS-8606:5# config cfm md "pmd" create index 1 maint-level 5 config cfm md "vmd" create index 3 maint-level 3

2

Enter the following commands to configure the maintenance association (MA). MERS-8606:5# config cfm md "nmd" ma "nma" create index 2 ccm-interval 1000 auto-detect enable MERS-8606:5# config cfm md "pmd" ma "pma" create index 1 auto-detect enable config cfm md "vmd" ma "vma1" create index 1 ccm-interval 1000 ccm-type unicast MERS-8606:5# config cfm md "vmd" ma "vma3" create index 1 ccm-interval 1000 ccm-type unicast

Nortel Metro Ethernet Routing Switch 8600 Configuration — VLANs, Spanning Tree, and Link Aggregation NN46220-511 04.01 26 June 2009 Copyright © 2007-2009 Nortel Networks. All Rights Reserved.

414

CLI configuration examples

3

Enter the following commands to configure the maintenance endpoint. MERS-8606:5# config cfm md "nmd" ma "nma" mep 5 create state enable MERS-8606:5# config cfm md "pmd" ma "pma" mep 25 create state enable config cfm md "vmd" ma "vma1" mep 3 create state enable MERS-8606:5# config cfm md "vmd" ma "vma3" mep 3 create state enable

4

Enter the following commands to configure the remote maintenance endpoint. MERS-8606:5# config cfm md "nmd" ma "nma" rmep 2 create remote-mac 00:1a:8f:06:d3:df MERS-8606:5# config cfm md "vmd" ma "vma1" rmep 1 create remote-mac 00:1a:8f:06:d0:80 config cfm md "vmd" ma "vma3" rmep 35 create remote-mac 00:1a:8f:06:d0:a0

5

Enter the following commands to configure the maintenance intermediate point. MERS-8606:5# cfm md "iclientmd" mip 500 create

6

Enter the following commands to perform phase 1 of port configuration. MERS-8606:5# config ethernet 2/1 perform-tagging enable MERS-8606:5# config ethernet 2/1 interface-type uni config ethernet 2/1 qnq-ethertype 0x88a8MERS-8606: 5# config ethernet 2/3 perform-tagging enable MERS-8606:5# config ethernet 2/3 interface-type uni MERS-8606:5# config ethernet 2/3 qnq-ethertype 0x88a8 MERS-8606:5# config ethernet 2/5 perform-tagging enable MERS-8606:5# config ethernet 2/5 interface-type uni MERS-8606:5# config ethernet 2/5 qnq-ethertype 0x88a8 MERS-8606:5# config ethernet 2/6 perform-tagging enable MERS-8606:5# config ethernet 2/6 interface-type uni MERS-8606:5# config ethernet 2/6 qnq-ethertype 0x88a8 MERS-8606:5# config ethernet 2/20 perform-tagging Nortel Metro Ethernet Routing Switch 8600 Configuration — VLANs, Spanning Tree, and Link Aggregation NN46220-511 04.01 26 June 2009 Copyright © 2007-2009 Nortel Networks. All Rights Reserved.

Dual home UNI and MSTP configuration example

415

enable MERS-8606:5# config ethernet 2/20 interface-type normal MERS-8606:5# config ethernet 2/30 perform-tagging enable MERS-8606:5# config ethernet 2/30 interface-type normal 7

Enter the following commands to configure MLT. MERS-8606:5# mlt 16 create MERS-8606:5# mlt 16 add ports 2/20,2/30 mlt 16 perform-tagging enable

8

ATTENTION UNI configuration The RCT port or MLT is not explicitly configured, as it in dual home ring. It is derived from the rct-vid.

Enter the following commands to configure MSTP dual home UNI. MERS-8606:5# config dh-uni 1 create mac-offset 53 MERS-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/1 MERS-8606:5# config dh-uni 1 partner-dh-uni-mac 00:15:e8:a4:60:81 MERS-8606:5# config dh-uni 2 create mac-offset 2 MERS-8606:5# config dh-uni 2 create MERS-8606:5# config dh-uni 2 name “Lab link 2” MERS-8606:5# config dh-uni 2 rct-hello-interval 1 MERS-8606:5# config dh-uni 2 port 2/3 MERS-8606:5# config dh-uni 2 partner-dh-uni-mac 00:15:e8:a4:60:82 9

Enter the following command to configure B-VLAN. MERS-8606:5# config vlan 100 create byport-mstpr stp 1

10

Enter the following commands to configure RCT-VLAN. MERS-8606:5# config vlan 1000 create byport-mstprs tp 2 config vlan 1000 add-mlt 16MERS-8606:5# config vlan 1000 add-nodal-mep nmd.nma.5

11

Enter the following commands to configure VLAN MEP VLAN. MERS-8606:5# config vlan 11 create byport-mstprstp 1 Nortel Metro Ethernet Routing Switch 8600 Configuration — VLANs, Spanning Tree, and Link Aggregation NN46220-511 04.01 26 June 2009 Copyright © 2007-2009 Nortel Networks. All Rights Reserved.

416

CLI configuration examples

MERS-8606:5# config vlan 11 ports remove 2/2-2/30 member portmember MERS-8606:5# config vlan 11 ports add 2/1 member portmember MERS-8606:5# config vlan 11 cfm-port 2/1 add-mep “vmd.vma.1” MERS-8606:5# config vlan 13 create byport-mstprstp 1 MERS-8606:5# config vlan 13 ports remove 2/1-2/2,2/4-2/30 member portmember MERS-8606:5# config vlan 13 ports add 2/3 member portmember MERS-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 the following commands to configure the port. MERS-8606:5# config ethernet MERS-8606:5# config ethernet “pmd.pma.25” MERS-8606:5# config ethernet ep pmd.pma.25 MERS-8606:5# config ethernet forceportstate disable MERS-8606:5# config ethernet forceportstate disable

13

2/1 add-cfm-control-m 2/1 mstp cist 2/3 mstp cist

Enter the following commands to configure dual home UNI, phase 2. MERS-8606:5# nmd.nma.1.1 MERS-8606:5# vmd.vma1.3.1 MERS-8606:5# MERS-8606:5# MERS-8606:5# nmd.nma.1.1 MERS-8606:5# vmd.vma3.3 MERS-8606:5# MERS-8606:5#

14

2/1 cfm-vid 100 2/1 add-mep

config dh-uni 1 add-controller-meps config dh-uni 1 add-controller-meps config dh-uni 1 rct-vid 1000 config dh-uni 1 state enable config dh-uni 2 add-controller-meps config dh-uni 2 add-controller-meps config dh-uni 2 rct-vid 1000 config dh-uni 2 state enable

Enter the following commands to configure MSTP. MERS-8606:5# config access-mstp 1 create MERS-8606:5# config access-mstp 1 bridge-mac 00:15:e8:a4:60:81 MERS-8606:5# config access-mstp 1 priority 0 MERS-8606:5# config access-mstp 1 forward-delay 1500

Nortel Metro Ethernet Routing Switch 8600 Configuration — VLANs, Spanning Tree, and Link Aggregation NN46220-511 04.01 26 June 2009 Copyright © 2007-2009 Nortel Networks. All Rights Reserved.

Dual home UNI and MSTP configuration example

417

MERS-8606:5# config access-mstp 1 max-age 2000 MERS-8606:5# config access-mstp 1 msti 1 create MERS-8606:5# config access-mstp 1 msti 1 priority 0 MERS-8606:5# config access-mstp 1 msti 1 add-vlan 100-199,2000 MERS-8606:5# config access-mstp 1 msti 2 create MERS-8606:5# config access-mstp 1 msti 2 priority 0 MERS-8606:5# config access-mstp 1 msti 2 add-vlan 200-299 MERS-8606:5# config access-mstp 1 msti 3 priority 0 MERS-8606:5# config access-mstp 1 msti 3 add-vlan 300-399 MERS-8606:5# config access-mstp 1 msti 4 priority 0 MERS-8606:5# config access-mstp 1 msti 4 add-vlan 400-499 MERS-8606:5# config access-mstp 1 name “Lab network” MERS-8606:5# config access-mstp 1 revision-level 2 MERS-8606:5# config access-mstp 1 config-id-sel 0 MERS-8606:5# config access-mstp 1 dh-uni 1 add MERS-8606:5# config access-mstp 1 dh-uni 1 add-master-msti 1 MERS-8606:5# config access-mstp 1 dh-uni 1 add-backup-msti 2-3 MERS-8606:5# config access-mstp 1 dh-uni 2 add MERS-8606:5# config access-mstp 1 dh-uni 2 add-backup-msti 4 15

Enter the following commands to I-SID.

ATTENTION You can add/remove B-VLAN to/from dual home UNI when the endpoint is enabled/disabled. Sub-endpoint 0 is supported; “dh-uni 1 create” is the same as “dh-uni 1.0 create”.

MERS-8606:5# config i-sid 1 create MERS-8606:5# config i-sid 1 b-vlan 100 MERS-8606:5# config i-sid 1 mac-table-size 100 MERS-8606:5# config i-sid 1 end-point dh-uni 1 create MERS-8606:5# config i-sid 1 end-point dh-uni 1 service-type qnq1 MERS-8606:5# config i-sid 1 end-point dh-uni 1 ingress-policer disable MERS-8606:5# config i-sid 1 end-point dh-uni 1 s-vlan 110 MERS-8606:5# config i-sid 1 end-point dh-uni 1 state enable MERS-8606:5# config i-sid 1 end-point dh-uni 1 cfm-vid 200 add-client-mep "cmd.cma.3" direction Nortel Metro Ethernet Routing Switch 8600 Configuration — VLANs, Spanning Tree, and Link Aggregation NN46220-511 04.01 26 June 2009 Copyright © 2007-2009 Nortel Networks. All Rights Reserved.

418

CLI configuration examples

up MERS-8606:5# config i-sid 1 end-point dh-uni 1 cfm-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--

Nortel Metro Ethernet Routing Switch 8600 Configuration — VLANs, Spanning Tree, and Link Aggregation NN46220-511 04.01 26 June 2009 Copyright © 2007-2009 Nortel Networks. All Rights Reserved.

419

.

Appendix Tap and OctaPID assignment (Release 3.x feature set) The switch fabric in the Metro Ethernet Routing Switch 8600 module has nine 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 slots and can support up to eight OctaPIDs. Each OctaPID can support up to eight ports. In the Metro Ethernet Routing Switch 8600, a physical port number is 10 bits 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) are usually referred to as the OctaPID ID. Table 63 "Available module types and OctapPID ID assignments" (page 420) lists the module types that are currently available, along with the associated OctaPID ID assignments for each module.

Nortel Metro Ethernet Routing Switch 8600 Configuration — VLANs, Spanning Tree, and Link Aggregation NN46220-511 04.01 26 June 2009 Copyright © 2007-2009 Nortel Networks. All Rights Reserved.

420

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

Table 63 Available module types and OctapPID ID assignments Module type

Port type

8608GBE and 8608GBM Modules

1000BASE-SX

OctaPID ID assignment Table 64 "8608GBE/860 8GBM/8608GTE/8608G TM/8608SXE modules" (page 421)

1000BASE-LX 1000BASE-ZX 1000BASE-XD 8608GTE and 8608GTM Modules

1000BASE-T

Table 64 "8608GBE/860 8GBM/8608GTE/8608G TM/8608SXE modules" (page 421)

8608SXE Module

1000BASE-SX

Table 64 "8608GBE/860 8GBM/8608GTE/8608G TM/8608SXE modules" (page 421)

8616SXE Module

1000BASE-SX

Table 65 "8616SXE module" (page 421)

8624FXE Module

100BASE-FX

Table 66 "8624FXE module" (page 422)

8632TXE and 8632TXM Modules

10BASE-T/100BASE-TX

Table 67 "8632TXE and 8632TZM modules" (page 422)

1000BASE-SX 1000BASE-LX 1000BASE-ZX 1000BASE-XD 8648TXE and 8648TXM Modules

10/100 Mb/s

Table 68 "8648TXE and 8648TXM modules" (page 422)

8672ATME and 8672ATMM Modules

OC-3c MDA

Table 69 "8672ATME and 8672ATMM modules" (page 423)

OC-12c MDA DS3 8681XLR Module

10GBASE-LR

Table 70 "8681XLR module" (page 423)

Nortel Metro Ethernet Routing Switch 8600 Configuration — VLANs, Spanning Tree, and Link Aggregation NN46220-511 04.01 26 June 2009 Copyright © 2007-2009 Nortel Networks. All Rights Reserved.

Dual home UNI and MSTP configuration example

Table 63 Available module types and OctapPID ID assignments (cont’d.) OctaPID ID assignment

Module type

Port type

8681XLW Module

10GBASE-LW

Table 71 "8681XLW module" (page 424)

8683POSM Module

OC-3c MDA

Table 72 "8683POSM module" (page 424)

OC-12c MDA

Table 64 "8608GBE/8608GBM/8608GTE/8608GTM/8608SXE modules" (page 421) describes the OctaPID ID and port assignments for the 8608GBE, 8608GBM, 8608GTE, 8608GTM, and 8608SXE modules. Table 64 8608GBE/8608GBM/8608GTE/8608GTM/8608SXE modules OctaPID ID assignment

Port assignment

OctaPID ID: 0

Port 1

OctaPID ID: 1

Port 2

OctaPID ID: 2

Port 3

OctaPID ID: 3

Port 4

OctaPID ID: 4

Port 5

OctaPID ID: 5

Port 6

OctaPID ID: 6

Port 7

OctaPID ID: 7

Port 8

Table 65 "8616SXE module" (page 421) describes the OctaPID ID and port assignments for the 8616SXE Module. Table 65 8616SXE module OctaPID ID assignment

Port assignment

OctaPID ID: 0

Ports 1 and 2

OctaPID ID: 1

Ports 3 and 4

OctaPID ID: 2

Ports 5 and 6

OctaPID ID: 3

Ports 7 and 8

OctaPID ID: 4

Ports 9 and 10

OctaPID ID: 5

Ports 11 and 12

OctaPID ID: 6

Ports 13 and 14

OctaPID ID: 7

Ports 15 and 16

Nortel Metro Ethernet Routing Switch 8600 Configuration — VLANs, Spanning Tree, and Link Aggregation NN46220-511 04.01 26 June 2009 Copyright © 2007-2009 Nortel Networks. All Rights Reserved.

421

422

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

Table 66 "8624FXE module" (page 422) describes the OctaPID ID and port assignments for the 8624FXE Module. Table 66 8624FXE module OctaPID ID assignment

Port assignment

OctaPID ID: 0

Ports 1 through 8

OctaPID ID: 1

Ports 9 through 16

OctaPID ID: 2

Ports 17 through 24

Table 67 "8632TXE and 8632TZM modules" (page 422) describes the OctaPID ID and port assignments for the 8632TXE and 8632TXM modules. Table 67 8632TXE and 8632TZM modules OctaPID ID assignment

Port assignment

OctaPID ID: 0

Ports 1 through 8

OctaPID ID: 1

Ports 9 through 16

OctaPID ID: 2

Ports 17 through 24

OctaPID ID: 5

Ports 25 through 32

OctaPID ID: 6

Port 33 (GBIC port)

OctaPID ID: 7

Port 34 (GBIC port)

Table 68 "8648TXE and 8648TXM modules" (page 422) describes the OctaPID ID and port assignments for the 8648TXE and 8648TXM Modules. Table 68 8648TXE and 8648TXM modules OctaPID ID assignment

Port assignment

OctaPID ID: 0

Ports 1 through 8

OctaPID ID: 1

Ports 9 through 16

OctaPID ID: 2

Ports 17 through 24

OctaPID ID: 5

Ports 25 through 32

OctaPID ID: 6

Ports 33 through 40

OctaPID ID: 7

Ports 41 through 48

Nortel Metro Ethernet Routing Switch 8600 Configuration — VLANs, Spanning Tree, and Link Aggregation NN46220-511 04.01 26 June 2009 Copyright © 2007-2009 Nortel Networks. All Rights Reserved.

Dual home UNI and MSTP configuration example

423

Table 69 "8672ATME and 8672ATMM modules" (page 423) describes the OctaPID ID and port assignments for the 8672ATME and 8672ATMM Modules. Table 69 8672ATME and 8672ATMM modules OctaPID ID assignment

Port assignment

OctaPID ID: 0

• • • • • •

OctaPID ID: 1

OctaPID ID: 2

Ports 1 through 4 (with OC-3c MDA) Port 1 (with OC-12c MDA) Ports 1 through 2 (with DS-3 MDA) Ports 5 through 8 (with OC-3c MDA) Port 5 (with OC-12c MDA) Ports 5 through 6 (with DS-3 MDA)

Not used

Table 70 "8681XLR module" (page 423) describes the OctaPID ID and port assignments for the 8681XLR Module. Table 70 8681XLR module OctaPID ID assignment

Port assignment

OctaPID ID: 0

Port 1

OctaPID ID: 1 OctaPID ID: 2 OctaPID ID: 3 OctaPID ID: 4 OctaPID ID: 5 OctaPID ID: 6 OctaPID ID: 7

Table 71 "8681XLW module" (page 424) describes the OctaPID ID and port assignments for the 8681XLW Module.

Nortel Metro Ethernet Routing Switch 8600 Configuration — VLANs, Spanning Tree, and Link Aggregation NN46220-511 04.01 26 June 2009 Copyright © 2007-2009 Nortel Networks. All Rights Reserved.

424

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

Table 71 8681XLW module OctaPID ID assignment

Port assignment

OctaPID ID: 0

Port 1

OctaPID ID: 1 OctaPID ID: 2 OctaPID ID: 3 OctaPID ID: 4 OctaPID ID: 5 OctaPID ID: 6 OctaPID ID: 7

Table 72 "8683POSM module" (page 424) describes the OctaPID ID and port assignments for the 8683POSM Module. Table 72 8683POSM module OctaPID ID assignment

Port assignment

OctaPID ID: 0

• • • • • •

OctaPID ID: 1

OctaPID ID: 2

Ports 1 and 2 (with OC-3c MDA) Port 1 (with OC-12c MDA) Ports 3 and 4 (with OC-3c MDA) Port 3 (with OC-12c MDA) Ports 5 and 6 (with OC-3c MDA) Port 5 (with OC-12c MDA)

Nortel Metro Ethernet Routing Switch 8600 Configuration — VLANs, Spanning Tree, and Link Aggregation NN46220-511 04.01 26 June 2009 Copyright © 2007-2009 Nortel Networks. All Rights Reserved.

425

.

Glossary aggregation switch A switch that aggregates multiple user access switches and provides core connections.

boundary port A bridge port that attaches a multiple spanning tree bridge to a LAN that is not in the same region.

Common and Internal Spanning Tree (CIST) The single spanning tree calculated by STP together with the logical continuation of that connectivity through MST bridges and regions, calculated by MSTP to ensure that all LANs in the bridged LAN are simply and fully connected.

Common Spanning Tree (CST) The single spanning tree calculated by STP and MSTP to connect multiple spanning tree regions.

Internal spanning tree (IST) An internal spanning tree that operates in a given multiple spanning tree region. Within a multiple spanning tree region, multiple spanning instances can be configured. Instance 0 within a region is known as the Internal Spanning Tree (IST).

Interswitch trunk A parallel point to point link that connects two aggregation switches together. The two aggregation switches use this channel to share information so that they can operate as a single logical switch. There can be only one interswitch trunk per SMLT aggregation switch.

Nortel Metro Ethernet Routing Switch 8600 Configuration — VLANs, Spanning Tree, and Link Aggregation NN46220-511 04.01 26 June 2009 Copyright © 2007-2009 Nortel Networks. All Rights Reserved.

426

Glossary

Interswitch Trunking (IST) A method of link aggregation that allows two aggregation switches to connect. The two aggregation switches use this channel to share information so that they can operate as a single logical switch. There can be only one interswitch trunk per SMLT aggregation switch.

MultiLink Trunking (MLT) MultiLink trunking is a method of link aggregation that allows multiple Ethernet trunks to be aggregated together to provide a single logical trunk. A multilink trunk provides the combined bandwidth of the multiple links, as well as the physical layer protection against the failure of any single link.

Multiple Spanning Tree Instance (MSTI) One of a number of spanning trees calculated by MSTP within a multiple spanning tree region. The instance provides a fully connected active topology for frames classified as belonging to a VLAN that is mapped to the MSTI by the MST configuration table used by the multiple spanning tree bridges of the MST region.

MST bridge A bridge capable of supporting the CST, and one or more MSTIs, and of selectively mapping frames classified in any given VLAN to the CST or a given MSTI.

MST region A set of LANs and MST bridges, physically connected via ports on those MST bridges, where each LAN CIST designated bridge is an MST bridge. Each port is either the designated port on one of the LANs, or else a non-designated port of an MST bridge that is connected to one of the LANs. The port MCID matches the MCID of the designated bridge of that LAN.

peer IP address The IP address of the neighbor IST switch VLAN that is chosen for configuring the interswitch trunk. Note that the peer IP address is the IP address of the IST VLAN on the other aggregation switch. You need only configure one VLAN with an IP address for the IST protocol to work. All other VLANs on the interswitch trunk do not require an IP address if you choose not to have VLAN routing enabled.

Nortel Metro Ethernet Routing Switch 8600 Configuration — VLANs, Spanning Tree, and Link Aggregation NN46220-511 04.01 26 June 2009 Copyright © 2007-2009 Nortel Networks. All Rights Reserved.

427

Single Port SMLT A multilink trunk where one or both ends are split between two aggregation switches; however only one port can be configured on each aggregation switch per SMLT ID.

Single Spanning Tree (SST) bridge A bridge capable of supporting only a single spanning tree: the CST. The SST may be supported by the Spanning Tree Protocol (STP) defined in IEEE 802.1d-1998.

SMLT aggregation switches The two switches that share an IST link. Typically, one or more switches that connect to multiple wiring closet switches, edge switches or CPE devices, usually within a single building.

SMLT client A switch located at the edge of the network, such as in a wiring closet or CPE. An SMLT client switch must be able to perform link aggregation (such as with MLT or some other compatible method) but does not require any SMLT intelligence.

SMLT ID The identification number used to specify the corresponding pair of SMLT links. This number is identified between the two aggregation switches and must be paired on each aggregation switch.

SMLT set Two SMLT aggregation switches and their directly connected SMLT clients.

SMLT square A pair of SMLT aggregation switches connected as SMLT clients to another pair of SMLT aggregation switches.

SMLT triangle A configuration where an SMLT client and the two aggregation switches form a triangle.

Spanning tree A simply and fully connected active topology formed from the arbitrary physical topology of connected bridged LAN components by relaying frames through selected bridge ports. The STP

Nortel Metro Ethernet Routing Switch 8600 Configuration — VLANs, Spanning Tree, and Link Aggregation NN46220-511 04.01 26 June 2009 Copyright © 2007-2009 Nortel Networks. All Rights Reserved.

428

Glossary

parameters and states are used and exchanged to facilitate the calculation of that active topology and to control the bridge relay function.

Spanning tree group A collection of ports in one spanning tree instance.

Split multilink trunk A multilink trunk where one or both ends are split between two aggregation switches, thus forming what is typically referred to as an SMLT triangle or SMLT square.

user access switch A switch located at the edge of the network. End stations typically connect directly to a user access switch.

Nortel Metro Ethernet Routing Switch 8600 Configuration — VLANs, Spanning Tree, and Link Aggregation NN46220-511 04.01 26 June 2009 Copyright © 2007-2009 Nortel Networks. All Rights Reserved.

Ciena Metro Ethernet Routing Switch 8600

Documentation Roadmap Copyright 2010 Ciena Corporation All Rights Reserved Printed in Canada, India, and the United States of America Release: 5.2 Publication: NN46220-101 Document status: Standard Document revision: 03.01 Document release date: 21 November 2008

To provide feedback or to report a problem in this document, e-mail us at [email protected]

www.ciena.com LEGAL 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.

Copyright 2010 Ciena® Corporation