NN46220-504 - 02.01 - CFG - (Configuration Provider Backbone Transport)

Nortel Metro Ethernet Routing Switch 8600
Configuration — Provider
Backbone Transport
NN46220-504 (322287-C Rev 01)

.
Document status: Standard
Document version: 02.01
Document date: 3 August 2007
Copyright © 2007, Nortel Networks

All Rights Reserved.
Sourced in Canada and the United States
This document is protected by copyright laws and international treaties. All information, copyrights and any other
intellectual property rights contained in this document are the property of Nortel Networks. Except as expressly
authorized in writing by Nortel Networks, the holder is granted no rights to use the information contained herein and
this document shall not be published, copied, produced or reproduced, modified, translated, compiled, distributed,
displayed or transmitted, in whole or part, in any form or media.
The information in this document is subject to change without notice. The statements, configurations, technical
data, and recommendations in this document are believed to be accurate and reliable, but are presented without
express or implied warranty. Users must take full responsibility for their applications of any products specified in this
document. The information in this document is proprietary to Nortel Networks Inc.
The software described in this document is furnished under a license agreement and may be used only in accordance
with the terms of that license. The software license agreement is included in this document.
Statement of conditions
In the interest of improving internal design, operational function, and/or reliability, Nortel Inc. reserves the right to
make changes to the products described in this document without notice.
Nortel Inc. does not assume any liability that may occur due to the use or application of the product(s) or circuit
layout(s) described herein.
Nortel Inc. software license agreement

NOTICE: Please carefully read this license agreement before copying or using the accompanying software or
installing the hardware unit with pre-enabled software (each of which is referred to as "Software" in this Agreement).
BY COPYING OR USING THE SOFTWARE, YOU ACCEPT ALL OF THE TERMS AND CONDITIONS OF THIS
LICENSE AGREEMENT. THE TERMS EXPRESSED IN THIS AGREEMENT ARE THE ONLY TERMS UNDER
WHICH Nortel WILL PERMIT YOU TO USE THE SOFTWARE. If you do not accept these terms and conditions,
return the product, unused and in the original shipping container, within 30 days of purchase to obtain a credit for
the full purchase price.
1. License grant. Nortel Inc. ("Nortel") grants the end user of the Software ("Licensee") a personal, nonexclusive,
nontransferable license: a) to use the Software either on a single computer or, if applicable, on a single authorized
device identified by host ID, for which it was originally acquired; b) to copy the Software solely for backup purposes in
support of authorized use of the Software; and c) to use and copy the associated user manual solely in support
of authorized use of the Software by Licensee. This license applies to the Software only and does not extend to
Nortel Agent software or other Nortel software products. Nortel Agent software or other Nortel software products are
licensed for use under the terms of the applicable Nortel Inc. Software License Agreement that accompanies such
software and upon payment by the end user of the applicable license fees for such software.
2. Restrictions on use; reservation of rights. The Software and user manuals are protected under copyright
laws. Nortel and/or its licensors retain all title and ownership in both the Software and user manuals, including any
revisions made by Nortel or its licensors. The copyright notice must be reproduced and included with any copy of any
portion of the Software or user manuals. Licensee may not modify, translate, decompile, disassemble, use for any
competitive analysis, reverse engineer, distribute, or create derivative works from the Software or user manuals or
any copy, in whole or in part. Except as expressly provided in this Agreement, Licensee may not copy or transfer the
Software or user manuals, in whole or in part. The Software and user manuals embody Nortel’ and its licensors’
confidential and proprietary intellectual property. Licensee shall not sublicense, assign, or otherwise disclose to
any third party the Software, or any information about the operation, design, performance, or implementation of the
Software and user manuals that is confidential to Nortel and its licensors; however, Licensee may grant permission to
its consultants, subcontractors, and agents to use the Software at Licensee’s facility, provided they have agreed to
use the Software only in accordance with the terms of this license.
3. Limited warranty. Nortel warrants each item of Software, as delivered by Nortel and properly installed and
operated on Nortel hardware or other equipment it is originally licensed for, to function substantially as described in its
accompanying user manual during its warranty period, which begins on the date Software is first shipped to Licensee.
If any item of Software fails to so function during its warranty period, as the sole remedy Nortel will at its discretion
provide a suitable fix, patch, or workaround for the problem that may be included in a future Software release. Nortel
further warrants to Licensee that the media on which the Software is provided will be free from defects in materials
and workmanship under normal use for a period of 90 days from the date Software is first shipped to Licensee. Nortel
will replace defective media at no charge if it is returned to Nortel during the warranty period along with proof of the
date of shipment. This warranty does not apply if the media has been damaged as a result of accident, misuse, or
abuse. The Licensee assumes all responsibility for selection of the Software to achieve Licensee’s intended results
and for the installation, use, and results obtained from the Software. Nortel does not warrant a) that the functions
contained in the software will meet the Licensee’s requirements, b) that the Software will operate in the hardware or
software combinations that the Licensee may select, c) that the operation of the Software will be uninterrupted or
error free, or d) that all defects in the operation of the Software will be corrected. Nortel is not obligated to remedy
any Software defect that cannot be reproduced with the latest Software release. These warranties do not apply to the
Software if it has been (i) altered, except by Nortel or in accordance with its instructions; (ii) used in conjunction
with another vendor’s product, resulting in the defect; or (iii) damaged by improper environment, abuse, misuse,
accident, or negligence. THE FOREGOING WARRANTIES AND LIMITATIONS ARE EXCLUSIVE REMEDIES AND
ARE IN LIEU OF ALL OTHER WARRANTIES EXPRESS OR IMPLIED, INCLUDING WITHOUT LIMITATION ANY
WARRANTY OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. Licensee is responsible for
the security of its own data and information and for maintaining adequate procedures apart from the Software
to reconstruct lost or altered files, data, or programs.
4. Limitation of liability. IN NO EVENT WILL Nortel OR ITS LICENSORS BE LIABLE FOR ANY COST OF
SUBSTITUTE PROCUREMENT; SPECIAL, INDIRECT, INCIDENTAL, OR CONSEQUENTIAL DAMAGES; OR ANY
DAMAGES RESULTING FROM INACCURATE OR LOST DATA OR LOSS OF USE OR PROFITS ARISING OUT OF
OR IN CONNECTION WITH THE PERFORMANCE OF THE SOFTWARE, EVEN IF Nortel HAS BEEN ADVISED OF
THE POSSIBILITY OF SUCH DAMAGES. IN NO EVENT SHALL THE LIABILITY OF Nortel RELATING TO THE
SOFTWARE OR THIS AGREEMENT EXCEED THE PRICE PAID TO Nortel FOR THE SOFTWARE LICENSE.
5. Government licensees. This provision applies to all Software and documentation acquired directly or indirectly by
or on behalf of the United States Government. The Software and documentation are commercial products, licensed
on the open market at market prices, and were developed entirely at private expense and without the use of any U.S.
Government funds. The license to the U.S. Government is granted only with restricted rights, and use, duplication, or
disclosure by the U.S. Government is subject to the restrictions set forth in subparagraph (c)(1) of the Commercial
Computer Software––Restricted Rights clause of FAR 52.227-19 and the limitations set out in this license for civilian
agencies, and subparagraph (c)(1)(ii) of the Rights in Technical Data and Computer Software clause of DFARS
252.227-7013, for agencies of the Department of Defense or their successors, whichever is applicable.
6. Use of software in the European Community. This provision applies to all Software acquired for use within
the European Community. If Licensee uses the Software within a country in the European Community, the
Software Directive enacted by the Council of European Communities Directive dated 14 May, 1991, will apply to
the examination of the Software to facilitate interoperability. Licensee agrees to notify Nortel of any such intended
examination of the Software and may procure support and assistance from Nortel.
7. Term and termination. This license is effective until terminated; however, all of the restrictions with respect to
Nortel’ copyright in the Software and user manuals will cease being effective at the date of expiration of the Nortel
copyright; those restrictions relating to use and disclosure of Nortel’ confidential information shall continue in effect.
Licensee may terminate this license at any time. The license will automatically terminate if Licensee fails to comply
with any of the terms and conditions of the license. Upon termination for any reason, Licensee will immediately
destroy or return to Nortel the Software, user manuals, and all copies. Nortel is not liable to Licensee for damages in
any form solely by reason of the termination of this license.
8. Export and re-export. Licensee agrees not to export, directly or indirectly, the Software or related technical
data or information without first obtaining any required export licenses or other governmental approvals. Without
limiting the foregoing, Licensee, on behalf of itself and its subsidiaries and affiliates, agrees that it will not, without
first obtaining all export licenses and approvals required by the U.S. Government: (i) export, re-export, transfer, or
divert any such Software or technical data, or any direct product thereof, to any country to which such exports or
re-exports are restricted or embargoed under United States export control laws and regulations, or to any national
or resident of such restricted or embargoed countries; or (ii) provide the Software or related technical data or
information to any military end user or for any military end use, including the design, development, or production of
any chemical, nuclear, or biological weapons.
9. General. If any provision of this Agreement is held to be invalid or unenforceable by a court of competent
jurisdiction, the remainder of the provisions of this Agreement shall remain in full force and effect. This Agreement
will be governed by the laws of the state of California.
Should you have any questions concerning this Agreement, contact Nortel Inc., 2375 N. Glenville Dr., Richardson, TX
75082.
LICENSEE ACKNOWLEDGES THAT LICENSEE HAS READ THIS AGREEMENT, UNDERSTANDS IT, AND
AGREES TO BE BOUND BY ITS TERMS AND CONDITIONS. LICENSEE FURTHER AGREES THAT THIS
AGREEMENT IS THE ENTIRE AND EXCLUSIVE AGREEMENT BETWEEN Nortel AND LICENSEE, WHICH
SUPERSEDES ALL PRIOR ORAL AND WRITTEN AGREEMENTS AND COMMUNICATIONS BETWEEN THE
PARTIES PERTAINING TO THE SUBJECT MATTER OF THIS AGREEMENT. NO DIFFERENT OR ADDITIONAL
TERMS WILL BE ENFORCEABLE AGAINST Nortel UNLESS Nortel GIVES ITS EXPRESS WRITTEN CONSENT,
INCLUDING AN EXPRESS WAIVER OF THE TERMS OF THIS AGREEMENT.
5
Contents
New in this release 9
Features 9
Other changes 10
Introduction 11
Navigation 11
Overview 11
Acronyms 12
Configuring PBT with the CLI 15

Navigation 15
Roadmap of CLI commands 16
Discarding unknown MAC addresses 22
Changing the base chassis MAC address 23
Configuring CFM ethernet type 24
Creating a maintenance domain 24
Creating a maintenance association 25
Creating a maintenance endpoint 27
Displaying MEP statistics 30
Creating a remote maintenance endpoint 32
Displaying RMEP statistics 33
Configuring loopback messages 35
Configuring linktrace messages 37
Creating a maintenance intermediate point 39
Displaying MIP statistics 39
Creating a transparent domain identifier 41
Configuring the TDI endpoint 43
Creating service instance IDs 46
Configuring an I-SID endpoint 47
Configuring a PBT VLAN 51
Configuring port VLANs for MEPs and MIPs 54
Creating the local end 56
Displaying PBT trunk statistics 60
Configuring a trunk group 61
Configuring PBT local switching 65

Configuration — Provider Backbone Transport
NN46220-504 02.01 Standard
4.2 3 August 2007
.
6 Contents
Displaying NNI connections 65

Displaying NNI statistics 66
Tracking dropped PBT packets 67
Configuring PBT with MSTP 69
Configuring PBT with Device Manager 71

Creating a maintenance domain 72
Monitoring CFM loopback messages 85
Monitoring CFM linktrace messages 87
Configuring a TDI endpoint 91
Configuring service instance IDs 98
Configuring a CFM VLAN for MEPs 109
Configuring a CFM VLAN for MIPs 111
Creating the local end of a PBT trunk 112
Displaying PBT trunk statistics 116
Configuring PBT local switching 119
Displaying NNI statistics 120
Configuring PBT policing options 121
PBT configuration example 125

Navigation 126
PBT domains 126
MERS 8600 number 1 129
Maintenance domain configuration 130
Maintenance association configuration 130
Maintenance endpoint configuration 130
Remote maintenance endpoint configuration 131
Port configuration 131
PBT-VLANs configuration 131
STG configuration 132
VLAN configuration 132

NN46220-504 02.01 Standard
4.2 3 August 2007
.
Contents 7
Trunk configuration 132

Trunk-group configuration 133
UNI configuration 133
I-SID configuration 134
Maintenance domain configuration 134
Maintenance association configuration 135
Maintenance endpoint configuration 135
Remote maintenance endpoint configuration 135
Port configuration 136
PBT-VLANs configuration 136
STG configuration 136
VLAN configuration 136
Trunk configuration 137
Trunk-group configuration 138
UNI configuration 138
I-SID configuration 138
MERS 8600 Three Switch Configuration 139
Transient switch with static entry point configuration 139

NN46220-504 02.01 Standard
4.2 3 August 2007
.
8 Contents

NN46220-504 02.01 Standard
4.2 3 August 2007
.
9
New in this release

The following sections detail what is new in Configuration — Provider
Backbone Transport (NN46220-504) for Release 4.2.
• Features
• "Other changes" (page 10)
Features
See the following sections for information about new features in this release:
• Base chassis MAC address — Release 4.2 enables you to change the
base chassis MAC address. For information, see "Changing the base
chassis MAC address" (page 23).
• Loopback message (LBM) enhancements — The LBM enhancements
are additional flags that support throughput and round trip time modes
of operation, a timeout interval, an inter-frame transmit interval, and fill
test patterns. For information, see "Configuring loopback messages"
(page 35).
• Trunk labels — Use the PBT trunk and trunk group labels to provide
more information that traps can use. For information, see "Creating the
local end " (page 56) and "Configuring a trunk group" (page 61).
• PBT trunk statistics — This feature enables you to display statistics on
the PBT trunk queuing classes. For information, see "Displaying PBT
trunk statistics" (page 60).
• Local switching — Use this feature to configure endpoints on the same
MERS 8600 so they can transport data locally. For information, see
"Configuring PBT local switching" (page 65).
• Dropped packets — Use this feature to track dropped packets with
unknown destination MAC addresses and dropped packets per queuing
class. For information, see "Tracking dropped PBT packets" (page 67).
• PBT with MSTP — MERS 8600 supports PBT in an MSTP network.
MERS 8600 does not support RSTP. You can configure MSTP only.
The MSTP implementation is RSTP-based, as the CIST and MSTI are

NN46220-504 02.01 Standard
4.2 3 August 2007
.
10 New in this release
RSTP implementations. For information, see "Configuring PBT with

MSTP" (page 69).
Other changes
See the following sections for information about changes that are not related
to features:
• Reorganization of the Connectivity Fault Management (CFM) content —
CFM is a diagnostic tool that supports both PBB and PBT. This document
describes the CFM commands required for configuring PBT. For more
general CFM information, see Troubleshooting (NN46220-701).

NN46220-504 02.01 Standard
4.2 3 August 2007
.
11
Introduction
This guide provides instructions for configuring Provider Backbone
Transport (PBT) on the Nortel* Metro Ethernet Routing Switch 8600. It
includes information for using the Device Manager graphical user interface
(GUI) and the command line interface (CLI) to configure and manage PBT
on the switch. For information on PBT concepts, see Nortel Metro Ethernet
Routing Switch Fundamentals (NN46220-100).
To reinforce the PBT configuration steps, see "PBT configuration example"

(page 125), which provides a sample configuration example with links to the
step-by-step procedures in "Configuring PBT with the CLI" (page 15) and
"Configuring PBT with Device Manager" (page 71).
Navigation
• "Overview" (page 11)
• "Acronyms" (page 12)
• "Configuring PBT with the CLI" (page 15)
• "Configuring PBT with Device Manager" (page 71)
• "PBT configuration example" (page 125)
Overview
PBT does not use or process layer 3 address information. PBT is strictly a
layer 2, connection-oriented feature. As such, you can use PBT to provision
point-to-point trunks and services. This enables a Service Provider (SP) to
add static provisioning to a standard Ethernet network.
PBT ensures that a predictable customer route is available over the

backbone with normal and failover paths. This predictability ensures
service level agreements (SLA) between SPs and customers. Because of
its reliability and seamless integration, SPs can use PBT to leverage the
simplicity and cost effectiveness of Ethernet, while adding carrier-grade
features. This allows SPs to extend Ethernet in LANs into the metropolitan
area network (MAN) and beyond. The practical application of PBT is that

NN46220-504 02.01 Standard
4.2 3 August 2007
.
12 Introduction
it provides the ideal infrastructure for triple play services, Ethernet-based

virtual private network (VPN) services, IPTV delivery and future bandwidth
intensive services.
PBT addresses the main challenges carriers face when deploying an

end-to-end Ethernet network. These challenges include resilience to
failures, scalability, and seamless integration. To meet these challenges,
PBT supports both Connectivity Fault Management (802.1ag) and Provider
Backbone Bridging (802.1ah).
PBT disables MAC address learning and Spanning Tree Protocol (STP). It
also disables broadcast-on-unknown. This means that it does not allow
broadcast and drops frames that do not have a forwarding record.
Acronyms
This manual uses the following acronyms.
802.1ad IEEE standard for Provider Bridge Networks

802.1ag IEEE standard for Connectivity Fault Management
802.1ah IEEE standard for PBB, also called MAC-in-MAC
or 802.1ah
802.1q IEEE standard for virtual LANs
BPDU bridge protocol data unit
CCM continuity check message (part of CFM)
CFM connectivity fault management
LBM loopback message (part of CFM)
LBR loopback reply (part of CFM)
LTM linktrace message (part of CFM)
MA maintenance association
MAC media access control
MAC-in-MAC Industry-standard term for service provider
encapsulation and is also called 802.1ah. (See
802.1ah and OEL2.)
MD maintenance domain
MEP maintenance endpoint
MEPID maintenance endpoint ID
MTU maximum transmission unit
NNI network-to-network interface
NPU network processing unit
OEL2 Optical Ethernet Layer 2

NN46220-504 02.01 Standard
4.2 3 August 2007
.
Acronyms 13
PBB Provider Backbone Bridging

SI service instance
SP service provider
SPVID service provider VLAN identifier
TD transparent domain
TDI transparent domain identifier
TG trunk group

NN46220-504 02.01 Standard
4.2 3 August 2007
.
14 Introduction

NN46220-504 02.01 Standard
4.2 3 August 2007
.
15
Configuring PBT with the CLI

This chapter describes how to configure Provider Backbone Transport
(PBT) on the Nortel Metro Ethernet Routing Switch 8600 using the CLI.
For information about PBT concepts, see Fundamentals (NN46220-100).
For Device Manager configuration information, see "Configuring PBT with
Device Manager" (page 71).
Navigation
• "Roadmap of CLI commands" (page 16)
• "Discarding unknown MAC addresses" (page 22)
• "Changing the base chassis MAC address" (page 23)
• "Configuring CFM ethernet type" (page 24)
• "Creating a maintenance domain" (page 24)
• "Creating a maintenance association" (page 25)
• "Creating a maintenance endpoint" (page 27)
• "Displaying MEP statistics" (page 30)
• "Creating a remote maintenance endpoint" (page 32)
• "Displaying RMEP statistics" (page 33)
• "Configuring loopback messages" (page 35)
• "Configuring linktrace messages" (page 37)
• "Creating a maintenance intermediate point" (page 39)
• "Displaying MIP statistics" (page 39)
• "Creating a transparent domain identifier" (page 41)
• "Configuring the TDI endpoint" (page 43)
• "Creating service instance IDs" (page 46)
• "Configuring an I-SID endpoint" (page 47)
• "Configuring a PBT VLAN" (page 51)

NN46220-504 02.01 Standard
4.2 3 August 2007
.
16 Configuring PBT with the CLI
• "Configuring port VLANs for MEPs and MIPs" (page 54)

• "Creating the local end " (page 56)
• "Displaying PBT trunk statistics" (page 60)
• "Configuring a trunk group" (page 61)
• "Configuring PBT local switching" (page 65)
• "Displaying NNI connections" (page 65)
• "Displaying NNI statistics" (page 66)
• "Tracking dropped PBT packets" (page 67)
• "Configuring PBT with MSTP" (page 69)
Roadmap of CLI commands

The following roadmap lists the PBT commands for use as a quick reference.
Command Parameter
config bootconfig base-chassis-mac
<mac-address>
config bootconfig flags unknown-destmac-dis
card <true|false>
config cfm info
ethertype <ether type>
pm <enable|disable>
port-vid <value>
config cfm md <md-name> info
create [index <value>]
delete
event-trap <enable|disable>
maint-level <level>
pm <enable|disable>
config cfm md <md-name> ma <ma-name> info
auto-detect <enable|disable>
ccm-interval <integer>
ccm-rdi <enable|disable>
ccm-type <multicast|unicast>
delete
event-trap <enable|disable>

NN46220-504 02.01 Standard
4.2 3 August 2007
.
Command Parameter
pm <enable|disable>
remove-auto-discovered-rmep <rmep-id>
config cfm md <md-name> ma <ma-name> mep info
<mep-id>
create
delete
state <enable|disable>
ccm-priority <integer>
ccm-tx <enable|disable>
remove-auto-discovered-rmep <rmep-id>
lbm <1..8191|00.00.00.00.00.00> [-c <value>]
[-p <value>] [-d <value>]
ltm <1..8191|00.00.00.00.00.00> [-t <value>]
[-p <value>]
show cfm mep stats
[md <value>] [ma <value>] [mep-id <value>]
[defect] [no-defect]
config cfm md <md-name> ma <ma-name> info
rmep <rmep-id>
create
delete
remote-mac <value>
show cfm rmep stats
[md <value>] [ma <value>] [rmep-id <value>]
[up] [down]
lbm <mdName.maName.mepId.rmepId | -c <value>
mdName.maName.mepId.rmepMac>
-d <value>
-f <value>
-i <value>
-m <value>
-p <value>
-t <value>
ltm <mdName.maName.mepId.rmepId | -t <value>
mdName.maName.mepId.rmepMac>
-p <value>
config cfm md <md-name> mip <mip-name> info

NN46220-504 02.01 Standard
4.2 3 August 2007
.
Command Parameter
delete
show cfm mip stats
config tdi <tdi-id> info
create
delete
ForceDelete
clear-stats
flush-mac
mapped-vlan <vid>
mux-mode <oneToone|manyToone>
name <string>
state <disable|enable|ForceDisable>
pbt <enable|disable>
evpn-broadcast-optimization <enable|disable>
config tdi <tdi-id> end-point <endpt-id> info
create
delete
default-tdi <enable|disable>
add-qtags <qtags>
remove-qtags <qtags>
add-outer-qtag <outer-qtag>
clear-stats
bpdu-traffic <normal|expedite|drop>
flush-mac
local-mac-age-timer <aging>
policing-option <pre-encap|post-encap>
remote-mac-age-timer <aging>
mac-table-size <size>
mac-table-watermark <size>
name <string>
connection <any2any|hub|spoke|p2p>
remote-uni <ipaddr> [mac <value>]

NN46220-504 02.01 Standard
4.2 3 August 2007
.
Command Parameter
ingress-cos-profile <string>
ingress-policer <enable|disable>
egress-cos-profile <string>
egress-policer <enable|disable
priority-mapping <pri-map-string>
override-pbit-pri <true|false>
override-type <tos|dscp>
color-based-remarking <enable|disable>
drop-red-packets <true|false>
trunk-group <string>
ingress-mirror <enable|disable>
egress-mirror <enable|disable>
add-user-label1 <string>
config i-sid <isid-id> info
create
delete
ForceDelete
b-vlan <vid>
name <string>
state <enable|disable|ForceDisable>
flush-mac
mac-age-timer <secs>
mac-table-size <size>
mac-table-watermark <percent>
evpn-broadcast-optimization <enable|disable>
mux-mode <oneToone|manyToone>
pbt <enable|disable>
config i-sid <isid-id> end-point mlt <mltId> info
create
delete
add-c-vlan <c-vlan-ids>

NN46220-504 02.01 Standard
4.2 3 August 2007
.
Command Parameter
remove-c-vlan <c-vlan-ids>
s-vlan <s-vlan-id>
name <string>
connection <any2any|p2p>
service-type <tls-transparent|tls-switched|qnq1
|qnq2>
defaullt-isid <enable|disable>
config i-sid <isid-id> end-point port <slot/port> info
create
delete
add-c-vlan <c-vlan-ids>
remove-c-vlan <c-vlan-ids>
s-vlan <s-vlan-id>
name <string>

NN46220-504 02.01 Standard
4.2 3 August 2007
.
Command Parameter
connection <any2any|p2p>
service-type <tls-transparent|tls-switched|qnq1
|qnq2>
defaullt-isid <enable|disable>
cfm-vid <cfm-vid-id> add-client-mep
<mdName.maName.mep_id>
cfm-vid <cfm-vid-id> remove-client-mep
<mdName.maName.mep_id>
l2pt-mac-swap cdp <enable|disable>
l2pt-mac-swap vtp <enable|disable>
l2pt-mac-swap stp <enable|disable>
config vlan <vid> cfm-port <slot/port> info
add-mep <mdName.maName.mepId>
remove-mep <mdName.maName.mepId
add-mip <mdName.mipId
remove-mip <mdName.mipId>
config pbt-vlans <vid> info
add <vid>
remove <vid>
config pbt-trunk <trunk-name> info
create
port <port>
source-mac <value>

NN46220-504 02.01 Standard
4.2 3 August 2007
.
Command Parameter
remote-peer-mac <value>
delete
vlan <vid>
reverse-vlan <vid>
hold-time <interval-timer>
add-mep <mdName.maName.mep-id>
remove <mep>
subport-queue-set <index>
config pbt-trunk info [name <value>] [port
<value>] [summary]
show pbt-trunk info [name <value>] [port
<value>] [summary]
config trunk-group <trunk-group-name> info
create
delete
loopback-vlan <vid>
primary-trunk <trunk-name>
secondary-trunk <trunk-name>
active-trunk <trunk-name>
revertive <enable|disable>
show pbt-nni info
[nni <value>] [uni <value>] [tdi <value>] [isid
<value>] [pw-index <value>]
show pbt-nni stats
[port <value>]
Discarding unknown MAC addresses

Before you start configuring PBT, set the bootconfig flag to discard
unknown MAC destinations.

NN46220-504 02.01 Standard
4.2 3 August 2007
.
Changing the base chassis MAC address 23
Procedure steps
Step Action
1 Set the bootconfig flag to true. The default setting is false.

config bootconfig flags unknown-destmac-discard true
2 Reboot the MERS 8600.
—End—
Changing the base chassis MAC address

Change the base chassis MAC address to specify the MAC address you
want to use in the network. This feature gives service providers more control
over the provider MAC addresses it wants to use in the network.
After changing the MAC address, the system prompts you to restart the
chassis. If you do not restart the chassis, the base MAC address change is
ignored. In HA systems, the primary and standby CPUs must be restarted
immediately for the chassis MAC address change to work correctly. If you
do not restart both CPUs, the chassis would not be in a consistent state.
The following restrictions apply to setting a new base chassis MAC address:
• If the MAC address capacity (number of MAC addresses on the chassis)
for the chassis is 2n, then the chassis base MAC should have the last n
bits set to zero. So if the MAC address capacity for the chassis is 1024
(which is the factory default), the last 10 bits should be all zeros.
• The first octet has to be all zeros. This avoids setting the base chassis
address to a multicast or broadcast address.
• The fourth and fifth octets cannot be all zeros. At least one of them
has to be non-zero.
• For the PBT base MAC, the last 10 bits should always be 0x3df.
• NMS, JDM, and PSP do not support changing the base chassis MAC
address.
Procedure steps
Step Action
1 Change the base MAC address.

config base-chassis-mac <mac-address>
2 Enter Y after the following system message to reboot the chassis.

NN46220-504 02.01 Standard
4.2 3 August 2007
.
Changing the chassis MAC requires the system reboot.

Do you want to boot? <Y|N>
—End—
Configuring CFM ethernet type

Use this procedure to run at a different connectivity fault management
(CFM) ethernet type than the default of 0x88e6. The ethernet type is used
in the continuity check message (CCM) header to identify the packet as
a CCM packet.
Procedure steps
Step Action
1 Configure the CFM ethernet type with the following command.

config cfm ethertype <value>
—End—
Variable definintions
Variable Value
ethertype <value> Specify the ethernet type as something other
than the default (0x88e6). The range is
0x1..xffff.
Creating a maintenance domain

Create a maintenance domain (MD) to define a part of the network
for connectivity fault management (CFM). With CFM, you can verify
connectivity, detect and isolate faults, and ensure the delivery of services.
CFM is a diagnostic tool that supports both PBB and PBT. This document
describes the CFM commands required for configuring PBT. For more
general CFM information, including Performance Management (PM), see
Troubleshooting (NN46220-701).
One MD may contain several maintenance associations and maintenance

endpoints. (The following sections describe how to configure these
features.) You can configure an MD for different levels within the metro
network: Trunk Group and Service Instance.

NN46220-504 02.01 Standard
4.2 3 August 2007
.
Procedure steps
Step Action
1 Create an MD with the following command and a string of 1 to 22

characters that uniquely names the MD.
config cfm md <md-name> create index <value>
2 Verify your configuration.

show cfm md info
The following shows output for the show cfm md info command.
—End—
Creating a maintenance association

Create a maintenance association (MA) to link a service instance (trunk,
VLAN, or VPN) to an MD. You also use this feature to set the continuity
check message (CCM) interval.
Prerequisites
• Create an MD. For information, see "Creating a maintenance domain"
(page 24).
Procedure steps
Step Action
1 Create an MA with the following command and a string of 1 to 22

characters that uniquely names the MA.
config cfm md <md-name> ma <ma-name> create index
<value>
2 Customize your MA by changing the default settings of preconfigured

parameters. For information, see the following variable definitions
table.

NN46220-504 02.01 Standard
4.2 3 August 2007
.
—End—
Variable definitions
Variable Value
auto-detect <enable|disable> Enables or disables the MA from automatically
detecting remote MEPs. The default is disable.
When you configure a trunk, PBT no longer
automatically adds or removes the MAC
address for the trunk VLAN to the forwarding
database entry. This eliminates the possibility of
the MAC address getting inadvertently removed
when the last trunk to this VLAN is removed.
ccm-interval <integer> Sets the time interval (in milliseconds) for how
often continuity check messages (CCM) are
sent between endpoints within a domain. The
options are: 10, 100, 1000, 10000, 60000, and
600000. The default is 10000.
create [index <value>] Creates a maintenance association.
remove-auto-discovered-rmep <rmep-id> Removes the specified remote MEP.
Example of configuring a maintenance association

This example configures an MA called matr1901.
Step Action
1 Name the MA matr1901 and assign the index value of 1.

config cfm md TRUNKDOMAIN ma matr1901 create index 1
2 Change the CCM interval to 1000.

config cfm md TRUNKDOMAIN ma matr1901 ccm-interval 1000

show cfm ma info
The following shows the current configuration information for the
show cfm ma info command.

NN46220-504 02.01 Standard
4.2 3 August 2007
.
—End—
Creating a maintenance endpoint

Create a maintenance endpoint (MEP) to link an endpoint to an MA. MEPs
originate CFM messages and respond to CFM messages sent by other
MEPs. You also use this feature to set the CFM message values.
Prerequisites
(page 24).
• Create an MA. For information, see "Creating a maintenance
association" (page 25).
Procedure steps
Step Action
1 Create a MEP with the following command and a string of 1 to 8191

characters that uniquely identifies the MEP.
config cfm md <md-name> ma <ma-name> mep <value> create
2 Enable the MEP.

config cfm md <md-name> ma <ma-name> mep <value> state
enable
3 Customize your MEP by changing the default settings of

preconfigured parameters. For information, see the following
variable definitions table.
—End—

NN46220-504 02.01 Standard
4.2 3 August 2007
.
Variable Value
ccm-priority <integer> Sets the priority level for transmitting continuity
check messages. The range is from 0 to 7, and
the default is 7.
ccm-tx <enable|disable> Enables or disables sending continuity check
messages from this MEP. The default is enable.
create Creates a maintenance endpoint.
lbm <1..8191|00.00.00.00.00.00> [-c Configures the loopback messages sent from
<value>] [-d <value>] [-f <value>] this MEP.
[-i <value>] [-m <value>] [-p
• -c <value> specifies the burst count
<value>] [-t <value>]
number, which determines how many LBM
messages to send to the remote MEP. The
default burst count is 1, and the maximum
count is 10000.
• -d <value> sets the size of the LBM. The
maximum size is 400 (in bytes). The default
size is the size of the LBM PDU.
• -f <value> sets the fill test pattern in the
LBM PDU to one of the following options
(0-3):
— 0 – Null signal (all zeros) without cyclical
redundancy checking (CRC) - 32
— 1 – Null signal with CRC-32
— 2 – Pseudo-random bit sequence
(PRBS) without CRC-32
— 3 – PRBS with CRC-32
The default value is 3.

• -i <value> sets the interval between LBM
frames with a range of (0, 10..1000) msecs
and a default value of 0 msecs. The value
of 0 msecs indicates to send the frames as
fast as possible.
• -m <value> sets the mode for the transmit
loopback service: RoundTripTime or
throughput mode of operation.
— 1 – This is the throughput mode, which
transmits LBM frames at the configured
transmit interval rate for the burst count
number (the -c option)

NN46220-504 02.01 Standard
4.2 3 August 2007
.
Variable Value
— 2 – This is the RoundTripTime mode,

which transmits lBM frames one at
a time and records the transmit time
locally
The default is 1.
• -p <value> sets the priority level for
transmitting continuity check messages.
The range is from 0 to 7, and the default
is 7.
• -t <value> sets the interval to wait for
an LBM timeout. The range is 1..10, (in
seconds). The default is 7.
ltm <1..8191|00.00.00.00.00.00> [-t Configures the linktrace messages sent from
<value>] [-p <value>] this MEP.
• -t <value> specifies the time-to-live (TTL)
value for the linktrace message. Each MP
on the way to the destination decrements
the TTL field in the linktrace frame. The
linktrace message is forwarded until it
reaches its destination or the TTL value is
decremented to 0. The default TTL is 64.
• -p <value> sets the priority level for
transmitting continuity check messages.
The range is from 0 to 7, and the default
is 7.
remove-auto-discovered-rmep Removes the specified remote MEP.
<rmep-id>
state <enable|disable> Administratively enables or disables the
maintenance endpoint. The default is disable.
Example of configuring a maintenance endpoint

This example configures a MEP with an ID of 10.
Step Action
1 Assign the MEP ID to 10.

config cfm md TRUNKDOMAIN ma matr1901 mep 10 create
2 Enable the MEP.

config cfm md TRUNKDOMAIN ma matr1901 mep 10 state
enable

NN46220-504 02.01 Standard
4.2 3 August 2007
.
3 Change the CCM priority to 0.

config cfm md TRUNKDOMAIN ma matr1901 ccm-priority 0

show cfm mep info
The following shows the current configuration information for the
show cfm mep info command.
—End—
Displaying MEP statistics

Display MEP statistics to monitor your system.
Prerequisites
(page 24).
• Create a MEP. For information, see "Creating a maintenance endpoint"
(page 27).
Procedure steps
Step Action
1 Display MEP statistics.

show cfm mep stats
2 Refer to the following figure for sample output for the show cfm
mep stats command. For a description of the column names, see
the variable definitions table following this procedure.

NN46220-504 02.01 Standard
4.2 3 August 2007
.
3 Clear statistics shown in the Maintenance Endpoint CCM stats table

with the following command.
clear cfm mep stats [ma-domain] [ma-assn] [mep-id]
This command clears the statistical values for any or all of
the following: maintenance domain, maintenance association,
maintenance endpoint.
4 Show a summary of all the MEPs.
show cfm mep summary
The following shows sample output for this command.
—End—
Variable Value
DOMAIN_NAME Shows the name of the maintenance domain
that these statistics are derived from.
ASSN_NAME Shows the name of the maintenance
association that these statistics are derived
from.

NN46220-504 02.01 Standard
4.2 3 August 2007
.
Variable Value
MEP_ID Shows the number of the maintenance
endpoint that these statistics are derived from.
TX_COUNT The total number of CFM messages
transmitted from the remote MEP.
DEFECT The total number of CFM messages missing
on the remote MEP.
Creating a remote maintenance endpoint

Create a remote maintenance endpoint (RMEP) to link the MAC address
of the remote endpoint to an MA.
Prerequisites
(page 24).
(page 27).
Procedure steps
Step Action
1 Create an RMEP with the following command and using a string of 1

to 8191 characters that uniquely identifies the RMEP.
config cfm md <md-name> ma <ma-name> rmep <rmep-id>
create
2 Specify the endpoint on another MERS 8600.

config cfm md <md-name> ma <ma-name> rmep <rmep-id>
remote-mac <mac-address>

show cfm rmep info

NN46220-504 02.01 Standard
4.2 3 August 2007
.
—End—
ATTENTION
If you see all zeros for the MAC addresses, disable the auto-detect feature. For
more information, see "Creating a maintenance association" (page 25). To see all
MAC addresses detected, enter show cfm rmep all.
Variable Value
create Creates a maintenance endpoint.
remote-mac <mac-address> Specifies the MAC address of the remote
MEP MAC.
Displaying RMEP statistics

Display RMEP statistics to monitor your system.
Prerequisites
(page 24).
(page 27).
• Create an RMEP. For information, see "Creating a remote maintenance
endpoint" (page 32).
Procedure steps
Step Action
1 Display RMEP statistics.

NN46220-504 02.01 Standard
4.2 3 August 2007
.
show cfm rmep stats
rmep stats command. For a description of the column names,
see the variable definitions table following this procedure.
3 Clear statistics shown in the Remote Maintenance Endpoint Stats

table with the following command.
clear cfm rmep stats [ma-domain] [ma-assn] [rmep-id]
This command clears the statistical values for any or all of the
following: maintenance domain, maintenance association, and
remote maintenance endpoint.
4 Show a summary of all the RMEPs.

show cfm rmep summary
—End—

NN46220-504 02.01 Standard
4.2 3 August 2007
.
Configuring loopback messages 35
Variable Value
DOMAIN_NAME Shows the name of the maintenance domain
ASSN_NAME Shows the name of the maintenance
association that these statistics are derived
from.
MEP_ID Shows the number of the maintenance
endpoint that these statistics are derived from.
RMEP_ID The total number of CFM messages
transmitted from the .
STATE Shows the current state of the remote RMEP.
RX_COUNT The total number of CFM messages received
by the local MEP.
SEQ_ERR The total number of CFM messages missing
from the remote MEP.
RDI Set to true when RMEP is sending Remote
Defect Indication (RDI), otherwise false.
Configuring loopback messages

Configure connectivity fault management (CFM) loopback messages to test
the connection between Maintenance Points (MP). You can also use this
feature to diagnose faults in the network as well as to measure performance.
The CFM solution uses both linktrace and loopback messages to isolate
the exact point of failure. When a port fails, the MAC addresses are flushed
from the forwarding database (FDB) of the VLANs associated with that port.
When this happens, the linktrace message (LTM) sent to the remote MEP
isolates the area of failure because the destination MERS 8600 does not
respond to the LTM. When you send LBMs to the ports on the unresponsive
MERS 8600, you can discover exactly which port failed.
Loopback messages are unicast messages that you can address to either
a MEP or a MIP, but only a MEP can initiate a loopback message. The
receiving Maintenance Point (MP) responds with a loopback reply. This
mechanism provides fault verification for the MD.
Prerequisites
(page 24).

NN46220-504 02.01 Standard
4.2 3 August 2007
.

(page 27).
Procedure steps
Step Action
1 Navigate to the MEP that you want to originate the LBM.

/config/md/<md-name>/ma/<ma-name>/mep/<mep-id>
2 Use the first command to configure an LBM when the destination is

a MEP. Use the second command when the destination is a MIP.
lbm <remote-mep-id|remote-mep-mac>
lbm <remote-mip-mac>
3 Customize the LBM by changing the default settings of preconfigured

table.
—End—
Variable Value
-c <value> Sets the burst count number, which
determines how many LBM messages to
send to the remote MEP. The default burst
count is 1, and the maximum count is 200.
-d <value> Sets the size of the LBM. The maximum
size is 400 (in bytes). The default size is
the size of the LBM PDU.
-f <value> Sets the fill test pattern in the LBM PDU to
one of the following options (0–3):
• 0 — Null signal (all zeros) without
cyclical redundancy checking (CRC)
-32
• 1 — Null signal with CRC-32
• 2 — Pseudo-random bit sequence
(PRBS) without CRC-32
• 3 — PRBS with CRC-32
The default value is 3.

NN46220-504 02.01 Standard
4.2 3 August 2007
.
Configuring linktrace messages 37
Variable Value
-i <value> The interval between LBM frames with
a range of (0, 10…1000) msecs with a
default value of 0 msecs. The value of 0
msecs indicates to send the frames as fast
as possible."
-m <value> Sets the mode for the transmit loopback
service: RoundTripTime or throughput
mode of operation.
• 1 — This is the throughput mode,
which transmits LBM frames at the
configured transmit interval rate for
the burst count number (-c).
• 2 — This is the RoundTripTime mode,
which transmits LBM frames one at
a time and records the transmit time
locally.
The default is 1.
-p <value> Sets the priority level for transmitting
continuity check messages. The range is
from 0 to 7, and the default is 7.
-t <value> Sets the interval to wait for an LBM
timeout. The range is 1..10, (in seconds),
the default value is 3.
Configuring linktrace messages

Configure CFM linktrace messages (LTM) to isolate faults in the network.
LTMs trace the hop-by-hop path to the destination MEP or MIP. All the
MPs along the path to the destination intercept the linktrace messages
and send a reply. This enables you to isolate failures to smaller segments
of the network.
Prerequisites
(page 24).

NN46220-504 02.01 Standard
4.2 3 August 2007
.

(page 27).
Procedure steps
Step Action
1 Navigate to the MEP that you want to originate the LTM.

/config/md/<md-name>/ma/<ma-name>/mep/<mep-id>
2 Configure an LTM.
ltm <remote-mep-id|remote-mep-mac>
3 Customize the LTM by changing the default settings of preconfigured

table.
—End—
Variable Value
-p <value> Sets the priority level for transmitting
continuity check messages. The range is
from 0 to 7, and the default is 7.
-t <value> Specifies the time-to-live (TTL) value
(1..64) for the linktrace message. Each
MP on the way to the destination does the
following:
• decrements the TTL field in the
linktrace frame
• sends a linktrace reply message to the
originating MEP
• forwards the original linktrace
message to the destination
The linktrace message is forwarded until it


NN46220-504 02.01 Standard
4.2 3 August 2007
.
Creating a maintenance intermediate point

Create a maintenance intermediate point (MIP) to reduce the distance
between MEPs. Because MIPs passively receive CFM messages, process
the messages received, and respond back to the originating MEP, you can
use MIPs to isolate connection failures to smaller segments of the network.
MIPs are support on both PBB and PBT on the NNI.
Prerequisites
(page 24).
(page 27).
Procedure steps
Step Action
1 Create a MIP.
config cfm md <md-name> mip <mip-name> create

show cfm mip info
The following shows output for this command.
—End—
Displaying MIP statistics

Display MIP statistics to monitor your system, which includes the loopback
and linktrace messages.

NN46220-504 02.01 Standard
4.2 3 August 2007
.
Prerequisites
• Create a MIP. For information, see "Creating a maintenance intermediate
point" (page 39).
Procedure steps
Step Action
1 Display MIP statistics.

show cfm mip stats
mip stats command. For a description of the column names, see
the variable definitions table following this procedure.
3 Clear statistics shown in the Maintenance Intermediate Point Stats

clear cfm mip stats [ma-domain] [mip-name]
This command clears the statistical values for any or all of the
following: maintenance domain, maintenance association, and
remote maintenance endpoint.
—End—
Variable Value
Domain Name Shows the name of the maintenance domain
Domain Index Shows the index number of the domain.
Mip Id Shows the MIP ID number.
Loopback Received Shows the total number of CFM loopback
messages received.

NN46220-504 02.01 Standard
4.2 3 August 2007
.
Variable Value
Loopback Replied Shows the total number of CFM loopback reply
messages sent.
Linktrace Received Shows the total number of CFM linktrace
messages received.
Linktrace Replied Shows the total number of CFM linktrace reply
messages sent.
Creating a transparent domain identifier

Create a transparent domain identifier (TDI) to enable PBT and select
a multiplexer (MUX) mode. TDIs support PBT on legacy modules. To
configure PBT on R-modules, see "Creating service instance IDs" (page 46).
A transparent domain (TD) is the same as a VLAN within a customer

network or a VPN within a service provider’s network. A TDI is simply the
ID for one TD, which is equivalent to a VPN ID.
The TD transports customer traffic between endpoints within the TD.

Because TDIs allow service providers to create separate logical networks for
each customer, this mechanism ensures the separation of customer traffic.
This section describes the commands for using TDIs with PBT. For more
information about TDIs, see Configuration—UNI and Endpoints for non-PBT
VPNs (NN46220-506).
This command includes the following parameters.
Procedure steps
Step Action
1 Create a TDI with the following command and a value from 1 to

16777215 that identifies the TDI.
config tdi <tdi-id> create
2 Set the mux mode.

config tdi <tdi-id> mux-mode oneToone
3 Enable PBT.
config tdi <tdi-id> pbt enable
4 Enable this TDI.

config tdi <tdi-id> state enable

NN46220-504 02.01 Standard
4.2 3 August 2007
.
show tdi info

The following figure shows output for the show tdi info
command.
—End—
Variable Value
create Creates a TDI.
mux-mode <oneToone|manyT Sets the MUX mode so that you can map
oone> one or many qtags to the endpoints for this
TDI. PBT uses one-to-one mode.
• oneToone sets the MUX mode value
to one-to-one mode.
• manyToone sets the MUX mode value
to many-to-one mode.
name <string> Sets a unique name for this transparent
domain.
name is an alphanumeric string in the

range of 1 to 25 characters.

NN46220-504 02.01 Standard
4.2 3 August 2007
.
Variable Value
pbt <enable|disable> Enables or disables PBT on this domain.
The default is disable.
state <disable|enable|For Sets the administrative state of the TDI.
ceDisable>
• enable sets the TDI state to enable.
• disable sets the TDI state to disable.
• ForceDisable disables the TDI
even if the TDI endpoints are in the
active state. When you invoke this
command, the endpoints are placed
into the "operational down" state,
and the administrative state remains
unchanged.
Configuring the TDI endpoint

Configure a TDI endpoint to identify the path for a specific customer’s
traffic within the assigned TD. Use this command to identify the connection
type, which for PBT must be point-to-point. You also use this command to
establish an association with the maintenance domain. TDI endpoints also
define QoS rules and apply policers to the customer traffic.
This section describes the commands for using TDI endpoints with PBT.
For more information about TDI endpoints, see Configuration—UNI and
Endpoints for non-PBT VPNs (NN46220-506).
Prerequisites
• Create a TDI. For information, see "Creating a transparent domain
identifier" (page 41).
Procedure steps
Step Action
1 Configure a TDI endpoint with the following command and a value

for the port or NPU ID for this endpoint ID in IP notation.
config tdi <tdi-id> end-point <endpt-id> create
2 Set the connection type.

config tdi <tdi-id> end-point <endpt-id> connection p2p
3 Specify the remote TDI endpoint.

NN46220-504 02.01 Standard
4.2 3 August 2007
.
config tdi <tdi-id> end-point <endpt-id> remote-uni

<ipaddr>
4 Add Q tags.
config tdi <tdi-id> end-point <endpt-id> add-qtags
<qtags>
5 Associate this endpoint with a trunk group.

config tdi <tdi-id> end-point <endpt-id> trunk-group
<string>
6 Enable this TDI endpoint.

config tdi <tdi-id> end-point <endpt-id> state enable
—End—
Variable Value
add-qtags <qtags> Sets the Qtags to the TLS-switched endpoints.
qtags is an integer value between 1 and 4096 that

represents the customer 802.1 qtag ID.
Qtag 4096 is a special tag ID for classifying

untagged packets.
connection Specifies the endpoint connection type.
<any2any|hub|spoke
If you select the spoke connection-type, you must
|p2p>
specify the remote UNI address of the hub.
If you select the p2p connection-type, you can
optionally specify the MAC address of the endpoint.
The default is any2any.
create Creates a TDI endpoint.
name <string> Sets a unique name for the specified endpoint.
name is an alphanumeric string from 1 to 30
characters.
The format is EP-<tdi>.<endpt>.
For example, if TDI = 1 and the port or NPU =
0.0.0.1, then EP-1.0.0.0.1 is the endpoint name.

NN46220-504 02.01 Standard
4.2 3 August 2007
.
Variable Value
remote-uni Sets the remote-destination UNI ID for
<ipaddr> [mac point-to-point and spoke endpoints.
<value>]
ipaddr is the destination UNI ID (in IP notation).
Optional:
mac value is the MAC address of the destination
UNI ID.
state <enable|disa Administratively enables or disables the port or
ble> NPU. The default is disable.
trunk-group Identifies the trunk group associated with this
<string> endpoint.
Example of configuring a TDI endpoint

The following example shows how to configure a TDI endpoint.
Step Action
1 Create the local TDI endpoint using the port or NPU’s ID.
config tdi 100 end-point 2.2.2.2 create
2 Set the connection type to point-to-point.

config tdi 100 end-point 2.2.2.2 connection p2p
3 Specify the remote TDI endpoint using the port or NPU’s ID.
config tdi 100 end-point 2.2.2.2 remote-uni 1.1.1.1
4 Add Q tags to classify this customer’s traffic.

config tdi 100 end-point 2.2.2.2 add-qtags 100

config tdi 100 end-point 2.2.2.2 trunk-group tg1
6 Enable this TDI endpoint.

config tdi 100 end-point 2.2.2.2 state enable

show tdi end-point
The following command shows output for the show tdi
end-point command.

NN46220-504 02.01 Standard
4.2 3 August 2007
.
—End—
Creating service instance IDs

Configure a service instance IDs (I-SID) to enable PBT on R-modules.
I-SIDs support PBT on R-modules. To configure PBT on legacy modules,
see "Creating a transparent domain identifier" (page 41)
This feature enables you to configure a Provider Backbone Bridge (PBB)

or a PBT network that complies with IEEE 802.1 (ah) and supports
MAC-in-MAC. This section describes the commands for using I-SIDs with
PBT. For more information such as configuring client MEPs and displaying
I-SID and I-SID endpoint statistics, see Configuration—UNI and Endpoints
for non-PBT VPN (NN46220-506).
Procedure steps
Step Action
1 Create an I-SID with the following command and a value from 1 to

16777215 that identifies the I-SID.
config i-sid <isid-id> create
2 Enable PBT.
config i-sid <isid-id> pbt enable
3 Enable this I-SID.

config i-sid <isid-id> state enable

show i-sid info
The following shows output for the show i-sid info command.

NN46220-504 02.01 Standard
4.2 3 August 2007
.
—End—
Variable Value
create Creates an I-SID.
name <string> Assigns a name to this I-SID.
pbt <enable|disable> Enables or disables PBT on this domain.
state <disable|enable|For Sets the administrative state of the I-SID.
ceDisable>
• enable sets the I-SID state to enable.
• disable sets the I-SID state to
disable.
• ForceDisable disables the I-SID
even if the I-SID endpoints are in the
active state. When you invoke this
command, the endpoints are placed
into the "operational down" state,
and the administrative state remains
unchanged.
Configuring an I-SID endpoint

Configure an I-SID endpoint to support MAC-in-MAC on R-modules
(802.1ah). This feature enables you to configure a Provider Backbone
Bridge (PBB) network or a PBT network that complies with IEEE 802.1ah
and supports MAC-in-MAC.

NN46220-504 02.01 Standard
4.2 3 August 2007
.
This section describes the commands for using I-SID endpoints with PBT.
For more information such as configuring client MEPs and displaying I-SID
and I-SID endpoint statistics, see Configuration—UNI and Endpoints for
non-PBT VPN (NN46220-506).
Prequisites
• Create an I-SID. For information, see "Creating service instance IDs"
(page 46).
Procedure steps
Step Action
1 Configure an I-SID endpoint with the following command and a value

for the port, MLT, ring, or as standalone. The following command
requires a value for port.
config i-sid <isid-id> end-point port <slot/port>
create
2 Set the connection type.

connection p2p
3 Add a customer VLAN.

add-c-vlan <c-vlan-id>

5 Enable this I-SID endpoint.

config i-sid <isid-id> end-point port <slot/port> state
enable
—End—
Variable Value
create Creates an I-SID endpoint.
add-c-vlan Identifies the Customer VLAN to add to this
<c-vlan-ids> endpoint.

NN46220-504 02.01 Standard
4.2 3 August 2007
.
Variable Value
s-vlan <s-vlan-id> Identifies the Service VLAN to add to this endpoint.
state <enable|disab Enables or disables the endpoint. The default is
le> disable.
name <string> Names the endpoint, which by default is EP-<sid>
PORT <PortNum>. For example, if SID=1 and it
uses port 1/2, the endpoint name is EP-1 PORT
1/2.
connection Specifies the endpoint connection type.
<any2any|p2p>
If you select the p2p connection-type, you can
optionally specify the MAC address of the endpoint.
The default is any2any.

mux-mode <oneToone| Specifies the mux mode. The oneToone mode
manyToone> enables you to map several qtags to one endpoint;
the manyToone mode does not remap qtags at the
local egress.
trunk-group Identifies the trunk group associated with this
<string> endpoint.
cfm-vid <cfm-vid-i Specifies the client MEPs that you want to assign
d> add-client-mep to this endpoint. A client MEP consists of the
<mdName.maName.mep Maintenance Domain, Maintenance Association,
_id> and the MEP ID and uses the following format:
<md>.<ma>.<mep_id>. Separate the MEP
components with a ’.’ and separate the MEPs in
the list with a ’,’. For example:
<md1>.<ma1>.<mep_id1>,<md2>.<ma2>.<mep
_id2>,...
You can have up to eight MEPs in the list.
Also, the cfm-vid, must match the c-vlan for
tls-switched. If it is tls-transparent there is no
c-vlan, therefore the cfm-vid can be configured to
any value.
cfm-vid <cfm-vid-id Specifies the client MEPs that you want to remove
> remove-client-mep from this endpoint. A client MEP consists of the
<mdName.maName.mep Maintenance Domain, Maintenance Association,
_id> and the MEP ID and uses the following format:
<md>.<ma>.<mep_id>. Separate the MEP
components with a ’.’ and separate the MEPs the
list with a ’,’ . For example: <md1>.<ma1>.<mep_i
d1>,<md2>.<ma2>.<mep_id2>,...
l2pt-mac-swap cdp Enable or disable L2pt (Layer 2 Tunneling Protocol)
<enable|disable> MAC swapping for a CDP, VTP or STP endpoint.

NN46220-504 02.01 Standard
4.2 3 August 2007
.
Variable Value
l2pt-mac-swap vtp
<enable|disable>
l2pt-mac-swap stp
<enable|disable>
Example of configuring an I-SID endpoint

The following example shows how to configure an I-SID endpoint.
Step Action
1 Create the local I-SID endpoint using the port ID.

config i-sid 100 end-point port 2/11 create
2 Set the connection type to point-to-point.

config i-sid 100 end-point port 2/11 connection p2p mac
00.00.00.00.00.00
3 Add a customer VLAN.

config i-sid 100 end-point port 2/11 add-c-vlan 900

config i-sid 100 end-point port 2/11 trunk-group tg1
5 Enable this I-SID endpoint.

config i-sid 100 end-point port 2/11 state enable

show i-sid end-point port 2/11
The following shows output for the show i-sid end-point port
command.
—End—

NN46220-504 02.01 Standard
4.2 3 August 2007
.
Example of configuring a client-level MEP using the CLI

This example adds a client-level MEP called C-VID.test.1 to a Customer
VLAN called c-vid 10.
System:5# config cfm md C-VID ma test mep 1 create

System:5# config i-sid 1 end-point port 7/1 c-vid 10
add-client-mep C-VID.test.1
To verify your configuration, enter the following command:
System:5# show cfm mep info
Configuring a PBT VLAN

Create a PBT VLAN to separate it from non-PBT VLANs. PBT VLANs
behave differently and have the following requirements:
• PBT VLANs do not support broadcast and drops frames that do not
have a forwarding record.
• PBT VLANs require a dedicated Spanning Tree Group (STG).
• PBT VLANs do not support Spanning Tree Protocol (STP).
• A PBT VLAN cannot be the default VLAN for a port.
There are three parts to creating a PBT VLAN:

• Use the config pbt-vlans command to reserve VLANs for PBT. You
can configure this command before you create the VLANs.
• Use the config stg command to create an STG, add ports to it, and
disable STP. For more information about this command, see Configuring
VLANs, Spanning Tree, and Link Aggregation (314725-E).
• Use the config vlan command to create VLANs and enable
unknown MAC discard. For more information about this command, see
Configuring VLANs, Spanning Tree, and Link Aggregation (314725-E).

NN46220-504 02.01 Standard
4.2 3 August 2007
.
Procedure steps
Step Action
1 Create a PBT VLAN by adding VLANs.

config pbt-vlans add <vid>
2 Create a PBT spanning tree group.

config stg <stg-id> create
3 Add ports to the this STG.

config stg <stg-id> add ports <ports>
4 Disable STP on this STG.

config stg <stg-id> group-stp disable
5 Create a port-based VLAN.

config vlan <vid> create byport <stg-id>
6 Discard unkown MAC destinations.

config vlan <vid> unknown-destmac-discard activation
enable
—End—
Variable Value
config pbt-vlans
add <vid> Adds a VLAN to this PBT domain.
config stg <stg-id>

add ports <ports> Adds ports to a spanning tree group.
create [type <value> ] Creates a new spanning tree group.
type <value> is the type of STG. The

choices are stgnormal, stgsvlan, and
stgpbt. For PBT, select stgpbt.
group-stp <enable|disabl Enables or disables the Spanning Tree
e> Protocol (STP) on the specified spanning
tree group.

NN46220-504 02.01 Standard
4.2 3 August 2007
.
Variable Value
config vlan <vid>
create byport <stg-id> Creates a port-based VLAN.
[name <value> ] [color
<value> ]
• stg-id is the spanning tree group ID (1
to 64).
• name <value> is the name of the
VLAN (0 to 20 characters).
• color <value> is the color of the VLAN
(0 to 32) that Optivity uses to display
the VLAN.
ports add <ports> [member Adds ports to an existing VLAN.
<value> ]
<ports> is the list of ports.
member <value> is one of the following

port member types:
• portmember, which is always a

member
• static, which is sometimes a member
• notallowed, which is never a member
ports remove <ports> Removes ports from a VLAN, but it does
[member <value> ] not delete the VLAN.

port member types:

member
unknown-destmac-discard Enable activation to drop packets with
activation <enable|disab unknown destination MAC addresses.
le>

NN46220-504 02.01 Standard
4.2 3 August 2007
.
Example of configuring a PBT VLAN

The following example shows how to configure a PBT VLAN.
Step Action
1 Add PBT VLANs to reserve them for PBT.

config pbt-vlans add 90-93
2 Create a PBT STG.

config stg 64 create type stgpbt
3 Add ports to this STG.

config stg 64 add ports 2/4, 4/1-4/2
4 Create a port-based VLAN.

config vlan 90 create byport 64
5 Discard unknown MAC destinations.

config vlan 90 unknown-destmac-discard activation
enable

show pbt-vlans info
The following shows output for the show pbt-vlans info
command.
—End—
Configuring port VLANs for MEPs and MIPs

Configure a connectivity fault management (CFM) VLAN to associate MEPs
and MIPs to a specific port so that you can monitor them.
ATTENTION
The default VLAN for cfm-vid is set to 1, which means it is not set to any VLAN.
This means that no CFM messages are accepted or forwarded. To specify a VLAN
to use as the sending VLAN for port CFM packets, use the following command:
config ethernet <slot/port> cfm-vid value 0..4094

NN46220-504 02.01 Standard
4.2 3 August 2007
.
Configuring port VLANs for MEPs and MIPs 55
Procedure steps
Step Action
1 Configure a CFM VLAN.

config vlan <vid> cfm-port <slot/port>
2 Add MEPs.
config vlan <vid> cfm-port <slot/port> add-mep
<mdName.maName.mepId>
3 Add MIPs.
config vlan <vid> cfm-port <slot/port> add-mip
<mdName.maName.mipId>

show vlan info cfm-port
The following shows output for the show vlan info cfm-port
command.
—End—
Variable Value
info Displays the current configuration
information for this command.

NN46220-504 02.01 Standard
4.2 3 August 2007
.
Variable Value
add-mep <mdName.maName.m Specifies the list of MEPs that you
epId> want to add to this VLAN. A MEP list
consists of the Maintenance Domain,
Maintenance Association, and the
MEP ID and uses the following format:
<mdName>.<maName>.<mep_id>.
Separate the MEP components with a ’.’
and separate the MEPs in the list with a ’,’
so a list looks like the following:
<md1>.<ma1>.<mep_id1>,<md2>.<ma2
>.<mep_id2>,...
You can have up to eight MEPs in the list.
add-mip <mdName.maName.m Specifies the list of MIPs that you
ipId> want to add to this VLAN. A MIP list
consists of the Maintenance Domain,
Maintenance Association, and the
MIP ID and uses the following format:
<mdName>.<maName>.<mip_id>.
Separate the MEP components with a ’.’
and separate the MIPs in the list with a ’,’
so a list looks like the following:
<md1>.<ma1>.<mep_id1>,<md2>.<ma2
>.<mep_id2>,...
You can have up to eight MIPs in the list.
Creating the local end

Create the local end to specify the network-to-network (NNI) port to use.
The trunk connects two NNI ports across the metro network to transport
traffic. Trunks also carry CFM frames to check the status of the path and
detect connectivity failures.
A PBT trunk consists of two unidirectional trunks going in opposite

directions. Each unidirectional trunk originates at one MERS NNI port and
terminates on an NNI port of a different MERS. These trunks are grouped
together and share the same pair of endpoints.
When you configure a trunk, PBT does not automatically add or remove
the MAC address for the trunk VLAN to the forwarding database. This
eliminates the possibility of the MAC address getting inadvertently removed

NN46220-504 02.01 Standard
4.2 3 August 2007
.
ATTENTION
You have to manually add and remove MAC addresses for the trunk VLAN.
Procedure steps
Step Action
1 Create the local end with the following command and a string of 1 to
32 characters that uniquely identifies the PBT trunk.
config pbt-trunk <trunk-name> create
2 Specify the NNI port you want to use.

config pbt-trunk <trunk-name> port <slot/port>
3 Specify the MAC address of the remote NNI port.

config pbt-trunk <trunk-name> remote-peer-mac
<mac-address>
4 Specify the VLAN to use with the local end of this PBT trunk.
config pbt-trunk <trunk-name> vlan <vid>
5 Specify the VLAN used by the remote end of this PBT trunk.
config pbt-trunk <trunk-name> reverse-vlan <vid>
6 Associate this PBT trunk to a MEP.

config pbt-trunk <trunk-name> add-mep md-1.ma-1.10
7 Customize the PBT trunk by changing the hold time interval

default or adding labels. For information, see the following variable
definitions table.
8 Enable this PBT trunk.
config pbt-trunk <trunk-name> state enable
—End—
Variable Value
add-mep <mdName.maName.m Adds a maintenance endpoint (MEP) to
epId> this PBT trunk. The range of valid MEP
IDs is from 1 to 8191.

NN46220-504 02.01 Standard
4.2 3 August 2007
.
Variable Value
add-user-label1 <string> Add a label to provide more management
information or data that would be included
in all traps related to this object. Check
with your network administrator to make
the label meaningful to the trap receiver.
create Creates a PBT trunk.
hold-time <interval-timer This is an optional parameter that sets the
> trunk hold timer value interval (in seconds).
The timer is used to wait after CCM has
come up before we declare the trunk up,
so as to avoid flapping. The range is from
1 to 120, and the default is 30.
name <value> Enter the name of the trunk for which you
want to display PBT trunk information.
port <port> Specifies the port to use for this PBT trunk.
port refers to the port name in the
slot/port format.
remote-peer-mac <value> Specifies the MAC address of the remote
peer.
value refers to the MAC address in the
0x00:0x00:0x00:0x00:0x00:0x00 format.
This command requires the remote MAC
address of the MERS 8600 on the other
end of this trunk. To get this address, enter
show sys info on the remote MERS
and note the address after PbtMacAddr
under Chassis Info.
reverse-vlan <vid> Specifies a VLAN to use with this PBT
trunk. The default is the configured VLAN
for the PBT trunk. The range is 0..4094.
Only 0,2,3..4094 is legal.
source-mac <value> Specifies the MAC address of the remote
trunk MEP. This is called the source MAC
because it is the source of the continuity
check messages that detect failures. This
field is optional.

NN46220-504 02.01 Standard
4.2 3 August 2007
.
Variable Value
subport-queue-set <index> Assign an index value to this subport
queue set. The range is 1..80, and the
default is 1.
state <enable|disable> Administratively enables or disables the
PBT trunk. The default is disable.
vlan <vid> Specifies the VLAN to use with this
unidirectional trunk. This trunk and the
opposing reverse-vlan unidirectional trunk
comprise one bidirectional PBT trunk. The
range is 0..4094. Only 0,2,3..4094 is legal.
Example of configuring a PBT trunk

The following example shows how to configure a PBT trunk.
Step Action
1 Create a PBT trunk called tr1901.

config pbt-trunk tr1901 create
2 Specify the NNI port to use.

config pbt-trunk tr1901 port 4/1
3 Specify the MAC address of the remote NNI port.

config pbt-trunk tr1901 remote-peer-mac 00:80:2d:2f:64
:1a
4 Specify the VLAN to use with the local end of this PBT trunk.
config pbt-trunk tr1901 vlan 90
5 Specify the VLAN used by the remote end of this PBT trunk.
config pbt-trunk tr1901 reverse-vlan 91
6 Associate this PBT trunk to MEP 10.

config pbt-trunk tr1901 add-mep md-1.ma-1.10
7 Set the hold time to 10 seconds.

config pbt-trunk tr1901 hold-time 10
8 Enable this PBT trunk.

config pbt-trunk tr1901 state enable
9 Verify your configuration to show information for all trunks, a specific

trunk, a specific port, or the only Screen II with the summary
information.

NN46220-504 02.01 Standard
4.2 3 August 2007
.
show pbt-trunk info [name <value>] [port <port>]

[summary]
The following shows output for the show pbt-trunk info
command.
For information about setting the CCM timer, see:

For information about RDI, see "Displaying RMEP statistics" (page

33).
—End—
Displaying PBT trunk statistics

Display PBT trunk statistics to monitor your system.
Prerequisites
• Create a PBT trunk. For information, see "Creating the local end "
(page 56).
Procedure steps
Step Action
1 Display PBT trunk statistics.

show pbt-trunk stats [<trunk-name>]

NN46220-504 02.01 Standard
4.2 3 August 2007
.
2 Refer to the following figure for sample output for the show
pbt-trunk stats command.
3 Clear statistics shown in the Maintenance Intermediate Point Stats

clear pbt-trunk stats [<trunk-name>]
This command clears the statistical values for all PBT trunks or just
the specified PBT trunk.
—End—
Configuring a trunk group

Configure a trunk group (TG) to associate it with a pair of trunks (Primary
and Secondary). Having two trunks provides failover protection. When CFM
detects a trunk failure, the TG transfers traffic to the Secondary or backup
trunk. Note that Secondary trunks are not required. However, if there is no
Secondary; there is no failover protection.
Traffic flows through the Primary or the Secondary trunk, never both.
Whichever one is in use is called the Active trunk.
In revertive mode, the primary trunk is the active trunk. If a failure occurs on
the primary trunk, the secondary trunk becomes active. Once the primary
trunk recovers from the failure, the primary trunk becomes the active trunk,
after the hold timer interval expires. The hold timer value is configured when
you create the local end.

NN46220-504 02.01 Standard
4.2 3 August 2007
.
In non-revertive mode, when the active trunk fails, the other trunk becomes
the active trunk. Traffic does not revert to the trunk that failed, when it
recovers from the failure.
If no endpoints are using the trunk group, the trunk group displays revertive
behavior, even when the revertive mode is disabled.
Prerequisites
• Create two PBT trunks. For information, see "Creating the local end "
(page 56).
Procedure steps
Step Action
1 Configure a PBT trunk group with the following command and a

string of 1 to 32 characters that uniquely identifies the PBT trunk
group.
config trunk-group <trunk-group-name> create
2 Specify a primary PBT trunk.

config trunk-group <trunk-group-name> primary-trunk
<trunk-name>
3 Specify a secondary PBT trunk.

config trunk-group <trunk-group-name> secondary-trunk
<trunk-name>
4 Enable the revertive feature.

config trunk-group <trunk-group-name> revertive enable
5 Customize the trunk group by adding labels or specifying an active

trunk. For information, see the following variable definitions table.
—End—
Variable Value
active-trunk <trunk-name> Specifies this trunk as the active trunk.
Use this to cause a manual switch for a
non-revertive trunk group.

NN46220-504 02.01 Standard
4.2 3 August 2007
.
Variable Value
create Creates a PBT trunk group.
loopback-vlan <vid> Configure a loop back VLAN for PBT
local switching. This VLAN must be a
PBT VLAN. For more information, see
"Configuring PBT local switching" (page
65).
primary-trunk <trunk-name Specifies this trunk as the primary trunk.
>
revertive Enables or disables making the primary
trunk revert to its former status as the
<enable|disable>
active trunk.
When the primary trunk fails, the
secondary trunk becomes the active trunk.
• When revertive is enabled and the
primary trunk recovers from a failure,
the primary trunk becomes the active
trunk, after the hold timer interval
expires.
• When revertive is disabled, the
secondary trunk remains the active
trunk, after the primary trunk recovers
from failure.

secondary-trunk Specifies this trunk as the secondary
<trunk-name> trunk, which serves as a backup to the
primary trunk.
Example of configuring a trunk group

The following example shows how to configure a trunk group.
Step Action
1 Create a trunk group called Path1.

NN46220-504 02.01 Standard
4.2 3 August 2007
.
config trunk-group Path1 create
2 Specify which PBT trunk to use as the Primary.

config trunk-group Path1 primary-trunk tr1901
3 Specify which PBT trunk to use as the Secondary.

config trunk-group Path1 secondary-trunk tr1902

config trunk-group Path1 revertive enable

show trunk-group info
The following shows output for the show trunk-group info
command.
—End—
The show trunk-group info command has the following parameters:

• show trunk-group info - Displays information (not including
endpoints) for all trunk-groups.
• show trunk-group info <tg-id> - Displays information (not
including endpoints) for the specified trunk-group.
• show trunk-group info details - Displays information (including
endpoints) for all trunk-groups.
• show trunk-group info <tg-id> details - Displays
information (including endpoints) for the specified trunk-group.

NN46220-504 02.01 Standard
4.2 3 August 2007
.
Configuring PBT local switching

Configure PBT local switching to define a trunk group as a loopback VLAN.
The trunk group loopback VLAN transports data between two locally
switched UNIs. It is a dedicated VLAN used for PBT local switching and
nothing else. The trunk group loopback VLAN must be a PBT VLAN, and
there can only be one loopback VLAN per switch.
Prerequisites
• Configure a PBT VLAN. For information, see "Configuring a PBT VLAN"
(page 51).
• Configure a trunk group. For information, see "Configuring a trunk
group" (page 61).
Procedure steps
Step Action
1 Configure a PBT trunk group.

config trunk-group <trunk-group-name> create
2 Specify a PBT VLAN to be the loopback VLAN for this trunk group.
config trunk-group <trunk-group-name> loopback-vlan
<vid>
—End—
Displaying NNI connections

Display NNI connections to see what maintenance endpoints you are using.
Procedure steps
Step Action
1 Display NNI connections.

show pbt-nni info
2 Refer to the following figure for sample output for the show pbt-nni
info command. For a description of the column names, see the

NN46220-504 02.01 Standard
4.2 3 August 2007
.
—End—
Variable Value
NNI Port Displays the PBT trunk port number.
SERVICE ID Displays the TDI or I-SID associated with this
NNI.
UNI PORT Displays the access port associated with this
NNI.
Displaying NNI statistics

Display NNI statistics to monitor your system.
Procedure steps
Step Action
1 Display NNI statistics.

show pbt-nni stats
2 Refer to the following figure for sample output for the show pbt-nni
stats command. For a description of the column names, see the

NN46220-504 02.01 Standard
4.2 3 August 2007
.
—End—
Variable Value
NNI PORT Shows the slot/portnumber of the NNI.
OEL2 RX Shows the total number of Optical Ethernet
Layer 2 (OEL2) encapsulated bytes processed
on this ingress NNI port.
OEL2 DROPPED Shows the total number of OEL2 encapsulated
bytes dropped by this ingress NNI port.
MIM RX Shows the total number of MAC-in-MAC or
802.1ah (MIM) encapsulated bytes processed
on this ingress NNI port.
MIM DROPPED Shows the total number of MIM encapsulated
bytes dropped by this ingress NNI port.
Tracking dropped PBT packets

Track drop packets so you can monitor how much traffic is not getting
through your network. This feature enables you to track packets that have
unknown destination MACs or exceed a queuing class threshold.
A dedicated PBT counter tracks packets with unknown destination MACs

per port. Every time the MERS 8600 drops an unknown MAC packet
ingressing the UNI port, it increments the counter and generates an SNMP
trap. To avoid sending too many traps, you can configure an interval timer.
Eight counters per port track dropped packets from each queuing class at
egress. The MERS 8600 generates a trap when the percentage of packets
being dropped exceeds a configurable threshold for each queuing class. To
avoid sending too many traps, you can configure an interval timer.
Procedure steps
Step Action
1 Configure the unknown destination MAC counter.

config pbt-drop-trap-timer <timer-value>
2 Display the PBT counter results.

show ports stats interface pbt-drop-count [port
<slot/port>]

NN46220-504 02.01 Standard
4.2 3 August 2007
.
3 Use the following command when you want to clear the drop counter
for all ports.
clear port stats
4 Configure the egress queuing class counter.

config qos drop-trap timer-interval <timer-value>
5 Specify they class and set the threshold percentage for traps sent on
packets dropped on QoS queues.
config qos drop-trap drop-threshold-percentage class
<0..7> percentage <percentage>
6 Display the QoS drop counter results.

show ports stats interface qos
7 Enable the drop traps on a particular queuing class.

config qos drop-trap recv-page-drop-trap class <0..7>
state <disable|enable>
—End—

NN46220-504 02.01 Standard
4.2 3 August 2007
.
Variable Value
pbt-drop-trap-timer <value> Configures the timer interval for the PBT
unknown destination MAC counter. The range
is from 1..1440 (in minutes). The 1440 value
equals 24 hours. The default value is 900 (15
minutes).
qos drop-trap drop-threshold-percen Specifies the QoS class, which is from 0..7 and
tage class percentage <percentage> sets the percentage for the drop threshold.
A trap is generated when the dropped packets
exceed this threshold. The range is from 0..100,
and the default is 0%.
• 0% indicates that a trap is set if any packet
is discarded, no matter how many.
• 100% indicates that a trap is set only if all
the packets are being discarded.
qos drop-trap timer-interval Configures the timer interval for the QoS drop
counter. The range is from 1..1440 (in minutes).
The 1440 value equals 24 hours. The default
value is 900 (15 minutes).
qos drop-trap recv-page-drop-trap class {0..7} Specifies the QoS class, which is from 0..7, and
state {disable|enable} enables or disables drop traps on the specified
queuing class.
Configuring PBT with MSTP

MERS 8600 supports PBT in an MSTP/RSTP network, but you cannot
configure RSTP on a MERS 8600. RSTP allows only one instance of STP,
which means all ports and all VLANs are part of the same STP instance.
This makes it impossible to support PBT with RSTP.
However, you can configure MSTP on a MERS 8600. Just like there is a
specific STP instance dedicated for PBT VLANs, an MSTP instance is also
dedicated for PBT VLANs. If you enable MSTP, then you must create all
PBT VLANs with this special MSTP instance. Furthermore, MSTP does not
operate in a compatibility mode. This means that all the switches in the
network must be MSTP enabled or none should be enabled.
Procedure steps
Step Action
1 Change the bootconfig flag from stg to mstp.

NN46220-504 02.01 Standard
4.2 3 August 2007
.
config bootconfig flags spanning-tree-mode mstp
2 Save the configuration.
3 Reboot the MERS 8600.

This action removes all STG VLANs.
4 Create new MSTP VLANs.

config vlan <vid> create byport-mstp <value>
—End—

NN46220-504 02.01 Standard
4.2 3 August 2007
.
71
Configuring PBT with Device Manager

This chapter describes how to configure Provider Backbone Transport (PBT)
on the Nortel Metro Ethernet Routing Switch 8600 with Device Manager.
For information about using the CLI, see "Configuring PBT with the CLI"
(page 15). For conceptual information, see Nortel Metro Ethernet Routing
Switch 8600 Fundamentals (NN46220-100).
Navigation
• "Creating a maintenance domain" (page 72)
• "Creating a maintenance endpoint" (page 76)
• "Displaying MEP statistics" (page 78)
• "Creating a remote maintenance endpoint" (page 79)
• "Displaying RMEP statistics" (page 81)
• "Creating a maintenance intermediate point" (page 82)
• "Displaying MIP statistics" (page 84)
• "Monitoring CFM loopback messages" (page 85)
• "Monitoring CFM linktrace messages" (page 87)
• "Creating a transparent domain identifier" (page 89)
• "Configuring a TDI endpoint" (page 91)
• "Configuring service instance IDs" (page 98)
• "Configuring an I-SID endpoint" (page 100)
• "Configuring a PBT VLAN" (page 105)
• "Configuring a CFM VLAN for MEPs" (page 109)
• "Configuring a CFM VLAN for MIPs" (page 111)
• "Creating the local end of a PBT trunk" (page 112)
• "Displaying PBT trunk statistics" (page 116)

NN46220-504 02.01 Standard
4.2 3 August 2007
.
72 Configuring PBT with Device Manager
• "Configuring a trunk group" (page 117)

• "Configuring PBT local switching" (page 119)
• "Displaying NNI connections" (page 119)
• "Displaying NNI statistics" (page 120)
• "Configuring PBT policing options" (page 121)
• "Tracking dropped PBT packets" (page 122)
• "Configuring PBT with MSTP" (page 123)
Creating a maintenance domain

Create a maintenance domain (MD) to define a part of the network
for connectivity fault management (CFM). With CFM, you can verify
connectivity, detect and isolate faults, and ensure the delivery of services.
One MD may contain several maintenance associations and maintenance
endpoints. (The following sections describe how to configure these
features.) You can configure an MD for different levels within the metro
network: Trunk Group and Service Instance.
Prerequisites
• You must set the bootconfig flag to discard unknown MAC destinations.
The default setting is false. For more information, see "Discarding
unknown MAC addresses" (page 22).
Procedure steps
Step Action
1 From the Device Manager menu, choose VPN > CFM >
Maintenance Domain.
The Maintenance Domain dialog box opens, which shows existing
domains. See the following figure.
Maintenance Domain dialog box
2 Click Insert.

NN46220-504 02.01 Standard
4.2 3 August 2007
.
The Maintenance Domain, Insert dialog box opens (see the following
figure).
Maintenance Domain, Insert dialog box
3 Enter a name for this MD.

4 Assign a level to this MD.
5 Click Insert.
—End—
For more information, see "Variable definitions" (page 73).
Variable Value
Index Assigns a unique index number to this
maintenance domain. Device Manager assigns
this automatically, which you can overwrite.
Name Assigns a name to this maintenance domain.
Level Separates MDs from each other so you can
provide different functions to different areas in
the network. The 802.1ag draft recommends the
following assignments:
• level 5–7 to customer equipment
• level 3–4 to service provider equipment
• level 0–2 to operator equipment
Creating a maintenance association

Create a maintenance association (MA) to link a service instance (trunk,
VLAN, or VPN) to an MD. You also use this feature to set the continuity
check message (CCM) interval.

NN46220-504 02.01 Standard
4.2 3 August 2007
.
Prerequisites
(page 72).
Procedure steps
Step Action
Maintenance Domain.
The Maintenance Domain dialog box opens.
2 Select an MD.
This activates its Maintenance Association button.
3 Click Maintenance Association.

The Maintenance Association dialog box opens (see the following
figure).
Maintenance Association dialog box
4 Click Insert.
The Maintenance Association, Insert dialog box opens (see the
following figure).

NN46220-504 02.01 Standard
4.2 3 August 2007
.
Maintenance Association, Insert dialog box
5 Enter a name for this MA.
6 Customize your MA by changing the default settings. For information,

see the following variable definitions table.
7 Click Insert.
—End—
Variable Value
AssociationIndex Assigns a unique index number to this
maintenance association. Device Manager
assigns this automatically, which you can
overwrite.
AssociationName Assigns a name to this maintenance
association.

NN46220-504 02.01 Standard
4.2 3 August 2007
.
Variable Value
CcmInterval Sets the time interval (in milliseconds) for how
often continuity check messages (CCM) are
sent between endpoints within a domain. The
default is 10000.
AutoDetect Enables or disables the MA from automatically
detecting remote MEPs. The default is disable.
When you configure a trunk, PBT no longer
automatically adds or removes the MAC
address for the trunk VLAN to the forwarding
database entry. This eliminates the possibility
of the MAC address getting inadvertently
removed when the last trunk to this VLAN is
removed.
Creating a maintenance endpoint

Create a maintenance endpoint (MEP) to link an endpoint to an MA. MEPs
originate CFM messages and respond to CFM messages sent by other
MEPs. You also use this feature to set the CFM message values.
Prerequisites
(page 72).
Procedure steps
Step Action
Maintenance Domain.
2 Select an MD to activate its Maintenance Association button.

3 Click the Maintenance Association button.
4 Select an MA to activate its Maintenance Endpoint button.
5 Click the Maintenance Endpoint button.

The Maintenance Endpoint dialog box opens (see the following
figure).

NN46220-504 02.01 Standard
4.2 3 August 2007
.
Maintenance Endpoint dialog box
6 Click Insert.
The Maintenance Endpoint, Insert dialog box opens (see the
following figure).
Maintenance Endpoint, Insert dialog box
7 Enable the MEP.
8 Customize your MEP by changing the default settings. For

information, see "Variable definitions" (page 77).
—End—
Variable Value
Id Assigns a unique ID number to this
maintenance endpoint. Device Manager
overwrite.
AdminState Administratively enables or disables the
maintenance association. The default is
disable.
CcmPriority Sets the priority level for transmitting continuity
check messages. The range is from 0 to 7,
and the default is 7.
CcmTxEnable Enables or disables sending continuity check
messages from this MA. The default is disable.

NN46220-504 02.01 Standard
4.2 3 August 2007
.
Displaying MEP statistics

Display MEP statistics to monitor your system.
To reset the statistics counters, use the VPN > CFM > Port Stats > Clear
Stats button. Clicking this button causes the columns to reset to zero and
automatically begin to recalculate statistical data. The Clear Stats button
does not affect the AbsoluteValue column. To reset absolute values, use the
resetCounters function (Edit > Chassis > System).
Prerequisites
(page 72).
• Create an MEP. For information, see "Creating a maintenance endpoint"
(page 76).
Procedure steps
Step Action
Maintenance Domain.

4 Select an MA to activate its Maintenance Endpoint button.

5 Click the Maintenance Endpoint button.
6 Select a MEP.
7 Click the Statistics tab.

The Maintenance Endpoint statistics dialog box opens (see the
following figure).
Maintenance Endpoint statistics

NN46220-504 02.01 Standard
4.2 3 August 2007
.
—End—
For a description of the column names, see "Variable definitions" (page 79).
Variable Value
Absolute Value Shows the absolute value of the received,
transmitted, and dropped octets.
Cumulative Shows the total number of received,
transmitted, and dropped octets.
Average/Sec Shows the average number of received,
transmitted, and dropped octets per second.
Minimum/Sec Shows the minimum number of received,
Maximum/Sec Shows the maximum number of received,
LastVal/Sec Shows the last value received per second.
TxCnt Shows the total number of CFM messages
transmitted from the remote MEP.
RxCnt Shows the total number of CFM messages
received by the local MEP.
RxZeroCnt Shows the total number of CFM messages
received by the local MEP.
MissedCnt Shows the total number of CFM messages
missing on the remote MEP.
UpTimeCnt Shows the total time that CFM messages are
up on the MEP (in milliseconds).
Creating a remote maintenance endpoint

Create a remote maintenance endpoint to link the MAC address of the
remote endpoint to an MA.
Prerequisites
(page 72).
(page 76).

NN46220-504 02.01 Standard
4.2 3 August 2007
.
Procedure steps
Step Action
Maintenance Domain.

4 Select an MA to activate its Remote Maintenance Endpoint button.
5 Click the Remote Maintenance Endpoint.

The Remote Maintenance Endpoint dialog box opens (see the
following figure).
Remote Maintenance EndPoint dialog box
ATTENTION
If you see all zeros for the MAC addresses, disable the AutoDetect
feature. For more information, see "Creating a maintenance association"
(page 73).
6 Click Insert.
The Remote Maintenance Endpoint, Insert dialog box opens (see
the following figure).
The Remote Maintenance Endpoint, Insert dialog box opens.
Remote Maintenance EndPoint, Insert dialog box
Enter the MAC address of the remote MEP.
7 Click Insert.
—End—

NN46220-504 02.01 Standard
4.2 3 August 2007
.
Variable Value
Id Assigns a unique ID number to this remote
maintenance endpoint. Device Manager
overwrite.
MacAddr Specifies the MAC address of the remote MEP
MAC.
Displaying RMEP statistics

Display RMEP statistics to monitor your system.
Prerequisites
(page 72).
(page 76).
Procedure steps
Step Action
Maintenance Domain.
4 Select an MA to activate its RemoteMaintenanceEndPoint button.
5 Click the RemoteMaintenanceEndPoint button.

6 Select a remote MEP.

NN46220-504 02.01 Standard
4.2 3 August 2007
.
The Remote Maintenance Endpoint statistics dialog box opens (see

Remote MEP Statistics dialog box
—End—
Variable Value
LearnType Shows how the remote MEP was learned.
• Static indicates the RMEP was manually created.
• Dynamic indicates the RMEP was automatically
detected.
When you configure a trunk, PBT no longer automatically

adds or removes the MAC address for the trunk VLAN
to the forwarding database entry. This eliminates the
possibility of the MAC address getting inadvertently
removed when the last trunk to this VLAN is removed.
RemoteMacAddr Shows the MAC address of the remote MEP.
RxCnt Shows the total number of CFM messages received by
the local MEP.
SeqErrCnt Shows the total number of CFM messages received by
the local MEP that are out of sequence.
OperState Shows the current state of the remote RMEP.
Creating a maintenance intermediate point

Create a maintenance intermediate point (MIP) to reduce the distance
between MEPs. Because MIPs passively receive CFM messages, process
the messages received, and respond back to the originating MEP, you can
use MIPs to isolate connection failures to smaller segments of the network.

NN46220-504 02.01 Standard
4.2 3 August 2007
.
MIPs are always associated with MEPs. Therefore, you cannot have a MIP
on a port that does not already have a MEP. Configuring a MEP with a
MIP is optional.
Prerequisites
• Create a MD. For information, see "Creating a maintenance domain"
(page 72).
• Create a MA. For information, see "Creating a maintenance association"
(page 73).
(page 76).
Procedure steps
Step Action
Maintenance Domain.
2 Select an MD to activate its Maintenance Intermediate Point button.
3 Click the Maintenance Intermediate Point button.

The Maintenance Intermediate Point dialog box opens (see the
following figure).
4 Click Insert.
The Maintenance Intermediate Point, Insert dialog box opens (see
5 Assign a unique index number to this maintenance intermediate

point.
6 Click Insert.

NN46220-504 02.01 Standard
4.2 3 August 2007
.
—End—
Displaying MIP statistics

Display MIP statistics to monitor your system, which includes loopback and
linktrace messages.
Prerequisites
• Create a MIP. For information, see "Creating a maintenance intermediate
point" (page 82).
Procedure steps
Step Action
Maintenance Domain.
2 Select an MD to activate its Maintenance Intermediate Point button.
3 Click the Maintenance Intermediate Point button.
4 Select a MIP.

The Maintenance Intermediate Point statistics dialog box opens (see
MIP Statistics dialog box
—End—

NN46220-504 02.01 Standard
4.2 3 August 2007
.
Monitoring CFM loopback messages 85
Variable Value
LoopbackReceived Shows the total number of CFM loopback messages
received.
LoopbackReplied Shows the total number of CFM loopback reply messages
sent.
LinktraceReceived Shows the total number of CFM linktrace messages
received.
LinktraceReplied Shows the total number of CFM linktrace reply messages
sent.
Monitoring CFM loopback messages

Monitor connectivity fault management (CFM) loopback messages to test
the connection between Maintenance Points (MP). You can also use this
feature to diagnose faults in the network as well as to measure performance.
Loopback messages are unicast messages that you can address to either a
MEP or MIP, but only a MEP can initiate a loopback message. The receiving
Maintenance Point (MP) responds with a loopback reply. This mechanism
provides fault verification for the MD.
Prerequisites
(page 72).
(page 76).
Procedure Steps
Step Action
Maintenance Domain.

NN46220-504 02.01 Standard
4.2 3 August 2007
.

The Maintenance Association dialog box opens.
4 Select an MA to activate its Maintenance EndPoint button.
5 Click the Maintenance EndPoint button.

6 Select a Maintenance EndPoint to activate its LoopBack button.
7 Click the LoopBack button.

The LoopBack dialog box opens (see the following figure).
LoopBack dialog box
—End—
Variable Value
DestMacAddress Specifies the MAC address of the destination
MEP.
DestMepId Specifies the ID of the destination MEP.
DestIsMepId Indicates whether the destination is the MEP
ID: true or false.
Messages Specifies the burst count number, which
determines how many LBM messages to send
to the remote MEP. The default burst count is 1,
and the maximum count is 10000.

NN46220-504 02.01 Standard
4.2 3 August 2007
.
Monitoring CFM linktrace messages 87
Variable Value
Priority Sets the priority level for transmitting continuity
check messages. The range is from 0 to 7, and
the default is 7.
Status Shows the status of the loopback command:
• ready indicates that the MEPs are ready for
you to initiate a loopback message.
• not ready indicates that the MEPs are not
configured so you cannot initiate a loopback
messaged.
• transmit initiates a loopback message.
Monitoring CFM linktrace messages

Fault isolation is achieved through the use of Linktrace Messages (LTM).
LTM is intercepted by all the MPs on the way to the destination MP (LTM
can be addressed to either MEP or MIP).
Monitor CFM linktrace messages to trace the hop-by-hop path to the
destination MEP or MIP. All the MPs along the path to the destination
intercept the linktrace messages and send a reply. This enables you to
isolate failures to smaller segments of the network.
Prerequisites
(page 72).
(page 76).
Procedure steps
Step Action
Maintenance Domain.

NN46220-504 02.01 Standard
4.2 3 August 2007
.

The Maintenance Association dialog box opens.
4 Select an MA to activate its LinkTrace button.
5 Click the LinkTrace button.

The LinkTrace dialog box opens (see the following figure).
LinkTrace dialog box
—End—
Variable Value
Sets the priority level for transmitting continuity
Vlan Priority check messages. The range is from 0 to 7, and
the default is 7.
Specifies the MAC address of the destination
DestMacAddress
MEP.
DestMepId Specifies the ID of the destination MEP.
Indicates whether the destination is the MEP
DestIsMepId
ID: true or false.

NN46220-504 02.01 Standard
4.2 3 August 2007
.
Variable Value
Ttl Specifies the time-to-live (TTL) value for the
linktrace message. Each MP on the way to the
destination does the following:
• decrements the TTL field in the linktrace
frame
• sends a linktrace reply message to the
originating MEP
• forwards the original linktrace message to
the destination
The linktrace message is forwarded until it

Status Shows the status of the linktrace command:
• ready indicates that the MEPs are ready for
you to initiate a linktrace message.
• not ready indicates that the MEPs are not
configured so you cannot initiate a linktrace
messaged.
• transmit initiates a linktrace message.
Creating a transparent domain identifier

Create a transparent domain identifier (TDI) to enable PBT and select
a multiplexer (MUX) mode. TDIs support PBT on legacy modules. To
configure PBT on R-modules, see "Configuring service instance IDs" (page
98)
A transparent domain (TD) is the same as a VLAN within a customer
network or a VPN within a service provider’s network. A TDI is simply the
ID for one TD, which is equivalent to a VPN ID.
The TD transports customer traffic between endpoints within the TD.
Because TDIs allow service providers to create separate logical networks for
each customer, this mechanism ensures the separation of customer traffic.
This section describes the commands for using TDIs with PBT. For more
information about TDIs, see Configuration — UNI and Endpoints for
non-PBT VPNs (NN46220-506).
Procedure steps
Step Action
1 From the Device Manager menu, choose VPN > TDI.

NN46220-504 02.01 Standard
4.2 3 August 2007
.
The TDI dialog box opens with the General tab displayed (see the
following figure).
Transparent Domain dialog box
2 Click Insert.
The TDI, Insert General dialog box opens (see the following figure).
TDI, Insert General dialog box
3 Assign an ID to this TDI.

4 Name the TDI.
5 Set MuxMode to oneToone
6 In the AdminState field, select enable.
7 In the PbtEnable field, select enable.
8 Click Insert.
—End—

NN46220-504 02.01 Standard
4.2 3 August 2007
.
Variable Value
Id Assigns a unique index number to this TDI.
Device Manager assigns this automatically,
which you can overwrite.
Name Assigns a name to this TDI.
MappedVlan PBT does not support mapped VLANs. If you
enable PBT, the MERS ignores this parameter.
See PbtEnable.
This is an optional parameter that sets the

mapped NNI VLAN for the TDI.
MuxMode Sets the MUX mode so that you can map one
or many qtags to the endpoints for this TDI.
PBT uses one-to-one mode.
oneToone sets the MUX mode value to

one-to-one mode.
manyToone sets the MUX mode value to

many-to-one mode.
AdminState Administratively enables or disables the TDI.
PbtEnable Enables or disables PBT on this domain. The
default is disable.
Configuring a TDI endpoint

Configure a TDI endpoint to identify the path for a specific customer’s
traffic within the assigned TD. Use this command to identify the connection
type, which for PBT must be point-to-point. You also use this command to
establish an association with the maintenance domain by specifying the
MEP ID. TDI endpoints also define QoS rules and apply policers to the
customer traffic.
This section describes the commands for using TDI endpoints with PBT.
For more information about TDI endpoints, see Configuration — UNI and
Endpoints for non-PBT VPNs (NN46220-506).
Prerequisites
• Create a TDI. For information, see "Creating a transparent domain
identifier" (page 89).

NN46220-504 02.01 Standard
4.2 3 August 2007
.
Procedure steps
Step Action
1 From the Device Manager menu, choose VPN > TDI.

The TDI dialog box opens with the General tab displayed.
2 Select Endpoint.
The TDI dialog box opens with the Endpoint tab displayed (see the
following figure).
TDI Endpoint dialog box
3 Click Insert.
The TDI, Insert Endpoint dialog box opens (see the following figure).
TDI, Insert Endpoint dialog box

NN46220-504 02.01 Standard
4.2 3 August 2007
.
4 Assign an ID to this TDI endpoint.
5 In the UniAddr field, enter the port or NPU’s ID.

6 In the Name field, assign a name to this TDI endpoint.
7 In the ConMode field, set the connection mode to pt2pt

(point-to-point).
8 In the RemoteUni field, specify the remote TDI endpoint using the
port or NPU’s ID.
9 In the Qtags field, add Q tags to classify customer traffic.

11 Click Insert.
—End—

NN46220-504 02.01 Standard
4.2 3 August 2007
.
Variable Value
TdId Sets a unique numeric value, in the range 1 and 16 777 215, that
represents the id of the transparent domain you are configuring.
UniAddr Sets the UNI ID (in IP notation)
Name Allows you to enter a unique name that identifies the TDI endpoint.
• Enter a string length in the range 1 and 32 alphanumeric
characters.
ConMode Allows you to set the connection-type value for the endpoint.
• any2any sets the connection-type value to any-to-any mode.
• hub sets the connection-type value to hub mode.
• spoke sets the connection-type value to spoke mode.
• pt2pt sets the connection-type value to point-to-point mode.
RemoteUni Sets the remote-destination UNI ID for point-to-point and spoke
endpoints.
• Enter a destination UNI ID (in IP notation).
Optional:
• Enter the MAC address of the destination UNI ID.
MacAddr Sets the MAC address for the endpoint in the format of
0x00:0x00:0x00:0x00:0x00:0x00
BpduTraffic Sets the BPDU Traffic control for the specified endpoint. The
default setting is normal.
• normal all BPDU traffic forwards without restriction.
• expedite sets the endpoint to expedite forwarding of BPDU
packets by raising the QoS level to the highest level defined
within the priority mapping values.
• drop drops selected BPDU traffic.
LocalMacAgeTimer Sets the MAC address ageing timer for locally learned customer
destination MAC address. This variable is valid for end-points
created on ESM ports only.
.
• number is an integer value in the range 1 and 65 535 seconds,
that represents the ageing time.

NN46220-504 02.01 Standard
4.2 3 August 2007
.
Variable Value
RemoteMacAgeTimer Sets the MAC address ageing timer for customer destination MAC
address learned from remote network UNI IDs. This variable is
valid for end-points created on ESM ports only.
• number is an integer value in the range 1 and 65 535 seconds,
that represents the ageing time.
MacTblSize Sets the maximum MAC table size for the endpoint. This variable
is valid for end-points created on ESM ports only.
• Enter an integer value in the range 0 and 97 000 entries, that
represents the MAC table size. This is true for ESM only, not
for R modules
If you enter a value of 0 (zero) you disable the MAC table size
parameter.
MacTblWaterMk Defines a high-watermark threshold for the MAC table size. When
this threshold is exceeded, the system sends an SNMP trap
to inform you that the threshold limit has been exceeded. This
variable is valid for end-points created on ESM ports only.
• Enter an integer value in the range 0 and 90%, that represents
the MAC table size threshold limit.
If you enter a value of 0 (zero) you disable the mac-table-watermark

threshold parameter.
IngressCosProfileName Sets the Cos profile for the ingress endpoint.
• Choose from a predefined selection of cos profiles.
• Default value is Default_Profile.
EgressCosProfileName Sets the Cos profile for the egress endpoint.
• Choose from a predefined selection of cos profiles.
• Default value is Default_Profile.
IngressPolicer Allows you to enable or disable the specified endpoint’s ingress
cos-profile command.
• enable enables the ingress cos-profile command.
• disable disables the ingress cos-profile command.
EgressPolicer Allows you to enable or disable the specified endpoint’s egress
• enable enables the egress cos-profile command.
• disable disables the egress cos-profile command.

NN46220-504 02.01 Standard
4.2 3 August 2007
.
Variable Value
PriMapping Sets the SP priority mapping for the endpoint.
• Enter a string length in the format a:b:c:d:e:f:g:h.
Where:
Each string character represents a value in the range 0 and 7,
which indicates the SP QoS remarking.
PriOverride Configures the endpoint to use DSCP/TOS bits for QoS
classification.
• Checked indicates that the endpoint uses DSCP/TOS bits
for QoS classification.
• Unchecked indicates that the endpoint uses P-bits for QoS
classification.
Qtags Sets the q-tags to the TLS-switched endpoints.
• Enter an integer value in the range 1 and 4 096, that
represents the customer 802.1 q-tag ID.
Q-tag 4096 is a special tag ID for classifying untagged packets.

OuterQtag Adds an outer q-tag parameter for a QinQ -type endpoint.
• Enter an integer value in the range 1 and 4 095, that
represents the customer 802.1 q-tag ID.
TrunkGroup Identifies the trunk group.
IngressMirrorState Sets the ingress mirror state for Endpoint:
• enable
• disable
EgressMirrorState Sets the egress mirror state for the endpoint:
• enable
• disable
PolicingOption Specify to polices frames before or after encapsulating packets
with OEL2.
• preEncap polices frames before encapsulating packets with
OEL2.
• postEncap polices frames after encapsulating packets with
OEL2.
For a full discussion of policing and other QoS features, see QoS
and Traffic Management (NN46220-508).

NN46220-504 02.01 Standard
4.2 3 August 2007
.
Variable Value
PriOverrideType When PriOverride is enabled (checked), this command specifies
what QoS field to use.
• tos specifies Type of Service (ToS).
• dscp specifies Differentiated Services Code Point (DSCP).
The default is ToS.

ColorBaseRemarking Enables or disables color-based remarking on this endpoint.
• enable allows the policer to use color-aware mapping
• disable allows the policer to use color-blind mapping.

DropRedColorPackets Determines whether or not packets marked red are dropped.
• if checked, the policer drops the packets.
• if unchecked, the policer uses the red mapping.
DefaultTdi Configures this port as a default TDI endpoint. You can configure
one default TDI endpoint per port only.
• enable means that ingress packets that do not belong to any
of the configured TDI ports are sent to this port.
• disable means that ingress packets that do not belong to any
of the configured TD ports are dropped.
UserLabel1 Add a label to provide more management information or data
that would be included in all traps related to this object. Check
with your network administrator to make the label meaningful to
the trap receiver.
UsersLabel2 Add a second label to provide more management information or
data that would be included in all traps related to this object. Check
the trap receiver.
L2ptMacSwapCdp Enable or disable L2pt (Layer 2 Tunneling Protocol) MAC
swapping for a CDP (Cisco Discovery Protocol) endpoint.
L2ptMacSwapVtp Enable or disable L2pt (Layer 2 Tunneling Protocol) MAC
swapping for a VTP (Vlan Trunking Protocol) endpoint.
L2ptMacSwapStp Enable or disable L2pt (Layer 2 Tunneling Protocol) MAC
swapping for an STP endpoint.
AdminState Sets the AdminState for Endpoint:
• enable
• disable

NN46220-504 02.01 Standard
4.2 3 August 2007
.
Configuring service instance IDs

Configure a service instance IDs (I-SID) to enable PBT on R-modules.
I-SIDs support PBT on R-modules. To configure PBT on legacy modules,
see "Creating a transparent domain identifier" (page 89).
This feature enables you to configure a Provider Backbone Bridge (PBB)
network that complies with IEEE 802.1ah, which supports MAC-in-MAC.
This section describes the commands for using I-SIDs with PBT. For more
information such as configuring client MEPs and displaying I-SID and I-SID
endpoint statistics, see Configuration—UNI and Endpoints for non-PBT
VPN (NN46220-506).
Procedure steps
Step Action
1 From the Device Manager menu bar, select VPN > I-SID.
The ISID dialog box appears with the General tab displayed (see
ISID dialog box, General tab
2 Click Insert.
The ISID, Insert General dialog box appears (see the following
figure).

NN46220-504 02.01 Standard
4.2 3 August 2007
.
Configuring service instance IDs 99
ISID, Insert General dialog box
3 Enter a name for this I-SID.

5 In the PbtEnable field, select enable.

6 Change the other default settings to customize your configuration.
For information on the I-SID fields, see the following table.
7 Click Insert.
—End—
Variable Value
Id Assigns a unique index number to this I-SID. Device Manager
assigns this automatically, which you can overwrite.
Name Assigns a name to this I-SID.
AdminState Enables or disable the I-SID. The ForceDisable administration
state disables the I-SID even if the I-SID endpoints are in the active
state. When you invoke this command, the endpoints are placed
into the "operational down" state, and the administrative state
remains unchanged.
PbtEndable Enables or disables PBT on the I-SID.

NN46220-504 02.01 Standard
4.2 3 August 2007
.
Configuring an I-SID endpoint

Configure an I-SID endpoint to support MAC-in-MAC on R-modules
(802.1ah). This feature enables you to configure a Provider Backbone
Bridge (PBB) network that complies with IEEE 802.1ah and supports
MAC-in-MAC.
This section describes the commands for using I-SID endpoints with PBT.
For more information such as configuring client MEPs and displaying I-SID
and I-SID endpoint statistics, see Configuration—UNI and Endpoints for
non-PBT VPN (NN46220-506).
Prerequisites
• Create an I-SID. For information, see "Configuring service instance IDs"
(page 98).
Procedure steps
Step Action
1 From the Device Manager menu bar, select VPN > I-SID .
The ISID dialog box open with the General tab displayed.
2 Click Endpoint.
The ISID dialog box, Endpoint tab opens.
3 Click Insert.
The I-SID Endpoint Insert dialog box appears (see the following
figure).

NN46220-504 02.01 Standard
4.2 3 August 2007
.
ISID, Insert Endpoint dialog box
4 Click any box to enter or select data as necessary.

NN46220-504 02.01 Standard
4.2 3 August 2007
.
6 Click Insert.
—End—
Variable Value
IsidId Assigns a unique index number to this I-SID.
Port Identifies the port assigned to this endpoint.
MltID Identifies MLT assigned to this endpoiont. The system supports up
to 128 UNI MLTs. You can assign MltIDs in the range of 0 to 256.
However, the maximum number of MLT identifiers you can configure
is 128.
RingId A unique integer value, in the range of 1 and 254, which represents
the ESU ring number that the Metro ESU 1800 or 1850 is connected
to.
ModId A unique integer value (in the range of 1 to 23) that identifies the
Metro ESU 1800 or 1850 within the ring.
EsuPort A unique integer value (in the range 1 to 28) that identifies the
physical port on the Metro ESU 1800 or 1850.
Name Names the endpoint, which by default is EP-<sid> PORT
<PortNum>. For example, if SID=1 and it uses port 1/2, the endpoint
name is EP-1 PORT 1/2.
ConnectType Specifies the type of endpoint connection: any2any or pt2pt.
RemoteMacAddr Identifies the remote MAC address of the other endpoint.
IngressCosProfileName Sets the Cos profile for the ingress endpoint. Choose from a
predefined selection of cos profiles. Default value is Default_Profile.
EgressCosProfileName Sets the Cos profile for the egress endpoint. Choose from a
predefined selection of cos profiles. Default value is Default_Profile.
IngressPolicer Allows you to enable or disable the specified endpoint’s ingress
• enable enables the ingress cos-profile command.
• disable disables the ingress cos-profile command.
The default is enable.

NN46220-504 02.01 Standard
4.2 3 August 2007
.
Variable Value
EgressPolicer Allows you to enable or disable the specified endpoint’s egress
• enable enables the egress cos-profile command.
• disable disables the egress cos-profile command.

IngressMirror State Sets the administrative state of ingress port mirroring for the
endpoint.
• enable allows ingress mirroring.
• disable turns off ingress mirroring.

EgressMirrorState Sets the administrative state of egress port mirroring for the endpoint.
• enable allows egress mirroring.
• disable turns off egress mirroring.

PriMapping Sets the SP priority mapping for the endpoint. Enter a string length
in the format a:b:c:d:e:f:g:h. Each string character represents a
value in the range 0 and 7, which indicates the SP QoS remarking.
PriOverride Configures the endpoint to use DSCP/TOS bits for QoS
classification.
• Checked indicates that the endpoint uses DSCP/TOS bits for
QoS classification
• Unchecked indicates that the endpoint uses P-bits for QoS
classification
BpduTraffic Sets the BPDU Traffic control for the specified endpoint.
• normal allows all BPDU traffic forward without restriction.
• expedite sets the endpoint to expedite forwarding of BPDU
packets by raising the QoS level to the highest level defined
within the priority mapping values.
• drop drops selected BPDU traffic.
The default setting is normal.

NN46220-504 02.01 Standard
4.2 3 August 2007
.
Variable Value
ServiceType Set the service type value.
• transparent sets the service type value to TLS transparent mode.
• switched sets the service type value to TLS switched mode.
• qnq1 sets the service type value to Q&Q (1) mode.
• qnq2 sets the service type value to Q&Q (2) mode.
•
C-Vlans Identifier for the customer VLAN. Use 4096 to represent untagged
customer packets.
S-Vlan Adds the specified s-VLAN to this endpoint. Applicable only to
endpoints with service type qnq1 or qnq2.
TrunkGroup Identifies the Trunk Group.
PolicingOption Specify to polices frames before or after encapsulating packets with
OEL2.
• preEncap polices frames before encapsulating packets with
OEL2.
• postEncap polices frames after encapsulating packets with
OEL2.
For a full discussion of policing and other QoS features, see QoS
and Traffic Management (NN46220-508).
PriOverrideType When PriOverride is enabled (checked), this command specifies
what QoS field to use.
• tos specifies Type of Service (ToS).
• dscp specifies Differentiated Services Code Point (DSCP).
The default is ToS.

ColorBaseRemarking Enables or disables color-based remarking on this endpoint.
• enable allows the policer to use color-aware mapping
• disable allows the policer to use color-blind mapping.

DropRedColorPackets Determines whether or not packets marked red are dropped.
• if checked, the policer drops the packets.
• if unchecked, the policer uses the red mapping.

NN46220-504 02.01 Standard
4.2 3 August 2007
.
Variable Value
DefaultIsid Configures this port as a default I-SID endpoint. You can configure
one default I-SID endpoint per port only.
• enable means that ingress packets that do not belong to any of
the configured I-SID ports are sent to this port.
• disable means that ingress packets that do not belong to any of
the configured I-SID ports are dropped.
L2ptMacSwapCdp Enable or disable L2pt (Layer 2 Tunneling Protocol) MAC swapping
for a CDP (Cisco Discovery Protocol) endpoint.
L2ptMacSwapVtp Enable or disable L2pt (Layer 2 Tunneling Protocol) MAC swapping
for a VTP (Vlan Trunking Protocol) endpoint.
L2ptMacSwapStp Enable or disable L2pt (Layer 2 Tunneling Protocol) MAC swapping
for an STP endpoint.
UserLabel1 Add a label to provide more management information or data that
would be included in all traps related to this object. Check with
your network administrator to make the label meaningful to the trap
receiver.
UsersLabel2 Add a second label to provide more management information or
data that would be included in all traps related to this object. Check
the trap receiver.
AdminState Enables or disables the endpoint.
Configuring a PBT VLAN

Configure a PBT VLAN to separate it from non-PBT VLANs. PBT VLANs
behave differently and have the following requirements:
• PBT VLANs do not support broadcast and drops frames that do not
have a forwarding record.
• PBT VLANs require a dedicated Spanning Tree Group (STG).
• PBT VLANs do not support Spanning Tree Protocol (STP).
• A PBT VLAN cannot be the default VLAN for a port.
There are four parts to configuring a PBT VLAN:

• Use the VPN > PBT > Vlans dialog box to reserve VLANs for PBT. You
can configure this command before you create the VLANs.
• Use the VLAN > STG > Insert dialog box to create a PBT spanning tree
group and add ports to it.
• Use the VLAN > STG dialog box to disable STP.
• Use the VLAN > VLANs dialog box to configure VLANs.

NN46220-504 02.01 Standard
4.2 3 August 2007
.
For information about STG, STP, and VLANs, see Configuring VLANs,
Spanning Tree, and Link Aggregation (314725-E).
Procedure steps
Step Action
1 From the Device Manager menu, choose VPN > PBT > Vlans.
The PBT VLANs dialog box opens (see "PBT VLANs dialog box"
(page 106)).
PBT VLANs dialog box
2 Enter the VLAN ID numbers that you want to reserve for PBT.
3 Click Apply.
4 From the Device Manager menu, choose VLAN > STG.

The STG dialog box opens with the Configuration tab displayed (see
"STG dialog box" (page 106)).
STG dialog box
5 Click Insert.
The STG, Insert Configuration dialog box opens (see "STG, Insert
Configuration dialog box" (page 107)).

NN46220-504 02.01 Standard
4.2 3 August 2007
.
STG, Insert Configuration dialog box
6 In the Type field, select pbt.

7 In the PortMembers field, add ports to this STG.
8 In the EnableStp field, clear the check mark to disable STP on this
STG.
9 Click Insert.
10 From the Device Manager menu, choose VLAN > VLANs.

The VLAN dialog box opens with the Basic tab displayed (see the
following figure).
VLAN Basic dialog box
11 Click Insert to configure a new VLAN.
12 In the Type field, select byport to create a port-based VLAN.
13 In the PortMembers field, add ports to this VLAN.
14 In the UnkDstMacDiscard field, select enable.
15 Click Insert.

NN46220-504 02.01 Standard
4.2 3 August 2007
.
—End—
Variable Value
PBT VLANs dialog box
Vlans Adds a VLAN to this PBT domain.
STG dialog box

Type Creates a new spanning tree group.
type <value> is the type of STG. The

choices are stgnormal, stgsvlan, and
stgpbt. For PBT, select stgpbt.
PortMembers Adds ports to a spanning tree group.
Enable Stp Enables or disables the Spanning Tree
Protocol (STP) on the specified spanning
tree group.
VLAN Basic dialog box

Type Creates a port-based VLAN.
• stg-id is the spanning tree group ID (1

to 64).
• name <value> is the name of the
VLAN (0 to 20 characters).
• color <value> is the color of the VLAN
(0 to 32) that Optivity uses to display
the VLAN.

NN46220-504 02.01 Standard
4.2 3 August 2007
.
Configuring a CFM VLAN for MEPs 109
Variable Value
PortMembers Adds ports to an existing VLAN.

port member types:

member
UnkDstMacDiscard Enable activation to drop packets with
unknown destination MAC addresses.
Configuring a CFM VLAN for MEPs

Configure a VLAN to associate multiple MEPs to a specific port so that you
can monitor them through connectivity fault management (CFM).
ATTENTION
The default VLAN for cfm-vid is set to 1, which means it is not set to any VLAN.
This means that no CFM messages are accepted or forwarded. To specify a VLAN
to use as the sending VLAN for port CFM packets, use the following command:
config ethernet <slot/port> cfm-vid <value 0..4094>
Procedure steps
Step Action

The VLAN dialog box opens with the Basic tab displayed.
2 Click CFM Port MEP.

The VLAN dialog box opens with the CFM Port MEP tab displayed
(see the following figure).

NN46220-504 02.01 Standard
4.2 3 August 2007
.
3 Click Insert.
The CFM Port MEP, Insert dialog box opens (see the following
figure).
4 Assign a unique VLAN ID.
5 Indicate which port to use for this VLAN.

6 List the MEPs to associate with this VLAN.
7 Click Insert.

NN46220-504 02.01 Standard
4.2 3 August 2007
.
Configuring a CFM VLAN for MIPs 111
—End—
Variable Value
VlanId Specifies a unique ID for this VLAN.
Specifies the port that you want to associate
Port
with this VLAN.
MepList Specifies the list of MEPs that you want
to add to this VLAN. A MepList consists
of the Maintenance Domain, Maintenance
Association, and the MEP ID and uses the
following format: <md>.<ma>.<mep_id>.
Separate the MEP components with a ’.’ and
separate the MEPs in the list with a ’,’ so a list
looks like the following:
<md1>.<ma1>.<mep_id1>,<md2>.<ma2>.<m
ep_id2>,...
You can have up to eight MEPs in the MepList.
Configuring a CFM VLAN for MIPs

Configure a VLAN to associate multiple MIPs to a specific port so that you
can monitor them through connectivity fault management (CFM).
Procedure steps
Step Action

The VLAN dialog box opens with the Basic tab displayed.
2 Click CFM Port MIP.

The VLAN dialog box opens with the CFM Port MIP tab displayed
(see the following figure).

NN46220-504 02.01 Standard
4.2 3 August 2007
.
3 Click Insert.
The CFM Port MIP, Insert dialog box opens (see the following figure).
4 Assign a unique VLAN ID.
5 Indicate which port to use for this VLAN.
6 List the MIPs to associate with this VLAN.
7 Click Insert.
—End—
Variable Value
VlanId Specifies a unique ID for this VLAN.
Specifies the port that you want to associate
Port
with this VLAN.
MipList Specifies the list of MIPs that you want
to add to this VLAN. A MipList consists
of the Maintenance Domain, Maintenance
Association, and the MIP ID and uses the
following format: <md>.<ma>.<mip_id>.
Separate the MEP components with a ’.’ and
separate the MEPs in the list with a ’,’ so a list
looks like the following:
<md1>.<ma1>.<mip_id1>,<md2>.<ma2>.<m
ip_id2>,...
You can have up to eight MIPs in the MipList.
Creating the local end of a PBT trunk

Create the local end to specify the network-to-network (NNI) port to use.
The trunk connects two NNI ports across the metro network to transport
traffic. Trunks also carry CFM frames to check the status of the path and
detect connectivity failures.

NN46220-504 02.01 Standard
4.2 3 August 2007
.
A PBT trunk consists of two unidirectional trunks going in opposite

directions. Each unidirectional trunk originates at one MERS NNI port and
terminates on an NNI port of a different MERS. These trunks are grouped
together and share the same pair of endpoints.
When you configure a trunk, PBT does not automatically add or remove
the MAC address for the trunk VLAN to the forwarding database. This
eliminates the possibility of the MAC address getting inadvertently removed
ATTENTION
You have to manually add and remove MAC addresses for the trunk VLAN.
Procedure steps
Step Action
1 From the Device Manager menu, choose VPN > PBT > Trunk.
The PBT Trunk dialog box opens (see the following figure).
PBT trunk dialog box
2 Click Insert.
The PBT Trunk, Insert dialog box opens (see the following figure).

NN46220-504 02.01 Standard
4.2 3 August 2007
.
PBT Trunk, Insert dialog box
3 Enter a name for the trunk.
4 In the Port field, specify the local NNI port that the trunk should use.
6 In the MAC field, specify the MAC address of the remote NNI port.
To find the MAC address of the remote NNI, log on to the MERS
8600 on the other end of this trunk. Click Edit > Chassis > Chassis
tab and note the address in the BaseMacAddr field.
7 In the MdName field, associate this trunk to an MD.
8 In the MaName field, associate this trunk to an MA.

9 In the VlanId field, specify the VLAN to use on the local end of this
trunk.
10 In the ReverseVlanId field, specify the VLAN that the remote end
of this trunk should use.
11 In the MepId field, associate this trunk to a MEP.
12 In the HoldTimer field, set the hold time.

13 Enter the MAC address of the remote MEP.
14 Click Insert.
—End—

NN46220-504 02.01 Standard
4.2 3 August 2007
.
Variable Value
Name Assigns a name to this trunk.
Port Specifies the port to use for this PBT trunk.
AdminState Administratively enables or disables the PBT
trunk.
Mac Specifies the MAC address of the MERS 8600
on the other end of this trunk.
To get this address, click Edit > Chassis >

Chassis tab on the remote MERS 8600 and
note the address after BaseMacAddr field.
MdName Specifies the MD to use with this PBT trunk.
MaName Specifies the MA to use with this PBT trunk.
VlanId Specifies the VLAN to use with this
unidirectional trunk. This trunk and the
opposing reverse-vlan unidirectional trunk
comprise one bidirectional PBT trunk. The
range is 0..4094. Only 0,2,3..4094 is legal.
ReverseVlanId Specifies a VLAN to use with this PBT trunk.
The default is the configured VLAN for the PBT
trunk. The range is 0..4094. Only 0,2,3..4094
is legal.
MepId Assigns a maintenance endpoint (MEP) to this
PBT trunk. The range of valid MEP IDs is from
1 to 8191. To unassign a MEP ID, enter a 0.
HoldTimer This is an optional parameter that sets the
trunk hold timer value interval (in seconds).
The timer is used to wait after CCM has come
up before we declare the trunk up, so as to
avoid flapping. The range is from 1 to 120, and
the default is 30.
SourceMac Specifies the MAC address of the remote trunk
MEP. This is called the source MAC because it
is the source of the continuity check messages
that detect failures. This field is optional.
UserLabel1 Add a label to provide more management
in all traps related to this object. Check with
your network administrator to make the label
meaningful to the trap receiver.

NN46220-504 02.01 Standard
4.2 3 August 2007
.
Variable Value
SubportQueueSet Assign an index value to this subport queue
set. The range is 1..80, and the default is 1.
Displaying PBT trunk statistics

Display PBT trunk statistics to monitor your system.
Prerequisites
Prerequisites
• Create a PBT trunk. For information, see "Creating the local end of
a PBT trunk" (page 112).
Procedure steps
Step Action
1 From the Device Manager menu, choose VPN > PBT > Trunk.
The PBT Trunk dialog box opens.
2 Select a trunk.

The PBT Trunk Statistics dialog box opens (see the following figure).
—End—

NN46220-504 02.01 Standard
4.2 3 August 2007
.
Configuring a trunk group

Configure a trunk group (TG) to associate a pair of trunks (primary and
secondary). Having two trunks provides failover protection. When CFM
detects a trunk failure, the TG transfers traffic to the secondary or backup
trunk. Note that secondary trunks are not required. However, if there is no
secondary; there is no failover protection.
Traffic flows through the primary or the secondary trunk, never both.
Whichever one is in use is called the active trunk.
In revertive mode, the primary trunk is the active trunk. If a failure occurs on
the primary trunk, the secondary trunk becomes active. Once the primary
trunk recovers from the failure, the primary trunk becomes the active trunk,
after the hold timer interval expires. The hold timer value is configured when
you create the local end.
In non-revertive mode, when the active trunk fails, the other trunk becomes
the active trunk. Traffic does not revert to the trunk that failed, when it
recovers from the failure.
If no endpoints are using the trunk group, the trunk group displays revertive
behavior, even when the revertive mode is disabled.
Prerequisites
• Create two PBT trunks. For information, see "Creating the local end of
a PBT trunk" (page 112).
Procedure steps
Step Action
1 From the Device Manager menu, choose VPN > PBT > Trunk
Group.
The Trunk Group dialog box opens (see the following figure).
Trunk Group dialog box
2 Click Insert.
The Trunk Group, Insert dialog box opens (see the following figure).

NN46220-504 02.01 Standard
4.2 3 August 2007
.
Trunk Group, Insert dialog box
3 Enter a name for the trunk group.

4 Specify a primary PBT trunk.
5 Specify a secondary PBT trunk.
7 Customize the trunk group by adding labels or specifying an active

trunk. For more information, see "Variable definitions" (page 118).
8 Click Insert.
—End—
Variable Value
Name Assigns a name to this trunk group.
PrimaryTrunk Specifies this trunk as the primary trunk.
SecondaryTrunk Specifies this trunk as the secondary trunk,
which serves as a backup to the primary trunk.
ActiveTrunk Specifies this trunk as the active trunk, which
means that it is currently in use.
Revertive Enables or disables making the primary trunk
revert to its former status as the active trunk.
When the primary trunk fails, the secondary

trunk becomes the active trunk.
• When revertive is enabled and the primary
trunk recovers from a failure, the primary
trunk becomes the active trunk, after the
hold timer interval expires.

NN46220-504 02.01 Standard
4.2 3 August 2007
.
Variable Value
• When revertive is disabled, the secondary

trunk remains the active trunk after the
primary trunk recovers from failure.

Configuring PBT local switching

Configure PBT local switching to define a trunk group as a loopback VLAN.
The trunk group loopback VLAN transports data between two locally
switched UNIs. It is a dedicated VLAN used for PBT local switching and
nothing else. The trunk group loopback VLAN must be a PBT VLAN, and
there can only be one loopback VLAN per switch.
Prerequisites
• Configure a PBT VLAN. For information, see "Configuring a PBT VLAN"
(page 105).
• Configure a trunk group. For information, see "Configuring a trunk
group" (page 117).
Procedure steps
Step Action
1 From the Device Manager menu, choose VPN > PBT > Trunk
Group.
2 Specify a PBT VLAN to be the loopback VLAN for this trunk group.
—End—
Displaying NNI connections

Display network-to-network interface (NNI) connections to find out
information about the connections.

NN46220-504 02.01 Standard
4.2 3 August 2007
.
Variable Value
Port Displays the PBT trunk port number.
ServiceId Displays the TDI or I-SID ID.
PwIndex Displays the pseudowire index associated with this NNI.
TlsIndex Displays the access port index associated with this NNI.
TgName Displays the PBT trunk group name.
Displaying NNI statistics

Display network-to-network interface (NNI) statistics to monitor your system
performance.
Procedure steps
Step Action
1 From the Device Manager menu, choose VPN > PBT > NNI.
The NNI dialog box opens.
2 Select an NNI.

The NNI statistics dialog box opens (see the following figure).
NNI statistics
—End—

NN46220-504 02.01 Standard
4.2 3 August 2007
.
Configuring PBT policing options 121
Variable Value
Oel2RxOctets Shows the total number of Optical Ethernet Layer 2
(OEL2) encapsulated bytes processed on this ingress
NNI port.
Oel2RxDroppedOctets Shows the total number of OEL2 encapsulated bytes
dropped by this ingress NNI port.
MimRxOctets Shows the total number of MAC-in-MAC or 802.1ah (MIM)
encapsulated bytes processed on this ingress NNI port.
MimRxDroppedOctets Shows the total number of MIM encapsulated bytes
PweRxOctets Shows the total number of Pseudowire (Pwe)
encapsulated bytes processed on this ingress NNI port.
PweRxDroppedOctets Shows the total number of Pwe encapsulated bytes
Configuring PBT policing options

Configure PBT policing options to police PBT frames before or after
encapsulating packets with OEL2 (using a TDI) or Mac-in-Mac or 802.1ah
(using an I-SID). For a full discussion of policing and other QoS features,
see QoS and Traffic Management (NN46220-508).
Procedure steps
Step Action
1 From the Device Manager menu bar, select one of the following
paths to select either a TDI or an I-SID:VPN > TDI or VPN > I-SID.
The I-SID dialog box open with the General tab displayed.
2 Click Endpoint.
3 Click Insert.
The I-SID Endpoint Insert dialog box appears (see the following
figure).

NN46220-504 02.01 Standard
4.2 3 August 2007
.
4 In the PolicingOption field, select how you want to police the frames:
pre or post encapsulation.
—End—
Tracking dropped PBT packets

Track drop packets so you can monitor how much traffic is not getting
through your network. This feature enables you to track packets that have
unknown destination MACs.
A dedicated PBT counter tracks packets with unknown destination MACs per
port. Every time the MERS 8600 drops an unknown MAC packet ingressing
the UNI port, it increments the counter and generates an SNMP trap.
Procedure steps
Step Action
1 Select the port that you want to monitor.
2 From the Device Manager menu, choose Graph > Port.

The Port dialog box opens.

NN46220-504 02.01 Standard
4.2 3 August 2007
.
3 Click the PBT tab.

The PBT port dialog box opens (see the following figure).
—End—
Configuring PBT with MSTP

MERS 8600 supports PBT in an MSTP/RSTP network, but you cannot
configure RSTP on a MERS 8600. RSTP allows only one instance of STP,
which means all ports and all VLANs are part of the same STP instance.
This makes it impossible to support PBT with RSTP.
However, you can configure MSTP on a MERS 8600. Just like there is a
specific STP instance dedicated for PBT VLANs, an MSTP instance is also
dedicated for PBT VLANs. If you enable MSTP, then you must create all
PBT VLANs with this special MSTP instance. Furthermore, MSTP does not
operate in a compatibility mode. This means that all the switches in the
network must be MSTP enabled or none should be enabled.
Procedure steps
Step Action
1 From the Device Manager menu, choose VLAN > Spanning Tree
> Globals.
The Globals dialog box opens (see the following figure).
2 Click mstp.
3 Click Apply.

NN46220-504 02.01 Standard
4.2 3 August 2007
.
A Warning message opens (see the following figure).
4 Click Yes.
5 Click Actions > Save Boot Config.
6 Click Device > Telnet .

7 Log on to the switch.
8 Enter boot and enter y to reboot the switch.

This action removes all STG VLANs.
9 Click VLAN > Spanning Tree > MSTP to create new MSTP VLANs.
—End—

NN46220-504 02.01 Standard
4.2 3 August 2007
.
125
PBT configuration example

This chapter provides an end-to-end example of a basic Provider Backbone
Transport (PBT) configuration. It includes all the commands for configuring
two MERS 8600s, one on each side of a service provider’s network. In this
example, the MERS 8600 on the left side of the network is MERS 8600
#1 and the MERS 8600 on the right side of the network is MERS 8600
#2. The example also shows how to configure both types of maintenance
domains (trunk and service instance) even though only the trunk domain
is mandatory for PBT. In addition, there is an example of configuring three
switches such that the middle, transient, switch has a static entry point,
which allows PBT traffic to pass through from the switch where the trunks
begin to the switch where the trunks terminate.
ATTENTION
To maintain backward compatibility, the CLI hierarchy changed for the
unknown-destmac-discard command. This command is now under flags.
When you first upgrade the boot monitor with oe8b4100.img, the existing boot.cfg
loads with no problem. After the switch is up and running and before you start
configuring PBT, set the bootconfig flag to discard unknown MAC destinations.
The default setting is false. Use the following command to set the bootconfig flag
to true. Then save boot.cfg and reboot the MERS 8600.
config bootconfig flags unknown-destmac-discard true
If you are not upgrading the boot monitor, use the following steps to stop
in monitor mode:
Step Action
1 Enter edit boot.cfg.
2 Delete the following line.

unknown-destmac-discard true
3 Add the following line.

flags unknown-destmac-discard true

NN46220-504 02.01 Standard
4.2 3 August 2007
.
126 PBT configuration example
4 Enter save boot.cfg.
5 Enter source boot.cfg.
6 Reboot.
—End—
Each section within the example shows the commands related to a specific
task. To learn more about these commands and their parameters, there is a
link to the CLI and Device Manager step-by-step procedures related to that
task. This chapter includes the following topics.
Navigation
• "PBT domains" (page 126)
• "MERS 8600 number 1" (page 129)
• "MERS 8600 number 2" (page 134)
• "MERS 8600 Three Switch Configuration" (page 139)
PBT domains
The following figures show the domains configured in this example.

NN46220-504 02.01 Standard
4.2 3 August 2007
.
PBT domains 127
Trunk maintenance domain example

NN46220-504 02.01 Standard
4.2 3 August 2007
.
Service instance maintenance domain example for TDI

NN46220-504 02.01 Standard
4.2 3 August 2007
.
Service instance maintenance domain example for ISID
MERS 8600 number 1

The following configuration tasks apply to MERS 8600 #1, which is shown
on the left side of the network:
• "Maintenance domain configuration" (page 130)
• "Maintenance association configuration" (page 130)
• "Maintenance endpoint configuration" (page 130)
• "Remote maintenance endpoint configuration" (page 131)

NN46220-504 02.01 Standard
4.2 3 August 2007
.
• "Port configuration" (page 131)

• "PBT-VLANs configuration" (page 131)
• "STG configuration" (page 132)
• "VLAN configuration" (page 132)
• "Trunk configuration" (page 132)
• "Trunk-group configuration" (page 133)
• "UNI configuration" (page 133)
• "I-SID configuration" (page 134)
Maintenance domain configuration

The following commands show how to configure a maintenance domain.
For more information and to see how to configure this command with the
CLI, see "Creating a maintenance domain" (page 24).
For more information and to see how to configure this command with Device
Manager, see "Creating a maintenance domain" (page 72).
cfm md SIDOMAIN create index 1

cfm md TRUNKDOMAIN create index 2
Maintenance association configuration

The following commands show how to configure a maintenance association
for both trunk domains.
CLI, see "Creating a maintenance association" (page 25).
Manager, see "Creating a maintenance association" (page 73).
cfm md SIDOMAIN ma masi1901 create index 1

cfm md TRUNKDOMAIN ma matr1901 create index 1
Maintenance endpoint configuration

The following commands show how to configure maintenance endpoints
for all domains.
CLI, see "Creating a maintenance endpoint" (page 27).
Manager, see "Creating a maintenance endpoint" (page 76).

NN46220-504 02.01 Standard
4.2 3 August 2007
.
cfm md SIDOMAIN ma masi1901 mep 10 create

cfm md SIDOMAIN ma masi1901 mep 10 state enable
cfm md TRUNKDOMAIN ma matr1901 mep 10 create
cfm md TRUNKDOMAIN ma matr1901 mep 10 state enable
Remote maintenance endpoint configuration

The following commands show how to configure remote maintenance
endpoints.
CLI, see "Creating a remote maintenance endpoint" (page 32)
Manager, see "Creating a remote maintenance endpoint" (page 79)
cfm md SIDOMAIN ma masi1901 rmep 20 create

cfm md SIDOMAIN ma masi1901 rmep 20 remote-mac 00:15:e8:b1
:10:16
cfm md TRUNKDOMAIN ma matr1901 rmep 20 create
cfm md TRUNKDOMAIN ma matr1901 rmep 20 remote-mac
00:15:e8:b1:10:17
00:15:e8:b1:10:18
Port configuration
The following commands show how to tag ports to maintain the customer’s
QoS requirements. This is not a PBT-specific command so it is documented
in another manual. See Configuring VLANs, Spanning Tree, and Link
Aggregation (314725-E).
ethernet 4/1 perform-tagging enable

PBT-VLANs configuration
The following command shows how to reserve VLANs for PBT to use.
CLI, see "Configuring a PBT VLAN" (page 51).
Manager, see "Configuring a PBT VLAN" (page 105).
pbt-vlans add 90-93

NN46220-504 02.01 Standard
4.2 3 August 2007
.
STG configuration
The following commands show how to configure STG and disable STP. This
is not a PBT-specific command so it is documented in another manual. See
stg 64 create type stgpbt

stg 64 add ports 2/4,4/1-4/2
stg 64 group-stp disable
VLAN configuration
The following commands show how to configure VLANs. This is not a
PBT-specific command so it is documented in another manual. See
vlan 90 create byport 64 color 1

vlan 90 unknown-destmac-discard activation enable
vlan 90 ports remove 2/1-2/3,2/5-2/8,3/1-3/8,4/2-4/8,8/1-8/48
member portmember
vlan 90 ports add 2/4,4/1 member portmember
vlan 91 ports remove 2/1-2/3,2/5-2/8,3/1-3/8,4/2-4/8,8/1-8/48
member portmember
vlan 92 ports remove
2/1-2/3,2/5-2/8,3/1-3/8,4/1,4/3-4/8,8/1-8/48
member portmember
vlan 93 ports remove
2/1-2/3,2/5-2/8,3/1-3/8,4/1,4/3-4/8,8/1-8/48
member portmember
Trunk configuration
The following commands show how to configure two PBT trunks.
The remote-peer-mac command requires the remote MAC address

of the MERS 8600 on the other end of this trunk. In this case, you are
configuring the MERS #1 so you need the MAC address of MERS #2. To
get that address, enter show sys info on MERS #2 and note the address
after PbtMacAddr under Chassis Info.
CLI, see "Creating the local end " (page 56).

NN46220-504 02.01 Standard
4.2 3 August 2007
.
Manager, see "Creating the local end of a PBT trunk" (page 112).
pbt-trunk tr1901 create

pbt-trunk tr1901 port 4/1
pbt-trunk tr1901 remote-peer-mac 00:80:2d:2f:64:1a
pbt-trunk tr1901 ma-domain TRUNKDOMAIN ma-assn matr1901
pbt-trunk tr1901 vlan 90
pbt-trunk tr1901 reverse-vlan 91
pbt-trunk tr1901 add-mep TRUNKDOMAIN.matr1901.10
pbt-trunk tr1901 hold-time 10
pbt-trunk tr1901 state enable
pbt-trunk tr1902 remote-peer-mac 00:80:2d:2f:64:1a
Trunk-group configuration
The following commands show how to configure a PBT trunk group.
CLI, see "Configuring a trunk group" (page 61).
Manager, see "Configuring a trunk group" (page 117).
trunk-group Path1 create

trunk-group Path1 primary-trunk tr1901
trunk-group Path1 secondary-trunk tr1902
trunk-group Path1 revertive enable
UNI configuration
The following commands show how to configure a UNI. This is not a
PBT-specific command so it is documented in other manuals.
For more information on how to configure this command, see

Configuration—UNI and Endpoints for non-PBT VPNs (NN46220-506).
uni 2.2.2.2 create

uni 2.2.2.2 port 2/4
uni 2.2.2.2 state enable

NN46220-504 02.01 Standard
4.2 3 August 2007
.
I-SID configuration
The following commands show how to configure an I-SID and assign an
I-SID endpoint.
CLI, see "Creating service instance IDs" (page 46)and "Configuring an
I-SID endpoint" (page 47).
Manager, see "Configuring service instance IDs" (page 98)and "Configuring
an I-SID endpoint" (page 100).
i-sid 100 create

i-sid 100 pbt enable
i-sid 100 state enable
i-sid 100 end-point port 1/25 create
i-sid 100 end-point port 1/25 connection p2p
mac 00:15:e8:b1:10:17
i-sid 100 end-point port 1/25 add-c-vlan 900
i-sid 100 end-point port 1/25 trunk-group tg1
i-sid 100 end-point port 1/25 state enable
MERS 8600 number 2

The following configuration tasks apply to the MERS 8600 #2, which is
shown on the right side of the network:
• "Maintenance domain configuration" (page 134)
• "Maintenance association configuration" (page 135)
• "Maintenance endpoint configuration" (page 135)
• "Remote maintenance endpoint configuration" (page 135)
• "Port configuration" (page 136)
• "PBT-VLANs configuration" (page 136)
• "STG configuration" (page 136)
• "VLAN configuration" (page 136)
• "Trunk configuration" (page 137)
• "Trunk-group configuration" (page 138)
• "UNI configuration" (page 138)
• "I-SID configuration" (page 138)
Maintenance domain configuration

The following commands show how to configure a maintenance domain.

NN46220-504 02.01 Standard
4.2 3 August 2007
.
CLI, see "Creating a maintenance domain" (page 24).
Manager, see "Creating a maintenance domain" (page 72).
cfm md SIDOMAIN create index 1

cfm md TRUNKDOMAIN create index 2
Maintenance association configuration

The following commands show how to configure a maintenance association
for both trunk domains.
CLI, see "Creating a maintenance association" (page 25).
Manager, see "Creating a maintenance association" (page 73).
cfm md SIDOMAIN ma masi1901 create index 1

Maintenance endpoint configuration

The following commands show how to configure maintenance endpoints
for all domains.
CLI, see "Creating a maintenance endpoint" (page 27).
Manager, see "Creating a maintenance endpoint" (page 76).
cfm md SIDOMAIN ma masi1901 mep 20 create

cfm md SIDOMAIN ma masi1901 mep 20 state enable
Remote maintenance endpoint configuration

The following commands show how to configure remote maintenance
endpoints.
CLI, see "Creating a remote maintenance endpoint" (page 32)

NN46220-504 02.01 Standard
4.2 3 August 2007
.
Manager, see "Creating a remote maintenance endpoint" (page 79)
cfm md SIDOMAIN ma masi1901 rmep 10 create

cfm md SIDOMAIN ma masi1901 rmep 10 remote-mac 00:15:40:b0
:10:16
00:15:40:b0:10:17
00:15:40:b0:10:18
Port configuration
The following commands show how to tag ports to maintain the customer’s
QoS requirements. This is not a PBT-specific command so it is documented
in another manual. See Configuring VLANs, Spanning Tree, and Link
Aggregation (314725-E).

PBT-VLANs configuration
The following command shows how to reserve VLANs for PBT to use.
CLI, see "Configuring a PBT VLAN" (page 51).
Manager, see "Configuring a PBT VLAN" (page 105).
pbt-vlans add 90-93
STG configuration
The following commands show how to configure STG and disable STP. This
is not a PBT-specific command so it is documented in another manual. See
stg 64 create type stgpbt

stg 64 add ports 3/1-3/2,7/1
stg 64 group-stp disable
VLAN configuration
The following commands show how to configure VLANs. This is not a
PBT-specific command so it is documented in another manual. See

vlan 90 ports remove 3/2-3/8,7/2-7/8 member portmember

NN46220-504 02.01 Standard
4.2 3 August 2007
.

vlan 91 ports remove 3/2-3/8,7/2-7/8, member portmember
vlan 92 ports remove 3/1,3/3-3/8,7/2-7/8, member portmember
vlan 93 ports remove 3/1,3/3-3/8,7/2-7/8 member portmember
Trunk configuration
The following commands show how to configure two PBT trunks.
The remote-peer-mac command requires the remote MAC address

of the MERS 8600 on the other end of this trunk. In this case, you are
configuring the MERS #2 so you need the MAC address of MERS #1. To
get that address, enter show sys info on MERS #1 and note the address
after PbtMacAddr under Chassis Info.
CLI, see "Creating the local end " (page 56).
Manager, see "Creating the local end of a PBT trunk" (page 112).

pbt-trunk tr1901 remote-peer-mac 00:0f:06:c6:d0:1a
pbt-trunk tr1902 remote-peer-mac 00:0f:06:c6:d0:1a

NN46220-504 02.01 Standard
4.2 3 August 2007
.
Trunk-group configuration
The following commands show how to configure a PBT trunk group.
CLI, see "Configuring a trunk group" (page 61).
Manager, see "Configuring a trunk group" (page 117).
trunk-group Path1 create

trunk-group Path1 primary-trunk tr1901
trunk-group Path1 secondary-trunk tr1902
trunk-group Path1 revertive enable
UNI configuration
The following commands show how to configure a UNI. This is not a
PBT-specific command so it is documented in other manuals.
For more information on how to configure this command, see

Configuration—UNI and Endpoints for non-PBT VPNs (NN46220-506).
uni 1.1.1.1 create

uni 1.1.1.1 port 7/1
uni 1.1.1.1 state enable
I-SID configuration
The following commands show how to configure an I-SID and assign an
I-SID endpoint.
CLI, see "Creating service instance IDs" (page 46)and "Configuring an
I-SID endpoint" (page 47).
Manager, see "Configuring service instance IDs" (page 98)and "Configuring
an I-SID endpoint" (page 100).
i-sid 200 create

i-sid 100 pbt enable
i-sid 100 state enable
i-sid 100 end-point port 1/26 create
i-sid 100 end-point port 1/26 connection p2p
mac 00:15:e8:b1:10:18
i-sid 100 end-point port 1/26 add-c-vlan 900
i-sid 100 end-point port 1/26 trunk-group tg1
i-sid 100 end-point port 1/26 state enable

NN46220-504 02.01 Standard
4.2 3 August 2007
.
MERS 8600 Three Switch Configuration

This example shows how to configure three switches such that the middle,
transient, switch has a static entry point, which allows PBT traffic to pass
through from the switch where the trunks begin to the switch where the
trunks end.
Transient switch with static entry point configuration

The purpose of this example is to allow PBT traffic to pass from the switch
where the trunks begin, through a middle switch, to a switch where the
trunks are terminated. The middle switch must be configured as a transient
switch with a static entry point that idendtifies where the trunks propagate
through. The fdb -static option configures Switch 2 with a static entry
for the PBT trunks to propagate traffic through the switch.
The example consists of three switches that allow PBT traffic to pass
through them.
• Switch 1: Configured for 2 trunks (primary/secondary) that belong to a
trunk group. This is the starting point of the trunk group (MAC address
of "ab:cd:e1:23:45:67").
• Switch 2: Configured as a transient switch with a static entry point. The
trunks pass through this switch.
• Switch 3: Configured for 2 trunks that belong to a trunk group. This is
the ending point of the trunks (MAC address of "12:34:56:78:ab:cd").
The example configures the mep as auto-detect enabled. However,

you can also configure the rmep MAC address for the mep instead of
auto-detect enabled. This optional configuration follows the example
for configuring the switches.
Example: Sw1---->PBT--->Sw2--->PBT-->-Sw3
• SW1 PBT MAC: xx:xx:xx:xx:xx:xx
• SW3 PBT MAC: yy:yy:yy:yy:yy:yy
Switch 1 TRUNK setup
Switch 1 PBT Trunk1 setup:
config cfm md PBT-Trunks create

config cfm md PBT-Trunks ma PBTMA1 create
config cfm md PBT-Trunks ma PBTMA1 auto-detect enable
config cfm md PBT-Trunks ma PBTMA1 ccm-interval 10
config cfm md PBT-Trunks ma PBTMA1 mep 1 create
config cfm md PBT-Trunks ma PBTMA1 mep 1 state enable
ethernet 4/2,4/4 perform-tagging enable
config stg 50 add ports 4/2,4/4

NN46220-504 02.01 Standard
4.2 3 August 2007
.
config pbt-vlan add 23-26

config vlan 23 port add 4/2
config pbt-trunk TRUNK1 create
config pbt-trunk TRUNK1 port 4/2
config pbt-trunk TRUNK1 vlan 23
config pbt-trunk TRUNK1 reverse-vlan 24
config pbt-trunk TRUNK1 remote-mac <remote pbt mac on sw3>
config pbt-trunk TRUNK1 add-mep PBT-Trunks.PBTMA1.1
config pbt-trunk TRUNK1 state enable

config trunk-group TRUNKS create
config trunk-group TRUNKS primary TRUNK1
config trunk-group TRUNKS secondary TRUNK2
Switch 2 transient static entry point configuration

config stg 6 add ports 2/3-2/6
config pbt-vlan 23-26
config vlan 23 port add 2/3,2/5
config vlan 23 fdb-static add <xx:xx:xx:xx:xx:xx>
port 2/3 qos 1
config vlan 23 fdb-static add <yy:yy:yy:yy:yy:yy>
port 2/5 qos 1
config vlan 24 create byport 6 config vlan 24
port add 2/3,2/5
port 2/3 qos 1

NN46220-504 02.01 Standard
4.2 3 August 2007
.

port 2/5 qos 1
port 2/4 qos 1
port 2/6 qos 1
port 2/4 qos 1
port 2/6 qos 1
Switch 3 TRUNK setup
config cfm md PBT-Trunks create

ethernet 4/2,4/4 perform-tagging enable
config stg 50 add ports 4/2,4/4
config pbt-vlan add 23-26


NN46220-504 02.01 Standard
4.2 3 August 2007
.

config trunk-group TRUNKS create
config trunk-group TRUNKS primary TRUNK1
config trunk-group TRUNKS secondary TRUNK2
You can also configure the rmep mac address for the mep, instead of
auto-detect enabled.

config cfm md PBT-Trunks ma PBTMA2 rmep 2 create
config cfm md PBT-Trunks ma PBTMA2 rmep 2 remote-mac
<sw1 PBT mac address>

NN46220-504 02.01 Standard
4.2 3 August 2007
.
143
Index
A L
active trunk 61, 117 linktrace messages 37
loopback messages 35
B
broadcast-on-unknown 12 M
MAC address
C finding remote trunk 132
CCM learning 12
MA parameters in CLI 26 maintenance association
MA parameters in Device configuration example 130
Manager 76 configuring with CLI 25
MEP parameters in CLI 28 configuring with Device Manager 72
MEP parameters in Device maintenance domain
Manager 77 configuration example 130
cfm ethernet type configuring with CLI 24
configuring with CLI 24 configuring with Device Manager 71
connection type 43, 47 maintenance endpoint
configuration example 130
E configuring with CLI 27
configuring with Device Manager 73
enabling PBT 41, 46, 77 statistics 30, 33, 65, 66, 76
encapsulation method 41, 46, 77 maintenance intermediate point
ethernet type (cfm) configuring with CLI 39
configuring with CLI 24 maintenance intermediate point statistics 39
mux mode 41, 46, 77
F
failover protection 61, 117 N
fdb -static option 139 NNI 56, 112
I P
I-SID PBT trunk
configuring with CLI 46 configuration example 132, 133, 139
configuring with CLI 56

NN46220-504 02.01 Standard
4.2 3 August 2007
.
144 Index
configuring with Device static entry point configuration 139

Manager 113 STG (Spanning Tree Group) 51, 105, 132
hold time 58, 115 STP (Spanning Tree Protocol) 12, 51, 105,
PBT VLAN 132
cannot be default 105
configuration example 131 T
configuring with CLI 51, 54 TDI
configuring with Device Manager 91 configuration example 134
PBT, enabling 41, 46, 77 configuring with CLI 41
point-to-point 43, 47 configuring with Device Manager 77
primary trunk 61, 117 transient switch configuration 139
trunk group
Q configuring with CLI 61
qtag 44 configuring with Device
Manager 117
R
remote MAC address 58, 115
U
remote MAC address of trunk 132 UNI 133
remote maintenance endpoint
configuring with CLI 32 V
revertive feature 61 VLAN, configuration example 132
revertive mode 117
S
secondary trunk 61, 117

NN46220-504 02.01 Standard
4.2 3 August 2007
.

All Rights Reserved.
Publication: NN46220-504
Document status: Standard
Document version: 02.01
Document date: 3 August 2007
To provide feedback or report a problem in this document, go to www.nortel.com/documentfeedback.
This document is protected by copyright laws and international treaties. All information, copyrights and any other intellectual
property rights contained in this document are the property of Nortel Networks. Except as expressly authorized in writing by Nortel
Networks, the holder is granted no rights to use the information contained herein and this document shall not be published, copied,
produced or reproduced, modified, translated, compiled, distributed, displayed or transmitted, in whole or part, in any form or media.
The information in this document is subject to change without notice. The statements, configurations, technical data, and
recommendations in this document are believed to be accurate and reliable, but are presented without express or implied warranty.
Users must take full responsibility for their applications of any products specified in this document. The information in this document
is proprietary to Nortel Networks Inc.
Nortel, the Nortel logo, the Globemark, and Passport 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.
Sourced in Canada and the United States of America

NN46220-504 - 02.01 - CFG - (Configuration Provider Backbone Transport)

Uploaded by

Document Information

Original Description:

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

NN46220-504 - 02.01 - CFG - (Configuration Provider Backbone Transport)

Uploaded by

Copyright:

Available Formats

Nortel Metro Ethernet Routing Switch 8600

NN46220-504 (322287-C Rev 01)

Copyright © 2007, Nortel Networks

Sourced in Canada and the United States

Nortel Inc. software license agreement

Configuring PBT with the CLI 15

Nortel Metro Ethernet Routing Switch 8600

Displaying NNI connections 65

Configuring PBT with Device Manager 71

PBT configuration example 125

Nortel Metro Ethernet Routing Switch 8600

Trunk configuration 132

Nortel Metro Ethernet Routing Switch 8600

Nortel Metro Ethernet Routing Switch 8600

New in this release

Nortel Metro Ethernet Routing Switch 8600

RSTP implementations. For information, see "Configuring PBT with

Nortel Metro Ethernet Routing Switch 8600

To reinforce the PBT configuration steps, see "PBT configuration example"

PBT ensures that a predictable customer route is available over the

Nortel Metro Ethernet Routing Switch 8600

it provides the ideal infrastructure for triple play services, Ethernet-based

PBT addresses the main challenges carriers face when deploying an

802.1ad IEEE standard for Provider Bridge Networks

Nortel Metro Ethernet Routing Switch 8600

PBB Provider Backbone Bridging

Nortel Metro Ethernet Routing Switch 8600

Nortel Metro Ethernet Routing Switch 8600

Configuring PBT with the CLI

Nortel Metro Ethernet Routing Switch 8600

• "Configuring port VLANs for MEPs and MIPs" (page 54)

Roadmap of CLI commands

Nortel Metro Ethernet Routing Switch 8600

Nortel Metro Ethernet Routing Switch 8600

Nortel Metro Ethernet Routing Switch 8600

Nortel Metro Ethernet Routing Switch 8600

Nortel Metro Ethernet Routing Switch 8600

Nortel Metro Ethernet Routing Switch 8600

Discarding unknown MAC addresses

Nortel Metro Ethernet Routing Switch 8600

1 Set the bootconfig flag to true. The default setting is false.

2 Reboot the MERS 8600.

Changing the base chassis MAC address

1 Change the base MAC address.

2 Enter Y after the following system message to reboot the chassis.

Nortel Metro Ethernet Routing Switch 8600

Changing the chassis MAC requires the system reboot.

Configuring CFM ethernet type

1 Configure the CFM ethernet type with the following command.

Creating a maintenance domain

One MD may contain several maintenance associations and maintenance

Nortel Metro Ethernet Routing Switch 8600

1 Create an MD with the following command and a string of 1 to 22

2 Verify your configuration.

Creating a maintenance association

1 Create an MA with the following command and a string of 1 to 22

2 Customize your MA by changing the default settings of preconfigured

Nortel Metro Ethernet Routing Switch 8600

Example of configuring a maintenance association

1 Name the MA matr1901 and assign the index value of 1.

2 Change the CCM interval to 1000.

3 Verify your configuration.