NN46220-406_323557-B_01.pdf

Nortel Metro Ethernet Routing Switch 8600

Release Notes — SoftwareRelease 4.0.4.3

ATTENTIONClicking 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: StandardDocument version: 01.01Document date: 5 January 2007

Copyright © 2007, Nortel NetworksAll Rights Reserved.

Restricted rights legendUse, 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 computersoftware, the rights of the United States Government regarding its use, reproduction, and disclosure are as set forthin the Commercial Computer Software-Restricted Rights clause at FAR 52.227-19.

Statement of conditionsIn the interest of improving internal design, operational function, and/or reliability, Nortel Networks Inc. reserves theright 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) orcircuit layout(s) described herein.

Portions of the code in this software product may be Copyright © 1988, Regents of the University of California. Allrights reserved. Redistribution and use in source and binary forms of such portions are permitted, provided that theabove copyright notice and this paragraph are duplicated in all such forms and that any documentation, advertisingmaterials, and other materials related to such distribution and use acknowledge that such portions of the softwarewere developed by the University of California, Berkeley. The name of the University may not be used to endorse orpromote products derived from such portions of the software without specific prior written permission.

SUCH PORTIONS OF THE SOFTWARE ARE PROVIDED "AS IS" AND WITHOUT ANY EXPRESS OR IMPLIEDWARRANTIES, INCLUDING, WITHOUT LIMITATION, THE IMPLIED WARRANTIES OF MERCHANTABILITY ANDFITNESS FOR A PARTICULAR PURPOSE.

In addition, the program and information contained herein are licensed only pursuant to a license agreement thatcontains restrictions on use and disclosure (that may incorporate by reference certain limitations and noticesimposed by third parties).

Nortel Networks Inc. software license agreementThis Software License Agreement ("License Agreement") is between you, the end-user ("Customer") and NortelNetworks Corporation and its subsidiaries and affiliates ("Nortel Networks"). PLEASE READ THE FOLLOWINGCAREFULLY. YOU MUST ACCEPT THESE LICENSE TERMS IN ORDER TO DOWNLOAD AND/OR USE THESOFTWARE. USE OF THE SOFTWARE CONSTITUTES YOUR ACCEPTANCE OF THIS LICENSE AGREEMENT.If you do not accept these terms and conditions, return the Software, unused and in the original shipping container,within 30 days of purchase to obtain a credit for the full purchase price.

"Software" is owned or licensed by Nortel Networks, its parent or one of its subsidiaries or affiliates, and iscopyrighted 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 wholeor partial copies. Nortel Networks grants you a license to use the Software only in the country where you acquired theSoftware. You obtain no rights other than those granted to you under this License Agreement. You are responsible forthe 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 theSoftware 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 Customerfurnished equipment ("CFE"), Customer is granted a nonexclusive license to use Software only on suchhardware or CFE, as applicable. Software contains trade secrets and Customer agrees to treat Software asconfidential information using the same care and discretion Customer uses with its own similar information that itdoes not wish to disclose, publish or disseminate. Customer will ensure that anyone who uses the Softwaredoes 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 engineeror otherwise translate the Software; c) create derivative works or modifications unless expressly authorized; or d)sublicense, rent or lease the Software. Licensors of intellectual property to Nortel Networks are beneficiaries ofthis provision. Upon termination or breach of the license by Customer or in the event designated hardware orCFE is no longer in use, Customer will promptly return the Software to Nortel Networks or certify its destruction.Nortel Networks may audit by remote polling or other reasonable means to determine Customer’s Softwareactivation or usage levels. If suppliers of third party software included in Software require Nortel Networks toinclude additional or different terms, Customer agrees to abide by such terms provided by Nortel Networkswith 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 DISCLAIMSALL WARRANTIES (CONDITIONS) FOR THE SOFTWARE, EITHER EXPRESS OR IMPLIED, INCLUDING,BUT NOT LIMITED TO THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR APARTICULAR PURPOSE AND ANY WARRANTY OF NON-INFRINGEMENT. Nortel Networks is not obligatedto provide support of any kind for the Software. Some jurisdictions do not allow exclusion of implied warranties,and, in such event, the above exclusions may not apply.

3. Limitation of Remedies. IN NO EVENT SHALL NORTEL NETWORKS OR ITS AGENTS OR SUPPLIERS BELIABLE FOR ANY OF THE FOLLOWING: a) DAMAGES BASED ON ANY THIRD PARTY CLAIM; b) LOSSOF, OR DAMAGE TO, CUSTOMER’S RECORDS, FILES OR DATA; OR c) DIRECT, INDIRECT, SPECIAL,INCIDENTAL, PUNITIVE, OR CONSEQUENTIAL DAMAGES (INCLUDING LOST PROFITS OR SAVINGS),WHETHER IN CONTRACT, TORT OR OTHERWISE (INCLUDING NEGLIGENCE) ARISING OUT OF YOURUSE OF THE SOFTWARE, EVEN IF NORTEL NETWORKS, ITS AGENTS OR SUPPLIERS HAVE BEENADVISED OF THEIR POSSIBILITY. The foregoing limitations of remedies also apply to any developer and/orsupplier of the Software. Such developer and/or supplier is an intended beneficiary of this Section. Somejurisdictions do not allow these limitations or exclusions and, in such event, they may not apply.

4. General

a. If Customer is the United States Government, the following paragraph shall apply: All Nortel NetworksSoftware available under this License Agreement is commercial computer software and commercialcomputer software documentation and, in the event Software is licensed for or on behalf of the United StatesGovernment, the respective rights to the software and software documentation are governed by NortelNetworks standard commercial license in accordance with U.S. Federal Regulations at 48 C.F.R. Sections12.212 (for non-DoD entities) and 48 C.F.R. 227.7202 (for DoD entities).

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

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

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

e. The terms and conditions of this License Agreement form the complete and exclusive agreement betweenCustomer and Nortel Networks.

f. 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 ofthe state of New York.

5

Contents

Metro Ethernet Routing Switch 8600 Software Release 4.0.4.3 7Important notes before upgrading to this release 8

Locating documentation 8File names for this release 9Fixes from earlier releases 10Downgrading the switch 10Ethernet Services Unit upgrade requirements 11Device Manager installation 11Supported Release 4.0.4.3 software capabilities 12Release 4.x and R-series module system requirements overview 14SMLT network design considerations 15

Operating the switch with the Metro ESM 8668 module 168010 and 8006 chassis 16

General upgrade considerations 18Configuration file requirements 19Dual CPU/SF upgrade process 19Hot-swapping the CPU/SF module or I/O modules 20

Upgrading the Metro Ethernet Routing Switch 8600 to Release 4.0.4.3 20Before upgrading the software 20Backing up the configuration and boot configuration files 21Verifying the boot-prom version 23Verifying the ESM status 24

Upgrading the software image 24Upgrading the Metro Ethernet Routing Switch 8600 environment with dual-home

rings 25Upgrading the software on a non-redundant Metro Ethernet Routing Switch

8600 CPU 25Upgrading the software on a redundant CPU for Warm Standby (Non HA) 28Upgrading the software on a redundant CPU for Hot Standby (HA) 33Upgrading Metro Ethernet Routing Switch 8600 and Ethernet Services Unit for

RRP 38Upgrading the ESM FPGA 39Updating Firmware revision on R-series modules 42Reformatting the 8692SF Flash from 16 MB to 40 MB 45

Nortel Metro Ethernet Routing Switch 8600Release Notes — Software Release 4.0.4.3

NN46220-406 01.01 Standard4.0.4.3 5 January 2007

Copyright © 2007, Nortel Networks Nortel Networks Confidential

.

6 Contents

New feature enhancements and changes 48Enhanced CLI commands 48

Hardware Support 51Supported standards, RFCs, and MIBs 51General configuration issues and considerations 53

Platform 53Provider Backbone Transport 54High-availability CPU 55ESU rings 55VLACP enabled on NNI ports 55IP static routes 56IS-IS 56OSPF 56CPU SSF management port 57Metro ESM 8668 58Local and remote UNI considerations 59Multi-service UNI ports 60Metro Ethernet Routing Switch 8600 QoS considerations 61Dual-home ring 63Legacy access ports (ESM Server ports) 64ESU and customer CPE management considerations 65Ethernet MTU size 65Transparent Domain Continuity tests 66MAC learning keys and 32-bit UNIs 68MLT and SMLT considerations 69Customer IP UNIs 71IP spoofing 71MSTP/RSTP 72QinQ 72

Scaling limits 73CRs fixed in Release 4.0.4.3 78CRs fixed in Release 4.0.4.2 78CRs fixed in Release 4.0.4.0 79Known issues and CRs 81

Platform 83PBT 85R-module UNI 87High Availability 88Dual-home ring 89

Documentation corrections 89Related publications 89Hard copy technical manuals 90How to get help 91




.

7

Metro Ethernet Routing Switch 8600Software Release 4.0.4.3

The release notes for Metro Ethernet Routing Switch 8600 Release 4.0.4.3describe file names, upgrade processes, and any known issues that existin this release. The information in these release notes is based on MetroEthernet Routing Switch 8600 Software Release 4.0.4.3 and Java DeviceManager (JDM) Release 5.9.9.

Unless otherwise specified, the term "switch" refers to the Metro EthernetRouting Switch 8600.

Note that the name "Metro Ethernet Passport 8600 Switch" is now known asthe "Metro Ethernet Routing Switch 8600," and the new name will appearin future documents.

The information in these release notes supersedes applicable information inother 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" (page20)

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



"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 releaseThe Metro Ethernet Routing Switch 8600 Software Release 4.0.4.3 doesnot support configuration files created with Enterprise Routing Switch 8600Software Release 3.7 software. Configuration files created with Release 3.7will not be supported until Release 4.1. Nortel recommends that you save abackup configuration before migrating to any new software release.

Locating documentationFor a complete list of related publications, refer to "Related publications"(page 89). The Metro Ethernet Routing Switch 8600 Release 4.0.4.3documentation suite is located on the documentation CD included with yoursoftware or on the Nortel technical documentation web site:

Step Action

1 Go to http://www.nortel.com/documentation

2 In the By Product Family section, click Metro Ethernet RoutingSwitch.

3 In the Metro Ethernet Routing Switch: General Availability section,scroll down to the Metro Ethernet Routing Switch 8600 Servicessection, then click Documentation.

—End—




.

http://www.nortel.com/documentation

Important notes before upgrading to this release 9

File names for this release

Supported Metro Ethernet Routing Switch 8600 software files

Module or file type Description File name

Boot configurationfile

Metro Ethernet Routing Switch 8600 boot configurationfile

boot.cfg

Configuration file Metro Ethernet Routing Switch 8600 configuration file config.cfg

MERS 8600 Images

Boot monitorimage

CPU and switch fabric firmware for the Metro EthernetRouting Switch 8600.

oe8b4043.img

Run-timeimage

Metro Ethernet Routing Switch 8600 image withVPN-based services supported on 8691SF, 8691omSF,and 8692omSF CPU modules.

oe8a4043.img

Run-timeimage for Rmodules

The Metro Ethernet Routing Switch 8600 image for Rmodules

oe8j4043.dld

Mezzanineimage

Onboard daughter card for the 8691omSF and8692omSF CPU module that is required to supportVLACP capabilities.

oe8m4043.dld

Metro ESM8668 image

The Metro Ethernet Routing Switch 8600 image forESM 8668 module provides Ethernet VPN, VLACP, andservice provider encapsulation capabilities.

oe8o4043.dld

3DES Encryption module, which allows you to use Secure Shell(SSH)

p80c4043.img

DES/SNMPv3image

Encryption module, which allows you to use the Privacyprotocol with SNMPv3

p80c4043.des

MIB Metro Ethernet Routing Switch 8600 MIB p80a4043.mib

MIB (zip file) zip file containing the MIB file p80a4043.mib.zip

POS Ethernetcode

Metro Ethernet Routing Switch 8600 POS Ethernet Codev4.0

p80p4043.dld

ATM Ethernetcode

Metro Ethernet Routing Switch 8600 ATM Ethernet Codev4.0

p80t4043.dld

JDM Images

Solaris forSPARC image

Device Manager software image jdm_5990_solaris_sparc.sh

MicrosoftWindowsimage

Device Manager software image jdm_5990.exe




.


Module or file type Description File name

Linux image Device Manager software image jdm_5990_linux.sh

HP Unix image Device Manager software image jdm_5990_hpux_ pa-risc.sh

8010 and 8006 chassis data performance

Module type Standard Slot (S1 and S10)[full duplex]

High Performance Slot(S2-4, S7-9) [full duplex]

Pre-E, E and M series 16Gbps 16Gbps

8630GBR, R series 16Gbps 60Gbps

8683XLR, R series 16Gbps 60Gbps

The following message displays on the console when an R-series module isinserted 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 9only. Insertion of an 8630GBR or 8683XLR into slot 1 or 10yields 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 backplanecompatible with existing pre-E, E- and M- series, and new R-series modulessupporting high performance in all slots, is shipping with all new chassispurchased.

Fixes from earlier releasesRelease 4.0.4.3 contains fixes from Metro Ethernet Routing Switch 8600Software releases up to and including:

• Ethernet Routing Switch 8600 Release 4.0.3.2

• Metro Ethernet Routing Switch 8600 Release 3.6.2.0





Downgrading the switchDowngrades from Release 4.0.4.3 to an earlier release require a previouslysaved config file (boot.cfg and config.cfg). Prior to downgrading to a 3.x.xrelease, you must remove the R modules.




.


Ethernet Services Unit upgrade requirementsWhen you upgrade the Metro Ethernet Routing Switch 8600 to Release4.0.4.3, you must upgrade all the ESUs to the software release supportedby Metro Ethernet Routing Switch 8600 Release 4.0.4.3 due to an optimizedIP VLAN broadcast datapath change and other known issues.

Supported ESU images with Metro Ethernet Routing Switch 8600Release 4.0.4.0The Metro Ethernet Services Unit 1800 and 1850 provide a demarcationpoint between the customer network and the service provider network andsupports aggregation of multiple ports on a single ring or on a standaloneconnection point. The ESU maintains its own image and features andsupport varies from release to release.

Metro Ethernet Routing Switch 8600 Release 4.0.4.3 is compatible withthe ESU images as noted in the following table. Support for earlier ESUreleases of software is limited only to maintaining ESU ring services andESU standalone service during the Metro Ethernet Routing Switch 8600upgrade process. See the ESU release notes for procedures on how toupgrade your ESU 1800 and ESU 1850 after completing the upgradeprocess for the Metro Ethernet Routing Switch 8600.

Supported ESU Images

Hardware Release Images Release Images

Metro Ethernet RoutingSwitch 8600

4.0.0.x 4.0.x, 4.0.x.x(see Note1)

ESU 1800 3.0.x, 3.1.x 3.0.x, 3.1.x (see Note 2)

ESU 1850 2.2.x, 3.0.x, 3.1.x 2.2.x, 3.0.x, 3.1.x

Note 1: The L2 SW mode of ESU is supported with all Metro Ethernet RoutingSwitch 8600 releases.

Note 2: The ESU 3.1 release contains HW Rev. 2, which supports RTC.

Device Manager installationJava Device Manager (JDM) version 5.9.9 supports Metro EthernetRouting Switch 8600 Release 4.0.4.3. To install JDM on your PC, Nortelrecommends that you have a minimum of 256 RAM and 350 MB of availabledisk space.

Device Manager installation procedures are now standardized across allplatforms. In addition, the required Java Runtime Environment (JRE)(version 1.4.2) is now part of the JDM installation package and does notrequire a separate installation. The bundled JRE is used with this JDM onlyand should not affect other JAVA applications on the same system.




.


For Solaris, note that certain OS patches are required for JDM/JRE tofunction properly. Consult with SUN to install the appropriate OS patchesbefore you launch JDM. For more information about Device Manager, seeInstalling and Using Device Manager (317832-D).

Supported Release 4.0.4.3 software capabilitiesThis section describes supported software and hardware capabilities inMetro Ethernet Routing Switch 8600 Release 4.0.4.3, and contains thefollowing topics:

• "Supported software capabilities" (page 12)

• "Unsupported Metro Ethernet Routing Switch 8600 Enterprise-basedfeatures" (page 14)

Supported software capabilitiesMetro Ethernet Routing Switch 8600 Release 4.0.4.3 supports the followingfeatures:

• Triple Play: Mixed Service Type - Ethernet VPN, IP Unicast, IP Multicast

• High-Availability CPU for L2 and EVPN

• Ethernet VPN and IP traffic path selection per C-VID

• VoIP, Internet Access (and Management traffic) - IP Unicast

• Video Distribution - IP Multicast

• Multicast Services (PIM-SSM and IGMP only)

• IPMC routing: PIM-SSM with IGMP channel table for SSM (static SSMfor IGMP v2)

• IGMP Access Control List Filters on legacy and ESM ports

• Global filters (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 MetroEthernet Routing Switch 8600 UNIs

• Enhanced Ring Resiliency Protocol (single-home rings only)

• Dual-home Layer 2 ESU ring into two Metro Ethernet Routing Switch8600s (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 classification for Metro Ethernet Routing Switch8600 stacked VLAN)

— QinQ(2) (dual tag classification for Metro Ethernet Routing Switch8600 stacked VLAN)

• Multi-Service ports (multiple UNI IDs on the same ESM port)

• Local UNI switching

• Different MAC aging timer configuration 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 configurations

• 50 millisecond Ethernet access ring with Metro ESU 1800 and 1850modules (50 ms access ring failover)

• 50 millisecond Ethernet Trunk MLT failover (with Mezzanine daughtercard installed on the 8691omSF, or 8692omSF CPU (SMLT links do notsupport VLACP and 50 ms failover.)

• Support point-to-point, point-to-multipoint, and multipoint-to-multipointconnectivity options

• Policing in 64k increments - two rate 3-color marker

• Configurable token bucket depth

• Ingress Multicast and Broadcast Policing in 64k increments

• Service Provider 4 classes of service with DSCP, and p-bit VLAN criteriafor COS classification

• Statistics and SLA functionality support

• Diagnostic services, including port mirroring, PCAP, and ping snoop (onNNI and legacy ports only)

• RMON on NNI ports (on NNI and legacy ports only; stats are not perVPN)

• Security services (Radius, SNMP-V3, SSL)




.


Unsupported Metro Ethernet Routing Switch 8600Enterprise-based featuresWhen you operate the Metro Ethernet Routing Switch 8600 Release 4.0.4.3as a VPN Metro Aggregation switch, the following Enterprise-based featuresare 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 ringthrough ESM ports

• RMON for ESM 8668 ports, including VPN-based UNIs andIP-Customer-VLAN UNIs

• MAC-flap-time-limit for local TLS access ports, ESU standalone, ESUring through ESM 8668 ports

• Web-server access for VPN information, OPM information (includingerrors and statistics), Access UNI information

• VLACP not supported on MLT ports used as IST links for SMLTaggregation 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 fileson the switch flash memory

Release 4.x and R-series module system requirements overviewNortel recommends installing R modules in high performance slots in eitherthe existing chassis, or high performance chassis. Details can be found inthe section 8010 and 8006 chassis.

Nortel requires using the 8692 CPU/SF in systems with R-series modulesinstalled to support maximum performance. A warning message isdisplayed on the console if R-series modules are running in a system witha 8691 CPU/SF:#CPU5 [06/28/05 09:19:23] HW WARNING For maximum performanceand support, the 8692SF is required for use of the 8630GBRand 8683XLR. Use of an 8630GBR or 8683 XLR with the8690/8691SF fabric is not a recommended configuration andcontinued use may result in an unacceptable level of trafficoversubscription.




.


Note that the 8690 CPU/SF is not supported in Metro Ethernet RoutingSwitch 8600 4.x.x.x

SMLT network design considerationsUse this procedure when designing an SMLT network. For more informationabout SMLT, see Network Design Guidelines (313197-D)

Step Action

1 Ensure proper IST connectivity; define a separate VLAN for the ISTprotocol:

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 theIST ports:

config ethernet <slot|port> cp-limit disable

3 Keep CP-limit enabled on SMLT ports; change multicast-limit valueto 6000:

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

Nortel recommends that CP limit is enabled on SMLT ports to protectthe SMLT aggregation switches against unforeseen DOS attacks.

4 Enable loop detect on SMLT ports:

config ethernet <slot/port> loop-detect enable actionport-down

For Release 4.0.4, Nortel recommends that you ENABLE loop detectwith the action port-down on your SMLT ports (do not enable it on ISTports); this recommendation is in direct contrast to earlier releases.Be aware that loop-detect will disable ports that see flapping MACaddresses between the correct port and the looping port. In certaincircumstances correct ports can get disabled. Disable loop-detecton 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 anddrop untagged frames to ensure that SMLT client switches withdefault configurations will not adversely affect SMLT aggregationswitch behavior.




.


6 Enable drop untagged frames on SMLT links:

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

—End—

Operating the switch with the Metro ESM 8668 moduleThe Metro Ethernet Services Module (Metro ESM 8668) supports NortelMetro Ethernet Solutions integration with the Metro Ethernet Routing Switch8600 backplane fabric. The Metro ESM 8668 module is compatible withmost legacy I/O modules (including the Ethernet Routing Switch 8608 SXE)and emulates the enhanced Ethernet VPN services that are also providedby the Optical Metro 1000 family product lines.

When you operate the Metro Ethernet Routing Switch 8600 with the MetroESM 8668 module installed, in combination with Metro Ethernet RoutingSwitch 8600 Release 4.0.4 software, the switch becomes a VPN MetroAggregation switch. Metro Ethernet Routing Switch 8600 Release 4.0.4adds service provider (SP) encapsulation services (VPN-type service) andVirtual LACP (VLACP) capability. VLACP is an extension to LACP, usedto detect end-to-end failure for MLT links within 50 milliseconds (ms). Anonboard daughter card for the 8692omSf and 8691omSf CPU is required tosupport 50 ms VLACP capabilities.

If you are using the Metro Ethernet Routing Switch 8600 software for itsEnterprise-specific capabilities, refer to the Release Notes for the EthernetRouting Switch 8000 Series Switch Software Release 4.0.1.0 (part number317177-C).

8010 and 8006 chassisRelease 4.x provides an enhanced set of features and functionality for theMetro Ethernet Routing Switch 8600, including new high-density modulesand switch fabrics for increasing the switch fabric performance to 512 Gbps.

The new R-series modules offer increased port density and performanceover the existing pre-E, E and M-series modules. However, for customerswith existing 8010 and 8006 chassis, it is important to introduce the conceptof standard and high performance slots. An R-series module installed ina standard slot will deliver increased port density, and an R-series moduleinstalled in a high performance slot will deliver increased performance aswell.




.

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 801010-slot chassis and slots 2 to 4 of the 8006 six-slot chassis operate at highperformance. R-series modules inserted into slot 1 and slot 10 of the 8010chassis, and slot 1 of the 8006 chassis operate at standard performance.Refer to "8010 and 8006 chassis data performance" (page 10) for relativedata performances per slot with two fabrics installed in the existing 8010and 8006 chassis.

If you have an existing installed base of ESM 8668 modules, and you arecurrently operating your switch nodes with Metro Ethernet Routing Switch8600 release 3.5.x, be sure to verify that you have up-to-date boot-proms onyour ESM 8668 blades. To verify your ESM 8668 boot-prom version, referto "Verifying the boot-prom version" (page 23).

Supported power suppliesThe 8010co, 8010, and 8006 chassis each provide three bays for installingpower supplies. The following power supplies are available for thesechassis:

• 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 DCpower supplies. A minimum of two power supplies is required for the 8010cochassis. You can also install an additional power supply for redundancy.

The 8010co chassis requires an air intake bezel. If you installed Model8005AC power supplies (1500W) in the 8010co chassis with an air intakebezel imprinted with 312096-A, or if you have difficulty installing the bezelover the 8005AC power supplies, you can order a modified bezel (OrderCode DS1411027).

When configuring a Metro Ethernet Routing Switch 8600 series system,you should consider total power consumption to ensure proper systemperformance. The total input power consumption of the components,including modules and fan trays, must not exceed the output power rating ofthe power supply. To determine the minimum number of power supplies toinstall for the system:

• Add the total (3.3 v and 12 v) input power consumption (wattage) for allcomponents including modules and fan trays assemblies. For moreinformation, see Installing and Maintaining the Metro Ethernet RoutingSwitch 8600 Series Chassis (320417-B).




.


• Refer to the output power rating of the power supply, based on the inputconnection. See your power supply installation manual for the outputpower ratings and other technical specifications.

General upgrade considerationsThis section contains guidelines you should consider when upgrading toMetro Ethernet Routing Switch 8600 Release 4.0.4.3.

CAUTIONDo not use a software image prior to the Metro 8600 Release3.6.0.0 with the 8692omSF module. If you downgrade thesoftware (specifically the boot monitor image, oe8b3600.img) tothe previous release 3.5.3.2 or earlier, it may become necessaryto return the module to Nortel, due to boot flash corruption.

CAUTIONThe configuration file generated with Metro Ethernet RoutingSwitch 8600 Software Release 4.0.4.3 contains options that arenot backward compatible with Metro Ethernet Routing Switch 8600Software Releases 3.5.x or 3.6.x. Loading a 4.0.x.x configurationfile on a 3.5.x or 3.6.x run-time image generates errors and causesthe image to abort loading the configuration file.As a precaution, before you upgrade or downgrade your switchsoftware, make a copy of the switch configuration file specified inthe boot.cfg file using the following command:

copy /flash/config.cfg /<device>/con-fig_backup.cfg

where device can be PCMCIA, flash, or an IP host.

• A system with or without R modules installed can operate using Release4.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 EthernetRouting Switch 8600 release 3.6.0 and greater. The 8691omSF CPU/SFmodules have no release restrictions.

• After you upgrade the Metro Ethernet Routing Switch 8600 software,save the configuration file.

• Nortel does not support different software versions on a redundantCPU/SF configuration. For example, you cannot have a primary CPU/SFrunning 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 files on the onboard flash or PCMCIA, verify flashcapacity before downloading the files.




.

General upgrade considerations 19

This section includes the following topics:

• "Configuration file 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)

Configuration file requirementsThe R-series modules require loading an I/O dld image file onto eachmodule. By default this file is named oe8j4043.dld and is loadedautomatically. If you plan to rename this file, you must enter the followingcommand for each R-module slot in the boot.cfg configuration file:

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 processThis section describes the recommended boot configuration options andthe recommended upgrade process.

Recommended boot configuration optionsThere is no hitless upgrade supported at this time, therefore a systemupgrade results in losing some customer traffic data.

In a system with dual Metro Ethernet Routing Switch 8691/92 CPU/SFmodules, a save-to-standby boot flag option is normally enabled. Thisoption, if enabled, automatically saves the configuration and boot files toboth standby and primary CPUs. The following example shows how toenable this option (default operation is disabled):

MERS-8610:5# config bootconfig flags savetostandby trueMERS-8610:5# save bootconfigMERS-8610:5# boot -y

If you are using the out-of-band Ethernet port of the 8691/92 CPU/SFmodule for management, Nortel recommends adding a virtual IP address.This allows access to the primary CPU, regardless if the primary CPU is slot5 or slot 6. To add a virtual IP address, enter the following CLI command,and save the configuration.

config sys set mgmt-virtual-ip <ipaddr/mask>




.


Recommended upgrade processIn dual CPU/SF systems, upgrade the standby CPU/SF first, and thenthe primary CPU. When the standby CPU/SF upgrade is complete, theprimary CPU/SF is rebooted (prior to upgrading the primary CPU/SF) toallow the system to manually switch over to the newly upgraded CPU/SF. Ifan unexpected problem occurs, the system reverts to the previous CPU/SFwith the older release. This process ensures that at least one CPU/SF isfully operational during the upgrade process.

Hot-swapping the CPU/SF module or I/O modulesWhen hot-swapping the active CPU/SF module in a Metro Ethernet RoutingSwitch 8600 with redundant CPU/SF modules, wait until the redundantCPU/SF module is stabilized before inserting other modules. The redundantCPU/SF module displays a logon prompt on the console screen. If noconsole connection is available, wait for at least 30 seconds before insertingthe 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 thenew CPU/SF becomes the primary CPU/SF.

CAUTIONDo not hot-swap or insert modules in a Ethernet Routing Switch8000 Series chassis while the switch is booting, as the module maynot be recognized and a module initialization failure may occur.

Upgrading the Metro Ethernet Routing Switch 8600 to Release4.0.4.3

This section provides instructions for upgrading the enterprise EthernetRouting Switch 8600 or the Metro Ethernet Routing Switch 8600 to supportthe Metro Ethernet Routing Switch 8600 Release 4.0.4.3 software image.After completing the software upgrade, the switch can operate as anaggregation device in the Metro Ethernet Network (MEN).


• "Before upgrading the software" (page 20)

• "Upgrading the software image" (page 24)

Before upgrading the softwareBefore upgrading to the Metro Ethernet Routing Switch 8600, you must:

• Read the entire upgrade procedure before attempting to upgradethe switch. This procedure can cause interruption of normal switchoperation.




.

Upgrading the Metro Ethernet Routing Switch 8600 to Release 4.0.4.3 21

• Back up your runtime configuration and boot configuration beforestarting 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 configuration file generated with software Release 4.0.4.3contains options that may not be backward compatible with priorsoftware releases. Loading a 4.0.4.3 configuration file on anyprior release run-time image may generate errors and cause theconfiguration file to abort loading. If this happens, a factory defaultconfiguration will be loaded.

— Before you run a copy command using TFTP to overwrite an existingfile with the same name on the flash or PCMCIA, be aware that ifthe file transfer fails, the file on the flash or PCMCIA is deleted. Forexample, if you issue the commandcopy 111.111.1.11:oe8a4043.img /flash/oe8a4043.img

and the server is not available or the file on the server does notexist, the oe8a4043.img file is deleted on the flash (if previouslyexisting). To preserve the original file, you can either rename ormake a backup copy of this file on the PCMCIA or flash before youbegin the copy process.

— When installing files on the onboard flash or PCMCIA, make surethat you verify capacity before you download the files.

— Nortel recommends that you save a copy of the boot.cfg file in the/flash directory. During bootup, if the /flash/boot.cfg file isnot present, and if a PCMCIA card is present, the Metro EthernetRouting Switch 8600 searches for boot.cfg on the PCMCIA card.

If a PCMCIA card is not present, or if boot.cfg is not present onthe PCMCIA or not present on the flash, the Metro Ethernet RoutingSwitch 8600 boots using a default boot-configuration setting.

If you are using a PCMCIA card manufactured by SanDisk, the MetroEthernet Routing Switch 8600 may not access /pcmcia/boot.cfg duringbootup. This limitation occurs only when accessing the SanDisk deviceafter bootup.

Backing up the configuration and boot configuration filesYou can use any of the following methods to back up the configuration andboot configuration files.

• back up using an FTP client

• back up using TFTP




.


• back up using the copy command from flash to PCMCIA

Configuring FTP and TFTP protocolsYou must enable the FTP and TFTP boot flag options if you want to useFTP or TFTP for backing up your files. To configure the FTP and TFTPboot flag options:

Step Action

1 Enter the following command to check if the FTP and TFTP flagoptions are enabled:

show bootconfig flags

2 If the FTP boot flag option is set to false and you want to enableit, enter the following command:

config boot flags ftp true

3 If the TFTP boot flag option is set to false and you want to enableit, enter the following command:

config boot flags tftp true

4 If you changed the boot flag options, enter the following command tosave the boot configuration file for the changes to take effect.

save bootconfig

—End—

Backing up using copyUse the following procedure to back up your configuration files using thecopy command.

Step Action

1 To verify the configuration file name that you are using, enter thefollowing command. By default, the configuration file name isconfig.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 configuration files using one of the following two methods.

• For copying files to PCMCIA, ensure that you have a PCMCIAcard installed, and then copy the files from flash to PCMCIA




.

Upgrading the Metro Ethernet Routing Switch 8600 to Release 4.0.4.3 23

using the following commands. The default configuration file isconfig.cfg.

copy /flash/config.cfg /pcmcia/

copy /flash/boot.cfg /pcmcia/

• For copying files to a remote TFTP server, enter the followingcommands.

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 versionThis describes verifying current boot-prom version for the ESM 8668modules.

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.dldESM Software Version: 3.5.3.2OE012ESM Boot PROM Version: 3.5.3.0OEESM FPGA version: 16ESM Image Build Date: (is the date stamp supplied on theboot prom image)

• ESM Image Name is the name of the dld driver, loaded by the ESMmodule.

• ESM Software Version is the loaded software version (name and versioncan be different).

• ESM Boot PROM Version is the current boot-prom version.




.


CAUTIONIf the ESM boot-prom version is blank or if the version shows3.6.0.0 with no appended "b<XX>" number (XX is any numberfrom 01 to 99), the Metro ESM 8668 boot-prom is not up todate. Contact Customer Support for assistance with upgradingthe ESM boot prom.

Verifying the ESM statusWhen you upgrade the ESM boot-prom, enter the following command tocheck 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 notreboot or reset if you see this message.

• ESM OPERATIONAL the ESM blade is in normal operation state. If thismessage appears, you can reboot switch or reset ESM blade if required.

• ESM BOOT the ESM blade is in the boot state and loading the ESMdrivers.

• ESM CONFIG the ESM blade is loading the ESM configurations.

Upgrading the software imageThis section describes how to upgrade previous Ethernet Routing Switch8600 and Metro Ethernet Routing Switch 8600 configurations to MetroEthernet Routing Switch 8600 software release 4.0.4.3.

Before upgrading the switch from Metro Ethernet Routing Switch 8600release 3.5.1.x to Metro Ethernet Routing Switch 8600 release 4.0.4.3,confirm that the current ESM 8668 boot-prom version is correct.


• "Upgrading the Metro Ethernet Routing Switch 8600 environment withdual-home rings" (page 25)

• "Upgrading the software on a non-redundant Metro Ethernet RoutingSwitch 8600 CPU" (page 25)

• "Upgrading the software on a redundant CPU for Warm Standby (NonHA)" (page 28)

• "Upgrading the software on a redundant CPU for Hot Standby (HA)"(page 33)

• "Upgrading Metro Ethernet Routing Switch 8600 and Ethernet ServicesUnit 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 withdual-home rings

When upgrading dual-home ring environments, Nortel recommends thefollowing 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 first.

• Wait 60 seconds for the ring to return to normal and traffic to resumeproperly.

• Upgrade the secondary dual-home ring switch.

Upgrading the software on a non-redundant Metro Ethernet RoutingSwitch 8600 CPU

Before upgrading your non-redundant CPU, Nortel recommends that youback up your configuration files as follows:

• Copy the configuration file currently used by the switch in memory byentering the following command:

save config file /<device>/<config file name>

• Copy the configuration file specified by the boot.cfg file by entering thefollowing command:

copy /<device>/<config file name> /<device>/<backup configfile name>

where device is flash or PCMCIA.

• Copy the current boot.cfg file by entering the following command:

copy /<device>/<boot.cfg file name> /<device>/<backupboot.cfg file name>

where device is flash or PCMCIA.

If your boot-configuration is configured to support FTP or TFTP, you can useeither TFTP or FTP file transfer tools to upload the images to the MetroEthernet Routing Switch 8600. Refer to your FTP or TFTP applicationguides on how to upload an image to the Metro Ethernet Routing Switch8600.




.


The following procedure describes how to upgrade the non-redundant CPUwith the new software image from the PCMCIA or from the TFTP server:

Step Action

1 Download the software image to a TFTP server or to a PCMCIA card.

2 Prior to copying the software images over to the switch flash system,verify flash capacity before proceeding with the next steps. To viewthe capacity available at the console port, type dir to list all fileson the flash. The total capacity, total used, and total free bytes aredisplayed at the bottom of the directory list. For release 4.0.4.3,Nortel recommends you have a minimum of 12 MB free space toupload files needed for the upgrade procedure.

3 Copy the boot image and the software image to the switch flashfile system.

a. To copy the boot image and the software image from thePCMCIA 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 TFTPserver, 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 duringthe initial upgrade procedure. If you have a server available, youcan use the option to boot this image from the TFTP server instep 7 instead of copying the image to flash.

4 Verify that the software has been copied to the CPU by using theCLI command:

dir




.


5 Use the following command to change the primary application imagefor the switch:

config bootconfig choice primary image-file/<location>/filename

For example, use the following command to change the primaryimage file to oe8a4043.img:

config bootconfig choice primary image-file /flash/

oe8a4043.img

6 Save the boot configuration file using the following command:

save bootconfig

7 Boot the switch with the boot-monitor image you downloadedpreviously in step 3:

boot <source>:<absolute path of boot monitor image>

For example, enter the following command to boot the oe8b4043.imgfile from flash:

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 MonitorFLASH image. Do NOT turn off power or press resetuntil this procedure is completed. Otherwise the cardmay be permanently damaged!!!

After the bootprom upgrade is complete, the CPU/SF that wasupgraded now reboots. If the primary image-file is correct, the switchboots the new 4.0.4.3 software image, and the default banner nowdisplays 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-GeneralAvailability)*****************************************

If the CPU is not running the new software version, you must eitherrepeat the procedure if the CPU allows you to log in, or access theconsole port on the CPU to stop at the boot monitor and fix theproblem. Most common failures are caused by improperly typing theimage file name in the bootconfig file or by the software not beingpresent on the flash on the CPU.




.


Using the console port to stop at the boot monitor enables you tore-enter the bootconfig choice primary information, if improperlytyped, and enables you to verify that the software is present onthe flash of the standby CPU. If the software is not present on theCPU, copy it from PCMCIA card to the CPU. Then, you can eithercopy it to the flash or change the bootconfig choice primary to usethe PCMCIA card.

8 After the completion of the upgrade, save the boot.cfg file to flashusing the following save command:

save bootconfig

Bootconfig commands can change between releases; to capture thecorrect commands, Nortel recommends that you save the bootconfigand reboot after every upgrade to capture the new enhancements.

The configuration file generated with Metro Ethernet Routing Switch8600 software release 4.0.4.3 contains options that are not backwardcompatible with software release 3.5.x or 3.6.x. Loading a 4.0.4.3configuration file on a 3.5.x or 3.6.x run-time image generates errorsand causes the image to abort loading the configuration file.

—End—

Upgrading the software on a redundant CPU for Warm Standby (Non HA)The Metro Ethernet Routing Switch 8600 supports HA CPU mode inRelease 4.0.4.3. However, releases prior to 4.0.2.0 do not support HACPU. 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 andstandby CPUs and activate HA CPU during the upgrade.

ATTENTIONIf 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 MetroEthernet Routing Switch 8600 CPU configuration and how to enable HAmode.

Step Action

1 Connect to the master CPU of the Ethernet Routing Switch 8600CLI interface using the management console port, telnet session,or Device Manager.

2 Before you upgrade the software, use the following command tomake a backup copy of the switch configuration file:




.


copy /flash/config.cfg /<device>/config_backup.cfg

copy /flash/config.cfg <tftpaddress>:config_backup.cfg

where device can be PCMCIA or flash, 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 files on the onboard flash or PCMCIA, be sure toverify flash capacity before downloading the files.

3 Before you upload the Release 4.0.4.3 image files, use the dircommand to ensure that you have the available space. The outputis the following:

total: 16039936 used: 6825539 free: 9214397 bytes

ATTENTIONA minimum disk space of 12 megabytes is required for the following filesneeded for this upgrade:

• oe8b4043.img

• oe8a4043.img

• oe8o4043.dld

• oe8j4043.dld

4 To remove files, use the following remove command:

rm /flash/<filename>

5 Use one of the following methods to copy the files:

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 file is required if your switch has R modules.

** — This file is required if you have the optional CPU mezzanineonboard daughter card in the switch.

*** — This file is required for SNMPv3 and SSH encryption.




.


b. For TFTP using Device Manager, ensure that your TFTP serveris operating, then select Edit > File System > Copy File.Perform this task for each file name.

The File System > Copy File page opens.

To copy files:

• In the Source text box, enter the source file.

• In the Destination text box, enter the destination file.

• Select Start.

• Click Apply.

• The Result section displays a message saying InProgress.Click Refresh to get the final result.

c. For FTP, using an FTP client, connect to the management IPaddress of the master CPU and transfer the required files toflash. Ensure that the FTP boot flag option is enabled. Forinformation about enabling the FTP flag, see "Backing up theconfiguration and boot configuration files" (page 21).

6 Use one of the following methods to confirm that the software filesare copied to flash:

a. Using the CLI, enter the dir command.

b. Using Device Manager, select Edit > File System and click theFlash Files tab.

7 Before you copy the 4.0.4.3 image files, enter the following commandto log into the standby CPU.

peer telnet

8 Use the dir command to ensure that you have the minimumavailable space of 12 MBs.



10 Log out.

ATTENTIONThe login prompt should now be on the primary CPU.

11 Use one of the following methods to copy the image files from themaster CPU/SF to the standby CPU/SF. Note that the address ofCPU 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 files:




copy <tftp IP address>:oe8j4043.dld /flash/





** — This file is required if you installed the optional CPUmezzanine onboard daughter card in the switch.




To copy files:



• Select Start.

• Click Apply.

The Result section displays a message saying InProgress. ClickRefresh to get the final result.

c. For FTP, using an FTP client, connect to the management IPaddress (not internal IP address of 127.0.0.x) of the standbyCPU and transfer the required files to flash. Ensure that theFTP boot flag option is enabled. For information about enablingthe FTP flag, see "Backing up the configuration and bootconfiguration files" (page 21).

12 If you are upgrading from a release prior to 4.0.2.0 and want toenable HA mode, enter the following command, otherwise proceedwith 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 withthe 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 takeeffect.Layer 2 features, ARP and static route will be enabledin L2/L3 redundancy mode.Boot configuration is being saved on both master andstandby.config being saved to master and slave

13 Use one of the following methods to update the boot configurationfile 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 filenameof the primary run-time image (oe8a4043.img).

Click Apply.

14 Use one of the following methods to save the boot configuration onboth the master and the standby CPU:


save bootconfig standby boot.cfg

b. Using Device Manager, select Edit> Chassis > System.

• Click saveBootConfig.

• Click Apply.

• Click SaveSlaveBootconfig.

• Click Apply.

15 Enter the following command to verify that the changed primaryimage file settings are in the boot.cfg file:

more boot.cfg

16 Enter the following command to log into the standby CPU:

peer telnet




.



more boot.cfg

18 Enter the following command to boot the standby CPU with the newboot monitor image:


ATTENTIONWhile booting the standby CPU/SF, the telnet session hangs and needsto timeout. To quickly exit the peer telnet session, enter CTRL and theright-bracket character (]) at the same time. Next, enter q when promptedwith the telnet prompt.

For Warm Standby (Non HA), you must wait for the standby CPU/SFto completely boot and come back online.

19 Enter the following command to upgrade the master CPU/SFwith the new boot monitor image after the standby CPU/SF hascompleted booting.

CAUTIONThis step causes an interruption to user traffic.


—End—

Upgrading the software on a redundant CPU for Hot Standby (HA)The following procedure describes how to upgrade a redundant MetroEthernet Routing Switch 8600 CPU configuration operating in HighAvailability (HA) mode.

Step Action


2 Before you upgrade the software, use the following command tomake a backup copy of the switch configuration file:

copy /flash/config.cfg /<device>/config_backup.cfg




.


copy /flash/config.cfg <tftpaddress>:config_backup.cfg

where device can be PCMCIA or flash, 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 files on the onboard flash or PCMCIA, be sure toverify flash capacity before downloading the files.

3 Before you upload the Release 4.0.4.3 image files, use the dircommand to ensure that you have the available space. The outputis the following:

total: 16039936 used: 6825539 free: 9214397 bytes

ATTENTIONA minimum disk space of 12 megabytes is required for the following filesneeded for this upgrade:

• oe8b4043.img

• oe8a4043.img

• oe8o4043.dld

• oe8j4043.dld



5 Use one of the following methods to copy the files:

a. For TFTP using CLI, ensure that the TFTP server is operating,then enter the following commands:




*copy <tftp IP address>:oe8j4043.dld /flash/





** — This file is required if you have the optional CPU mezzanineonboard daughter card in the switch.





.




To copy files:



• Select Start.

• Click Apply.


c. For FTP, using an FTP client, connect to the management IPaddress of the master CPU and transfer the required files toflash. Ensure that the FTP boot flag option is enabled. Forinformation about enabling the FTP flag, see "Backing up theconfiguration and boot configuration files" (page 21).

6 Use one of the following methods to confirm that the software filesare copied to flash:

a. Using the CLI, enter the dir command.

b. Using Device Manager, select Edit > File System and click theFlash Files tab.

7 Before you copy the 4.0.4.3 image files, enter the following commandto log into the standby CPU.

peer telnet

8 Use the dir command to ensure that you have the minimumavailable space of 12 MBs.



10 Log out.

ATTENTIONThe logon prompt should now be on the primary CPU.

11 Use one of the following methods to copy the image files from themaster CPU/SF to the standby CPU/SF. Note that the address ofCPU 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 files:




copy <tftp IP address>:oe8j4043.dld /flash/





** — This file is required if you installed the optional CPUmezzanine onboard daughter card in the switch.




To copy files:



• Select Start.

• Click Apply.


c. For FTP, using an FTP client, connect to the management IPaddress (not internal IP address of 127.0.0.x) of the standbyCPU and transfer the required files to flash. Ensure that theFTP boot flag option is enabled. For information about enablingthe FTP flag, see "Backing up the configuration and bootconfiguration files" (page 21).

12 Use one of the following methods to update the boot configurationfile with the new 4.0.4.3 run-time image.



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 filenameof the primary run-time image (oe8a4043.img).

Click Apply.

13 From the primary CPU, change your bootconfig choice primaryimage file to the new run-time image file using the following CLIcommand:


14 Use one of the following methods to save the boot configuration onboth the master and the standby CPU:


save bootconfig standby boot.cfg

b. Using Device Manager, select Edit> Chassis > System.

• Click saveBootConfig.

• Click Apply.

• Click SaveSlaveBootconfig.

• Click Apply.


more boot.cfg

16 Enter the following command to log into the standby CPU:

peer telnet


more boot.cfg

18 Enter the following command to boot the standby CPU with the newboot monitor image.

For Hot Standby, you must boot the standby and master CPUs usingthe following sequence:

• Reboot the standby CPU/SF.

• Wait 10 seconds.

• Reboot the master CPU/SF before the standby CPU/SFcompletes booting.




.



ATTENTIONWhile booting the standby CPU/SF, the telnet session hangs and needsto timeout. To quickly exit the peer telnet session, enter CTRL and theright-bracket character (]) at the same time. Next, enter q when promptedwith the telnet prompt.

19 Enter the following command to upgrade the master CPU/SF withthe new boot monitor image.

ATTENTIONThis step causes an interruption to user traffic.


—End—

Upgrading Metro Ethernet Routing Switch 8600 and Ethernet ServicesUnit for RRP

The supported Ethernet Services Unit images include a new Enhanced RingResiliency feature to provide additional ring protection above the currentLayer 1 mechanism. This new protocol monitors and detects isolatedfailures not seen at the physical layer. For more information, see Configuringthe Metro Ethernet Routing Switch 8600 using the CLI (320746-A).

To upgrade ESUs attached to the Metro Ethernet Routing Switch 8600and to activate the Enhanced Resiliency Protocol in an existing MetroEthernet Routing Switch 8600 environment, Nortel recommends using thefollowing 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 8600Release 4.0.4.0" (page 11)). For more information on ESU upgradesand supported features, see Release Notes for the Metro EthernetServices Unit 1800 (317812-G) and Release Notes for the MetroEthernet Services Unit 1850 (320416-F).

• Enable RRP features on all ESUs.For the ESU 1800, see Configuring Ethernet VPN and IP VLAN Servicesin ESU 1800 using the CLI (321766-A).For the ESU 1850, see Configuring Ethernet VPN and IP VLAN Servicesin ESU 1850 using the CLI (321258-A).




.


• Start configuring with the first ESU in the ring. Nortel recommends thisprocess, but the order of which ESU to configure first is not important.

• Enable the RRP feature on each ESU to ensure that no ESUs aremissed.

If you upgrade the ESU prior to upgrading the Metro Ethernet RoutingSwitch 8600, VPLS broadcast issues may occur after the first ESU isupgraded. To resolve the broadcast condition, flush the TDI MAC table forall TDIs assigned to the ring (config tdi <id> flush-mac).

Upgrading the ESM FPGAThe ESM 8668 may require a Field Programmable Gate Array (FPGA)firmware revision upgrade. Nortel recommends that all ESM 8668 modulesbe upgraded to the latest firmware FPGA image when using 8692omSF or8692SF CPUs. The upgrade is optional if you are using the 8691 CPU. It ismandatory for chassis with multiple ESM 8668 modules to operate with thesame FPGA firmware revision (mixed firmware 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 chassisor reseating the ESM card to activate the new FPGA.

Nortel recommends doing the FPGA upgrade during a maintenancewindow. There should not be a significant amount of traffic running throughthe ESM card during the upgrade process.

Use the following steps to upgrade the FPGA firmware:

Step Action

1 Use one of the following CLI commands to determine the ESMFPGA (CPLD) version.

If the ESM FPGA version is 18, no upgrade is required. If the ESMFPGA version is a different version and a 8692omSF or 8692SFCPU 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 modulein slot 2:

MERS 8600:5# config esm 2 get-imageversion

ESM Image name: oe8o4000.dldESM Software Version: 4.0.0.0OE020ESM Boot PROM Version: 3.5.3.0OEESM FPGA Version: 18




.


ESM Image build date: Jul 7 2005

The ESM modules require loading an I/O dld image file onto eachmodule. By default, this file is named oe8o4002.dld and is loadedautomatically. If you plan to rename this file, you must enter thefollowing command for each ESM slot in the boot.cfg configurationfile:

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/oe8o4002.dld 2

MERS 8600:5# save bootconfig

2 If an update is needed, copy the latest ESM dld (oe8o4043.dld) onthe flash 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 thesame code version must be set as the primary image file in the bootconfig. Under normal circumstances, the Metro Ethernet RoutingSwitch 8600 is already upgraded to the latest revision of the code.

3 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 anESM FPGA in slot 7.

CAUTIONDo not reset the chassis or the ESM cards during theupgrade process. A reset permanently damages the ESMcard. A warning message is displayed as shown in thefollowing example.

MERS 8600:5# config esm 7 fpga-upgrade

################ ESM(Slot:7) FPGA Upgrade################## WARNING: You are about tore-program this ESM’s Water Works FPGA DoNOT turn off power, press reset or pull out thecard until this procedure is completed. Otherwisethe card may be permanently damaged

Do you want to continue (y/n) ? y

MERS 8600:5# boot

FPGA Upgrade in progress on one or more ESM’s.Wish toContinue (y/n) ? n




.


MERS 8600:5# reset

FPGA Upgrade in progress on one or more ESM’s.Wish toContinue (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. Wishto Continue (y/n) ? n

If multiple ESM cards exist in the same chassis, you can runsimultaneous FPGA upgrades for the different ESM cards. Repeatthe command for each slot where there is an ESM card.

4 After successfully starting the FPGA upgrade for each slot, boththe ESM console and the CP console display informational FPGAupgrade messages. A message is displayed when the upgradeprocess is complete.

FPGA is being Re-Programmed, Please wait for UpgradeComplete Indication...

MERS 8600:5# CPU5 [12/08/05 16:25:15] ESM INFO FPGAUpgrade initiated for ESM card on slot 7

If you use the command show log file tail, you can see inthe log file that the FPGA was updated:

MERS 8600:5# show log file tail

CPU5 [12/08/05 16:25:23] ESM INFO FPGA Upgradeinitiated for ESM card on slot 8Successfully Re-Programmed Water Works FPGA!

5 When the upgrade is complete, power cycle the chassis or reseatthe ESM card to activate the new FPGA.

If you do not power cycle the chassis or reseat the ESM card, thenew FPGA image does not take effect. Neither a soft reset of thecard nor the CLI boot command successfully upgrades the FPGA.

After a successful upgrade, the ESM FPGA (CPLD) revision numberis 18. To view the revision number and verify the upgrade wassuccessful, use one of the following commands:

show config module diag

or

show esm <slot #> get-imageversion

The entire upgrade process takes approximately 57 minutes tocomplete. If multiple cards are upgraded simultaneously, theupgrade time is the same for each card; the time is not cumulative.




.


—End—

Updating Firmware revision on R-series modulesA new Fabric Output Queue (FOQ) Field Programmable Gate Array (FPGA)firmware (version 267) is available with this release. This new firmwarerevision resolves a potential issue which existed since the initial releaseof the 8648GTR module, Release 4.0.1. Note that the two other FPGAdevices, BMC and DPC, are unchanged. This issue happens only in someheavily congested networks where a backpressure message has to be sentat ingress using the FOQ.

Although this issue is specific to the 8648GTR module, since the FOQdevice is on the base board of all R modules, you should review and updatefirmware revisions on every R module for consistency.

The FOQ update is not required if you are not using an 8648GTR module orif you don’t expect to encounter high congestion.

To verify the revision, see "Verifying firmware revisions on R modules8630GBR, 8683XLR, 8683XZR, and 8648GTR" (page 42). To updatethe revision, see "Updating firmware revisions on R modules 8630GBR,8683XLR, 8683XZR, and 8648GTR" (page 43).

Verifying firmware revisions on R modules 8630GBR, 8683XLR,8683XZR, and 8648GTRThe following devices on the R module baseboard require updates to theirfirmware and, if required, to their release revisions shown in "Device andFirmware R Module decimal values" (page 42).

Device and Firmware R Module decimal values

Device Firmware Revision Current filenames

FOQ 267 foq267.xsvf

DPC 184 dpc184.xsvf

BMC 776 bmc776.xsvf

Due to the file creation tool, new versions of the firmware files are the samesize as previous versions.

The new FOQ file is backward compatible with 4.0.x releases.




.


ATTENTIONYou can only update the firmware for one FPGA device on an R module at a time.For example, you must complete the update for the FOQ before you can updatethe BMC or DPC on the same R module.

Enter the following show command to check the current firmware revisionson the slot containing an R module. The following example displaysfirmware 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=0CLUE=0 F2I=0 F2E=0 FTMUX=0 CC=3 FOQ= 260 DPC= 180 BMC=770 MAC=4

If the firmware revisions are not equivalent to those in "Device and FirmwareR Module decimal values" (page 42), an update is required, otherwise nofurther action is necessary.

Updating firmware revisions on R modules 8630GBR, 8683XLR,8683XZR, and 8648GTR

ATTENTIONNortel strongly recommends that you use a direct console cable connection toupgrade the FPGA.

To update firmware revisions:

Step Action

1 Ensure that Release 4.0.4.3 is operating on the system.

2 Disable all ports on the module to upgrade.

3 Using TFTP or FTP, copy the files to the 8692omSF flash on theEthernet Routing Swich 8000 Series chassis that contain the Rmodule you are updating.

You can also complete this upgrade with the files on a PCMCIA card.

4 Enter the following command for the device type and slot-numbercontaining an R module that needs updating.

Repeat the command for each additional device type on an R modulethat needs updating.




.


You can only update the firmware for one FPGA device on anR module at a time. For example, you must complete the updatefor the FOQ before you can update the BMC or DPC on the sameR module. Do not open several Telnet or SSH sessions and try toupdate several device types simultaneously.

ATTENTIONOnce the update process begins, do not enter commands or reset themodule or switch during the process. If any failure occurs, retry theupdates or contact Nortel before resetting the module or switch.

Do not interrupt the update process, which is approximately tenminutes in length. Wait until the FPGA UPDATE SUCCESS messagedisplays for each slot you are updating. The success message isappended to the log file. Do not save the configuration file once theupgrade has started or before the switch reboots.

If you do not enter a file name, then the default file 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 minutesDon’t reset the card or box during the processA SUCCESS message will display on the console and willget appended to the log file upon completion of theupdate.MERS-8610:5# CPU5 [02/08/05 18:55:31] SW ERRORR-Module Slot<1> is unable to Process Async messagesand Slot Reset is Disabled!!MERS-8610:5# CPU5 [04/12/05 14:05:38] COP-SW INFO Slot1:FPGA UPDATE SUCCESS

ATTENTIONDisregard the message SW ERROR unable to Process Asyncmessages and Slot Reset is Disabled!! The messagedisappears after the system reboot.

Note that the show sys info asic command does not displayupdated firmware revisions until after you reboot.

5 Once all the modules have been updated, enter the followingcommand to reboot the system for the updates to take effect.




.


MERS-8610:5# boot -y

—End—

When the system reboots, the firmware revision is verified and if an updateis required, a warning message displays on the console:CPU5 [04/01/06 23:06:00] SW WARNING Slot 7 is running oldersoftware version(s) of FPGA. Please upgrade to the latestversion(s)CPU5 [04/01/06 23:06:00] SW WARNING FOQ FPGA currentrevision: 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 FOQFPGA.

• Perform the FPGA upgrade on your R modules. See "UpdatingFirmware revision on R-series modules" (page 42).

Reformatting the 8692SF Flash from 16 MB to 40 MBThe following sections describe how to upgrade from 16 MB to 40 MB andalso to downgrade from 40 MB to 16 MB.

Reformatting from 16 MB to 40 MBComplete the following procedure to upgrade from 16 MB to 40 MB flash:

Step Action

1 Complete the upgrade procedure in "Upgrading the software image"(page 24).


3 Enter the following command to connect to the standby CPU.

peer telnet

4 Enter the following command to back up all files to the PCMCIA card.

copy /flash/<src-file> /pcmcia/<dest-file>

5 Enter the following command to reformat the flash on the standbyCPU/SF.

format-flash

6 Reboot the standby CPU/SF.




.


boot /pcmcia/0e8a4043.img

ATTENTIONWhile booting the standby CPU/SF, the Telnet session hangs and needsto timeout. To quickly exit the peer Telnet session, enter CTRL and theright-bracket character (]) at the same time. Next, enter q when promptedwith the Telnet prompt.

7 After the standby CPU/SF is active again, enter the followingcommand to connect to the standby CPU.

peer telnet

8 Enter the following command to copy all files back from the PCMCIAcard to flash.

copy /pcmcia/<src-file> /flash/<dest-file>

9 Boot the system to activate the new configuration and image files.

boot -y

10 Enter the following command to connect to the standby CPU.

peer telnet

11 Confirm that the CPU is operational.

12 Enter the following command to verify that the changed primaryimage files and configuration file settings are in the boot.cfg file:

more boot.cfg

13 Log out of the standby CPU.

14 Enter the following command to back up all files to the PCMCIA card.

copy /flash/<src-file> /pcmcia/<dest-file>

15 Enter the following command to reformat the flash on the primaryCPU/SF.

format-flash

16 Reboot the primary CPU/SF.

boot /pcmcia/0e8a4043.img

CAUTIONThis step causes an interruption in traffic.




.


17 After the primary CPU is active again, enter the following commandto copy all files back from the PCMCIA card to flash.

copy /pcmcia/<src-file> /flash/<dest-file>

18 Boot the system to activate the new configuration and image files.

boot -y

—End—

Downgrading from 40 MB to 16 MBTo downgrade from 40 MB to 16 MB, use the following procedure:

Step Action

1 Copy your files from the flash to the PCMCIA card or a TFTP/FTPserver.

2 Downgrade the boot monitor with an earlier release of the software.

CAUTIONDo not use a software image prior to Metro 8600 Release3.6.0.0 with the 8692omSF module. If you downgradethe software (specifically the boot monitor image,oe8b3600.img) to a previous release (Release 3.5.3.2or earlier), it may be necessary to return the module toNortel due to boot flash corruption.

3 Format the flash, using the command format-flash.

4 boot /pcmcia/0e8b4043.img

5 boot /pcmcia/0e8a4043.img

When the switch comes back up, the 16 MB flash is now availableto you.

6 Copy all files from the PCMCIA card or TFTP/TFP server to whichyou copied them in step 1 back to your flash.

—End—




.


New feature enhancements and changesEnhanced CLI commands

You can now search for MAC entries even when the TDI on which theendpoint belongs is unknown. This section has the following enhancedCLI commands:

• "Showing information from the endpoint MAC address table" (page 48)

• "Showing TDI endpoint information" (page 50)

Showing information from the endpoint MAC address tableYou can now show a wide variety of information from the MAC address tableusing the dump endpoint-mac-table command. You can specify a numberof different tables (TLS port, ESM UNI, ring port, and standalone port) andsorting using a variety of options (TDI ID, UNI, qtag, outer qtag, and MACaddress). 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 Displays all TDI and UNI information.

info [tdi <value>] [uni <value>] [mac<value>] [qtag <value>] [outer-qtag<value>]

Displays specified TDI and UNIinformation.

• tdi <value> displays thespecified TDI as an integerbetween 1 and 16777215.

• uni <value> displays the UNIspecified in the format of a.b.c.d.

• mac <value> displays the MACaddress in hexadecimal format0x00:0x00:0x00:0x00:0x00:0x00.

• qtag <value> displays the qtagspecified as an integer rangebetween 1 to 4093.

• outer-qtag <value> displaysthe outer qtag specified as aninteger 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 formatof slot/port number.




• outer-qtag <value> displaysthe outer qtag specified as aninteger 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 fora ESM UNI. You identify a UNI for aESU ring by its ring ID, module ID,and the port number on the ESU onwhich the UNI was created.

• ring-mod-port <ring_id> isthe ESU ring number.

• mod-id <value> is the modulenumber assigned on the switch asan integer between 1 and 24.

• port-id <value> is the ESUport number as an integerbetween 1 to 24 and 28.




standalone-esu-port <port> mod-id<value> esu-port-id <value> [tdi<value>] [mac <value>] [qtag <value>]

Allows ring and port-based searchfor a standalone port. You identify aUNI for a standalone ESU by the ESMport on which the standalone ESU isconfigured, with the mod-id, and theport number on the SU on which theUNI was created.




.


• standalone-esu-port<port> is the standalone portnumber on the Metro EthernetRouting Switch 8600 in the formatslot/port.

• mod-id <value> is the modulenumber assigned to the ESUon which the UNI was created.Specify an integer between 1 and24.

• esu-port-id <value> is theESU port number as an integerbetween 1 to 26 and 28.




This command replaces the dump endpoint-mac-table tdi <tdi>[uni <value>] [mac <value>] [qtag <value>] command, whichis now obsolete.

Showing TDI endpoint informationYou 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 1to 4093.

• name <value> is the endpoint name as a string length of 1 to 30characters.




.

Supported standards, RFCs, and MIBs 51

• detail shows all the endpoint information in detail.

This command replaces the show tdi end-point config infoend-point [<ipaddr>] [tdi <value>] [name <value>][detail] command, which is now obsolete.

Hardware SupportThere is no new hardware support for release 4.0.4.3.

Supported standards, RFCs, and MIBsThis section identifies the 802 standards, RFCs, and network managementMIBs supported in this release.

"Supported standards" (page 51) lists the supported standards.

Supported standards

Supported standards

802.3 CSMA/CD Ethernet ISO/IEC 8802-3

802.3i 10BaseT ISO/IEC 8802-3

802.3u 100BaseT ISO/IEC 8802-3

802.3z Gigabit Ethernet

802.3ab Gigabit Ethernet 1000BaseT 4 pair Cat5UTP

802.3ae 10 Gigabit Ethernet

802.1Q and 802.1p VLAN tagging and prioritization

802.3x Flow Control

802.1D MAC bridges/spanning tree protocol

"Supported protocol RFCs" (page 51) lists the protocol RFCs supported inthis release.

Supported protocol RFCs


RFC 768 UDP protocol

RFC 783 TFTP protocol

RFC 791 IP protocol

RFC 792 IGMP

RFC 793 TCP protocol

RFC 826 ARP protocol




.



RFC 854 Telnet protocol

RFC 903 Reverse ARP

RFC 1541 and 1542 BootP and DHCP

RFC 1542 BootP

RFC 1112 IGMPv1

RFC 2236 IGMPv2

RFC 3376 IGMPv3

draft-holbrook-idmr-igmpv3-ssm-02.txt

IGMPv3 for SSM

RFC 2178 OSPFv2

RFC 2131 Dynamic Host Control Protocol (DHCP)

RFC 2338 Virtual Router Redundancy Protocol

RFC 2362 PIM-SM

RFC 3569 (draft-ietf-ssm-arch-03.txt)

PIM-SSM

RFC 2474 and 2475 DiffServ

RFC 2597 and 2598 DiffServ per hop behavior

RFC 2138 RADIUS Authentication

RFC 2139 RADIUS Accounting

RFC 1591 DNS Client

"Supported network management MIBs" (page 52) lists the networkmanagement MIBs and standards supported in this release.

Supported network management MIBs

Supported MIBs

RFC 1155.mib SMI MIB

RFC 1157.mib SNMP MIB

RFC1213.mib MIB for networks management ofTCP/IP-based internets MIB2

RFC 1215.mib A convention for defining traps for use withthe SNMP

RFC 1493.mib Definitions of management objects for bridges

RFC 1573.mib Interface MIB

RFC 1643.mib Definitions of managed objects for theEthernet-like interface types




.

General configuration issues and considerations 53

Supported MIBs

RFC 1757.mib Remote network monitoring MIB (support ofalarms, events, statistics, and history groups)

RFC 1389.mib OSPFv2 MIB

RFC 1907.mib SNMPv2 MIB

RFC 2021.mib RMON MIB (using SMIv2)

RFC 2096.mib IP forwarding table MIB

RFC 2233.mib The interfaces group MIB using SMIv2

RFC 2674.mib Definitions of management objects for bridgeswith traffic classes, multicast filtering andvirtual LAN extensions

RFC 2932.mib IPv4 multicast routing MIB

RFC 2933.mib Internet Group Management Protocol MIB

RFC 2934.mib PIM MIB

RFC 2571, 2572, 2573, 2574,2575, 2576 mibs

SNMPv3 MIB

RFC 2674.mib Definitions of Managed Object for bridges withTraffic Classes, Multicast Filtering, and VirtualLAN extensions

RFC 2925.mib Ping and Traceroute MIBs

General configuration issues and considerationsThis section lists general, non-critical system issues that you should beaware of when operating the Metro Ethernet Routing Switch 8600.

PlatformIf you remove a PCMCIA card before you complete, or upload, a writeoperation, the file that is being written to may contain a corrupted EOFmarker. Additional attempts to write to this file can generate an errormessage. To resolve this problem, remove the file created during the uploadprocess, and recreated from the beginning.

Some PCMCIA cards do not contain a file attribute table (FAT). Use theCLI command dos-chkdsk /pcmcia to check the card. If you receiveerror messages, use the dos-chkdsk /pcmcia/ repair command orthe dos-format command.

When you enter the CLI command boot –y, the console displays theerror message invalid option "-y" in config/bootconfig andthen reboots the Metro Ethernet Routing Switch 8600 chassis. The errormessage is invalid and has no effect on rebooting the chassis.




.


Previous Nortel Metro Ethernet Routing Switch 8600 release notesincorrectly state that the maximum number of supported VLANs is 1980.The maximum achievable number of VLANs is 1973.

Provider Backbone TransportRelease 4.0.4.3 includes Nortel’s first release of Provider BackboneTransport (PBT). As such, you can only use it under controlled availability.For details on release authorization, contact your local account teammanager.

When creating PBT trunks, you can configure the same MEP-ID on the localand remote MAs. However, if the MEP-IDs are the same, the PBT trunk willremain in a down state as duplicate network identifiers are not supported.You should not have duplicate MED-IDs.

Currently in the Nortel Metro Ethernet Routing Switch 8600, the consolehangs when you source a PBT configuration file (with Ring and Trunk PBTtunnels). Do not source a configuration file using the source command.

Currently in the Nortel Metro Ethernet Routing Switch 8600, removing thePBT trunk slot causes all trunks and SGs to bounce. You can resolve this byfirst disabling the slot, then removing the module.

In the Nortel Metro Ethernet Routing Switch 8600, there are three possiblescenarios for disabling a PBT trunk:

• Administratively disabled primary trunk with no secondary trunk — Inthis case, traffic stops immediately.

• Administratively disabled primary trunk with a secondary trunk — In thiscase, traffic continues to pass through the primary trunk for 50ms untilfailover to the secondary trunk completes.

• Hardware failure such as a faulty ESM module — In this case, the portis administratively down and the operation status is up. Traffic continuesto pass through the trunk for two minutes during High Availability-CPUswitch.

In the Nortel Metro Ethernet Routing Switch 8600, with MaintenanceAssociation (MA) state disabled, the PBT trunk still comes up. You canresolve this issue by deleting MA and recreating it with MA state disabled.Configuring the same trunk with this MA brings the trunk back up without anerror message.

The MERS 8600 does not support PBT if you configure the chassisspanning tree mode for RSTP or MSTP. You must use the default spanningtree mode (STP) when using PBT services.




.


When configuring PBT-based endpoints with ESU rings, Nortel recommendsmaintaining the default settings for the following parameters:

• ccm-interval — This parameter sets the time interval for how oftenCCM messages are sent between endpoints within a Service Groupdomain. Nortel recommends leaving this setting at the default of 5000milliseconds.

• ccm-lifetime — This parameter sets the life time before CCM times outwithin a Service Group domain. Nortel recommends leaving this settingat the default of 150000 milliseconds.

Failover times for PBT trunks vary from 50 ms to 1 second depending on thetotal number of trunks assigned to a failed port. The greater the number oftrunks on a single port, the longer the failover time is.

For Release 4.0.4.3, Nortel recommends that you do not use DeviceManager for configuring PBT services. This includes maintenance domains,maintenance associations, MEP IDs, and trunk ports. Use the commandline interface instead.

High-availability CPUWhen using HA-CPU, if the primary CPU is physically removed from thechassis, data traffic failover to the standby CPU may take 3 to 6 seconds,depending on the config and traffic load. Prior to removing the primary CPU,you should perform a CPU switchover action using the command configsys set action cpuswitchover to activate the standby CPU prior toremoving the primary CPU from the chassis.

Nortel does not support the use of HA-CPU in a scaled ESM ring andendpoint environment.

ESU ringsIn the Nortel Metro Ethernet Routing Switch 8600, when using cust-ip-vlanUNIs, IP multicast packets may be dropped for more than 50 ms upon ringrecovery.

In configurations with 16 or more rings connected to one Metro EthernetRouting Switch 8600, you must disable enhanced RRP. However, thisonly applies to the Metro Ethernet Routing Switch 8600. You can still useenhanced RRP between ESUs on the rings.

VLACP enabled on NNI portsIf you enable spanning tree on ports with VLACP enabled, or if the portsused to transport VLACP messages have spanning tree enabled, theVLACP sessions will be delayed upon recovery of services. After spanningtree completes the convergence cycle, the VLACP session is established.




.


IP static routesIn the Metro Ethernet Routing Switch 8600, IP static routes take precedenceover all other learned routes with the same cost, except for Open ShortestPath First (OSPF) learned type 2 routes.

The Metro Ethernet Routing Switch 8600 does not allow you to configurea static route, dynamically learned. However, you can add the route in theASCII configuration, and boot the switch accordingly. The configured staticroute is then chosen as the route, provided the next hop is available.

IS-ISIf IS-IS is globally disabled, disabling/enabling at the interface level does nottake any effect. No informational message displays after IS-IS integrationconfiguration. The Metro Ethernet Routing Switch 8600 JDM does notsupport the display of informative messages.

On the L1 only router, no error message displays when configuring the L2metric at the interface level. The CLI does not warn the user with an errormessage, after entering the command <<L2-only-mode>>.In IS-IS, when a router is configured as an L1 router at the global level, theL2 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 L1LSP. The IS_IS TYPE bits are indicating the type of Intermediate Systemrouter instead of type of lsp.

Nortel recommends that all metrics in the IS-IS network are set to the samemetric type. By default, the metric is set to wide. Nortel also recommendsthat this parameter is left at the default setting. If only one router metricis changed, the IS-IS network may lose a significant amount of routes.Also, metric changes do not take place dynamically. You must restart IS-ISglobally.

After selecting IP Routing > ISIS > Summary Address tab > Insert, withoutadding any configuration parameters, the following error message appears:isisSummAddrPrefixLen: Unparseable number:’’ ’’

OSPFWhen you design your network, consider the following OSPF capabilities:

• In order to operate the Metro Ethernet Routing Switch 8600 at thepublished scaling limit, a maximum recommended number of areasper switch is four.

• In order to operate the Metro Ethernet Routing Switch 8600 atthe published scaling limit, a maximum recommended number ofadjacencies 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. Thereis always a DR and a BDR on a IP subnet running OSPF if there areat least two routers.

When using OSPF on chassis with ESU rings installed, convergence timemay increase significantly if you reduce the ESU ring discovery protocolinterval to values below 30 seconds. For networks with more than 1000routes to redistribute, Nortel recommends maintaining a minimum ESUring discovery interval of 30 seconds.

CPU SSF management portYou can only disable the management Ethernet port using the MetroEthernet Routing Switch 8600 console port. You cannot disable themanagement port using Device Manager because this capability is notsupported.

The management Ethernet port can communicate only with devices on itslocal subnet and on up to four statically-configured, remote subnets. Themanagement Ethernet port does not support a default gateway or defaultroute. The remote subnet is configured 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.11and its next hop is 10.125.2.1, use this command to correctly set up themanagement port:config bootconfig net mgmt route add 13.177.76.0 10.125.2.1

Debugging using the trace level commandIf you specify the CLI command trace screen on, be cautious when youswitch on trace levels. After you add the new Metro Ethernet Routing Switch8600 software code base and debug messages specific to the new platform,you can encounter various platform-related performance issues that cancause the software to become unstable at certain times.

CPU password synchronizationTo synchronize the primary and slave CPU passwords, perform these steps:

Step Action

1 Change the password on the primary CPU.

2 Save the password by entering the CLI command save config.




.


3 Enter the CLI command save config file config.cfgstandby.

4 Go to the slave CPU, and change the password by entering the CLIcommand:

config cli password rwa <username> [<password>]

—End—

Metro ESM 8668This section describes the following topics:

• "Unused module removal" (page 58)

• "Hot-swap and module insertion" (page 58)

• "Ring ports" (page 58)

Unused module removalMinor packet loss can occur when you remove unused Metro ESM 8668modules, or standby CPUs, from the chassis. The packet loss occurs onlyduring the instance of the module removal.

Hot-swap and module insertionIf you need to remove a Metro ESM 8668 module, it is highly recommendedthat you first disable the slot before removal by using the CLI commandconf slot # state dis. If the module is active when removed, ringfailover times may be longer than expected. Disabling the slot provides aclean disconnect from all services before removing the module.

When hot-swapping a configured Metro ESM 8668 module, if you rebootthe Metro Ethernet Routing Switch 8600 before you install the newreplacement Metro ESM 8668 module, the ports are not configured afterthe new replacement Metro ESM 8668 is initialized. When the MetroEthernet Routing Switch configuration is loaded, it loads only the sectionof the configuration for the cards currently installed at time of reboot. Youmust reboot the Metro Ethernet Routing Switch 8600, or manually enter theconfiguration for the specific ports.

Ring portsWhen using Metro ESM 8668 ring ports with Metro ESU 1800 or ESU 1850switches, recovery time can exceed 50 milliseconds if the spanning treegroup to which the ports are assigned is enabled. After the link is lost onthe secondary or primary ring port, the port is removed from the defaultService Provider VLAN.




.


When the link is recovered on the ring port, spanning tree blocks themulticast channel from the Mapped NNI VLAN; no loop can exist. Nortelrecommends that you disable spanning tree on all ESM ring-enabled ports.

Local and remote UNI considerationsThis section describes the following topics:

• "Configuring 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)

Configuring endpoints during heavy CPU utilizationWhen switch utilization is close to 100%, you can experience time-outs whenusing Device Manager to configure the switch. Nortel recommends that youconfigure the switch using the CLI during periods of heavy CPU utilization.

QinQ UNIsQinQ does not forward untagged customer packets. Customer packetsmust be tagged on ingress for any UNI type that forwards to a remote UNI,defined as a QinQ type endpoint.

QinQ UNIs are not supported with ManytoOne TDIs. The TDI must be set toOnetoOne before configuring a Q&Q UNI.

L2-VPN broadcasts into ESU ringsIf multiple endpoints within a common ESU ring share the same TDI, whenbroadcast packets or multicast packets (i.e. topology or OSPF packets) aresent within the TDI, these packets must be replicated for each endpoints, atthe ESM ring port, before it is sent to all designated endpoints within thering. As the number of common endpoints within a TDI increase within thering, so will the overall aggregate traffic rate increase. For example, if youhave 10 endpoints, for every broadcast packet send within the TDI, thepacket must be replicated 10 times to be sent to each endpoint in the ring.This will result in a 10 fold increase in traffic bursts for every broadcastrelated packet sent. To minimize the overall burst rate, Nortel recommendsno more than 5 endpoints per TDI in a single ring.

When multiple endpoints share the same TDI in the same ring, if anyone of the ESU access ports should drop its link (for example, the userdisconnects from a port, or the attached device drops its port state), a fewpackets may be dropped on all other active endpoints in the ring. Due to




.


different rates, packet sizes, and traffic patterns that may exist, the actualnumber of lost packets may vary according to traffic conditions at the timethe endpoint disconnects.

Moving UNI IDs between ESM portsWhen moving either an active UNI ID between ESM ports, or a primary ringport of an existing ring to another ESM port, all remote UNIs fail to learnthe new UNI port destination MAC. Until the customer destination MACaddress ages out or the remote UNIs are reset, the remote UNI IDs continueto send customer traffic to the original ESM port before the UNI ID wasmoved. When moving a UNI ID or primary ring port, Nortel recommendsthat all remote endpoints are disabled and then re-enabled after the localUNI ID is moved.

R-module UNIsFor this release, you must configure a point-to-point EVPN on an R-moduleUNI port. However, before you enable the endpoint, configure the remoteB-MAC address. This is not “optional.” If you do not provision the remoteB-MAC address, the R module encapsulates the customer traffic with adestination MAC address set to 00-00-00-00-00-00, which results in trafficflooding into the core network.

The R module endpoint classification rule consists of an Ethernet UNI ID anda TDI. For endpoints assigned to an Ethernet UNI ports with service typeTLS-Switched or QinQ, one or more q-tags are included in the classificationrule. In Release 4.0.4.3, the endpoint connection type supported ispoint-to-point only and is based on an Ethernet line (E-Line) service.

R-module endpoints designate the end user’s connection-type, and receiveassignment to a customer through the TDI. Endpoints classify and policethe traffic on a per endpoint basis using pre-defined QoS rules and policersassigned to ingress and egress policer profiles per endpoint.

8648GTR portsIn the Nortel Metro Ethernet solution, 8648GTR ports can be used as UNIports. Because of this, Nortel recommends using the strict priority scheduleron these ports to provide the best support for the four service classes.

Multi-service UNI portsAs of release 4.0.4, ESM ports support multiple UNI IDs with multi-servicetypes. A single ESM port may include support for Local TLS-Switched UNIs,QinQ(1) UNIs and QinQ(2) UNIs. Multi-Service UNIs are not supportedon ESU ports; only ESM and R-module ports support multiple UNI IDsat this time.




.


Many-to-one restrictionsPorts assigned with both QinQ UNIs and TLS-Switch UNIs may not beassigned to Many-To-One TDIs, even if the QinQ UNIs are assignedto One-To-One TDIs and the TLS-Switched UNIs are assigned to theMany-to-One TDIs.

Local port switchingLocal switching between TLS-Switched UNIs assigned to the same ESMport is supported. However, local port switching of QinQ UNIs or localswitching between QinQ and TLS-Switched UNIs on the same ESM orR-module port is not supported.

Metro Ethernet Routing Switch 8600 QoS considerationsThis section describes the following QoS considerations:

• "ACL filters" (page 61)

• "QoS policing" (page 61)

• "COS profile" (page 61)

• "Premium traffic restrictions" (page 62)

• "Egress QoS markings for untagged packets within an ESU ring" (page62)

• "TDI congestion drop counters" (page 63)

ACL filtersRelease 4.0.4.3 does not support access control list (ACL) filters onR-module UNIs and endpoints. However, if you are using R-module ports inan Enterprise solution, the ACL filters function as documented.

QoS policingFor this release, policed rates for Metro Ethernet Routing Switch 8600endpoints do not include inter-packet gap and preamble (Start of Headerbits) for every packet sent.

COS profileIf you set the Premium COS value to drop out-of-profile traffic(premium-pir-usage=disabled), and if traffic rates should exceed CIR levels,the attached devices sending control plane requests, such as ARP requestsor VRRP responses, are dropped. In management environments, the abilityof a CPE device to respond or receive ARP requests can cause loss ofnetwork 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 CIRlevel, or that you allow the COS profile to burst premium traffic above CIR byenabling the premium-pir-usage flag.




.


When using L2-VPNs to manage multiple ESUs and customer deviceswithin the same TDI, Nortel recommends limiting the maximum PIR rate tolimit broadcasts, autotopology messages, and SNMP discovery probes intothe L2-VPN. A significant amount of broadcast traffic can be generated,impacting general services on ESU rings and other VPNs not related to theTDI that is being used to manage all devices in the common TDI.

Premium traffic restrictionsFor non-R-module interfaces, the maximum egress rate of all "aggregateflows" for premium marked traffic should never exceed a sustained rate of1.2 Gbps or burst above 1.4 Gbps out a single Gigabit port. This maximumbit-rate includes all overhead including Optical Ethernet Layer 2 overheadper packet.

For example, if four endpoints share the same hub port, the maximumpremium bit rate supported for each UNI should not exceed a combinedrate of 255 Mbps each, if all four ports are sending to the hub port at thesame time.

Premium traffic is always provided unlimited switch-fabric bandwidthsupport, regardless of congestion rates. The switch fabric attempts toforward all traffic, and uses all available resources to maintain a 0% lossrate for premium traffic. This includes using all buffer space available toother ports before dropping the traffic. If the combined flows of all premiumtraffic flows should exceed or burst above 1.4 Gbps, traffic loss may occuron all ports on the chassis, regardless of service type or QOS level. Nortelrecommends that Premium or Expedited Forwarding (EF) traffic should notexceed 20% of your overall SLA requirements for a single egress port.

Egress QoS markings for untagged packets within an ESU ringAs of release 3.6.0.0 and above, when untagged customer packets egressinto a Metro ESU 1800 or ESU 1850 ring (i.e., packets destined for the MetroESU 1800 or 1850 UNI port at the egress node), the ring packets includethe 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 goldclassification and the default priority and egress QoS maps are used, whenthe packet enters the egress Metro ESU 1800 or ESU 1850 ring, the p-bitsis marked as 4.

By default, the Metro ESU 1800 or 1850 ring treats a p-bit setting of 4 as aclass 0 (standard) COS value. You must make sure the Metro ESU 1800 or1850 802.1 user-priority mappings for each possible SP p-bit is set to thecorrect desired level.

For the above example, change the 802.1 user priority level 4 to a class-2setting. This provides the same level COS value as Gold.




.


TDI congestion drop countersThe TDI congestion drop counter (CDR) provides statistics on the numberof classified VPN packets dropped (as the switch fabric was congested).

The CDR counter does not increment if any portion of the packet is droppeddue to increases in congestion within the switch fabric before the packetcompletes its transition into the switch fabric.

The occurrence of a post-drop is more likely on larger packets due to thetime required to clock the bits into the switch fabric. For packets that aresuccessfully transferred into the switch fabric, if congestion occurs at theegress port (for example, at the NNI port or the local switch UNI port), anOutloss packet counter counts the number of packets lost due to egress portcongestion. The Outloss packet counter is a global counter for all VPNs thatuse the egress port.

Dual-home ringWhen configuring dual-home rings, the ERT trunks must be configured asMLT trunks. If a single non-MLT trunk is used, if a mid-span ring breakshould occur, up to 15% traffic loss will be seen, regardless of traffic 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 orany ESU resets that may occur while the ring is recovering may result in adouble-fault ring break condition. If a double-fault condition occurs, trafficmay stop forwarding or the ring may transition to the down state. If, after thering breaks are remedied the ring remains down or cut, you must disablethe ring and re-enable it after the ring is healed.

Static destination UNI MACsWhen using static destination UNI MAC addresses in a dual-home ringconfiguration, the primary dual-home switch does not update or configurethe static entry on the secondary dual-home switch. You must configurethe same static destination UNI MAC address on both the primaryand secondary dual-home switches. To avoid synchronization errorswhen configuring static destination UNI MACs, configure the secondarydual-home switch first before configuring the primary dual-home switch.

Dual-home ring endpoint MAC table sizeFor endpoints assigned to a dual-home ring, if you modify the mac-table-sizeor any endpoint attributes on the primary dual-home ring switch first, andthen make the subsequent change on the secondary dual-home switch, thesecondary switch sometimes fails to learn the customer destination MACaddress and will always multicast traffic out all ports assigned to the TDI




.


and mapped VLAN. Any changes required for an endpoint must be made tothe endpoint on the secondary dual-home switch first followed by the samechanges on the UNI assigned to the primary dual-home ring switch.

Configuring endpoints for dual-home ringsWhen configuring new endpoints or changing the status of existingendpoints in a live network, configure and enable endpoints on thesecondary dual-home switch first before enabling the endpoint on theprimary switch. If the endpoint is enabled on the primary switch first, MACaddresses may be learned on the primary before the secondary is updatedresulting in traffic broadcasting into the service provider backbone.

Dual-home ring and OPE3500 NNI interoperabilityWhen connecting Ethernet NNI uplinks for both the primary and secondarydual-home switch to a Nortel OPE OM3500 switch, the ERT or ERT-MLTports on the primary dual-home switch must be configured as the root portfor the STG group. The Spanning Group default path-cost value of a MetroRouting Switch 8600 GigE (1G or 10G) port when active is 1. The followingconfiguration rule applies when connecting to the OM3500:

• The secondary dual-home node must be configured as root bridge forall STGs defined.

• STG must be enabled on the ERT or ERT MLT port and also the Metro8600 NNI ports connected to the OM3500 mapped ports.

• The IBT or the IBT MLT ports on the primary dual-home node must beconfigured as the STG root port.

• The path-cost assigned to the Metro 8600 NNI interface on both theprimary dual-home switch and secondary dual-home switch, that areconnected to the OM3500 mapped port, should have a path cost greaterthan 1 but less than 100. In order to force the required STG path, it isrecommended that the primary dual-home node’s ERT port or ERT MLTport 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 switchNNI 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 10Gig ERT ports.

The OPE3500 path-cost for STG is not configurable.

Legacy access ports (ESM Server ports)Legacy Access ports (also know as ESM Server ports) are no longersupported for general customer UNI access as of release 4.0.0.0. Legacyports may still be used to maintain L2-VPN management for sites using




.


dual-home rings or to manage existing sites using L2-VPNs to manageESUs within single-home rings. See 3.6.1 release notes for more informationabout general configuration and considerations of Legacy Access ports.

After migrating services from Legacy Access EVPNs and associatedendpoints to ESM-based ports (local, ring or standalone), you have to resetthe legacy module to restore normal service to the legacy ports. To reset alegacy module, remove and re-insert the module into its slot or reset thechassis. Nortel recommends migrating Legacy Access port EVPNs toESM-based ports during a scheduled maintenance window.

ESU and customer CPE management considerationsThis section describes when to use Layer 2 VPNs.

L2-VPN based managementIf IP services are not possible, or if you are using dual-home rings, youcan manage the Metro ESU 1800 or ESU 1850 device using layer 2 VPNconnections from the Metro Ethernet Routing Switch 8600 to the NOCcenters. All UNI service types are supported. To limit broadcast domains,Nortel recommends using different TDIs and Mapped NNI VLANs wheneverpossible to reduce the broadcast auto-topology messages and SNMPdiscovery broadcasts within a TDI and mapped VLAN that can occur inlarge networks.

When using L2-VPNs to manage ESUs and attached CPE devices, theuse of local switched loopback connections between a UNI endpoint andan IP based VLAN on the same Metro Ethernet Routing Switch 8600 is notsupported and should be avoided. Possible switch fabric loop conditionscould occur during reboot or when changing service types on endpoints.These conditions can result in switch fabric lockup conditions or loss ofcustomer traffic.

Ethernet MTU sizeFor Release 4.0.4.3, the maximum transmission unit (MTU) size supportedis 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 fixed to 1500 regardless of port MTUsettings for OSPF services.

Note that the MTU numbers are interface maximums and do not include anyservice provider encapsulation overhead. End customer traffic maximumframe size will be smaller.




.


Transparent Domain Continuity testsThis 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 issuesThe following list describes non-critical TDC test issues:

• If you configure a TDC test with a specific QoS level, when the TDCtest packet arrives at the ingress endpoint, the TDC test packet’s QoSlevel is remarked based on the endpoint priority map, upon which theTDC packet is classified.

• If you use TDC tests with the Optical Metro 3500 switch, and youconfigure Round Trip Time (RTT) stamps, some test results can show anegative RTT time stamp when the Optical Metro 3500 switch CPU isunder a severe load.

• If you configure TDC to test various endpoints within an Optical Metro3500 switch environment, the total RTT time stamp between the MetroEthernet Routing Switch 8600 devices at the edge of the ring can appearless than the same TDC test case using an Optical Metro 3500 switchdestination UNI that is in the same data path. The TDC RTT test resultsbetween the Metro Ethernet Routing Switch 8600 devices are correct.

• For test cases where the number of Unicast and Multicast packets areconfigured in the range of 50 and 100 packets, and the destination UNIis an Optical Metro 3500 switch UNI, the duration of the test can belonger than you expect. For 100 Multicast and Unicast packets, the totaltest duration for results can take upwards to 20 seconds to complete.

Metro ESU 1800 or ESU 1850 UNI portsIf you do not define port policer on a Metro ESU 1800 or ESU 1850 port,the switch does not forward customer traffic. However, the TDC test casepasses.




.


Round Trip Time stamp measurementsThe Round Trip Time (RTT) parameter measures the total time the TDC testpacket takes from point of origin (source ID) and back again (back fromdestination ID). The overall time noted includes processing time of the TDCpacket by Metro ESM 8668 modules and, in case of Ring topology, it alsoincludes ESU 1800 and 1850 processing time.

For local TLS and legacy access ports, the average RTT nodal delaybetween CPU and the ESM port is around 30 µSecs. Various trafficpatterns, QoS, and lookup processing time can add latency to the actualTDC data packet.

For the Metro ESU 1800 and 1850, the RTT Time parameter measuresthe total time the TDC test packet takes from point of origin (source ID)and back again (back from destination ID). The overall time noted includesprocessing time of the TDC packet by each Metro ESU 1800 or 1850. Theactual latency measurement is not the true customer end-to-end latencyexpectation. Processing time of TDC packets through each Metro ESU1800 or 1850 could average between 700 and 1000 micro seconds. ForRTT values between two Metro ESU 1800 or 1850 devices, the TDC packetis processed twice, once from the originating Metro ESU 1800 or 1850device, and again at the terminating Metro ESU 1800 or 1850 device.

TDC processing time is affected by traffic processing and managementtraffic. Filter hits, QoS scheduling, SNMP queries and use of console port toaccess statistics and other ESU management information can affect andincrease the overall processing time above the stated average.

The Metro Ethernet Routing Switch 8600 RTT timestamps values areincremented in milliseconds (ms). A round trip time under 1 ms results ina display of 0 ms RTT on the Metro Ethernet Routing Switch 8600 TDCtest results.

TDC error messages on ESU 1800 or ESU 1850 power down stateWhen you power down one or more Metro ESU 1800 or ESU 1850 switchesthat have an active running TDC test, the Metro Ethernet Routing Switch8600 console may display CPU and TDC error messages. These messagesdisplay because of the loss of the TDC assigned UNI interfaces going downwhen the Metro ESU 1800 or ESU 1850 is powered down. These messagesdo 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 TDCtest ID (for example, you change priority, or change RTT-threshold), thecurrent test aborts and all previous history data are cleared. Cleared historyalso applies to changes made to the TDC test after it has completed allperiodic test counts.




.


Known Optical Metro 3500 TDC interoperability issuesOlder versions of Optical Metro 3500 (Version 13.x or earlier) run-timeimages are unable to interpret the Metro Ethernet Routing Switch 8600timestamps. If the Optical Metro 3500 originates a TDC request with RTToptions on older versions of Optical Metro 3500 operating code, the OpticalMetro 3500 software displays the following message and the RTT (RoundTrip Time) is set to zero:"Warning, can’t process time information"

TDC test resultsNot all Metro Ethernet Routing Switch 8600 TDC test case conditionsare responded to by TDC test case requests from other Optical Ethernetdevices. Examples of known test conditions that will fail as "timeout" (or noresponse from the Metro Ethernet Routing Switch 8600) are as follows:

• Wrong UNI point-to-point type, spoke-to-spoke, hub-to-point-to-point, andpoint-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 toESU ring port update status, the correct error message is displayed. Defaultperiodic ring updates are 30 seconds; after the update verifies Metro ESUport down, all future TDC test cases for the Metro ESU UNI timeout.

MAC learning keys and 32-bit UNIsThe Metro Ethernet Routing Switch 8600 supports 32-bit UNI ID’s for localMetro ESM 8668 and legacy access ports. However, if the learned customerdestination MAC address remains the same, but the UNI ID changes, onlythe least significant 24 bits for ESM Local Ports and least significant 16 bitsfor legacy access ports are compared and verified as unique. For example:




.


An ESM Local Port at site A learns destination customer MAC00:00:AA:01:01:01 from source (remote site) UNI ID 2.1.1.1. When theESM Local Port at local site A forwards to the known customer destinationMAC 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 toanother UNI ID before the customer destination MAC table ages at the localsite A, only the least 24 bits are used to compare and verify that the UNIID changed. In this case, if the device at the remote site moved to UNI ID3.1.1.1, there would be no change in the learned customer MAC table asthe least 24 bits are still the same and packets will continue to forward toUNI 2.1.1.1.

However, if the device had moved to UNI ID 3.1.1.2, because the lower 8bits 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 asthe destination UNI ID. This same rule applies to local legacy access ports,except that the UNI ID verification is based on a unique 16-bit match.

MLT and SMLT considerationsThis section describes some MLT and SMLT considerations that you shouldbe aware of when configuring your network.

ATTENTIONAggregate throughput may be less than line rate when both of the followingconditions 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 installingdual CPUs.

VPN-based MLT load sharing algorithmA multilink NNI trunk aggregates bandwidth between two switches. TheMetro Ethernet Routing Switch 8600 uses one of two algorithms todetermine which active NNI port in the multilink trunk (MLT) to use for eachEVPN packet. The MLT algorithms provide load sharing while ensuring thateach packet in a flow does not arrive out of sequence.

Attention: These MLT algorithms are the same traffic distribution algorithmsused for IEEE 802.3ad-based link aggregation.

• Algorithm for ESM modules — For customer-facing traffic with ESMmodules, the distribution algorithm always uses the Optical EthernetLayer 2 UNI IDs to determine which NNI port to use within the MLTgroup. In this case, the six least-most significant bits of the source UNI




.


ID and destination UNI ID of the Optical Ethernet Layer 2 Ethernet frameto be forwarded are compared using the following XOR operation:

(DestUNI-ID[5:0] XOR SrcUNI-ID[5:0]) MOD (number of activelinks)

• Algorithm for R modules — For customer-facing traffic with R-moduleUNI ports, the distribution algorithm uses the Optical Ethernet Layer2 header MAC address (B-MAC) or the Provider Backbone Bridge(802.1ah) Layer 2 Header MAC address (B-MAC) to determine whichNNI port to use within the MLT group. In this case, the six least-mostsignificant bits of the source MAC and destination MAC of the eitherthe Optical Ethernet Layer 2 Ethernet frame or Provider BackboneBridge Layer 2 Ethernet frame to be forwarded are compared using thefollowing XOR operation:

(DestMAC[5:0] XOR SrcMAC[5:0]) MOD (number of activelinks)

The following example demonstrates how the formula works with customerpackets 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. Thelast byte of the UNI source IP address is 0x21, the binary representation ofwhich is 00100001. Use the 6 least-most significant bits, which are 100001.

Likewise, the binary representation of the last byte in the UNI destination IPaddress, 0x56, is 01010110, of which 010110 are the bits of significance.The formula is {(A XOR B) MOD x}, where A and B are the 6 least-mostsignificant bits in the UNI source and UNI destination IP addresses, and x isthe 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, thisparticular Ethernet frame would traverse the fourth NNI port of the MLTgroup.

The MLT port number is based on the port’s IF index number, from lowto high.

SMLTTo avoid creating loops when converting a Spanning Tree network intoan SMLT network, design your network as recommended in the NetworkDesign Guidelines (313197-C).




.


To determine whether your network topology forms a loop outside theSMLT/IST core, you must review all STGs and VLANs that pass throughthe IST and SMLT links. If a loop exists, Spanning Tree does not detect itsince Spanning Tree is disabled on all SMLT/IST ports. If CP-limit or theloop detect feature is enabled on the port, one port in the loop is identifiedand it is blocked.

Nortel recommends that you do not enable CP-Limit on the IST port.

When configuring MLT/SMLT, make sure to include both ports and VLANs inthe MLT configuration file. If you specify only VLANs in the configurationand do not add MLT/SMLT ports, this can cause intermittent MAC learningissues on the next hop of the SMLT link.

Customer IP UNIsWhen creating a UNI for Customer IP VLAN Support, only the TLS servicetype is supported. Customer IP UNIs are only supported on TLS-Switchedservice types. If a TLS-Transparent UNI is assigned to an Ethernet ServicesUnit port (ring or standalone connection), the Ethernet Services Unit portmust 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 noconsistency check as the Metro Routing Switch 8600 and Ethernet ServiceUnit are different platforms. Assigning the TLS-Transparent UNI port to anIP_VLAN may result in unpredictable behavior if a matching qtag (or if theIP_VLAN is 4094, an untagged packet) should enter the port, the packet istreated as an IP packet and not as an Ethernet VPN packet.

IP multicast services for customer IP UNIsThe IP Triple Play service on the OESS platform is a Layer 3 function.The ESM 8668 does not support bridging of Multicast services. You mustenable the PIM-SM Multicast Protocol on the NNI interface or the SP-VLANassigned to the customer IP UNI for Multicast to work properly. (As of thisrelease, 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 DesignGuidelines (313197-C) for more information on how to design and scalemulticast networks.

IP spoofingThis enhancement enables the Metro Ethernet Routing Switch 8600 toprevent spoofing of IP address within the VLAN. IP spoofing is supportedon legacy and NNI ports, in addition to ESM 8668 ports. This feature




.


requires the switch to be rebooted. Nortel strongly recommends enablingthis feature during the upgrade to OE 4.0.4.3 in order to minimize the impactfor the network traffic.

This feature detects duplicate IP address based on ARP packets received.It is only during this detection phase that the security feature will restrict anddrop offending data traffic. If an attached host has already spoofed thenetwork and remote devices have learned the MAC address, this featuredoes not protect the network from an existing IP spoofing incident nor will itrestrict the traffic flows in progress.

An ESM port can be configured for prevention of IP spoofing on a per ESMport basis. All UNIs assigned to the ESM port for Local TLS and all UNIsassigned to an ESM ring port participate when IP spoofing is enabled.IP spoofing cannot be disabled per UNI or endpoint. When enabling IPspoofing on ESM ring ports, the service must be enabled on both of theprimary and secondary ring ports, or connectivity issues may occur.

MSTP/RSTPThe Metro Ethernet Routing Switch 8600 supports three Spanning TreeProtocol modes: STP, RSTP, and MSTP. Configuration files are notcompatible across modes. This means that you can use a configuration fileonly in the same mode in which it was created. For example, if you save aconfiguration file in RSTP mode, you can only use that file in RSTP mode,not STP or MSTP. To change modes, use config bootconfig flagsspanning-tree-mode <mstp|rstp|default>. STP is the defaultmode.

When using RSTP or MSTP services, if a tagged port is added to a VLAN ininstance 0, and the same port is later removed from VLAN 1 or any otherVLAN, the port is removed from all assigned VLANs within the instance. Youmust remove the port from all undesired VLANs first prior to assigning thetagged port to its intended VLAN and RSTP instance.

QinQInner tag (C-Tag) VID of 4096 (untagged) is not supported with QinQ2UNI types. In this release, QinQ2 UNI types always expect the presenceof C-Tags. Frames without C-Tags will be dropped with QinQ2 UNI. Thislimitation does not exist with QinQ1 UNI, as QinQ1 UNI types only examinethe Outer Tag (S-Tag).




.

Scaling limits 73

Scaling limits"FCS scaling limits" (page 73) outlines the scaling limits for the variouscomponents of the Metro Ethernet Routing Switch 8600 and the Metro ESU1800 and 1850.

FCS scaling limits

Feature or Service Maximum or Range Comments

Physicalrecommendations:

Maximum Metro ESM8668 modules perchassis

8

Maximum Metro ESM8668 ports per chassis

64

Maximum R modules perchassis

8

Maximum R moduleports per chassis

384

Maximum Metro ESU1800 or ESU 1850 ringsper chassis

24

Maximum Metro ESU1800 ports per ring

336

Maximum Metro ESU1850 ports per ring

140

Maximum Metro ESUsper ring

14

Min RRP Hello Timer 1 sec, 1 to 7 rings

5 sec, 8 to 15 rings

With 16 or more rings,you can use enhancedRRP between ESUs,but you must disable iton the MERS 8600.

MTU:

Maximum Metro ESM8668 ports

1950

Metro ESU 1800 or ESU1850 ports

1600

R module 9600




.



UNIrecommendations:

Maximum Access modeUNIs (local TLS) perMetro ESM 8668 port

4100

Maximum Access modeUNIs (local TLS) perR-Module port

• 4100 per port

• 4100 per lane

QinQ UNIs • Maximum ESMsupported outerq-tags per QinQUNI is 128.

• Maximum R-Module supported outerq-tags per QinQUNI is 4094.

• Maximum innerq-tags per QinQUNI is 4094

Maximum Metro ESU1800 or ESU 1850 ringUNIs per ring

• 336 per ESU 1800

• 140 per ESU 1850

Transparent UNIs • 24 per ESU 1800

• 10 per ESU 1850

Switched UNIs 128 per ESU 1800 and1850 ring

Up to a total of 336UNIs per ring, of which128 can be tls-switched(remainder can betransparent).

TDIs:

Maximum TDIs perchassis

30 000 Recommendedmaximum of fiveendpoints per TDI.

Endpoints:

Maximum EVPNendpoints per ESMaccess port (local TLS)

4100 Maximum of fiveendpoints per TDIper local TLS port.

Maximum EVPNendpoints per ESMring

2500 Recommendedmaximum of fiveendpoints per TDI.




.

Scaling limits 75


Maximum EVPNendpoints per R-moduleaccess port (local TLS)

• 8630GBR - 4100per group of 10 GEports

• 8648GTR - 4100per group of 24 GEports

• 8683XLR - 4100 per10 GE port

Maximum of twoendpoints per TDI.

Maximum endpoints perESM server port

2

Maximum q-tags perMany-To-One TDIendpoint

15 This limit applies only toESM, not R modules.

Metro ESU 1800 orESU 1850 ring:

Maximum transparentendpoints

• 336 per ESU 1800

• 140 per ESU 1850

One endpoint pertransparent UNI.

Maximum switchedendpoints

128 This limitation is basedon scaling tests.

Maximum NNI ports:

Maximum Gigabit Trunkports supported as NNI

240 ports The 240 ports canbe individual links orcombined in multipleMLT groups. The8648GTR is notsupported for NNItrunks with EVPNs.

Maximum R-Module10 Gigabit Trunk portssupported as NNI

24

NNI VLANs:

Maximum mapped NNIVLANs per chassis(Local TLS only)

1000

Maximum mapped NNIVLANs per chassis (withESU Rings)

250




.



Non-NNI VLANs:

Maximum non-NNIVLANs per chassis

Up to 1973 Total of 1973 VLANsis supported on thechassis

Static destinationUNIs and customerdestinationMAC addresses:

Per chassis 10 000

Per TDI 10

COS:

COS-profiles 2000 Two are preconfiguredfor default data anddefault managementprofiles.

Max DestinationMAC and Source IPaddresses:

Per Ring/Local TLS porton the Metro ESM 8668

97 000 Destination MAC andIP addresses use thesame table.

IP VLANs:

Max perRing/Standalone

32

Max per local TLS port 32

Max per Chassis 1973

Max Metro IP VLANs 512

IS-IS and OSPF

IS-IS Adjacencies per sw 40

IS-IS Routes 10 000

OSPF areas per switch 5

OSPF adjacencies perswitch

80

OSPF routes Pre-E and E-modules:15 000

M-modules: 20 000

R-modules: 20 000




.

Scaling limits 77


Multicast Services:

PIM Passive Interfaces 500

PIM Active Interfaces(legacy ports only)

80 Maximum of 64 passiveESM interfaces

Multicast Source SubnetTrees

500

Multicast (S,G) Records- PIM

2000

Supported ScalingCapabilities

Maximum numbersupported

Hardware forwardingrecords

Pre-E and E-modules:25 000M-modules: 125 838(see Note 1)R-modules: 256 000 IProute support, 16 000ARP support, and64 000 MAC support

VLANs 1973

IP interfaces 512 or 1973 with chassisMAC upgrade

Static ARP entries 2000

Static route entries 2000

IP ARP entries 16 000

Spanning Tree Groups Metro Ethernet RoutingSwitch 8600: 25(see Note 2)

MLT groups(see Note 3)

Metro Ethernet RoutingSwitch 8600: 32

Note 1: Number of records available with record reservation fields set to zero.For more information about the record reservation feature, see ManagingPlatform Operations (315545-D).

Note 2: Nortel supports ONLY 25 STGs in this release. Although you canconfigure up to 64 STGs (only 63 when a Web Switching Module is present),configurations including more than 25 STGs are not supported. If you needto configure more than 25 STGs, contact your Nortel Customer Supportrepresentative for more information about the support for this feature.

Note 3: The MLT feature is statically compliant with the 802.3ad standard (nosupport of LACP).




.


CRs fixed in Release 4.0.4.3This section lists the CRs fixed in Metro Ethernet Routing Switch 8600Release 4.0.4.3.

• (Q01499861-01) In some specific traffic patterns the soft port resetmechanism on the ESM 8668 may trigger erroneously.

• (Q01525889) In a multicast traffic scenario, traffic is lost when traversingthe network and a High Availability failover occurs.

• (Q01526396) Dual-home secondary switch does not relearn MACaddresses after disable-enable of endpoints.

• (Q01527279) When the login session times out during the dumpend-point-mac-table command, a subsequent running of thecommand does not work.


• (Q01376595-02) STP works appropriately when the 8683XLR module isremoved and re-inserted.

• (Q01475103) Ingress traffic is no longer dropped ingressing from anR module UNI with an NNI MLT.

• (Q01475191) Traffic is now forwarded out of the UNI port after an Rmodule is reinserted. Previously, the traffic would not forward out of aUNI port on a R module after reinsertion. You had to remove the Rmodule UNI port from the mapped-vlan and then add it back. Then addthe fdb-static entry in the mapped-vlan for UNI port MAC with outgoingport as UNI port.

• (Q01478507-03) You can no longer configure an MLT with a null nameor with white space using the CLI. Note that previous configurations withno 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 preventthe addition of a new MLT without any warning.

• (Q01479548) STG now converges properly after a R module reset or aHA-CPU failover. Previously, after R module reset or a HA-CPU failover,the edge device would continue to forward instead of block, thus causingSTP to not converge.

• (Q01480000) The CP no longer resets in a SMLT system when the slaveCPU takes over from the master CPU after enabling HA-CPU and thenmanually rebooting the master CPU. Previously, the CP would resetafter enabling HA-CPU and then manually rebooting the master.

• (Q01490160) Traffic is no longer lost egressing from an R module UNIwith NNI MLT and using OCP vendor port GBICs. Previously, enabling




.

CRs fixed in Release 4.0.4.0 79

and disabling a remote end switch with some OCP SFPs would causethe non-OCP SFPs to lock up without any error indication.


• (Q01219594-01)(Q01424230-01) Fixed this ESM issue; endpoints cannow be configured for more than 14 q-tags.

• (Q01236974) In a Metro Ethernet Routing Switch 8600 dual-homering, the primary now reports the proper state of the last ESU whenpowered off.

• (Q01239869-05) When the log file exceeds its configured size limitduring the bootup process, the Metro Ethernet Routing Switch 8600 nowprints a warning on the console the first time the condition is detected.

• (Q01278848-02) System log messages no longer display “\n” to indicatethe continuation of a line of text. Instead, a log error report that containsseveral lines of text has multiple messages.

• (Q01295840-02) Zeros no longer appear in the MAC entry table outputwhen using the CLI command dump endpoint-mac-table.

• (Q01327693-05) OSPF LSA type 11 packets are no longer beingimproperly processed. Previously, an incorrect check in the code wascausing duplicate insertions of LSA in the database.

• (Q01328700-03) The 8630GBR no longer experiences port lockup ona lane.

• (Q01330437-02) The correct ESM port is now indicated when an ESUring goes down. Previously, if the secondary port went down, theinformation message indicated the primary port had gone down.

• (Q01330502-02) The CLI dump endpoint-mac-table commandnow provides the capability to do a TDI-independent search of MACentries. In addition, port and ESU-specific searches are now supported.

• (Q01336861-02) Some Nortel SFPs no longer generate HW ERRORTxFault if the ESM port is disabled.

• (Q01336877-02) The CLI command show sys info gbic correctlyshows the SFPs located on an ESM 8668 module.

• (Q01353959) Fixed this initialization problem when an ESM 8668module is inserted.

• (Q01360515-01) (Q01443076) In a Metro Ethernet Routing Switch 8600dual-home ring, the IBT MLT ports are no longer removed from theVLAN when deleting an endpoint.




.


• (Q01378820-01) Continuous ring cut messages no longer appear whenthe ring is cut or the secondary port is down.

• (Q01384353-01) When using the log transferFile, the CPU slot numberis no longer appended to the file name.

• (Q01385429-01) CLI and SNMP are no longer inoperable when asecond attempt of a TFTP log file transfer occurs after an initial failedattempt.

• (Q01391005) With a Metro Ethernet Routing Switch 8600 dual-homering, connectivity is no longer lost when the primary ring port is bounced(disabled, followed by enabled).

• (Q01391063) On a Metro Ethernet Routing Switch 8600 secondarydual-home ring, the FDB is no longer corrupted when the primary port isenabled after being disabled.

• (Q01392095) The Metro Ethernet Routing Switch 8600 dual-home ringnow recovers after a loop condition is removed on the secondary.

• (Q01392111) The Metro Ethernet Routing Switch 8600 dual-home ringnow recovers after a loop condition is removed on the primary.

• (Q01395451-01) Listing the GMAC statistics ( dump_gmac ) no longerlocks up the console under rare conditions.

• (Q01415664) You can now dynamically add an MLT to a NNI VLANin a dual-home ring.

• (Q01418474) Fixed this ESM mailbox reset issue.

• (Q01419634-01) A switch running in MSTP Spanning Tree mode is nolonger inoperable when the ESM 8668 card, with a port configured as aprimary or secondary ESU ring port, is reset.

• (Q01424145-01) Fixed ESM timeout that was occurring after multipledisables and enables of UNI port.

• (Q01424707-01) ESM no longer resets after repeatedly disabling andenabling the port.

• (Q01424948-02) Yielding violations were overcome after periods of highutilization on the Metro Ethernet Routing Switch 8600 were reduced.

• (Q01434345) The topology table on a switch that is operating in HighAvailability mode no longer gets emptied after a master CPU failoveroccurs. Previously, following a master CPU failover on a switch runningin 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 traffic to OM1K transparentendpoints, 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 whendeleting dual-home ring endpoints.

Known issues and CRsThis section describes issues and bugs (CRs) known to exist in this softwarerelease.

• (Q01524578) When the dual-home ring is in cut state and a HA-CPUfailover is performed, an ESM port lockup may occur and reset theESM card.

Workaround: None

• (Q01134934) For the best ESM performance, Nortel recommends usingMetro ESM 8668 ports 2 through 8 for applications which are expectedto run the ESM interface close to line rate. On rare occasions, an ESMreboot can occur when a soft port reset happens on port 1 of the ESM,due to high traffic volume on that port.

Workaround: None

• (Q01317956-01) If one SMLT link is missing a VLAN which is configuredon the corresponding SMLT link on the other aggregation switch, theMAC record will be dropped in hardware by the switch missing the VLANrecord.

Workaround: Be sure to configure the same VLAN on both aggregation8600 switches with SMLT.

• (Q01355032-02) The command dump endpoint-mac-table allor dump endpoint-mac-table tdi <tdi> may show duplicateMAC addresses for local TLS many-to-one endpoints after using thecommand config tdi <tdi> flush-mac or config tdi <tdi>endpoint <uni-id> .

Workaround: None

• (Q01393899) For the 8630GBR module, the SFP name details areincomplete: the display refers to the SFP as Lx rather than a CWDMSFP.

Workaround: None

• (Q01406398-01) FDB aging with MSTP/RSTP mode is not accurate.

Workaround: None.

• (Q01424014) 8630GBR module reboots when a UNI port goes inforwarding.




.


Workaround: Disable Spanning Tree on the UNI port.

• (Q01425882-01) When you configure the Metro Ethernet Routing Switch8600 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 notdiscard OEL2 traffic destined to an invalid destination UNI MAC address.

Workaround: This issue only happens when a remote endpoint ismisconfigured.

• (Q01448228) An erroneous error message appears while booting up adual-home ring switch (CheckValid ERROR: FAILED Parameter.Slot = 15). The error has no effect on the switch.

Workaround: None

• (Q01448402) Traffic loss is seen after rebooting the primary switch withring ports disabled in a dual-home ring environment.

Workaround: As soon as the ring ports are enabled the traffic willcontinue.

• (Q01455973) A complete ESM mailbox recovery failure causes theMetro Ethernet Routing Switch 8600 to temporarily pause for 10seconds.

Workaround: This issue is only seen when the switch is under heavyload for an extended period of time.

• (Q01456686-01) Current fabric selection algorithm does not considerthe destination card type. For a Legacy destination, packets from thesame source can arrive from two different fabrics. In this case, thepotential exists for a Legacy card to lose some traffic.

Workaround: None

• (Q01475170) With R-mod UNI TDC tests running in periodic mode, ifthe Source UNI port is down there may be extra printfs appearing onthe console (test_periodic_run: tdc_start_test failed). This does notaffect the operation of the switch.

Workaround: None

• (Q01487134) With HA-CPU failover and large configs, the slave CP mayreset after the primary CP is removed.

Workaround: None

• (Q01479958) While running 500 TDC tests with 1 minute interval, theremay 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 flag in boot.cfg or use a different rloginclient.

• (Q01498864) The CLI command show sys info gbic does notshow the GBICs inserted in 8630 module. This occurs only after aHA-CPU switch-over and remains present until rebooting the chassis.

Workaround: To see if a GBIC is present and determine its type (LX orSX), use the CLI command show port info config. Or, you canuse Device Manager to display the port properties (select a port, thenchoose Edit > Port > Interface). However, the GBIC vendor name isomitted in both cases.

• (Q01499861) The soft port reset mechanism on the ESM module canfalsely trigger and reset an ESM port if multiple types of priority trafficflow through the port.

Workaround: None

Platform(Q01211817) The IEEE 802.1ag Connectivity Fault Management packetsby default use QOS p-bit 7. If you set the priority level for the assigned MAto any other value, the packets will still forward with QOS p-bit 7.

Workaround: None

(Q01246689) SMLT failover links may fail when rebooting an aggregateswitch that is redistributing BGP routes to OSPF routes when OSPFtransitions from the exchange state to the loading state. Traffic from edgeswitch’s will not forward if the backup SMLT links are down.

Workaround: Large distribution route tables may result in downtimes ofup to 4 seconds. When using SMLT connections to edge switches, it isrecommended to reduce number of routes to under 1000.

(Q01268520) In the Nortel Metro Ethernet Routing Switch 8600, the ringremains cut after secondary ring port break occurs with 900Mbps ofmulti-cast flows or greater in the ring.

Workaround: When multi-cast (source) traffic stops, ring will recover. Youmay 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, clearingcust-ip-vlan stats an error fail to clear for each UNI will appear on theconsole. 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 traffic over IP VLAN UNIs will not increment, ormay only intermittently increment, the RX-SP-MCAST and TX-SP-MCASTstats for the selected cust-ip-vlan UNI.

Workaround: None

(Q01295721) If the existing Nortel Metro Ethernet Routing Switch 8600config includes ESU rings with and ESU-MOD-ID 24 configured, whenupgrading to Release 4.0.0.1, 4.0.0.2, or 4.0.2.x, the config will fail to load.

Workaround: You must reconfigure any ESUs with MOD ID 24 to be withinthe supported range of MOD ID 1 to 23. Any UNIs assigned to a ring withESU 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 theprimary ring port (link down on primary ring port), subsequent changes toendpoint level parameters may cause incorrect IP ARP forwarding entries toappear in the database, resulting in packet loss until the ARP entries ageout of the system. Total duration of aging ARP entries may last up to 6hours assuming no traffic from attached devices.

Workaround: If the primary ring breaks at the primary port, once the repairsare made, it is recommended that you flush the IP ARP entries from allSP-VLANs assigned to this ring.

(Q01307226) As of Release 4.0.0.2 and above, cust-ip-vlan 4094 is notvalid. The valid cust-ip-vlan range is 1 to 4093 and 4096. If the existingNortel Metro Ethernet Routing Switch 8600 config includes UNIs withcust-ip-vlan 4094, when upgrading to Release 4.0.0.2 or 4.0.2x, the configwill fail to load.

Workaround: Reconfigure any UNIs assigned to cust-ip-vlan 4094 to avalid qtag range of 1 to 4093 and 4096 before upgrading to Release 4.0.0.2and above.

(Q01307541) In the Nortel Metro Ethernet Routing Switch 8600, if the NNIMLT ports should flap, the show ports stats interface extended commandwill display negative packet counts.

Workaround: This issue does not affect traffic flows out the NNI ports. If theport statistics are cleared, the issue goes away.




.


PBT(Q011321440) When operating the Nortel Metro Ethernet Routing Switch8600 with PBT and HA-CPU, if you admin disable the primary PBT trunkport, an “Application Sync Failed” message may appear on the standbyCPU console port while the trunk port is admin disabled.

Workaround: Re-enable the primary trunk port.

(Q01319462) When operating the Nortel Metro Ethernet Routing Switch8600 with PBT and HA-CPU, if you disconnected the ESU-Ring from thering ports, an error message for each assigned SG may appear on theconsole, but will not impact normal operations for other traffic flows notaffected 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 flapwhen using 8632TX legacy modules for NNI trunk ports.

Workaround: Do not use 8632TX, 8632TXE, or 8632TXM modules for PBTtrunks or EVPN NNI trunk ports.

(Q01351809) When clearing mep stats, a debug message starting withcfmCollectMepStatsFromMip may appear on the console for each mepconfigured on the chassis. This message will not harm existing data flowsand is not an indication of problems.

Workaround: None

(Q01351925) ESM port will incur sustained traffic throughput loss, when thetraffic load is greater than 400M for small packets. This condition occurswhen there are more than 100 service groups (SG) configured on the port.

Workaround: Maintain only 100 SGs or less per ESM port for environmentswhere most traffic consists of small data packets.

(Q01357642) When adding new PBT trunks to R-module ports within anMLT group, all PBT trunks associated with the MLT port may transition to adown 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 thePBT trunk session. Issue occurs only on the first time a new PBT trunk isadded to the MLT port. After port is disabled/enabled, subsequent adds willhave no issue until the chassis is reset.




.


(Q01358652) When configuring 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 loopdesign errors or from accidental assignment of a PBT VLAN to a non-UNIaccess port by discarding packets not intended to be forwarded to thedestination PBT trunk interface. If an unknown destination MAC enters anR-module NNI port for a specific PBT VLAN, the packet will flood out allports assigned to the PBT VLAN.

Workaround: Make sure the PBT VLAN paths are end-to-end, with no VLANloops in the core. Make sure there are no "non-UNI" access ports assignedto the PBT VLAN. As an additional safeguard, Nortel recommends that youdisable all ports along the PBT path, assign the ports to the PBT vlans andonce the configs are re-confirmed, enable the ports.

(Q01361263) If you use a MEP ID greater than 256, the show mep statscommand does not display the MEP statistics.

Workaround: Nortel recommends using MEP IDs in the range of 1 to 256only.

Q01362526 - If you save the run-time config with multiple PBT trunksdisabled and then reboot the chassis with the saved config, the ESM modulemay reset multiple times after the chassis restores the saved config.

Workaround: Save the config with enabled PBT trunks only.

(Q01364125) The service group (SG) does not come up if you add amaintenance endpoint (MEP) after enabling the SG.

Workaround: Always configure a MEP and then enable SG. Always savethe configuration with a MEP added. If you load a configuration with anenabled SG that does not have a MEP, reset the ESM if there are no otherservices on this card.

(Q01364156) You cannot add a previous maintenance association (MA)and maintenance endpoint (MEP) back to a service group (SG) once youchange the SG values, even after deleting the SG.

Workaround: You must delete the SG and reset the ESM module that theSG was assigned to.

(Q01365162) In large scale PBT-based networks, it may take severalminutes for clear mep stats to clear all values. During this time, theconsole locks until all stats are cleared.

Workaround: None.




.


(Q01365176) The clear mep stats ma-domain <value> causesthe following error message to appear multiple times on the console"interrupt: Error enqueueing to Rxlist.”

Workaround: None. Nortel recommends not using this command in thisrelease. However, keep in mind that this issue does not affect the normaloperation of the switch.

R-module UNI(Q01269522, Q01210718, Q01210713, Q01210703, Q01210721,Q01212861 and Q01234797) The command show sys info, show sysinfo card, show sys info asic, or show tech incorrectly displaysinformation for an R-module under the heading of Card FrontType. Thisproblem also happens in Device Manager for the heading Card Type.

Workaround: None

(Q01288587) When using R-module UNIs, when changing the pir-usageflag 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 CIRrate even though there is bandwidth available within the PIR setting.

Workaround: None

(Q01300070) When using R-module UNIs, with cust-ip-vlan assigned, ifIP traffic is present when the R-module access port is first initialized, thetraffic forwarded out the NNI ports will be marked critical (QOS 7) for a shortperiod of time (up to 10 seconds) regardless of the QOS markings on theoriginal data packets. After the port is fully up, the traffic will forward out theNNI ports with the correct QOS markings.

Workaround: None

(Q01300881) When clearing TDI stats with R-module UNIs, a debugmessage starting with tlsSendSyncMsgToRmod may appear on theconsole. This message will not harm existing data flows and is not anindication of problems.

Workaround: None

(Q01303229) When using R-module UNIs, the End-Point Override-P-bit isignored 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)-traffic endpoint parameter is ignored. Expedite and Drop will notwork with-module UNIs.

Workaround: None

High Availability(Q01280082) When operating the Metro Ethernet Routing Switch 8600with HA-CPU, if you reset the primary CPU and than reset the standbyCPU before it has completed the Table Sync process, when the originalCPU (primary) attempts to take over again, a Hardware Fatal error doublefault condition may occur and the CPU will reset again to clean up thetables. Several Error and fault messages will appear during this doublefault condition.

Workaround: After resetting the primary CPU, wait for the HA-CPU tablesync process to complete. When the standby CPU is up and table sync iscomplete, you may reset the new primary CPU to failover back to the originalCPU. Check system logs to confirm 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 theCPU failover service completed, when you re-insert the CPU, the table syncprocess may take up to 8 minutes. During this time, no changes to theconfig will be allowed. Length of time is dependent on the number of SGs,PBT trunks and endpoints configured.

Workaround: Smaller configs take significantly less time to resync the tables.

(Q01350933) After the primary CPU fails and HA-CPU failover occurs, if aPBT trunk failure occurs within 45-50 seconds, the PBT data will not failoverto the secondary backup trunk.

Workaround: To recover from this condition, you must restore the primarytrunk connection on the chassis that has encountered the HA-CPU failoverto restore all PBT traffic flows.

(Q01351914) When HA-CPU failover occurs with active PBT trunks, trafficforwarding over the trunks may see multiple drops of traffic while the standbyCPU takes over.

Workaround: None




.

Related publications 89

Dual-home ring(Q01309776) For dual-home ring environments, any dynamic change to theendpoint parameters should not be performed when the ring is cut. Theresulting change will flush the forwarding entries and may result in a loss oftraffic forwarding for the endpoint.

Workaround: Disable and re-enable the dual-home ring on the primaryswitch followed by the same action on the secondary switch.

Documentation correctionsThere is an error in Installation and Using Device Manager (317832-D).The "Windows minimum requirements" section incorrectly states the PCrequirements for RAM and disk space. To install JDM on your PC, Nortelrecommends that you have a minimum of 256 MB of RAM and 350 MB ofavailable disk space.

Related publicationsThe Metro Ethernet Routing Switch 8600 documentation set includesdocuments from the Enterprise Ethernet Routing Switch that are commonto both platforms.

Hardware installation and user guidesThe following guides provide instructions for installing the chassis and itscomponents:

Installing and Maintaining the Metro Ethernet Routing Switch8600 Series Chassis and Components

320417-B

Installing the Metro Ethernet Routing Switch 8600 SeriesModules

312418-B

Important Information about the Routing Switch 8600 MetroEthernet Services Module 8668 and the CPU/SF Module8691/8692omSF

317980-C

Important Notice Metro Ethernet 8600 CPU ExpansionMezzanine Card

317801-B

Installing a CPU Memory Upgrade 314832-C

Important Notice for using the correct software version withthe 8692SF CPU module

320229-A

Installing the Web Switch Module for the 8600 Series Switch 314969-C

Using the Ethernet Routing Switch 8600 10 Gigabit EthernetModules

315893-D

Installing the Breaker Interface Panel for the 8010co Chassis 312755-F

Installing an AC Power Supply in an 8000 Series Switch 312751-D

Installing a DC Power Supply in an 8000 Series Switch 313070-D




.


Installing a Fan Tray in a Routing Switch 8000 Series Switch 312752-D

Installing SFP & XFP Transceivers & GBIC’s 318034-C

Software installation and user guidesThe following guides provide installation, reference, and configurationinformation for both the Device Manager and Command Line Interface (CLI):

Upgrading to Metro Ethernet Routing Switch 8600 SeriesSoftware Release 4.0.2

316674-B

Getting Started with the Metro Ethernet Routing Switch 8600Software

317814-C

Network Design Guidelines 313197-E

Installing and Using Device Manager 317832-D

Configuring the Metro Ethernet Routing Switch 8600 withDevice Manager

320747-A

Configuring the Metro Ethernet Routing Switch 8600 with CLI 320746-A

Adding MAC addresses to the 8600 Series Chassis 212486-B

Using the 8672ATME and 8672ATMM Modules 209195-F

Configuring IP Routing Operations 314720-E

Configuring BGP Services 314721-D

Configuring Network Management 314723-D

Configuring and Managing Security 314724-D

Configuring VLANs, Spanning Tree, and Link Aggregation 314725-D

Managing Platform Operations 315545-D

Configuring Internet Group Membership AuthenticationProtocol (IGAP).

316343-C

Configuring QoS and IP Filters for Routing Switch 8600 LegacyModules

316433-D

Configuring QoS and IP Filters for Routing Switch 8600 Rmodules

318637-A

Using Diagnostic Tools 317359-B

Using the Packet Capture Tool (PCAP) 315023-D

System Messaging Platform Reference Guide 315015-D

Hard copy technical manualsYou can print selected technical manuals and release notes free, directlyfrom the Internet, using the following directions:




.

How to get help 91

Step Action

1 Go to http://www.nortel.com/support.

2 Scroll to and select the product for which you require documentation.

3 Locate the specific category and model or version for your hardwareor software product.

4 Use Adobe* Acrobat Reader* to open the manuals and releasenotes. (You can go to Adobe Systems at http://www.adobe.com todownload a free copy of Adobe Acrobat Reader.)

5 Search, then print onto most standard printers, any desireddocument sections.

—End—

How to get helpIf you purchased a service contract for your Nortel product from a distributoror authorized reseller, contact the technical support staff for that distributoror reseller for assistance.

If you purchased a Nortel service program, contact Nortel NetworksTechnical Support. To obtain contact information online, go tohttp://www.nortel.com/contactus and click on the Technical Solutionshyperlink.

From the Technical Support page, you can open a Customer ServiceRequest online or find the telephone number for the nearest TechnicalSolutions 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 TechnicalSolutions Center.

An Express Routing Code (ERC) is available for many Nortel products andservices. When you use an ERC, your call is routed to a technical supportperson who specializes in supporting that product or service. To locate anERC for your product or service, go to http://www.nortel.com/erc.




.

http://www.nortel.com/support

http://www.adobe.com

http://www.nortel.com/contactus

http://www.nortel.com/erc





.

Nortel Metro Ethernet Routing Switch 8600

Release Notes — Software Release 4.0.4.3Copyright © 2007, Nortel NetworksAll Rights Reserved.

Publication: NN46220-406Document status: StandardDocument version: 01.01Document 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, configurations, technical data, andrecommendations 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 specified in this document. The information in this documentis 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 theterms 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.

http://www.nortel.com/documentfeedback

NN46220-406_323557-B_01.pdf

Documents

united states government

primaryimagesource text box

copy

ethernet services unit

des flash copy

hexadecimal format 0x00

destination text box

output power rating