NN46220-406 323557-B 01 PDF

Nortel Metro Ethernet Routing Switch 8600
Release Notes Software Release 4.0.4.3
ATTENTION Clicking on a PDF hyperlink takes you to the appropriate page. If necessary, scroll up or down the page to see the beginning of the referenced section.
NN46220-406
.
323557-B Rev 01
Document status: Standard Document version: 01.01 Document date: 5 January 2007 Copyright 2007, Nortel Networks All Rights Reserved.
Restricted rights legend

Use, duplication, or disclosure by the United States Government is subject to restrictions as set forth in subparagraph (c)(1)(ii) of the Rights in Technical Data and Computer Software clause at DFARS 252.227-7013. Notwithstanding any other license agreement that may pertain to, or accompany the delivery of, this computer software, the rights of the United States Government regarding its use, reproduction, and disclosure are as set forth in the Commercial Computer Software-Restricted Rights clause at FAR 52.227-19.
Statement of conditions
In the interest of improving internal design, operational function, and/or reliability, Nortel Networks Inc. reserves the right to make changes to the products described in this document without notice. Nortel Networks Inc. does not assume any liability that may occur due to the use or application of the product(s) or circuit layout(s) described herein. Portions of the code in this software product may be Copyright 1988, Regents of the University of California. All rights reserved. Redistribution and use in source and binary forms of such portions are permitted, provided that the above copyright notice and this paragraph are duplicated in all such forms and that any documentation, advertising materials, and other materials related to such distribution and use acknowledge that such portions of the software were developed by the University of California, Berkeley. The name of the University may not be used to endorse or promote products derived from such portions of the software without specic prior written permission. SUCH PORTIONS OF THE SOFTWARE ARE PROVIDED "AS IS" AND WITHOUT ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, WITHOUT LIMITATION, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE. In addition, the program and information contained herein are licensed only pursuant to a license agreement that contains restrictions on use and disclosure (that may incorporate by reference certain limitations and notices imposed by third parties).
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 afliates ("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 afliates, 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 condential 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 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 modications unless expressly authorized; or d) sublicense, rent or lease the Software. Licensors of intellectual property to Nortel Networks are beneciaries 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 Customers 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. 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, CUSTOMERS 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 foregoing limitations of remedies also apply to any developer and/or supplier of the Software. Such developer and/or supplier is an intended beneciary of this Section. Some jurisdictions do not allow these limitations or exclusions and, in such event, they may not apply. General a. 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 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). 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. Customer is responsible for payment of any taxes, including personal property taxes, resulting from Customers use of the Software. Customer agrees to comply with all applicable laws including all applicable export and import laws and regulations. Neither party may bring an action, regardless of form, more than two years after the cause of the action arose. The terms and conditions of this License Agreement form the complete and exclusive agreement between Customer and Nortel Networks. 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.
3.
4.
b.
c.
d. e. f.
Contents
Metro Ethernet Routing Switch 8600 Software Release 4.0.4.3 7
Important notes before upgrading to this release 8 Locating documentation 8 File names for this release 9 Fixes from earlier releases 10 Downgrading the switch 10 Ethernet Services Unit upgrade requirements 11 Device Manager installation 11 Supported Release 4.0.4.3 software capabilities 12 Release 4.x and R-series module system requirements overview 14 SMLT network design considerations 15 Operating the switch with the Metro ESM 8668 module 16 8010 and 8006 chassis 16 General upgrade considerations 18 Conguration le requirements 19 Dual CPU/SF upgrade process 19 Hot-swapping the CPU/SF module or I/O modules 20 Upgrading the Metro Ethernet Routing Switch 8600 to Release 4.0.4.3 20 Before upgrading the software 20 Backing up the conguration and boot conguration les 21 Verifying the boot-prom version 23 Verifying the ESM status 24 Upgrading the software image 24 Upgrading the Metro Ethernet Routing Switch 8600 environment with dual-home rings 25 Upgrading the software on a non-redundant Metro Ethernet Routing Switch 8600 CPU 25 Upgrading the software on a redundant CPU for Warm Standby (Non HA) 28 Upgrading the software on a redundant CPU for Hot Standby (HA) 33 Upgrading Metro Ethernet Routing Switch 8600 and Ethernet Services Unit for RRP 38 Upgrading the ESM FPGA 39 Updating Firmware revision on R-series modules 42 Reformatting the 8692SF Flash from 16 MB to 40 MB 45
Nortel Metro Ethernet Routing Switch 8600 Release Notes Software Release 4.0.4.3 NN46220-406 01.01 Standard 4.0.4.3 5 January 2007
Copyright 2007, Nortel Networks
.
Nortel Networks Condential
6 Contents New feature enhancements and changes 48 Enhanced CLI commands 48 Hardware Support 51 Supported standards, RFCs, and MIBs 51 General conguration issues and considerations 53 Platform 53 Provider Backbone Transport 54 High-availability CPU 55 ESU rings 55 VLACP enabled on NNI ports 55 IP static routes 56 IS-IS 56 OSPF 56 CPU SSF management port 57 Metro ESM 8668 58 Local and remote UNI considerations 59 Multi-service UNI ports 60 Metro Ethernet Routing Switch 8600 QoS considerations 61 Dual-home ring 63 Legacy access ports (ESM Server ports) 64 ESU and customer CPE management considerations 65 Ethernet MTU size 65 Transparent Domain Continuity tests 66 MAC learning keys and 32-bit UNIs 68 MLT and SMLT considerations 69 Customer IP UNIs 71 IP spoong 71 MSTP/RSTP 72 QinQ 72 Scaling limits 73 CRs xed in Release 4.0.4.3 78 CRs xed in Release 4.0.4.2 78 CRs xed in Release 4.0.4.0 79 Known issues and CRs 81 Platform 83 PBT 85 R-module UNI 87 High Availability 88 Dual-home ring 89 Documentation corrections 89 Related publications 89 Hard copy technical manuals 90 How to get help 91
.
Metro Ethernet Routing Switch 8600 Software Release 4.0.4.3

The release notes for Metro Ethernet Routing Switch 8600 Release 4.0.4.3 describe le names, upgrade processes, and any known issues that exist in this release. The information in these release notes is based on Metro Ethernet Routing Switch 8600 Software Release 4.0.4.3 and Java Device Manager (JDM) Release 5.9.9. Unless otherwise specied, the term "switch" refers to the Metro Ethernet Routing Switch 8600. Note that the name "Metro Ethernet Passport 8600 Switch" is now known as the "Metro Ethernet Routing Switch 8600," and the new name will appear in future documents. The information in these release notes supersedes applicable information in other documentation. The following main topics are discussed in this document:
Topic "Important notes before upgrading to this release" (page 8) "Operating the switch with the Metro ESM 8668 module" (page 16) "General upgrade considerations" (page 18) "Upgrading the Metro Ethernet Routing Switch 8600 to Release 4.0.4.3" (page 20) "Upgrading the software image" (page 24) "New feature enhancements and changes" (page 48) "Hardware Support" (page 51) "Supported standards, RFCs, and MIBs" (page 51) "General configuration issues and considerations" (page 53) "Scaling limits" (page 73)
.
8 Metro Ethernet Routing Switch 8600 Software Release 4.0.4.3
Topic "CRs fixed in Release 4.0.4.3" (page 78) "CRs fixed in Release 4.0.4.2" (page 78) "CRs fixed in Release 4.0.4.0" (page 79) "Known issues and CRs" (page 81) "Documentation corrections" (page 89) "Related publications" (page 89) "Hard copy technical manuals" (page 90) "How to get help" (page 91)
Important notes before upgrading to this release

The Metro Ethernet Routing Switch 8600 Software Release 4.0.4.3 does not support conguration les created with Enterprise Routing Switch 8600 Software Release 3.7 software. Conguration les created with Release 3.7 will not be supported until Release 4.1. Nortel recommends that you save a backup conguration before migrating to any new software release.
Locating documentation
For a complete list of related publications, refer to "Related publications" (page 89). The Metro Ethernet Routing Switch 8600 Release 4.0.4.3 documentation suite is located on the documentation CD included with your software or on the Nortel technical documentation web site: Step 1 2 3 Action Go to http://www.nortel.com/documentation In the By Product Family section, click Metro Ethernet Routing Switch. In the Metro Ethernet Routing Switch: General Availability section, scroll down to the Metro Ethernet Routing Switch 8600 Services section, then click Documentation. End
.
Important notes before upgrading to this release 9
File names for this release

Supported Metro Ethernet Routing Switch 8600 software les Module or file type Boot configuration file Configuration file MERS 8600 Images Boot monitor image Run-time image Run-time image for R modules Mezzanine image Metro ESM 8668 image 3DES DES/SNMPv3 image MIB MIB (zip file) POS Ethernet code ATM Ethernet code JDM Images Solaris for SPARC image Microsoft Windows image Device Manager software image Device Manager software image jdm_5990_sol aris_sparc.sh jdm_5990.exe CPU and switch fabric firmware for the Metro Ethernet Routing Switch 8600. Metro Ethernet Routing Switch 8600 image with VPN-based services supported on 8691SF, 8691omSF, and 8692omSF CPU modules. The Metro Ethernet Routing Switch 8600 image for R modules Onboard daughter card for the 8691omSF and 8692omSF CPU module that is required to support VLACP capabilities. The Metro Ethernet Routing Switch 8600 image for ESM 8668 module provides Ethernet VPN, VLACP, and service provider encapsulation capabilities. Encryption module, which allows you to use Secure Shell (SSH) Encryption module, which allows you to use the Privacy protocol with SNMPv3 Metro Ethernet Routing Switch 8600 MIB zip file containing the MIB file Metro Ethernet Routing Switch 8600 POS Ethernet Code v4.0 Metro Ethernet Routing Switch 8600 ATM Ethernet Code v4.0 oe8b4043.img oe8a4043.img Description Metro Ethernet Routing Switch 8600 boot configuration file Metro Ethernet Routing Switch 8600 configuration file File name boot.cfg config.cfg
oe8j4043.dld
oe8m4043.dld
oe8o4043.dld
p80c4043.img p80c4043.des p80a4043.mib p80a4043.mib .zip p80p4043.dld p80t4043.dld
.
Module or file type Linux image HP Unix image
Description Device Manager software image Device Manager software image
File name jdm_5990_linu x.sh jdm_5990_hpu x_ pa-risc.sh
8010 and 8006 chassis data performance Module type Pre-E, E and M series 8630GBR, R series 8683XLR, R series Standard Slot (S1 and S10) [full duplex] 16Gbps 16Gbps 16Gbps High Performance Slot (S2-4, S7-9) [full duplex] 16Gbps 60Gbps 60Gbps
The following message displays on the console when an R-series module is inserted into a standard slot. The actual warning message reads:
CPU5 [09/26/05 10:29:26] HW warning For maximum performance, Nortel recommends placing R modules in slots 2 to 4 or 7 to 9 only. Insertion of an 8630GBR or 8683XLR into slot 1 or 10 yields a limited performance with existing chassis hardware. Please refer to 4.0 Release Notes for additional details.
A new chassis revision with an upgraded High Performance backplane compatible with existing pre-E, E- and M- series, and new R-series modules supporting high performance in all slots, is shipping with all new chassis purchased.
Fixes from earlier releases

Release 4.0.4.3 contains xes from Metro Ethernet Routing Switch 8600 Software releases up to and including: Ethernet Routing Switch 8600 Release 4.0.3.2 Metro Ethernet Routing Switch 8600 Release 3.6.2.0 Metro Ethernet Routing Switch 8600 Release 4.0.0.4 Metro Ethernet Routing Switch 8600 Release 4.0.2.2 Metro Ethernet Routing Switch 8600 Release 4.0.4.0 Metro Ethernet Routing Switch 8600 Release 4.0.4.2
Downgrading the switch

Downgrades from Release 4.0.4.3 to an earlier release require a previously saved cong le (boot.cfg and cong.cfg). Prior to downgrading to a 3.x.x release, you must remove the R modules.
.
Ethernet Services Unit upgrade requirements

When you upgrade the Metro Ethernet Routing Switch 8600 to Release 4.0.4.3, you must upgrade all the ESUs to the software release supported by Metro Ethernet Routing Switch 8600 Release 4.0.4.3 due to an optimized IP VLAN broadcast datapath change and other known issues.
Supported ESU images with Metro Ethernet Routing Switch 8600 Release 4.0.4.0
The Metro Ethernet Services Unit 1800 and 1850 provide a demarcation point between the customer network and the service provider network and supports aggregation of multiple ports on a single ring or on a standalone connection point. The ESU maintains its own image and features and support varies from release to release. Metro Ethernet Routing Switch 8600 Release 4.0.4.3 is compatible with the ESU images as noted in the following table. Support for earlier ESU releases of software is limited only to maintaining ESU ring services and ESU standalone service during the Metro Ethernet Routing Switch 8600 upgrade process. See the ESU release notes for procedures on how to upgrade your ESU 1800 and ESU 1850 after completing the upgrade process for the Metro Ethernet Routing Switch 8600.
Supported ESU Images Hardware Metro Ethernet Routing Switch 8600 ESU 1800 ESU 1850 Release Images 4.0.0.x 3.0.x, 3.1.x 2.2.x, 3.0.x, 3.1.x Release Images 4.0.x, 4.0.x.x (see Note1) 3.0.x, 3.1.x (see Note 2) 2.2.x, 3.0.x, 3.1.x
Note 1: The L2 SW mode of ESU is supported with all Metro Ethernet Routing Switch 8600 releases. Note 2: The ESU 3.1 release contains HW Rev. 2, which supports RTC.
Device Manager installation

Java Device Manager (JDM) version 5.9.9 supports Metro Ethernet Routing Switch 8600 Release 4.0.4.3. To install JDM on your PC, Nortel recommends that you have a minimum of 256 RAM and 350 MB of available disk space. Device Manager installation procedures are now standardized across all platforms. In addition, the required Java Runtime Environment (JRE) (version 1.4.2) is now part of the JDM installation package and does not require a separate installation. The bundled JRE is used with this JDM only and should not affect other JAVA applications on the same system.
.
For Solaris, note that certain OS patches are required for JDM/JRE to function properly. Consult with SUN to install the appropriate OS patches before you launch JDM. For more information about Device Manager, see Installing and Using Device Manager (317832-D).
Supported Release 4.0.4.3 software capabilities

This section describes supported software and hardware capabilities in Metro Ethernet Routing Switch 8600 Release 4.0.4.3, and contains the following topics: "Supported software capabilities" (page 12) "Unsupported Metro Ethernet Routing Switch 8600 Enterprise-based features" (page 14)
Supported software capabilities

Metro Ethernet Routing Switch 8600 Release 4.0.4.3 supports the following features: Triple Play: Mixed Service Type - Ethernet VPN, IP Unicast, IP Multicast High-Availability CPU for L2 and EVPN Ethernet VPN and IP trafc path selection per C-VID VoIP, Internet Access (and Management trafc) - IP Unicast Video Distribution - IP Multicast Multicast Services (PIM-SSM and IGMP only) IPMC routing: PIM-SSM with IGMP channel table for SSM (static SSM for IGMP v2) IGMP Access Control List Filters on legacy and ESM ports Global lters (restrictions apply) Ring Egress IP Multicast BGP Routing (for NMS management of edge routers) IP management of ESU and edge devices in front of ESU and Metro Ethernet Routing Switch 8600 UNIs Enhanced Ring Resiliency Protocol (single-home rings only) Dual-home Layer 2 ESU ring into two Metro Ethernet Routing Switch 8600s (restrictions apply) 802.1w RSTP NNI 802.1s MSTP NNI Optical Ethernet Layer 2 functionality (such as Optical Metro 1000.OPE) UNI support:
.
Transparent Switched QinQ(1) (single tag classication for Metro Ethernet Routing Switch 8600 stacked VLAN) QinQ(2) (dual tag classication for Metro Ethernet Routing Switch 8600 stacked VLAN) Multi-Service ports (multiple UNI IDs on the same ESM port) Local UNI switching Different MAC aging timer conguration per endpoint MAC address limit per VPN endpoint IP address limit per customer-ip-vlan endpoint Mapped Management VLAN NNI feature Customer VLAN remapping on egress Static VPN congurations 50 millisecond Ethernet access ring with Metro ESU 1800 and 1850 modules (50 ms access ring failover) 50 millisecond Ethernet Trunk MLT failover (with Mezzanine daughter card installed on the 8691omSF, or 8692omSF CPU (SMLT links do not support VLACP and 50 ms failover.) Support point-to-point, point-to-multipoint, and multipoint-to-multipoint connectivity options Policing in 64k increments - two rate 3-color marker Congurable token bucket depth Ingress Multicast and Broadcast Policing in 64k increments Service Provider 4 classes of service with DSCP, and p-bit VLAN criteria for COS classication Statistics and SLA functionality support Diagnostic services, including port mirroring, PCAP, and ping snoop (on NNI and legacy ports only) RMON on NNI ports (on NNI and legacy ports only; stats are not per VPN) Security services (Radius, SNMP-V3, SSL)
.
Unsupported Metro Ethernet Routing Switch 8600 Enterprise-based features

When you operate the Metro Ethernet Routing Switch 8600 Release 4.0.4.3 as a VPN Metro Aggregation switch, the following Enterprise-based features are not supported: IPX Routing via access ports and NNI ports Multicast features IGAP and DVMRP Ethernet Routing Switch 8600 Release 3.5 SMP logging enhancements Policy-based VLANs SAM security enhancements and SSL module Spanning Tree for local TLS access ports, ESU standalone, ESU ring through ESM ports RMON for ESM 8668 ports, including VPN-based UNIs and IP-Customer-VLAN UNIs MAC-ap-time-limit for local TLS access ports, ESU standalone, ESU ring through ESM 8668 ports Web-server access for VPN information, OPM information (including errors and statistics), Access UNI information VLACP not supported on MLT ports used as IST links for SMLT aggregation switches 50 ms Ethernet Trunk MLT Failover for SMLT aggregation switches Stacked VLANs on NNI trunk ports The Enterprise md5 command used to calculate the md5 digest les on the switch ash memory
Release 4.x and R-series module system requirements overview

Nortel recommends installing R modules in high performance slots in either the existing chassis, or high performance chassis. Details can be found in the section 8010 and 8006 chassis. Nortel requires using the 8692 CPU/SF in systems with R-series modules installed to support maximum performance. A warning message is displayed on the console if R-series modules are running in a system with a 8691 CPU/SF:
#CPU5 [06/28/05 09:19:23] HW WARNING For maximum performance and support, the 8692SF is required for use of the 8630GBR and 8683XLR. Use of an 8630GBR or 8683 XLR with the 8690/8691SF fabric is not a recommended configuration and continued use may result in an unacceptable level of traffic oversubscription.
.
Note that the 8690 CPU/SF is not supported in Metro Ethernet Routing Switch 8600 4.x.x.x
SMLT network design considerations

Use this procedure when designing an SMLT network. For more information about SMLT, see Network Design Guidelines (313197-D) Step 1 Action Ensure proper IST connectivity; dene a separate VLAN for the IST protocol:
config mlt 1 ist create ip <value> vlan-id <value>
Do not enable a routing protocol on this VLAN. 2 To ensure IST is not disabled inadvertently, disable CP-limit on the IST ports:
config ethernet <slot|port> cp-limit disable
Keep CP-limit enabled on SMLT ports; change multicast-limit value to 6000:

config ethernet <slot|port> cp-limit enable multicast-limit 6000
Nortel recommends that CP limit is enabled on SMLT ports to protect the SMLT aggregation switches against unforeseen DOS attacks. 4 Enable loop detect on SMLT ports:
config ethernet <slot/port> loop-detect enable action port-down
For Release 4.0.4, Nortel recommends that you ENABLE loop detect with the action port-down on your SMLT ports (do not enable it on IST ports); this recommendation is in direct contrast to earlier releases. Be aware that loop-detect will disable ports that see apping MAC addresses between the correct port and the looping port. In certain circumstances correct ports can get disabled. Disable loop-detect on critical interfaces which should not be disabled in a looping case. 5 Enable tagging on SMLT links:
config ethernet <slot/port> perform-tagging enable
Nortel recommends that you enable tagging on SMLT ports and drop untagged frames to ensure that SMLT client switches with default congurations will not adversely affect SMLT aggregation switch behavior.
.
Enable drop untagged frames on SMLT links:

config ethernet <slot/port> untagged-frames-discard enable
End
Operating the switch with the Metro ESM 8668 module

The Metro Ethernet Services Module (Metro ESM 8668) supports Nortel Metro Ethernet Solutions integration with the Metro Ethernet Routing Switch 8600 backplane fabric. The Metro ESM 8668 module is compatible with most legacy I/O modules (including the Ethernet Routing Switch 8608 SXE) and emulates the enhanced Ethernet VPN services that are also provided by the Optical Metro 1000 family product lines. When you operate the Metro Ethernet Routing Switch 8600 with the Metro ESM 8668 module installed, in combination with Metro Ethernet Routing Switch 8600 Release 4.0.4 software, the switch becomes a VPN Metro Aggregation switch. Metro Ethernet Routing Switch 8600 Release 4.0.4 adds service provider (SP) encapsulation services (VPN-type service) and Virtual LACP (VLACP) capability. VLACP is an extension to LACP, used to detect end-to-end failure for MLT links within 50 milliseconds (ms). An onboard daughter card for the 8692omSf and 8691omSf CPU is required to support 50 ms VLACP capabilities. If you are using the Metro Ethernet Routing Switch 8600 software for its Enterprise-specic capabilities, refer to the Release Notes for the Ethernet Routing Switch 8000 Series Switch Software Release 4.0.1.0 (part number 317177-C).
8010 and 8006 chassis

Release 4.x provides an enhanced set of features and functionality for the Metro Ethernet Routing Switch 8600, including new high-density modules and switch fabrics for increasing the switch fabric performance to 512 Gbps. The new R-series modules offer increased port density and performance over the existing pre-E, E and M-series modules. However, for customers with existing 8010 and 8006 chassis, it is important to introduce the concept of standard and high performance slots. An R-series module installed in a standard slot will deliver increased port density, and an R-series module installed in a high performance slot will deliver increased performance as well.
.
Operating the switch with the Metro ESM 8668 module 17
R-series modules inserted in slots 2 to 4 and slots 7 to 9 of the 8010 10-slot chassis and slots 2 to 4 of the 8006 six-slot chassis operate at high performance. R-series modules inserted into slot 1 and slot 10 of the 8010 chassis, and slot 1 of the 8006 chassis operate at standard performance. Refer to "8010 and 8006 chassis data performance" (page 10) for relative data performances per slot with two fabrics installed in the existing 8010 and 8006 chassis. If you have an existing installed base of ESM 8668 modules, and you are currently operating your switch nodes with Metro Ethernet Routing Switch 8600 release 3.5.x, be sure to verify that you have up-to-date boot-proms on your ESM 8668 blades. To verify your ESM 8668 boot-prom version, refer to "Verifying the boot-prom version" (page 23).
Supported power supplies

The 8010co, 8010, and 8006 chassis each provide three bays for installing power supplies. The following power supplies are available for these chassis: 8004 AC Power Supply 8005 AC Power Supply 8004 DC Power Supply 8005 DC Power Supply
The 8006 and 8010 chassis provide three bays for installing either AC or DC power supplies. A minimum of two power supplies is required for the 8010co chassis. You can also install an additional power supply for redundancy. The 8010co chassis requires an air intake bezel. If you installed Model 8005AC power supplies (1500W) in the 8010co chassis with an air intake bezel imprinted with 312096-A, or if you have difculty installing the bezel over the 8005AC power supplies, you can order a modied bezel (Order Code DS1411027). When conguring a Metro Ethernet Routing Switch 8600 series system, you should consider total power consumption to ensure proper system performance. The total input power consumption of the components, including modules and fan trays, must not exceed the output power rating of the power supply. To determine the minimum number of power supplies to install for the system: Add the total (3.3 v and 12 v) input power consumption (wattage) for all components including modules and fan trays assemblies. For more information, see Installing and Maintaining the Metro Ethernet Routing Switch 8600 Series Chassis (320417-B).
.
Refer to the output power rating of the power supply, based on the input connection. See your power supply installation manual for the output power ratings and other technical specications.
General upgrade considerations

This section contains guidelines you should consider when upgrading to Metro Ethernet Routing Switch 8600 Release 4.0.4.3.
CAUTION
Do not use a software image prior to the Metro 8600 Release 3.6.0.0 with the 8692omSF module. If you downgrade the software (specically the boot monitor image, oe8b3600.img) to the previous release 3.5.3.2 or earlier, it may become necessary to return the module to Nortel, due to boot ash corruption.
CAUTION
The conguration le generated with Metro Ethernet Routing Switch 8600 Software Release 4.0.4.3 contains options that are not backward compatible with Metro Ethernet Routing Switch 8600 Software Releases 3.5.x or 3.6.x. Loading a 4.0.x.x conguration le on a 3.5.x or 3.6.x run-time image generates errors and causes the image to abort loading the conguration le. As a precaution, before you upgrade or downgrade your switch software, make a copy of the switch conguration le specied in the boot.cfg le using the following command: copy /flash/config.cfg /<device>/config_backup.cfg where device can be PCMCIA, ash, or an IP host.
A system with or without R modules installed can operate using Release 4.0.4.3, provided that the CPU/SF has at least 256 MB of memory. The 8692omSf CPU/SF module is only supported with Metro Ethernet Routing Switch 8600 release 3.6.0 and greater. The 8691omSF CPU/SF modules have no release restrictions. After you upgrade the Metro Ethernet Routing Switch 8600 software, save the conguration le. Nortel does not support different software versions on a redundant CPU/SF conguration. For example, you cannot have a primary CPU/SF running release 3.6.1 and a standby CPU/SF running 4.0.4.3. The primary and standby CPU/SF require the same amount of memory. The only exception is the memory being used during the upgrade. When installing les on the onboard ash or PCMCIA, verify ash capacity before downloading the les.

.
General upgrade considerations 19
This section includes the following topics: "Conguration le requirements" (page 19) on this page, "Dual CPU/SF upgrade process" (page 19) "Hot-swapping the CPU/SF module or I/O modules" (page 20)
Conguration le requirements
The R-series modules require loading an I/O dld image le onto each module. By default this le is named oe8j4043.dld and is loaded automatically. If you plan to rename this le, you must enter the following command for each R-module slot in the boot.cfg conguration le:
bootp image-name /flash/newjname.dld <slot-number>
The following is an example for an R module in slot 2: MERS-8610:5# bootconfig bootp image-name /flash/oe8j4043.dld 2 MERS-8610:5# save bootconfig
Dual CPU/SF upgrade process

This section describes the recommended boot conguration options and the recommended upgrade process.
Recommended boot conguration options

There is no hitless upgrade supported at this time, therefore a system upgrade results in losing some customer trafc data. In a system with dual Metro Ethernet Routing Switch 8691/92 CPU/SF modules, a save-to-standby boot ag option is normally enabled. This option, if enabled, automatically saves the conguration and boot les to both standby and primary CPUs. The following example shows how to enable this option (default operation is disabled): MERS-8610:5# config bootconfig flags savetostandby true MERS-8610:5# save bootconfig MERS-8610:5# boot -y If you are using the out-of-band Ethernet port of the 8691/92 CPU/SF module for management, Nortel recommends adding a virtual IP address. This allows access to the primary CPU, regardless if the primary CPU is slot 5 or slot 6. To add a virtual IP address, enter the following CLI command, and save the conguration. config sys set mgmt-virtual-ip <ipaddr/mask>
.
Recommended upgrade process

In dual CPU/SF systems, upgrade the standby CPU/SF rst, and then the primary CPU. When the standby CPU/SF upgrade is complete, the primary CPU/SF is rebooted (prior to upgrading the primary CPU/SF) to allow the system to manually switch over to the newly upgraded CPU/SF. If an unexpected problem occurs, the system reverts to the previous CPU/SF with the older release. This process ensures that at least one CPU/SF is fully operational during the upgrade process.
Hot-swapping the CPU/SF module or I/O modules

When hot-swapping the active CPU/SF module in a Metro Ethernet Routing Switch 8600 with redundant CPU/SF modules, wait until the redundant CPU/SF module is stabilized before inserting other modules. The redundant CPU/SF module displays a logon prompt on the console screen. If no console connection is available, wait for at least 30 seconds before inserting the replacement CPU/SF module or the removed CPU/SF module. In addition, during a CPU/SF failover, do not hot-swap I/O modules until the new CPU/SF becomes the primary CPU/SF.
CAUTION
Do not hot-swap or insert modules in a Ethernet Routing Switch 8000 Series chassis while the switch is booting, as the module may not be recognized and a module initialization failure may occur.
Upgrading the Metro Ethernet Routing Switch 8600 to Release 4.0.4.3

This section provides instructions for upgrading the enterprise Ethernet Routing Switch 8600 or the Metro Ethernet Routing Switch 8600 to support the Metro Ethernet Routing Switch 8600 Release 4.0.4.3 software image. After completing the software upgrade, the switch can operate as an aggregation device in the Metro Ethernet Network (MEN). This section includes the following topics: "Before upgrading the software" (page 20) "Upgrading the software image" (page 24)
Before upgrading the software

Before upgrading to the Metro Ethernet Routing Switch 8600, you must: Read the entire upgrade procedure before attempting to upgrade the switch. This procedure can cause interruption of normal switch operation.
.
21
Back up your runtime conguration and boot conguration before starting the switch upgrade. Consult Important Security Information for the 8000 Series Switch (314997-D) for security-related issues. Take special note of the following cautionary messages: The conguration le generated with software Release 4.0.4.3 contains options that may not be backward compatible with prior software releases. Loading a 4.0.4.3 conguration le on any prior release run-time image may generate errors and cause the conguration le to abort loading. If this happens, a factory default conguration will be loaded. Before you run a copy command using TFTP to overwrite an existing le with the same name on the ash or PCMCIA, be aware that if the le transfer fails, the le on the ash or PCMCIA is deleted. For example, if you issue the command copy 111.111.1.11:oe8a4043.img /flash/ oe8a4043.img and the server is not available or the le on the server does not exist, the oe8a4043.img le is deleted on the ash (if previously existing). To preserve the original le, you can either rename or make a backup copy of this le on the PCMCIA or ash before you begin the copy process. When installing les on the onboard ash or PCMCIA, make sure that you verify capacity before you download the les. Nortel recommends that you save a copy of the boot.cfg le in the /flash directory. During bootup, if the /flash/boot.cfg le is not present, and if a PCMCIA card is present, the Metro Ethernet Routing Switch 8600 searches for boot.cfg on the PCMCIA card. If a PCMCIA card is not present, or if boot.cfg is not present on the PCMCIA or not present on the ash, the Metro Ethernet Routing Switch 8600 boots using a default boot-conguration setting.
If you are using a PCMCIA card manufactured by SanDisk, the Metro Ethernet Routing Switch 8600 may not access /pcmcia/boot.cfg during bootup. This limitation occurs only when accessing the SanDisk device after bootup.
Backing up the conguration and boot conguration les

You can use any of the following methods to back up the conguration and boot conguration les. back up using an FTP client back up using TFTP
.
back up using the copy command from ash to PCMCIA
Conguring FTP and TFTP protocols

You must enable the FTP and TFTP boot ag options if you want to use FTP or TFTP for backing up your les. To congure the FTP and TFTP boot ag options: Step 1 Action Enter the following command to check if the FTP and TFTP ag options are enabled:
show bootconfig flags
If the FTP boot ag option is set to false and you want to enable it, enter the following command:
config boot flags ftp true
If the TFTP boot ag option is set to false and you want to enable it, enter the following command:
config boot flags tftp true
If you changed the boot ag options, enter the following command to save the boot conguration le for the changes to take effect.
save bootconfig
End
Backing up using copy

Use the following procedure to back up your conguration les using the copy command. Step 1 Action To verify the conguration le name that you are using, enter the following command. By default, the conguration le name is cong.cfg
show bootconfig choice primary
The following shows sample output for this command: choice primary backup-config-file "" choice primary config-file "/flash/config.cfg" 2 Copy the conguration les using one of the following two methods. For copying les to PCMCIA, ensure that you have a PCMCIA card installed, and then copy the les from ash to PCMCIA
.
23
using the following commands. The default conguration le is cong.cfg.

copy /flash/config.cfg /pcmcia/ copy /flash/boot.cfg /pcmcia/
For copying les to a remote TFTP server, enter the following commands.
copy /flash/config.cfg <tftp server IP address>: config.cfg copy /flash/boot.cfg <tftp server IP address>: boot.cfg
End
Verifying the boot-prom version

This describes verifying current boot-prom version for the ESM 8668 modules. If you are currently operating the switch node with release 3.5.3.x or above, you can skip this section, and proceed to "Upgrading the software image" (page 24). To verify the boot-prom version, enter the following command:
config ESM <slot number> get-imageversion
The system displays the following line items:

ESM Image Name: oe8o3530.dld ESM Software Version: 3.5.3.2OE012 ESM Boot PROM Version: 3.5.3.0OE ESM FPGA version: 16 ESM Image Build Date: (is the date stamp supplied on the boot prom image)
ESM Image Name is the name of the dld driver, loaded by the ESM module. ESM Software Version is the loaded software version (name and version can be different). ESM Boot PROM Version is the current boot-prom version.
.
CAUTION
If the ESM boot-prom version is blank or if the version shows 3.6.0.0 with no appended "b<XX>" number (XX is any number from 01 to 99), the Metro ESM 8668 boot-prom is not up to date. Contact Customer Support for assistance with upgrading the ESM boot prom.
Verifying the ESM status

When you upgrade the ESM boot-prom, enter the following command to check the ESM state:
config ESM <slot number> status
The following shows sample output for this command.

Current: ESM State: XXXXXXXX
In the above example, state can be any of the following: BOOT PROM UPGRADING the PROM is in the upgrade state. Do not reboot or reset if you see this message. ESM OPERATIONAL the ESM blade is in normal operation state. If this message appears, you can reboot switch or reset ESM blade if required. ESM BOOT the ESM blade is in the boot state and loading the ESM drivers. ESM CONFIG the ESM blade is loading the ESM congurations.
Upgrading the software image

This section describes how to upgrade previous Ethernet Routing Switch 8600 and Metro Ethernet Routing Switch 8600 congurations to Metro Ethernet Routing Switch 8600 software release 4.0.4.3. Before upgrading the switch from Metro Ethernet Routing Switch 8600 release 3.5.1.x to Metro Ethernet Routing Switch 8600 release 4.0.4.3, conrm that the current ESM 8668 boot-prom version is correct. This section includes the following topics: "Upgrading the Metro Ethernet Routing Switch 8600 environment with dual-home rings" (page 25) "Upgrading the software on a non-redundant Metro Ethernet Routing Switch 8600 CPU" (page 25) "Upgrading the software on a redundant CPU for Warm Standby (Non HA)" (page 28) "Upgrading the software on a redundant CPU for Hot Standby (HA)" (page 33) "Upgrading Metro Ethernet Routing Switch 8600 and Ethernet Services Unit for RRP" (page 38)
.
Upgrading the software image 25
"Upgrading the ESM FPGA" (page 39) "Updating Firmware revision on R-series modules" (page 42) "Reformatting the 8692SF Flash from 16 MB to 40 MB" (page 45)
Upgrading the Metro Ethernet Routing Switch 8600 environment with dual-home rings
When upgrading dual-home ring environments, Nortel recommends the following procedure: Upgrade the switch only when dual-home rings are in a normal state (not cut). Avoid any ring cuts during the upgrade process. Do not disable any ring ports during the upgrade. Upgrade the primary dual-home ring switch rst. Wait 60 seconds for the ring to return to normal and trafc to resume properly. Upgrade the secondary dual-home ring switch.
Upgrading the software on a non-redundant Metro Ethernet Routing Switch 8600 CPU
Before upgrading your non-redundant CPU, Nortel recommends that you back up your conguration les as follows: Copy the conguration le currently used by the switch in memory by entering the following command:
save config file /<device>/<config file name>
Copy the conguration le specied by the boot.cfg le by entering the following command:
copy /<device>/<config file name> /<device>/<backup config file name>
where device is ash or PCMCIA. Copy the current boot.cfg le by entering the following command:
copy /<device>/<boot.cfg file name> /<device>/<backup boot.cfg file name>
where device is ash or PCMCIA. If your boot-conguration is congured to support FTP or TFTP, you can use either TFTP or FTP le transfer tools to upload the images to the Metro Ethernet Routing Switch 8600. Refer to your FTP or TFTP application guides on how to upload an image to the Metro Ethernet Routing Switch 8600.
.
The following procedure describes how to upgrade the non-redundant CPU with the new software image from the PCMCIA or from the TFTP server: Step 1 2 Action Download the software image to a TFTP server or to a PCMCIA card. Prior to copying the software images over to the switch ash system, verify ash capacity before proceeding with the next steps. To view the capacity available at the console port, type dir to list all les on the ash. The total capacity, total used, and total free bytes are displayed at the bottom of the directory list. For release 4.0.4.3, Nortel recommends you have a minimum of 12 MB free space to upload les needed for the upgrade procedure. Copy the boot image and the software image to the switch ash le system. a. To copy the boot image and the software image from the PCMCIA card, use the following CLI commands:
copy /pcmcia/oe8b4043.img /flash/oe8b4043.img copy /pcmcia/oe8a4043.img /flash/oe8a4043.img copy /pcmcia/oe8o4043.dld /flash/oe8o4043.dld copy /pcmcia/oe8j4043.dld /flash/oe8j4043.dld
b. To copy the boot image and the software image from the TFTP server, use the following CLI commands:
copy <tftpserver IP address>:oe8b4043.img /flash/oe8b4043.img copy <tftpserver IP address>:oe8a4043.img /flash/oe8a4043.img copy <tftpserver IP address>:oe8o4043.dld /flash/oe8o4043.dld copy /<tftpserver IP address>:oe8a4043.dld /flash/oe8a4043.dld copy /<tftpserver IP address>/oe8j4043.dld /flash/oe8j4043.dld
The boot-monitor image, oe8b4043.img, is required only during the initial upgrade procedure. If you have a server available, you can use the option to boot this image from the TFTP server in step 7 instead of copying the image to ash. 4 Verify that the software has been copied to the CPU by using the CLI command:
dir
.
Use the following command to change the primary application image for the switch:
config bootconfig choice primary image-file /<location>/filename
For example, use the following command to change the primary image le to oe8a4043.img:
config bootconfig choice primary image-file /flash/ oe8a4043.img
Save the boot conguration le using the following command:

save bootconfig
Boot the switch with the boot-monitor image you downloaded previously in step 3:
boot <source>:<absolute path of boot monitor image>
For example, enter the following command to boot the oe8b4043.img le from ash:
boot /flash/oe8b4043.img
Alternatively, when the software image is stored on the TFTP server:

boot <tftp-server IP address>:oe8b4043.img
The screen displays the following message:

WARNING: You are about to reprogram your Boot Monitor FLASH image. Do NOT turn off power or press reset until this procedure is completed. Otherwise the card may be permanently damaged!!!
After the bootprom upgrade is complete, the CPU/SF that was upgraded now reboots. If the primary image-le is correct, the switch boots the new 4.0.4.3 software image, and the default banner now displays the upgraded software release as 4.0.4.3.
**************************************** * Copyright (c) 2006 Nortel, Inc. * All Rights Reserved * Nortel Metro Ethernet Routing 8600 Switch 8006 * Software Release REL4.0.4.3OE (Released-General Availability) *****************************************
If the CPU is not running the new software version, you must either repeat the procedure if the CPU allows you to log in, or access the console port on the CPU to stop at the boot monitor and x the problem. Most common failures are caused by improperly typing the image le name in the bootcong le or by the software not being present on the ash on the CPU.
.
Using the console port to stop at the boot monitor enables you to re-enter the bootcong choice primary information, if improperly typed, and enables you to verify that the software is present on the ash of the standby CPU. If the software is not present on the CPU, copy it from PCMCIA card to the CPU. Then, you can either copy it to the ash or change the bootcong choice primary to use the PCMCIA card. 8 After the completion of the upgrade, save the boot.cfg le to ash using the following save command:
save bootconfig
Bootcong commands can change between releases; to capture the correct commands, Nortel recommends that you save the bootcong and reboot after every upgrade to capture the new enhancements. The conguration le generated with Metro Ethernet Routing Switch 8600 software release 4.0.4.3 contains options that are not backward compatible with software release 3.5.x or 3.6.x. Loading a 4.0.4.3 conguration le on a 3.5.x or 3.6.x run-time image generates errors and causes the image to abort loading the conguration le. End
Upgrading the software on a redundant CPU for Warm Standby (Non HA)
The Metro Ethernet Routing Switch 8600 supports HA CPU mode in Release 4.0.4.3. However, releases prior to 4.0.2.0 do not support HA CPU. To upgrade from a release prior to 4.0.2.0 and enable High Availability (HA) mode, use the following procedure to upgrade both the primary and standby CPUs and activate HA CPU during the upgrade.
ATTENTION
If you are upgrading from 4.0.2.x to 4.0.4.3 and have HA enabled, go to "Upgrading the software on a redundant CPU for Hot Standby (HA)" (page 33).
The following procedure describes how to upgrade a redundant Metro Ethernet Routing Switch 8600 CPU conguration and how to enable HA mode. Step 1 Action Connect to the master CPU of the Ethernet Routing Switch 8600 CLI interface using the management console port, telnet session, or Device Manager. Before you upgrade the software, use the following command to make a backup copy of the switch conguration le:
.
copy /flash/config.cfg /<device>/config_backup.cfg copy /flash/config.cfg <tftpaddress>:config_backup.cfg
where device can be PCMCIA or ash, as in the following examples:

copy /flash/config.cfg /pcmcia/config_backup.cfg copy /flash/config.cfg a.b.c.d:config_backup.cfg
When installing les on the onboard ash or PCMCIA, be sure to verify ash capacity before downloading the les. 3 Before you upload the Release 4.0.4.3 image les, use the dir command to ensure that you have the available space. The output is the following:
total: 16039936 used: 6825539 free: 9214397 bytes
ATTENTION
A minimum disk space of 12 megabytes is required for the following les needed for this upgrade:
oe8b4043.img oe8a4043.img oe8o4043.dld oe8j4043.dld
To remove les, use the following remove command:

rm /flash/<filename>
Use one of the following methods to copy the les: a. For TFTP using CLI, ensure that the TFTP server is operating, then enter the following commands:
copy <tftp IP address>:oe8b4043.img /flash/ copy <tftp IP address>:oe8a4043.img /flash/ copy <tftp IP address>:oe8o4043.dld /flash/ *copy <tftp IP address>:oe8j4043.dld /flash/ **copy <tftp IP address>:oe8m4043.img /flash/ ***copy <tftp IP address>:p80c4043.des /flash/ ***copy <tftp IP address>:p80c4043.img /flash/
* This le is required if your switch has R modules. ** This le is required if you have the optional CPU mezzanine onboard daughter card in the switch. *** This le is required for SNMPv3 and SSH encryption.
.
b. For TFTP using Device Manager, ensure that your TFTP server is operating, then select Edit > File System > Copy File. Perform this task for each le name. The File System > Copy File page opens. To copy les: In the Source text box, enter the source le. In the Destination text box, enter the destination le. Select Start. Click Apply. The Result section displays a message saying InProgress. Click Refresh to get the nal result.
c. For FTP, using an FTP client, connect to the management IP address of the master CPU and transfer the required les to ash. Ensure that the FTP boot ag option is enabled. For information about enabling the FTP ag, see "Backing up the conguration and boot conguration les" (page 21). 6 Use one of the following methods to conrm that the software les are copied to ash: a. Using the CLI, enter the dir command. b. Using Device Manager, select Edit > File System and click the Flash Files tab. 7 Before you copy the 4.0.4.3 image les, enter the following command to log into the standby CPU.
peer telnet
8 9
Use the dir command to ensure that you have the minimum available space of 12 MBs. To remove les, use the following remove command:
10
Log out.
ATTENTION
The login prompt should now be on the primary CPU.
11
Use one of the following methods to copy the image les from the master CPU/SF to the standby CPU/SF. Note that the address of CPU slot 5 is 127.0.0.5 and the address of CPU slot 6 is 127.0.0.6.
.
a. For TFTP using the CLI, copy the following les:

copy <tftp IP address>:oe8b4043.img /flash/ copy <tftp IP address>:oe8a4043.img /flash/ copy <tftp IP address>:oe8o4043.dld /flash/ copy <tftp IP address>:oe8j4043.dld /flash/ **copy <tftp IP address>:oe8m4043.img /flash/ ***copy <tftp IP address>:p80c4043.des /flash/ ***copy <tftp IP address>:p80c4043.img /flash/
* This le is required if your switch has R modules. ** This le is required if you installed the optional CPU mezzanine onboard daughter card in the switch. *** This le is required for SNMPv3 and SSH encryption. b. For TFTP using Device Manager, ensure that your TFTP server is operating, then select Edit > File System > Copy File. Perform this task for each le name. The File System > Copy File page opens. To copy les: In the Source text box, enter the source le. In the Destination text box, enter the destination le. Select Start. Click Apply.
The Result section displays a message saying InProgress. Click Refresh to get the nal result. c. For FTP, using an FTP client, connect to the management IP address (not internal IP address of 127.0.0.x) of the standby CPU and transfer the required les to ash. Ensure that the FTP boot ag option is enabled. For information about enabling the FTP ag, see "Backing up the conguration and boot conguration les" (page 21). 12 If you are upgrading from a release prior to 4.0.2.0 and want to enable HA mode, enter the following command, otherwise proceed with the next step. The standby CPU will automatically be rebooted after this step.
config bootconfig flags ha-cpu true The config file on the Master will be overwritten with the current active configuration
.
Do you wish to continue (y/n) y Save bootconfig to file boot.cfg successful. Save config to file /flash/config.cfg successful. You need to reset the master for the changes to take effect. Layer 2 features, ARP and static route will be enabled in L2/L3 redundancy mode. Boot configuration is being saved on both master and standby. config being saved to master and slave
13
Use one of the following methods to update the boot conguration le with the new 4.0.4.3 run-time image. a. Using the CLI, enter the following command:
config bootconfig choice primary image-file /flash/oe8a4043.img
b. Using Device Manager, right-click the 8691 or 8692 CPU/SF, select Edit and click the Boot tab. The Edit > Boot page opens. In the PrimaryImageSource text box, enter the path and lename of the primary run-time image (oe8a4043.img). Click Apply. 14 Use one of the following methods to save the boot conguration on both the master and the standby CPU: a. Using the CLI, enter the following command:
save bootconfig standby boot.cfg
b. Using Device Manager, select Edit> Chassis > System. 15 Click saveBootCong. Click Apply. Click SaveSlaveBootcong. Click Apply.
Enter the following command to verify that the changed primary image le settings are in the boot.cfg le:
more boot.cfg
16
Enter the following command to log into the standby CPU:

peer telnet

.
17
more boot.cfg
18
Enter the following command to boot the standby CPU with the new boot monitor image:
ATTENTION
While booting the standby CPU/SF, the telnet session hangs and needs to timeout. To quickly exit the peer telnet session, enter CTRL and the right-bracket character (]) at the same time. Next, enter q when prompted with the telnet prompt.
For Warm Standby (Non HA), you must wait for the standby CPU/SF to completely boot and come back online. 19 Enter the following command to upgrade the master CPU/SF with the new boot monitor image after the standby CPU/SF has completed booting.
CAUTION
This step causes an interruption to user trafc.
End
Upgrading the software on a redundant CPU for Hot Standby (HA)

The following procedure describes how to upgrade a redundant Metro Ethernet Routing Switch 8600 CPU conguration operating in High Availability (HA) mode. Step 1 Action Connect to the master CPU of the Ethernet Routing Switch 8600 CLI interface using the management console port, telnet session, or Device Manager. Before you upgrade the software, use the following command to make a backup copy of the switch conguration le:
copy /flash/config.cfg /<device>/config_backup.cfg
.
copy /flash/config.cfg <tftpaddress>:config_backup.cfg
where device can be PCMCIA or ash, as in the following examples:

copy /flash/config.cfg /pcmcia/config_backup.cfg copy /flash/config.cfg a.b.c.d:config_backup.cfg
When installing les on the onboard ash or PCMCIA, be sure to verify ash capacity before downloading the les. 3 Before you upload the Release 4.0.4.3 image les, use the dir command to ensure that you have the available space. The output is the following:
total: 16039936 used: 6825539 free: 9214397 bytes
ATTENTION
A minimum disk space of 12 megabytes is required for the following les needed for this upgrade:
oe8b4043.img oe8a4043.img oe8o4043.dld oe8j4043.dld
To remove les, use the following remove command:

Use one of the following methods to copy the les: a. For TFTP using CLI, ensure that the TFTP server is operating, then enter the following commands:
copy <tftp IP address>:oe8b4043.img /flash/ copy <tftp IP address>:oe8a4043.img /flash/ copy <tftp IP address>:oe8o4043.dld /flash/ *copy <tftp IP address>:oe8j4043.dld /flash/ **copy <tftp IP address>:oe8m4043.img /flash/ ***copy <tftp IP address>:p80c4043.des /flash/ ***copy <tftp IP address>:p80c4043.img /flash/
* This le is required if your switch has R modules. ** This le is required if you have the optional CPU mezzanine onboard daughter card in the switch. *** This le is required for SNMPv3 and SSH encryption.
.
b. For TFTP using Device Manager, ensure that your TFTP server is operating, then select Edit > File System > Copy File. Perform this task for each le name. The File System > Copy File page opens. To copy les: In the Source text box, enter the source le. In the Destination text box, enter the destination le. Select Start. Click Apply. The Result section displays a message saying InProgress. Click Refresh to get the nal result.
c. For FTP, using an FTP client, connect to the management IP address of the master CPU and transfer the required les to ash. Ensure that the FTP boot ag option is enabled. For information about enabling the FTP ag, see "Backing up the conguration and boot conguration les" (page 21). 6 Use one of the following methods to conrm that the software les are copied to ash: a. Using the CLI, enter the dir command. b. Using Device Manager, select Edit > File System and click the Flash Files tab. 7 Before you copy the 4.0.4.3 image les, enter the following command to log into the standby CPU.
peer telnet
8 9
Use the dir command to ensure that you have the minimum available space of 12 MBs. To remove les, use the following remove command:
10
Log out.
ATTENTION
The logon prompt should now be on the primary CPU.
11
Use one of the following methods to copy the image les from the master CPU/SF to the standby CPU/SF. Note that the address of CPU slot 5 is 127.0.0.5 and the address of CPU slot 6 is 127.0.0.6.
.
a. For TFTP using the CLI, copy the following les:

copy <tftp IP address>:oe8b4043.img /flash/ copy <tftp IP address>:oe8a4043.img /flash/ copy <tftp IP address>:oe8o4043.dld /flash/ copy <tftp IP address>:oe8j4043.dld /flash/ **copy <tftp IP address>:oe8m4043.img /flash/ ***copy <tftp IP address>:p80c4043.des /flash/ ***copy <tftp IP address>:p80c4043.img /flash/
* This le is required if your switch has R modules. ** This le is required if you installed the optional CPU mezzanine onboard daughter card in the switch. *** This le is required for SNMPv3 and SSH encryption. b. For TFTP using Device Manager, ensure that your TFTP server is operating, then select Edit > File System > Copy File. Perform this task for each le name. The File System > Copy File page opens. To copy les: In the Source text box, enter the source le. In the Destination text box, enter the destination le. Select Start. Click Apply. The Result section displays a message saying InProgress. Click Refresh to get the nal result.
c. For FTP, using an FTP client, connect to the management IP address (not internal IP address of 127.0.0.x) of the standby CPU and transfer the required les to ash. Ensure that the FTP boot ag option is enabled. For information about enabling the FTP ag, see "Backing up the conguration and boot conguration les" (page 21). 12 Use one of the following methods to update the boot conguration le with the new 4.0.4.3 run-time image. a. Using the CLI, enter the following command:
b. Using Device Manager, right-click the 8691 or 8692 CPU/SF, select Edit and click the Boot tab.
.
The Edit > Boot page opens. In the PrimaryImageSource text box, enter the path and lename of the primary run-time image (oe8a4043.img). Click Apply. 13 From the primary CPU, change your bootcong choice primary image le to the new run-time image le using the following CLI command:
14
Use one of the following methods to save the boot conguration on both the master and the standby CPU: a. Using the CLI, enter the following command:
save bootconfig standby boot.cfg
b. Using Device Manager, select Edit> Chassis > System. 15 Click saveBootCong. Click Apply. Click SaveSlaveBootcong. Click Apply.
more boot.cfg
16
Enter the following command to log into the standby CPU:

peer telnet
17
more boot.cfg
18
Enter the following command to boot the standby CPU with the new boot monitor image. For Hot Standby, you must boot the standby and master CPUs using the following sequence: Reboot the standby CPU/SF. Wait 10 seconds. Reboot the master CPU/SF before the standby CPU/SF completes booting.
.
ATTENTION
While booting the standby CPU/SF, the telnet session hangs and needs to timeout. To quickly exit the peer telnet session, enter CTRL and the right-bracket character (]) at the same time. Next, enter q when prompted with the telnet prompt.
19
Enter the following command to upgrade the master CPU/SF with the new boot monitor image.
ATTENTION
This step causes an interruption to user trafc. boot /flash/oe8b4043.img
End
Upgrading Metro Ethernet Routing Switch 8600 and Ethernet Services Unit for RRP
The supported Ethernet Services Unit images include a new Enhanced Ring Resiliency feature to provide additional ring protection above the current Layer 1 mechanism. This new protocol monitors and detects isolated failures not seen at the physical layer. For more information, see Conguring the Metro Ethernet Routing Switch 8600 using the CLI (320746-A). To upgrade ESUs attached to the Metro Ethernet Routing Switch 8600 and to activate the Enhanced Resiliency Protocol in an existing Metro Ethernet Routing Switch 8600 environment, Nortel recommends using the following procedure: Upgrade the Metro Ethernet Routing Switch 8600 to Release 4.0.4.3. For information, see "Upgrading the software image" (page 24). Upgrade all ESU 1800s and ESU 1850s to the latest supported release (see "Supported ESU images with Metro Ethernet Routing Switch 8600 Release 4.0.4.0" (page 11)). For more information on ESU upgrades and supported features, see Release Notes for the Metro Ethernet Services Unit 1800 (317812-G) and Release Notes for the Metro Ethernet Services Unit 1850 (320416-F). Enable RRP features on all ESUs. For the ESU 1800, see Conguring Ethernet VPN and IP VLAN Services in ESU 1800 using the CLI (321766-A). For the ESU 1850, see Conguring Ethernet VPN and IP VLAN Services in ESU 1850 using the CLI (321258-A).
.
Start conguring with the rst ESU in the ring. Nortel recommends this process, but the order of which ESU to congure rst is not important. Enable the RRP feature on each ESU to ensure that no ESUs are missed.
If you upgrade the ESU prior to upgrading the Metro Ethernet Routing Switch 8600, VPLS broadcast issues may occur after the rst ESU is upgraded. To resolve the broadcast condition, ush the TDI MAC table for all TDIs assigned to the ring (config tdi <id> flush-mac).
Upgrading the ESM FPGA

The ESM 8668 may require a Field Programmable Gate Array (FPGA) rmware revision upgrade. Nortel recommends that all ESM 8668 modules be upgraded to the latest rmware FPGA image when using 8692omSF or 8692SF CPUs. The upgrade is optional if you are using the 8691 CPU. It is mandatory for chassis with multiple ESM 8668 modules to operate with the same FPGA rmware revision (mixed rmware revisions are not supported). The FPGA upgrade process requires approximately 57 minutes to complete. The ESM card needs to be power cycled by either power cycling the chassis or reseating the ESM card to activate the new FPGA. Nortel recommends doing the FPGA upgrade during a maintenance window. There should not be a signicant amount of trafc running through the ESM card during the upgrade process. Use the following steps to upgrade the FPGA rmware: Step 1 Action Use one of the following CLI commands to determine the ESM FPGA (CPLD) version. If the ESM FPGA version is 18, no upgrade is required. If the ESM FPGA version is a different version and a 8692omSF or 8692SF CPU is in use, you need to upgrade the FPGA.
config esm <slot #> get-imageversion
or
show config module diag
The following is an example of getting the version of an ESM module in slot 2:

MERS 8600:5# config esm 2 get-imageversion ESM ESM ESM ESM Image name: oe8o4000.dld Software Version: 4.0.0.0OE020 Boot PROM Version: 3.5.3.0OE FPGA Version: 18
.
ESM Image build date:
Jul 7 2005
The ESM modules require loading an I/O dld image le onto each module. By default, this le is named oe8o4002.dld and is loaded automatically. If you plan to rename this le, you must enter the following command for each ESM slot in the boot.cfg conguration le:
bootp image-name /flash/newoname.dld <slot-number>
The following is an example for the ESM module in slot 2:

MERS 8600:5# bootconfig bootp image-name /flash/oe8o40 02.dld 2 MERS 8600:5# save bootconfig
If an update is needed, copy the latest ESM dld (oe8o4043.dld) on the ash or PCMCIA and make it the default dld image for the slot. To make the o dld image the default dld image, the a image of the same code version must be set as the primary image le in the boot cong. Under normal circumstances, the Metro Ethernet Routing Switch 8600 is already upgraded to the latest revision of the code.
To start the FPGA upgrade process, enter the command:

config esm <slot-number> fpga-upgrade
The following is an example of starting the upgrade process for an ESM FPGA in slot 7.
CAUTION
Do not reset the chassis or the ESM cards during the upgrade process. A reset permanently damages the ESM card. A warning message is displayed as shown in the following example. MERS 8600:5# config esm 7 fpga-upgrade ################ ESM(Slot:7) FPGA Upgrade ################## WARNING: You are about to re-program this ESMs Water Works FPGA Do NOT turn off power, press reset or pull out the card until this procedure is completed. Otherwise the card may be permanently damaged Do you want to continue (y/n) ? MERS 8600:5# boot FPGA Upgrade in progress on one or more ESMs.Wish to Continue (y/n) ? n y
.
MERS 8600:5# reset FPGA Upgrade in progress on one or more ESMs.Wish to Continue (y/n) ? n MERS 8600# config esm 7 reset Are you sure you want to reset the ESM card(s) (y/n) ? y FPGA Upgrade in progress on ESM card in Slot 7. to Continue (y/n) ? n Wish
If multiple ESM cards exist in the same chassis, you can run simultaneous FPGA upgrades for the different ESM cards. Repeat the command for each slot where there is an ESM card. 4 After successfully starting the FPGA upgrade for each slot, both the ESM console and the CP console display informational FPGA upgrade messages. A message is displayed when the upgrade process is complete.
FPGA is being Re-Programmed, Please wait for Upgrade Complete Indication... MERS 8600:5# CPU5 [12/08/05 16:25:15] ESM INFO FPGA Upgrade initiated for ESM card on slot 7
If you use the command show log file tail, you can see in the log le that the FPGA was updated:
MERS 8600:5# show log file tail CPU5 [12/08/05 16:25:23] ESM INFO FPGA Upgrade initiated for ESM card on slot 8 Successfully Re-Programmed Water Works FPGA!
When the upgrade is complete, power cycle the chassis or reseat the ESM card to activate the new FPGA. If you do not power cycle the chassis or reseat the ESM card, the new FPGA image does not take effect. Neither a soft reset of the card nor the CLI boot command successfully upgrades the FPGA. After a successful upgrade, the ESM FPGA (CPLD) revision number is 18. To view the revision number and verify the upgrade was successful, use one of the following commands:
show config module diag
or
show esm <slot #> get-imageversion
The entire upgrade process takes approximately 57 minutes to complete. If multiple cards are upgraded simultaneously, the upgrade time is the same for each card; the time is not cumulative.
.
End
Updating Firmware revision on R-series modules

A new Fabric Output Queue (FOQ) Field Programmable Gate Array (FPGA) rmware (version 267) is available with this release. This new rmware revision resolves a potential issue which existed since the initial release of the 8648GTR module, Release 4.0.1. Note that the two other FPGA devices, BMC and DPC, are unchanged. This issue happens only in some heavily congested networks where a backpressure message has to be sent at ingress using the FOQ. Although this issue is specic to the 8648GTR module, since the FOQ device is on the base board of all R modules, you should review and update rmware revisions on every R module for consistency. The FOQ update is not required if you are not using an 8648GTR module or if you dont expect to encounter high congestion. To verify the revision, see "Verifying rmware revisions on R modules 8630GBR, 8683XLR, 8683XZR, and 8648GTR" (page 42). To update the revision, see "Updating rmware revisions on R modules 8630GBR, 8683XLR, 8683XZR, and 8648GTR" (page 43).
Verifying rmware revisions on R modules 8630GBR, 8683XLR, 8683XZR, and 8648GTR

The following devices on the R module baseboard require updates to their rmware and, if required, to their release revisions shown in "Device and Firmware R Module decimal values" (page 42).
Device and Firmware R Module decimal values Device FOQ DPC BMC Firmware Revision 267 184 776 Current filenames foq267.xsvf dpc184.xsvf bmc776.xsvf
Due to the le creation tool, new versions of the rmware les are the same size as previous versions. The new FOQ le is backward compatible with 4.0.x releases.
.
ATTENTION
You can only update the rmware for one FPGA device on an R module at a time. For example, you must complete the update for the FOQ before you can update the BMC or DPC on the same R module.
Enter the following show command to check the current rmware revisions on the slot containing an R module. The following example displays rmware requiring an update. MERS-8610:5# show sys info asic # Asic Info: # SlotNum Name |CardType |MdaType |Parts Description # # Slot 1 -0x00000001 0x00000000 # Slot 1 8630GBR 0x2432511e 0x00000000 RSP=0 CLUE=0 F2I=0 F2E=0 FTMUX=0 CC=3 FOQ= 260 DPC= 180 BMC= 770 MAC=4 If the rmware revisions are not equivalent to those in "Device and Firmware R Module decimal values" (page 42), an update is required, otherwise no further action is necessary.
Updating rmware revisions on R modules 8630GBR, 8683XLR, 8683XZR, and 8648GTR ATTENTION
Nortel strongly recommends that you use a direct console cable connection to upgrade the FPGA.
To update rmware revisions: Step 1 2 3 Action Ensure that Release 4.0.4.3 is operating on the system. Disable all ports on the module to upgrade. Using TFTP or FTP, copy the les to the 8692omSF ash on the Ethernet Routing Swich 8000 Series chassis that contain the R module you are updating. You can also complete this upgrade with the les on a PCMCIA card. 4 Enter the following command for the device type and slot-number containing an R module that needs updating. Repeat the command for each additional device type on an R module that needs updating.
.
You can only update the rmware for one FPGA device on an R module at a time. For example, you must complete the update for the FOQ before you can update the BMC or DPC on the same R module. Do not open several Telnet or SSH sessions and try to update several device types simultaneously.
ATTENTION
Once the update process begins, do not enter commands or reset the module or switch during the process. If any failure occurs, retry the updates or contact Nortel before resetting the module or switch.
Do not interrupt the update process, which is approximately ten minutes in length. Wait until the FPGA UPDATE SUCCESS message displays for each slot you are updating. The success message is appended to the log le. Do not save the conguration le once the upgrade has started or before the switch reboots. If you do not enter a le name, then the default le name foq.xsvf, bmc.xsvf, or dpc.xsvf is displayed. MERS-8610:5# config diag fpga foq update <slot> <file-name> MERS-8610:5# config diag fpga bmc update <slot> <file-name> MERS-8610:5# config diag fpga dpc update <slot> <file-name>
Starting the update Process, will take a few minutes Dont reset the card or box during the process A SUCCESS message will display on the console and will get appended to the log file upon completion of the update. MERS-8610:5# CPU5 [02/08/05 18:55:31] SW ERROR R-Module Slot<1> is unable to Process Async messages and Slot Reset is Disabled!! MERS-8610:5# CPU5 [04/12/05 14:05:38] COP-SW INFO Slot 1: FPGA UPDATE SUCCESS
ATTENTION
Disregard the message SW ERROR unable to Process Async messages and Slot Reset is Disabled!! The message disappears after the system reboot.
Note that the show sys info asic command does not display updated rmware revisions until after you reboot. 5 Once all the modules have been updated, enter the following command to reboot the system for the updates to take effect.
.
MERS-8610:5# boot -y End
When the system reboots, the rmware revision is veried and if an update is required, a warning message displays on the console:
CPU5 [04/01/06 23:06:00] SW WARNING Slot 7 is running older software version(s) of FPGA. Please upgrade to the latest version(s) CPU5 [04/01/06 23:06:00] SW WARNING FOQ FPGA current revision: 266. Upgrade to the latest revision: 267
If you see this warning message, choose one of the following options: Disregard the above warning message and do not upgrade the FOQ FPGA. Perform the FPGA upgrade on your R modules. See "Updating Firmware revision on R-series modules" (page 42).
Reformatting the 8692SF Flash from 16 MB to 40 MB

The following sections describe how to upgrade from 16 MB to 40 MB and also to downgrade from 40 MB to 16 MB.
Reformatting from 16 MB to 40 MB
Complete the following procedure to upgrade from 16 MB to 40 MB ash: Step 1 2 Action Complete the upgrade procedure in "Upgrading the software image" (page 24). Connect to the master CPU of the Ethernet Routing Switch 8600 CLI interface using the management console port, telnet session, or Device Manager. Enter the following command to connect to the standby CPU.
peer telnet
Enter the following command to back up all les to the PCMCIA card.
copy /flash/<src-file> /pcmcia/<dest-file>
Enter the following command to reformat the ash on the standby CPU/SF.
format-flash
Reboot the standby CPU/SF.


.
boot /pcmcia/0e8a4043.img
ATTENTION
While booting the standby CPU/SF, the Telnet session hangs and needs to timeout. To quickly exit the peer Telnet session, enter CTRL and the right-bracket character (]) at the same time. Next, enter q when prompted with the Telnet prompt.
After the standby CPU/SF is active again, enter the following command to connect to the standby CPU.
peer telnet
Enter the following command to copy all les back from the PCMCIA card to ash.
copy /pcmcia/<src-file> /flash/<dest-file>
Boot the system to activate the new conguration and image les.
boot -y
10
Enter the following command to connect to the standby CPU.

peer telnet
11 12
Conrm that the CPU is operational. Enter the following command to verify that the changed primary image les and conguration le settings are in the boot.cfg le:
more boot.cfg
13 14
Log out of the standby CPU. Enter the following command to back up all les to the PCMCIA card.
copy /flash/<src-file> /pcmcia/<dest-file>
15
Enter the following command to reformat the ash on the primary CPU/SF.
format-flash
16
Reboot the primary CPU/SF.

boot /pcmcia/0e8a4043.img
CAUTION
This step causes an interruption in trafc.
.
17
After the primary CPU is active again, enter the following command to copy all les back from the PCMCIA card to ash.
copy /pcmcia/<src-file> /flash/<dest-file>
18
Boot the system to activate the new conguration and image les.
boot -y
End
Downgrading from 40 MB to 16 MB
To downgrade from 40 MB to 16 MB, use the following procedure: Step 1 2 Action Copy your les from the ash to the PCMCIA card or a TFTP/FTP server. Downgrade the boot monitor with an earlier release of the software.
CAUTION
Do not use a software image prior to Metro 8600 Release 3.6.0.0 with the 8692omSF module. If you downgrade the software (specically the boot monitor image, oe8b3600.img) to a previous release (Release 3.5.3.2 or earlier), it may be necessary to return the module to Nortel due to boot ash corruption.
3 4 5
Format the ash, using the command format-flash. boot /pcmcia/0e8b4043.img boot /pcmcia/0e8a4043.img When the switch comes back up, the 16 MB ash is now available to you.
Copy all les from the PCMCIA card or TFTP/TFP server to which you copied them in step 1 back to your ash. End
.
New feature enhancements and changes

Enhanced CLI commands
You can now search for MAC entries even when the TDI on which the endpoint belongs is unknown. This section has the following enhanced CLI commands: "Showing information from the endpoint MAC address table" (page 48) "Showing TDI endpoint information" (page 50)
Showing information from the endpoint MAC address table

You can now show a wide variety of information from the MAC address table using the dump endpoint-mac-table command. You can specify a number of different tables (TLS port, ESM UNI, ring port, and standalone port) and sorting using a variety of options (TDI ID, UNI, qtag, outer qtag, and MAC address). To view this information, use the following command:
dump endpoint-mac-table
The dump endpoint-mac-table command has the following options:

dump endpoint-mac-tablefollowed by: all info [tdi <value>] [uni <value>] [mac <value>] [qtag <value>] [outer-qtag <value>] Displays all TDI and UNI information. Displays specified TDI and UNI information. tdi <value> displays the specified TDI as an integer between 1 and 16777215. uni <value> displays the UNI specified in the format of a.b.c.d. mac <value> displays the MAC address in hexadecimal format 0x00:0x00:0x00:0x00:0x00:0x00. qtag <value> displays the qtag specified as an integer range between 1 to 4093. outer-qtag <value> displays the outer qtag specified as an integer range between 1 to 4093.
.
New feature enhancements and changes
49
port <port> [tdi <value>] [mac <value>] [qtag <value>] [outer-qtag <value>]
Allows port-based search. port is the ring port in the format of slot/port number. tdi <value> displays the specified TDI as an integer between 1 and 16777215. mac <value> displays the MAC address in hexadecimal format 0x00:0x00:0x00:0x00:0x00:0x00. qtag <value> displays the qtag specified as an integer range between 1 to 4093. outer-qtag <value> displays the outer qtag specified as an integer range between 1 to 4093.
ring-mod-port <ring_id> mod-id <value> port-id <value> [tdi <value>] [mac <value>] [qtag <value>]
Allows ring and port-based search for a ESM UNI. You identify a UNI for a ESU ring by its ring ID, module ID, and the port number on the ESU on which the UNI was created. ring-mod-port <ring_id> is the ESU ring number. mod-id <value> is the module number assigned on the switch as an integer between 1 and 24. port-id <value> is the ESU port number as an integer between 1 to 24 and 28. tdi <value> displays the specified TDI as an integer between 1 and 16777215. mac <value> displays the MAC address in hexadecimal format 0x00:0x00:0x00:0x00:0x00:0x00. qtag <value> displays the qtag specified as an integer range between 1 to 4093.
standalone-esu-port <port> mod-id <value> esu-port-id <value> [tdi <value>] [mac <value>] [qtag <value>]
Allows ring and port-based search for a standalone port. You identify a UNI for a standalone ESU by the ESM port on which the standalone ESU is configured, with the mod-id, and the port number on the SU on which the UNI was created.
.
standalone-esu-port <port> is the standalone port number on the Metro Ethernet Routing Switch 8600 in the format slot/port. mod-id <value> is the module number assigned to the ESU on which the UNI was created. Specify an integer between 1 and 24. esu-port-id <value> is the ESU port number as an integer between 1 to 26 and 28. tdi <value> displays the specified TDI as an integer between 1 and 16777215. mac <value> displays the MAC address in hexadecimal format 0x00:0x00:0x00:0x00:0x00:0x00. qtag <value> displays the qtag specified as an integer range between 1 to 4093.
This command replaces the dump endpoint-mac-table tdi <tdi> [uni <value>] [mac <value>] [qtag <value>] command, which is now obsolete.
Showing TDI endpoint information

You can now view more TDI endpoint information by specifying a TDI, qtag, outer qtag, or endpoint name, using the following command:
show tdi end-point config info end-point [<ipaddr>] [tdi <value>] [qtag <value>] [outer-qtag <value>] [name <value>] [detail]
where ipaddr is the UNI ID in the format a.b.c.d. tdi <value> is the TDI ID as an integer between 1 and 16777215. qtag <value> is the qtag value as an integer between 1 to 4093. outer-qtag <value> is the outer qtag value as an integer between 1 to 4093. name <value> is the endpoint name as a string length of 1 to 30 characters.
.
Supported standards, RFCs, and MIBs 51
detail shows all the endpoint information in detail.
This command replaces the show tdi end-point config info end-point [<ipaddr>] [tdi <value>] [name <value>] [detail] command, which is now obsolete.
Hardware Support
There is no new hardware support for release 4.0.4.3.
Supported standards, RFCs, and MIBs

This section identies the 802 standards, RFCs, and network management MIBs supported in this release. "Supported standards" (page 51) lists the supported standards.
Supported standards Supported standards 802.3 CSMA/CD Ethernet 802.3i 10BaseT 802.3u 100BaseT 802.3z 802.3ab 802.3ae 802.1Q and 802.1p 802.3x 802.1D ISO/IEC 8802-3 ISO/IEC 8802-3 ISO/IEC 8802-3 Gigabit Ethernet Gigabit Ethernet 1000BaseT 4 pair Cat5 UTP 10 Gigabit Ethernet VLAN tagging and prioritization Flow Control MAC bridges/spanning tree protocol
"Supported protocol RFCs" (page 51) lists the protocol RFCs supported in this release.
Supported protocol RFCs Supported protocol RFCs RFC 768 RFC 783 RFC 791 RFC 792 RFC 793 RFC 826 UDP protocol TFTP protocol IP protocol IGMP TCP protocol ARP protocol
.
Supported protocol RFCs RFC 854 RFC 903 RFC 1541 and 1542 RFC 1542 RFC 1112 RFC 2236 RFC 3376 draft-holbrook-idmr-igmpv3-ssm02.txt RFC 2178 RFC 2131 RFC 2338 RFC 2362 RFC 3569 (draft-ietf-ssm-arch-0 3.txt) RFC 2474 and 2475 RFC 2597 and 2598 RFC 2138 RFC 2139 RFC 1591 Telnet protocol Reverse ARP BootP and DHCP BootP IGMPv1 IGMPv2 IGMPv3 IGMPv3 for SSM OSPFv2 Dynamic Host Control Protocol (DHCP) Virtual Router Redundancy Protocol PIM-SM PIM-SSM DiffServ DiffServ per hop behavior RADIUS Authentication RADIUS Accounting DNS Client
"Supported network management MIBs" (page 52) lists the network management MIBs and standards supported in this release.
Supported network management MIBs Supported MIBs RFC 1155.mib RFC 1157.mib RFC1213.mib RFC 1215.mib RFC 1493.mib RFC 1573.mib RFC 1643.mib SMI MIB SNMP MIB MIB for networks management of TCP/IP-based internets MIB2 A convention for defining traps for use with the SNMP Definitions of management objects for bridges Interface MIB Definitions of managed objects for the Ethernet-like interface types
.
General conguration issues and considerations 53
Supported MIBs RFC 1757.mib RFC 1389.mib RFC 1907.mib RFC 2021.mib RFC 2096.mib RFC 2233.mib RFC 2674.mib Remote network monitoring MIB (support of alarms, events, statistics, and history groups) OSPFv2 MIB SNMPv2 MIB RMON MIB (using SMIv2) IP forwarding table MIB The interfaces group MIB using SMIv2 Definitions of management objects for bridges with traffic classes, multicast filtering and virtual LAN extensions IPv4 multicast routing MIB Internet Group Management Protocol MIB PIM MIB SNMPv3 MIB Definitions of Managed Object for bridges with Traffic Classes, Multicast Filtering, and Virtual LAN extensions Ping and Traceroute MIBs
RFC 2932.mib RFC 2933.mib RFC 2934.mib RFC 2571, 2572, 2573, 2574, 2575, 2576 mibs RFC 2674.mib
RFC 2925.mib
General conguration issues and considerations

This section lists general, non-critical system issues that you should be aware of when operating the Metro Ethernet Routing Switch 8600.
Platform
If you remove a PCMCIA card before you complete, or upload, a write operation, the le that is being written to may contain a corrupted EOF marker. Additional attempts to write to this le can generate an error message. To resolve this problem, remove the le created during the upload process, and recreated from the beginning. Some PCMCIA cards do not contain a le attribute table (FAT). Use the CLI command dos-chkdsk /pcmcia to check the card. If you receive error messages, use the dos-chkdsk /pcmcia/ repair command or the dos-format command. When you enter the CLI command boot y, the console displays the error message invalid option "-y" in config/bootconfig and then reboots the Metro Ethernet Routing Switch 8600 chassis. The error message is invalid and has no effect on rebooting the chassis.
.
Previous Nortel Metro Ethernet Routing Switch 8600 release notes incorrectly state that the maximum number of supported VLANs is 1980. The maximum achievable number of VLANs is 1973.
Provider Backbone Transport

Release 4.0.4.3 includes Nortels rst release of Provider Backbone Transport (PBT). As such, you can only use it under controlled availability. For details on release authorization, contact your local account team manager. When creating PBT trunks, you can congure the same MEP-ID on the local and remote MAs. However, if the MEP-IDs are the same, the PBT trunk will remain in a down state as duplicate network identiers are not supported. You should not have duplicate MED-IDs. Currently in the Nortel Metro Ethernet Routing Switch 8600, the console hangs when you source a PBT conguration le (with Ring and Trunk PBT tunnels). Do not source a conguration le using the source command. Currently in the Nortel Metro Ethernet Routing Switch 8600, removing the PBT trunk slot causes all trunks and SGs to bounce. You can resolve this by rst disabling the slot, then removing the module. In the Nortel Metro Ethernet Routing Switch 8600, there are three possible scenarios for disabling a PBT trunk: Administratively disabled primary trunk with no secondary trunk In this case, trafc stops immediately. Administratively disabled primary trunk with a secondary trunk In this case, trafc continues to pass through the primary trunk for 50ms until failover to the secondary trunk completes. Hardware failure such as a faulty ESM module In this case, the port is administratively down and the operation status is up. Trafc continues to pass through the trunk for two minutes during High Availability-CPU switch.
In the Nortel Metro Ethernet Routing Switch 8600, with Maintenance Association (MA) state disabled, the PBT trunk still comes up. You can resolve this issue by deleting MA and recreating it with MA state disabled. Conguring the same trunk with this MA brings the trunk back up without an error message. The MERS 8600 does not support PBT if you congure the chassis spanning tree mode for RSTP or MSTP. You must use the default spanning tree mode (STP) when using PBT services.
.
When conguring PBT-based endpoints with ESU rings, Nortel recommends maintaining the default settings for the following parameters: ccm-interval This parameter sets the time interval for how often CCM messages are sent between endpoints within a Service Group domain. Nortel recommends leaving this setting at the default of 5000 milliseconds. ccm-lifetime This parameter sets the life time before CCM times out within a Service Group domain. Nortel recommends leaving this setting at the default of 150000 milliseconds.
Failover times for PBT trunks vary from 50 ms to 1 second depending on the total number of trunks assigned to a failed port. The greater the number of trunks on a single port, the longer the failover time is. For Release 4.0.4.3, Nortel recommends that you do not use Device Manager for conguring PBT services. This includes maintenance domains, maintenance associations, MEP IDs, and trunk ports. Use the command line interface instead.
High-availability CPU
When using HA-CPU, if the primary CPU is physically removed from the chassis, data trafc failover to the standby CPU may take 3 to 6 seconds, depending on the cong and trafc load. Prior to removing the primary CPU, you should perform a CPU switchover action using the command config sys set action cpuswitchover to activate the standby CPU prior to removing the primary CPU from the chassis. Nortel does not support the use of HA-CPU in a scaled ESM ring and endpoint environment.
ESU rings
In the Nortel Metro Ethernet Routing Switch 8600, when using cust-ip-vlan UNIs, IP multicast packets may be dropped for more than 50 ms upon ring recovery. In congurations with 16 or more rings connected to one Metro Ethernet Routing Switch 8600, you must disable enhanced RRP. However, this only applies to the Metro Ethernet Routing Switch 8600. You can still use enhanced RRP between ESUs on the rings.
VLACP enabled on NNI ports

If you enable spanning tree on ports with VLACP enabled, or if the ports used to transport VLACP messages have spanning tree enabled, the VLACP sessions will be delayed upon recovery of services. After spanning tree completes the convergence cycle, the VLACP session is established.
.
IP static routes
In the Metro Ethernet Routing Switch 8600, IP static routes take precedence over all other learned routes with the same cost, except for Open Shortest Path First (OSPF) learned type 2 routes. The Metro Ethernet Routing Switch 8600 does not allow you to congure a static route, dynamically learned. However, you can add the route in the ASCII conguration, and boot the switch accordingly. The congured static route is then chosen as the route, provided the next hop is available.
IS-IS
If IS-IS is globally disabled, disabling/enabling at the interface level does not take any effect. No informational message displays after IS-IS integration conguration. The Metro Ethernet Routing Switch 8600 JDM does not support the display of informative messages. On the L1 only router, no error message displays when conguring the L2 metric at the interface level. The CLI does not warn the user with an error message, after entering the command <<L2-only-mode>>. In IS-IS, when a router is congured as an L1 router at the global level, the L2 commands at the interface level are hidden but still available for use (i.e. 12-hello-interval, 12-metric). The Metro Ethernet Routing Switch 8600 sets IS-TYPE as L12 in an L1 LSP. The IS_IS TYPE bits are indicating the type of Intermediate System router instead of type of lsp. Nortel recommends that all metrics in the IS-IS network are set to the same metric type. By default, the metric is set to wide. Nortel also recommends that this parameter is left at the default setting. If only one router metric is changed, the IS-IS network may lose a signicant amount of routes. Also, metric changes do not take place dynamically. You must restart IS-IS globally. After selecting IP Routing > ISIS > Summary Address tab > Insert, without adding any conguration parameters, the following error message appears:
isisSummAddrPrefixLen: Unparseable number:
OSPF
When you design your network, consider the following OSPF capabilities: In order to operate the Metro Ethernet Routing Switch 8600 at the published scaling limit, a maximum recommended number of areas per switch is four. In order to operate the Metro Ethernet Routing Switch 8600 at the published scaling limit, a maximum recommended number of adjacencies is 16 per switch.
.
Non-OSPF interfaces build adjacencies with the designated router (DR) and the backup designated router (BDR). DRs and BDRs build adjacencies with all routers on a subnet. There is always a DR and a BDR on a IP subnet running OSPF if there are at least two routers.
When using OSPF on chassis with ESU rings installed, convergence time may increase signicantly if you reduce the ESU ring discovery protocol interval to values below 30 seconds. For networks with more than 1000 routes to redistribute, Nortel recommends maintaining a minimum ESU ring discovery interval of 30 seconds.
CPU SSF management port

You can only disable the management Ethernet port using the Metro Ethernet Routing Switch 8600 console port. You cannot disable the management port using Device Manager because this capability is not supported. The management Ethernet port can communicate only with devices on its local subnet and on up to four statically-congured, remote subnets. The management Ethernet port does not support a default gateway or default route. The remote subnet is congured using the following CLI command, which requires knowledge of the next hop address:
config bootconfig net mgmt route add < a.b.c.d> < w.x.y.z>
For example, if the IP address of the management port is 10.125.2.11 and its next hop is 10.125.2.1, use this command to correctly set up the management port:
config bootconfig net mgmt route add 13.177.76.0 10.125.2.1
Debugging using the trace level command

If you specify the CLI command trace screen on, be cautious when you switch on trace levels. After you add the new Metro Ethernet Routing Switch 8600 software code base and debug messages specic to the new platform, you can encounter various platform-related performance issues that can cause the software to become unstable at certain times.
CPU password synchronization

To synchronize the primary and slave CPU passwords, perform these steps: Step 1 2 Action Change the password on the primary CPU. Save the password by entering the CLI command save config.
.
3 4
Enter the CLI command save config file config.cfg standby. Go to the slave CPU, and change the password by entering the CLI command:
config cli password rwa <username> [<password>]
End
Metro ESM 8668

This section describes the following topics: "Unused module removal" (page 58) "Hot-swap and module insertion" (page 58) "Ring ports" (page 58)
Unused module removal

Minor packet loss can occur when you remove unused Metro ESM 8668 modules, or standby CPUs, from the chassis. The packet loss occurs only during the instance of the module removal.
Hot-swap and module insertion

If you need to remove a Metro ESM 8668 module, it is highly recommended that you rst disable the slot before removal by using the CLI command conf slot # state dis. If the module is active when removed, ring failover times may be longer than expected. Disabling the slot provides a clean disconnect from all services before removing the module. When hot-swapping a congured Metro ESM 8668 module, if you reboot the Metro Ethernet Routing Switch 8600 before you install the new replacement Metro ESM 8668 module, the ports are not congured after the new replacement Metro ESM 8668 is initialized. When the Metro Ethernet Routing Switch conguration is loaded, it loads only the section of the conguration for the cards currently installed at time of reboot. You must reboot the Metro Ethernet Routing Switch 8600, or manually enter the conguration for the specic ports.
Ring ports
When using Metro ESM 8668 ring ports with Metro ESU 1800 or ESU 1850 switches, recovery time can exceed 50 milliseconds if the spanning tree group to which the ports are assigned is enabled. After the link is lost on the secondary or primary ring port, the port is removed from the default Service Provider VLAN.
.
When the link is recovered on the ring port, spanning tree blocks the multicast channel from the Mapped NNI VLAN; no loop can exist. Nortel recommends that you disable spanning tree on all ESM ring-enabled ports.
Local and remote UNI considerations

This section describes the following topics: "Conguring endpoints during heavy CPU utilization" (page 59) "QinQ UNIs" (page 59) "L2-VPN broadcasts into ESU rings" (page 59) "Moving UNI IDs between ESM ports" (page 60) "R-module UNIs" (page 60) "8648GTR ports" (page 60)
Conguring endpoints during heavy CPU utilization

When switch utilization is close to 100%, you can experience time-outs when using Device Manager to congure the switch. Nortel recommends that you congure the switch using the CLI during periods of heavy CPU utilization.
QinQ UNIs
QinQ does not forward untagged customer packets. Customer packets must be tagged on ingress for any UNI type that forwards to a remote UNI, dened as a QinQ type endpoint. QinQ UNIs are not supported with ManytoOne TDIs. The TDI must be set to OnetoOne before conguring a Q&Q UNI.
L2-VPN broadcasts into ESU rings

If multiple endpoints within a common ESU ring share the same TDI, when broadcast packets or multicast packets (i.e. topology or OSPF packets) are sent within the TDI, these packets must be replicated for each endpoints, at the ESM ring port, before it is sent to all designated endpoints within the ring. As the number of common endpoints within a TDI increase within the ring, so will the overall aggregate trafc rate increase. For example, if you have 10 endpoints, for every broadcast packet send within the TDI, the packet must be replicated 10 times to be sent to each endpoint in the ring. This will result in a 10 fold increase in trafc bursts for every broadcast related packet sent. To minimize the overall burst rate, Nortel recommends no more than 5 endpoints per TDI in a single ring. When multiple endpoints share the same TDI in the same ring, if any one of the ESU access ports should drop its link (for example, the user disconnects from a port, or the attached device drops its port state), a few packets may be dropped on all other active endpoints in the ring. Due to
.
different rates, packet sizes, and trafc patterns that may exist, the actual number of lost packets may vary according to trafc conditions at the time the endpoint disconnects.
Moving UNI IDs between ESM ports

When moving either an active UNI ID between ESM ports, or a primary ring port of an existing ring to another ESM port, all remote UNIs fail to learn the new UNI port destination MAC. Until the customer destination MAC address ages out or the remote UNIs are reset, the remote UNI IDs continue to send customer trafc to the original ESM port before the UNI ID was moved. When moving a UNI ID or primary ring port, Nortel recommends that all remote endpoints are disabled and then re-enabled after the local UNI ID is moved.
R-module UNIs
For this release, you must congure a point-to-point EVPN on an R-module UNI port. However, before you enable the endpoint, congure the remote B-MAC address. This is not optional. If you do not provision the remote B-MAC address, the R module encapsulates the customer trafc with a destination MAC address set to 00-00-00-00-00-00, which results in trafc ooding into the core network. The R module endpoint classication rule consists of an Ethernet UNI ID and a TDI. For endpoints assigned to an Ethernet UNI ports with service type TLS-Switched or QinQ, one or more q-tags are included in the classication rule. In Release 4.0.4.3, the endpoint connection type supported is point-to-point only and is based on an Ethernet line (E-Line) service. R-module endpoints designate the end users connection-type, and receive assignment to a customer through the TDI. Endpoints classify and police the trafc on a per endpoint basis using pre-dened QoS rules and policers assigned to ingress and egress policer proles per endpoint.
8648GTR ports
In the Nortel Metro Ethernet solution, 8648GTR ports can be used as UNI ports. Because of this, Nortel recommends using the strict priority scheduler on these ports to provide the best support for the four service classes.
Multi-service UNI ports

As of release 4.0.4, ESM ports support multiple UNI IDs with multi-service types. A single ESM port may include support for Local TLS-Switched UNIs, QinQ(1) UNIs and QinQ(2) UNIs. Multi-Service UNIs are not supported on ESU ports; only ESM and R-module ports support multiple UNI IDs at this time.
.
Many-to-one restrictions
Ports assigned with both QinQ UNIs and TLS-Switch UNIs may not be assigned to Many-To-One TDIs, even if the QinQ UNIs are assigned to One-To-One TDIs and the TLS-Switched UNIs are assigned to the Many-to-One TDIs.
Local port switching

Local switching between TLS-Switched UNIs assigned to the same ESM port is supported. However, local port switching of QinQ UNIs or local switching between QinQ and TLS-Switched UNIs on the same ESM or R-module port is not supported.
Metro Ethernet Routing Switch 8600 QoS considerations

This section describes the following QoS considerations: "ACL lters" (page 61) "QoS policing" (page 61) "COS prole" (page 61) "Premium trafc restrictions" (page 62) "Egress QoS markings for untagged packets within an ESU ring" (page 62) "TDI congestion drop counters" (page 63)
ACL lters
Release 4.0.4.3 does not support access control list (ACL) lters on R-module UNIs and endpoints. However, if you are using R-module ports in an Enterprise solution, the ACL lters function as documented.
QoS policing
For this release, policed rates for Metro Ethernet Routing Switch 8600 endpoints do not include inter-packet gap and preamble (Start of Header bits) for every packet sent.
COS prole
If you set the Premium COS value to drop out-of-prole trafc (premium-pir-usage=disabled), and if trafc rates should exceed CIR levels, the attached devices sending control plane requests, such as ARP requests or VRRP responses, are dropped. In management environments, the ability of a CPE device to respond or receive ARP requests can cause loss of network access to NMS type applications. If the CPE edge device on the attached endpoint requires NMS support, Nortel recommends that the premium service COS value have a proper CIR level, or that you allow the COS prole to burst premium trafc above CIR by enabling the premium-pir-usage ag.
.
When using L2-VPNs to manage multiple ESUs and customer devices within the same TDI, Nortel recommends limiting the maximum PIR rate to limit broadcasts, autotopology messages, and SNMP discovery probes into the L2-VPN. A signicant amount of broadcast trafc can be generated, impacting general services on ESU rings and other VPNs not related to the TDI that is being used to manage all devices in the common TDI.
Premium trafc restrictions

For non-R-module interfaces, the maximum egress rate of all "aggregate ows" for premium marked trafc should never exceed a sustained rate of 1.2 Gbps or burst above 1.4 Gbps out a single Gigabit port. This maximum bit-rate includes all overhead including Optical Ethernet Layer 2 overhead per packet. For example, if four endpoints share the same hub port, the maximum premium bit rate supported for each UNI should not exceed a combined rate of 255 Mbps each, if all four ports are sending to the hub port at the same time. Premium trafc is always provided unlimited switch-fabric bandwidth support, regardless of congestion rates. The switch fabric attempts to forward all trafc, and uses all available resources to maintain a 0% loss rate for premium trafc. This includes using all buffer space available to other ports before dropping the trafc. If the combined ows of all premium trafc ows should exceed or burst above 1.4 Gbps, trafc loss may occur on all ports on the chassis, regardless of service type or QOS level. Nortel recommends that Premium or Expedited Forwarding (EF) trafc should not exceed 20% of your overall SLA requirements for a single egress port.
Egress QoS markings for untagged packets within an ESU ring

As of release 3.6.0.0 and above, when untagged customer packets egress into a Metro ESU 1800 or ESU 1850 ring (i.e., packets destined for the Metro ESU 1800 or 1850 UNI port at the egress node), the ring packets include the service provider p-bits to manage the packets QOS level within the ring. For example: If a customer packet enters a remote UNI with a gold classication and the default priority and egress QoS maps are used, when the packet enters the egress Metro ESU 1800 or ESU 1850 ring, the p-bits is marked as 4. By default, the Metro ESU 1800 or 1850 ring treats a p-bit setting of 4 as a class 0 (standard) COS value. You must make sure the Metro ESU 1800 or 1850 802.1 user-priority mappings for each possible SP p-bit is set to the correct desired level. For the above example, change the 802.1 user priority level 4 to a class-2 setting. This provides the same level COS value as Gold.
.
TDI congestion drop counters

The TDI congestion drop counter (CDR) provides statistics on the number of classied VPN packets dropped (as the switch fabric was congested). The CDR counter does not increment if any portion of the packet is dropped due to increases in congestion within the switch fabric before the packet completes its transition into the switch fabric. The occurrence of a post-drop is more likely on larger packets due to the time required to clock the bits into the switch fabric. For packets that are successfully transferred into the switch fabric, if congestion occurs at the egress port (for example, at the NNI port or the local switch UNI port), an Outloss packet counter counts the number of packets lost due to egress port congestion. The Outloss packet counter is a global counter for all VPNs that use the egress port.
Dual-home ring
When conguring dual-home rings, the ERT trunks must be congured as MLT trunks. If a single non-MLT trunk is used, if a mid-span ring break should occur, up to 15% trafc loss will be seen, regardless of trafc load. The 4.0.4.3 release does not resolve known multiple ring break conditions. If a ring break occurs, any additional breaks within the span of the ring or any ESU resets that may occur while the ring is recovering may result in a double-fault ring break condition. If a double-fault condition occurs, trafc may stop forwarding or the ring may transition to the down state. If, after the ring breaks are remedied the ring remains down or cut, you must disable the ring and re-enable it after the ring is healed.
Static destination UNI MACs

When using static destination UNI MAC addresses in a dual-home ring conguration, the primary dual-home switch does not update or congure the static entry on the secondary dual-home switch. You must congure the same static destination UNI MAC address on both the primary and secondary dual-home switches. To avoid synchronization errors when conguring static destination UNI MACs, congure the secondary dual-home switch rst before conguring the primary dual-home switch.
Dual-home ring endpoint MAC table size

For endpoints assigned to a dual-home ring, if you modify the mac-table-size or any endpoint attributes on the primary dual-home ring switch rst, and then make the subsequent change on the secondary dual-home switch, the secondary switch sometimes fails to learn the customer destination MAC address and will always multicast trafc out all ports assigned to the TDI
.
and mapped VLAN. Any changes required for an endpoint must be made to the endpoint on the secondary dual-home switch rst followed by the same changes on the UNI assigned to the primary dual-home ring switch.
Conguring endpoints for dual-home rings

When conguring new endpoints or changing the status of existing endpoints in a live network, congure and enable endpoints on the secondary dual-home switch rst before enabling the endpoint on the primary switch. If the endpoint is enabled on the primary switch rst, MAC addresses may be learned on the primary before the secondary is updated resulting in trafc broadcasting into the service provider backbone.
Dual-home ring and OPE3500 NNI interoperability

When connecting Ethernet NNI uplinks for both the primary and secondary dual-home switch to a Nortel OPE OM3500 switch, the ERT or ERT-MLT ports on the primary dual-home switch must be congured as the root port for the STG group. The Spanning Group default path-cost value of a Metro Routing Switch 8600 GigE (1G or 10G) port when active is 1. The following conguration rule applies when connecting to the OM3500: The secondary dual-home node must be congured as root bridge for all STGs dened. STG must be enabled on the ERT or ERT MLT port and also the Metro 8600 NNI ports connected to the OM3500 mapped ports. The IBT or the IBT MLT ports on the primary dual-home node must be congured as the STG root port. The path-cost assigned to the Metro 8600 NNI interface on both the primary dual-home switch and secondary dual-home switch, that are connected to the OM3500 mapped port, should have a path cost greater than 1 but less than 100. In order to force the required STG path, it is recommended that the primary dual-home nodes ERT port or ERT MLT port path-cost be set to 1 (default is 1 for 1 Gig and 10 Gig ports).
The following path-costs are recommended when both the dual-home switch NNI links are directly attached to the OM3500 mapped ports: Set NNI Gig Ethernet links to a path-cost of 20. Maintain the default path-cost; the value is 10 for Gig Ethernet or 10 Gig ERT ports.
The OPE3500 path-cost for STG is not congurable.
Legacy access ports (ESM Server ports)

Legacy Access ports (also know as ESM Server ports) are no longer supported for general customer UNI access as of release 4.0.0.0. Legacy ports may still be used to maintain L2-VPN management for sites using
.
dual-home rings or to manage existing sites using L2-VPNs to manage ESUs within single-home rings. See 3.6.1 release notes for more information about general conguration and considerations of Legacy Access ports. After migrating services from Legacy Access EVPNs and associated endpoints to ESM-based ports (local, ring or standalone), you have to reset the legacy module to restore normal service to the legacy ports. To reset a legacy module, remove and re-insert the module into its slot or reset the chassis. Nortel recommends migrating Legacy Access port EVPNs to ESM-based ports during a scheduled maintenance window.
ESU and customer CPE management considerations

This section describes when to use Layer 2 VPNs.
L2-VPN based management

If IP services are not possible, or if you are using dual-home rings, you can manage the Metro ESU 1800 or ESU 1850 device using layer 2 VPN connections from the Metro Ethernet Routing Switch 8600 to the NOC centers. All UNI service types are supported. To limit broadcast domains, Nortel recommends using different TDIs and Mapped NNI VLANs whenever possible to reduce the broadcast auto-topology messages and SNMP discovery broadcasts within a TDI and mapped VLAN that can occur in large networks. When using L2-VPNs to manage ESUs and attached CPE devices, the use of local switched loopback connections between a UNI endpoint and an IP based VLAN on the same Metro Ethernet Routing Switch 8600 is not supported and should be avoided. Possible switch fabric loop conditions could occur during reboot or when changing service types on endpoints. These conditions can result in switch fabric lockup conditions or loss of customer trafc.
Ethernet MTU size

For Release 4.0.4.3, the maximum transmission unit (MTU) size supported is 1950 for legacy access ports and ESM local ports. For ESU ring ports, the maximum MTU size is 1600. R-module MTU support is 9600 bytes. The IP Control Plane protocol MTU is xed to 1500 regardless of port MTU settings for OSPF services. Note that the MTU numbers are interface maximums and do not include any service provider encapsulation overhead. End customer trafc maximum frame size will be smaller.
.
Transparent Domain Continuity tests

This section describes the following Transparent Domain Continuity (TDC) topics: "Non-critical TDC test issues" (page 66) "Metro ESU 1800 or ESU 1850 UNI ports" (page 66) "Round Trip Time stamp measurements" (page 67) "TDC error messages on ESU 1800 or ESU 1850 power down state" (page 67) "Known Optical Metro 3500 TDC interoperability issues" (page 68) "TDC test results" (page 68)
Non-critical TDC test issues

The following list describes non-critical TDC test issues: If you congure a TDC test with a specic QoS level, when the TDC test packet arrives at the ingress endpoint, the TDC test packets QoS level is remarked based on the endpoint priority map, upon which the TDC packet is classied. If you use TDC tests with the Optical Metro 3500 switch, and you congure Round Trip Time (RTT) stamps, some test results can show a negative RTT time stamp when the Optical Metro 3500 switch CPU is under a severe load. If you congure TDC to test various endpoints within an Optical Metro 3500 switch environment, the total RTT time stamp between the Metro Ethernet Routing Switch 8600 devices at the edge of the ring can appear less than the same TDC test case using an Optical Metro 3500 switch destination UNI that is in the same data path. The TDC RTT test results between the Metro Ethernet Routing Switch 8600 devices are correct. For test cases where the number of Unicast and Multicast packets are congured in the range of 50 and 100 packets, and the destination UNI is an Optical Metro 3500 switch UNI, the duration of the test can be longer than you expect. For 100 Multicast and Unicast packets, the total test duration for results can take upwards to 20 seconds to complete.
Metro ESU 1800 or ESU 1850 UNI ports

If you do not dene port policer on a Metro ESU 1800 or ESU 1850 port, the switch does not forward customer trafc. However, the TDC test case passes.
.
Round Trip Time stamp measurements

The Round Trip Time (RTT) parameter measures the total time the TDC test packet takes from point of origin (source ID) and back again (back from destination ID). The overall time noted includes processing time of the TDC packet by Metro ESM 8668 modules and, in case of Ring topology, it also includes ESU 1800 and 1850 processing time. For local TLS and legacy access ports, the average RTT nodal delay between CPU and the ESM port is around 30 Secs. Various trafc patterns, QoS, and lookup processing time can add latency to the actual TDC data packet. For the Metro ESU 1800 and 1850, the RTT Time parameter measures the total time the TDC test packet takes from point of origin (source ID) and back again (back from destination ID). The overall time noted includes processing time of the TDC packet by each Metro ESU 1800 or 1850. The actual latency measurement is not the true customer end-to-end latency expectation. Processing time of TDC packets through each Metro ESU 1800 or 1850 could average between 700 and 1000 micro seconds. For RTT values between two Metro ESU 1800 or 1850 devices, the TDC packet is processed twice, once from the originating Metro ESU 1800 or 1850 device, and again at the terminating Metro ESU 1800 or 1850 device. TDC processing time is affected by trafc processing and management trafc. Filter hits, QoS scheduling, SNMP queries and use of console port to access statistics and other ESU management information can affect and increase the overall processing time above the stated average. The Metro Ethernet Routing Switch 8600 RTT timestamps values are incremented in milliseconds (ms). A round trip time under 1 ms results in a display of 0 ms RTT on the Metro Ethernet Routing Switch 8600 TDC test results.
TDC error messages on ESU 1800 or ESU 1850 power down state
When you power down one or more Metro ESU 1800 or ESU 1850 switches that have an active running TDC test, the Metro Ethernet Routing Switch 8600 console may display CPU and TDC error messages. These messages display because of the loss of the TDC assigned UNI interfaces going down when the Metro ESU 1800 or ESU 1850 is powered down. These messages do not affect the overall performance of the switch or the use of TDC tests. If a TDC test is running in periodic state and a change is made to the TDC test ID (for example, you change priority, or change RTT-threshold), the current test aborts and all previous history data are cleared. Cleared history also applies to changes made to the TDC test after it has completed all periodic test counts.
.
Known Optical Metro 3500 TDC interoperability issues

Older versions of Optical Metro 3500 (Version 13.x or earlier) run-time images are unable to interpret the Metro Ethernet Routing Switch 8600 timestamps. If the Optical Metro 3500 originates a TDC request with RTT options on older versions of Optical Metro 3500 operating code, the Optical Metro 3500 software displays the following message and the RTT (Round Trip Time) is set to zero:
"Warning, cant process time information"
TDC test results

Not all Metro Ethernet Routing Switch 8600 TDC test case conditions are responded to by TDC test case requests from other Optical Ethernet devices. Examples of known test conditions that will fail as "timeout" (or no response from the Metro Ethernet Routing Switch 8600) are as follows: Wrong UNI point-to-point type, spoke-to-spoke, hub-to-point-to-point, and point-to-point-to-hub UNI disabled on the Metro Ethernet Routing Switch 8600 Endpoint disabled on the Metro Ethernet Routing Switch 8600 TDI disabled on the Metro Ethernet Routing Switch 8600 UNI Port Down (state down or Link Down) Remote UNI ID not exist TDI mismatch Metro ESU 1800 and 1850 port down * Metro ESU 1800 and 1850 link down * If the Metro ESU 1800 or ESU 1850 port or link state down occurs prior to ESU ring port update status, the correct error message is displayed. Default periodic ring updates are 30 seconds; after the update veries Metro ESU port down, all future TDC test cases for the Metro ESU UNI timeout.
MAC learning keys and 32-bit UNIs

The Metro Ethernet Routing Switch 8600 supports 32-bit UNI IDs for local Metro ESM 8668 and legacy access ports. However, if the learned customer destination MAC address remains the same, but the UNI ID changes, only the least signicant 24 bits for ESM Local Ports and least signicant 16 bits for legacy access ports are compared and veried as unique. For example:
.
An ESM Local Port at site A learns destination customer MAC 00:00:AA:01:01:01 from source (remote site) UNI ID 2.1.1.1. When the ESM Local Port at local site A forwards to the known customer destination MAC address, it uses customer destination UNI ID 2.1.1.1. If the remote device at MAC address 00:00:AA:01:01:01 should move to another UNI ID before the customer destination MAC table ages at the local site A, only the least 24 bits are used to compare and verify that the UNI ID changed. In this case, if the device at the remote site moved to UNI ID 3.1.1.1, there would be no change in the learned customer MAC table as the least 24 bits are still the same and packets will continue to forward to UNI 2.1.1.1. However, if the device had moved to UNI ID 3.1.1.2, because the lower 8 bits are different (changed from .1 to .2), the new UNI ID 3.1.1.2 is captured, and the customer destination MAC table would now include UNI 3.1.1.2 as the destination UNI ID. This same rule applies to local legacy access ports, except that the UNI ID verication is based on a unique 16-bit match.
MLT and SMLT considerations

This section describes some MLT and SMLT considerations that you should be aware of when conguring your network.
ATTENTION
Aggregate throughput may be less than line rate when both of the following conditions are true:
R-module ports in the MLT group are on the same module. One CPU is installed in the switch.
If you use R-module ports on the same module, Nortel recommends installing dual CPUs.
VPN-based MLT load sharing algorithm

A multilink NNI trunk aggregates bandwidth between two switches. The Metro Ethernet Routing Switch 8600 uses one of two algorithms to determine which active NNI port in the multilink trunk (MLT) to use for each EVPN packet. The MLT algorithms provide load sharing while ensuring that each packet in a ow does not arrive out of sequence. Attention: These MLT algorithms are the same trafc distribution algorithms used for IEEE 802.3ad-based link aggregation. Algorithm for ESM modules For customer-facing trafc with ESM modules, the distribution algorithm always uses the Optical Ethernet Layer 2 UNI IDs to determine which NNI port to use within the MLT group. In this case, the six least-most signicant bits of the source UNI
.
ID and destination UNI ID of the Optical Ethernet Layer 2 Ethernet frame to be forwarded are compared using the following XOR operation:
(DestUNI-ID[5:0] XOR SrcUNI-ID[5:0]) MOD (number of active links)
Algorithm for R modules For customer-facing trafc with R-module UNI ports, the distribution algorithm uses the Optical Ethernet Layer 2 header MAC address (B-MAC) or the Provider Backbone Bridge (802.1ah) Layer 2 Header MAC address (B-MAC) to determine which NNI port to use within the MLT group. In this case, the six least-most signicant bits of the source MAC and destination MAC of the either the Optical Ethernet Layer 2 Ethernet frame or Provider Backbone Bridge Layer 2 Ethernet frame to be forwarded are compared using the following XOR operation:
(DestMAC[5:0] XOR SrcMAC[5:0]) MOD (number of active links)
The following example demonstrates how the formula works with customer packets entering an ESM UNI port: Source UNI ID: 192.100.200.21 Destination UNI ID: 200.100.100.56 In this example, assume that the MLT group comprises 4 NNI ports. The last byte of the UNI source IP address is 0x21, the binary representation of which is 00100001. Use the 6 least-most signicant bits, which are 100001. Likewise, the binary representation of the last byte in the UNI destination IP address, 0x56, is 01010110, of which 010110 are the bits of signicance. The formula is {(A XOR B) MOD x}, where A and B are the 6 least-most signicant bits in the UNI source and UNI destination IP addresses, and x is the number of active links in the MLT. Thus, we have:
{(100001 XOR 010110) MOD 4} = 55 MOD 4 = 3
Therefore, since the ports in the MLT are numbered 0 through 3, this particular Ethernet frame would traverse the fourth NNI port of the MLT group. The MLT port number is based on the ports IF index number, from low to high.
SMLT
To avoid creating loops when converting a Spanning Tree network into an SMLT network, design your network as recommended in the Network Design Guidelines (313197-C).
.
To determine whether your network topology forms a loop outside the SMLT/IST core, you must review all STGs and VLANs that pass through the IST and SMLT links. If a loop exists, Spanning Tree does not detect it since Spanning Tree is disabled on all SMLT/IST ports. If CP-limit or the loop detect feature is enabled on the port, one port in the loop is identied and it is blocked. Nortel recommends that you do not enable CP-Limit on the IST port. When conguring MLT/SMLT, make sure to include both ports and VLANs in the MLT conguration le. If you specify only VLANs in the conguration and do not add MLT/SMLT ports, this can cause intermittent MAC learning issues on the next hop of the SMLT link.
Customer IP UNIs
When creating a UNI for Customer IP VLAN Support, only the TLS service type is supported. Customer IP UNIs are only supported on TLS-Switched service types. If a TLS-Transparent UNI is assigned to an Ethernet Services Unit port (ring or standalone connection), the Ethernet Services Unit port must not be assigned to an ESU IP_VLAN, it is not supported. If the Ethernet Services Unit port is assigned to an IP_VLAN, there is no consistency check as the Metro Routing Switch 8600 and Ethernet Service Unit are different platforms. Assigning the TLS-Transparent UNI port to an IP_VLAN may result in unpredictable behavior if a matching qtag (or if the IP_VLAN is 4094, an untagged packet) should enter the port, the packet is treated as an IP packet and not as an Ethernet VPN packet.
IP multicast services for customer IP UNIs

The IP Triple Play service on the OESS platform is a Layer 3 function. The ESM 8668 does not support bridging of Multicast services. You must enable the PIM-SM Multicast Protocol on the NNI interface or the SP-VLAN assigned to the customer IP UNI for Multicast to work properly. (As of this release, only PIM-SM and PIM-SSM is supported on the ESM 8668 ports. DVMRP is not supported at this time). Refer to the Enterprise Routing Switch 8000 release 3.5 Network Design Guidelines (313197-C) for more information on how to design and scale multicast networks.
IP spoong
This enhancement enables the Metro Ethernet Routing Switch 8600 to prevent spoong of IP address within the VLAN. IP spoong is supported on legacy and NNI ports, in addition to ESM 8668 ports. This feature
.
requires the switch to be rebooted. Nortel strongly recommends enabling this feature during the upgrade to OE 4.0.4.3 in order to minimize the impact for the network trafc. This feature detects duplicate IP address based on ARP packets received. It is only during this detection phase that the security feature will restrict and drop offending data trafc. If an attached host has already spoofed the network and remote devices have learned the MAC address, this feature does not protect the network from an existing IP spoong incident nor will it restrict the trafc ows in progress. An ESM port can be congured for prevention of IP spoong on a per ESM port basis. All UNIs assigned to the ESM port for Local TLS and all UNIs assigned to an ESM ring port participate when IP spoong is enabled. IP spoong cannot be disabled per UNI or endpoint. When enabling IP spoong on ESM ring ports, the service must be enabled on both of the primary and secondary ring ports, or connectivity issues may occur.
MSTP/RSTP
The Metro Ethernet Routing Switch 8600 supports three Spanning Tree Protocol modes: STP, RSTP, and MSTP. Conguration les are not compatible across modes. This means that you can use a conguration le only in the same mode in which it was created. For example, if you save a conguration le in RSTP mode, you can only use that le in RSTP mode, not STP or MSTP. To change modes, use config bootconfig flags spanning-tree-mode <mstp|rstp|default>. STP is the default mode. When using RSTP or MSTP services, if a tagged port is added to a VLAN in instance 0, and the same port is later removed from VLAN 1 or any other VLAN, the port is removed from all assigned VLANs within the instance. You must remove the port from all undesired VLANs rst prior to assigning the tagged port to its intended VLAN and RSTP instance.
QinQ
Inner tag (C-Tag) VID of 4096 (untagged) is not supported with QinQ2 UNI types. In this release, QinQ2 UNI types always expect the presence of C-Tags. Frames without C-Tags will be dropped with QinQ2 UNI. This limitation does not exist with QinQ1 UNI, as QinQ1 UNI types only examine the Outer Tag (S-Tag).
.
Scaling limits 73
Scaling limits
"FCS scaling limits" (page 73) outlines the scaling limits for the various components of the Metro Ethernet Routing Switch 8600 and the Metro ESU 1800 and 1850.
FCS scaling limits Feature or Service Physical recommendations: Maximum Metro ESM 8668 modules per chassis Maximum Metro ESM 8668 ports per chassis Maximum R modules per chassis Maximum R module ports per chassis Maximum Metro ESU 1800 or ESU 1850 rings per chassis Maximum Metro ESU 1800 ports per ring Maximum Metro ESU 1850 ports per ring Maximum Metro ESUs per ring Min RRP Hello Timer 8 Maximum or Range Comments
64 8 384 24
336 140 14
1 sec, 1 to 7 rings 5 sec, 8 to 15 rings
With 16 or more rings, you can use enhanced RRP between ESUs, but you must disable it on the MERS 8600.
MTU: Maximum Metro ESM 8668 ports Metro ESU 1800 or ESU 1850 ports R module 1950 1600 9600
.
Feature or Service UNI recommendations: Maximum Access mode UNIs (local TLS) per Metro ESM 8668 port Maximum Access mode UNIs (local TLS) per R-Module port QinQ UNIs
Maximum or Range
Comments
4100
4100 per port 4100 per lane Maximum ESM supported outer q-tags per QinQ UNI is 128. Maximum R-Modu le supported outer q-tags per QinQ UNI is 4094. Maximum inner q-tags per QinQ UNI is 4094 336 per ESU 1800 140 per ESU 1850 24 per ESU 1800 10 per ESU 1850 Up to a total of 336 UNIs per ring, of which 128 can be tls-switched (remainder can be transparent).
Maximum Metro ESU 1800 or ESU 1850 ring UNIs per ring Transparent UNIs
Switched UNIs
128 per ESU 1800 and 1850 ring
TDIs: Maximum TDIs per chassis 30 000 Recommended maximum of five endpoints per TDI.
Endpoints: Maximum EVPN endpoints per ESM access port (local TLS) Maximum EVPN endpoints per ESM ring 4100 Maximum of five endpoints per TDI per local TLS port. Recommended maximum of five endpoints per TDI.
2500
.
Scaling limits 75
Feature or Service Maximum EVPN endpoints per R-module access port (local TLS)
Maximum or Range 8630GBR - 4100 per group of 10 GE ports 8648GTR - 4100 per group of 24 GE ports 8683XLR - 4100 per 10 GE port
Comments Maximum of two endpoints per TDI.
Maximum endpoints per ESM server port Maximum q-tags per Many-To-One TDI endpoint 2 15
This limit applies only to ESM, not R modules.
Metro ESU 1800 or ESU 1850 ring: Maximum transparent endpoints Maximum switched endpoints Maximum NNI ports: Maximum Gigabit Trunk ports supported as NNI 240 ports The 240 ports can be individual links or combined in multiple MLT groups. The 8648GTR is not supported for NNI trunks with EVPNs. 128 336 per ESU 1800 140 per ESU 1850 One endpoint per transparent UNI. This limitation is based on scaling tests.
Maximum R-Module 10 Gigabit Trunk ports supported as NNI NNI VLANs: Maximum mapped NNI VLANs per chassis (Local TLS only) Maximum mapped NNI VLANs per chassis (with ESU Rings)
24
1000
250
.
Feature or Service Non-NNI VLANs: Maximum non-NNI VLANs per chassis Static destination UNIs and customer destination MAC addresses: Per chassis Per TDI
Maximum or Range
Comments
Up to 1973
Total of 1973 VLANs is supported on the chassis
10 000 10
COS: COS-profiles 2000 Two are preconfigured for default data and default management profiles.
Max Destination MAC and Source IP addresses: Per Ring/Local TLS port on the Metro ESM 8668 IP VLANs: Max per Ring/Standalone Max per local TLS port Max per Chassis Max Metro IP VLANs IS-IS and OSPF IS-IS Adjacencies per sw IS-IS Routes OSPF areas per switch OSPF adjacencies per switch OSPF routes 40 10 000 5 80 Pre-E and E-modules: 15 000 M-modules: 20 000 R-modules: 20 000 32 32 1973 512 97 000 Destination MAC and IP addresses use the same table.
.
Scaling limits 77
Feature or Service
Maximum or Range
Comments
Multicast Services: PIM Passive Interfaces PIM Active Interfaces (legacy ports only) Multicast Source Subnet Trees Multicast (S,G) Records - PIM Supported Scaling Capabilities Hardware forwarding records 500 80 500 2000 Maximum number supported Pre-E and E-modules: 25 000 M-modules: 125 838 (see Note 1) R-modules: 256 000 IP route support, 16 000 ARP support, and 64 000 MAC support 1973 512 or 1973 with chassis MAC upgrade 2000 2000 16 000 Metro Ethernet Routing Switch 8600: 25 (see Note 2) Metro Ethernet Routing Switch 8600: 32 Maximum of 64 passive ESM interfaces
VLANs IP interfaces Static ARP entries Static route entries IP ARP entries Spanning Tree Groups
MLT groups (see Note 3)
Note 1: Number of records available with record reservation fields set to zero. For more information about the record reservation feature, see Managing Platform Operations (315545-D). Note 2: Nortel supports ONLY 25 STGs in this release. Although you can configure up to 64 STGs (only 63 when a Web Switching Module is present), configurations including more than 25 STGs are not supported. If you need to configure more than 25 STGs, contact your Nortel Customer Support representative for more information about the support for this feature. Note 3: The MLT feature is statically compliant with the 802.3ad standard (no support of LACP).
.
CRs xed in Release 4.0.4.3

This section lists the CRs xed in Metro Ethernet Routing Switch 8600 Release 4.0.4.3. (Q01499861-01) In some specic trafc patterns the soft port reset mechanism on the ESM 8668 may trigger erroneously. (Q01525889) In a multicast trafc scenario, trafc is lost when traversing the network and a High Availability failover occurs. (Q01526396) Dual-home secondary switch does not relearn MAC addresses after disable-enable of endpoints. (Q01527279) When the login session times out during the dump end-point-mac-table command, a subsequent running of the command does not work.

This section lists the CRs xed in Metro Ethernet Routing Switch 8600 Release 4.0.4.2. (Q01376595-02) STP works appropriately when the 8683XLR module is removed and re-inserted. (Q01475103) Ingress trafc is no longer dropped ingressing from an R module UNI with an NNI MLT. (Q01475191) Trafc is now forwarded out of the UNI port after an R module is reinserted. Previously, the trafc would not forward out of a UNI port on a R module after reinsertion. You had to remove the R module UNI port from the mapped-vlan and then add it back. Then add the fdb-static entry in the mapped-vlan for UNI port MAC with outgoing port as UNI port. (Q01478507-03) You can no longer congure an MLT with a null name or with white space using the CLI. Note that previous congurations with no MLT name or a white space name will now receive a default name. Previously, a null MLT name or a white space MLT name would prevent the addition of a new MLT without any warning. (Q01479548) STG now converges properly after a R module reset or a HA-CPU failover. Previously, after R module reset or a HA-CPU failover, the edge device would continue to forward instead of block, thus causing STP to not converge. (Q01480000) The CP no longer resets in a SMLT system when the slave CPU takes over from the master CPU after enabling HA-CPU and then manually rebooting the master CPU. Previously, the CP would reset after enabling HA-CPU and then manually rebooting the master. (Q01490160) Trafc is no longer lost egressing from an R module UNI with NNI MLT and using OCP vendor port GBICs. Previously, enabling
.
79
and disabling a remote end switch with some OCP SFPs would cause the non-OCP SFPs to lock up without any error indication.

This section lists the CRs xed in Metro Ethernet Routing Switch 8600 Release 4.0.4.0. (Q01219594-01)(Q01424230-01) Fixed this ESM issue; endpoints can now be congured for more than 14 q-tags. (Q01236974) In a Metro Ethernet Routing Switch 8600 dual-home ring, the primary now reports the proper state of the last ESU when powered off. (Q01239869-05) When the log le exceeds its congured size limit during the bootup process, the Metro Ethernet Routing Switch 8600 now prints a warning on the console the rst time the condition is detected. (Q01278848-02) System log messages no longer display \n to indicate the continuation of a line of text. Instead, a log error report that contains several lines of text has multiple messages. (Q01295840-02) Zeros no longer appear in the MAC entry table output when using the CLI command dump endpoint-mac-table. (Q01327693-05) OSPF LSA type 11 packets are no longer being improperly processed. Previously, an incorrect check in the code was causing duplicate insertions of LSA in the database. (Q01328700-03) The 8630GBR no longer experiences port lockup on a lane. (Q01330437-02) The correct ESM port is now indicated when an ESU ring goes down. Previously, if the secondary port went down, the information message indicated the primary port had gone down. (Q01330502-02) The CLI dump endpoint-mac-table command now provides the capability to do a TDI-independent search of MAC entries. In addition, port and ESU-specic searches are now supported. (Q01336861-02) Some Nortel SFPs no longer generate HW ERROR TxFault if the ESM port is disabled. (Q01336877-02) The CLI command show sys info gbic correctly shows the SFPs located on an ESM 8668 module. (Q01353959) Fixed this initialization problem when an ESM 8668 module is inserted. (Q01360515-01) (Q01443076) In a Metro Ethernet Routing Switch 8600 dual-home ring, the IBT MLT ports are no longer removed from the VLAN when deleting an endpoint.
.
(Q01378820-01) Continuous ring cut messages no longer appear when the ring is cut or the secondary port is down. (Q01384353-01) When using the log transferFile, the CPU slot number is no longer appended to the le name. (Q01385429-01) CLI and SNMP are no longer inoperable when a second attempt of a TFTP log le transfer occurs after an initial failed attempt. (Q01391005) With a Metro Ethernet Routing Switch 8600 dual-home ring, connectivity is no longer lost when the primary ring port is bounced (disabled, followed by enabled). (Q01391063) On a Metro Ethernet Routing Switch 8600 secondary dual-home ring, the FDB is no longer corrupted when the primary port is enabled after being disabled. (Q01392095) The Metro Ethernet Routing Switch 8600 dual-home ring now recovers after a loop condition is removed on the secondary. (Q01392111) The Metro Ethernet Routing Switch 8600 dual-home ring now recovers after a loop condition is removed on the primary. (Q01395451-01) Listing the GMAC statistics ( dump_gmac ) no longer locks up the console under rare conditions. (Q01415664) You can now dynamically add an MLT to a NNI VLAN in a dual-home ring. (Q01418474) Fixed this ESM mailbox reset issue. (Q01419634-01) A switch running in MSTP Spanning Tree mode is no longer inoperable when the ESM 8668 card, with a port congured as a primary or secondary ESU ring port, is reset. (Q01424145-01) Fixed ESM timeout that was occurring after multiple disables and enables of UNI port. (Q01424707-01) ESM no longer resets after repeatedly disabling and enabling the port. (Q01424948-02) Yielding violations were overcome after periods of high utilization on the Metro Ethernet Routing Switch 8600 were reduced. (Q01434345) The topology table on a switch that is operating in High Availability mode no longer gets emptied after a master CPU failover occurs. Previously, following a master CPU failover on a switch running in HA-CPU mode, the topology table was emptied on slots with MLTs; causing the discovery of adjacent switches to fail. (Q01441104) Fixed CLI command interactions. (Q01442848) Improved ESM Mailbox reset time.
.
Known issues and CRs 81
(Q01452723) QinQ1 endpoints now send trafc to OM1K transparent endpoints, which now allows for proper data transfer. (Q01454261) SMP log message corrected for ESM Soft Port reset. (Q01456140) IBT ports are no longer removed from VLAN when deleting dual-home ring endpoints.
Known issues and CRs

This section describes issues and bugs (CRs) known to exist in this software release. (Q01524578) When the dual-home ring is in cut state and a HA-CPU failover is performed, an ESM port lockup may occur and reset the ESM card. Workaround: None (Q01134934) For the best ESM performance, Nortel recommends using Metro ESM 8668 ports 2 through 8 for applications which are expected to run the ESM interface close to line rate. On rare occasions, an ESM reboot can occur when a soft port reset happens on port 1 of the ESM, due to high trafc volume on that port. Workaround: None (Q01317956-01) If one SMLT link is missing a VLAN which is congured on the corresponding SMLT link on the other aggregation switch, the MAC record will be dropped in hardware by the switch missing the VLAN record. Workaround: Be sure to congure the same VLAN on both aggregation 8600 switches with SMLT. (Q01355032-02) The command dump endpoint-mac-table all or dump endpoint-mac-table tdi <tdi> may show duplicate MAC addresses for local TLS many-to-one endpoints after using the command config tdi <tdi> flush-mac or config tdi <tdi> endpoint <uni-id> . Workaround: None (Q01393899) For the 8630GBR module, the SFP name details are incomplete: the display refers to the SFP as Lx rather than a CWDM SFP. Workaround: None (Q01406398-01) FDB aging with MSTP/RSTP mode is not accurate. Workaround: None. (Q01424014) 8630GBR module reboots when a UNI port goes in forwarding.
.
Workaround: Disable Spanning Tree on the UNI port. (Q01425882-01) When you congure the Metro Ethernet Routing Switch 8600 to not log messages to the screen (conf log screen off), log messages still appear. Workaround: None (Q01448333) Under some conditions, the ESM 8668 endpoint does not discard OEL2 trafc destined to an invalid destination UNI MAC address. Workaround: This issue only happens when a remote endpoint is miscongured. (Q01448228) An erroneous error message appears while booting up a dual-home ring switch (CheckValid ERROR: FAILED Parameter. Slot = 15). The error has no effect on the switch. Workaround: None (Q01448402) Trafc loss is seen after rebooting the primary switch with ring ports disabled in a dual-home ring environment. Workaround: As soon as the ring ports are enabled the trafc will continue. (Q01455973) A complete ESM mailbox recovery failure causes the Metro Ethernet Routing Switch 8600 to temporarily pause for 10 seconds. Workaround: This issue is only seen when the switch is under heavy load for an extended period of time. (Q01456686-01) Current fabric selection algorithm does not consider the destination card type. For a Legacy destination, packets from the same source can arrive from two different fabrics. In this case, the potential exists for a Legacy card to lose some trafc. Workaround: None (Q01475170) With R-mod UNI TDC tests running in periodic mode, if the Source UNI port is down there may be extra printfs appearing on the console (test_periodic_run: tdc_start_test failed). This does not affect the operation of the switch. Workaround: None (Q01487134) With HA-CPU failover and large congs, the slave CP may reset after the primary CP is removed. Workaround: None (Q01479958) While running 500 TDC tests with 1 minute interval, there may be intermittent failures. Workaround: Run fewer than 500 TDC tests or increase the time interval.
.
(Q01491606-03) The Putty rlogin client version 0.58 will fail. Workaround: Disable the rlogind ag in boot.cfg or use a different rlogin client.
(Q01498864) The CLI command show sys info gbic does not show the GBICs inserted in 8630 module. This occurs only after a HA-CPU switch-over and remains present until rebooting the chassis. Workaround: To see if a GBIC is present and determine its type (LX or SX), use the CLI command show port info config. Or, you can use Device Manager to display the port properties (select a port, then choose Edit > Port > Interface). However, the GBIC vendor name is omitted in both cases.
(Q01499861) The soft port reset mechanism on the ESM module can falsely trigger and reset an ESM port if multiple types of priority trafc ow through the port. Workaround: None
Platform
(Q01211817) The IEEE 802.1ag Connectivity Fault Management packets by default use QOS p-bit 7. If you set the priority level for the assigned MA to any other value, the packets will still forward with QOS p-bit 7. Workaround: None (Q01246689) SMLT failover links may fail when rebooting an aggregate switch that is redistributing BGP routes to OSPF routes when OSPF transitions from the exchange state to the loading state. Trafc from edge switchs will not forward if the backup SMLT links are down. Workaround: Large distribution route tables may result in downtimes of up to 4 seconds. When using SMLT connections to edge switches, it is recommended to reduce number of routes to under 1000. (Q01268520) In the Nortel Metro Ethernet Routing Switch 8600, the ring remains cut after secondary ring port break occurs with 900Mbps of multi-cast ows or greater in the ring. Workaround: When multi-cast (source) trafc stops, ring will recover. You may also disable the ESU ring and re-enable to recover the ring state. (Q01287684) If the ring cut and the chassis is reset, upon recovery, clearing cust-ip-vlan stats an error fail to clear for each UNI will appear on the console. Stats will not be cleared and statistics will continue to increment. Workaround: Restore the ring and wait for ring to show normal state.
.
(Q01294884) Multicast trafc over IP VLAN UNIs will not increment, or may only intermittently increment, the RX-SP-MCAST and TX-SP-MCAST stats for the selected cust-ip-vlan UNI. Workaround: None (Q01295721) If the existing Nortel Metro Ethernet Routing Switch 8600 cong includes ESU rings with and ESU-MOD-ID 24 congured, when upgrading to Release 4.0.0.1, 4.0.0.2, or 4.0.2.x, the cong will fail to load. Workaround: You must recongure any ESUs with MOD ID 24 to be within the supported range of MOD ID 1 to 23. Any UNIs assigned to a ring with ESU MOD ID 24, must also be changed to the new MOD ID prior to upgrade. (Q01300764) When using IP_VLAN UNIs, if a prior ring break occurs at the primary ring port (link down on primary ring port), subsequent changes to endpoint level parameters may cause incorrect IP ARP forwarding entries to appear in the database, resulting in packet loss until the ARP entries age out of the system. Total duration of aging ARP entries may last up to 6 hours assuming no trafc from attached devices. Workaround: If the primary ring breaks at the primary port, once the repairs are made, it is recommended that you ush the IP ARP entries from all SP-VLANs assigned to this ring. (Q01307226) As of Release 4.0.0.2 and above, cust-ip-vlan 4094 is not valid. The valid cust-ip-vlan range is 1 to 4093 and 4096. If the existing Nortel Metro Ethernet Routing Switch 8600 cong includes UNIs with cust-ip-vlan 4094, when upgrading to Release 4.0.0.2 or 4.0.2x, the cong will fail to load. Workaround: Recongure any UNIs assigned to cust-ip-vlan 4094 to a valid qtag range of 1 to 4093 and 4096 before upgrading to Release 4.0.0.2 and above. (Q01307541) In the Nortel Metro Ethernet Routing Switch 8600, if the NNI MLT ports should ap, the show ports stats interface extended command will display negative packet counts. Workaround: This issue does not affect trafc ows out the NNI ports. If the port statistics are cleared, the issue goes away.
.
PBT
(Q011321440) When operating the Nortel Metro Ethernet Routing Switch 8600 with PBT and HA-CPU, if you admin disable the primary PBT trunk port, an Application Sync Failed message may appear on the standby CPU console port while the trunk port is admin disabled. Workaround: Re-enable the primary trunk port. (Q01319462) When operating the Nortel Metro Ethernet Routing Switch 8600 with PBT and HA-CPU, if you disconnected the ESU-Ring from the ring ports, an error message for each assigned SG may appear on the console, but will not impact normal operations for other trafc ows not affected by the removal of the ESU ring. The message will appear with CallingSendCfmSgInfoRecordToPort in the header of the message. Workaround: None (Q01345751) Changing EP priority mappings may cause PBT trunks to ap when using 8632TX legacy modules for NNI trunk ports. Workaround: Do not use 8632TX, 8632TXE, or 8632TXM modules for PBT trunks or EVPN NNI trunk ports. (Q01351809) When clearing mep stats, a debug message starting with cfmCollectMepStatsFromMip may appear on the console for each mep congured on the chassis. This message will not harm existing data ows and is not an indication of problems. Workaround: None (Q01351925) ESM port will incur sustained trafc throughput loss, when the trafc load is greater than 400M for small packets. This condition occurs when there are more than 100 service groups (SG) congured on the port. Workaround: Maintain only 100 SGs or less per ESM port for environments where most trafc consists of small data packets. (Q01357642) When adding new PBT trunks to R-module ports within an MLT group, all PBT trunks associated with the MLT port may transition to a down state on the R-module port that the new PBT trunk is added to. Workaround: The MLT port must be disabled and re-enabled to recover the PBT trunk session. Issue occurs only on the rst time a new PBT trunk is added to the MLT port. After port is disabled/enabled, subsequent adds will have no issue until the chassis is reset.
.
(Q01358652) When conguring PBT VLANs, the "unknown-mac-discard" option does not work with R-module ports assigned to the PBT VLAN. The "unknown-mac-discard" feature is intended to protect against network loop design errors or from accidental assignment of a PBT VLAN to a non-UNI access port by discarding packets not intended to be forwarded to the destination PBT trunk interface. If an unknown destination MAC enters an R-module NNI port for a specic PBT VLAN, the packet will ood out all ports assigned to the PBT VLAN. Workaround: Make sure the PBT VLAN paths are end-to-end, with no VLAN loops in the core. Make sure there are no "non-UNI" access ports assigned to the PBT VLAN. As an additional safeguard, Nortel recommends that you disable all ports along the PBT path, assign the ports to the PBT vlans and once the congs are re-conrmed, enable the ports. (Q01361263) If you use a MEP ID greater than 256, the show mep stats command does not display the MEP statistics. Workaround: Nortel recommends using MEP IDs in the range of 1 to 256 only. Q01362526 - If you save the run-time cong with multiple PBT trunks disabled and then reboot the chassis with the saved cong, the ESM module may reset multiple times after the chassis restores the saved cong. Workaround: Save the cong with enabled PBT trunks only. (Q01364125) The service group (SG) does not come up if you add a maintenance endpoint (MEP) after enabling the SG. Workaround: Always congure a MEP and then enable SG. Always save the conguration with a MEP added. If you load a conguration with an enabled SG that does not have a MEP, reset the ESM if there are no other services on this card. (Q01364156) You cannot add a previous maintenance association (MA) and maintenance endpoint (MEP) back to a service group (SG) once you change the SG values, even after deleting the SG. Workaround: You must delete the SG and reset the ESM module that the SG was assigned to. (Q01365162) In large scale PBT-based networks, it may take several minutes for clear mep stats to clear all values. During this time, the console locks until all stats are cleared. Workaround: None.
.
(Q01365176) The clear mep stats ma-domain <value> causes the following error message to appear multiple times on the console "interrupt: Error enqueueing to Rxlist. Workaround: None. Nortel recommends not using this command in this release. However, keep in mind that this issue does not affect the normal operation of the switch.
R-module UNI
(Q01269522, Q01210718, Q01210713, Q01210703, Q01210721, Q01212861 and Q01234797) The command show sys info, show sys info card, show sys info asic, or show tech incorrectly displays information for an R-module under the heading of Card FrontType. This problem also happens in Device Manager for the heading Card Type. Workaround: None (Q01288587) When using R-module UNIs, when changing the pir-usage ag from disable to enable, the new rate change may take up to 20 seconds. During this time, the ingress policer will continue to police at the current CIR rate even though there is bandwidth available within the PIR setting. Workaround: None (Q01300070) When using R-module UNIs, with cust-ip-vlan assigned, if IP trafc is present when the R-module access port is rst initialized, the trafc forwarded out the NNI ports will be marked critical (QOS 7) for a short period of time (up to 10 seconds) regardless of the QOS markings on the original data packets. After the port is fully up, the trafc will forward out the NNI ports with the correct QOS markings. Workaround: None (Q01300881) When clearing TDI stats with R-module UNIs, a debug message starting with tlsSendSyncMsgToRmod may appear on the console. This message will not harm existing data ows and is not an indication of problems. Workaround: None (Q01303229) When using R-module UNIs, the End-Point Override-P-bit is ignored and TOS bits will not be honored. Workaround: None. Only P-Bits are supported in Release 4.0.2.x for R-module UNIs.
.
(Q01303264) When using R-module UNIs, the Bridge Protocol Data Unit (BPDU)-trafc endpoint parameter is ignored. Expedite and Drop will not work with-module UNIs. Workaround: None
High Availability
(Q01280082) When operating the Metro Ethernet Routing Switch 8600 with HA-CPU, if you reset the primary CPU and than reset the standby CPU before it has completed the Table Sync process, when the original CPU (primary) attempts to take over again, a Hardware Fatal error double fault condition may occur and the CPU will reset again to clean up the tables. Several Error and fault messages will appear during this double fault condition. Workaround: After resetting the primary CPU, wait for the HA-CPU table sync process to complete. When the standby CPU is up and table sync is complete, you may reset the new primary CPU to failover back to the original CPU. Check system logs to conrm primary CPU is in synchronized state (SNMP trap is also sent to NMS tools when synchronized state is complete). (Q01321861) When using HA-CPU and PBT, in large scaled environments, if the primary CPU was pulled out, or is pulled after standby takes over the CPU failover service completed, when you re-insert the CPU, the table sync process may take up to 8 minutes. During this time, no changes to the cong will be allowed. Length of time is dependent on the number of SGs, PBT trunks and endpoints congured. Workaround: Smaller congs take signicantly less time to resync the tables. (Q01350933) After the primary CPU fails and HA-CPU failover occurs, if a PBT trunk failure occurs within 45-50 seconds, the PBT data will not failover to the secondary backup trunk. Workaround: To recover from this condition, you must restore the primary trunk connection on the chassis that has encountered the HA-CPU failover to restore all PBT trafc ows. (Q01351914) When HA-CPU failover occurs with active PBT trunks, trafc forwarding over the trunks may see multiple drops of trafc while the standby CPU takes over. Workaround: None
.
Related publications
89
Dual-home ring
(Q01309776) For dual-home ring environments, any dynamic change to the endpoint parameters should not be performed when the ring is cut. The resulting change will ush the forwarding entries and may result in a loss of trafc forwarding for the endpoint. Workaround: Disable and re-enable the dual-home ring on the primary switch followed by the same action on the secondary switch.
Documentation corrections
There is an error in Installation and Using Device Manager (317832-D). The "Windows minimum requirements" section incorrectly states the PC requirements for RAM and disk space. To install JDM on your PC, Nortel recommends that you have a minimum of 256 MB of RAM and 350 MB of available disk space.
Related publications
The Metro Ethernet Routing Switch 8600 documentation set includes documents from the Enterprise Ethernet Routing Switch that are common to both platforms.
Hardware installation and user guides

The following guides provide instructions for installing the chassis and its components:
Installing and Maintaining the Metro Ethernet Routing Switch 8600 Series Chassis and Components Installing the Metro Ethernet Routing Switch 8600 Series Modules Important Information about the Routing Switch 8600 Metro Ethernet Services Module 8668 and the CPU/SF Module 8691/8692omSF Important Notice Metro Ethernet 8600 CPU Expansion Mezzanine Card Installing a CPU Memory Upgrade Important Notice for using the correct software version with the 8692SF CPU module Installing the Web Switch Module for the 8600 Series Switch Using the Ethernet Routing Switch 8600 10 Gigabit Ethernet Modules Installing the Breaker Interface Panel for the 8010co Chassis Installing an AC Power Supply in an 8000 Series Switch Installing a DC Power Supply in an 8000 Series Switch
.
320417-B 312418-B 317980-C
317801-B 314832-C 320229-A 314969-C 315893-D 312755-F 312751-D 313070-D
Installing a Fan Tray in a Routing Switch 8000 Series Switch Installing SFP & XFP Transceivers & GBICs
312752-D 318034-C
Software installation and user guides

The following guides provide installation, reference, and conguration information for both the Device Manager and Command Line Interface (CLI):
Upgrading to Metro Ethernet Routing Switch 8600 Series Software Release 4.0.2 Getting Started with the Metro Ethernet Routing Switch 8600 Software Network Design Guidelines Installing and Using Device Manager Configuring the Metro Ethernet Routing Switch 8600 with Device Manager Configuring the Metro Ethernet Routing Switch 8600 with CLI Adding MAC addresses to the 8600 Series Chassis Using the 8672ATME and 8672ATMM Modules Configuring IP Routing Operations Configuring BGP Services Configuring Network Management Configuring and Managing Security Configuring VLANs, Spanning Tree, and Link Aggregation Managing Platform Operations Configuring Internet Group Membership Authentication Protocol (IGAP). Configuring QoS and IP Filters for Routing Switch 8600 Legacy Modules Configuring QoS and IP Filters for Routing Switch 8600 R modules Using Diagnostic Tools Using the Packet Capture Tool (PCAP) System Messaging Platform Reference Guide 316674-B 317814-C 313197-E 317832-D 320747-A 320746-A 212486-B 209195-F 314720-E 314721-D 314723-D 314724-D 314725-D 315545-D 316343-C 316433-D 318637-A 317359-B 315023-D 315015-D
Hard copy technical manuals

You can print selected technical manuals and release notes free, directly from the Internet, using the following directions:
.
How to get help
91
Step 1 2 3 4
Action Go to http://www.nortel.com/support. Scroll to and select the product for which you require documentation. Locate the specic category and model or version for your hardware or software product. Use Adobe* Acrobat Reader* to open the manuals and release notes. (You can go to Adobe Systems at http://www.adobe.com to download a free copy of Adobe Acrobat Reader.) Search, then print onto most standard printers, any desired document sections. End
How to get help

If you purchased a service contract for your Nortel product from a distributor or authorized reseller, contact the technical support staff for that distributor or reseller for assistance. If you purchased a Nortel service program, contact Nortel Networks Technical Support. To obtain contact information online, go to http://www.nortel.com/contactus and click on the Technical Solutions hyperlink. From the Technical Support page, you can open a Customer Service Request online or nd the telephone number for the nearest Technical Solutions Center. If you are not connected to the Internet, you can call 1-800-4NORTEL (1-800-466-7835) to learn the telephone number for the nearest Technical Solutions Center. An Express Routing Code (ERC) is available for many Nortel products and services. When you use an ERC, your call is routed to a technical support person who specializes in supporting that product or service. To locate an ERC for your product or service, go to http://www.nortel.com/erc.
.
.
Nortel Metro Ethernet Routing Switch 8600
Release Notes Software Release 4.0.4.3

Copyright 2007, Nortel Networks All Rights Reserved. Publication: NN46220-406 Document status: Standard Document version: 01.01 Document date: 5 January 2007 To provide feedback or report a problem in this document, go to http://www.nortel.com/documentfeedback. The information in this document is subject to change without notice. The statements, congurations, technical data, and recommendations in this document are believed to be accurate and reliable, but are presented without express or implied warranty. Users must take full responsibility for their applications of any products specied in this document. The information in this document is proprietary to Nortel Networks Inc. The software described in this document is furnished under a license agreement and may be used only in accordance with the terms of that license. The software license agreement is included in this document. Nortel Networks, the Nortel Networks logo, and the Globemark are trademarks of Nortel Networks. Adobe and Acrobat Reader are trademarks of Adobe Systems Incorporated. Microsoft, Windows, and Windows NT are trademarks of Microsoft Corporation. All other trademarks are the property of their respective owners. This document is sourced in Canada and the United States of America.

NN46220-406 323557-B 01 PDF

Transféré par

Informations du document

Description originale:

Titre original

Copyright

Formats disponibles

Partager ce document

Partager ou intégrer le document

Options de partage

Avez-vous trouvé ce document utile ?

Ce contenu est-il inapproprié ?

Droits d'auteur :

Formats disponibles

NN46220-406 323557-B 01 PDF

Transféré par

Droits d'auteur :

Formats disponibles

Nortel Metro Ethernet Routing Switch 8600

Release Notes Software Release 4.0.4.3

Restricted rights legend

Nortel Networks Inc. software license agreement

Nortel Networks Condential

Nortel Networks Condential

Metro Ethernet Routing Switch 8600 Software Release 4.0.4.3

Nortel Networks Condential

8 Metro Ethernet Routing Switch 8600 Software Release 4.0.4.3

Important notes before upgrading to this release

Nortel Networks Condential

Important notes before upgrading to this release 9

File names for this release

p80c4043.img p80c4043.des p80a4043.mib p80a4043.mib .zip p80p4043.dld p80t4043.dld

Nortel Networks Condential

10 Metro Ethernet Routing Switch 8600 Software Release 4.0.4.3

Module or file type Linux image HP Unix image

Description Device Manager software image Device Manager software image

File name jdm_5990_linu x.sh jdm_5990_hpu x_ pa-risc.sh

Fixes from earlier releases

Downgrading the switch

Nortel Networks Condential

Important notes before upgrading to this release 11

Ethernet Services Unit upgrade requirements

Device Manager installation

Nortel Networks Condential

12 Metro Ethernet Routing Switch 8600 Software Release 4.0.4.3

Supported Release 4.0.4.3 software capabilities

Supported software capabilities

Nortel Networks Condential

Important notes before upgrading to this release 13

Nortel Networks Condential

14 Metro Ethernet Routing Switch 8600 Software Release 4.0.4.3

Unsupported Metro Ethernet Routing Switch 8600 Enterprise-based features

Release 4.x and R-series module system requirements overview

Nortel Networks Condential

Important notes before upgrading to this release 15

SMLT network design considerations

Keep CP-limit enabled on SMLT ports; change multicast-limit value to 6000:

Nortel Networks Condential

16 Metro Ethernet Routing Switch 8600 Software Release 4.0.4.3

Enable drop untagged frames on SMLT links:

Operating the switch with the Metro ESM 8668 module

8010 and 8006 chassis

Nortel Networks Condential

Operating the switch with the Metro ESM 8668 module 17

Supported power supplies

Nortel Networks Condential

18 Metro Ethernet Routing Switch 8600 Software Release 4.0.4.3

General upgrade considerations

Copyright 2007, Nortel Networks

Nortel Networks Condential

General upgrade considerations 19

Dual CPU/SF upgrade process

Recommended boot conguration options

Nortel Networks Condential

20 Metro Ethernet Routing Switch 8600 Software Release 4.0.4.3

Recommended upgrade process

Hot-swapping the CPU/SF module or I/O modules

Upgrading the Metro Ethernet Routing Switch 8600 to Release 4.0.4.3

Before upgrading the software

Nortel Networks Condential